yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] player911:
That doesn't say anything positive other then the telephony apks require to be signed by the carriers and won't work properly otherwise. Like said above, what the hell have they been doing the in the past with AOSP roms then? I'm on a AOSP 4.0.3 Toro rom now and my telephony is working fine.

I just don't get their motives. Sounds like garbage to me.

LTE EX Galaxy Nexus - 4.0.3 AOSP

Asus Transformer - Revolver OC/UV
[Samsung Galaxy Nexus] adrynalyne:
Lets just hope they misworded their explanation. Because right now, its bull****.
[Samsung Galaxy Nexus] TiltedAz:
I didn't read the previous 100 or so posts but to me it seems Google isn't dropping the ball since ICS was intended to be device independent from the get-go.

I guess it will put the burden on phone manufacturers and gawd knows they're more interested in designing the next phone design than supporting current devices.
[Samsung Galaxy Nexus] davidjcoburn:
Dev's don't actually sign the custom ROM's with actual production keys. To load the ROM's that they make we have to use a unlocked rooted phone to do so. If the DEV's here wanted to build a ROM for users who don't want to unlock... well that won't work, for many reason besides CMDA .APK's....
[Samsung Galaxy Nexus] adrynalyne:
Installing on Unlocked devices is 110% irrelevant to this discussion.

This is about aosp and CDMA. It isn't even specific to the Galaxy Nexus.
[Samsung Galaxy Nexus] arirang:
Nexus brand cache:

Before 2/3/2012=In Google We Trust

After 2/3/2012=Troll Bait

What a PR disaster! Cult of Mac will be rubbing this in with every future Nexus release.
[Samsung Galaxy Nexus] MMcCraryNJ:
Jerry Hildenbrand over at AndroidCentral.com explained it pretty well and then elaborated on it a bit more here http://www.androidcentral.com/verizon-galaxy-nexus-support-not-dropped-after-all

I'll post his other comments here in case you guys don't wanna scroll through the comments to look for them:

And in responding to a Nexus S 4G user:
[Samsung Galaxy Nexus] adrynalyne:
Let me explain why that is crap.

You can take oem signed proprietaries right now (libs and bins), and add them in a vendor to aosp.

With a good machine, you can have built, flashed, and be making and taking calls along with data in 20 minutes.

So many people talking like they are in the know, but haven't built one aosp rom to know what they are talking about.

If this is an issue with Google not being able to secure a license distribute cdma proprietaries like GSM, I get it. Thats fine. But do not concoct some **** and bull story about not being able to get data or make calls without correct signing.

The only thing that needs to be signed at this time for 100% working CDMA aosp build is GoogleBackupTransport.apk. The reason for this is for APP RESTORE. Not one proprietary APK is needed, even though the vendor setup copies some from your phone when you use extract-files.sh. Those can ALL be deleted, and you will still have data and voice.

Their explanation was a lie or gross exaggeration. So do I trust them to tell me that they are JUST updating documentation? No I do not.
[Samsung Galaxy Nexus] player911:
Well apple has always had this one in the bag when it comes to streamlining their stuff. Although they can do this because they don't release source thus don't worry about proprietary sources being released.

Android is sweet but I'm starting to wonder whose driving the bus anymore.

I was always a GSM fan but work pays for a Verizon phone. So to save some bucks every month I jumped on the Nexus thinking Verizon wouldn't have its dirty hands all up in my stuff. I was leery and now this happens.

But at the end of the day the Nexus is amazing. Its 1am and have 23% battery left off 9am charge. Plus work pays the bill so its free to me. I guess I can't really complain. Even if we don't get frequent AOSP builds, I know the community will port over whatever the GSM variant pulls in. So at the end of the day it isn't a huge set back, more of a kick to the balls.

Seriously Google, just go back to having HTC build the latest and greatest and sell it yourself. First year had "low numbers" but now Nexus is a household name (IMO). There should be no reason why you can't sell it yourself and push code all day long. Straight and narrow and if carriers want a piece of the action they will conform. Look what sprint pulled just to sell iPhones. $$$. Hell MIUI is even doing this (on a smaller scale).

LTE EX Galaxy Nexus - 4.0.3 AOSP

Asus Transformer - Revolver OC/UV
[Samsung Galaxy Nexus] tannor:
I am with adrynalyne,

I compiled and built 4.0.3 and was able to have data/cell service without doing anything special (no signing or anything), only thing I was missing was the proprietary drivers from samsung for the camera/gps.

So the explanation makes no sense to me.
[Samsung Galaxy Nexus] sirgoob:
I'm upset with Google, not Verizon and just switched from Tmo to Verizon. I'm going back to my N1, screw this piece of junk, its for sale
[Samsung Galaxy Nexus] lrs421:
Give it a few days, who knows what may happen in the next week. Are you a dev? Do you compile from source? Just trying to understand what about it annoys you so much.

For me, it just feels like I purchased a nexus that's not really a nexus. The lack of Google wallet without a hack hinted at it but this latest move pretty much confirms it. There's really no other device and service out there that compels me enough to switch though. I'm annoyed at Android in general.
[Samsung Galaxy Nexus] @rbiter:
GSM ftw.

Sent from my Nexus in Texas.
[Samsung Galaxy Nexus] adrynalyne:
Helpful. Really.
[Samsung Galaxy Nexus] afma_afma:
I am so pissed about this and planning to dump android forever.....planning to move on to iPhone...
[Samsung Galaxy Nexus] Skrazz:
They're sweeping this device under the rug for the real GNex with the better GPU. Relax ;-)
[Samsung Galaxy Nexus] afma_afma:
@skrazz ...u relax...lol

at least for iPhone the updates are streamlined.... every carrier phone is treated equal.
[Samsung Galaxy Nexus] cam30era:
Thank you for your no BS explanation. So, what does this mean to the end user who has unlocked the bootloader, rooted, and running a custom ROM?
[Samsung Galaxy Nexus] psychoace:
To bad each updates sucks as much as the last one. If you look at donut and then look at ice cream its a completely different os. Now look at what the iphone had 2 years ago and what they have today and you won't see much of a difference. The iPhone upgrades are minor to say the least
[Samsung Galaxy Nexus] sirgoob:
The phone in general. The battery life, the camera quality sucks, the so called 720p display. There are some nice features, but really not enough to justify using. Google will still release source updates, but this phone has too much negative about it .
[Samsung Galaxy Nexus] droiddog:
When Verizon goes lte for calls, will we still need those types of files signed?

Btw, I know this isn't happening for a few years.
[Samsung Galaxy Nexus] Stadsport:
So why not sell your phone?
[Samsung Galaxy Nexus] adrynalyne:
No files have needed to be re-signed so far for it. So we shall see in a few years.
[Samsung Galaxy Nexus] adrynalyne:
Because its more sensationalist to post hate.
[Samsung Galaxy Nexus] Jameslepable:
You guys need to chill out, google is still going to update the cdma version, it's just not going to be considered a reference phone that's all, nothing is going to change one single bit.
[Samsung Galaxy Nexus] adrynalyne:
So all those folks in other countries in the same situation with Wallet don't really have a Nexus either?

:confused
[Samsung Galaxy Nexus] adrynalyne:
Spreading rumors seems to be an XDA pastime.
[Samsung Galaxy Nexus] adrynalyne:
Nothing..at this time.

The future may hold some rather nasty surprises though.

At best, things continue as they have, with them not giving us any props, except maybe for graphics. Even if they don't, this is fine because we can use the Maguro graphics props with some slight .mk file modifications. It will be up to us to get the props for cdma/lte. This really doesn't change how it was handled in the past for cdma and aosp (Hence extract-files.sh is still on aosp). This COULD mean that cdma development could slow some, but will not stop.

At worst, they remove all LTE and CDMA support from telephony in aosp, and we are left with hacked garbage. If they close the source on CDMA and LTE, this WILL happen. This is a fear I have.
[Samsung Galaxy Nexus] afma_afma:
+1 ..same here....
[Samsung Galaxy Nexus] adrynalyne:
You clearly aren't a dev.

There is a real fear here. Especially when the explanation doesn't make any sense. I agree, don't sweat ota support from Google.

But folks working with aosp, should be concerned.
[Samsung Galaxy Nexus] lrs421:
I see what you're saying and I agree with your statements but when I look at this latest move combined with Verizon branding, Verizon apps and Google wallet that's the feeling I get.

I do have a question for you though. What do you feel is the real motivation behind this move? You seem to be one of the few who truly understands these devices.
[Samsung Galaxy Nexus] adrynalyne:
I am honestly not sure what to think. JBQ isn't responding to my tweets, and Dan Morrill's statement is the only thing out there to go by.

Some weeks ago (feels like months), JBQ posted proprietaries for our phones, Maguro, and Toro. The problem immediately arose that CDMA props were missing. There were many queries, and it boiled down to JBQ telling us via twitter that he was trying to negotiate/find a way to distribute the proprietaries to us, but it was taking some time. Remember, Google has to play by the rules, and follow all laws and restrictions a license carries with it.

Well, they never got posted. We made it work with 4.0.2 props, and/or leaked 4.0.3 props that folks got their hands on. This is where we stand now.

My thought and hope is that there was simply no way for Google to procure a way to distribute the proprietaries. If thats the case, I expected it, because if it was going to happen, it would have happened a while ago. This leaves Google in a precarious situation. Their instructions to build an aosp rom simply will not leave you with a working phone if you are CDMA/LTE. Hence, they yanked official support.

This in itself is fine with me. In the past, cdma users always had to use extract-files.sh to get their proprietaries (which is allowed by license). However, Mr. Morrill's explanation that there is a signing issue involving apks and telephony, is not true. Due to this falsehood, whether mistake or intentional, I am worried about whether its a documentation change, or something far more sinister. Maybe I need to don a tin-foil hat, but the last place I expect incorrect technical info from is Google.

We have no clarification on the issue. Its entirely possible it was a poorly worded statement. Its also possible that something bad is being covered up, such as closing source on LTE and CDMA. That won't stop otas by any means, nor will it slow them down. It will however strike one hell of a blow to those building from AOSP. Remember the Thunderbolt? Want to go back to hacked RILs? Me neither.
[Samsung Galaxy Nexus] koszor:
Thanks for clearing things up just about 100% for me, but can you explain what 'props' are?
[Samsung Galaxy Nexus] adrynalyne:
Thats lazy type for, 'proprietaries'.

Closed source binaries.
[Samsung Galaxy Nexus] Rem3Dy:
Google can't sign closed source properties with an open source license. The explanation was poorly worded at an attempt to dumb it down for the average Joe.
[Samsung Galaxy Nexus] adrynalyne:
Im aware.

That said...we aren't doing anything of that sort... so whats the BS that calls and data don't wok, etc?

Nothing needs to be re-signed for either.

Dumbing down is one thing. Completely incorrect is quite another.
[Samsung Galaxy Nexus] KWKSLVR:
+1

To the average end user, like 99% of XDA, this means NOTHING. If you never rooted/unlocked your phone and built a ROM yourself, this means NOTHING. Updates will still come. Google is good about supporting devices. Verizon is good about supporting devices. Samsung, believe it or not, is good about supporting devices. The sky is not falling people. Some of the same people whining in this thread were whining before they ever bought the phone because they feared it wouldn't be a "true Nexus". Well, you bought the phone anyway. Shut up about it. It's old and retarded. It's still a Nexus. It still gets updates from Google.

People will disagree, and that's fine, but there is a difference between inclusion into AOSP and receiving OTA support from Google. They're two separate things that the community has lumped into one "feature" for a long time now, and that's BS. Before the damn VZW version ever hit stores there was talk about Toro and likely chance it wouldn't fall under the standards of AOSP. Anytime you're meshing CDMA with AOSP there are challenges. I don't have to be a developer to have been able to observe that fact for a very long time now.

If it bothers you, swap to AT&T and get a GSM version. If you can't swap to another carrier, go buy a Razer, Rezound or Bionic and enjoy dealing with modding those. I'll take updates from Google and ICS over those any day of the week. Those are nice devices, but the reason I bought a GNEX was for updates from Google, and ICS. Those things are still happening. The reality is that the Toro building of the GNEX is the closest we'll ever get to a Nexus device on Verizon. Take it for what it is or leave it, but don't whine on a message board about it. Google is not reading. Google can't do anything about it. Google gave people the closest they could to what they wanted (A Nexus on Verizon).

End users need to take a damn chill pill and stop having aneurysms over a device they can't and don't even develop for.

/rant

;)
[Samsung Galaxy Nexus] lrs421:
Which is exactly why I'm sitting on my sofa, watching old episodes of the walking dead with a Brooklyn lager in my hand. Once I understood the nature of the issue I was no longer pissed but still annoyed. That 1% you speak of though, they have a right to be irritated. In fact, it's good for the rest of the community to fully understand the nature of the situation as well. Not everyone here started out as devs and perhaps people purchased this "developer" device to get into compiling and building, those people have now taken a hit as well.

I posted in other thread that I'm not going back to skinned android versions and I meant that. It was true last week and it's true today. Do I feel that this device as a true/blue as the GSM version, no. But I rather have this phone than any other out there. So, I'll finish drinking my beer...I have what I have and that's all to it.
[Samsung Galaxy Nexus] mzjc:
Thanks to everyone that has been clarifying this mess with the general population. :) I'm not sure if this has been asked anywhere, but what does this mean for all you devs and new roms moving forward? Say 4.0.4, and so on are released.. will you be able to update and create new roms and kernels?

I have my phone unlocked, but haven't rooted yet and was about to this weekend until this great news got posted.
[Samsung Galaxy Nexus] lrs421:
Roms will likely still continue but the radio work on future builds will be challenging. Read adrynalyne's posts you'll get a clear picture. He's also a thunderbolt dev so he knows what it's like to deal with radio issues.
[Samsung Galaxy Nexus] mustbepbs:
This. I still am not certain what this means for future update builds (eg 4.0.4). Are they going to continue to release source for updates, and we'll just have to wait for radio source via OTA? That's the only part of don't understand.
[Samsung Galaxy Nexus] adrynalyne:
They said nothing will change. However, if they were incorrect about part of the statement, who is to say they are correct about that?
[Samsung Galaxy Nexus] adrynalyne:
I don't know what a chill pill is, but the next person that tells me to take one is going to die a horrible death.

Their statement was blatantly incorrect. I get their take home message was nothing will change, but how can I trust that info when their explanation as to why was 100% inaccurate?

According to their statement, you cannot build a rom right now and have voice and data unless you have correctly signed proprietaries (signed for aosp).

Thats a lie.

PS--I do develop for this device.
[Samsung Galaxy Nexus] lrs421:
Lmao.

I'm going to follow you on Twitter to see if you get a response.
[Samsung Galaxy Nexus] adrynalyne:
Or keep an eye out for jbq:

https://twitter.com/#!/jbqueru

He either took the weekend off (likely) or is ignoring me though.
[Samsung Galaxy Nexus] adrynalyne:
But then, was Sprint in on that decision too? Because both were removed. If they aren't going to give cdma users proprietaries, I get it. I accept it. Heck, I am even USED to it.

My fear is that it is worded losely enough that AOSP may lose LTE and CDMA telephony support. That really bugs me. I'm not necessarily upset at Google, because I don't know exactly who to be upset at. I am just upset that their statement is misl;eading, vague, and as clear as mud in most aspects.
[Samsung Galaxy Nexus] Esteway.619:
Here's an article posted on the nexus s 4g side that will give a bit more light to some of the questions asked.

http://m.engadget.com/default/artic...-pages-over-cdma/&category=classic&postPage=1
[Samsung Galaxy Nexus] adrynalyne:
Sorry, system is temporarily unavailable, please try again later.

I feel enlightened ;)
[Samsung Galaxy Nexus] KWKSLVR:
It's back up, here's what it says which is what we already knew they said. ;)
[Samsung Galaxy Nexus] AdamHart612:
This is all really dumb. But I find it hard to consider the CDMA Nexus S or Galaxy Nexus to be "real" Nexus device's anyway. What good is open software if the physical handset is locked to a carrier? CDMA Nexuses are essentially on house arrest, free to move within the confines of their own network but nothing more. Agree or not, a CDMA handset and "open" are two opposing ideas.

At the same time, I don't blame anyone on Sprint or Verizon (my work line is on Sprint and I would love a second Nexus...) for wanting a Nexus on their carrier. But Google should have stuck with GSM, if only because the nature of CDMA carriers mean that handsets are inherently closed.

But all that aside, this is a bunch of hooey. Google shouldn't have dropped Nexus phones on carriers using technology resulting in licensing conflicts without some kinda plan to deal. Then again, Google is in the business of making money and cutting out Verizon and Sprint eliminates a huge market in the USA.
[Samsung Galaxy Nexus] zephiK:
Google isn't in the business of making money. Nexus devices are developer devices, they are not intended for mainstream usage.

During the holidays, Google was giving out GSM Galaxy Nexus devices to their employees not CDMA. Google themselves already prefer GSM. Blame Verizon for making Galaxy Nexus a carrier exclusive in the U.S.
[Samsung Galaxy Nexus] adrynalyne:
The only companies not in the business of making money are the bankrupt ones.
[Samsung Galaxy Nexus] republitarian:
Guys what's up with the essay long posts... can I have a cliff notes version?
[Samsung Galaxy Nexus] adrynalyne:
Google did this, we said that...then DRAMA.

Cliff notes version.
[Samsung Galaxy Nexus] player911:
Well it isn't like anything changed with the carriers to suddenly require signed apks.

Google new this going in. In this case they simply shouldn't make Nexi for those carriers.

With the current situation they could still release AOSP without the proprietary binaries and just have them as separate downloads pre-signed apks (not source).

We'll see how it pans out I guess.

LTE EX Galaxy Nexus - 4.0.3 AOSP

Asus Transformer - Revolver OC/UV
[Samsung Galaxy Nexus] adrynalyne:
APKs are not the issue. Folks keep reverting back to an earlier state of the conversation.

No APKs are required for CDMA/LTE.
[Samsung Galaxy Nexus] android_nexus:
Google crazy, insane and mad?
[Samsung Galaxy Nexus] KWKSLVR:
I disagree. Android is about options, the more the merrier. Like I eluded to earlier, there is this notion that "Dev Phone" = Pure Android + Updates straight from Google.

This is incorrect.

Toro is still pure Android.

Toro still gets updates directly from Google.

To 99% of the 5% of the 1% of Android users that own a VZW GNEX, this means nothing. It's a change in documentation. Big deal.

As far as long posts. Guys, if you can't focus on reading for a few minutes, go do something else or take a Ritalin.
[Samsung Galaxy Nexus] Jameslepable:
No am not a dev but a leaked 4.0.4 update seems to agree with me.
[Samsung Galaxy Nexus] lrs421:
No it doesn't. We already established that updates will continue. But tell us this, do you have the source for that 4.0.4 update? Could you compile it from scratch right now if you wanted to? That's what's in danger here, not ota's.
[Samsung Galaxy Nexus] Wiloid76:
Possibility of Nexus Cdma devices' bootloaders not being unlockable in the future???

Hi, I just checked out the article to which Esteway.619 placed the link to on his post in this discussion and it made me a little nervous. The last paragraph in the article that's supposedly a quote from Google, explains that they are not promising that Nexus Cdma devices' Bootloaders will be unlockable in the future. If they do that it would be a horrible move but it's a move that most likely the a**hole carriers would demand. Just to make it clear I don't like or intend to start rumors. I just got nervous when reading that last paragraph. Did anyone read that article?
[Samsung Galaxy Nexus] Tidbits:
At Some point Verizon and Sprint will be LTE... They are already working and planning on running VoLTE so what's the point of doing that if they are going to stick with CDMA voice? Sprint has already outlined they are going FULL LTE by 2013.
[Samsung Galaxy Nexus] xxprodigyxx11:
Don't forget AT&T. They're already rolling out LTE.
[Samsung Galaxy Nexus] tannor:
Updated post from JBQ

https://groups.google.com/group/android-platform/browse_thread/thread/10c8db7b1c893e1e?pli=1

I don't think it been posted here or did not see it

Another update but pretty much similar to above from JBQ

http://androidcommunity.com/google-...per-phones-not-publishing-aosp-code-20120206/
[Samsung Galaxy Nexus] Jameslepable:
All I was saying is google will still update it, it just isn't a reference phone that's the point am making. The cdma SGN (atm) is exclusive to verizon. How can you use a phone that works with one carrier as a reference for all phones running ICS. Especially when the majority of phones are GSM.
[Samsung Galaxy Nexus] KWKSLVR:
Sweet! Thanks for sharing. I like to see when my theories are right! Legal issues suck, but at least we got a REAL explanation.
[Samsung Galaxy Nexus] tannor:
Not sure about your theories this has me the most concerned in terms of development:

Everything he said is if we can, I am not sure how this is all good for AOSP developers on CDMA? Right now we can compile AOSP for cdma, but there might be a point in time it will no longer possible, or will be hacked that not everything works properly.

I see fragmentation happening down the line just among the different nexus.
[Samsung Galaxy Nexus] adrynalyne:
Sprint couldn't roll out wimax in any timely fashion. You really be live they will be FULL LTE by 2013? More like lucky if 1/3 of the LTE roll out for just data is complete by 2013.
[Samsung Galaxy Nexus] miketoasty:
4.0.4 was a leak and nothing more, Google doesn't post the code for build's that aren't official.

There is no extreme danger to us in terms of building AOSP.
[Samsung Galaxy Nexus] lrs421:
I know, let's see if we get the source when it or whatever official build is released. I was referring to the danger of losing the ability to compile from aosp. The poster was using a leak to validate his argument.
[Samsung Galaxy Nexus] adrynalyne:
We have already lost said ability unless you know what to add back.

They removed all CDMA devices from the lunch menu (used to choose builds).
[Samsung Galaxy Nexus] Jameslepable:
Yea and my argument is google is still going to update the phone. The leak proves that it's still getting updates.