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

[Verizon] [rom]jbsourcery v5.4-lte[06/07/13] jb4.2.2 The Final Call

Yep, completely clean install. No app reloading via titanium. I didn't use titanium at all this last go round. It's been stable since my last post, but the battery life is still pretty bad. Anyone flash any other kernels with this rom version yet?

Yeah, I usually give my phone a few days to settle into itself before I think about other kernels, just because I know I'm going to be changing and tweaking things, and I expect the battery to die a little faster at first. I'd say give it another day or two, see if it stabilizes, then maybe try another kernel. I'm still on stock, but I think I'm staying there until this weekend to be safe. I know I still can't stop messing with things!
 
Upvote 0
Yeah, I usually give my phone a few days to settle into itself before I think about other kernels, just because I know I'm going to be changing and tweaking things, and I expect the battery to die a little faster at first. I'd say give it another day or two, see if it stabilizes, then maybe try another kernel. I'm still on stock, but I think I'm staying there until this weekend to be safe. I know I still can't stop messing with things!


I'll give that a try. I did a third clean install realizing that I have only ever wiped cache, Dalvik, and then factory reset.... Never have I ever wiped system data before... Great tip from whoever earlier! Things seem to be running better than ever now. I'll keep an eye on the battery.
 
Upvote 0
I'll give that a try. I did a third clean install realizing that I have only ever wiped cache, Dalvik, and then factory reset.... Never have I ever wiped system data before... Great tip from whoever earlier! Things seem to be running better than ever now. I'll keep an eye on the battery.

Glad to hear it's going smoother :) I haven't had any issues lately either on mine, and still going through and finding all the little tweaks to play with. Every time I think I'm almost set, the next version drops lol. Of course, I COULD just not download the new one right away.....yeahright.
 
Upvote 0
I'll give that a try. I did a third clean install realizing that I have only ever wiped cache, Dalvik, and then factory reset.... Never have I ever wiped system data before... Great tip from whoever earlier! Things seem to be running better than ever now. I'll keep an eye on the battery.

Galaxy Nexus Superwipe is great for clean installs: you install the zip and it automatically formats /data, /cache, /Dalvik and /system. Then you can install the ROM/Gapps on a perfectly slicked phone. Highly recommended zip to have in memory :)
 
Upvote 0
:D

There is also a BT fix in JBSourcery Tools under Mods

I'm on the toroplus version of 5.2 - and BT is pretty bad (constant drops)
*It wasn't this bad with 5.1.x (5.1.1, 5.1.6, 5.1.8) - it would drop, but not every 5 minutes

I saw the BT Fix in JBS Tools under Mods (same file name - BTFixTest) - but when I tried to flash it, I got the following error in recovery
Assert failed: getprop("ro.product.device") == "
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/SourceryTools/mods/B

(looks like it is getting truncated at the end - I can't scroll to the right to see what the rest of the message is)

Do you know if the fix you provided in your previous link is specific only to the Verizon version? Or would it work on the Sprint version too?


Edit: looking at the script in the BTFIxTest, it is actually looking for the product.device or build.product to be toro - that explains the problem with the flash. Just wondering if the actual fix would work for toroplus though.
 
Upvote 0
Clean install, zebra gapps, market restore with TiBu restore of app data only and a few sideloaded apps, bunch of Sourcery mods.

Had a few crashes. First happened when I was on speaker phone and the screen had turned off. I plugged the phone into the charge mid-call and it crashed. Had to hold down the power button to reboot, so not a hot reboot. I have the phone set to have the screen turn on when it plugs in.

Similarly, another speaker phone call, not plugged in thsi time. After hang up it crashed and required a reboot. I have the phone set to return to the previous activity at the end of a call, which usually turns on the screen.

Finally, a call while on bluetoooth and navigating. Since I was driving, I didn't look, but I think the phone was on the dialer screen and not navigation, so the screen had turned off. Same thing as above -- at the end of the call, I had to reboot.

If someone can link me to instructions about how to generate and email a logcat, I'll be happy to do so as this seems pretty reproducible, at least on my phone.

Otherwise, things seem to be working well -- slick ROM as always!
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones