Aquila
Retired Moderator
Re: Can't agree with Pixel being the top based on their current "Best Android Phone" article
It would be possible to push O to devices that don't support seamless and then just never provide another update. No one wants that. It'd also be possible for Samsung to send their update to Google and for Google to send it out to devices - which is hackery and would be at best temporary.
The quote about it not being required is true - on N devices (those that ship with N) it isn't required. And that's a huge part of the problem. Being optional may be, "you don't have to do this, but if you do not, you're never updating devices past API level x".
There are two other possible paths.
1. The the Pixels and everything that ships with N and supports seamless updates get updated to 8.0 while everything else gets a new version of 7.x with many of the features, but it's basically a final update. Samsung has gone this route before with Gingerbread, rather than pushing an update to ICS.
2. There are two versions of O - 1 for devices that don't support requirements and 1 those that will get updated to Peeps. This is fragmentation of the worst kind and would generally suck for everyone.
But the question isn't just, "what does Google WANT to do". It is: what can Google, Samsung, HTC, Moto, LG, Huawei, Qualcomm, Sony, etc, etc. work out amongst themselves that is in the financial best interests as determined via negotiation for as many parties as possible, respective of their positional clout and tolerance?
And the final questions are - if Google does have this requirement for O, did they let their partners know about it and if so, will the OEM's actually comply for those devices that do ship with N?
It's important to remember that Google isn't doing this to Samsung, they're taking an action that improves both the security and user experience for millions of users in all future versions and the line does have to be drawn somewhere - and that line will impact a lot of devices, such as the Nexus devices, perhaps the Pixel C - etc.
It would be possible to push O to devices that don't support seamless and then just never provide another update. No one wants that. It'd also be possible for Samsung to send their update to Google and for Google to send it out to devices - which is hackery and would be at best temporary.
The quote about it not being required is true - on N devices (those that ship with N) it isn't required. And that's a huge part of the problem. Being optional may be, "you don't have to do this, but if you do not, you're never updating devices past API level x".
There are two other possible paths.
1. The the Pixels and everything that ships with N and supports seamless updates get updated to 8.0 while everything else gets a new version of 7.x with many of the features, but it's basically a final update. Samsung has gone this route before with Gingerbread, rather than pushing an update to ICS.
2. There are two versions of O - 1 for devices that don't support requirements and 1 those that will get updated to Peeps. This is fragmentation of the worst kind and would generally suck for everyone.
But the question isn't just, "what does Google WANT to do". It is: what can Google, Samsung, HTC, Moto, LG, Huawei, Qualcomm, Sony, etc, etc. work out amongst themselves that is in the financial best interests as determined via negotiation for as many parties as possible, respective of their positional clout and tolerance?
And the final questions are - if Google does have this requirement for O, did they let their partners know about it and if so, will the OEM's actually comply for those devices that do ship with N?
It's important to remember that Google isn't doing this to Samsung, they're taking an action that improves both the security and user experience for millions of users in all future versions and the line does have to be drawn somewhere - and that line will impact a lot of devices, such as the Nexus devices, perhaps the Pixel C - etc.