• 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.
drellisdee said:
What speed do you have kernel set at?
Click to expand...

I didn't have setcpu. I did find a way to get back in and installed setcpu. It is at 600 Mhz, but still having kernel panic issues. I am thinking about trying to install it again. Perhaps something went wrong for me in the initial flashing of JIT
 
Wow is all I can say. I finally took the plunge and flashed this kernel to my stock ROM, and I'm running it OC'd at 748 with no problems. Scoring 7.87MFLOPS at 748, and got an 8.259 out of it at 787, then it got a kernel panic. Maybe it'll hold at 748...time will tell.
Thanks drellisdee, donation will be coming next payday.
JL
 
Well, after a night of playing around with several apps and stress testing/benchmarking, I'm fairly certain that my Ally will run 768 solidly, and scores 8.376 MFLOPS @ 768. I have to say I'm very pleased with these results-that's at more than 2x faster than stock, which scored 3.929 MFLOPS.
JL
 
With velocity .2 befor installing update I got 3.044
Afterer update running at stock 600 I got 6.895

729- 7.862
748- 7.921
768- 8.428 then I got a kernel panic
 
Moinster said:
With velocity .2 befor installing update I got 3.044
Afterer update running at stock 600 I got 6.895

729- 7.862
748- 7.921
768- 8.428 then I got a kernel panic
Click to expand...


The kernel panics I got were at 600 Mhz. I am wondering if my phone just doesn't like the OC component. I am thinking about trying out JIT without the OC.
 
i am having an opposite problem per se... I flashed the turbo4 after using turbo3, and thats when my problems occured. FOr me, it depends on the day i guess. Like one day, I can run at 787 no prob, and others i cant even run at 600. I get random kernel panics. Some even on boot. ANd they all flash the black screen with white text saying what happened and my tables, but not even displaying it for more than a half a second. ANy idea? I had no problems with the first release.
 
Commandofern said:
i am having an opposite problem per se... I flashed the turbo4 after using turbo3, and thats when my problems occured. FOr me, it depends on the day i guess. Like one day, I can run at 787 no prob, and others i cant even run at 600. I get random kernel panics. Some even on boot. ANd they all flash the black screen with white text saying what happened and my tables, but not even displaying it for more than a half a second. ANy idea? I had no problems with the first release.
Click to expand...

Nothing changed except for the calculator.apk
 
You do not see the differnce? Look at settings > about phone and scroll down to Kernel Version. Mine is getitnowmarketing@laptop #1

I have flashed JIT + OC kernel.
 
Make sure you have the drivers from installing PDA Net, make sure USB debugging is ON
Code: 
C:\android-sdk-windows\tools>adb usb
* daemon not running. starting it now *
* daemon started successfully *
restarting in USB mode

C:\android-sdk-windows\tools>adb shell
$
 
can anyone post step by step instructions on how to install this kernal. I have a rooted ally but am not by any means a computer science guy. Just looking for a detailed way to install this kernal and see how it performs.
 
last5liter said:
can anyone post step by step instructions on how to install this kernal. I have a rooted ally but am not by any means a computer science guy. Just looking for a detailed way to install this kernal and see how it performs.
Click to expand...

The origianl post is pretty straight forward. In order to flash this kernel you need a custom recovery image. See this site for info on custom recoveries. Ally Custom Recoveries Info

Once you flash a custom recovery follow the instructions on the original post.
 
I have flashed the newest update of this w/kernal to my ally and cannot get it to load past the android boot animation, it hangs, and I have cleared all caches 3 time +

the only way i can get it to work is by formating my data, is there anything in data that could be causing this.

I have even advance restored my backups resoring all but data and it still will boot all the way, but as soon as I restore data, it will then hang on the boot animation.

does anyone know what in Data may cause this.

rom dapper duck 2nd build, clockwork recovery and have cleared all caches several times.

still have apps to sd which works for me on dapper duck and dont want to lose that by going to velocity

Thanks to all who my have input on this
 
doihaveto said:
I have flashed the newest update of this w/kernal to my ally and cannot get it to load past the android boot animation, it hangs, and I have cleared all caches 3 time +

the only way i can get it to work is by formating my data, is there anything in data that could be causing this.

I have even advance restored my backups resoring all but data and it still will boot all the way, but as soon as I restore data, it will then hang on the boot animation.

does anyone know what in Data may cause this.

rom dapper duck 2nd build, clockwork recovery and have cleared all caches several times.



still have apps to sd which works for me on dapper duck and dont want to lose that by going to velocity

Thanks to all who my have input on this
Click to expand...

Its the apps2sd. My boot.img is not apps2sd enabled. Try the no kernel one which will give you jit but no overclocking. If that fails he will need to incorporate it into rom and port my boot.img
 
ok so I will keep apps to sd because when i didn't have it I kept getting space low warnings,

so unless someone has some secret to get me more space for apps without apps to sd I will have to hold off on overclocking, what are the chances of havign overclocking and keeping the apps to sd in the future,

also dont understand that I heard apps to sd was unstable but i have been running it since dapper duck 1.4 build came out and have had little to no problems apparently related to apps to sd

lastly i cant seem to keep the radio update when I use the new update rom that is rooted then flash back to my custom rom it appears to lose the radio update

what should my phone say in the about phone baseband and sw versions if I have the new radio update

Thanks again for your inputs
 
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.
 
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...

The recovery isn't flashing. Common issue i see with clockwork. Just keep trying to re-flash the recovery.
 
Status
Not open for further replies.
Back
Top Bottom