• 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)

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

Yea Chief, I'll tell you this: I dirtied (my FIRST EVER IN YEARS) from 3.3 to 3.4 because I took so long to set up 3.3 that I didn't want to lose it. No problems whatsoever. I flashed 7/13 Gapps earlier tonight, flashed a Nates' Mods (Red) and that's it. The ROM has performed beautifully. I mean, there's really nothing else you can ask from Jake. It's smooth, has no issues (caveat to be added below) and I really can't think of anything else he can really do with it since he wanted it to be as close to AOSP stock as possible. This will be my DD for a long while.

Caveat: I'm just not sure what some of these people are doing, and that's the problem with the Internet. Some have spoken of issues with their WiFi. I can agree with that; the first time I flash a Jelly Belly ROM from Jake, I have to reset my extension in order for it to lock. Once it does however, that's it. I have oft suggested this in the thread. Others are having problems (still) with the GPS/Google Voice even though the LAST Gapps Jake pushed fixes these issues and even barring that, Kejar's version of Gapps fixed it already. Others are just having off the wall things going on like they can't access their SD card and other things that IMHO have nothing to do with Jelly Belly and everything to do with whatever they're doing when accessing recovery.

All I can say is that when in doubt: cleanly wipe everything, and reflash. I know it's a pain, but it's the only way to TRULY make sure you're not mixing things. Also, doing a simple 'Fix Permissions' (in TWRP and CWM it's in 'Advanced' --> 'Fix Permissions' has seemed to fix a lot of things. That's also in the OP of the RootsWiki thread. All in all, I'm super happy with this ROM and JB in general. I couldn't be happier, actually. Bugless Beast wasn't so bugless, but Jelly Belly is.
 
*sigh* has anyone been able to get Google Movies to work? Read recently that they allowed rooted streaming and many report that to be true. I keep getting "couldn't fetch license (error -1)" and to make matters worse it was after I bought 4 movies >.<


I'm gonna bump this..
 
Does anyone know of a mod that can separate the navigation volume and music volume? I like how the navigation attenuates the music but I would like for it to be louder. And I don't want to turn the music up loud only to have Ginny interrupt and bust my ear drums.
 
mine is working ok

did you try clearing data or cache in the app settings or undoing the updates and reupdate?

Nope, have not tried that...will give it a shot and see. Tried and can't get to app settings, because it will not log in. I went to apps and clears data there, but didn't do any good.

Negatory. Voice working fine here. Unless, are you talking about setting it up as voicemail? Because that I have not tried and can neither confirm or deny...but calls and messages working fine

What I am doing is opening up Google Voice and yes setting up the voicemail. I'm simply trying to sign in and it will not. I cannot get my voicemail messages to play.
 
One thing that I need to get used to is the voice output when I'm using maps. One thing I have noticed is that it waits till you're almost to the point where you need to turn and then it tells you. Since I done this out in the country and I knew the turn was coming up, but how does this work in a city setting? The older version would start telling me at quarter a mile away that my turn was coming up. Guess I'll check this again tomorrow when I take a trip to another town.

I tested my navigation tonight, and it was giving me 1/4 mile warnings and warnings right before the turn like it used to. Did you clean or dirty wipe? You on 3.4 with 7/12 GApps?
 
How is everybody's keyboard working? When I was on 2.5, the word prediction was working really well and the autocorrect picked up most of my mistakes. On 3.4, the word prediction is slowly starting to learn my typing style, but 2.5 seemed to know it right away. Also, this keyboard isn't autocorrecting at all. If I type a word wrong, I have to click one of the words to the left or right of the suggestion bar. For example, if I type "dont" and then hit spacebar, it will insert "dont". it gives "don't" as an option to click and insert, but hitting spacebar inserts the incorrect spelling. On 2.5 (and every other Android ROM, version, and phone) it corrects basic misspellings by hitting spacebar.

I've gone through all the keyboard settings (there are a lot and are sort of convoluted). I've turned all all autocorrect settings, cranked it up to very aggressive, done everything I can think of in the settings. The weird thing is that I have all my keyboard settings exactly how they were on 2.5 and it was working perfectly...

EDIT: I cleared data from the keyboard and the autocorrect is working again. I'll have to wait and see how fast the word prediction learns me. I think that's a really cool feature.
 
How is everybody's keyboard working? When I was on 2.5, the word prediction was working really well and the autocorrect picked up most of my mistakes. On 3.4, the word prediction is slowly starting to learn my typing style, but 2.5 seemed to know it right away. Also, this keyboard isn't autocorrecting at all. If I type a word wrong, I have to click one of the words to the left or right of the suggestion bar. For example, if I type "dont" and then hit spacebar, it will insert "dont". it gives "don't" as an option to click and insert, but hitting spacebar inserts the incorrect spelling. On 2.5 (and every other Android ROM, version, and phone) it corrects basic misspellings by hitting spacebar.

I've gone through all the keyboard settings (there are a lot and are sort of convoluted). I've turned all all autocorrect settings, cranked it up to very aggressive, done everything I can think of in the settings. The weird thing is that I have all my keyboard settings exactly how they were on 2.5 and it was working perfectly...

EDIT: I cleared data from the keyboard and the autocorrect is working again. I'll have to wait and see how fast the word prediction learns me. I think that's a really cool feature.


I agree NSuth it is great. I use aggressive with next word predic off in adv settings. And tx for pointing out clear cache

Happy burpday Troop hope it's an awesome one! :D
 
3 known and repeated bugs for me:

1. Can't change the amount of time after screen turns off that face unlock takes effect. It stays at 5 seconds regardless of what I choose.

2. Can't get owner info to stick. I'll type of in, but whenever I go back, it goes back to blank.

3. Google search FC's when I try to interact with the results. For example, I search for "convert 5 kilometers to miles." The results pop right up and gives me the option to adjust the number of miles or kilometers. But as soon as I touch either the miles or kilometers, it FC's.
 
3 known and repeated bugs for me:

1. Can't change the amount of time after screen turns off that face unlock takes effect. It stays at 5 seconds regardless of what I choose.

2. Can't get owner info to stick. I'll type of in, but whenever I go back, it goes back to blank.

3. Google search FC's when I try to interact with the results. For example, I search for "convert 5 kilometers to miles." The results pop right up and gives me the option to adjust the number of miles or kilometers. But as soon as I touch either the miles or kilometers, it FC's.


Don't use facelock but will test shortly and report back. # 2 and 3 work without issue on my end just tested several times to be sure ;)
 
#1 works perfectly for me as well. You coming from clean wipe?

My thinking is that since 3.4 will be a (somewhat) milestone build, I'm going to clean flash again and hope it fixes the issues. I really want 3.4 to work like a milestone build!
 
Hope your birthday was great Trooper....

3.4 is working great! I did a dirty wipe from 3.3...but I already had the JB Boot loader, and it appears that something was fixed since all of my inverted apps work perfectly. Have not had a single bug or issue at all!! Made my nandroid....this is definitely a Daily Driver build for me!!
 
Wow. Jellybean notifications changed so much that now notifications can always persist on top (meaning without updating themselves). Now Power Controls is exactly like AOKP toggles because they're always on top.
 
Hope your birthday was great Trooper....

3.4 is working great! I did a dirty wipe from 3.3...but I already had the JB Boot loader, and it appears that something was fixed since all of my inverted apps work perfectly. Have not had a single bug or issue at all!! Made my nandroid....this is definitely a Daily Driver build for me!!

Could you tell me how to get the inverted apps installed? I tried but it didn't work.
 
Back
Top Bottom