Hi guys,
I currently have a Dinc2, but have been doing my due diligence in searching for a new phone. The verizon Galaxy Nexus is on my list but I'm having a hard time understanding the cdma binary package signing and it's implications for AOSP roms. Can anyone make it a little more clear for me? Or have a link that explains it in relation to the modding scene?
I'm basically wondering if it's a hinderance at all to the modding community. I see a lot of roms in the android development section, are those legit AOSP roms? Or are they modded stock roms from Verizon?
baggar11
Not a hindrance at all since the Verizon Galaxy Nexus is an AOSP device with its binaries available at Google's developer portal.
Sent from my Galaxy Nexus using Tapatalk 2
All Gnex are AOSP out of the box, the VZW version just has the VZW app added.
What was all this hoopla about then? Sounds like Verizon was making it hard for Google and the community to support the cdma Nexus's. Is that stuff pretty much resolved, or was it never really a problem for the community? Thanks for the reply guys!
http://pocketnow.com/2012/07/10/gal...p-support-with-jelly-bean-but-not-for-sprint/
CDMA devices have been a thorn in the side of the AOSP for some time now. Google explained the issues at hand when it made a statement back in February, pointing out how the need for carrier-signed binaries containing critical communications code was getting in the way of developers being able to build Android for these devices. Luckily, things started looking up just last week, with new binaries becoming available for the Nexus S 4G on Sprint. At the time, the situation still looked bleak for the Verizon Galaxy Nexus. A week later, the tide has really turned, and last night’s publication of the Android 4.1 Jelly Bean source saw the arrival of some eagerly awaited binaries for the VZW GNex. Where are the equivalent files for the Sprint GNex, though?
WiredPirate said:
All Gnex are AOSP out of the box, the VZW version just has the VZW app added.
Click to expand...
Click to collapse
Sprint version is not supported by AOSP, as of yet.
Related
So I tried to do some searching around multiple sites, and couldn't seem to find any answers.
Is there a Dev on the CyanogenMod team that is supporting the CDMA Galaxy Nexus? I have seen multiple Kang CM9 roms, but nothing official from any devs. I am not asking for ETA's or release dates, I just would like to follow the person on Twitter or Google+ to see any updates or progress they talk about. Also, is there a site for the change logs for CM9 yet or is that still pending the server fix for nightly builds. Any links or names would be helpful.
Thanks for any info in advance.
No one? I found this on github
https://github.com/CyanogenMod/android_device_samsung_toro
I know there are a couple CM devs who have the Galaxy Nexus. While I haven't seen any mention of working on CM9 for it, I would be amazed if there is not a developer working on it right now. I'm sure there will be a stable build releasing soon.
I'm personally holding off on even rooting my phone until an official CM9 ROM is released. Stock ICS is more than adequate for now.
sn0warmy said:
I know there are a couple CM devs who have the Galaxy Nexus. While I haven't seen any mention of working on CM9 for it, I would be amazed if there is not a developer working on it right now. I'm sure there will be a stable build releasing soon.
I'm personally holding off on even rooting my phone until an official CM9 ROM is released. Stock ICS is more than adequate for now.
Click to expand...
Click to collapse
Isn't the nexus line the most supported phone by devs?
Which Android phone out there gets the most development support from the community? I'm just curious.
The Nexus One was the most well supported phone I ever owned. The Nexus S took a while to get going (come to think of it, the n1 did too, wish I would've stuck it out with my S), but eventually had a great dev community. The OG droid had a great dev community as well, as did the HTC desire (due to being so similar to the n1). Recently, the international galaxy s2 has been getting a lot of dev love because its such a beast internally. The galaxy nexus is showing incredible progress for as long as its been out for. I find it takes devs about 4-8 months after a phone's release to really start showing some impressive stuff. CM9 in February or March will be a milestone for this phone and will definitely deliver a hefty helping of tweaks / mods to ICS. I've seen a lot of great devs working with the Nexus so I'm not too worried. I, personally, don't even have mine rooted yet, because I'm waiting for the dust to settle. I'm not the crack flasher I once was and ICS is so damned good on its own that I'll probably wait for a nice, feature-complete version of bugless beast or MCR to come out (probably only 2-3 weeks). CM9 will most likely be my rom of choice once that's out.
There are already CM9 kangs in the CDMA forums. CM9 isn't out yet but once nightlies roll out we'll be good.
-Galaxy Nexus
-Asus Transformer
aaronpaws said:
The Nexus One was the most well supported phone I ever owned. The Nexus S took a while to get going (come to think of it, the n1 did too, wish I would've stuck it out with my S), but eventually had a great dev community. The OG droid had a great dev community as well, as did the HTC desire (due to being so similar to the n1). Recently, the international galaxy s2 has been getting a lot of dev love because its such a beast internally. The galaxy nexus is showing incredible progress for as long as its been out for. I find it takes devs about 4-8 months after a phone's release to really start showing some impressive stuff. CM9 in February or March will be a milestone for this phone and will definitely deliver a hefty helping of tweaks / mods to ICS. I've seen a lot of great devs working with the Nexus so I'm not too worried. I, personally, don't even have mine rooted yet, because I'm waiting for the dust to settle. I'm not the crack flasher I once was and ICS is so damned good on its own that I'll probably wait for a nice, feature-complete version of bugless beast or MCR to come out (probably only 2-3 weeks). CM9 will most likely be my rom of choice once that's out.
Click to expand...
Click to collapse
The top 2 I can think of is the hd2 and the evo 4g. I have the evo and there are tons of roms for it.
Sent from my Galaxy Nexus using Tapatalk
Several of the early Droid phones were very popular with Dev's because they were so easy to unlock. As for newer phones, it seems to be the Nexus devices and any that are easy to unlock.
Can't wait for nightly builds of CM9 to start.
The phone has been out for like 2 weeks people. Give it another month or two and this place will be booming with development. Relax and enjoy the phone as is for a minute. The development will grow. I promise.
I normally have my Android phones rooted within 1 hour of getting them out of the packaging. However, I haven't even found a single reason to root this thing.
I'm also holding off on modding it until CM9 comes. I need to stay on stock for a while so I can make comparisons.
sn0warmy said:
I know there are a couple CM devs who have the Galaxy Nexus. While I haven't seen any mention of working on CM9 for it, I would be amazed if there is not a developer working on it right now. I'm sure there will be a stable build releasing soon.
I'm personally holding off on even rooting my phone until an official CM9 ROM is released. Stock ICS is more than adequate for now.
Click to expand...
Click to collapse
Same here. I haven't done a thing with it...I'm completely satisfied with the OS and everything. If only the signal issues could be fixed I'd be a happy clam.
Kind of stinks that I get 0 signal in at least 1/2 of all places I've gone in the past week and a half. I don't mean 0 bars, I mean I can't make/receive voice calls and I get no data connection when trying to use any app that accesses the internet. Text messages send, but it usually takes them 20+ seconds to do so. This kind of connection quality is horrifyingly bad.
From techeye:
http://news.techeye.net/mobile/google-abandons-cdma?
CDMA is marked "archived, for reference only"
http://code.google.com/android/nexus/images.html
I guess that finally nails the Verizon Galaxy Nexus as a carrier-phone. Next time buy a truly free & open device (i.e. GSM)
Seriously though. This Galaxy Nexus launch and follow-up has to be the messiest thing I've ever since Google set its foot into. From launch, to providing international release-dates, to US promotion, to handling updates, to releasing buggy updates, to pulling them, to general PR.
It's all been a big ****ing mess.
Is this the sign of the start of the end of the Nexus program or what? Or is leaving closed CDMA networks and carriers behind actually a sign of a new, better start?
Discuss.
Welcome to last week.
Sent from my Galaxy Nexus
Edit: Rootzwiki seems to have something more to offer than the techeye article.
http://rootzwiki.com/_/articles/ann...dma-galaxy-nexus-will-continue-to-update-r374
Still not crystal clear, and definitely falls under my definition of messy PR.
The rootzwiki even has an update, because Google has messed up its correcting response and needs to correct itself, again.
Yeah this is old news. Plus the 4.0.4 update is out for the VZW. What's it like beating a dead horse lol?
Sent from my Gummy Nexus
http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus
Funny thing is how the 'abandoned' device is getting more frequent updates than e officially supported device. We still don't have 4.0.3 officially yet (the last relapse is officially the Nexus S one), and 4.0.4 is CDMA only.
Welcome to last week, BTW.
Omg. Not only does it keep being reposted but by people who don't even understand what's going on and say things like " next time buy a truly free and open device".
Sent from my 'closed' 4.0.4 CDMA Galaxy Nexus.
matt30 said:
http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Hm. Should have searched the forum better it seems. I didn't find it before posting. Anyway. The conclusion from that thread still seems to be incredibly messy.
Can anyone tell WTH it now does mean to be a "Nexus" device? Ever since the release of the Galaxy Nexus and its "evil" CDMA counter-pair, that definition seems to have been in a flux.
Haesslich said:
Welcome to last week, BTW.
Click to expand...
Click to collapse
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
http://androinica.com/2012/02/cdma-...l-dev-support-updates-still-come-from-google/
Sent from my Gummy Nexus
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
Don't talk about what you do not comprehend. That is the most ignorant thing I have heard in a long time.
I too can build 4.0.3 for CDMA. So go get educated.
adrynalyne said:
I too can build 4.0.3 for CDMA. So go get educated.
Click to expand...
Click to collapse
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this
josteink said:
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this
Click to expand...
Click to collapse
If my understanding is correct, you need to build 4.0.3 with the proprietary files (binaries) contained in a working cdma build of the device (what Google has called "apks"). Since those files are closed source, they cannot be included in AOSP.
Why those cdma files are closed source is a mystery. It could be for legal reasons or it could be because of the way cdma networks communicate with devices (requiring them to have a signature from the carrier embedded in them).
Sent via Galaxy Nexus
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
adrynalyne said:
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
Click to expand...
Click to collapse
And cmda (and I guess the proprietary software) is owned by a working group of several different telecom companies.
Sent via Galaxy Nexus
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
sahakiap said:
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
Click to expand...
Click to collapse
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
josteink said:
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
Click to expand...
Click to collapse
Thanks for posting josteink. I hadn't seen it before either. Not sure why everyone is getting their feathers ruffled when you clearly put a smiley face beside the comment. And besides, those that are posting saying it is old news keep bumping the thread...
josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
There is no source release of 4.0.4 yet but I have been on 4.0.3 since the day I got my phone.
How does it feel? It feels great to have 32GB of space on my phone and get an average 20Mbps downstream. (At times reaching 40Mbps+)
This isn't old news at all and it is a big deal. A lot of people got screwed here by both Google and Verizon. Not having official AOSP support for developer nexus phone is unacceptable. If there were code distribution issues, then Google should have worked that out way before the official launch. I'm still holding out hope that this will be resolved, but at this point i'd settle for just getting out of my contract and moving over to the GSM variant.
On a related note, I wish CDMA would just fade away into a bad memory.
Is it just me or are we stuck for a while now switching couple of ROMs that bring out new "features" like updated Market, Amazon Store or launchers?
Wait for more people to get ICS, hey it's all I got.
Also, what the hell more do you want from your phone? Lol.
zerozoneice said:
Is it just me or are we stuck for a while now switching couple of ROMs that bring out new "features" like updated Market, Amazon Store or launchers?
Click to expand...
Click to collapse
Lol sounds like you need to follow a real dev if the roms you are using only do that between versions.
adrynalyne said:
Lol sounds like you need to follow a real dev if the roms you are using only do that between versions.
Click to expand...
Click to collapse
what's out there besides AOKP and CM9 that does real development?
zerozoneice said:
what's out there besides AOKP and CM9 that does real development?
Click to expand...
Click to collapse
Nothing? Besides kernels. A lot of the other roms cherry pick from those.
If all you see as real development is aokp and cm, you arent paying attention. BAMF Paradigm is 100% aokp free and 99% cm free.
The only things we borrowed was the T9 dialer and some of the cm overclocking settings.
If you have used it, you know it is a clone of neither. Aokp has more cm code in their rom than we do.
I am sure there are other original roms out there as well.
You're not going to see much traction on features until Samsung, LG, Motorola, and HTC start releasing ICS phones, and once the developers actually have time to learn about the new features. Historically, a good portion of the options available in ROMs on Nexus phones are cherry-picked and re-engineered from features we see implemented by the manufacturers of the other phones.
My Nexus One that I bought two years ago was plain jane for about 6 months because stock Android was the bleeding edge. Then once the Desire hit the shelves in the U.K. people were scrambling to slap Sense onto the Nexus. Then the Galaxy S came out and people were scrambling to slap TouchWiz onto the Nexus.
Be patient, or learn how to develop for Android so you can make your own contributions to CM and AOKP.
Yea I totally agree. I switched from galaxy s2 i9100 and I kind if miss it. Galaxy s2 had so many roms and so much development was going on. I tried 30+ roms on that beast. The community was well enthusiastic. I really miss hyperdroid and check roms. ... I guess we need to wait and let others joint ICS gang and hope for best.
Sent from my Galaxy Nexus using Tapatalk
Hey Everyone,
I have a question for you Nexus phone owners. Coming from the Epic 4G Touch, it's incredibly frustrating when the dev community comes out with a fantastic new ROM, which is immediately crippled due to a lack of drivers/kernels/etc. My understanding is that this wouldn't be an issue for Nexus devices, is that correct? As I understand it, the stock rom is AOSP, and all of the drivers and kernel are open sourced, is that right?
Thanks!!
thaprinze said:
Hey Everyone,
I have a question for you Nexus phone owners. Coming from the Epic 4G Touch, it's incredibly frustrating when the dev community comes out with a fantastic new ROM, which is immediately crippled due to a lack of drivers/kernels/etc. My understanding is that this wouldn't be an issue for Nexus devices, is that correct? As I understand it, the stock rom is AOSP, and all of the drivers and kernel are open sourced, is that right?
Thanks!!
Click to expand...
Click to collapse
The stock Rom is almost AOSP, with some Google apps bundled (play store/gallery/Gmail and a couple more).
Swype'ed on my CM10 Galaxy Nexus
Right, but otherwise, developers have full access to everything else they need, right? None of that "no gps/camera/wifi/etc until Samsung/HTC/Moto/etc releases a Jelleybean kernel" crap, right?
thaprinze said:
Right, but otherwise, developers have full access to everything else they need, right? None of that "no gps/camera/wifi/etc until Samsung/HTC/Moto/etc releases a Jelleybean kernel" crap, right?
Click to expand...
Click to collapse
let me put it to you this way. back on my ns4g a certain dev was able to build a completely functional ics rom from the android sdk before there ever was an official ics rom released to the public for ANY device. suffice to say that devs have a lot more flexibility.
If it is a GSM Nexus device then you are correct to my knowledge. But a CDMA device is a different story.
WiredPirate said:
If it is a GSM Nexus device then you are correct to my knowledge. But a CDMA device is a different story.
Click to expand...
Click to collapse
Awesome! Now, if only there was a Galaxy Nexus Note...
Honestly though, I've been so frustrated with all the kernel/driver issues with my E4GT. I think I'm Nexus from here on out. Thanks for your help!
So as I understand it, much has been made about the difficulty of getting LTE in the Nexus line because of proprietary drivers and binaries. Consequently, when the Nexus 7 LTE was announced many rejoiced that we would finally have AOSP LTE. However, I also heard many caution and say that we could get something similar to the Verizon Nexus that just left that information out of AOSP.
So now that we've got the Nexus 7 LTE out and I believe also have the AOSP for the LTE variant out, what is the answer? Are all of the binaries and drivers there? Also, are there any other binaries or drivers left out of the AOSP?
So checking this page:
https://developers.google.com/android/nexus/images
...it looks like the image for the LTE variant might not have been released yet. If so, then I guess this question is not answerable yet.
... and checking this page, the last update is 7 weeks ago, the JLS36C is missing.
https://android.googlesource.com/device/asus/deb/
Looks like after Jean-Baptiste Queru has quit the AOSP nobody at google cares anymore. The End of AOSP? Hopefully not ... :crying:
So it's out now. Any additional thoughts?
I'm bumping this again as there has been some time to look at it now. thoughts?
Poke_N_PDA said:
I'm bumping this again as there has been some time to look at it now. thoughts?
Click to expand...
Click to collapse
I imagine development and including the binaries will be at the discretion of the devs. Some do it (like Carbon) while many others don't at all.
I think once adoption rate rises it will be more common.
driver binaries and factory images are available for Nexus 7 LTE (razorg). Not if the binaries are complete though.
https://developers.google.com/android/nexus/drivers#razorg
https://developers.google.com/android/nexus/images#razorg
EDIT: sorry, i think i mis-read your question.