Verizon GNex and AOSP

[DaEXfactoR]

Now that the Verizon version of the Galaxy Nexus has ASOP support, what exactly does that mean? Can I expect faster updates? Better custom development? Updates from Google? I'm not ashamed to say I'm a little confused when it comes to carrier branded Nexus'. Or more specifically, CDMA Nexus devices.

Sent from my Galaxy Nexus using Android Central Forums

 

[anon(596177)]

Now that the Verizon version of the Galaxy Nexus has ASOP support, what exactly does that mean? Can I expect faster updates? Better custom development? Updates from Google? I'm not ashamed to say I'm a little confused when it comes to carrier branded Nexus'. Or more specifically, CDMA Nexus devices.

Sent from my Galaxy Nexus using Android Central Forums

AOSP support basically means it is easier for the developers to build and compile custom ROM's for the VZN Galaxy nexus now, where in the past (after they lost AOSP support initially that is) they had to add additional code to the AOSP code to make the VZN nexus work with those builds.

I'm not a developer by any means but if I recall correctly that's the only advantage to the Gnex being recertified as an AOSP device. It doesnt affect OTA's from verizon at all, it only affects those that build custom ROMs and those who use those ROMs.

 

[dmmarck]

AOSP support basically means it is easier for the developers to build and compile custom ROM's for the VZN Galaxy nexus now, where in the past (after they lost AOSP support initially that is) they had to add additional code to the AOSP code to make the VZN nexus work with those builds.

I'm not a developer by any means but if I recall correctly that's the only advantage to the Gnex being recertified as an AOSP device. It doesnt affect OTA's from verizon at all, it only affects those that build custom ROMs and those who use those ROMs.

Correct. Essentially, they have the proprietary binaries needed to get stuff working whereas before they ran into some roadblocks in getting those binaries listed and compliant with AOSP and the open source licensing. They are still proprietary, and you still must agree to terms of service, but they are now listed and supported.

 

[DaEXfactoR]

Ah, this is why I love the AC community. Thanks guys

Sent from my Galaxy Nexus using Android Central Forums

 

[les017]

Thanks for the info!!! Now I also better understand. But if I could get one final clarification....

1) This will not really affect OTA updates thru Verizon (T/F)
2) This only really helps a user get better choice thru dev community IF devs decide to bother with dealing with these binaries (T/F)

thanks in advance

 

[TheAssailant]

True and true. AOSP doesn't change Verizon's foot-dragging.

Sent from my VZW Galaxy Nexus using Android Central Forums

 

[georgeanderson]

Just get a custom ROM if you're worried about VZW. That's what I did. Running the I/O JB on my GNex now.

 

[smccloud]

Hmm, now to figure out how to build Jelly Bean for my GN now

 

[dmmarck]

Hmm, now to figure out how to build Jelly Bean for my GN now

You'll run into some issues with some of the GAPPs. Let me know if you want any tips/tricks..lol

 

[smccloud]

You'll run into some issues with some of the GAPPs. Let me know if you want any tips/tricks..lol

Those would definitely be helpful.

 

[dmmarck]

Those would definitely be helpful.

The main issues were making sure the source synced and then having to manually type in the build and build type, because for some reason they were unavailable in the regular "lunch" menu.

Follow the instructions they have (just google how to build android, google has a great site setup for this) and they're usually spot on!