Motorola exec's comments on Android updates don't jibe with reality
0. phoneArena 09 Feb 2012, 12:44 posted on
This seems like a strange claim, and we're not even sure that we believe what Motorola is saying, but it Motorola executive Christy Wyatt believes that it is the Nexus hardware which is to blame for the slow...
This is a discussion for a news. To read the whole news, click here
1. kshell1 (Posts: 1143; Member since: 05 Oct 2011)
the nexus s did not use a qualcomm. it used a samsung hummingbird.
2. AndresJ (Posts: 48; Member since: 06 Feb 2012)
Even if other companies don't get the code right away it's understandable. Like Wyatt said companies need to test it before, so does google. Google doesn't want to give out OS, what is full of flaws. So please stop whining like a little bi*ch.
26. cheetah2k (Posts: 1542; Member since: 16 Jan 2011)
What a cupcake.. Wyatt should be sacked.
If its really so hard to produce firmware updates for various Motorola devices, then why the fcuk are the members of XDA Developers able to whip them up in no time?? Infact My motorola Xoom has been furnished with the latest 4.0.3 which, thanks to the Tiamat Team, works even more stable than any of the firmware released by Motorola....
So, Wyatt, just tell the truth! - Motorola have never given a fcuk about their customer base. Its as simple as that...
3. paulyyd (Posts: 338; Member since: 08 Jan 2011)
Lol I like how throughout the article you keep saying "we". "we have a bone to pick" or "we were told something else" I just think you have the problem here. Why would an executive for motorola say that then?
4. ph00ny (Posts: 1226; Member since: 26 May 2011)
This is a huge load of crap. Just for the fact that few community devs can beat them to the OS releases, that's a disgrace on its own but to make further excuses that nexus is to be blamed is hilarious
23. ngo2dd (Posts: 896; Member since: 08 Jul 2011)
the community Rom are few of bugs and then they fix it as user report the bugs. The OEM can't do that kind of things.
28. ph00ny (Posts: 1226; Member since: 26 May 2011)
OEM roms go through manufacturer QA and carrier QA. This is before we get into having access to hardware drivers, source codes, etc
I'm not saying bugs do not happen but i'm saying they can't simply blame "Nexus" device for not releasing ICS update
6. ibap (Posts: 754; Member since: 09 Sep 2009)
Comments will never "jive" with reality.
They might, however, "jibe" with reality.
IS THERE AN EDITOR OUT THERE?
7. theBankRobber (Posts: 681; Member since: 22 Sep 2011)
OK lets rethink this for a min, the other 2 devices besides the nexus S are tablets which don't have cell phone radio bands in them. So wouldn't it make sense what they are saying? If they have to make sure it works with not only hardware but also the radios inside the cell phones, Isn't both of those tablets wifi only and only the Xoom wifi got ICS? Ether way I would love to beta test ICS if they sent out invites. :)
11. remixfa (Posts: 14255; Member since: 19 Dec 2008)
nexus uses a humming bird processor and is the only android phone to do so other than the sgs1. it got the update rather quickly. I had a working port on my sgs1 months ago which is now 100% stable before any official release. the issue is Manufacturer will to do so, overlays, and carrier testing.
17. theBankRobber (Posts: 681; Member since: 22 Sep 2011)
Another sad part about what she is saying is how the dev team can make ports of ICS with minimum flaws . She is just beating around the bush, the problem is way to many phones to make the update all at once, then test each one, make tweaks it they need to, then send it to the carriers.
8. Bigbluetundra (Posts: 45; Member since: 03 Nov 2011)
Too bad there was no photo available for her that didn't use the same facial expression that Sling Blade reserved for speaking of 'french fried pertaters...nnn-huhh'. It makes her look much less credible.
10. protozeloz (Posts: 5396; Member since: 16 Sep 2010)
But moto even uses a similar processor to the one in the nexus.....
12. Sniggly (Posts: 7305; Member since: 05 Dec 2009)
Honestly, Motorola's delays are even starting to annoy me. I still love their phones, but bulls**t like the Developer's Edition and the refusal to even announce what phones are getting ICS besides Verizon's most recent Moto offerings is getting insulting.
18. remixfa (Posts: 14255; Member since: 19 Dec 2008)
didn't u just praise moto's updates in the other article?
19. Sniggly (Posts: 7305; Member since: 05 Dec 2009)
Thus far they've been great at actually getting updates OUT. However, they've been extremely vague about what devices are getting ICS so far, and the bootloader fiasco (and their response to it) still annoys me.
I love Motorola. However, they have issues I want to see worked out.
13. Whateverman (Posts: 3253; Member since: 17 May 2009)
How about the same old idea people have been saying for three years now. Make your stupid skins optional! Put the hardware together, ship it with vanilla Android, and make your stupid skins downloadable from the market. LauncherPro works perfectly fine on every Android I've had and more flexible. By making Sense, Blur, and TouchWiz an app instead of update blocking obstacle, your customers will be a bit happier as well. Don't blame it on Google, it's your own fault! And Motorola mobile wouldn't even exist anymore if it weren't for the OS they're currently b*tching about.
24. tedkord (Posts: 10922; Member since: 17 Jun 2009)
This. In fact, Google should make that part of the license - custom launcher skins have to be disableable, with vanilla enabled by default.
Of course, the reason they don't do this is it would be super easy to port to any phone. Like Sense, but prefer Samsung hardware? You could just move Sense to the Galaxy Sx, and not buy an HTC phone.
14. speckledapple (Posts: 892; Member since: 29 Sep 2011)
Actually, I think it takes a long time for them to optimize it because of their individual (Adjusts). If it were not for the addons they put with the phones, it would be out quick and quick. The problem is partly with Google for not stepping up to the plate and making some more definitive schedules for updates but manufacturers are just as much to blame for the bloatware that few ask for but they insist upon having with locked bootloaders (htc im looking at you). Bottom line is that the process needs to get better. Ice cream is a better version of Android so the system that supports it needs to get better moving forward.
16. gallitoking (Posts: 4718; Member since: 17 May 2011)
sorry to barge in here.. but my old Motorola badge still works... she is cute though
20. MorePhonesThanNeeded (Posts: 645; Member since: 23 Oct 2011)
Hey does no one here read? Motorola did say that they have to test the Android build on the current phones then make sure it works without any flaws, then add their own skin and also have to get it re-certified by the carriers...that last part right there...see it...re-certified. That is the big slow down aside from Moto's own skin, which by the way is pretty darn useful in its own right. Sure they may move slow, but not many other OEM get Android version updates faster than Moto. So this is basically a moot point.
Oh and another thing, while Moto has an idea of which phones they want to update to ICS, it still rests with the carrier on which that phone is in use. No point in wasting effort if the carrier is just going to say no. So we come to the point where Moto is going to release less phones and keep the line less cluttered so this kind of transitioning will be made much simpler. I look forward to less Moto phones per quarter and this will in turn speed up updates and hopefully we can get the carriers to back the eff off with the garbage they want OEM to do before they carry their phones. I don't need no stinking tethering VZW, I have Optimum WiFi. Moto is wise not to put it out there which phones will get ICS aside from the obvious dual core line up, keeps them from getting hate mail all day when a phone they said might get it doesn't.
21. sprockkets (Posts: 1611; Member since: 16 Jan 2012)
"The comments don't really work with what we've seen and been told. First of all, Wyatt seems to be saying that Google creates the new version of the Android software to be optimized specifically with the hardware found in the Nexus device, which flatly goes against every design comment any Google employee has ever made about Android. Google has always asserted that the software has to be optimized to run on a huge variety of hardware. The comments also go against what we've seen with the first three devices to get the ICS update, which have not been TI OMAP devices (like the Galaxy Nexus), but rather the Nexus S (Samsung Hummingbird), Asus Transformer Prime (NVIDIA Tegra 3), and Motorola XOOM (NVIDIA Tegra 2). If it were really that difficult for manufacturers to re-optimize the code for other hardware, it would follow that TI OMAP devices would see the update first. "
HTC with the sensation has to recompile the drivers for the camera, touchscreen, and other devices specific to the phone. I'm watching their progress with it, and their first test releases broke the wifi hotspot due to wifi supplicant not working. They still have to work out a few bugs here and there, and they've released 4 new radio firmwares and 4 new boot loaders to go with it.
What I believe she is saying is that yes, ICS was in development with the Galaxy Nexus, thus is ready out the door. They can't start developing and testing until the source is released. But going from 3 to 4 isn't that big of a deal for Tegra, plus nVidia helped a lot there. The only real oddball arch btw OMAP and Exynos and Qualcomm's is Qualcomm's stuff like Snapdragon which is a custom arm processor.
25. PAPINYC (banned) (Posts: 2315; Member since: 30 Jul 2011)
Of course it's a combination of manufacturer and carrier; Android has less to do with version update than it has to do with iToones.