Database Info

3.2 and SetCPU issues

Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?

Never heard of such an issue on the Xoom until now...
Common sense I know, but... make sure you don't have any profiles set up to cause this. That is the only thing I can think of. Ex: It's set to clock to the lowest speed while AC charging, etc.
If all else fails... wiping data is your best friend to fix strange problems while flashing custom Roms. Back up all of your apps with their data via Titanium Backup, then wipe data, wipe cache, wipe dalvik cache, then restore all apps with data, but do not restore any system data or system apps. That's the best thing you can do, if you do not do this... you may experience problems like so. I've had strange issues before and doing this fixed it all up no problem.

PensFan66 said:
Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?
Click to expand...
Click to collapse
You can set the lowest speed higher. Use interactive and don't set on boot unless you are really sure that it's stable.

Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?

Almighty1 said:
Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?
Click to expand...
Click to collapse
I think it only works the first time on the Xoom.

okantomi said:
I think it only works the first time on the Xoom.
Click to expand...
Click to collapse
setcpu never worked right for me. use no-frills cpu.

System Tuner

Hi all,
I've got a problem with System Tuner. On every ICS ROM I try the CPU clock and voltage settings won't stick. After I reboot the phone they go back to their defaults. Hence, I've got 3 questions:
1. Does everyone have these problems? Did I not check a setting or something?
2. What alternatives to System Tuner don't turn the second CPU core permanetly on?
And 3. Is there an init.d script which lets you set the clock speeds/voltage settings? Because I would rather not use an app at all to do that.

Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.

ccs16rocks said:
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
Click to expand...
Click to collapse
Yes I did that, but the minimum frequency doesn't stick.

Nobody?
I'm using No-frills atm, but does that turn CPU1 permanently on?

-editedpost-

V1k70r said:
Yes I did that, but the minimum frequency doesn't stick.
Click to expand...
Click to collapse
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?

yasobaso said:
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
Click to expand...
Click to collapse
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny

boroboy69r said:
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
Click to expand...
Click to collapse
Could you be more detailed Do you mean " Re-Apply CPU settings" if so yes I had it enabled. I will reflash stock o any other kernel and check if it's going to solve this.

I also have this problem with system tuner pro, now i'm using setcpu and the settings stick.
using vipers 1.1.0, tried anthrax/bricked/faux123 all didn't stick.

You know you.could ask the dev of super tuner. He's always very responsive anytime I've had issues. Also having different versions backed up in Ti helps as well cause a new update fixes one thing from a slew of phones but might just break yours. Having a backup versions means you can go back restore and test.
Casperi.
Sent from my SGH-T989 using xda premium

In relation to your second question, what kernel are you using? Faux's kernel has the second core on by default. System tuner doesn't have the ability to turn it off. If you want it offline until it's needed, try seb's or bricked kernels instead.

System Tuner 3.0
Just to let you know System Tuner 3.0 was released some time ago and provides improved CPU handling, new GPU, Gamma, MP, thermal controls on many custom kernels and a lot of other new or improved features (entropy, fstrim to name a few).
This is now a spawn of Android Tuner, and benefits from a larger user-base, improved stability and performance.
It now has the ability to turn on/off CPU cores, with a dedicated screen-off option. Only if custom kernel allows it though.

NSTools and SetCPU Set on Boot

If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2

why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor

Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.

i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"

qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.

I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.

I can't seem to overclock my TF300T! it will later reset back to 1.3ghz!

Hi,
I have tried different rom + kernel:
cleanrom
ultra fast rom: http://forum.xda-developers.com/showthread.php?t=1901784
untermensch kernel: http://forum.xda-developers.com/showthread.php?t=1892326
and still can't oc the cpu to something higher than 1.3ghz
I used the No-frills CPU as well as the antutu cpu master (free version)
for the No-frills cpu, whenever I set the CPU speed to something high (ie. 1.6ghz max and 102mhz min), checked apply on root then apply, it worked fine for a while, but later on when I open no-frills cpu, th e current max and min will reset back to 1.3ghz and 102mhz.
Governor and I/O scheduler is fine though.

Sounds to me like u need to check start on boot..i havent oveclocked mine yet but option should be there where u select governors and such...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Of course i have checked that it just didnt work

Give Voltage Control a try. It gives you the options to apply on boot or init.d. I use the init.d setting because the phone boots quicker. I had that problem with CPU Master in the past while running it on my phone.
Sent from my LG-LG855 using Xparent Green Tapatalk 2

Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device

redjersey said:
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
Click to expand...
Click to collapse
Hi !
Overclock automatically deactivates when the device enters in standby !

surdu_petru said:
Hi !
Overclock automatically deactivates when the device enters in standby !
Click to expand...
Click to collapse
Ahh, that's what I thought was going on, this is happening to me as well.

treo4life said:
Ahh, that's what I thought was going on, this is happening to me as well.
Click to expand...
Click to collapse
Hi!
No, this happens to everyone
However, it seems a pretty good thing - why we need OC - if the device sleep ? :laugh:
- it is also good for battery - !

So i will have to reoverclock it everytime ??

Mine doesn't do this at all. I use CleanROM 3.1, unters kernel and setcpu. No issues.

I guess I know why it's because setcpu has the profile settings allows u to set the CPU speed when screen is on / when screen is unlocked
Othe CPU apps I have tried have no such feature which means oc works when u set it, but when u turn off the screen then turn it on , it will reset back to 1.3ghz

Using setcpu, what I did was set a "screen off" profile to max out at 1700ghz when the screen is off or in sleep mode and it worked for me!!! That way will not default back to stock 1300ghz everytime I hit screen off or sleep mode.

[Q] Overclock problem on CM10.1

Sorry for my English
I am using CM10.1 ROM
I use the No-frills CPU Control to overclock CPU to 1.2GHz(performance cpu governor). However, when I locked the screen and woke it up, my phone would automatically restore the default CPU setting(1.0GHz). I had to go to the app and apply the setting everytime. How could I prevent the system change CPU frequency?

Make sure that the option called "set on boot" is checked. It will automatically apply the settings (overlclock to 1.2) on boot.
Hope this helped

Dbstudioz said:
Make sure that the option called "set on boot" is checked. It will automatically apply the settings (overlclock to 1.2) on boot.
Hope this helped
Click to expand...
Click to collapse
I have already made a tick. I also found that when I locked the screen for a few minutes, there is nothing changed. And if my phone idle for an hour or even longer, then the system would automatically restore the default CPU setting.
Does the system have battery saving mode? How can I turn off it? I haven't downloaded any battery saving apps

Try.. Trickster mod.. U can lock frequency with it..

hafizkris90 said:
Try.. Trickster mod.. U can lock frequency with it..
Click to expand...
Click to collapse
Wow, it works. I can lock the frequency. Thank you very much for your help:laugh:

No prob.. glad i can help..
Sent from my MB865 using Tapatalk 4 Beta