3 ms·
It's incredible to me how long it took Google to realize this was their fault. A lot of people here have bought the "blame the OEM" nonsense for a really long t
by ocdtrekkie 10y ago
It's incredible to me how long it took Google to realize this was their fault. A lot of people here have bought the "blame the OEM" nonsense for a really long time, and you can see the comments here reflect that.
But in reality, there's a huge expense to all the work of updating devices to support Google's rapid change cycle for dozens or hundreds of different models, and the problem stems first and foremost from that lack of abstraction layer.
This is likely a first step to finally catching up to Windows Mobile: Making the core OS upgrade come straight from the actual OS developer, so that the company that writes the code is actually the one that updates the code.
- therealmarv 10y agoWell I can blame OEM because I never asked for special features and skins on top of Android. I want stock Android and stock should be easier to update. Speaking about testing of updates: I'm sure this abstraction layer will not reduce the testing time and it will only slightly reduce the release time of new version.
- ocdtrekkie 10y agoThere's no such thing as "stock Android" from an update distribution view. Each Android release, currently, has to be custom-fitted to each given hardware model. That is the problem being solved here, and it's not the OEM's fault, it's the architectural design of Android itself, which is changing.
- nileshtrivedi 10y agoIt's not just Android design's fault though. ARM does not have the equivalent of Bios for hardware discovery and initialization. So you can't have a generic OS image to be installed on any device.
- MBCook 10y ago> Well I can blame OEM because I never asked for special features and skins on top of Android. Did you buy an Android phone? Then it wasn't enough pressure. There simply aren't enough people in the market who care about this to put much pressure on phone companies. Basically EVERYONE has a phone, and since almost none of them know about this issue they'll always make the purchases of people who do care a rounding error on the books. Just like the 'I need a removable battery' or 'I want a hardware keyboard' people. They're real groups, but they have little sway in the market compared to the people who are indifferent (or at least willing to accept the trade-off grudgingly) so they don't get much traction.
- maxsilver 10y ago> I want stock Android and stock should be easier to update. That's not actually true, unfortunately. The BSPs are where the majority of the work is, and zero percent of that work is different between "Stock Android" and "Weird OEM Customized" Android. If you look at what it takes to get "Product X" from an existing Android version, to a new Android version, very little of that time is updating the crapware everyone hates, and the vast majority of that time is updating the BSP + drivers needed to get any Android working properly at all. For instance, if you build a product, you might buy a board from a random OEM, and that board might be built around a Qualcomm SOC on it. If Qualcomm doesn't support "the next android" for that particular chipset, your basically stuck unless you re-invent all of the Qualcomm-specific drivers and tools yourself. Since Qualcomm isn't supporting it, the OEM you bought your board from isn't either, and the product itself gets stuck on old Android. ocdtrekkie is getting downvoted for this, but he's mostly right. Google could easily solved this problem years ago by letting Android devices reuse existing BSPs, and it looks like they are finally doing exactly that.
- bitmapbrother 10y agoIt's also incredible that you still don't comprehend that Google cannot update an OS created by another OEM. When you allow an OEM to create their own OS only they can update it. Your Windows comparison is also flawed because OEM's do not build the OS - they're given the binaries from Microsoft and cannot change them.
- ocdtrekkie 10y agoThis is, as with every time you've posted it, a complete fiction. Android doesn't become "not Google's OS" because of the shoddy distribution method in use, and Google still does dictate to OEMs what does and doesn't qualify for release, as Google still has effectively complete control of the ecosystem via the MADA/Play Store license.
- bitmapbrother 10y agoYour reply doesn't make sense and you have not answered how it's technically possible for Google to update an OS created by another OEM. Google does not have the source code for the OEM's changes so to expect Google to update their OS would be impossible. It's like asking Debian to update Ubuntu.
- wmf 10y agoThe solution is for there to be no OEM changes, just like Windows.
- bitmapbrother 10y agoI agree.
- kllrnohj 10y agoSo the solution is for Android to be closed source? I'm not sure I agree with that.
- 10y ago
- asveikau 10y ago> This is likely a first step to finally catching up to Windows Mobile: Do you remember the same Windows Mobile that I do? In version 5 or 6 they had a "Windows Update" control panel which I basically never saw work, and that wasn't for lack of builds coming out of Redmond. In that time I had to illegitimately re-flash to get any updates. Or perhaps you mean Windows Phone where zero devices got upgraded from 6.x to 7, zero devices got upgraded to 8, and a bunch of phones never got 10. And late in that game there was effectively one hardware vendor plus some rounding error.
- wvenable 10y agoWindows Mobile was technically capable of all this; custom versions of Windows mobile back-ported to older phones were far more prevalent than custom versions of Android are now despite Android being open source and based on Linux. This should be a cautionary tale for those thinking that this technical initiative will have huge benefits for consumers -- it didn't work out well for Windows Mobile users because the manufacturers and carriers are still the gatekeepers. Just because they can more easily produce new versions doesn't mean they will.