I want APIs to android apps, I use material notes app as a personal twitter and to track my excercise, I want to schedule a backup of the app, which surprisingly gives you the internal sqlite database, I'd then sync it to my machine using syncthing and then perform analytics on it. I want to eventually be able to sync up everything & make my phone into my personal assistant like it'd suggest me to call up someone I hadn't called in a long time, remember birthdays, and it'd be voice enabled which'd work offline.
Developer Preview of Android O
81–90 of 115 posts
Re: Developer Preview of Android O
#82I'm most excited about the new APIs for autofilling. Using a password manager on the phone today is a pain. Password filling on webpages and native apps is wonky (to say the least), and most of the time I end up manually coping passwords to clipboard, which is both cumbersome and insecure. I really hope the major password managers are quick to adopt this, and it improves the current user experience. "Autofill APIs: A…
I really hope this works out well. Maybe then we can get it on the desktop!
It really shouldn't be this hard. I personally had to do a lot of hacking to get my password manager to work consistently. UX designers are really determined to make logging in as obtuse as possible.
Re: Developer Preview of Android O
#83Another opportunity wasted to create a unified Android driver model that would allow easy upgrades.
I was curious so I took a look: It seems they're implementing a new system; there are shared libraries in /vendor/lib/hw on my Pixel running O that aren't there on my Pixel XL running 7.1.
sailfish:/ $ ls /vendor/lib/hw
android.hardware.audio.effect@2.0-impl.so android.hardware.graphics.composer@2.1-impl.so android.hardware.vibrator@1.0-impl.so
android.hardware.audio@2.0-impl.so android.hardware.graphics.mapper@2.0-impl.so android.hardware.vr@1.0-impl.so
android.hardware.boot@1.0-impl.so android.hardware.keymaster@3.0-impl.so flp.default.so
android.hardware.camera.provider@2.4-impl.so android.hardware.light@2.0-impl.so gatekeeper.msm8996.so
android.hardware.configstore@1.0-impl.so android.hardware.memtrack@1.0-impl.so keystore.msm8996.so
android.hardware.contexthub@1.0-impl.so android.hardware.nfc@1.0-impl.so sensors.vl530l0.tof.so
android.hardware.drm@1.0-impl.so android.hardware.power@1.0-impl.so sound_trigger.primary.msm8996.so
android.hardware.gatekeeper@1.0-impl.so android.hardware.sensors@1.0-impl.so vulkan.msm8996.so
android.hardware.gnss@1.0-impl.so android.hardware.soundtrigger@2.0-impl.so
android.hardware.graphics.allocator@2.0-impl.so android.hardware.thermal@1.0-impl.so
Re: Developer Preview of Android O
#84Still no user-grantable audio capture permission… Why are only OEM-blessed apps allowed to capture system audio output, when any app can already request permission to screen capture?
I use CyanogenMod and I am able to capture audio and screen, my mother has a lenovo phone which allows you to capture calls directly.
Re: Developer Preview of Android O
#85Still no user-grantable audio capture permission… Why are only OEM-blessed apps allowed to capture system audio output, when any app can already request permission to screen capture?
Option 1: DRM concerns (exploiting the "analog hole" on digital level, or HDCP restrictions - how deep is HDCP actually enforced in Android?) Option 2: Privacy (call recorders come to mind - unrelated: does anyone know of a working call recorder?)
I used CallRec. It wasn't easy to get it working. After rooting my phone, I had to spend hours making other tweaks.
And of course the software ecosystem is so fragmented, and if you do want to find anything out, you have to sift through mountains of misinformation.
Re: Developer Preview of Android O
#86I'm most excited about the new APIs for autofilling. Using a password manager on the phone today is a pain. Password filling on webpages and native apps is wonky (to say the least), and most of the time I end up manually coping passwords to clipboard, which is both cumbersome and insecure. I really hope the major password managers are quick to adopt this, and it improves the current user experience. "Autofill APIs: A…
With Dashlane I have 0 issues with auto fill across apps and chrome.
Re: Developer Preview of Android O
#87Earlier quoted context omitted.
It can't help that Google hasn't released a phone comparable in spirit to the Galaxy Nexus, Nexus 4 and Nexus 5 phones. We're talking about phones that have a practical size, reasonably good specs, and a $300-$400 price tag. The Nexus 6 and 6P were impractically sized for many users. Even the 5X was too large. The Pixel's sizing is perhaps more tolerable, but the price tag is much too high. People hanging on to a Nex…
The OnePlus 3 is a worthy successor to the Nexus line in terms of quality and price (at $399), though I still wish it were a little smaller at times (like the Nexus 5 I used before it).
I also replaced my Nexus 5 with a OnePlus 3. The OnePlus 3 is so large that I develop finger pains reading on the subway. It's ridiculous.
Re: Developer Preview of Android O
#88Earlier quoted context omitted.
But then I have to use their crappy keyboard, which doesn't have all the features of the Google one.
You can just switch keyboards when you need to use 1Password. Not optimal, but not a terrible experience either.
Which is undoubtedly going to be much better with an official Autofill API.
Re: Developer Preview of Android O
#89Earlier quoted context omitted.
I liked my 5x, until the fingerprint recognition suddenly disappeared. Literally disappeared from all settings this week after a restart. Have to restore or something equally tedious.
I liked my 5X until it died from the bootloop issue 1mo out of warranty. Happened to at least two other co-workers and burned me enough to swear off Google phones. I'm not going to drop $700 on something that might last less than a year. OnePlus 3T got my money instead.
May be worth checking to see if you can get an out of warranty replacement. I bought the phone through my carrier (Google Fi) and they replaced it for free with a refurbished 5X. 6 months out of warranty.
Re: Developer Preview of Android O
#90Too bad the OEMs don't keep up. Only 2% of devices have Android 7 (N). http://www.digitaltrends.com/mobile/android-distribution-new...
I look at these previews as an example of things to come 3 years from now. I keep hoping that Google will figure out a solution to that (restrict access to Play Services, say). Until then, I guess I'll continue targeting API 16.
If you are still targeting 16, you should make sure that you are handling a bunch of pretty serious security changes made between 17-21. There are a lot of ways you can shoot yourself in the foot when using the old APIs.