4 ms·
Here, I think it's the multiple layers of people with their hands in the source code. Just because Google and OEM X have some agreement doesn't mean that Carri
by andrewstuart2 11y ago
Here, I think it's the multiple layers of people with their hands in the source code.
Just because Google and OEM X have some agreement doesn't mean that Carrier Y trusts OEM X not to muck up their network (or their bloatware). So carriers end up adding their own drawn-out testing process for their own reasons, probably including time to update their carrier bloatware.
I should point out as evidence that I use a major carrier and run a Nexus phone, and I have no issues whatsoever getting Google updates, security or otherwise. I expect to have Android Marshmallow on my handset by the end of the week.
- madeofpalk 11y agoBut why can't Google enforce trust between AT&T and Samsung to ensure updates are received in minimal time? As a platform vendor, IMO that's their job. At a bare minimum , to ensure their users get the security updates they need.
- wldcordeiro 11y agoIf you recall the history of Android, Google had to make concessions with regards to control of the operating system to the carriers and other partners. So now years down the line we're dealing with the repercussions of their compromise.