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

81–90 of 367 posts

Re: Introducing Android 9 Pie

#81

Post by scottlamb »

yathern wrote: post #58
pjmlp wrote: post #55

Android Oreo, one year later in spite of Treble, 12.1%

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'd like to see a "distribution vs days since following version released" with a line for each old version.

Re: Introducing Android 9 Pie

#82

Post by xd1936 »

bitmapbrother wrote: post #29
sigfubar wrote: post #16

Earlier quoted context omitted.

By the time Android P actually makes it to non-Pixel devices, the beta will have long since ended, so this doesn't really matter.

Android P is available for the Essential phone[0] the same day as the Pixel. Technically, every device in that was enrolled in the Android P beta could have also had it day one. [0] https://www.essential.com/

Yup. I've got Android P on my Essential PH-1 right now. I'm bummed I don't have the wellbeing features that were promised.

Re: Introducing Android 9 Pie

#83

Post by izacus »

Sir_Cmpwn wrote: post #75

Surprised not to see mention of the cutout stuff yet. It seems pretty dumb to me that Google is jumping on board with this ridiculous feature. Maybe this'll be one of those Dropbox-style HN comments which in hindsight looks misled, but I honestly can't find any redeeming factors to the cutout idea.

Except developers being able to properly support their apps around it? OEMs have decided to add notches, want it or not. Not having a API to work with them would be a huge pain.

Re: Introducing Android 9 Pie

#84

Post by josephh »

mrep wrote: post #68
wvenable wrote: post #23

Earlier quoted context omitted.

The general consensus amount Samsung users from my experience is that that they do these features better than Google. Samsung's multi-window support was better than eventually came to Android. Samsung's handling of app badges was WAY better (message counts!) and that went away with Oreo's terrible implementation (a dot indicating un-dismissed notifications). My impression after upgrading to Oreo and getting more Goog…

Really? I had a galaxy s4 back in the day and I hated the skin/bloatware on it so much I went back to iphone. I recently got the pixel 2 to see if googles own phone would be a better experience and I have liked it as much as my old iphone.

I believe most of the preconception against Samsung-branded Android OS is based on their experience with older (pre S6) devices. I wholeheartedly agree they were bad at it back then (esp. the bloatware that poorly replicated the functionality of various stock apps), but they've since gotten significantly better with their UX.

Re: Introducing Android 9 Pie

#85

Post by cptskippy »

haldean wrote: post #17
unethical_ban wrote: post #6

* It looks like they've taken away the "apps" homerow button and swapped it for "swipe up from anywhere". So that is one less gesture available to apps, unless you install an alternative desktop. * Wi-Fi RTT sounds pretty neat, I had not heard of that before. * Shutting mic, camera and sensor data off for idle/background apps is neat, though I'm shocked that wasn't an option before.

It also looks like the back button is gone... how is that supposed to work?

It's now an application navigation function and not an OS navigation function. So in screenshots demonstrating core OS functions it's absent but in screenshots demonstrating Apps it's present.

Re: Introducing Android 9 Pie

#87

Post by Legogris »

I can't be the only one getting a chill down my spine when I read this. Google, a company "committed to reach and engage the right users safely and cost-effectively around the world", doing deep analysis of my every input and my context in order to "drive engagement" and "surfacing the best parts of the apps [I] use all the time"?

I hope this stuff is kept out of AOSP. Yes, I know it seems like at least some of the computation happens on-device, but I am not comfortable having it done on a device out of my full control regardless.

Re: Introducing Android 9 Pie

#88

Post by mtgx »

fixermark wrote: post #39
hateful wrote: post #36

> We partnered with DeepMind on a feature called Adaptive Battery that uses machine learning to prioritize system resources for the apps the user cares about most. You know what mind I would like to control what apps get more resources? Me

Not most people though. There was a time when in MacOS, one could manually limit the amount of memory a program was launched into by setting the required and preferred memory footprint. But that kind of low-level stuff isn't something most people care about or want to do. They just want the damn thing to work.

Do you know what I would like? For Android to actually show what apps/services drain battery life.

I noticed recently that WhatsApp, Reddit Sync, and a few other apps were draining battery life like crazy. But none of that drainage was being shown in the battery stats.

Google is purposefully hiding how some apps use battery, and it started years ago when they allowed apps to hide under "Android OS" and "System" categories. In more recent versions they "fixed" this by simply not showing the Android OS and System categories in the battery stats anymore.

Google doesn't want to show how some apps use your battery because they drain the battery with similar methods that Google itself uses to drain your battery (by polling your location all the time, etc).

Re: Introducing Android 9 Pie

#90

Post by DennisAleynikov »

rayiner wrote: post #62
kayone wrote: post #31

Earlier quoted context omitted.

I don't really see any difference besides what appears to be your own personal bias.

Google markets how a feature "drives engagement." Apple talks about how it "help users quickly accomplish tasks."

You're comparing developer marketing materials which should show the reason devs would want this vs human marketing materials?

I get apple is for developers too but they word things in the most utopian way it's almost like they believe they're in a Utopia.

Post reply on HN