GNM_TURBO JIT + OC = 8+ mflops

[getitnowmarketing]

Forgot to check mflops prior to new kernel.
With kernel, 6.627 on a 12.65 second test.
WHere can I find a free version of set cpu, even if its a demo or limited... I can only find the paid one in the market....?
Also, Is it safe to overclock??? like will it make my phone start smoking and blow up eventually like in the next 2 years?

Google keywords xda setcpu. The dev gives it free to xda members. Well worth the $1.99 if you believe in supporting an awesome app.

 

[Commandofern]

i got a version of set cpu... v 1.5.0a
I cant get it to detect frequencies. any help?

 

[cb3p0]

just got into the top ten, only one ther running at 768mhz, yeah baby, check me out

 

[cb3p0]

nvmd i got taken off that list quick

 

[cb3p0]

we back in there lol, 8.684 on 768 mhz baby

 

[jCorrr]

Just topped out at 9.106 linpack score. OC to 787MHz, though.

*Proof*

 

[cb3p0]

Just topped out at 9.106 linpack score. OC to 787MHz, though.

*Proof*

u kicked me out the top ten lol. did u get a kernel panic

 

[jCorrr]

u kicked me out the top ten lol. did u get a kernel panic

Nah. My Ally runs fine on 787MHz. Running smoother than ever, I switched to rooting after constant annoyance by persistent lag. Never gonna go back. Love you Drellisdee.

 

[Commandofern]

ok. so i was in set cpu. got it from xda v 2.0.3 or something like that. the newest there. I accidentally slid it to 787 and it instantly gave me a kernel panic. now, when i try to go back into set cpu to change it, it starts, fc's then kernel panic. how can i fix this. i was able to run 768 fine and pushed it and cant change it now.

 

[getitnowmarketing]

ok. so i was in set cpu. got it from xda v 2.0.3 or something like that. the newest there. I accidentally slid it to 787 and it instantly gave me a kernel panic. now, when i try to go back into set cpu to change it, it starts, fc's then kernel panic. how can i fix this. i was able to run 768 fine and pushed it and cant change it now.

Uninstall reinstall setcpu

 

[jCorrr]

ok. so i was in set cpu. got it from xda v 2.0.3 or something like that. the newest there. I accidentally slid it to 787 and it instantly gave me a kernel panic. now, when i try to go back into set cpu to change it, it starts, fc's then kernel panic. how can i fix this. i was able to run 768 fine and pushed it and cant change it now.

Restart your device? Unless you put set on boot, which I think the highest boot MHz is 600, which shouldn't give you kernel panic. If you did set on boot, and somehow it stayed at 787MHz through booting, try to open setCPU and quick as possible when first booting the phone, and slide it down as far as possible and it shouldn't force close so you can reset your CPU clock.

 

[Commandofern]

i got it. thanks. I love all of you simply because not only are you smart and BA, you guys are accepting of anyone with a question. I have been on forums where you ask andy question and you might as well have shot someone. THanks though.

 

[jCorrr]

i got it. thanks. I love all of you simply because not only are you smart and BA, you guys are accepting of anyone with a question. I have been on forums where you ask andy question and you might as well have shot someone. THanks though.

No problem, also, make sure to look up some profile tips in setCPU. It's a battery lifesaver. If you have any further problems with anything feel free to stop on the LG Ally IRC Channel, and see if anyones in there to help you out, couple people walked me through setting up my rooting process and flashing a ROM and kernel.

 

[Commandofern]

wierdest thing, in my opinion, just ran a stress test at 787 with no errors for 111833ms. Linpack is 8.277mflops over 10.13 s. Thanks. would the reason im not getting a kernel panic possibly due to just what processes could be running that make it panic then five minutes later let it run fine?

 

[Commandofern]

Ok, so I did a bunch of testing between 787 and 768 and don't really notice any differences. THe linpack tests for both (for me) both average out to be around 8 mflops, give or take .5 here or there. ANy ideas? Also, what are your thoughts on profiles for setcpu?

 

[jCorrr]

Ok, so I did a bunch of testing between 787 and 768 and don't really notice any differences. THe linpack tests for both (for me) both average out to be around 8 mflops, give or take .5 here or there. ANy ideas? Also, what are your thoughts on profiles for setcpu?

If your up to it, you might wanna jump into the LG Ally IRC Channel, so I can private instant message you and we will debate back and forth about what you should be running in your profile tab.

 

[getitnowmarketing]

Well since froyo didnt hit mid september I guess this will bridge the gap in performance for the next several months.

 

[jCorrr]

Well since froyo didnt hit mid september I guess this will bridge the gap in performance for the next several months.

Yes, indeed it will. You've made my life so much easier already man, very greatful. With 2.2 and a ROM and Kernel like this one I'm sure us Ally users will be a part of the speedy top android devices

 

[darkxsun]

Well since froyo didnt hit mid september I guess this will bridge the gap in performance for the next several months.

Agreed x 1000.

Thanks again.

 

[jetblack]

I've tried applying this twice using drellisdee's recovery 1.2.3, but both times I've received a "No signature" error. I saw that some folks had this happen with Velocity 0.2 using 1.2.2, which is why I am using 1.2.3. I was able to apply Velocity 0.2 just fine.

Has anyone else had this happen? Should I just turn off signature verification, or is this indicative of some other problem.

 

[Commandofern]

drellisdee, I honestly do not know how to thank you. I would donate but I have no paypal or anything like that. Still, if there is anything that I may be able to help with please let me know. thanks

 

[getitnowmarketing]

I've tried applying this twice using drellisdee's recovery 1.2.3, but both times I've received a "No signature" error. I saw that some folks had this happen with Velocity 0.2 using 1.2.2, which is why I am using 1.2.3. I was able to apply Velocity 0.2 just fine.

Has anyone else had this happen? Should I just turn off signature verification, or is this indicative of some other problem.

That was my fault as I forgot to sign the zip. Untill I upload a new one just turn signature verification off on zips. The next one will be signed.

 

[jetblack]

That was my fault as I forgot to sign the zip. Untill I upload a new one just turn signature verification off on zips. The next one will be signed.

No worries, drellisdee - and thanks. I just wanted to be sure it was expected behavior. It installed fine after turning off signature verification.

 

[PowerBomb]

Wow, someone got into the 9s! Nice.

Been messing with my phone most of the evening, clearly much more responsive.

 

[death2all110]

so far so good 787 maxed =)

heavy usage.

battery temp even decreased!