Earlier 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.
Android Oreo
31–40 of 658 posts
Re: Android Oreo
#32Re: Android Oreo
#33Re: Android Oreo
#34> Native C/C++ API for high-performance audio. API function for high-performance audio including Native C/C++ audio API. I wonder if this will be good enough to close the gap with the rich music creation ecosystem on iOS.
Re: Android Oreo
#35A 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.
They did the same thing wit KitKat.
Re: Android Oreo
#36Re: Android Oreo
#37Project 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 "…
For instance, the Galaxy S8 is the hottest new thing on the market right now, and it launched with Nougat. It will probably be six months to a year before Samsung pushes an Oreo update to it, if at all.
Re: Android Oreo
#38Why 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
#39Earlier quoted context omitted.
>Gee, I've never heard of "Mopria" but this sounds interesting. 97% of printers sold now - the initiative happened in 2014, and I assume that it took manufacturers a few years to ramp. So probably don't expect it to work with your 5 year old all-in-one.
If it supports prior services like Google cloud print, perhaps even uncertified printers could work
Re: Android Oreo
#40A 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.