• 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

I've only ever seen the delay in roms that have custom lock screen targets. I'm running Eclipse 3.1 right now, it doesn't have lock screen targets as a customization and I get no delay at the lock screen.
 
For those of you on this "seeder kick". Flash the new lean kernel. IMO has implemented some of that feature. Seems to work...I never notice many issues to begin with... But it seems to work
 
I'm on the "Seeder kick" and it has vastly improved the laggy behavior I was experiencing when a screen opens, switches between apps. It doesn't speed up the device or load times, it just makes it seem that way since the lag is omitted. At least that's my experience.
 
I'm still on Sourcery 3.2/Android 4.1.2 and I don't have any lockscreen lag. I've always had the proximity sensor issue even before I rooted and rom'd this phone, at least as far as the dialer turning off as my other fingers are longer than my index finger. No other proximity issues, though.

I am happy with Sourcery 3.2, have installed the 4.2 camera and for me see no reason to change at this time.

Thanks!:):smokingsomb:
 
teddyearp said:
I'm still on Sourcery 3.2/Android 4.1.2 and I don't have any lockscreen lag. I've always had the proximity sensor issue even before I rooted and rom'd this phone, at least as far as the dialer turning off as my other fingers are longer than my index finger. No other proximity issues, though.

I am happy with Sourcery 3.2, have installed the 4.2 camera and for me see no reason to change at this time.

Thanks!:):smokingsomb:
Click to expand...

HAHA, im still on JBS 3.2 as well. I dont see the true advantage of 4.2 just yet. I dont think Google does either to be 100% honest! Im just sitting tight till the next 'true' update comes to android...
 
Excuse my ignorant question (hey, I've been working like a dog for a while :o):
I'm on build V4.0, is there a newer one? Looking through your site, I couldn't find one. Thanks!
 
Just installed the theme MMS from tools. When selecting a contact the text is also black. Is this known...or a fix available? Thanks
 
I have a replacement Galaxy Nexus that I've successfully rooted, but I can't flash JBSourcery with TWRP or CWM no matter what I try. I get the the error message:

assert failed getprop ro.product.device

Any suggestions?
 
nordy420 said:
Reading your post, I noticed that it says you successful rooted. Did you happen to unlock your nexus also. Maybe the custom kernals are messing with your phone???
Click to expand...

Yes, it's unlocked. I've tried going back to stock and rerooting it and that still didn't help. I've tried it with and without any custom kernels. :mad:
 
mrichick said:
I seem to remember Gapi having the same problem with all jb roms when they first came out? I know he resolved eventually but don't remember how
Click to expand...

Gapi was able to flash the roms, but ran into issues with bootloops after successful flashes of compatible JB roms. Once Verizon released the OTA for 4.1.1, I believe Gapi exchanged it for another device and has been fine ever since. This error that keeps getting thrown by Ron is an unusual one. I've done some searches and the remedy seems to be wide stretch from complete reformatting of the sd away from fat32, deleting assert checks in the script from within the zip file, or trying a different recovery.
 
When I set certain toggles in the notification bar they are blank squares. All of them work for me except the WiFi one. It is a blank square when I put it in the toggles.
 
Odd problem just cropped up, not sure if ROM related or not.

Was on a phone call with my ISP (a whole other bucket of worms!), which required typing in my account number. I went to open up the keypad, and found my screen was unresponsive to any touch input. The screen was not frozen (clock and call timer still functioned), but no screen touches worked. Eventually did a battery pull to reboot, as I couldn't hit "Reboot" in the power menu. Phone is working fine after reboot.

If it's a random one-off thing, I'm not concerned. If others have seen this, I'd like to figure out some ways to avoid it, as it's kind of really annoying...
 
iwoloschin said:
Odd problem just cropped up, not sure if ROM related or not.

Was on a phone call with my ISP (a whole other bucket of worms!), which required typing in my account number. I went to open up the keypad, and found my screen was unresponsive to any touch input. The screen was not frozen (clock and call timer still functioned), but no screen touches worked. Eventually did a battery pull to reboot, as I couldn't hit "Reboot" in the power menu. Phone is working fine after reboot.

If it's a random one-off thing, I'm not concerned. If others have seen this, I'd like to figure out some ways to avoid it, as it's kind of really annoying...
Click to expand...

...and my phone just asked to update PGM Nexus, wit the "What's New" section mentioning screen problems while in a call. Rebooting the phone now with new PGM Nexus installed, hopefully this was the problem.
 
You must log in or register to reply here.
Back
Top Bottom