Get your Jelly Bean...NOW!

[ObieNobie]

I'm having trouble with my Gps. I heard it was a comment problem. I'm on vanirbean v5. Is there a fix I can flash or should I change some setting?

Sent from my Galaxy Nexus using Tapatalk 2

 

[ObieNobie]

Ignore my last post. I now see we are on v8.

Sent from my Galaxy Nexus using Tapatalk 2

 

[mach330]

Does any rom work with cwmm touch?

 

[sbenson]

I'm having trouble with my Gps. I heard it was a comment problem. I'm on vanirbean v5. Is there a fix I can flash or should I change some setting?

Sent from my Galaxy Nexus using Tapatalk 2

GPS is a common issue across all JB "roms" and will continue to be so, until Google releases the official source (hopefully next week).

 

[Trusstopher]

GPS is a common issue across all JB "roms" and will continue to be so, until Google releases the official source (hopefully next week).

Are you still sticking with Jelly Belly? I'm up to 2.2 and about to step to 2.5... a small part of me wonders what the others have to offer at this point but another part of me is pretty sure that nothing can be as smooth as what jelly belly has been for me.

 

[sbenson]

Are you still sticking with Jelly Belly? I'm up to 2.2 and about to step to 2.5... a small part of me wonders what the others have to offer at this point but another part of me is pretty sure that nothing can be as smooth as what jelly belly has been for me.

I've been following Jelly Belly pretty close and dirty flashing each new build. I'm on the current 2.5 with Franco kernel (#215) and I'm pretty happy.

Now that the newness has worn off a bit, I'm temped to flash back to ICS just so I can see the difference again...nah, no way

 

[sbenson]

Best case scenario, Google pushes source next week. GSM Nexus will get the update, my Wifi Xoom will get the update and the dev community goes nuts on the source.

 

[pc747]

Best case scenario, Google pushes source next week. GSM Nexus will get the update, my Wifi Xoom will get the update and the dev community goes nuts on the source.

Like that scenario, but better case scenario is if all that happened this week. My nexus is getting a taste for aokp flavored jbs.

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

 

[Hugg727]

I've been following Jelly Belly pretty close and dirty flashing each new build. I'm on the current 2.5 with Franco kernel (#215) and I'm pretty happy.

Now that the newness has worn off a bit, I'm temped to flash back to ICS just so I can see the difference again...nah, no way

I have been flashing Superwipe before I flash JB each time. Is that still considered "Dirty"?

 

[sbenson]

I have been flashing Superwipe before I flash JB each time. Is that still considered "Dirty"?

No, superwipe simulates a full wipe. Meaning you have to set up your phone from scratch each time. Use this if you're having issues or are switching to a different rom.

A dirty flash is just wiping your cache and dalvik. When you boot up, all your data and apps are still there. Use this if you're upgrading within the same rom (i.e. upgrading from 2.4 --> 2.5), unless the developing says otherwise. I've dirty flashed every build Jelly Belly since 1.7 with zero issues.

A super dirty flash would be wiping absolutely nothing. Not recommended. Use this if you like living dangerously. No matter what you do, make sure you have a nandroid backup to fall back on.

 

[sbenson]

FYI, for those on Jelly Belly, it appears the deep sleep bug has finally been squashed. I'm able to get full deep sleep straight out of a reboot now, without having to open Maps. This was still broken on 2.4 and every single JB Rom I'd tried before, but 2.5 seems to be good so far.

 

[Hugg727]

No, superwipe simulates a full wipe. Meaning you have to set up your phone from scratch each time. Use this if you're having issues or are switching to a different rom.

A dirty flash is just wiping your cache and dalvik. When you boot up, all your data and apps are still there. Use this if you're upgrading within the same rom (i.e. upgrading from 2.4 --> 2.5), unless the developing says otherwise. I've dirty flashed every build Jelly Belly since 1.7 with zero issues.

A super dirty flash would be wiping absolutely nothing. Not recommended. Use this if you like living dangerously. No matter what you do, make sure you have a nandroid backup to fall back on.

Thanks, thats what I thought.

I have been wiping the davlik/cache and then flashing superwipe. I can believe how fast this thing comes back. the entire process is done in 10 minutes!

 

[sbenson]

Thanks, thats what I thought.

I have been wiping the davlik/cache and then flashing superwipe. I can believe how fast this thing comes back. the entire process is done in 10 minutes!

If you flash superwipe, you don't need to wipe the others...

Sent from my Galaxy Nexus using Tapatalk 2

 

[pc747]

Like that scenario, but better case scenario is if all that happened this week. My nexus is getting a taste for aokp flavored jbs.

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

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

 

[sbenson]

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

Yes! Source tonight! That means I'll have a source built ROM waiting for me to flash in the morning!

Sent from my Galaxy Nexus using Tapatalk 2