Database Info

Overclocking in ICS?

I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.

stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.

sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.

Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.

Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.

stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?

Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL

Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.

UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.

I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.

fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss

WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.

horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.

O'c Help please

Ok I have unlocked and rooted my HOX 4.0.4 using the new method. I have 2.20 so I a flashed the Kernel to the rom I want using Fastboot, I then did a clean install of the ROM. I use NoFrills CPU to over clock and apply the settings but when I run a bench mark it still says I am at 1.5 GHz. I have tried several differnet roms and kernels to no avail even though It says I am over clocking it to 1.8 in no frills cpu I have even tried antutu cpu master it shows I am overclocked but benchmarks say I am still at 1.5 and my scores do not go any higher.
Any idea's please.

I had problems at times with nofrills i just use cm10 built in works fine. I use rohan kernel b4.

DvineLord said:
I had problems at times with nofrills i just use cm10 built in works fine. I use rohan kernel b4.
Click to expand...
Click to collapse
Are you on 2.20 using the new unlock and root method

i unlocked back during 1.85 but i did flash the 2.20. i think 2.20 is better then 1.85 but the hboot restrictions are very annoying. but flashimagegui makes many things alot better now.

[Q] Elemental-S-JB-v2.1 Kernel and Overclocking

Hello,
I have an HTC One S with ViperS 2.0.0 rom. Few days ago, I installed Elemental-S-JB-v2.1 kernel and choosed an 1.7 overclock for the CPU. After flashing the kernel zip and update boot.img via fastboot flash boot command, I booted my phone. All seems to work but when I controlled my overclock with kernel tuner.
So I noticed that the second core was at stock frequency instead of 1.7 GHz like the first core.
Some one could me explain why ?

Just set the second core's maximum clock rate to 1.7Ghz. The Kernel allows you to do this now.

KACE321 said:
Just set the second core's maximum clock rate to 1.7Ghz. The Kernel allows you to do this now.
Click to expand...
Click to collapse
Effectively, I notice that I could with kernel tuner manualy set the frequency of the second core. But I wonder why the overclock frequency choosed during installation of the kernel doesn't affect the second core.
For me, it's perhaps a mistake, it shows that the overclok frequency is not well applied by the installer or there with an problem with frequency policy with this kernel.

Nobody can give me an answer.
I noticed too that the CPU Governor between the first core and the second is different.
Someone knows why ?
That is normal ?
Someone with a stock Rom could check with kernel tuner if the CPU gouvernors are the same ?

Stuff like that has always been picky and not much you can do about it.

[Q] Help with SOD?

Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
I had a stock Froyo on my phone and I tried following the steps of this thread : http://forum.xda-developers.com/show....php?t=1894737
The first mistake I did, was I flashed XXKPQ directly by mistake instead of XXKPE, which I noticed while I was in the middle of doing it.
The phone was working properly on the GB rom. After that I rooted it, following the guide using a cf root of XXKPQ.
Now, I didn't know if there was prerequisite for it or not, but I flashed the custom rom of http://forum.xda-developers.com/show....php?t=2300693
The first problem I saw was that while installing it from the sdcard, for a long time, the screen was blank. I left it thinking that it was part of it, but since it persisted, I rebooted it. The phone opened properly and after that I installed the gapps later through recovery mode.
The first major problem I saw was that the phone after screen locking, it used to shut down automatically. After looking through solutions, where none were working, I tried flashing to stock rom via odin (stock rom : http://forum.xda-developers.com/show...php?p=16107097)
After that though, whenever I open the phone, it just stucks at the samsung logo screen and doesn't go further.
Also, when in download mode, I tried it attaching to Odin but "USB device not recognized" comes all the time.
I don't know what to do.. I know I must have made loads of huge mistakes and I should have done everything, being properly informed, but now I really need a solution..
Click to expand...
Click to collapse
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?

tyson123g said:
Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?
Click to expand...
Click to collapse
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.

karthik gowtham said:
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.
Click to expand...
Click to collapse
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?

tyson123g said:
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?
Click to expand...
Click to collapse
Why Do You Got To XXKPE From DDLF2 ,All I Was Trying To Say Was
XXKPE--->DDMF1--->CF-Root or Custom Kernels--->CM10.1 or Any Other Rom.

Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?

tyson123g said:
Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?
Click to expand...
Click to collapse
REMICS v6 now is out (smoother and more stable)
kernel 3.0.8 by dhiru1602 does not support OC but you can change the governor to ondemand or performance (performance>>processor>>CPU governor) and the I/O scheduler to deadline (performance>>I/O scheduler) but first you have to enable the developper options (7 hits on the Build number).
Hit thanks "button" if i helped you!
regards

Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.

tyson123g said:
Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.
Click to expand...
Click to collapse
Yes, because as i know kernel 3.0.8 by dhiru1602 which is the default (preinstalled) kernel of CM10.1 (Jelly bean 4.2.2) (REMICS 5.x and 6 and the newer jelly bean roms are based on CM10.1 by dhiru1602) does not support OC and you won't find other kernel for CM10.1 better than dhiru1602 kernel (it's only my idea).
I think dhiru1602 didn't implement OC in his kernel for reasons of stability and battery backup...and you don't have to use no frills CPU app anymore, just 7 hits on the Build number (About the phone >> Build number) will enable the "developper options" and "performance" (in "performance" you can change the CPU governor and I/O scheduler).
And don't use REMICS 5.8, REMICS 6 is better because many bugs were fixed!!!
Hit thanks "button" if i helped you!
regards

Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..

tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
in CM10.1 kernel overclocking is not there for some stability issues... overclocking is possible but do it at your own risk

tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
You really don't need to OC your CPU....if you are facing some lags in CM, this maybe because you didn't wipe data before install CM.
Usually I downclock my cpu to 600MHz and set the governor to conservative to save battery without facing lags...so really CM10.1 A8 is not lagging!!!

Okay. I have to install REMICS 6 anyway. I will try again. Hopefully this time, it is quick.

Well, I changed my mind and went with CM 10.1 A8. It is fast and good.
But for some reason, my phone is rebooting by itself.

[Q] Can't set CPU speed on Lollipop

Hi all,
I just installed Nameless ROM and am having trouble setting the CPU speeds. I've tried with Device control (built in) and then with No Frills CPU, both with root access, and have not had any success setting my CPU speed. When I set anything on minimum, I exit the app and when I return it goes back to its original value (1574). Same thing with No Frills. I have BusyBox installed and the latest version of SuperSu. So my question is, does anyone have any idea why this is happening? Is there a workaround? Has anyone had a similar experience? I do not have a custom Kernel, but my experience in the past has been quite similar with Franco Kernel and ElementalX kernel across a number of different ROMs.
Any help would be appreciated.

Not actually a help but franco.Kernel Updater (App) doesn't work with CM12 as long as you don't install SuperSU. I did and it solved all problems. It has something to do with the internal su management I guess... but I'm not sure what's wrong with your setup since you already tried SuperSU.

Use a custom kernel.

@Lethargy: Damn, pretty simple answer! I've somehow missed that he says "no custom kernel" :S

Custom kernel
Custom kernels yield same result. Flashed Franco and the same thing is happy ING in the FKUpdater app. Forgive me if I'm wrong but the device control that's baked in to the Rom should be able to scale the kernel set in place by the same rom, right?

xkn0s said:
Custom kernels yield same result. Flashed Franco and the same thing is happy ING in the FKUpdater app. Forgive me if I'm wrong but the device control that's baked in to the Rom should be able to scale the kernel set in place by the same rom, right?
Click to expand...
Click to collapse
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?

Lethargy said:
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?
Click to expand...
Click to collapse
Did not know that. Thanks for the info!
SELinux is Enforcing.

xkn0s said:
Did not know that. Thanks for the info!
SELinux is Enforcing.
Click to expand...
Click to collapse
Try setting it to Permissive

Lethargy said:
Whatever "device control that's baked into the ROM" makes no difference. All kernel apps/methods are the same, which is to simply echo a value (sysfs). You can do it via any kernel app, embedded kernel app, Tasker, Terminal, its the exact same thing.
What is your SELinux state?
Click to expand...
Click to collapse
Lethargy said:
Try setting it to Permissive
Click to expand...
Click to collapse
Changed to permissive verified and reboot, still having the same trouble... tried flashing Franco again and went into boot loop; Same with Hellcore kernel and ElementalX kernel.

xkn0s said:
Changed to permissive verified and reboot, still having the same trouble... tried flashing Franco again and went into boot loop; Same with Hellcore kernel and ElementalX kernel.
Click to expand...
Click to collapse
Not sure why it would end up in a non-boot. Try reflashing your ROM then the kernel.

Lethargy said:
Not sure why it would end up in a non-boot. Try reflashing your ROM then the kernel.
Click to expand...
Click to collapse
Booted TWRP, Flashed Rom and ElementalX in one go, boot stuck at Google splash screen for 20 minutes. Reflashed rom and booted up. Still not able to set CPU. Tried Reflashing Franco Kernel with app again and back to Google Splash Screen.

xkn0s said:
Booted TWRP, Flashed Rom and ElementalX in one go, boot stuck at Google splash screen for 20 minutes. Reflashed rom and booted up. Still not able to set CPU. Tried Reflashing Franco Kernel with app again and back to Google Splash Screen.
Click to expand...
Click to collapse
If you reflash the ROM it'll probably go back to using it's original kernel. Have you tried with a different ROM?

Lethargy said:
If you reflash the ROM it'll probably go back to using it's original kernel. Have you tried with a different ROM?
Click to expand...
Click to collapse
Yeah I reflashed /system and it came back up.
I just flashed Terminus Rom (http://forum.xda-developers.com/google-nexus-5/development/android-5-0-0r7-lrx21v-t2950499) and set up as new device. installed Kernel Toolkit and was able to set the Clock, but after a few minutes it just went back to default.
Flashed ElementalX kernel after that and installed the corresponding app and was able to set clock without it changing back. seems to only work in ElementalX app though.
It survived a Reboot and I sat and watched it for a while and it seems to all be working now!
Thanks for your help @Lethargy

xkn0s said:
Yeah I reflashed /system and it came back up.
I just flashed Terminus Rom (http://forum.xda-developers.com/google-nexus-5/development/android-5-0-0r7-lrx21v-t2950499) and set up as new device. installed Kernel Toolkit and was able to set the Clock, but after a few minutes it just went back to default.
Flashed ElementalX kernel after that and installed the corresponding app and was able to set clock without it changing back. seems to only work in ElementalX app though.
It survived a Reboot and I sat and watched it for a while and it seems to all be working now!
Thanks for your help @Lethargy
Click to expand...
Click to collapse
ElementalX and it's app use an init.d script (as of the latest version, it uses a ramdisk script instead) to set the values upon boot, reading values from a config file.

Hi all,
For reply at first message, I think have a solution (that's worked for me). On many devices like Nexus or Xperia, a Qualcomm service can be installed and running at boot (MPDecision) and change the CPU usages when it's necessary (number of cores and frequencies).
Maybe this priority is higher than all in Lollipop, and overwrite the modifications changed in other CPU managment apps. I found this when I searched a solution to this same problem on my Xperia Z with Lollipop 5.0.2. I used lot of app and no one worked for me, and tried Kernel Adiutor to see more parameters (need install Busybox). I disabled MPDecision to the CPU Hotplug section, and the SetCPU profiles worked after.
But you can see that disable this option keep all cores enable (with MPDecision enable, many cores change status to "disconnected" when no usage) maybe it's better to use SetCPU profiles on a full day than leave MPDecision manage your CPU. Just compare.
Sorry for my bad english, and happy if this help someone.