I don't like the product placement in the release name.
Android Oreo
41–50 of 658 posts
Re: Android Oreo
#42Project Treble is the most important thing in this release >The biggest change to the foundations of Android to date: a modular architecture that makes it easier and faster for hardware makers to deliver Android updates. With any luck, this will end the huge security/update problem Android has. Right now an update is dependent on the chip manufacturer's drivers, then the OEM adding them to the ROM with their custom "…
Then again, this new architecture likely makes it easier to move the Android userland to a new (non-linux) kernel, so maybe it'll be a moot point.
Re: Android Oreo
#43Why on earth did they go with a restricted trademark, Oreo? Oreo must have payed a good sum of money I suppose? Coming up with the legalese on how and where Google is allowed to use the Oreo trademark seems difficult.
If not, then there is no trademark issue. Google isn't selling a food, it's selling an operating system.
Re: Android Oreo
#44Earlier quoted context omitted.
If it supports prior services like Google cloud print, perhaps even uncertified printers could work
Cloud print has been supported since KitKat, you just need to install the driver (sorry, "print plugin"): https://play.google.com/store/apps/details?id=com.google.and...
Re: Android Oreo
#45Earlier quoted context omitted.
Or even if just gets the chip manufacturers out of the equation, that alone fixes most of the problems. The OEM side is usually pretty easy / trivial in comparison. And there are a number of OEMs who would happily push updates but can't, because they can't get hardware packages from Qualcomm / Amlogic / Freescale / etc. That, more than anything else, holds back new Android releases on lots of hardware.
Supposedly the carriers are real pains as well. I've heard horror stories of months-long approvals processes on Verizon and AT&T ROMs. It's a game I wish they'd get out of entirely. There's no such thing as a useful carrier overlay.
Six months and counting, waiting for Verizon to approve the Nougat update on my HTC One M9. It has literally hit everyone else:
[0]http://www.androidpolice.com/2016/12/09/unlocked-htc-one-m9-...
[1]http://www.androidpolice.com/2017/02/23/android-7-0-nougat-o...
[2]http://www.androidpolice.com/2017/03/21/t-mobile-variant-htc...
[3]http://www.androidpolice.com/2017/04/12/htc-one-m9-sprint-ge...
[4]http://www.androidpolice.com/2017/05/16/atts-htc-one-m9-upda...
Re: Android Oreo
#46I don't like the product placement in the release name.
Re: Android Oreo
#47A non-generic brand name for their O-release? Did they strike a deal with Nabisco/Cadbury? I can't imagine Google doing this without some form of legal go-ahead from the trademark owner.
In case of 4.4 KitKat it was the idea of Nestle's advertising agency, J. Walter Thompson [0]. It was novel at the time, and it as more than just jumping on the letter "K", because it tied the "have a break, have a kitkat" line with the idea that people reach for their smartphones when they have a break. Now I imagine it's just people in suits negotiating the deal for the next release name. [0] https://jwt.co.uk/work/…
All the stories I've heard[1] say the idea came from Google as Hiroshi Lockheimer (now head of Android & Chrome OS) was a big fan of KitKats.
1: https://www.theverge.com/2013/9/3/4691040/android-kitkat-the...
Re: Android Oreo
#48Finally Android will stop Facebook apps from sucking my RAM secretly!
Re: Android Oreo
#49Why on earth did they go with a restricted trademark, Oreo? Oreo must have payed a good sum of money I suppose? Coming up with the legalese on how and where Google is allowed to use the Oreo trademark seems difficult.
Re: Android Oreo
#50"new emoji" is an OS-level feature now. Welcome to 2017.