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

Android Oreo

android.com

Post reply on HN
Print view View original

491–500 of 658 posts

Re: Android Oreo

#491

Post by romanovcode »

izacus wrote: post #99
amrrs wrote: post #89

Has Google ever released a report on how much time it takes an average flagship device to get the latest android version? Even if you've paid $$$$ in getting Samsung Galaxy S8 just recently, you're not going to get Android O tomorrow morning. But that's definitely the case with iOS. That makes a huge difference in the world where Software updates play a huge role in performance and functionality than hardware update…

Just like you have to buy an Apple phone to get Apple updates immediately, you need to buy a Google phone to get Google updates immediately. Pixel and Nexus rollout is starting nowish (and beta participants are already getting the OTAs). This is really not a secret at this time anymore and should be taken into account when you succumb to Samsung marketing. Everybody else will be probably 4-6 months late.

> Everybody else will be probably 4-6 months late.

I am on OnePlus2 and still using version 6 because maintainers do not give a crap about 2 year old phone and it will never get updated at this point.

Flagship my ass.

Re: Android Oreo

#492

Post by thanksgiving »

microtonal wrote: post #446
mjevans wrote: post #148

Earlier quoted context omitted.

Reflect for a moment; what was the 'new' price of the Nexus 4 vs the 'new' price of the iPhone at the time? A Nexus 4 was a 2012 phone with 2GB ram, and 8GB storage (entry model) https://en.wikipedia.org/wiki/Nexus_4 An iPhone 5 is the comparable year device. https://en.wikipedia.org/wiki/IPhone_5 It had entry specs of only 1GB of RAM, but 16GB of storage. The apps would also be native binaries instead of 'java' apps…

IMO what killed support on the older Nexus phones was /mostly/ the insufficient entry level storage. This is provably false. The Nexus 6 plenty of storage space (32GB or 64GB) and does not get Oreo. Google's Nexus policy is to provide security updates for 3 years (or 18 months after the device stops selling, whichever is longer): https://www.theregister.co.uk/2017/05/01/google_eol_for_nexu... Also, the average Androi…

I thought the reason is Qualcomm not giving what it takes to support a newer firmware on their soc. I have a Nexus 5 on lineage and I'm on Linux kernel 3.4.0.

Re: Android Oreo

#493

Post by amiga-workbench »

0x00000000 wrote: post #69

Android has really been annoying me lately. Maybe I didn't care before but now that I can't root my phone I am forced to deal with it. Still can't disable or customize to stupid "share" menu that puts you one click away from accidentally sending something to a stranger you contacted once on sms or facebook messenger or email. Still can't revoke certain permissions from apps (like vibration). There is zero reason why…

Is anybody else getting seriously bored of the share menu being totally different in each app?

Re: Android Oreo

#494

Post by Natanael_L »

nicpottier wrote: post #360
dcomp wrote: post #122

Earlier quoted context omitted.

> VTS certified If it passed VTS it should be able to run AOSP. The new CTS will be an AOSP System image running their VTS passing "drivers". Even if your vendor doesn't push any updates. At least you should be able to run a number of newer versions of AOSP as long as Android doesn't deprecate those VTS drivers.

You've said this in a few different places, do you have a source for that? You are saying you could load AOSP on an S9 regardless of what Samsung does? If so, this is indeed huge, but I have some serious doubts about it, perhaps because I have felt so very burned by Android so many times in this respect on anything but Nexus devices.

Maybe - the bootloader must allow you to run that AOSP ROM, which only is possible if the bootloader isn't locked. Lots of OEM:s lock their bootloaders. But otherwise, yes, there's nothing else stopping you.

Re: Android Oreo

#495

Post by veeti »

flukus wrote: post #330
rdsubhas wrote: post #141

Not saying that everything else is bad, but one thing that strikes me is how much they have run out of interesting things now that they had to use fillers[1] like: Tooltips Support for tooltips (small popup windows with descriptive text) for views and menu items. Normally, this would be relegated to a git changelog in the support library. But this is on the global marketing landing page. I like to imagine a fictional…

How do tooltips even work on a touch based OS?

Chrome OS has first class support for Android apps nowadays. You can use a keyboard and mouse through USB OTG or Bluetooth on an Android as well.

Re: Android Oreo

#496

Post by madeofpalk »

kuschku wrote: post #370
madeofpalk wrote: post #220

Earlier quoted context omitted.

I remember many years ago when a few carrier and chipset execs stood up on Google I/O stage and announced a new program to ensure Android devices get updated quicker. Nothing came out of that. The proof here will be when they ship. Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction.

> Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction. A move towards replacing an open OS with an entirely proprietary solution full of tracking by a single vendor is "a step in the right direction"? There's thousands of solutions for how you can update core OS components, none of them require what Google's doing to open source.

Look, the reality of the market is that most people are a lot more concerned about getting timely (security) updates than an 'open source' mobile OS.

Re: Android Oreo

#497

Post by eloisant »

sitepodmatt wrote: post #386
dcomp wrote: post #108

The most interesting part is the way they are planning on tackling fragmentation in O onwards with Project Treble [0] If your device ships with O it should be running an immutable semantically versioned HAL. In essence you should be able to be able to flash AOSP on every new device. No matter what the vendor does. Edit: I can see it now, in the technical specs of each device you will see a list of HAL Versions. The n…

Android have been promising to finally tackle fragmentation in every release since KitKat. It seems people have a very short memory.

I think they did a great job at reducing fragmentation by pulling out most of the OS into upgradable components.

All applications are upgradable, even Play Services are upgradable, and developers get the support library to get all the new things to all devices.

So I believe they did a great job at reducing fragmentation in the sense that it no longer really matters what version you have, you still get all the newest stuff. Just look at every iOS version announcement: 3/4 of the new features are in the apps: iMessages, maps, home screen...

Re: Android Oreo

#498

Post by josteink »

snoyberg wrote: post #474
josteink wrote: post #428

Earlier quoted context omitted.

But if a carrier has the nerve to actually block updates to my phone and I find out, I'll switch my phone to another carrier the next day. What's in it for them?

Most people don't think about such things when buying (renting) a new phone. If you do consider it, you're an exception to the rule.

What do you mean rent?

I buy my phone. It's mine. I can put it on any network I like.

Re: Android Oreo

#499

Post by eloisant »

pjmlp wrote: post #426
robert_foss wrote: post #397

Earlier quoted context omitted.

The code speaks for itself. Any Android implementation is now split in two halfs, one which is easily replaced and one which is not. If vendors choose to not use this feature it is on them.

Actually since Google is still allowing customizations, it will hardly change anything.

They can impose whatever they want to OEMs who want to ship the Play Services and Google apps. That's pretty much all of them.

If they say "install it this way or no Play Store for you", every manufacturer will follow.

Re: Android Oreo

#500

Post by rdsubhas »

rdsubhas wrote: post #117

Not saying that everything else is bad, but one thing that strikes me is how much they have run out of interesting things now that they had to use fillers[1] like: Tooltips Support for tooltips (small popup windows with descriptive text) for views and menu items. Normally, this would be relegated to a git changelog in the support library. But this is on the global marketing landing page. I like to imagine a fictional…

(for some reason my comment got double posted, pls ignore this dupe, other comment is somewhere on top)
Post reply on HN