4 ms·

Damn it Google. Stop releasing more "editions" in an already fragmented OS market. OEMs are refusing to push updates specially to the lower end phones. So stop

Damn it Google. Stop releasing more "editions" in an already fragmented OS market. OEMs are refusing to push updates specially to the lower end phones. So stop giving them reasons to keep releasing new phones.

Fnoord 9y ago
That's what Android One and Project Treble are for. Android Go is meant for low end, slower connectivity devices aka "upcoming markets". I wonder if Android Go does less profiling etc. Android Go was announced half a year ago on Google I/O 2017. Here's a few sources: [1] [2]. Quoting: "Android Go will be launched with Android O, but will be an integral part of every Android version in the future. Every Android device with 1 GB of RAM or less will be able to use Android Go. Several key points of the operating system will be optimized and tweaked to take changed specs into account: * Android Go will have a new data counter, which will allow for better monitoring of data consumption. * Data Saver will be enabled by default. * The Play Store will be included with all available apps, but Android Go customized apps will be highlighted. * Gboard, Google's keyboard app, will have new translation features. * Google apps will be optimized for weaker chipsets and slower networks." Keep in mind 1 GB or less means according to the article on Google Blog: 512 MB - 1 GB. So anything less than 512 MB RAM won't fly. Data Saver [3]: "To optimize for Data Saver mode, apps should: * Remove unnecessary images * Use lower resolution for remaining images * Use lower bitrate video * Trigger existing “lite” experiences * Compress data * Respect metered vs. unmetered network status even when Data Saver is off Conversely, to work well with Data Saver, apps should not: * Autoplay videos * Prefetch content/attachments * Download updates / code * Ask to be whitelisted unless background data is truly part of core functionality * Treat whitelisting as a license to use more bandwidth" I'm not sure whether Data Saver mode uses Google proxies. The article on Google Blog is actually a decent read as well. It explains how on 8 GB flash storage, 50% is available with Android Go, and apps are 50% size. Its unclear to me how Google benefits from Android Go apart from happy customers. I'm giving some hints throughout my post but nothing conclusive. The name is also confusing given their programming language, Go. [1] https://www.androidpit.com/what-is-android-go https://www.androidpit.com/what-is-android-go [2] https://www.androidauthority.com/android-go-773037/ https://www.androidauthority.com/android-go-773037/ [3] https://source.android.com/devices/tech/connect/data-saver https://source.android.com/devices/tech/connect/data-saver
- izacus 9y ago
  Data saver is available since 6.x or 7.x and it doesn't use proxies at the moment.
- AdmiralAsshat 9y ago
  Google made a disastrous decision to make Project Treble an optional framework. The end result is that even though supporting it would allow phones to get faster updates, the vast majority of OEMs who updated their phones to Oreo don't support it.[0] Basically, Google said, "With this awesome new thing, you the consumer can continue to easily get updates for years without having to wait for the OEMs to push updates!" and the OEMs said, "Yeah...we don't think we want to support that." [0]http://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/ http://www.androidpolice.com/2017/11/26/phones-updated-suppo...
  - Ajedi32 9y ago
    IIRC, all phones shipping with Oreo are required to support Treble. Also, Treble doesn't allow you to get updates "without having to wait for the OEMs", it just makes it easier for OEMs to update Android, since they no longer have to rely on chip manufacturers (e.g. Qualcomm) to provide updated drivers for the new OS version.
    - AdmiralAsshat 9y ago
      > IIRC, all phones shipping with Oreo are required to support Treble. "Shipping" is the keyword. So OEMs can get around that trivially by shipping the phone with Nougat and promising to update to Oreo very shortly thereafter, thereby bypassing the requirement. Look no further than the recently launched OnePlus 5T: http://www.androidpolice.com/2017/11/21/oneplus-confirms-wont-project-treble-current-devices-including-oneplus-5t/ http://www.androidpolice.com/2017/11/21/oneplus-confirms-won... I would not be surprised if they intentionally did it this way just to get around the Project Treble requirements. > Also, Treble doesn't allow you to get updates "without having to wait for the OEMs", it just makes it easier for OEMs to update Android This is true, but it could also allow one to more easily flash ROMs onto the device without the usual unlocking the bootleader process, which would in theory let people then put a ROM onto their phone that's still getting updates, a la LineageOS. OEMS, predictably, probably see that as a drawback.
adrianmonk 9y ago
Historically, not having a light version of Android often just encouraged crazy hardware vendors to choose an even worse form of fragmentation: sticking to an older version of Android. If those are the two choices, I think it's better to have everyone on a different flavor of the current release. At least then users have a better shot at getting security updates and app developers don't have to target quite as wide a range of API levels.

Fnoord 9y ago

That's what Android One and Project Treble are for. Android Go is meant for low end, slower connectivity devices aka "upcoming markets". I wonder if Android Go does less profiling etc. Android Go was announced half a year ago on Google I/O 2017. Here's a few sources: [1] [2]. Quoting: "Android Go will be launched with Android O, but will be an integral part of every Android version in the future. Every Android device with 1 GB of RAM or less will be able to use Android Go. Several key points of the operating system will be optimized and tweaked to take changed specs into account: * Android Go will have a new data counter, which will allow for better monitoring of data consumption. * Data Saver will be enabled by default. * The Play Store will be included with all available apps, but Android Go customized apps will be highlighted. * Gboard, Google's keyboard app, will have new translation features. * Google apps will be optimized for weaker chipsets and slower networks." Keep in mind 1 GB or less means according to the article on Google Blog: 512 MB - 1 GB. So anything less than 512 MB RAM won't fly. Data Saver [3]: "To optimize for Data Saver mode, apps should: * Remove unnecessary images * Use lower resolution for remaining images * Use lower bitrate video * Trigger existing “lite” experiences * Compress data * Respect metered vs. unmetered network status even when Data Saver is off Conversely, to work well with Data Saver, apps should not: * Autoplay videos * Prefetch content/attachments * Download updates / code * Ask to be whitelisted unless background data is truly part of core functionality * Treat whitelisting as a license to use more bandwidth" I'm not sure whether Data Saver mode uses Google proxies. The article on Google Blog is actually a decent read as well. It explains how on 8 GB flash storage, 50% is available with Android Go, and apps are 50% size. Its unclear to me how Google benefits from Android Go apart from happy customers. I'm giving some hints throughout my post but nothing conclusive. The name is also confusing given their programming language, Go. [1] https://www.androidpit.com/what-is-android-go https://www.androidpit.com/what-is-android-go [2] https://www.androidauthority.com/android-go-773037/ https://www.androidauthority.com/android-go-773037/ [3] https://source.android.com/devices/tech/connect/data-saver https://source.android.com/devices/tech/connect/data-saver

izacus 9y ago
Data saver is available since 6.x or 7.x and it doesn't use proxies at the moment.
AdmiralAsshat 9y ago
Google made a disastrous decision to make Project Treble an optional framework. The end result is that even though supporting it would allow phones to get faster updates, the vast majority of OEMs who updated their phones to Oreo don't support it.[0] Basically, Google said, "With this awesome new thing, you the consumer can continue to easily get updates for years without having to wait for the OEMs to push updates!" and the OEMs said, "Yeah...we don't think we want to support that." [0]http://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/ http://www.androidpolice.com/2017/11/26/phones-updated-suppo...
- Ajedi32 9y ago
  IIRC, all phones shipping with Oreo are required to support Treble. Also, Treble doesn't allow you to get updates "without having to wait for the OEMs", it just makes it easier for OEMs to update Android, since they no longer have to rely on chip manufacturers (e.g. Qualcomm) to provide updated drivers for the new OS version.
  - AdmiralAsshat 9y ago
    > IIRC, all phones shipping with Oreo are required to support Treble. "Shipping" is the keyword. So OEMs can get around that trivially by shipping the phone with Nougat and promising to update to Oreo very shortly thereafter, thereby bypassing the requirement. Look no further than the recently launched OnePlus 5T: http://www.androidpolice.com/2017/11/21/oneplus-confirms-wont-project-treble-current-devices-including-oneplus-5t/ http://www.androidpolice.com/2017/11/21/oneplus-confirms-won... I would not be surprised if they intentionally did it this way just to get around the Project Treble requirements. > Also, Treble doesn't allow you to get updates "without having to wait for the OEMs", it just makes it easier for OEMs to update Android This is true, but it could also allow one to more easily flash ROMs onto the device without the usual unlocking the bootleader process, which would in theory let people then put a ROM onto their phone that's still getting updates, a la LineageOS. OEMS, predictably, probably see that as a drawback.

adrianmonk 9y ago

Historically, not having a light version of Android often just encouraged crazy hardware vendors to choose an even worse form of fragmentation: sticking to an older version of Android. If those are the two choices, I think it's better to have everyone on a different flavor of the current release. At least then users have a better shot at getting security updates and app developers don't have to target quite as wide a range of API levels.