Share this Story

Google Issues Statement Regarding CDMA Nexus Devices

We reached out to Google to see if we could get some clarification or reasoning as to why CDMA devices would no longer be “supported” as developer devices and they responded. Dan Morril, an Android engineer who you may be familiar with, provided an explanation at this Google Group’s page:

Hello! This is a quick clarification about support for CDMA devices.

For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called “platform” key. However, when an individual creates a custom build from the AOSP source code, they don’t use the same signing key as these CDMA flies were signed with.

The result is that these files don’t work properly, and pure AOSP builds running on these devices can’t place calls, access mobile data, and so on. Because we aim to make sure that we are as clear as possible about the degree of support that devices have, we updated the docs over at source.android.com to reflect this reality.

We will still make available as many as possible of the closed-source binaries for these devices, and Nexus devices will continue to have unlockable bootloaders. And, of course, GSM/HSPA+ devices are still supported, as are any other devices we’re able to support. We’ve simply updated the documentation to be clearer about the current extent of CDMA support.

We are of course always working to improve support, and we’ll keep everyone updated as we make improvements. Thanks as always for your interest in AOSP!

So basically, CDMA is not widely supported as we mentioned earlier and is also simply a pain in the ass. From what we have been told though, the Galaxy Nexus on Verizon is still a “Nexus” and will continue to be updated in a timely manner, but Google is simply making it clear that a device running a CDMA radio cannot be officially “supported” since its files are signed differently from AOSP code. If that makes any sense.

And devs in the building, please feel free to clarify that further.

  • Mymuzik73

    I emailed google and this is what they sent back to me in a email. Hello! Thank you for writing to us.

    The media reports are confusing our statement about support for CDMA devices. Android and Google will certainly continue to support CDMA devices going forward.

    We have only dropped support for these devices as Android developer phones for Android open source development (ie. for people who want to configure and load their own Android distribution on devices) because they require some closed source modules from the OEM and/or operator. In other words, we just can’t open source all of the code on these devices, but they will certainly be supported and receive updates to new platform releases in future.

    Sorry for the confusion. Please see the updated media reports (http://briefmobile.com/dan-morrill-dont-worry-cdma-nexus-still-supported), and statement from our open source team here: https://groups.google.com/forum/? fromgroups#!topic/android-contrib/phz3S5ZdveU

    Thanks for your interest in Android!

    – The Android Compatibility Team

  • Wmsco51

    I hear all the reasons for why but here is my statement : what happened to stand behind your product and having all your ducks in a row before releasing! Is this the 2012 business policy dump on the customer! In my book, take it off the shelves and offer full rebates or make it right!! And take the faltering party to court for breach of contract or agreement, not dumping on the customer. Is this what we are to expect from major business oops sorry tuff crap but thanks for your money see ya by by now you have a nice day.!? @$%#@$%#

  • Megatron

    I knew this device was going to be a disaster from the hardware to the carrier and now technically isn’t even a real AOSP device……

  • morespeed

    List Anything You Want For Free Here! http://www.monsterrlister.com

  • Anonymous

    Google seriously needs to hire better Public Relations personnel.  

  • I’m going to hold off on being upset over this for now, and see how it plays out. I don’t have the time, nor know how to go the custom ROM route, so that’s not an easy solution for me. Regardless, I have had signal issues, as well as connectivity and battery issues. Not good for my work email, that’s for sure. That being said, if I don’t see 4.0.3 fairly soon, I’m going to be fairly upset. What bothers me about this is that these are not problems I had with my Rezound (yes I understand, new firmware, issues will happen, etc.). I will say though, even with those issues, which can be fixed, I’m loving this thing. I even got over the lack of mass storage quickly, and devs are updating their apps to support 4.0 pretty quickly it seems. Pure ICS is awesome, bottom line..

  • Tam

    Likewise this also seems to be the situation in my place. But unlike the lucky CDMA users we still got our question unanswered. 

    I am from Hong Kong, and I am now using a GSM version of Galaxy Nexus. You should have known not all Galaxy Nexus are created equals. For GSM version we have a “yakju” build which updates are pushed directly from Google. But other builds (like yakjuxw, yakjuzs) aren’t. The Galaxy Nexus in Hong Kong (and Taiwan and some othe replaces) are “yakjuzs” builds.

    We learned that non-yakju builds are not updated by Google but from Samsung, and we need to ask Samsung for the update timeframe. But when we asked Samsung, they clarify that they are not going to update our phone because this is none of their business. They affirm it is Google to update our phone.

    BOTH GOOGLE AND SAMSUNG HAVE DENIED RESPONSIBILITY PUSHING UPDATE TO OUR PHONES. And both party remains complete silence when we ask them to clairfy the matter.

    I can tell you that this is the most terrible Nexus device experience which I never expected to have. The situation now is that we are stilling on 4.0.1 but new phones selling in the retails have 4.0.2 preloaded. And no, we are not asking for an update, we are just asking WHO is responsible to push an update. 

    You may check the unanswered thread right here:

  • iphone 5, here i come. 

    • Adam Brandt

      WOOHOO!!!!!, at least they do what they want and don’t let ANY carrier boss them around

    • Tim242

      You mean 6.

    • Anonymous

      Due for release sometime in 2016. I hear it might even have a 720p display this time. 

  • none

    Probably has a lot to do with CDMA, PCMAG had a really good article about the sick level of control CDMA carriers have and back in early december had an article about how a Nexus can never be a true Nexus phone on CDMA due to carrier involvement. But it probably has a lot to do with Google trying to temper Samsung’s momentum too. A lot of people think Samsung is gaining leverage to eventually make demands on the Android platform due to their success in the market. Finally we have Motorola because in a couple of years (3-4) it will probably get dissolved by Google or become the de facto carrier of the Nexus line since Google will improve integration of the hardware with their own technicians.

    • none

      it would have been nice to get updates before everyone but this was pretty much VZW b*tch slapping us to maintain control on their network. I’m still loving the phone and we have enough devs who know what they are doing. If a dev with a GSM phone gets their hands on that updated phone, guess who will port it over to us CDMA punks weeks and months before Motorola HTC etc. I hate to admit it but I can’t use anything but VZW, they do have the best network. Does being the first to the update mean I have to give up their excellent service? I don’t know. 

      • DBK

        Google will still update the Nexus. They just can’t “officially” support CDMA devices running custom ROMs because their signatures are different from ASOP signatures. This is just a “covering their behinds” thing, so no need to worry.

  • Joe

    HA! +1 for me who went for the GSM vs the el crapo CDMA model.  Verizon sucks my grandma’s b*llz.

    • Adam Brandt

      I envy you, I was SO CLOSE to doing that too, and I payed CASH for the CDMA one.  Blech, I wish I had gone GSM

  • Anonymous

    Carrier phones were obsolete before Android launched.

  • Counsel Dew

    Does this mean Verizon can’t use unsigned telephony binaries? Is rhis why some nexus devices lose the ability to be heard after recieving a call? More info, please….

  • from what i understand this mean google wont provide the updates for the Verizon galaxy nexus anymore. if so i feel like if i bought a touchpad!

    • DBK

      You should really read some of the comments on here. Google will still update the Nexus. They just can’t “officially” support CDMA devices running custom ROMs because their signatures are different from ASOP signatures. This is just a “covering their behinds” things, so no need to worry.

      • Adam Brandt

        People keep saying Google will update the Nexus, but will THEY actually update it THEMSELVES?  Or provide an update to Verizon to mess with and release the Verizon version of Google’s update?  I think THAT is what people aren’t clear about.  In what WAY will Google be updating us?  The same as before, or by handing over to Verizon to do what they want with, and hold onto however long they want for and release months after the GSM and Sprint version with any additional changed and bloat they choose to add?

        • Tim242

          Doesit matter? No.

          • Wmsco51

            Yes it does the reasons many people spent their hard earn money!

          • Tim242

            Updates are updates. Besides, most people bought this phone to install custom roms.

  • Oh well Verizon is out as soon as my contract is done anyway. Only in the CDMA world would some parts of the Nexus become closed source. 

  • Harryballs1234

    Being a Droid RAZR MAXX owner I don’t understand…. Why do you need updates from Google when you have all these Devs creating custom roms?

    • DBK

      Because the devs can’t update their ROMs without getting the OS update from google first (many times via a leak of some sort).

  • Anonymous

    It is so funny watching all the GNex users loose their minds over this. All the non-nexus vzw people can just sit back and laugh.

    • Anonymous

      Laugh while you are still on gingerbread while the rest of the GNex users are enjoying ICS and will be enjoying the next version of Android while your phone will be just getting ICS 🙂

      • Jack Holt

        Amen to that. People can hate, but Ice Cream Sandwich, is still amazing. The Gnex has decent hardware with the latest and greatest. The phone will see updates quicker than that of the Maxx, Rezound and so on. Custom Rom development will still be strong. We will just appreciate this more as devs will work their asses more to keep our phones top notch. 

      • none

        Actually the next version of android will be on a different phone before it hits the GNEX. Don’t forget about money and politics. We were just the first suckers to ICS. And we will be the last of the nexus line. But the phone is decent and the devs are great. Eventually Motorola will become Googled and just have the dev phone on lock, although I can’t see how VZW won’t b*tch slap us again

    • Harryballs1234

      Yeah, it would suck to no longer get updates AND have a crappy phone…..

      • ILuvSoPA

        It was a crappy phone before this.. How has it changed any? ICS = Lipstick & Samsung Nexus = Pig.

        • Anonymous


          • ILuvSoPA


          • Anonymous

            you’re still here why?

  • David Verba

    Well if they aren’t going to support this device, I’m getting an iphone just to spite these d*psh*ts

    • DBK

      They will still provide updates, so no need to do anything drastic.

    • Anonymous

      I would rather have a G1 one than any iPhone. 

      • Zachary Stern

        Then you’re an idiot?

  • James

     So no one on VZW has a Nexus phone. I see.

    • You clearly are completely lost or just do not know what you’re talking about.

      • ReallyNow

        You got trolled too, haha.

    • angermeans


      • TheObvious


  • Rizheno

    This whole this is being blown way, way out of proportion. It means absolutely nothing to anyone except developers who build from source; and odds are it hardly affects them either. It basically just means that the *.apk files needed for voice and data have to go through Verizon. I think it is also safe to assume that these *.apk files aren’t going to change from 4.02 to 4.03 or even 4.6 for that matter. It might slow developers down by a little bit in the case of an extreme android update (such as gingerbread to ics), but I think it’s safe to assume it will hardly be a hiccup.

  • Coach

    +Google owns +Motorola which makes CDMA radios. will Google alienate its own mobile division? makes no sense unless this is a sign of the future in which Motorola CDMA phones will be the ONLY ones with Google’s AOSP stamp of approval.

    • Tim242

      Motorola does not make CDMA radios
      That would be Qualcom.

  • The scariest thing about this statement, IMO, is the extrapolated possibility (though perhaps not probability) that we won’t see another VZW Nexus device anytime soon.

    • angermeans

      This is exactly the one thing that I am worried about. Then again the whole Galaxy Nexus release has made me feel that this will be the first and last true Nexus device on Verizon Wireless and that makes me sad. I won’t buy another device that runs a horrid and buggy skin no matter what. 

      • ILuvSoPA

        Soon all Vzw phones will be VoLTE and none of this will matter.

      • Adam Brandt

        Amen, I won’t either…Have you seen how cluttered Sense 4.0 is on ICS?  A shame.  What is wrong with a simple, elegent design which retains all the functionality and performance one needs.  Why does HTC and others HAVE to bog down the CPU with their useless skins.  If I can’t get a pure device with an unlocked bootloader again, this will be the last Android phone I own

  • Guest

    Updayes so dast we still dont have an offical 4.0.3…..

  • Yellowcanary73

    So now I have to wait for Verizon to put out the update.The main reason I bought this phone was that the update would come from google which would be quicker if i would have known would have just went with the Razor better quality better radio.I think after this phone I’m done with anything google or android.

    • Mike McCrary

      Read again. Google has explicitly stated that they will still be pushing updates to the Verizon Galaxy Nexus. 

    • Tim242

      You need to read. Google is still providing updates. The Razr does not have a better radio. I had both the Razr and Nexus for two days to compare them. In my house, the Razr had 4 out of 5 bars, the Nexus 2 out of 5. Diving into the settings, they both showed -93 dBm. That means the Razr just has inflated signal bars.

      • Anonymous

        Where has Google said it is still providing updates to users of the Galaxy Nexus LTE? That has not been mentioned by Google yet from what I can see.  Did another Google employee post it, if so where?

        Would be interesting to see since this is a similar situation as the original Droid and it got updates from VZW and not from Google like the Nexus One at the time.

        • Tim242

          The original Droid was not a Nexus. Here’s where Google says they will still provide updates. http://mobile.theverge.com/2012/2/3/2769480/verizon-galaxy-nexus-removed-from-googles-developer-support-pages

          • Anonymous

            And all other Nexus phones are dev phones so it really doesn’t matter what you, I or some website says.

            The link the verge provides is the same quoted post as above. The linked google post has no mention of Google stating that it will be pushing updates to end users of the GNex LTE. 

          • Tim242

            You didn’t read it all. They said that Google reached out to them and said they will still be supporting it with updates. It is in update 2. Here is the copied text.
            Update 2: Google has reached out again to say that it incorrectly responded to our initial request for comment — this has nothing to do with Google Wallet, and furthermore, the company will continue to support the Verizon Galaxy Nexus through official firmware updates. Disaster averted.
            On Feb 3, 2012 7:08 PM, “Disqus”

          • Anonymous

            That is just hearsay then?  Why would they tell The Verge that but no other website or mention it on the Google post?

            Google does have 4.0.4 for Sprint coming out soon since it was leaked a few days ago so maybe it will be the same as the GNex LTE. Google will push it but may come after the GSM phones.

          • Tim242

            Dude, the changes only affect the dialer apk of the phone. It has been blown way out of proportion. Here’s a good explanation. Be sure to read the comments. Jerry gives more insight there. http://m.androidcentral.com/verizon-galaxy-nexus-support-not-dropped-after-all

          • Anonymous

            It is more than just the dialer. Do you build ROMs? If so look in your vendor or device folder depending on how you have your source set up and see how many files are needed for the LTE build. The keys are mis-matched already and things work. That’s how we are able to build ROMs with working radio and verizon framework so apps made just for Verizon work.

            The code for CDMA dialing does not come from the phone.apk directly.  It is the same phone package across GSM and CDMA devices and it is the proprietary files that make the dialing work.

            When you pull the files from the phone the signature stays intact which is the verizon signature. Then when you build, the proprietary files retain the same verizon signature since the prebuilt files are not signed.

            The only time the signature would come into play is if there was an update from market for one of the proprietary files, you would get a signature mismatch error but that would never happen because those files would be pushed via OTA.

            What Google is saying is not entirely true and there has to be more to this.

            It’s what I said before in another post. Verizon and Sprint do not want to open their code for the CDMA bits.  Which makes no sense at all cause if someone wants them then they can just decompile the APK files a certain way to get to the source.

          • Tim242

            At least you understand it’s about minor things, and Google is not abandoning us.

          • Tim242

            Btw, the Sprint Nexus is no longer in there either. But, as pointed out, none of this means a thing.

    • none

      try the iphone, no lie. That phone is sweet

  • Anonymous

    so basically we have to wait on verizon to sign the radios specially we can’t get updates as fast as gsm phones?

    • Madcow06

       That has always been the case since the gnex came out on verizon.

  • Davidgg72

    iphone here i come. Whuh google has to screw up something good is beyond me. Just when i thought i had a great phone.

    • Anonymous

      Google isn’t screwing it up. VZW will be the problem if there proves to be one. Enjoy your “open” iPhon’t. Might want to buy a magnifying glass for the screen while you’re at it.

  • Jeff

    So basically we are screwed and at the mercy of Verizon to update our Nexus phone unless we root and load custom ROMS….

    So what has changed????

    • no! Google will update our phones still. There are just certain things we can’t have because they aren’t signed by Verizon(ex. google wallet). so “full support” is not there. Everything is still fine

  • Anonymous

    “Google is simply making it clear that a device running a CDMA radio cannot be officially “supported” since its files are signed differently from AOSP code. If that makes any sense.”

    Does not make sense to me at least, the files they are talking about do work with the AOSP signature and that’s why we can have working ROMs now.

    Wish companies could just be straight and tell us what exactly is going on…

    Them saying we will provide updates in a timely manner can mean so many different things.

    Push the updates to users or CDMA providers in a timely manner? They can push the CDMA providers the same time they push to GSM devices and then it will be up to the CDMA providers to push the updates to users.


    The CDMA providers push their files to Google and hopefully Google does not have their own updates delayed because of it.

  • as i non-developer i read it like this, and hopefully somebody can say if i got it right:

    It says that since AOSP(Android Open Source Project) can’t give devs the verizon-signed CDMA .apk file, they can’t claim that the VZW GN is a developer device, since if one were to get all source code from the AOSP site and built a ROM from it, it would be unable to make phone calls. it makes no mention of support or updates in general, and is solely related to development within the AOSP. anything beyond that goes far past speculation.devs, how did i do?

    • Peter Kelly

      I THINK this is right, but since I’m not a lawyer, I won’t make any claims to validity (or any guarantees).

      If I had to guess, I think it’s along the same lines that linux users who have an NVIDIA video card complain about using NVIDIA compiled binaries linked into the kernel.  “ZOMG, it’s not really open source!”.  Meh.  It always works.  NVIDIA keeps the binaries updated.  If VZW pisses me off too much, there are plenty of of options.  

      The only requirement is the ability to use
      fastboot oem unlock

      After that, it’s all good.

  • Clarkkent434

    So the Verizon Galaxy Nexus will be last one probably on Verizon and probably Sprint.. 

  • Vaporware

    What this all means is that when Google has an update ready to roll out they will provide the update to Samsung and/or Verizon and they will then be responsible for adding the necessary files and then push out said update. In others words the future updates for the Verizon Galaxy Nexus will be made available when Verizon and/or Samsung is ready to roll them out and not a minute sooner.

    • that’s not what it means at all. it means when you personally get the source to build a rom, you can’t get the cdma apk from the android website. that’s it.

      • Scott Hartman

        I think Kevan has nailed it. AOSP is (by definition) open source, and those files aren’t, so Google can’t distribute them. A developer can (and many probably will) get those proprietary files…say from their own phones. You just aren’t going to get them from Google’s developer page.

        This has no material impact on official updates – at least, no new impact.

        • Anonymous

          Google did distribute them and their explanation of signature is not holding up since the files are working…

  • Anonymous

    So.. this will be the first and last nexus device on Verizon then. Theyre a bunch of @ssholes.

  • Charlie

    So Verizon still has to sign off on the Gnex updates just like any other phone.  Thanks, that clears things up.

    • Tim242

      That has always been the case…on all carrier Nexus phones.

    • Anonymous

      They always did, however this appears to mean that Google has to write a version of android (4.0.4, for example), send it to Verizon to add in the CDMA radio apks, then Verizon has to test it, then Google releases it.  It’s my understanding that this was all true before barring the  fact that Verizon had to add their files to it for it to be a complete build.

      On a separate rant, I still think this is totally unacceptable.  Am I the only one that still feels like I got screwed by both Verizon AND Google?  

      “Here’s a banana for all you banana lovers out there!  We know you’ve been waiting a long time for a banana, and all your friends have bananas…so now it’s your turn!  It’ll only cost you $299 and a 2 year commitment…Great!  Now that you’ve bought that awesome banana, we have to mention that you can’t peel the banana unless you get a special tool from the banana tool people…sorry!  We have no control over that!”

  • i would agree with that

  • Russell Holly

    “Insensibly one begins to twist facts to suit theories, instead of theories to suit facts”

  • ddevito

    His explanation is as clear as mud. It doesn’t answer the question of whether or not ROM devs will be able to use the source as quickly as they’ve been.

    I’d like a ROM dev’s take on this.

  • Anonymous

    I don’t quite get this. Haven’t numerous devs over at XDA made custom ROMs based on AOSP?

    • Anonymous

      Thats because the files that are Verizon files are copied from phone to the source….Google use to supply most of them but not all.

  • Cutillo


  • Anonymous

    When you download the AOSP code it does not come with any drivers needed for for GSM and/or CDMA phones.

    You get these drivers by running a script with your phone attached to USB or by downloading them from Google.

    For the CDMA devices Google had most of the drivers there and for GSM devices I believe they were all there.  I usually ran the script and pulled the files from the phone.

    So once the the files are in place and your build your ROM the prebuilt APK files get transferred over into the build.
    After reading this I believe they are not signed so the original signature is still in tact.  At first I thought they would be signed so it did not create any conflicts with the other APK files.  That’s why I am sort of confused now.

    So what this whole thing basically means is Google is not releasing the source for CDMA devices which means that it will be up to the CDMA carriers to issue updates since they need to add in their own files.  Like what Moto adds to their source but a whole let less.  So now Verizon is directly involved in future updates.

    Sounds like Verizon did not want to hand over code for their own crap.

    • That is a scary conclusion. 🙁

      • Jim McClain

        hear anything on the updates for gnex, hope they can fix this awfull speaker,camera and redios

        • DroidzFX

      • Anonymous

        I am still scratching my head about this. 

        If files pulled from phone are not signed during the build process I would have guessed that the different signatures would cause some sort of conflict when certain apk files needed to interact with each other.Google is saying that Verizon uses it own keys to sign the files which will cause conflicts because it is different than the public key which is used in AOSP.

        So if building a ROM does not sign the prop files then the signatures do not match.

        If the prop files are signed then the signature matches but Google claims the prop files will not work.

        I guess I can just compare the signatures before and after build to see what is going on.

        I am still new at developing so maybe another dev can chime in since most of my info can be wrong 😀

        • Guest

          I think that all the *.apk files needed are unsigned and residing in /system where nothing is signed.

          • Adrynalyne

            Everything is signed, my friend.  Everything.

          • Rizheno

            Are there different signatures at different levels? I can decompile, recompile and push any /system/app app without signing them, but I have to use the test keys for any app in /data/app.

          • Adrynalyne

            You can keep signatures intact when you modify an apk.  Anything that has a Meta-INF folder in it is signed.  There are four signing keys in a rom actually.  For aosp, its testkey, platform, media, and shared.

          • Rizheno

            Ah.. I totally forgot about the meta-inf folder and the fact that it never gets touched. I didn’t know about the other keys, either, but I just recently started dabbling in android development. Thanks for the info!

          • Adrynalyne

            Any time 🙂

        • Adrynalyne

          The only apk I know of that will not work with AOSP using the oem signatures (which are Google, NOT Verizon) is rtn.apk.  Signing it with aosp keys will allow it to work.  I have not checked the others, because they aren’t of interest to me or anyone else on aosp.  Either way, none of them affect getting data or making calls.  In fact, no proprietary apk is needed at all for aosp.

      • Anonymous

        Well the signature of the apk files that Google mentioned are the same before and after build.  The “special” apk files are pulled from Galaxy Nexus LTE so they must be signed from Verizon which is obviously working with AOSP builds. So I am not sure what they are trying to say now and will just shut up till someone with more knowledge comes a long cause I am confused as f*ck and just going back to building…Everything works for now so who cares…

        But I am willing to bet that Verizon is now involved with the updates since they would have to push their “special” files to Google and that Verizon is not willing to place their code out in the open.

    • DroidzFX

      so basically your saying Google just got Verizon’d   

      I see..

      • Tim242

        Really? Explain the Sprint Nexus.

        • Joe

           I’d rather not acknowledge it’s existence.  about as pointless as explaining your dad’s third testicle.

    • Tim242

      Really? Explain the Sprint Nexus.

    • i don’t see how verizon would need to be involved in future updates the way you’re implying. this is simply about AOSP, meaning the builds you or i make, it says nothing about official android builds,which would be coming from google, who i’m pretty sure VZW would give their signed APK to. just because it requires a file from verizon, i don’t see that as saying they have to hand the build over to VZW so they can tweak it and take months to send it out, i think they’re just saying that android phones with CDMA radios need a proprietary file, and since it’s proprietary, they can’t offer it in the AOSP source. if it were true that the build had to be approved by VZW first before it could recieve the signed apk (as opposed to VZW giving it to google, just not making it open souce), i don’t see how the development of ICS and GN would have worked at all since they would have built the entire thing without voice or data coverage on the phone, until VZW gave the thumbs up. think of how tedious that would be.

      • Anonymous

        They also said that the signature would not work with AOSP files and that is not true either.

        It’s not just one file, it is about 40 of them and 7 of them being APK files.

        • but does this have anything to do with OTA updates, which is what i believe most people are freaking out about? believe me, i’m not saying that it does not make it more difficult for people to use build fully functional ROMs. i just don’t see how this affects anything outside of the AOSP, especially consumer updates.

          • Anonymous

            I guess we can wait and see.  It can go either way.  This whole thing is strange. The way it was worded is very strange and to say the signature will not work with AOSP builds is almost an outright lie.  We all know it does work with the AOSP builds.  If it did not then we would not have working ROMs.

            Google, Verzion and any other manufacture build ROMs the same way we do.  They get the source, setup their vendor folder with the changes and build. I wish I had their machines though 🙂

            If the real issue was the whole signature thing then why not just ask Verizon to sign with public key?  What are they really protecting?

            The only time the signature will most likely come into play is if one of the APK files needed to be updated from market but that would never happen and would be pushed with an OTA.

            I am glad that I left Verizon many months back.  There is always some sort of BS going on with them.  Like how Moto and Verizon always go back and fourth about who is to blame for locked bootloaders and now this.

          • Anonymous

            in the past Google only pushed updates to developer phones too.  The original Droid got it updates from Verizon and it was not an official dev phone but ran AOSP. So who knows.

    • Anonymous

      Not quite. Nothing has changed except the documentation. I compiled a source built AOSP ROM over a month ago and it worked great but the cellular radio did not work. Proprietary drivers are needed as they always have been.

      • Anonymous

        Exactly.  At one point Google did provide most of the drivers but not all of them.  If you ran the script to extract the files from your phone or downloaded the proprietary drivers than you would have had a working Radio.

        That’s the whole issue here with me, Google claims the signature will not work with AOSP but they do.

    • Adam Brandt

      sounds about right, F EN Verizon

  • Anonymous

    I didn’t understand any of that. Not even ashamed to admit it.

  • can I join the CDMA hate? 😀

  • I am running a rom on my Galaxy Nexus and it is working just fine.  I can access everything and even use NFL mobile.  I also get much better battery life using this rom.

    • Anonymous

       Which ROM?

  • Scott

    Can someone explain this in idiot terms please?  In other words, will my stock 4.0.2 Nexus be trapped on 4.0.2 forever?

    • Anonymous

       “will my stock 4.0.2 Nexus be trapped on 4.0.2 forever”


    • Bionicman

      it may mean that it may be stuck on 4.0.2 for a long time but eventually will be updated, but i hope that’s just my pessimism..

  • Anonymous

    “The result is that these files don’t work properly, and pure AOSP builds running on these devices can’t place calls, access mobile data, and so on.”
    Except I made a pure AOSP build with files extracted from my phone and it worked perfectly fine. Does this just mean that the files I extracted aren’t ever going to be in the AOSP tree, like they are for GSM devices?
    Obviously, if you’re making builds for a device, you should probably own the device, and I don’t think proprietary binaries should be in AOSP in the first place.

  • Anonymous

    Not sure where you’re getting this from, Kellex…. ”
    The Galaxy Nexus on Verizon is still a “Nexus” and will continue to be updated in a timely manor…”

    I didn’t read that from Morrill’s post.  Hope I’m wrong, but he didn’t seem to confirm or deny that speculation.  You should ask for confirmation on that directly from Morrill.

    I read that to mean there is proprietary code regarding CDMA tech that must be provided by the carriers on Android 4.0 devices.  This would mean that it falls back to the carriers to tweak the device ROMs and include their proprietary code, and push out updates.  <- Really hope I'm wrong about this.

    • Was told that separately from Google.

      • Anonymous

        Yep, and I see TheVerge confirmed the same. Much ado about nothing (thank god).
        “Update 2: Google has reached out again to say that it incorrectly responded to our initial request for comment — this has nothing to do with Google Wallet, and furthermore, the company will continue to support the Verizon Galaxy Nexus through official firmware updates. Disaster averted. ”

        • Anonymous

          The Verge’s journalistic malpractice on that original article is absolutely shameful.

          • Anonymous

            Agreed.  I zinged Ziegler for X-ing out the whole damned article.

      • Philip A. Kaiser

        While the original Droid was never meant to be as open as it became, it happened nonetheless. Google, Motorola, Verizon, none of these guys made it the legend that it became. It was the homegrown developers, rommers, themers and ameteur programmers that gave the Droid a life that lasted far longer than anyone could have possibly dreamed. Whatever happens in these next few weeks, I really don’t care. I know there are teams of programmers that will always be hell bent on getting us every single morsel we desire. The Gnex has become the new D1 and it isn’t going anywhere.

        Don’t forget to donate!

    • Anonymous

      This just means that you cannot go to the AOSP and build for the CDMA devices directly from source and have it work since the required binaries would be missing as they can’t be signed to match.  This doesn’t prevent Verizon from sending the officially files to Google to sign with the build so they work with the official build Google will make to release.  

    • Doug Wing

      From p3Droid (who I think we all know is right in the mix of things):

      It is about the pure AOSP build, when you build pure aosp you don’t have data/cell you have to copy the binaries from your build to get it to work properly therefore they (Google) are saying its not a pure AOSP because you can’t build and go



  • Anonymous

    Still don’t regret buying it.

  • Daniel Rose

    So basically, the real story is that Google noticed only recently that their AOSP builds for CDMA phones won’t work.

    • Anonymous

      They work if done properly and I am still confused about this statement…

  • Geoh711

    So … no worries?

  • Anonymous

    While we may still have a “Nexus” device it’s been almost 2 months since release and we have yet to see any official updates. 

    • Mike McCrary

      You’re forgetting the update to 4.0.2 that we got at least a full month BEFORE the GSM model. 

  • “CDMA is ancient tech” – Nowhere is that implied in Morril’s statement.

    • That’s just me hating on CDMA. Corrected. 😛

      • Tim242

        Hate on CDMA if you must. But, quality-wise, it’s much better than GSM. CDMA travels further, penetrates buildings better, has higher capacity, has better hand off, and provides better call clarity. There’s a reason Verizon and Sprint get best quality and fewest dropped calls…CDMA.

        • Daniel

          Please, we all know CDMA to LTE isn’t possible as hand off.

          If its on a lower frequency, GSM will go through walls, that’s why LTE is so wide, because it’s on a low frequency.

          Low quality is due to AT&T or the phone, I have a a GSM iPhone 4S and it’s clear.

          • Tim242

            ummm my Nexus hands off from CDMA to LTE just fine. CDMA towers cover an 8-10 mile radius. GSM only 1-4. That is why it takes so many more GSM towers to cover an area. CDMA holds 50 calls per channel, GSM only 6. That’s one of the reasons for dropped calls and busy circuits.

          • LTE covers much more, and uses GSM.

          • Tim242

            LTE is not GSM. You should really do your research. HSPA is not even GSM.

          • Tim242

            Have a read. This explains how LTE is not GSM. http://db.tt/QA6UX75C

      • I’ll take Verizon’s call quality over that which I had on AT&T any day, but that’s just me.

  • Anonymous

    So they aren’t supporting it because developers can make a rom that won’t work properly? Well that makes no sense considering the majority of users aren’t rooted. What an I missing?

  • So basically nexus devices limited to a certain carrier will have less support than the ones able to support multiple carriers? I think.. this seems fairly reasonable i suppose…

  • But once all phones migrate to LTE and away from 3G CDMA, it won’t matter for future devices… will it?

    • Anonymous

      That should be how everything goes down.

  • developers gonna develop

  • actually, CDMA is newer than GSM.  

    • Daniel

      HSPA is newer then EVDO

      • John Jones

        NSYNC is newer than NKOTB

        • DroidzFX

          Google got CDMA’d

          actually I think CDMA just got Google’d

          • Anonymous

            LTE  got MILF’d

        • OreoMan

          Boyz to Men is still making money and Bobby Brown is not!!

      • Anonymous

        SMFD is my favorite pastime.

    • Anonymous

      And W-CDMA (3G GSM standard, aka UMTS and now built into HSPA – GSM, of course, referring to the standards setting association and not the technology that was left to die on the vine at EDGE) is newer than CDMA… and yet, all are being replaced by LTE… making 2G GSM, UMTS and CDMA2000 all ancient, by technology standards.

      • Too… many… acronyms!

        Seriously though, this doesn’t really change anything. Updates don’t come directly from Google; they come from Verizon. Google gives Verizon the update, Verizon tweaks it a bit, Google quality checks it, and it gets pushed out. Honestly, it’s never been a real Nexus, but it’s pretty damn close.

        • Cody Walton

          I wonder if this will affect the frequency and speed of the updates though.  Or if they’ll now come with Verizon bloat….

  • Tim242


    Google says they will still support the Verizon Nexus with updates.

    I told you people you were just being drama queens. : )

    • Michael Forte

      Ahh good. Not that I don’t run custom ROMs anyways, but for anyone that doesn’t, the whole point of the Nexus was that it received updates directly from Google and if that were to be taken away, I’m sure Google and Verizon would hear an earful.

      • Anonymous

        I suspect that’s not the point and most users don’t care or have any idea

        • Anonymous

          Most users of a nexus bought it because it was a nexus, including updates from Google!

          • Blootzm3

            exactly, thats what i got it for. have been waiting for it for years. as was the majority, especialy since it wasn’t advertised anyway. so the majority that even new about it got it for that exact reason. otter34 doesnot know what he is talking about.

          • Anonymous

            No. Most users, that is the average user bought it because they like the look and feel of it, performance, etc. Outside of some in this forum nobody cares if says nexus or yomama and could care less about direct updates from Google.

          • surely you are incorrect, if average users were to go for feel of a phone they wouldv’e picked the Razr, as for performance they would’ve picked the Rezound (and Beats because most average users dont know that you can do that with DSP), however most Nexus users bought the device because it was a developer phone or had vanilla android on it no lame skins.

          • Anonymous

            you couldn’t be more wrong.

          • Gaznox

            The majority of people bought the phone because of the marketing and how the employees up-sold it as the best phone on the market.

        • iMiNrU

          lol agreed…only the rooting community knows what the meaning of a nexus device is…Majority of sales came because of big beautiful screen

    • To Tim242, Thanks for everything, Julie Newmar.

      • Tim242

        Haha I love that movie.

        • I’m always amazed that Patrick Swayze was in that movie.

      • Kaliboyred1

        You made me fall out of my chair laughing with this one!! Great post!!

    • SomeDude

      But what about custom ROMs. Especially AOSP based ones. Aren’t those the more affected by all of this?

      • Tim242

        Not really. They can easily pull what they need from the phone, as most already do.

      • Luis

        No CM for you!

        • Joe


  • Anonymous


  • Anonymous

    So all that was for nothing?

  • Michael Forte

    This is still unclear whether or not updates for the Verizon Galaxy Nexus will come from Google or not. It makes it seem like they won’t, since CDMA devices aren’t officially supported…

    • Anonymous

      And to be honest I would have expected an update by now which we have not seen. My Droid 1 received an official update in December about a month after release.

      • Daniel Rose

        You are as up to date with a Verizon GN as everyone else. 4.0.2 is the official version for all Galaxy Nexus at the moment.

        • Anonymous

          I know, but that’s not what I meant. I think Nexus phones should get little updates here and there as they make improvements. This phone is awesome but it did release with some issues. I would like to see frequent updates.

      • alex drum

        us not seeing an update has nothing to do with the radio of the verizon nexus.  if it did the gsm/hspa+ model would have had an update, but both phones are running 4.0.2

    • Dave

      Judging by the description as to why, it sounds like they will still come from google, they however, have to include a key to some CDMA specific code that they don’t control, so they support it operating system wise, but in terms of the actual CDMA chips, it’s not in their court, so they don’t control it, so they can’t say they officially support it, since they can’t change it.

      • Adam Brandt

        so will they ever release new radio firmware?

  • Sounds like somebody isn’t willing to pony up some source code for some CDMA radio stuff. *glares at Qualcomm*

  • No offense but, HYPEBEASTIN’ TROLL!