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.

how can I revert flashed kernel settings

so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom

spidasense said:
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
Click to expand...
Click to collapse
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.

buhohitr said:
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
Click to expand...
Click to collapse
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1

spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
Click to expand...
Click to collapse
You should able to flash cleanrom without losing any data, during the install there're options for many kernels, I suggest try the "_that stock kernel" first

spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
Click to expand...
Click to collapse
Anyone else with an unlocked bootloader uses a custom ROM that sets the display dpi. This has nothing to do with the GPU, it's just a setting that tells Android the display resolution so that it can scale UI elements accordingly.
To get your 240 dpi back, either install CleanROM Inheritance, or the first kernel in this thread:
http://forum.xda-developers.com/showthread.php?t=2106689

that is actually the kernel Iflashed to ttry and fix the dpi. thanks for informing me on that, I had a hunch dpi had something t odo with the problem I was having. I only tried one of them I guess theother one (ill have to check my sd card to find out which one ) will fix it.
and to be clear, I can flash clear rom inheritince and not lose app data or settings?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

[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.

D801 20g/30b Stock Kernels

As with many d801 users i have switched to the custom lp by DJLamontagneIII and we all know that sometimes flashing updates to the kernel can lead to issues...or maybe you just want to use good ol stock...I just made it flashable through recovery and can take 0 credit for the kernel all that goes to LG...lol...Enjoy!
https://app.box.com/s/rxagw7391n6cm5xlpacy4v9cbpw4o985

If I flash this with the bumped TWRP blastagator is there any risk? Will I lose my customer recovery or will it still work? Sorry for the noob questions

StonerSteve420 said:
If I flash this with the bumped TWRP blastagator is there any risk? Will I lose my customer recovery or will it still work? Sorry for the noob questions
Click to expand...
Click to collapse
They are 100% stock...fine to flash...this is just if you need stock kernel back after using custom...recovery will be unaffected

Cool thanks. After bumping the bootloader and switching kernels I've had some issues. Don't know if it is because of that or if the leaked official D80130b has some issues that the real official update doesn't

jamesd1085 said:
As with many d801 users i have switched to the custom lp by DJLamontagneIII and we all know that sometimes flashing updates to the kernel can lead to issues...
Click to expand...
Click to collapse
after using DJL's kernel and flashing back the stock, mpdecision can't be enabled through kernel tuning apps. it just switches back to off again after settings are applied.
not sure what stops it since i see that the mpdecision file is intact in system folder. however, looks like DJL did something to it after he introduced a different hotplug.

mannequin said:
after using DJL's kernel and flashing back the stock, mpdecision can't be enabled through kernel tuning apps. it just switches back to off again after settings are applied.
not sure what stops it since i see that the mpdecision file is intact in system folder. however, looks like DJL did something to it after he introduced a different hotplug.
Click to expand...
Click to collapse
Do you have any kernel control apps...if so try deleting all profiles and reboot and set up again...but as i mentioned i just made flashables of stock kernel pulled straight from our d801 .kdz files...if that doesn't help i would ask him if he had made any major changes that would cause conflict

jamesd1085 said:
if that doesn't help i would ask him if he had made any major changes that would cause conflict
Click to expand...
Click to collapse
figured it out, mpdecision file didn't have enough permissions set. perhaps, that was his change.

Thanks for this man, you saved me today.

demoncamber said:
Thanks for this man, you saved me today.
Click to expand...
Click to collapse
No problem...also if anyone needs them dorimanx has added stock kernels for all his supported devices to his download sites

[Kernel] [SM-T560/gtelwifi][4.4]

This is a Custom Kernel for SM-T560/gtelwifi running stock ROM.
-Added CPU Governor Ondemand
-Added CPU Governor Powersave
-Default cpu Governor is set to Ondemand
-Fixed cpu Frequency from resetting it self if lowered manually by user.
-Added Virtualization Drivers.
Flash with twrp.
Download here
drive.google.com/open?id=1G6-t7ykD6PDNoGegNAXPyAggnd_UArVO

Hi
First of all,thank you for your hard work...
Now i tried your kernel on my samsung sm-t560 only wifi,i tried it with stock ROM and "Lightning ROM" but it's stuck on bootloop(kernel splash screen).Am i doing something wrong,or this kernel isn't for my tablet?Thanks
Edit;
So i managed to flash the kernel and it works,it finally works,i was looking for this thing for so long.Thank you very much

pren22 said:
Hi
First of all,thank you for your hard work...
Now i tried your kernel on my samsung sm-t560 only wifi,i tried it with stock ROM and "Lightning ROM" but it's stuck on bootloop(kernel splash screen).Am i doing something wrong,or this kernel isn't for my tablet?Thanks
Edit;
So i managed to flash the kernel and it works,it finally works,i was looking for this thing for so long.Thank you very much
Click to expand...
Click to collapse
Same thing happened to me. How did you manage to fix it?

Here is the upload of the kernel.

GreeyChip said:
This is a Custom Kernel for SM-T560/gtelwifi running stock ROM.
-Added CPU Governor Ondemand
-Added CPU Governor Powersave
-Default cpu Governor is set to Ondemand
-Fixed cpu Frequency from resetting it self if lowered manually by user.
-Added Virtualization Drivers.
Flash with twrp.
Download here
drive.google.com/open?id=1G6-t7ykD6PDNoGegNAXPyAggnd_UArVO
Click to expand...
Click to collapse
Could i ask you to do the same thing for the latest version of t560 4.4.4. i'll upload the stock kernel and if you can do it i would really appreciate it.
I think the kernels are the same but when i try to install the modified from above, it gets stuck the first boot splash.
Thank you