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

GNM_TURBO JIT + OC = 8+ mflops

Status
Not open for further replies.
flyinjoe13 said:
Dang, still no luck with this. Tried to flash it using Rom Manager and when I choose to Reboot into Recovery, I get a screen that flashes with a little Android icon and a triangle with an exclamation point in it and then the phone just reboots back to my homescreens like normal. I never actually get to the Recovey mode screen.
Click to expand...

That screen is actually the screen for the LG recovery. The clockwork recovery did not install. Everytime I've installed it, it takes two tries. Flash it again and you should be okay.
 
Hi all - I'm kind of new to all this but did apply this kernel to my new velocity3.0 ROM tonight. The linpack MFLOPS before was 3.99 - used SetCPU to OC at 878* and hit 8.25 first time. 8.345 the next...awesome!

(Oops, not 878. Meant 787)
 
Well I love Velocity Its Great!!!
I tried overclocling and JIT I have been able to OC to 748Mhz!!! WHOO HOO!!!

The only casualty of war that I have run across is you Tubes Widget starts poo pooing out. It just sits there loading loading loading.
It never shows the most viewed.

So I pulled my nandroid out that I made Previous to OC + JIT and everything works great again. So I tried it again. First putting OC on.
Once I had this done I checked and everything worked fine. You Tube working like a champ. Now I introduced Turbo4 JIT WHAM You Tube went away again. And yes I am using the proper JIT for use with the OC Kernal.

So Its a minor problem but still a problem. The ONLY one I have found mind you. Now Maybe I did somthing wrong I dunno. I mean you are supposed to just Flash over OC and JIT with the Zip flash on Drellisdees Recovery 1.2.4 right?

Thanks a bunch to everyone especially Trident and the Drell-Man.
 
drellisdee said:
Simple solution. Dont use F**KING CLOCKWORK!!! Use my recovery which seems to stick a whole lot better on this device. Also, kernel is set to 600mhz same as stock on boot unless you selected set on boot with setcpu to a higher speed (which is a big mistake). This was done as a saftey measure incase you picked a speed higher than you can handle. Try pulling your battery.

To fix recovery pull your battery and boot holding send + menu + power and let go when you see lg logo. Hopefully clockwork didn't fail you. If clockwork failed you you need to go into irc and get help installing my recovery with fastboot.
Click to expand...
lol clockwork really sucks.... seriously lol.
oh by the way ally rr might help you boot with his recovery, it uses fastboot... ive booted mine with it when clockwork fu#@ed me the first time around before drellisdee's clockwork zip was released.
 
myfishbear said:
lol clockwork really sucks.... seriously lol.
oh by the way ally rr might help you boot with his recovery, it uses fastboot... ive booted mine with it when clockwork fu#@ed me the first time around before drellisdee's clockwork zip was released.
Click to expand...

Just remeber that allyrr uses and outdated version of drellisdee's recovery.
 
So my phone can run 787mhz with no problems whatsoever. Am I ok to continue running it? Are there any risks of damaging my phone in the long run?
 
motorsport226 said:
So my phone can run 787mhz with no problems whatsoever. Am I ok to continue running it? Are there any risks of damaging my phone in the long run?
Click to expand...
yeah its fine it just uses more power so it might make your battery a bit weaker... bty what do you have installed on your ally? i might try it out cuz i had problems with 787.
 
myfishbear said:
yeah its fine it just uses more power so it might make your battery a bit weaker... bty what do you have installed on your ally? i might try it out cuz i had problems with 787.
Click to expand...

Nothing out of the ordinary...Velocity V0.3, LauncherPro. I try to keep apps at a minimum though.

If you don't run LP then I might start there, given it's huge responsiveness improvement over the stock Android launcher and the LG launcher it could be the reason why I'm stable at 787 or it could just be luck of the draw on the build quality of the phone.
 
yeah i have velocity 3 and turbo 4 kernel but i still cant seem to get past 600. the phone runs much smoother but still gets a little choppy. is there anything else i should know that i missed?
 
cryptic732 said:
yeah i have velocity 3 and turbo 4 kernel but i still cant seem to get past 600. the phone runs much smoother but still gets a little choppy. is there anything else i should know that i missed?
Click to expand...

Try using a different kernel. Using the JIT OC kernel you should get it up there.
 
motorsport226 said:
Nothing out of the ordinary...Velocity V0.3, LauncherPro. I try to keep apps at a minimum though.

If you don't run LP then I might start there, given it's huge responsiveness improvement over the stock Android launcher and the LG launcher it could be the reason why I'm stable at 787 or it could just be luck of the draw on the build quality of the phone.
Click to expand...
kk lol i was using the older v3turbo i changed it to the newer one and i dont get kernel panic anymore idk i had issues with velocity v3 and switched back to 2 (figured the problem was on my end). when v4 comes out i think ill upgrade again.
 
Stock velocity v.03
~ 4.7 mflops
With Turbo4 no OC
- 6.7 mflops
OC to 748 mhz
~ 7.5ish mflops
OC to 787 mhz
~ 8.9 mflops

Currently set 768 mhz:
Average mflops over 5 tests = 7.96
SetCPU Long bench:
- avg of 15 tests = 949 ms
- mean of 15 tests = 975 ms

Runs great. Quick and smooth. Very responsive. Will definitely be donating for this masterwork.
 
I had Velocity .3 and then yesterday, I applied the GNM_TURBO4.zip (first link). I first wiped just cache and dalvik cache and my phone got stuck on the VELOCITY loop, so I pulled the battery and went booted back into recovery, restored a backup I made just before applying, cleared cache, dalvik cache, and data. Everything seemed alright once I redownloaded all my apps and restored the backups for the apps that I made. Only problem is I can't seem to find the youtube app that came on my phone when I first flashed Velocity .3 (also the "flashlight" app was missing, but I can get that with anycut). So I guess I need the youtube apk or a good replacement one I can find on the market. Also, I think since the youtube app is missing, I can't view videos online anymore.
 
Math-Uhhh-Saurus said:
I had Velocity .3 and then yesterday, I applied the GNM_TURBO4.zip (first link). I first wiped just cache and dalvik cache and my phone got stuck on the VELOCITY loop, so I pulled the battery and went booted back into recovery, restored a backup I made just before applying, cleared cache, dalvik cache, and data. Everything seemed alright once I redownloaded all my apps and restored the backups for the apps that I made. Only problem is I can't seem to find the youtube app that came on my phone when I first flashed Velocity .3 (also the "flashlight" app was missing, but I can get that with anycut). So I guess I need the youtube apk or a good replacement one I can find on the market. Also, I think since the youtube app is missing, I can't view videos online anymore.
Click to expand...

Thats a rom issue as you lost the apps from wiping data.
 
Status
Not open for further replies.
Back
Top Bottom