Seditec
Well-known member
Mine was doing it for a while with high clocking but since I updated I haven't bothered to clock that far up again
I was clocked to 864
Sent from my LS670
I was clocked to 864
Sent from my LS670
Mine was doing it for a while with high clocking but since I updated I haven't bothered to clock that far up again
I was clocked to 864
Sent from my LS670
Wow that's high. I can't clock over 806 on my v lol
Sent from my LG-VM670 using Tapatalk 2
Hmm, it's currently at 787. I'll try putting it back to 600 and see if that helps. Thanks.Mine was doing it for a while with high clocking but since I updated I haven't bothered to clock that far up again
I was clocked to 864
Apart from the lock screen issue (which may or may not be fixed now), this rom has been great. I'm using this on the Optimus V.
I don't really have deep sleep issues anymore, I did until I tried this, but now it seems to be fixed. The only issue I see now is the clock lag, but I don't mind that because I don't use an alarm.
Thanks theKraven.
My phone won't boot after flashing Alpha19. It's stuck at the LG screen.
EDIT: When installing it has the following error:
E:Corrupt file: system/usr/icu/icudt461.dat
E:signature verification failed
EDIT2: After toggling the security checks it successfully installed. I don't recall having to ever do that before.
EDIT3: Now it's stuck at the loading screen that shows the lanky android guy with the glowing circle on his chest.
ahh thank you. changed that line I'll see how it is. by the way, not sure if this is a problem.. I noticed there are two folders in /system/modules. one is a folder the 35 test kernel and the other is the 36 kernel. both have the same items inside. should I delete the older one? I thought it was supposed to be deleted as I installed a newer one. unless they rely on each other then is kool lols
EDIT: Also, is there any particular reason why this: ☠ [APK][Tweaks & Mods] █ PIMP MY ROM █ v1.9.1 {Any Device // Any Rom}[ALPHA][WIP] ☠ - xda-developers is causing me to get stuck on boot? Perhaps the init.d setup in this ROM isn't compatible with it? I don't even get past the first set of tweaks after reboot.
Mine was doing it for a while with high clocking but since I updated I haven't bothered to clock that far up again
I was clocked to 864