The industry isn’t particularly happy when we ask them what the status is on a particular device, when it comes to a software update. Usually, if it isn’t public, they don’t want it to be, for one reason or another.
Our job at PhoneNews.com is to provide fair and balanced coverage, all while advocating for you, the user. Even if it’s pointing out that a company isn’t doing its duty in the customer service department, can create change in the industry. And, the more handset makers realize they’re losing customers for poor handling of firmware updates… the more likely they’ll actually start competing with the likes of Nexus and iOS.
Who knows, Microsoft might even make good on that promise of unofficial Windows Phone 8 updates for each and every device that doesn’t push through the update on its own. We’re still waiting for the details on that one, or for it to be pulled (remember, Microsoft also promised free tethering on Windows Phone 7).
Here’s what we want you to do: Post a comment with the name of a device that you care about, for which you’re still left in the dark on where all the updates are. No, we don’t want to know about devices that obviously have had their update lifespans cut off already. Your device that you don’t know if it will be updated to Windows Phone 7.8, Jelly Bean, or even Ice Cream Sandwich (yes, Droid Incredible 2 owners, we know you’re still waiting… but, please, share that grief with us). Unlike most of the industry, we’re listening.
We’ll aggregate your comments, and go after device makers and carriers the most based on your feedback.
It’s a tough job, but we’re willing to lose ad deals and draw ire to get it done. Somebody’s got to do it.
I currently own a Samsung Galaxy 3. It’s got Jelly Bean, but it took forever. The reality is that if any manufacturer promised to upgrade their phones as long as humanely possible and on time, but another manufacturer had a more appealing phone – sad to say, I’d probably choose the sexier phone, and hope that someone else would create a ROM for it I could use 12 or 18 months down the line.
Sex appeal beats updates, even though both are important. In order, I think it now goes – 1. Appeal 2. Micro-SD card slot 3. Updates.
I think a better question is – why are manufacturers pretending SD card slots are no longer a must-have feature?
Galaxy S III
I know it sounds ‘bad,’ I guess you could say since we’ve already gotten the initial jellybean update, my brother and I, but we’re in the dark for the update that brings our Motorola Atrix HD phones from 4.1.1 to 4.1.2. When we got the phones as late as we did after the phone ha been in the market, we got the update from ICS to JB in like a half a month but don’t see why it’s taking so long to go up from a .1 to .2 when we beleive, from what we’ve seen and read, that the changes from initial to final JB were almost purely ‘cosmetical.’ Surely do appreciate having you guys as our advocates and the sacrifices involved in doing so, that’s very honorable and we much appreciate you for that. It’s great to know that ‘someone’ is on our side. :]
My biggest wants would be to see my sons HTC- THUNDERBOLT to at least get ICS(Ice cream sandwhich), also my own phone, being the Razr, the first one with a non removable battery.to get jellybean…you asked.By the way, the Razr lines here to stay…
Mike, the HTC Thunderbolt has been updated to Android 4.0. If your device is not updating properly, manually run an update check from inside Settings. If that fails, call Verizon Technical Support.
The RAZR is still on-track to get Jelly Bean. Word from sources is that the entire series (Bionic, Droid 4, and RAZR/maxx) will be updated in the March-April timeframe, provided there aren’t additional testing delays.
Droid Incredible 2. Still in awe the 4MB update released last week was not ICS, and still unclear exactly what the update “enhanced”
The 4 MB update was a critical update to fix a security hole in Gingerbread. Our understanding was that ICS had to be delayed to fix the major security hole… since ICS wasn’t ready to release.
And yes, that means ironically that all the delays in getting Gingerbread replaced on DI2 wound up delaying the ICS update further… to go back and patch Gingerbread once again.