So I gave JellyBean a run but had some issues so flashed back to my LiquidSmooth 1.4 nandroid, but I'm curious now that the 4.1 port is available, does that mean our favorite developers of our favorite ROMs (AOKP, Liquid, BAMF, etc...) will be focusing their attention to 4.1, or will they still be supporting 4.0x? And if ROMs are 4.1 based, does that mean we'll be seeing less reboots and the other issues that many of us were plagued with when trying out 4.1?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[Verizon] What does JellyBean mean for 4.0x based ROMs?
- Thread starter viper689
- Start date
-
- Tags
- galaxy nexus
jbdan
Extreme Android User
They will focus (well I know team kang will) on 4.1 when source from the Goog is available. As far as still supporting pre-4.1, I guess that will be up to the developers. When the 4.1 roms are built using source they will be more reliable. 4.1 present is hackery at it's finest, a port made from a nandroid off a GSM device. I'm astounded they've gotten this far with it.
jbdan
Extreme Android User
D
Deleted User
Guest
Exactly.
Google said the source would drop mid-July, when they start shipping the new Nexus devices.
You'll see a very quick shift in focus over to JB-based ROMs, and will probably see the ICS ROMs get neglected completely... but that won't matter, because once the source is here the JB ROMs will be stable and happy again.
As a layperson, I am still very curious as to what is required for a pure Jelly bean ROM for the Verizon GNexus (no current 4.0 code hacked in to make it work). Does the framework itself require the future JB proprietary Verizon files, or is it really only the special radios that are required?
jbdan
Extreme Android User
A great question. As far as I'm concerned, a pure JB ROM to me does NOT have to have the VZW proprietary files. But if you want that, I assume it would be like 4.0.4, when it leaked, then VZ soak tested, then they sent out the OTA. Rooters and devs had their hands on the OTA weeks before VZ pushed it. I'd say it'd be similar with JB. Just a wild guess on my part. I'm as "lay" as they get
jbdan
Extreme Android User
Zaphod from team kang mentions:
"Even when JB source rolls out, we don't know how hard its going to be to roll our mods into that.
I suspect we have a pretty big job ahead of us. This is not likely going to be a few changes in the build tree and viola we are updated. At best, we (that's the Royal we, poor Roman will likely do the bulk of this) have to manually merge a crap-ton of commits. On the worse side, we may have to re-write significant amounts of code.
There is no way to know until we see that source. Just enjoy AOKP on 4.0.4 for now, or try one of the stock 4.1 ROMs that have been built (I am ... first time I've been off of AOKP since about December.)"
"Even when JB source rolls out, we don't know how hard its going to be to roll our mods into that.
I suspect we have a pretty big job ahead of us. This is not likely going to be a few changes in the build tree and viola we are updated. At best, we (that's the Royal we, poor Roman will likely do the bulk of this) have to manually merge a crap-ton of commits. On the worse side, we may have to re-write significant amounts of code.
There is no way to know until we see that source. Just enjoy AOKP on 4.0.4 for now, or try one of the stock 4.1 ROMs that have been built (I am ... first time I've been off of AOKP since about December.)"