Jelly Bean source code released!

[moyajaya]

Can't wait till we get a taste of this!

https://groups.google.com/forum/m/#!topic/android-building/XBYeD-bhk1o

UPDATE: here is the official CyanogenMod statement:

 

[suhas_greeneyes]

Gr8 news..hope it ll fix emmc bug..
But couldnt find nything for our NOTE
Sent from my GT-N7000 using xda app-developers app

 

[mbh87]

Gr8 news..hope it ll fix emmc bug..
But couldnt find nything for our NOTE
Sent from my GT-N7000 using xda app-developers app

AOSP ROMs already dont have the brick bug. It will be a long time before Samsung pushes out a touchwiz jelly bean OTA.

 

[LordManhattan]

Hell yeah! Let's get to work people!

Sent from my GT-N7000 using xda premium

 

[msedek]

Wonder how long till the first aosp jb rom for us

Sent from my GT-N7000 using xda premium

 

[mbh87]

My guess is not until CM nightly builds are JB since all source ROMs are based on that for are phone.

 

[ipguy]

My guess is not until CM nightly builds are JB since all source ROMs are based on that for are phone.

That didn't make any sense to me

 

[LordManhattan]

The Cyanogenmod team won't start on JB (CM10) until the final release of CM9 is out. That's what i read.

But the changes (code wise) aren't that big between ICS and JB like GB and ICS, so i bet it won't take that long until we see an alpha release of CM10.

Sent from my GT-N7000 using xda premium

 

[emprize]

The Cyanogenmod team won't start on JB (CM10) until the final release of CM9 is out. That's what i read.

But the changes (code wise) aren't that big between ICS and JB like GB and ICS, so i bet it won't take that long until we see an alpha release of CM10.

Sent from my GT-N7000 using xda premium

Fair enough but not what i expected, lol
Who cares about cm9 if cm10 released

Sent from my GT-N7000 using XDA Premium HD app

 

[clandestino123]

The Cyanogenmod team won't start on JB (CM10) until the final release of CM9 is out. That's what i read.

Wonder how they'll decide when it is "final"? when all known bugs are fixed ?

 

[mbh87]

The Cyanogenmod team won't start on JB (CM10) until the final release of CM9 is out. That's what i read.

Sent from my GT-N7000 using xda premium

Doubtful, they always start on new versions of android while still perfecting the previous version.

 

[CoopZor]

Wonder how they'll decide when it is "final"? when all known bugs are fixed ?

CM9 is perfect for me already, what is not working then ?

 

[Hitschman]

According to their Google+ post they will start working on it right away and in paralell to CM9.

Sent from my GT-N7000 using xda app-developers app

 

[Kangal]

Hell yeah! Let's get to work people!

Sent from my GT-N7000 using xda premium

Wrong.

I read somewhere (their twitter I think) they will start it right away.
CM10 Nightlies will be arriving soon (probably tonight), but they aren't meant to be safe or official.

All official CM9 devices will be CM10 from the get-go. That will be the official CM10.
They will work on CM9 up until CM9 gets to its first milestone, think of it as rc1, or what comes after beta (gamma?).

From that point on it will be like this:
CM6 = discontinued, unofficially supported
CM7 = officially supported and unofficially supported
CM8 = non-existant
CM9 = discontinued, unofficially supported
CM10+ = officially supported and unofficially supported

I'm more concerned about what they're going to do for CM10
They've discussed merging ParanoidAndroid and AOKP into CM, its likely that they could be introduced once CM10 gets stable, making it into CM10.1
Though it would be an awesome surprise if they manage to do it for CM10 in the first go... I'm having trouble leaving AOKP or PA for CM

 

[slitex]

Quote from Cyanogenmod on G+

"CM7, 9, and 10 at the same time?

Our goal is to release a stable CM 9.0.0 (and any needed .1’s). After that, we will work on CM7 and CM10 only. As stated above, CM9 devices are highly likely to get CM10, so maintaining a separate class of devices for CM9 only is inefficient. "

 

[moyajaya]

OP updated with official word from CyanogemMod.

 

[baz77]

Actually they do have the bug, but have what triggers it switched off.
Currently all phones have the bug as its a firmware of emmc chip issue. Its prevented triggering, not fixing, firmware issue on emmc chip as how I understand it.

Sent from my GT-N7000 using Tapatalk 2