• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [ROM]JDX (formerly Jelly Belly) AOSP+ - v15 (7/28)

Neither dirty flash nor dirty wipe sound good. But regardless, I dirty flashed from 3.3 to 3.4 and I can't report any issues. Deep sleep is 94%, GPS locks on fast as long as I'm near a window or outside, Nav works with names unlike 3.3, face unlock works, no signal drop, native tether works.

I download the verizon login client in order to use the my verizon app. Is it possible that this will cause tethering to show up on my bill?
 
iowabowtech said:
So has anybody been following the Rootz thread today? Any indication of future efforts?
Click to expand...

IBT, I'm following pretty much every single mind-numbing post in Rootz. I have no indication that Jake is feverishly working on 3.5, although I suspect that he is. Not sure what else he could do to it: it's a nearly perfect stock ROM as it is.

I am sorry, saddened and slightly shocked that fellow Androiders here are having so many problems flashing Jelly Belly. My one issue was easily resolved by clearing the app data. Tether works, wifi works... everything just works.

Unless 3.5 has some really tangible improvements, I will likely stay right here for awhile.

Of course, that's what I said about 3.3 after I got it running right... and look how long THAT lasted :p
 
I think chief mentioned this earlier, but if Nav voice isn't working or is taking two attempts, go into settings/apps/all/maps and clear data. Worked like a charm
 
I just had something strange happen on my way home from work. First the background...I have had 3.4 installed since last night. I flashed twrp 2.2 today. I tested nav on the way home. That worked fine. I tested volume levels with nav and google music. I lose 4G and go through a 4G/3G dead zone before I get to my house. Music dropped out during this time. When I got to my house 2 minutes later, I switched to wifi due to low signal which is normal. Just after I switched to wifi I noticed an error from google music due to no signal (probably because I signal on the way home). I then received an email and the phone randomly rebooted. I gave so much information hoping that maybe someone would have an idea as to which event caused it to crash.
 
I really don't know what I did!

Yes I pulled my battery but that was after I shut down. I have two batteries and was swapping out for the freshly charged battery. Then it just wouldn't boot.

I tried restoring a nandroid, which failed at data. Tried a different one, no go!

So I wiped and flashed b40 AOKP. Bootloop!

Had to change recovery to twrp so I could mount USB and pull all files from SD as I hadn't backed up. Then flashed back to stock 4.0.4. So yeah, I am up and running but boy am I missing a lot. All my stuff is on my computer and I am worn from staying up 3 extra hours to save my phone just to set an alarm to sleep for two hours and have a functioning phone!

I feel like flashing jellybelly again since I don't have any files to lose so if I had to flash back I could do so without all the angst.

Just feel like something hasn't yet been discovered about Jelly Bean in terms of the data corruption that is occurring. We never dealt with long boot times and corrupt partitions until now. And this has occurred with folks who flashed the nandroid hack as well as the recent AOSP builds. Something tells me not everything is as official as it seems.

My 2 cents!

jmar
 
Well I decided to revert back to stock and then re-download the bootloader, 3.4 and gapps to see if that will help out with my prior issue. Well after doing all of that I downloaded some of my previous apps I lost during all of this and went to sign into Google Now. Well after going through all of the Yes answers and it starts to load up my cards for the first time it caused my maps to force close. Thought it was odd so I closed out Google Now and went into maps and it started up fine w/o any force closes. Went back into Google Now and no issues. I really think my phone is jinxed because of today LOL...
 
You must log in or register to reply here.
Back
Top Bottom