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

Hi again, folks!

Okay, full wipe and 3.2 flash with gapps 7-11 and TiBU restore.

Face unlock STILL doesn't work. :(
GPS locked in 15 seconds. :D
Google Now lady speaks... Navigation lady does not :(
BT works. BT voice dial works, but "speak now" lady still doesn't talk. I still have to time it and then tell it who to call on my own :(
1% Battery and Power Menu mods work great, as does Lean Kernel :)

Still exploring...

Where are you getting Lean Kernel? I'm finding the volume to still be kind of low, thinking that the Kernel might help.
 
Hey Chief saw you say Google Now lady is talking. What build?

3.2

BUT....
Nav is not talking, nor is the "speak now" prompt on BT voice dial.

And now I'm noticing that Chrome-to-Phone's not working? Oh this isn't gonna fly. Maybe a reboot will help.

EDIT: A reboot DIDN'T help. No Chrome-to-Phone. I may revert back to 3.1 unless these things are resolved in short order... this is ridiculous: even for an alpha ROM.
 
I've held off flashing 3.2 because I want it in the OP. At this point is it even worth it to flash it? Think he's planning on 3.3 soon anyway?
 
Yeah let us know. Did it happen on 3.0 and 3.1 or just 3.0? So you went clean from aokp straight to JB jelly belly 3.0 with a clean wipe prior top flashing JB right
Posting from AOKP. Sensor appears to be hardware related. Have insurance but $100 replacement is ouch!
 
I've held off flashing 3.2 because I want it in the OP. At this point is it even worth it to flash it? Think he's planning on 3.3 soon anyway?

No. I wouldn't. This ROM is too unpredictable.

On some phones everything works. On some phones a few things don't work. Same procedure, same wipe, same ROM and gapps. It's bizarre. Hopefully the NEXT version will stabilize things a little and normal it out.

We'll see. But that's part of the risk you take being on the bleeding edge of technology :)
 
i Ran All of The Previous jellbelly roms Below 3.0 With No Issues. Clean wiped Prior To 3.0.
WOw $100 dang sorry to hear that :(

Wow, you've been a huge help so far. They are installing as we speak (fingers crossed!)
Awesome let me know how it goes....up and running with 4 bars of 4G yet? :D

Not sure about a kernel fixing volume, but stranger things have happened. Here you go:

:)
Kernels and volume are directly related Chief. I don't know how or why though :p
 
I'm on 3.0 and the only issue I have is the google now doesn't search. Got really good battery life today on 4G though. I'm thinking of going to 3.1.
 
Awesome let me know how it goes....up and running with 4 bars of 4G yet? :D
Well it's up and running but no changes in bars, at least in my apartment (I only get two of 4G). My concern is more about the 3G to 4G handoffs and issues with data loss. I travel a lot for work so I should know more tomorrow. Thanks again!
 
Does anyone still have a link to v2.6? I'm on 2.4 and my GPS,nav is not working well at all, but wanna hold off for a week on the aosp version bugs to be worked out. thanks in advance!
 
I see voice nav is still not speaking. I'm sure it'll be fixed though. Thanks for the update IBT

Checking it out now, just got it loaded up, apps are optimizing. I noticed it fixes an adb issue...I couldn't adb pull on the last build or 2, will be trying that out, checking out face unlock and a few other things. Reporting back in a few.
 
Faster bootup. Face unlock still a no go. Faster transitions between menus (if you can believe that. It's like lightning now). ADB issues do in fact seem to be remedied. Too tired to check anything else out tonight. It's getting close but there's still a few minor issues to be addressed. This is the best build yet.
 
OK, so I am ready to make the jump from 2.5 to 3.3. I have downloaded TWRP, the TWRP recovery image(?), 3.3 zip, and 7/11 gapps.

I currently have CWMR as my recovery and heard that installing TWRP is a better choice. With that being said, I went ahead and made a Nandroid of my phone in its current state.

What is my next step?
 
Back
Top Bottom