Google gets smooth early Android releases. OEMs are struggling The rollout of Android 7.0 on some Samsung devices has smacked them right in the battery. Meanwhile in the background, further competition issues around the Google mobile OS are brewing. Testing by GSMArena reveals a dramatic loss of battery life on the Samsung S7 Edge (Exynos 8890 version) using the platform update. Battery …
> So It's not Android, it's Samsung that is the issue here. Nice try thou.
Not just Samsung, it's sometimes others, as the article notes. I use Android and not iOS, and before upgrading the OS i wait a couple of weeks and lurk around forums to see if other users of my specific handset have experienced any issues.
Of course there are more handsets out there that use Snapdragon SoCs - including most Nexus phones - than use Samsung's Exonyss or whatever it's called.
You mean, unlike the customers who are stranded on old versions?
My S6 Edge says 'Android 6.0.1', 'Android security patch level 1 October 2016'.
What happened to 7.0? LG managed to ship that back in August.
Or even, just more security updates since Google keep providing Samsung (and everyone) with patches.
Funnily enough, my (HTC) Pixel says '7.1.1', and is currently updating to the February 2017 patches.
The whole point is that Google are showing that it's entirely possible to bring updates out, consistently, and frequently. That's probably because they don't distract themselves by releasing 1000 variants yearly (SM-G920 / SM-G925 / SM-G928, in F and I variants - and that's just the S6 brand), or some of the recent junk such as the Galaxy J1 mini prime, J3 Emerge, C7 Pro, etc....
Precisely, if the manufacturers stuck to a handful of well designed phones, a entry, a mid and a high end, and stick to using a global capable chipset, rather than cutting corners and producing phones for each market, then they wouldn't have the vast number of phones to support, and could focus on supporting them properly.
If Google can make 1 Pixel that works across the Globe, then so can Samsung, HTC, LG and Sony.
"The whole point is that Google are showing that it's entirely possible to bring updates out, consistently, and frequently."
I don't quite see why people miss the big reason why non-Google phones have a longer delivery cycle. Have you ever used a Google phone versus another manufacturer like Samsung? If you have, you'd notice the obvious difference. Samsung has put a lot of work into making their interface consistent across all of their devices via the TouchWiz interface. If you compare the S4 through the S7, you'll notice that all of them operate very similarly (interface-wise). Google simply takes what they've created as stock and slaps it on the phone. When a new release comes out, they can easily deploy it because everything in the release is basically exactly what goes on the phone. Samsung has to update, tweak, and compatibility test all of the customizations they have made to integrate them into the new release. If Samsung ran stock, I'm sure major updates would be released a lot faster. If you look at the security point releases for the S7, Samsung actually keeps pace quite well.
You also have the issue with carrier tie-in. It's why the Samsung on AT&T can receive the update on a different timeline than the exact same Samsung on Verizon. Each carrier will want their own control over how things are built to make sure their own cruft gets included.
I agree.
Samsung tried stock for a while with the Google Play Edition, but even when they weren't adding TouchWiz they still took forever to release updates. Example: http://www.gsmarena.com/samsung_galaxy_s4_google_play_edition_finally_receives_android_51-news-13959.php
S7 only got recently updated because there isn't a newer flagship; I had the Note7 (RIP), and I suspect the second the S8 ships the S7 will start to get the same treatment the S6 gets currently.
Samsung are crazy; not only do they have TouchWiz, they also have Good Lock, which is actually more useful IMO than TouchWiz but... wow... they must really have nothing better to do than maintain (or not) all these different versions of stuff, an entire Store. Oh, and the Game Launcher stuff, GearVR, etc. etc. etc.
"I can't see a conflict of interest there at all."
But if Google is taking technical decisions and making updates to Android, based on it's knowledge and implementation of Pixel hardware, and not communicating to the OEMs about this then the OEMs are at a trading disadvantage; remember that the big Android OEMs are paying Google money for it, so they can expect some consideration in this.
From what I've read online, it is difficult to lay your hands on a Pixel phone. Indeed, there have been some reports in the last few days that production is to end. I dont know if this limited supply is a deliberate decision by Google.
"Indeed, there have been some reports in the last few days that production is to end."
In the last week or two, rumours have begun to surface of a "Pixel 2" later this year.
In other news, my Pixel C tablet updated itself to Android 7.1.2 yesterday.
No news of updates on my Nexus 6P
And yet, I click on the assistant button on the Pixel and have this conversation:
me> what are you
pixel< I'm your Google Assistant
me> what can you do
pixel< Here are some things you can ask for:
[stuff]
For non-Pixel phones you can *also* get it. All you have to do is install a copy of Google Allo from the Play store.
I launch that on my S6 Edge, click on 'Google Assistant', and...
me> what is the point
s6 edge< i think the point is to leave the world better than you found it
So, you *can* get it on any modern phone that runs Android (and has the Play store) though it's not directly linked to a button like, for example the trash that S-Voice.
First they introduce Doze which didn't improve my battery life but did make receiving push notifications for my email client a bit problematic. The next major version of Android is supposed to include an even more aggressive version of Doze and co-incidentally worsens battery life on my device.
I thought Google employed clever programmers? Or maybe there's something in this unfair competition malarkey after all :-/
Either way since buying my S7 Edge I've increasingly felt that Android was no longer the home for me. I used to have a fairly generic, pocket sized computer I could carry around with me that I felt would do whatever I wanted. Now various developers of applications I use are starting to complain about the API not allowing them to do certain things they need to do. For IMAP push notifications I believe developers have been advised to switch to Google's proprietary notification system which incurs a financial cost on them and a privacy cost on the users.
Unfortunately, you've not got many choices.
iOS. Where software guys have to program specifically for the background API: https://developer.apple.com/library/content/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html
Fail to do it and your app gets paused (and killed, to free RAM)
Android: As per the link you posted, follow the process properly or your app gets paused (eventually) and killed (to free RAM)
Microsoft: Err...
BlackBerry: Now Android
Simbian: ?
Any other contenders?
If they contributed more actively to things that use AOSP then not only would they be able to release security fixes (the most important part) and OS updates much more frequently, but they would have less work doing so.
LineageOS (the successor to CyanogenMod) already has an impressive list of devices and, minor problems aside (do make sure you backup before trying it, is working well. Smoother than CM13.1 on my Samsung S5 and battery life seems better – could be down to Doze. Notifications on CM 14.1 were definitely more of a problem.
IMO Google will only be in trouble if they stop providing timely updates to AOSP. But this would also give OEMs more power and also drive people away from the services they're hoping to make money on.
Google get some tricks from the MS bag this time, when MS products too advantage far earlier of new OS features, often some "undocumented" ones... and they could even upgrade some pieces of the OS itself.
After all did someone believe they wold have let MS copy their slurping doing nothing?? <G>
Spin it any which way you like, but the 'competitive' Android market collectively decided to connect the Android maternity hospital directly to an Orphanage, screwing the consumer.
Google's line exists to stop the competitive bar falling into the mud again. There aren't really any other ways to do it beside competing.
The remaining question is should Google be allowed to bundle Google Assistant. That's really the only discriminating factor. Everything else is noise.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
