The HTC US site has just posted an interesting update which explains a little of the process of what happens with the update process from the viewpoint of a major manufacturer.
The infographic is fairly large – click on the image below to have it expand fully – but lists the step by step process from a US standpoint – but the concepts are still valid – from the release of the framework through the Partner Development Kit(PDK) through to the implementation of the HTC Sense framework and certification process.
It’s a fairly long read, and pretty much explains why the update process can be a fairly lengthy process, although Motorola has been blowing this up recently with timely and extremely fast updates for their Moto X in the US, where the Verizon version actually beat the Nexus 4 to receiving Android 4.4.
The Google play line is interesting, primarily because it bypasses so many steps that seem redundant to those of us that enjoy a ‘vanilla’ experience, it does show how the carrier and OEM modifications can slow down the process.
Steps 6, 7, and 8 are the steps which need to be diked out.
OS updates being blocked if HTC Sense and/or carrier bloatage can’t be squeezed onto a device. Google needs to kill both of those malpractices. Yesterday if at all possible.
I agree but that will cause bad use experience as users who get used to the sense and carrier apps might feel bit confused ( what Android already makes new users)
Not every user is a geek
Good point, Vijay. I’d not considered that.
Maybe then, what needs to be done is actively prevent steps 6, 7, and 8, from being able to happen during the design and planning and prototyping of new Android devices, so users don’t have to suffer such bloatware from the outset. Hopefully that would speed up updates and make them available to older devices.
The issue is more that Google doesn’t want to do this. They could do so quite easily if they wanted to.