Linked by Thom Holwerda on Fri 11th May 2018 22:47 UTC
Android

Updates are easily the biggest problem facing the Android ecosystem, and Google is working hard to fix that. Project Treble has proven that it's capable of making updates easier, and now Google is stepping up requirements for OEMs when it comes to security patches.

Every little step in this department is a welcome one. It's not yet clear what, exactly, the requirements entail, but hopefully, it's a strict and hard requirement to publish every monthly security update.

Thread beginning with comment 656545
To read all comments associated with this story, please click here.
Finally!
by moondevil on Fri 11th May 2018 22:56 UTC
moondevil
Member since:
2005-07-08

Apparently the largely ignored Oreo's adoption is finally making Google move.

Currently 5.7% adoption after one year, which by this rate would mean Android P would probably never be adopted if they continue to ignore the elephant in the room.

https://developer.android.com/about/dashboards/

Reply Score: 2

RE: Finally!
by gld59 on Sat 12th May 2018 00:09 in reply to "Finally!"
gld59 Member since:
2012-11-09

I wonder how much of that is a result of vendors putting all their resources into putting Oreo on new devices, and having none left to roll out updates to older devices? *If* that is the case, then hopefully once vendors are more familiar with creating the vendor partitions/blobs required for (new) Oreo devices, they can swing resources back to trickling out updates for older devices.

Reply Parent Score: 1

RE[2]: Finally!
by moondevil on Sat 12th May 2018 06:45 in reply to "RE: Finally!"
moondevil Member since:
2005-07-08

If a new device comes out with Android Nougat and gets updated to Oreo, it is not required to go through the Oreo Treble's certification process.

Most new devices on 2018 are still being released with Nougat or Marshmallow on them.

Even if an handset is released with Oreo, thus Treble certified, it is up to the OEM to push the updates, which isn't really happening outside Google, 8.1 is only on 0.8% from those 5.7%.

Reply Parent Score: 2

RE[2]: Finally!
by Brendan on Sat 12th May 2018 09:55 in reply to "RE: Finally!"
Brendan Member since:
2005-11-16

Hi,

I wonder how much of that is a result of vendors putting all their resources into putting Oreo on new devices, and having none left to roll out updates to older devices? *If* that is the case, then hopefully once vendors are more familiar with creating the vendor partitions/blobs required for (new) Oreo devices, they can swing resources back to trickling out updates for older devices.


The world doesn't work like that.

Imagine you are a mobile phone manufacturer; and you know that by hiring more staff (to roll out updates to older devices) it will cost you $X for the staff and cost you $Y in lost sales due to people not replacing old phones with new phones; but you will also get an additional $Z in publicity (to help sell new phones).

If $X + $Y is less than $Z, then you hire more staff because you'll end up making more profit; and if $X + $Y is greater than $Z you just ignore all the people that want updates because you don't want to lose money.

Note: the words "hire more staff" can be replaced by "not make existing staff redundant" if/where necessary. Either way it's mostly the same $X.

- Brendan

Reply Parent Score: 5

RE[2]: Finally!
by unclefester on Sun 13th May 2018 02:24 in reply to "RE: Finally!"
unclefester Member since:
2007-01-13

The low cost models are MTK reference platforms with vanilla Android. This low margin business model makes software updates and ongoing support totally uneconomic.

Reply Parent Score: 3