Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Android 9 Pie

android-developers.googleblog.com

Post reply on HN
Print view View original

191–200 of 367 posts

Re: Introducing Android 9 Pie

#191

Post by izacus »

cmurf wrote: post #152

I wonder if Google's own apps are exempt from adaptive battery? I continue to have problems with Google's apps soaking my phone's battery. Reset the phone, and I get 6 days of standby (this is LineageOS). Install Google apps, and it's now 4 hours. Wakelock detector says the apps Inbox, Google, and Google Contacts are the top offenders with dozens of wakes keeping the phone awake between 40% and 99% of the time. Super…

That wakelock detector is probably showing wrong data (especially on newer API levels). Can you try something more advanced like Battery Historian (in dev tools) to see what's waking up the CPU?

(And no, Google apps are beholden to all power saving restrictions like other apps - Play Services being the exception because it services functionality that must work at all times.)

Re: Introducing Android 9 Pie

#192

Post by Latteland »

maxxxxx wrote: post #127
izacus wrote: post #116

Earlier quoted context omitted.

Most of that data is still available, just gated behind permissions that require explicit consent from user now.

I hope that the permissions are better to understand and control than the current ones. Right now they seem to be designed to give the appearance of giving users control but the implementation is pretty bad and user unfriendly.

And the other problem is you install an app all the time and the permissions aren't clearly laid out. I want:

1. tell me I install an app that wants "some list of permissions".

2. let me disable this permission for all apps installed now and in the future.

Re: Introducing Android 9 Pie

#193

Post by rayiner »

Navarr wrote: post #183
rayiner wrote: post #11

> App Actions is a new way to raise the visibility of your app and drive engagement. Actions take advantage of machine learning to surface your app to the user at just the right time, based on your app's semantic intents and the user's context. Aside from the unnecessary jargon, this irks me how it portrays the user as some passive consumer. It really drives home how Google is, first and foremost, an advertising comp…

You're reading a developer blog. The Android.com page is more similar to Apple's: > App Actions predicts what you’re about to do, so you get to your next task more quickly. If you do something like connect your headphones, the playlist you were listening to earlier is front and center. [1] [1] https://www.android.com/versions/pie-9-0/

> You're reading a developer blog.

Both things that I quoted are for developers:

> Siri can now intelligently pair users’ daily routines with your apps to suggest convenient shortcuts right when they’re needed.

The Android.com copy you quote, by contrast, is directed to users ("connect your headphones").

Re: Introducing Android 9 Pie

#194

Post by viraptor »

cptaj wrote: post #190
izacus wrote: post #116

Earlier quoted context omitted.

Most of that data is still available, just gated behind permissions that require explicit consent from user now.

Does the permission model even work at this point? The vast majority of users just accept whatever the app asks for without a second thought. The rest is bullied by platform monopolies. There is very little real choice for users.

There may be few real alternatives. But this is a choice: You're getting the information, you're making a choice to use all features, use limited features, or just drop the app.

Re: Introducing Android 9 Pie

#195

Post by machiavelli1024 »

cmurf wrote: post #152

I wonder if Google's own apps are exempt from adaptive battery? I continue to have problems with Google's apps soaking my phone's battery. Reset the phone, and I get 6 days of standby (this is LineageOS). Install Google apps, and it's now 4 hours. Wakelock detector says the apps Inbox, Google, and Google Contacts are the top offenders with dozens of wakes keeping the phone awake between 40% and 99% of the time. Super…

That ML pipeline ain’t gonna feed itself, y’know?

Re: Introducing Android 9 Pie

#196

Post by AndyKelley »

"Android 9 harnesses the power of machine learning to make your phone ...simpler"

What a ridiculous concept. Have you ever tried to install TensorFlow? It's a giant, flaming shit-pile covered in a layered shit cake. A word such as "simple" in this context is obscene. This is all bloatware. Android is garbage and it's only getting worse.

What phone can I get that isn't Android or iOS?

Re: Introducing Android 9 Pie

#197

Post by jeroenhd »

scottlamb wrote: post #81
yathern wrote: post #58

Earlier quoted context omitted.

Oreo was in tandem with Treble. Updates in Oreo and in the future should show an increase. Not upgrades to Oreo.

Agreed. Put another way: Treble should make the Oreo distribution percentage go down more quickly than other versions did once they're not the latest. Since Pie was released today, this is the starting line. It'll be interesting to see how it goes. Where could one find graphs of the Android major versions' distribution percentage over time? https://developer.android.com/about/dashboards/ just shows today's numbers. I…

Wikipedia has a nice graph: https://en.wikipedia.org/wiki/Android_version_history#/media...

Needs an update though; this one only goes up to February this year.

Re: Introducing Android 9 Pie

#198

Post by cpeterso »

what_ever wrote: post #146
bitsoda wrote: post #140

Feels kind of lazy going with "Pie" after having used "Key Lime Pie" in the past. Though technically not a dessert, I was rooting for "Pancake".

It was changed from KLP to Kitkat though. So Pie was never used. Disc: Googler but nowhere close to Android.

I was rooting for "Pumpkin Pie", a nice alliterative two-word name. And not trademarked! :)

Re: Introducing Android 9 Pie

#200

Post by izacus »

Latteland wrote: post #192
maxxxxx wrote: post #127

Earlier quoted context omitted.

I hope that the permissions are better to understand and control than the current ones. Right now they seem to be designed to give the appearance of giving users control but the implementation is pretty bad and user unfriendly.

And the other problem is you install an app all the time and the permissions aren't clearly laid out. I want: 1. tell me I install an app that wants "some list of permissions". 2. let me disable this permission for all apps installed now and in the future.

Anything targeting API level 23 has all permissions denied by default (and targeting higher level is mandatory for all new apps right now).
Post reply on HN