[moosc]

Straight from Google plus

Jean-Baptiste Queru 1 hour ago · Desktop · Public Sprint Galaxy Nexus: not supported in AOSP

I've been getting a few questions about AOSP support for the Sprint Galaxy Nexus.

The short answer is: the Sprint Galaxy Nexus is not supported in the Android Open Source Project.

The long answer: the release process for the Spring Galaxy Nexus is similar to that of the non-yakju variants of the GSM Galaxy Nexus (e.g. yakjuxw, yakjuux, yakjudv...), which makes that device similarly impossible to support in AOSP. There are no source files, no proprietary hardware-related binaries and no factory images available for the Sprint Galaxy Nexus. In addition, since it's a CDMA device, it would probably be limited by the usual CDMA licensing issues that have been affecting the other CDMA devices.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

[Paul627g]

For anyone wondering...

"torospr" project has been created at the Google pages but the answer is above explaining why its not being supported in AOSP.

[rwong48]

Permalink:

[demmalition1]

Can someone tell me in plain english what this means exactly? I haven't rooted my Evo 4G yet, but I know some of the lingo regarding rooting/flashing and am planning to root/flash my G Nexus today after I pick it up form the store.

Does this mean that I won't get updates straight from Google like the NS4G was with ICS? If Jelly Bean comes out in July for example, do I have to wait for it or can I get it by flashing/rooting it onto my Nexus somehow?

Finally, does this cripple the phone in any significant way other than what I listed above? Would this in any way mean that the Sprint Nexus is ruined and that it would just be easier to go to the Evo LTE (don't care about hardware, just software and if its crippled in some way so that it is similar in update rate to the Evo LTE, I might as well get the better hardware as well)?

Thanks for any replies, as I'm rather confused as to what is going on right now despite being a long-time lurker on this and other sites.

[mmmajor]

Can someone tell me in plain english what this means exactly? I haven't rooted my Evo 4G yet, but I know some of the lingo regarding rooting/flashing and am planning to root/flash my G Nexus today after I pick it up form the store.

Does this mean that I won't get updates straight from Google like the NS4G was with ICS? If Jelly Bean comes out in July for example, do I have to wait for it or can I get it by flashing/rooting it onto my Nexus somehow?

Finally, does this cripple the phone in any significant way other than what I listed above? Would this in any way mean that the Sprint Nexus is ruined and that it would just be easier to go to the Evo LTE (don't care about hardware, just software and if its crippled in some way so that it is similar in update rate to the Evo LTE, I might as well get the better hardware as well)?

Thanks for any replies, as I'm rather confused as to what is going on right now despite being a long-time lurker on this and other sites.

+1 everything he just said..

[demmalition1]

Thanks for the support mmmajor, but can anyone please tell me in detail what this means exactly? I haven't bought my Nexus yet because of this. I'm rather concerned about being locked down in a 2 year contract with a phone that gets slow updates and has inferior hardware.

Is this a deal breaker in any way?

[Paul627g]

No its not really a deal breaker I don't believe... We are still going to get updates we but we are going to be at the mercy of Sprint/Sammy on when we receive them.

The only phone that gets them straight from Google with no red tape is the GSM models...

As far as custom ROMs are concerned and such, they will still be able to use source to build them but to get started someone is going to have to pull proprietary files and other things directly from a Sprint GNex that Google doesn't have.

Once those files are out in circulation among the devs things will basically continue onward as usual... Devs will build from Google ICS source and then add in the custom related files for Sprint's GNex.

[makeotapackage-j4]

The biggest concern for me is if there will be a dedicated build option with the "lunch" command. I'm all good with keeping mine, as long as its exactly as the NS4G is-where the binaries can be downloaded from Google, and when the lunch cmnd is entered, we see a specific option. (Just as it is with Crespo and Crespo4g right now.)
Thanks Paul :-)

[Paul627g]

The biggest concern for me is if there will be a dedicated build option with the "lunch" command. I'm all good with keeping mine, as long as its exactly as the NS4G is-where the binaries can be downloaded from Google, and when the lunch cmnd is entered, we see a specific option. (Just as it is with Crespo and Crespo4g right now.)
Thanks Paul :-)

Ya I'm not sure how its all going to play out. I'm actually learning more about building from source and getting to know my way around. Two weeks ago I wouldn't of even known what the heck you were talking about with the LUNCH command but now I do...

Going to just have to sit back and wait and see what is offered up by Sammy/Sprint and Google in the coming weeks.

I would think as soon as developers like Pete Alfonso and CM team get the parts they need together to create a build repo that will explain more of the picture.

[moosc]

I don't thank that will happen the only thing well see from Google is asop builds for GSM. It really sounds like the old way of doing it what for sprint/vzw cdma leak so we can add all necessary radios and binarys to the asop tree. Sounds like more work for devs.

The biggest concern for me is if there will be a dedicated build option with the "lunch" command. I'm all good with keeping mine, as long as its exactly as the NS4G is-where the binaries can be downloaded from Google, and when the lunch cmnd is entered, we see a specific option. (Just as it is with Crespo and Crespo4g right now.)
Thanks Paul :-)

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2