5 ms·

We've seen a similar promise from Google at I/O 2011 about Android OS updates: > [W]e're jointly announcing that new devices from participating partners will r

by conroy 13y ago

We've seen a similar promise from Google at I/O 2011 about Android OS updates: > [W]e're jointly announcing that new devices from participating partners will receive the latest Android platform upgrades for 18 months after the device is first released, as long as the hardware allows ... and that's just the beginning. [1] The announced partners were Verizon, HTC, Samsung, Sprint, Sony Ericsson, LG, T-Mobile, Vodafone, Motorola and AT&T. Since then, many have broken that promise[2]. Three of them (Sprint, T-Mobile, and LG) are now Firefox OS partners. I'm just skeptical that this time will be any different. [1] http://googleblog.blogspot.com/2011/05/android-momentum-mobile-and-more-at.html http://googleblog.blogspot.com/2011/05/android-momentum-mobi... [2] http://arstechnica.com/gadgets/2012/06/what-happened-to-the-android-update-alliance/ http://arstechnica.com/gadgets/2012/06/what-happened-to-the-...

cpeterso 13y ago
I think those manufactuers' broken promises are why Google is pushing the Google "Play Services" library (released at Google I/O 2013) that adds new APIs that are compatible from Froyo and above. An old device many have an outdated OS, but Google can still push new Play Services APIs from the Play Store (and Google has to deal with the backwards compatibility).
ndesaulniers 13y ago
This is a legitimate concern. As part of the licensing agreement to be called a "Firefox OS phone" I believe carriers must provide updates for a certain amount of time. For how long, I do not know. If the duration is public knowledge, I do not know. If partners will actually follow through, well... the articles you linked to paint a bleak picture. Of course, since our entire OS is open source, they can just use it on their own, and never release a single update, as long as they don't brand it a "Firefox OS phone." I'm prototyping an add on right now that would detect a connected device, download updated pre-compiled images of the layers (gonk, gecko, gaia) and allow you to update them (if I verified that the update worked on your device beforehand, to make sure you wouldn't end up bricking your phone). Just trying to raise awareness within the org right now to get a green light to work on this more.

by conroy 13y ago

cpeterso 13y ago

I think those manufactuers' broken promises are why Google is pushing the Google "Play Services" library (released at Google I/O 2013) that adds new APIs that are compatible from Froyo and above. An old device many have an outdated OS, but Google can still push new Play Services APIs from the Play Store (and Google has to deal with the backwards compatibility).

ndesaulniers 13y ago

This is a legitimate concern. As part of the licensing agreement to be called a "Firefox OS phone" I believe carriers must provide updates for a certain amount of time. For how long, I do not know. If the duration is public knowledge, I do not know. If partners will actually follow through, well... the articles you linked to paint a bleak picture. Of course, since our entire OS is open source, they can just use it on their own, and never release a single update, as long as they don't brand it a "Firefox OS phone." I'm prototyping an add on right now that would detect a connected device, download updated pre-compiled images of the layers (gonk, gecko, gaia) and allow you to update them (if I verified that the update worked on your device beforehand, to make sure you wouldn't end up bricking your phone). Just trying to raise awareness within the org right now to get a green light to work on this more.