Discussion Group: Overclocking NRG ROM

[DaveTN]

Originally Posted by stab244

This does work on battery power right? I've heard/read on the XDA topic (well the general XDA topic for OCing on a bunch of devices) that you need to be on AC power to have it work. I don't want to be tied to my computer all day (especially since school starts now).

If you use the mortscript it works on battery power just fine. There is a message in the overclocking app that says that it works on AC power only. That is more informational. If you use the methods described in the links above, all should work fine for you.

I'm currently running NRG 8/18 Standard 23xxx at a conservative 729 and things are working great. Its too soon since my flash to say anything about battery life but everything is very snappy on this non-cookie build.

David

[stab244]

Originally Posted by DaveTN

If you use the mortscript it works on battery power just fine. There is a message in the overclocking app that says that it works on AC power only. That is more informational. If you use the methods described in the links above, all should work fine for you.

I'm currently running NRG 8/18 Standard 23xxx at a conservative 729 and things are working great. Its too soon since my flash to say anything about battery life but everything is very snappy on this non-cookie build.

David

Okay then. Really tempted to try it out now. Thank you.

[Larkstarr]

It looks like the "conservative" 729 is the best my phone can handle. anything higher and the device freezes, usually when typing. I'm going to start increasing the interval time from 1000 ms to higher, see if it goes into the SOD.

[Maxx134]

Good News:
Sense no longer freeze/crash for me as easy on Aug25 and it no longer leaves a "application Data" folder on the Storage card.
You should be able to clock higher without Sense problams.
But still can have Opera closing issue.

[IIVisionII]

Thanks for the no SOD on call cab. Seems to have fixed all my ocing probs. Running at 710 now with no problems. Tried 748 and get lockups in windows.

[DaveTN]

Trying out NRG's latest 9/4 24xxx CHT at 729. Going to be on vacation for a few days so I hope all works well.

I just got two new 1800 mah extended batteries so I'll break them in too.

David

[sl8763]

I'm running Energy's CHT ROM (Cookie Energy Style) dated August 28th 2010. I am using OCT v.1.5 and using these settings:

OCT V1.5 @ 768
2000ms interval
1 steps (so it idles at 384)
100 load max
0 load min
80 jump max
3 jump min

I've only been running it for a day but I've really tried to put the phone through its paces and everything seems quite stable. I am LOVING the new speed, it's like having a new phone.

[slinkydoo1982]

Originally Posted by sl8763

I'm running Energy's CHT ROM (Cookie Energy Style) dated August 28th 2010. I am using OCT v.1.5 and using these settings:

OCT V1.5 @ 768
2000ms interval
1 steps (so it idles at 384)
100 load max
0 load min
80 jump max
3 jump min

I've only been running it for a day but I've really tried to put the phone through its paces and everything seems quite stable. I am LOVING the new speed, it's like having a new phone.

I've been at zero steps for a while now, but yea, same settings. People, these might be the right settings for 768mhz...

[Maxx134]

Originally Posted by slinkydoo1982

I've been at zero steps for a while now, but yea, same settings. People, these might be the right settings for 768mhz...

I am not one of those lucky useres than can go up to 768 without trouble.
My highest stable is 748, with 768 barely working.

I have some observations.
On Energy Sept4 build 21914 I have notice Sense more stable..
I can now clock my highest stable (748Mhz) without low polling.

Also, for me, OCT at same speed(748testing) froze my unit on texting (zero settings, NO dynamic scalling) ,
So I must assume that the "setcpuspeed 1d cab" is working better for me than the OCT cab..
Also interesting to note is that I did not install Netripper's original app, just the "setcpuspeed 1d cab"..

Also I did an experiment to see which Overclock application would "take over" control of the processor...
Yes let them fight it out, ha!
I installed both the "OCT_V_1.5" cab and the "setcpuspeed 1d cab", and "setcpuspeed 1d cab" won, as it took over at a different speed I set it at.
OCT would try when I pressed "on" button, but instantly revert back to the "setcpuspeed 1d cab" setting.

ALso when I set both on same time to same speed, my unit frooze, whoops!
I guess I'm lucky I didn't melt my unit ha.
These are just some observations and I don't recommend anyone try unless they are not afraid .
Bottom line is, use whatever works for you.

[slinkydoo1982]

Originally Posted by Maxx134

I am not one of those lucky useres than can go up to 768 without trouble.
My highest stable is 748, with 768 barely working.

I have some observations.
On Energy Sept4 build 21914 I have notice Sense more stable..
I can now clock my highest stable (748Mhz) without low polling.

Also, for me, OCT at same speed(748testing) froze my unit on texting (zero settings, NO dynamic scalling) ,
So I must assume that the "setcpuspeed 1d cab" is working better for me than the OCT cab..
Also interesting to note is that I did not install Netripper's original app, just the "setcpuspeed 1d cab"..

Also I did an experiment to see which Overclock application would "take over" control of the processor...
Yes let them fight it out, ha!
I installed both the "OCT_V_1.5" cab and the "setcpuspeed 1d cab", and "setcpuspeed 1d cab" won, as it took over at a different speed I set it at.
OCT would try when I pressed "on" button, but instantly revert back to the "setcpuspeed 1d cab" setting.

ALso when I set both on same time to same speed, my unit frooze, whoops!
I guess I'm lucky I didn't melt my unit ha.
These are just some observations and I don't recommend anyone try unless they are not afraid .
Bottom line is, use whatever works for you.

Did you try the 2000ms polling interval? with a wide load min/max? I guess it just be the quality of the chip, but If anyone is running similar settings to mine, with success, then maybe that will prove it has more to do with settings and overall environment, (ROM, cabs and such)