3 ms·
OEM's update woes are their own doing. The further they get from AOSP the more painful it is to hack updates together.
by discreditable 11y ago
OEM's update woes are their own doing. The further they get from AOSP the more painful it is to hack updates together.
- ocdtrekkie 11y agoThat's kinda false on multiple fronts. First and foremost: From everything I've heard Google doesn't go out of their way to support any hardware besides Nexus devices, so if you use any different chips, you have to do your own work to get it to work. Also, Google often ships Android versions non-compliant with carrier requirements. I remember when the last Nexus 7 rolled out, it's radios were compatible with Verizon, but they couldn't meet Verizon's standards for certification until a later patch level of Android. OEMs often have to bear the burden of making Android actually work on a carrier. And finally, the further they get from proprietary Google Android (it's not AOSP if it has Google Apps), the more likely they solve the 'lack of profit' problem. Google saps up all of the potential revenue streams for a manufacturer with it's various apps and services that OEMs are forced to install. Many of their own apps and customizations offer them additional potential for income.