Share this Story

Motorola: Google’s Nexus Hardware Choice to Blame for Slow Android Updates

Ever wondered why it takes so long for smartphone manufacturers to push the latest version of Android to your phone? According to Motorola, it’s because of hardware. And more specifically, it’s because of the hardware and chipsets that Google chooses to develop their newest versions of Android on.

As many of you know, Google invites all Android players to produce a phone and submit it for consideration at becoming the next “Nexus.” It’s a battle we don’t know all the specifics on, but with Samsung winning the last two Nexus titles, you should have an idea as to what Google expects. But with Google choosing a particular manufacturer to build the phone, they also pick a processor and other hardware components that they feel will really help push development of the platform. You may not see the normal pairings for chipsets and phones when it comes to a Nexus. For example, the Galaxy Nexus is produced by Samsung and runs a TI OMAP4460. Samsung has almost always used their own processors in phones and from time to time will slip in something from Qualcomm, but TI is new ground for them.

So Motorola is basically saying that Google is optimizing Android for that specific phone and chipset, which then makes it difficult for other manufacturers who use other chipsets to get Android to play nicely, hence the long drawn out update periods. And Google does in fact optimize the newest version of Android for whatever chipset and phone that has been chosen, which is why Nexus devices are almost always more fluid, responsive, and stable at the OS level than other non-Nexus phones. (Notice I said “OS level” and not “radio level” – damn Samsung.) Hard to argue with the idea that it could slow them down some, but it’s also not the only reason these things take so long.

You also can’t forget that Moto and other OEMs like to slap on their custom skins and that carriers want their grubby hands all over the updates once they are finished to make sure they will work well enough on their network. There are a number of factors here. Hardware compatibility is one, just not the only one.

Via:  PCMag

  • Anonymous

    i have a feeling that moto gave google the razr for the nexus competition , so they lost and are now bitching about it

    • Truthfully, I almost wish Moto won it. I like the G-Nex, but I like the Razr’s build quality more.

  • Prime7

    Here’s an idea for Moto: make a good phone, for a change, and maybe they’ll win the Nexus brand.

  • Anonymous

    And this is why you should own a nexus!

  • Whatever Moto, don’t blame Google. It’s those horrible custom skins with the added bloatware that is the hinderance for our upgrades!!! We the people know the deal!!!

  • Anonymous

    So sick of Motorola always having excuses.
    Don’t buy their garbage products folks.

  • Where does that leave me, or rather my Moto XYBOARD 8.2. If it doesn’t get 4 by this summer, I’m moving on to Windows. This crap is getting old!

  • Del Preston

    If Pete Alfonso can do it, why can’t Moto?

  • Del Preston

    My Senses were Blurred, so I took a Touchwiz, and it came out pure vanilla stock @; )

  • Anonymous

    I agree with Motorola here.  Google should man up, throw some more resources at the project and work with the top 4 partners at the same time to get updates out in sync.  If any of the partners leak anything or mess up the release schedule, they get tossed out of the club and #5 gets added. 

    • ddevito

      What the hell are you talking about?

      Google gives them the code, OEMs have had ICS code since November.

      • Anonymous

        Obviously, that’s my point.  Google develops behind closed doors for 6 months with one partner, they should include a few more in that process at once.  This is the biggest reason there is a 6 month lag after launch for most phones to get the new version of the OS.  After the lead device is released, Google throws the code over the wall and all the other OEMs have to start from scratch.  Getting it working on their devices and validated by all the carriers they will run on takes a long time.

        • which is why businesses won’t do this. they would have to stick with the once processor, and a sales point to normal consumers is better and faster. it would allow less processor choices

  • Joeybee01


    I am new here and just got a Galaxy Nexus.  I saw that there was a release of version 4.0.4, but my phone did not update and is still running 4.0.2.  The only thing that I have done to my phone is unlocked it, is this preventing me from getting the update?

    • Anonymous

      4.0.3 is only a tablet release and some Nexus S phones, 4.0.4 is only a leak at this point.  4.0.2 is the official release for the GNex.

  • ddevito

    Oh yeah, well, this Nexus hardware was capable of this. eat it Moto.


    • Wow. i almost spit my food out when i saw this. Verizon is really on track with hitting 100Mbps

  • ddevito

    Isn’t this THE EXACT reason Google chose a TI CPU? Wow Moto is so stupid

  • J Dub

    Well then how is it that the Cyanogen Mod team can build a ROM for like 50 different devices across all manufactures and do it better than the OEM can?

  • Jordan

    So why is ICS already running on my Snapdragon powered Samsung Captivate? I’m calling BS on this one. 

    • Jordan

      Sorry Hummingbird**

      • Hummingbird == Exynos 3110. But it’s because they took great pains to do ABI translation from the Gingerbread kernel to the Ice Cream Sandwich kernel. Annoying as hell to do, but it can work. Brittle as hell, though.

  • Azndan4

    There goes Motorola making excuses for their failures like usual.

  • Anonymous

    so basically moto is bitching because they lost the competition to make the nexus

  • Maybe if Moto didn’t produce phone’s with locked bootloaders, pentile screens, and (at times) yesterday’s technology (I’m looking at you, Razr qhd screen), they could actually be chosen as a Nexus provider.

  • Okay, Moto. Since you can do better, YOU make a Nexus then. With a keyboard. Global. NO PenTile. {{-_-}}

  • Anonymous

    … moto is sooooooo stupid. hey moto, your new devices all run omap’s.

  • DaveTea

    Updates are slow as the manufacturers simply want to sell you a new phone instead of worry about providing free updates for a device they have already sold. Its a low priority for them. If they really cared about pushing high quality updates several times during the life of a phone they would hire a large enough technical staff to make it happen. Its in their best interest to spend their time and money developing the next phone that they want to bring to market not to improve existing phones. It sucks..but that is the reality of the situation. When you have small teams of hobby developers cranking out ROMs with fixes and new features it tells me that Moto (or anyone) does not care enough to do the same. If they did they would hire a few more folks to get it done.

  • Anonymous

    Some high school kids can get a ROM up & running before Moto can – and with better quality too!  I know, I own a DX and a Xoom.  Next device will not be a Moto.

  • Anonymous

    MOTO = butthurt

  • deeznuts

    Solution: Boycott motorola and scrap your Bionic/RAZR/Atrix/X/X2 and get a GNex.  You won’t regret it.  To hell with motorola with their lies and lack of updates and locked bootloaders.

    • Anonymous

      Nexus fanboy troll alert!

      • Staticx57

        then get a Rezound… just not moto.

        • Anonymous

          HTC is garbage; plastic pieces of crap.

          • Droidlynn

            I agree, Htc really is cruddy, but I have to give them credit for when they told Apple off by telling them to “quit suing and play fairly”, cuz Apple wants to monopolize everything. I have a DROID X, and love it, and don’t want to upgrade even when I’m due for one next year. It would be like getting rid of my feathered daughter for a bird that is better than her. Also Verizon is so greedy about money, cuz all they want you to do is upgrade to a better phone every 2 years. I’ve been with VZW since 2004 and I’ve upgraded every 2 years, and I have the perfect phone which is my Droid X. X is the best friend I never had. X even behaves better than my animals do. I can’t imagine life without my X.

          • Anonymous

            Yes but HTC can’t back anything up against Apple.  Only Moto can go after them and win in these patent wars.

          • Anonymous

            You do realized out of contract you are still paying the same price for your plan as you were when you were paying for a subsidized phone. Anyone who does not upgrade every 2 years is just loosing money.

          • And what is the Bionic made out of? LOL 


          • Anonymous

            Compared to HTC……yes! 😀

      • Vonny571

        Moto fanboy response???

        • Anonymous

          Fan of phones that actually work as such.  At least Moto phones can make phone calls compared to the Nexus.

          • ddevito

            This is based on what? I haven’t droped a call on my GNex yet.

          • Anonymous

            You were one of the lucky ones then.  Most returns of the Nexus were because people couldn’t connect to LTE where they once could or couldn’t even make a phone call without having it drop.

          • ddevito
          • Anonymous

            And this is to mean what?  It is fake anyway because Veizon’s LTE is not capable of more than 42Mbps.

          • Jim McClain

            my best is  41.52 mbps download and 17.02 mbps upload

          • Anonymous

            That is on the high end of most LTE, but much more realistic than 72Mbps.

          • Jim McClain

            thats a full 4 bars on lte

          • Back when 4G was still new to Indy, I pulled more than 42 on my Bionic, 46 or 47 IIRC.

          • Anonymous

            Still realistic compared to 72.

          • it isn’t fake. Verizon’s contract to keep its spectrum’s it to get to 100Mbps by 2013

          • That is, unfortunately, by design. The Nexus actually is one of the few CDMA phones that do CSFB as well as active dual-mode operation for voice. 

            If you aren’t actively using data (i.e. non-background process), then CSFB knocks you off LTE. Occasionally, it trips up and CSFB kicks in prematurely when a data request is sent out and kicks you off CDMA to activate an LTE data session.

            If you have the phone set to use active dual-mode operation (the default for all other Verizon LTE phones), battery life is chewed up, but no more dropped calls.

            The thing is, CSFB is not intended for CDMA2000/LTE devices. It’s intended for HSPA+/LTE devices. I’m not sure why it is even supported in the Galaxy Nexus for Verizon.

          • Anonymous

            Sorry to say that all the new LTE phones (Bionic forward) have dual mode so you can talk on 3g and surf on LTE.  The difference is that the moto phones don’t drop calls like the Nexus does and can connect to LTE where the nexus can’t.  Now there are data drop issues with the moto phones that they are working on and getting better.

          • Of course they can. The thing is, there are two different approaches to doing that. One approach is to have both the CDMA2000 and LTE radios constantly connected, and another way is to always have LTE connected until a call starts, and only start an LTE radio when data requests come through while in a call. Active dual-mode operation describes the former, while CSFB describes the latter.

          • Anonymous

            Count me as lucky one too then, cause I’ve yet to drop a call, like ever. And I had it the day it came out.
            Also I recall there being a poll about this “problem” in this very site and it reported that 73% of people never experienced this “problem”. Thats lot of lucky people.

    • Jim McClain

      well I have a nexus, and if by the end of the month they dont have an update to fix all the crap thats wrong with this thing, im going to verizon and raise hell till they trade me a razor maxx for this piece os $hit

  • Android should just run like windows.  All PC builds are different yet they can all run windows granted the specs are good enough.  Google should make the builds for phones honestly…They are a software-based company, let the manufacturers worry about phones builds and let Google design the software or at least force the companies to make stock android versions available to dl onto devices if users want.

    • That is exactly what they do…?

      Google does not manufacture phones, they manufacture software.  Open source software, which means any and all manufacturers can take advantage of it if they please.  Even Windows has to have hardware (built by someone else, just like Google does), to develop the next version of Windows.  You don’t just develop software without some sort of hardware to build and test it on.

    • ddevito

      Google makes Android. The OEMs chose to make their sh1tty skins. Google doesn’t license Android so they can do what they want with it.

      Blame the OEMs, not Google

  • Anonymous

    And yet Moto is the fastest (behind Google) at updating their entire lineup of phones….

    • Anonymous


  • Darkseider

    Um so what’s Motorola’s excuse for not having timely updates or for that matter non existent updates for the majority of their phones?  Seeing that the TI OMAP 3x and 4x are what’s in most of their devices the GNex’s hardware shouldn’t be an issue.  

  • I bet the RAZR was submitted as a Nexus and Motorola is pissed they lost so they slapped the Iconic name on that phone and were hoping to stick it to Samsung by releasing it first.  Now they have to piss and moan and do whatever they can to keep people from buying a phone that will have ICS before 2013.

  • Avienrandeor

    Apparently Asus didn’t get that memo with the Transformer Prime.  

    • I wish the Moto rep that stated this was standing right in front of us and could be forced to reply to what you just said.  If what they say is true, how exactly did Asus get ICS out so fast on the Prime?  That negates their whole argument.  

  • Anonymous

    Motorola you are quickly becoming the laughing stock of the mobile industry. Please stop playing games and clouding the real issue. “its not us, it’s them” seems to be the standard answer you have when it comes to everything.. Locked bootloader = Verizon.. Slow updates = Google Nexus hardware.. 

  • Anonymous

    I never pointed this out but when i purchased my g-nexus there was a qualcom label right next to the usb port

    • That is because Qualcomm owns CDMA every CDMA phone ever made has to have a Qualcomm sticker on it.  Even Motorola CMDA phones have a Qualcomm sticker on them.  Well they own the essential patents that make CDMA possible so if you wanna run CDMA you have to pay Qualcomm some sort of licensing.  Qualcomm generally is good about it and requires their sticker along with some nice fees. Here is a wikipedia article so take it with a grain of salt but even going to Qualcomms site you can find the information about them owning CMDA 1x-EVDO.


      • PC_Tool

        This is also the reason CDMA devices are no longer “supported” by AOSP:  Qualcomm BS.

  • Anonymous

    moto’s a big cry baby

  • Matthew Rosidivito

    Assuming this is true (which I am sceptical of), I would still rather have one super fluid phone and 49 decent “get’s the job done” phones as opposed to just 50 decent “get’s the job done” phones.

  • Bunkheaded

    I believe it is because of the crappy skins that manufacturers put on all of their devices. I loved my Samsung Galaxy Tab 10.1, then they released a crappy new skin with the newer version. I feel like I got a switcheroo pulled on me.

  • Boblevel

    Another Motor Exec that Google will be firing once they take over..

  • Anonymous

    I think they mean they’re ready to release ICS on my X2 and XOOM LTE. Go Team Tegra 2! Ha

  • Anonymous

    This is obvious BS.  Android updates take so long because of the following reasons:

    -OEMs inherently don’t care about phones once you buy them
    -OEMs just suck at software. They’re hardware makers, they haven’t been known for software until Android
    -They feel the need the “differentiate” their phones by adding BS apps, skins, and frameworks that need to be updated before an Android update can roll out. If they just rolled plain AOSP they’d only have to worry about drivers
    -Carrier meddling and testing

    OEMs should feel ashamed every time a small group of hackers in the basement can release an updated ROM that is smoother than their stock ROM (see the Thunderbolt). There is no excuse for it.

  • Anonymous

    I call bullsh!t.

  • Arm chair despot

    ….cue the Moto bashers who are SO in the know, that they are more informed than Motorola themselves. Couldn’t possibly be that Moto has a point. Read the actual article on PCMag.

    • Except Motorola is missing the point. The RAZR and Nexus core hardware platform is the same (TI OMAP 44xx). The 4430 and 4460 aren’t that much different. Both use Samsung Super AMOLED display modules, though the Nexus is at 720p HD instead of 540p HD. The main differences lie in the 3G, WiFi/BT, and GPS modules. However, those use standard interfaces and the only change required is a kernel driver swap.

      For the most part, there isn’t really anything hardware wise that is a significant blocker for all of the hardware released in the second half of the year on Verizon. The Photon on Sprint, maybe, but nothing on Verizon.

      • Stephen D

        The RAZR’s OLED screen isn’t from Samsung. I believe it’s actually a Sony display. 

        • Then the Motorola can’t call it a “Super AMOLED” display. “Super AMOLED” is a trademark of Samsung, and only Samsung’s displays can be called “Super AMOLED.” That’s why LG’s equivalent is called “Ultra AMOLED.”

        • Anonymous

          Only Samsung makes the Super Amoled brand. If Sony or LG made the oled screen, it’s not Super Amoled. Just so you know Super Amoled is a type of technology (Super-Thin Active Matrix OLED method for manufacturing) patented by Samsung.

          So, the Razr’s “Super Amoled Advanced” screen is from Samsung.

          • Stephen D

            I know what an OLED screen is….point is, Sony has an OLED division, and I forget where, but I read that the OLED on the Razr is from Sony. Don’t forget that Samsung manufactures most of Sony’s panels, at least for LCDs. 

            Oh well. It’s a pretty awful display no matter who makes it. The green push drives me nuts.  

      • Arm chair despot

         Like I said, read the actual article. Moto is talking about making ALL the various chips and hardware parameters (not just the processor) across all of the global market play nice. There are lots of other variables involved (camera, modem, memory etc.). It’s not as simple as just the processor.

        • Arm chair despot

           (the “read the actual article” sounded snarky… wasn’t meant to, just meant referring to the source article).

        • Unsurprisingly, it’s actually not that difficult to swap out support for different modules. The only slightly complex part would be cellular banding. That’s just changing configuration data so that certain technologies and bands are supported in software. Not really that difficult, especially since the software now supports auto-discovery of banding and air interface.

          The Linux kernel provides standard interfaces for everything, and Android uses them. If it was so difficult to swap out kernel drivers, then how in the world is CyanogenMOD able to do it? It only becomes difficult if you have to translate ABIs like CyanogenMOD has to sometimes.

          Motorola doesn’t have to do that, since it has access to the kernel module sources for all components of its devices.

    • deez

      …and because motorola has been SO honest in the past.

    • Anonymous

      Reading the article, “When Google does a release of the software … they do a version of the
      software for whatever phone they just shipped,” she said. “The rest of
      the ecosystem doesn’t see it until you see it. Hardware is by far the
      long pole in the tent, with multiple chipsets and multiple radio bands
      for multiple countries. It’s a big machine to churn.”

      Motorola understands that consumers want their Android upgrades sooner,
      but the process is complicated, she said. First there’s hardware
      support, then the layering in of custom software from manufacturers like
      Motorola, and finally, phones must be re-certified by carriers, taking
      more time”

      But the source has been out for a while now and there are builds that are made for each chipset and the APIs are also out for them. They also do a release of the source a bit earlier than when the build is released to the phone. So how is it that hobbyists are able to get builds out and the company with all the code and drivers cannot do it? Does Motorola make an effort to have people on staff to update the OS for their systems? Why is it that they have so many chip sets if it is troublesome? What she describes is them shooting themselves in the foot.

  • Anonymous

    Other than the fact that the Razr Maxx is a pretty good device, moto has failed miserably at everything else.

    • You mean the RAZR Maxx battery is pretty good.  Other than that the software and display (the 2 most important things about a phone other than battery) are garbage.

      • Jtwildman1

        Not sure what’s to not like about the display. I hate Verizon bloat ware, but everything else about the phone is awesome! It is a very well built phone. Its ok if you don’t want a phone with a locked bootloader or “skin” but everything else about the phone is top notch. I’m not a fanboy of anything but Android, motorola built a fantastic device with this one.

  • Michael Forte

    How about manufacturers stop with releasing 50 different phones every year on top of putting skins on Android? I’m sure we’d see much faster updates if that were the case. Each manufacturer should release maybe 3-4 phones a year, that’s it.

    • Matthew Rosidivito


    • How about they release 1 a year.  Why do we need 3 or 4?

      • Michael Forte

        1 high end slab, a lower end phone, and a keyboard phone. Release the same devices on all carriers too.

      • Eddie Jr

         3 or 4 is perfect.  It’s good to have choices vs the 1 fits all model.

      • Anonymous

        I have the answer.. Choice

    • QtDL

       I agree that 3-4 phones a year per OEM is perfect. 1 phone per quarter released and then they can concentrate on updates. A low, mid, and high end phone and a keyboard slider will likely cover all bases.

  • So what’s Moto’s excuse for not getting the Bionic update out sooner?  Its got the TI OMAP4430

  • So then release a vanilla version of Android that works on the phone and allow their customers to update to that first. Then once the manufacturer skin version is ready, release that. Then they can gauge how much real interest their is in customers who want to use their skins. 

    Honestly, most of the manufacturer skins are not worth the time it takes to update the newest version of Android to use them. This might have been the case back in the early days of Android, but definitely not anymore. 

  • Anonymous

    Is it me or is Motorola making excuses. Who else is the biggest user of the TI chipsets? Motorola! So they have plenty of experience in that department. They can say whatever they want at this point because they’re very close to being acquired.

  • James

    This is garbage. Cyanogenmod always ran the newest versions of Android on all kinds of phones. So its not a hardware problem.

    • Cyanogenmod also releases nightly builds that are not always 100% stable and drives its fixes off of community involvement. Cyanogenmod doesn’t support every device either all at one time a lot get added over time. Motorola can’t afford to jsut give their beta software to everyone and expect feed back.  They have an obligation to release software that works.  Granted they miss sometimes and do have to bug fix but over all when a new release comes out it can stand on it’s own for a while. Cyanogenmod has plenty of builds that stuff is completely busted for quite a while.  People live with the Cyanogenmod bugs because they can report them and realize they are not Motorola and didn’t design it.  It’s all in the mindset you take into it.  If Cyanogenmod released a phone that they developed and were able to sell it on a carrier like Verizon it would take a lot longer and there would be a lot of features left out.  Cyanogenmod right now is having troubles with CM9 due to getting the drivers to run the hardware in the phones.  It is most certainly a hardware problem and it is either something you live with or you can go buy an iPhone their hardware is all similar enough they can push a major change out to nearly all of their devices at the same time.  Same goes for PC’s, there was plenty of hardware that was no longer supported in windows 7 because the manufacturers were not going to take the time to make it work.  You have to draw a line somewhere.  I personally think they need to stop releasing a new device every 2 months and only do 1 device a quarter so they can focus on working out these bugs.

      • James

        Ok forget about CM7. When I had an OG Droid, Motorola said 2.3 was not coming bc the hardware wasn’t up to specs yet Pete’s 2.3 AOSP ROM worked ran fine on it with no problem. If one guy can basically figure it out why can’t a whole team? Maybe I am misinformed but I don’t really see what Motorola is talking about here.

        • James

          My apologies for the slight typo, I’m typing this on my phone.

        • Marvin de Pano

           The OG at the time is old news and they just want you to buy new phones.

          • Anonymous

            I think you missed his point…

          • Marvin de Pano

             Why would you spend time porting over an OS on an old phone when you got newer phones coming out?

          • Anonymous

            You are still missing the point. Peter Alfanso single handedly got a pure stock version of GB to work practically flawlessly on an OG Droid. He’s not saying they need to put ICS on the Droid, he’s saying that if one guy can do it on a phone that “wasn’t up to spec” then what is the problem putting it on a phone with arguably similar specs.

          • Anonymous

            The OG could NOT run GB.  I had every version built trying to run and they all sucked.  Screen refreshes made it impossible to use the phone.  The OG was a great phone but when GB came out it was time to upgrade.

          • ddevito

            My OG ran Pete Alfonso’s GPA series of Gingerbread (stock) ROMs, ran flawlessly. Moto had no excuse

          • Anonymous

            Again, you are one of the lucky ones because the OG was known for horrible homescreen refresh due to lack of memory running GB.

          • Marvin de Pano

             This ^. Couple the fact that even with compcache on GMaps was closing by itself all the time (not FC, but closing).

          • Marvin de Pano

             Dude, read again what I wrote, it’s all about money! Comprende?

          • Anonymous

            Wait… Are you saying Moto didn’t put GB on the Droid because it wasn’t worth the money?

            If so, that makes sense. It just took a couple drinks for me to understand you.

          • Marvin de Pano

             Yes! It only took you 2? It took me 4 to understand you.

          • Anonymous

            With the bass acwards thinking you had to do to come up with your irrelevant point, I could see it taking that many.

          • Marvin de Pano

             Whatever man, have a good day!

          • Sdasdsa

            just want 
            to see
            this text become in this thight place

          • Saasd

            me too

      • KingDuece

        Then why are new phones with up to date or better hardware being released with older versions?

      • Anonymous

        B.S. Moto could get their testing and feedback done simply by paying people to run nightly builds. It shouldn’t be hard for a major corporation with deep pockets to do something the CM team gets volunteers to do.

  • If it were hardware limitations the custom ROM projects would be affected.  The only thing that holds back the custom ROMs are the lack of source code from the manufacturers and of course locked bootloaders.

    Really it’s a combination of factors, for one thing the carriers and the phone manufacturers both have a vested interest in keeping the latest android goodies from customers who bought their phones 6 months ago or longer. They would much rather sell you a new phone and get you to extend your contract (and pay a hefty premium for your hardware if you aren’t eligible for a full upgrade “discount” and also the custom skins make it much harder.

    • Luke Murray

      This isn’t necessarily true.  On the custom ROM side of things, they usually receive the source code for most of what they need.  For the rest, they’re burdened w/ the chore of reverse engineering that code.  The difference, however, is that the development community plays friendly with one another.  When one developer has a break through, s/he shares that breakthrough with the rest of the community.  This makes the whole process seem to go much smoother as one breakthrough causes the rest of the community to have a little less work.  This is all evident when major version updates occur.  Take the Droid Bionic atm.  We don’t have a fully working ICS ROM yet because of a hinderance w/ the way data is handled on it.  We have several people working together on it, though.  Once that is overcome, we’ll see several ICS ROMs for that device start cropping up.

      • Anonymous

        No no no; you’re doing it wrong. It’s because of Motoblur and Verizon bloatware. Shut up with the facts and reason and stuff.

      • With the ICS for Bionic though, we don’t have camera support. I assume that’s something that won’t be fixed for a good while either, since we’ve nothing to reference from for that until Motorola accidentally slips up and a dev build or leak gets out so we can have the drivers for it. 

        Everyone in the process from OEM to Carrier is at fault. If the OEMs weren’t so concerned with differentiating themselves and adding functionality to their phones and only their phones, we probably wouldn’t have half the mess we do.

        You made a great point about the way data is handled on the Bionic vs the RAZR. However, why is it that those two phones handle things so differently if at a software and hardware level they’re so similar? We need for Moto ICS stuff to start leaking out and about, get in the hands of CM or any of the devs working on the D3/Bionic/RAZR/D4. 

        This still isn’t going to solve the issue with Motorola’s encrypted bootloaders. Which is the #1 reason I don’t think I’ll be buying another Moto phone for a while. I love the hardware on my Bionic, but I hate the software, and in the past Droid/Incredible/Fascinate, heck even my Blackberries.. I’ve been able to flash custom software and take care of the things I don’t like about my device. I can do that now, but it’s nothing like it was on any of my other devices. I also feel like it’s unfair to have to essentially fill up my internal storage to swap into another ROM like LIberty, which is great, I just don’t feel like it’s all the way there. I want AOSP, and I’d strongly prefer CM. I want to be able to flash a standard recovery and just swap between ROMs and backups at will, without having to turn off and on a ‘safe’ mode with my bootstrap. 

  • Tabe

    Moto, way to blame the TI chipset when you use the….. TI chipset…. We know its because of your custom skin, nice try though.

  • Anonymous

    Off subject, but I can’t stand that I get only 5 home pages on my gnex. And I don’t want to download a launcher. I only want more pages! Hope google will give me that in a release sometime. Anybody know of an app that will only give me more pages? I don’t think it exists, it would have to be a new launcher.

    • Kuboo99

       NOVA launcher is pretty good, it really doesn’t look any different than the stock launcher. Catch is to make everything work (the widgets in the app drawer) you need to be rooted so you can flash it in Clockwork Recovery.

      • Kuboo99

         Oh yeah, and it lets you have more homescreens. Forgot to mention that in my first comment.

        • Anonymous

          Love it…problem solved

    • Anonymous

      Nova is just like the stock launcher IMO. You do have to be rooted to get the widgets to appear with the apps though. I prefer my widgets to show up like they used to (grouped in a vertical array) so the Nova Launcher was perfect for my needs.

      I’m also the guy that doesn’t fill up 3 screens so….

  • Worm

    Slow news day apparently. Thought this was common knowledge

  • John

    I blame MotoBlur.

  • They’re just mad they haven’t got a Nexus yet.  Pretty lame move by Moto if you ask me.

    • Anonymous

      For all intents and purposes, the O.G. Droid was the first Nexus device. And let’s not forget the fact that the Xoom was essentially the HC Nexus of tablets. That said, I do not feel that it was fair to give Samsung two Nexus handsets in a row. I would much rather have seen Motorola or HTC hardware for ICS. Or, better yet, two or even three Nexus handsets for each release– perhaps one with a keyboard and one without?

      • Wasn’t the T-Mo G1 actually the first Nexus the OG was the first popular one but not the first IMO.  There is also the XOOM which they screwed up completely but the Nexus One was only shortly after the OG anyways.  I wanted to see Samsung screens with Moto Radios.  That would make one hell of a phone.

        • Anonymous

          Samsung screen + Moto radios = RAZR.

  • MFG

    Damn…if only Motorola could work more closely with Google…

    • Trooper

      Indeed. Or sell their radios to Samsung since their’s suck.

      • Anonymous

        Or Samsung could simply start purchasing Qualcomm modems instead of Broadcom ones (hate to say it, since I have a buddy that works for Broadcom).

        • akhi216

          Qualcomm modems suck. I switched to Motorola because I got tired of the Crapcomm radios in HTC phones.

          • Anonymous

            Motorola generally uses Qualcomm modems, FYI (for CDMA; they make a custom, in-house chip for the LTE modem). Sorry to burst your bubble.

  • This would mean a lot more… if Moto isn’t using a TI chipset in nearly everything they make these days…

    • Anonymous

      Seriously. The majority of Motorola’s Verizon devices have been TI. This is a surprising amount of BS coming from a company Google is going to own soon.

      • Anonymous

        They’re trying to fail as hard as they can before Google steps in and demands they stop.

        • Anonymous


        • Noyfb

          Let’s pray that Google will step in and make Motorola lose blur and other crap on their phones. I’d love to see a Motorola hardware set with pure Vanilla Android. I have a Dream… That one day motorola will have have a Nexus Phone

          • Chad Ramey

            a dream or hallucination

    • Anonymous

      Yes, but the last Nexus phone was a Hummingbird processor. Maybe that’s what they’re talking about.

      If they’re referring to the RAZR, then that makes much less sense, as it and the GNex are TI OMAP4 chipsets.

      • MK17

        If I’m not mistaken, the code has to be leaked or reverse engineered because the company (moto in this case) will not release it to the public. That’s really not a problem for moto….

    • Stephen D

      Exactly what I was going to say. What a BS excuse. The OMAP 4430 and 4460 are literally the exact same, except the GPU and CPU are clocked higher. They take each 4430, and the ones that can handle the higher clockspeed requirements are then labelled as 4460s. 

    • Anonymous

      No kidding, this is total BS from Moto.  

      The reason it takes long is because they want all of their bloatware to work after each build and they have to rework their UI skins each time.  If all of these companies would realize how terrible their UI skins are and how good vanilla Android is, then updates would be quicker.Hardware is always going to be different between devices, because a lot of phone manufacturers make their own chips/radios to create better profit margins for themselves, as well as better compatibility. 

      Moto just needs to stop talking and get back to the drawing board.  If they haven’t figured it out, their last 4-5 phones have been flops.  The Razr Maxx is the only device worth buying out of their entire catalog right now and that’s because it has an amazing battery in it while remaining thin. 

      Stop using terribly designed phones with a terrible UI skin and you’ll gain your following again Moto.

      Here’s a Pro Tip: don’t slam the company who just bought you because you couldn’t stand on your own two feet.

  • Anonymous

    Rrright, nothing to do with all those customized skins.

  • Anonymous

    Dear Motorola,

    Your choice of screen resolution and closed bootloader take the blame for slow Android updates. I mean, still tugging 800 x 480 on RAZR? Come on.

    • Uhh. The DROID RAZR uses qHD (960×540).

    • Anonymous

       Check your facts please. Its qHD.

    • Anonymous

      Razr has Qhd. Come on man know your facts first.

      • angermeans

        its not that much better. The screen on the Razr is garbage

        • Anonymous

          The screen is great on the RAZR. Sure, if you load up a page of static, white text on a black background and look at it from 2″ away it’ll be worse than a GNex with a page of static, white text on a black background from 2″ away, but calling a sAMOLED panel at qHD resolution on a 4.3″ screen “garbage” strongly smacks of fanboism. In real world usage, it’s a complete non-issue.

        • @EMAW_29

          I’m really hoping that’s sarcasm…

        • cantcurecancer

          The RAZR’s screen is garbage, as seen in the picture attached. From top to bottom: Galaxy Nexus, HTC Rezound, Moto Razr. The two people who replied above are just narrow-minded Moto fanboys

        • Anonymous

          The Rzar actually has the best screen of Motorola phones, as it uses the RGBG Super Amoled screen instead of the crappy RGBW used in previous phones including Bionic. The Razr screen is halfway from Galaxy S screen and Galaxy Nexus screen.