Slashdot Mirror
Google Steps Up Pressure on Partners Tardy in Updating Android (bloomberg.com)
Google is actively tracking the time its partner OEMs take to release a new version of Android onto their devices. According to a Bloomberg report, the company is drawing up rankings that could shame some phone makers into better behavior. From the report: Google shared this list with Android partners earlier this year. It has discussed making it public to highlight proactive manufacturers and shame tardy vendors through omission from the list, two of the people said. [...] Google is making progress persuading phone makers and carriers to install security updates quicker "for the good of users," Android chief Hiroshi Lockheimer said. The same expedited process may then be used to send operating system updates to phones, he explained. The most challenging discussions are with carriers, which can be slow to approve updates because they test them thoroughly to avoid network disruption. The report adds that several OEMs are also stepping up their game to better comply with Google's new wishes. Motorola, for instance, is working on offering quarterly updates to its three years old devices.
For users with non-Nexus devices, it's really frustrating to wait for months, and in some cases, years, before their devices from Samsung, Xiaomi, Huawei, HTC and other manufacturers get upgraded to a newer version of Android. Another challenge for Google is to push its partners to actively release updates to affordable and mid-range smartphones. Many OEMs mostly worry about serving those users who have the flagship and high-end models.
For users with non-Nexus devices, it's really frustrating to wait for months, and in some cases, years, before their devices from Samsung, Xiaomi, Huawei, HTC and other manufacturers get upgraded to a newer version of Android. Another challenge for Google is to push its partners to actively release updates to affordable and mid-range smartphones. Many OEMs mostly worry about serving those users who have the flagship and high-end models.
The carriers need to be careful - the FTC/FCC will probably order them to unlock bootloaders for any devices they refuse to update. They really won't want to do that. The FCC is regulatory-captured by the telcos, but the FTC isn't as much.
(of course *I* want that to be an option - I paid for the damn phone)
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Google abandoned their own device.
The idea that such a list will somehow "shame tardy vendors" is laughable.
VP #1: Chairman! Terrible news! We're not on Google's list!
Chairman: Oh, no! I am ashamed! I must atone for this stain on my character by committing Seppuku!
VP #2: No, Chairman! That will leave your family dishonored!
Chairman: There is no other recourse - I must atone!
#DeleteChrome
To be honest, I've never had a problem with the device manufacturers, it's always been my network (carrier) that's been a pain up the ass with spending time adding their extra branding, crap apps, and the like. Even worse, mine has a blanket policy of "We'll tell you when there's new firmware, we aren;t going to give you any ETA's, status reports or anything. You have to wait until it appears (or not)
"How fine you look when dressed in rage."
- Stop certifying new devices unless they are on the most recent two releases as of the day the hardware first ships to customers. So, that would many any hardware that releases today would have to be running Lolipop or Marshmellow to ship with the Play Store.
- Require unlocked bootloaders and full AOSP releases with all necessary driver sources for the hardware to get certification and Play Store for manufactures with poor update performance, so that third parties get a crack at updating devices when manufactures and carriers lag behind.
- Restructure royalty payments so that app purchases on the play store pay carriers and handset manufactuers significantly more if they are on a current release, and significantly less the older the release is.
- Give strong financial incentives to manufactures to partner with google to offer the option of direct-from-google "pure" firmware that customers can elect to install AFTER purchasing the device. with all the manufacturer and carrier customization offered to said users as apps in a special section of the play store.
No, they can't tell them that.
First, it's already a done deal. Samsung Knox, TouchWiz, and on and on -- and different, incompatible versions from each IHV -- are considered by these companies' executives to be their "crown jewels". They're "distinguishing" factors that set them apart from other handset makers. You would actually break a fair number of Android apps by going back and retroactively removing these incompatible subsystems, since a number of apps actually use them.
Second, the partners have the source code. Almost all of it save for perhaps the Google-branded applications suite. The code is also liberally licensed. If Google tried to put their foot down, the manufacturers would just ignore them and fork Android. See: CyanogenMod, Amazon FireOS.
Third, Google has no direct relationship with carriers. Carriers interface with the IHVs, not with Google (except, perhaps, for Nexus devices). As long as the IHVs are okay with slow security updates and love to make money by dumping their own crapware on the phones (and letting the carriers do the same), they have no motivation to change their ways.
Naming and shaming won't do much to change this momentum. It's a very poorly engineered, overly bureaucratic process created by tight competition and a tendency (by both IHVs and Google) to want to continually tighten up the ecosystem and make things more proprietary and less open.
Apple has really cornered the market on rapid OTAs and addressing security issues quickly. Google has a chance of matching them with first-party phones and Nexus devices, but that's it. Outside Nexus, Android is the wild wild west, kinda like the old Windows 3.1 / 95 days, but even worse in some respects.
There is no happy medium that's both open and secure because the market doesn't demand it. People keep buying Android's mostly-closed, buggy, insecure crap and Apple's completely-closed, less buggy, probably-more-secure-but-we-don't-really-know walled garden crap.
When has a Android update ever caused an issue with a carriers network?
Hell my Samsung Rugby is still sitting at 4.4.2. Samsung has 0 interest in updating anything. It's like tech companies forgot that still have to maintain previous models and not just shake/jingle the shiny new keys at customers
Disclaimer: I'm not a coder, I'm a user and a fixer at best.
I switched from Apple to Android in 2010 for many reasons. In that time Android quickly improved to a point and then seemed, in my eyes to stagnate. Apple very very slowly improved and continued to improve and hasn't stopped...
I am pretty frustrated that some of the older hardware I support, such as an iPad 3, iPhone 5s and 4s (!) are still being routinely updated by Apple, but Android based phones are being left in the dust.
What can be done to fundamentally fix this? It didn't bother me 2 years ago when I was in an overpaid job, valued my money differently and I simply /knew/ I would be getting a new phone within 24 months at most, likely as short as 12.
as we all suspected all along,
Who is this 'we'? Do you have a hamster in your pocket or is that your iPhone buzzing?
My phone has an ARM processor, and until I can install iOS on it, that's an irrelevant spam topic to bring into this discussion.
So when is Apple going to start selling an iOS I can install? Or is their code so fragile it only runs on a precious few devices?