Root overclock kernels not installing?

[The FlyerFly]

Ok...here it goes...

Just fixed my recovery mode issues through the solution given in this thread...

http://androidforums.com/droid-all-...y-coming-back-custom-recovery-wont-stick.html

...so i tried the next step on my agenda, which was to find an overclock kernel for Froyo 2.2. Ive tried a handful of ChevyNo1 kernels, and a couple from jdlfg and none of them seem to take. The speed scale in SetCPU remains at a max of 600mHz, while Overclock widget shows me a possible max of 900mHz. Even if i try to set the max at 900mHz in Overclock widget, the widget never actually reads that high and SetCPU never reflects that speed either.



I can confirm that I have root, and both SetCPU and Overclock Widget are being given superuser permissions.

 

[Lock-N-Load]

first, whats the point of Overclock Widget when that is exactly what SetCPU does.. and then some.

I would download several kernels, like Chevy's 1.0 and 1.1 and a 1.2 and put them on your SD card into a directory you call /kernels/. This way, when/if 1 fails, you can boot right into recovery and try another & not miss a beat. BUT, for most, Chevy's 1.0 lv is a great stable start.

once you put those on your SD, reboot into recovery - either via ROM manager or hold X at startup. Then select to install file and select to install from SD card and then scroll to your kernel and select it and install (a few seconds) and reboot.. viola, it should load fine.

then, you can go into SetCPU and make your settings.

BTW, no matter what you use - that widget or SetCPU - if no kernel is installed, forget getting passed 800. But, SetCPU is the app to use as it is so powerful and you can set nice conditions.

 

[The FlyerFly]

first, whats the point of Overclock Widget when that is exactly what SetCPU does.. and then some.

I would download several kernels, like Chevy's 1.0 and 1.1 and a 1.2 and put them on your SD card into a directory you call /kernels/. This way, when/if 1 fails, you can boot right into recovery and try another & not miss a beat. BUT, for most, Chevy's 1.0 lv is a great stable start.

once you put those on your SD, reboot into recovery - either via ROM manager or hold X at startup. Then select to install file and select to install from SD card and then scroll to your kernel and select it and install (a few seconds) and reboot.. viola, it should load fine.

then, you can go into SetCPU and make your settings.

BTW, no matter what you use - that widget or SetCPU - if no kernel is installed, forget getting passed 800. But, SetCPU is the app to use as it is so powerful and you can set nice conditions.

Thanks L-n-L.

Actually, the only reason i have both SetCPU and Overclock Widget is because i use SetCPU to set up my speed profiles and run them, but i use Overclock Widget to see the actual speed in real time in the widget itself as the profiles are being run. In any case, I decided to uninstall OW to avoid any potential conflicts.

ChevyNo1 LV 1.0 was my very first choice for a kernel, but it didnt take earlier. I took your advice and placed the three kernels you mentioned in a /kernels/ directory on my SDCard. I also used your method of loading them, but I am seeing the same thing. I confirmed that the kernels loaded properly by checking for them under the "Info" tab in SetCPU. However, I still cannot scale the speed higher than 600mHz either on the main screen or in my profiles.

I also cleared all the data for SetCPU, uninstalled, and reinstalled, with no luck.

 

[Lock-N-Load]

SetCPU has a widget that can show real time hi and low and temp.. AND if you touch it it launches SetCPU.. so, that app can do it all

now.. did you, in SetCPU, make sure you set it to "autodetect" in the Device Selection? At the bottom of the main screen it will say so if you did, if not, make sure you did.

also, check settings > about phone > Kernel version (seen at bottom of list) to confirm an install

also, did you just try to slide the slider up to 1.0 with your finger. I have had weird times were it was grayed out, but the moment I touched it and moved it, it turned green and became movable.

 

[The FlyerFly]

SetCPU has a widget that can show real time hi and low and temp.. AND if you touch it it launches SetCPU.. so, that app can do it all

now.. did you, in SetCPU, make sure you set it to "autodetect" in the Device Selection? At the bottom of the main screen it will say so if you did, if not, make sure you did.

also, check settings > about phone > Kernel version (seen at bottom of list) to confirm an install

also, did you just try to slide the slider up to 1.0 with your finger. I have had weird times were it was grayed out, but the moment I touched it and moved it, it turned green and became movable.

Thanks, L-n-L. The autodetect seemed to do the trick. Thought I had picked that before, but I guess not.

And right now I am running ChevyNo1 LV 1.0. Can I expect to run this at 900mHz like I did with 2.1? Back then, I was able to run at that speed and rarely ever hit 110 degrees F, even when browsing and charging.

 

[Lock-N-Load]

I cannot say what you can or cannot do with yours as they all seem to be so different in what they can tolerate. all you can do is try, set alerts, set profiles, etc. trial and error. BUT Chevy's are pretty stable and so far, the best I have used and I have tried most.

BTW, I think you meant 900mhz? If I were you, crank it up to 1000MHZ and get on with it. that is why you OC'd and so set it at the max and try it. there are some great SeCPU threads on the finer nuiances - profiles to set, ondemand versus performance - but you picked 1000 so use 1000 I say

 

[johnlgalt]

I would add a cautionary remark here. If the OC kernel has enough slots, and one of them is a 900 slot, then yes you can run the 1000 MHz kernel at 900.

It is definitely up to you to figure out where you want to be at - but if you regularly use apps that crank up your CPU and take your temps routinely over 100 degF, then you can lower the OC as you see fit.

Just so you know, you can also use profiles to auto downclock the OC when it gets past a certain temp - that would allow you to run a higher clock but at the same time automatically control the phone when it starts getting hot.

Finally, your CPU is rated to work at temps well above 50 degC (aka 122 F) - in actuality, from the research I have done, it can easily surpass even 75C (although the DROID is supposed to auto shutdown itself at around 140+ deg F

 

[Lock-N-Load]

Finally, your CPU is rated to work at temps well above 50 degC (aka 122 F) - in actuality, from the research I have done, it can easily surpass even 75C (although the DROID is supposed to auto shutdown itself at around 140+ deg F

with 1.2 kernels, this is what I routinely exhibit.. even with profiles it gets to hot to fast and it seems the profiles respond to late to try to address the heat.