Motorola says its older, low-range Android devices will no longer get upgrades
posted by Alan F. / Feb 08, 2011, 10:02 PM
While some might have bought these models in the hope that the phone would eventually be upgraded to at least the Android 2.2 build required to install Adobe Flash Player 10.1, these low -range models may not have the processor speed required. Regardless, Motorola did say that it made every effort to upgrade these models, but at the end of the day, nothing could be done. As the company said, "In the end, we were not able to develop a version ... that would deliver an optimal customer experience."
The remaining three phones are the PTT Motorola i1, the Motorola FLIPOUT and the Motorola CHARM. The first will forever more be frozen at Android 1.5, while the latter two will stop at Android 2.1. For owners of the CHARM and FLIPOUT, being frozen at Eclair must be especially galling considering the next upgrade would be the Froyo build that would allow for Flash support.
As for those who are holding on to their Motorola DROID, the ole' boy has held them in good stead so far with the phone currently upgraded to Android 2.2. Thanks to its lack of MotoBlur, Motorola has found it easier to upgrade the DROID than say, the DROID X. And while it looks like the phone that started the current run of Androidmania will be able to get upgraded to Android 2.3, the DROID's comparatively slow processor and 18 month old-specs means that eventually the Time Magazine 2009 Gadget of The Year will no longer receive the next build. But for now, there should be at least one more upgrade left in the handset.
source: Computerworld via TheDroidGuy, androinica
Posts: 31; Member since: Jan 17, 2011
An this is why HTC remains the best choice for any Android lover, personally having t go through that whole Cliq update mess made me lose faith in Motorola, hopefully this year they do better but until then HTC it is
posted on Feb 08, 2011, 10:13 PM 4
Posts: 1436; Member since: Jul 11, 2008
HTC is no better. The DROID eris, aria, and G1 are in the same spot. Granted the G1 is ancient by modern trends. But these devices are stuck in the upgrade limbo. And just like moto takes longer updating devices with blur, so does HTC with sense. People just wouldn't notice since sense is in almost every HTC device but this is apparent if you look at the upgrade cycle of the nexus 1 and sense UI handsets. Sure the nexus is a dev handset at heart but that's because it can upgrade asap thanks to the lack of sense.
posted on Feb 08, 2011, 11:12 PM 1
BTW the Droid eris and aria weren't even in the same class hardware wise as the Motorola Droid. Gawd don't even get me started on the G1. Simple fact is that the Droid was a high end device that made officially upgrading easier. The G1 isn't even worth upgrading if it can't even use all the features that Froyo can offer due to its older hardware. Getting Froyo first on the Nexus 1 is like the jackass who replies "first" in the comments. So you got it first but whats the point if phone is a POS by modern hardware standards. I feel the whole first issue is a justification of the original expensive price of the Nexus 1. The downside was that Verizon, At&t, Sprint all passed on providing a "pure google" phone and decided for us that we love bloatware and extra UI's. Besides, if ur brave just jailbreak ur phone with mods.
posted on Feb 09, 2011, 2:24 AM 0
If there going to sell them then they need to keep them updated through the 2 year contract.
posted on Feb 09, 2011, 3:11 AM 0
Posts: 124; Member since: Jan 05, 2011
They are not obligated to keep them upgraded during the two year period. Cellphones are like computers used to be. They are getting better hardware, software, every few months. To expect a phone that is a year or two old to be able to take updates intended for newer phones is unreasonable. The phones that do not get upgraded will work just fine over a two year contract. Seems to me the only people this will bug are the nitpicky phone addicts out there.
posted on Feb 09, 2011, 5:54 AM 0
What concerns me is that it seems maybe my memory isnt as good as they dont want to update any phones with Motorola blur on it. They have the atrix coming out for att with blur on it which now makes me think it may never get an update.
posted on Feb 09, 2011, 7:30 AM 0
Blur, SenseUI etc are honestly the bane of android inmho. They are the root cause of all the "fragmentation" complaining out there. imho they should make these UIs... applications. Easy to remove/install if a user wants to. Then hopefully upgrades would be easier for everyone. Not to mention as least give options to mitigate "fragmentation".
posted on Feb 09, 2011, 9:48 AM 1
Posts: 3165; Member since: Jun 19, 2010
This is the biggest downfall of the Android platform, leaving it up to the phone manufacturers and carriers to do software updates. They are only in it to sell phones. Why update the phones when you can just PO the current users and make them feel forced into paying retail price for phone or cancel their current carrier and upgrade with someone else to get a phone? You sell more phones this way. Google really needs to step in here, because the carriers and manufacturers so far have proved they dont care about the end users.
posted on Feb 10, 2011, 9:49 PM 0
Posts: 3165; Member since: Jun 19, 2010
Think of it this way. Say Microsoft decided to "leave it up to HP, Dell, Toshiba, etc." to release the updates for their computers. We would start seeing major fragmentation on the Windows market, and also say you buy a new HP PC with Windows 7, but HP decides your particular computer model is only good enough to receive updates for the next year despite your PC being capable of the updated software. The goal is to drive you to buy more, and this plan will backfire on them and push people to iOS, WebOS, Symbian, and WP7 phones sooner rather than later.
posted on Feb 10, 2011, 10:02 PM 0
Send a warning to post author
Send a warning to Selected user.
The user has 0 warnings currently.
Next warning will result in ban!
Ban user and delete all posts
Message to PhoneArena moderator (optional):