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.
Related
What scaling setting do you use, maybe you have custom profile?
I personally use 'ondemand', but I was thinking.... It would be nice to have a smart scaling setting, based on the amount the phone is used, screen brightness and the battery temperature, etc.
Sent from my X10a using XDA App
Hi.
I've set mine at 576 max and left minimum at 245, scaling is on demand, and have set a profile for screen off at 245 for both. I've left the advanced screen as I don't have a clue what any of it means lol.
Non
Used it at first when got rooted. still on root BA23 firmware and im very happy with the current setup. I left the processor to operate the way it want to do.
Dont take me wrong, its a great software, everything is depends on overall apps you are running. and its unique to your phone, check its really necessary.
After-all we are talking about android, not windows.
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Mano1982 said:
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Click to expand...
Click to collapse
I had that problem once. But i think it is a OS bug than the SetCPU bug itself. You should re-root your fone and set profiles one more time. It will help you save a lot of battery
My setting (following someone on the net)
- Fully chage (AC/USB): 998/245
- Screenoff: Max: 348 Min: 245
- Battery <25%: Max: 348 Min: 245
Ok Dundun, I've set profiles again same as yours let's see how it workd
Just came across this thread for decent SetCPU setting: http://forum.xda-developers.com/showthread.php?t=734886
I am running Tiamat 1.3.2 and after a reboot setcpu ignores my settings and and the zoom runs at 216mhz. I can go in and move the slider and it will work fine until next reboot. Any ideas?
Is there a checkmark in the "set on boot" box?
Yes, should it not be there?
It should be checked. Did you set up any profiles? Before i had any profiles set up when i powered off the screen my xoom would scale down to something absurdly slow, like 256mhz. (Guessing since i dont have it with me currently) See if that makes a difference.
i haven't set up any profiles. I am still researching what profiles would suit me best. I will go in and set up a temp profile just to see if it resolves the issue
I have the opposite (sort of) problem. No matter what i set the max rate to on setcpu, it sometimes still maxes out to 1504. Anyone have this issue?
I had the same problem with it jumping to 1504 when I had it set to 1200. I tried Droid overclock as well and still had instability issues. I've went back to stock until there is more development. I could care less about overclocking and am pretty sure it was causing my Xoom to force reboot all the time.
Sent from my Xoom using Tapatalk
Brenardo said:
I am running Tiamat 1.3.2 and after a reboot setcpu ignores my settings and and the zoom runs at 216mhz. I can go in and move the slider and it will work fine until next reboot. Any ideas?
Click to expand...
Click to collapse
Are you moving the minimum slider or the maximum? It will run at 216 when you aren't doing anything, then when it will run at whatever you have set as maximum when you're doing something.
Move the slider if tge numbers at the top doesnt move then u may have to disable perflock
Sent from my HTC Desire using XDA Premium App
Just noticed the same issue. Had it set to performance 200/1500 and it would never go above 1500 after I rebooted untill I touched one of the sliders.
Flashed 1.4.0 and now I don't seem to be having any issues.... who knows? Anyway I hope it is fixed as it was quite annoying when unlocking to use to have to mess with SetCPU everytime.
I hope everyone else gets their fix too.
I actually first noticed this on timian 1.4.0, but that was also the first time I tried changing to the performance profile.
Motorola Xoom Wifi Only, 1.4.4 3.1
I just popped Set CPU back on my xoom after putting on 1.4.4 and set it to "interactive"
I cranked the max up to 1.7ghz and checked set on boot.
It restarted and now, it boots and then crashes every time I get to the pattern unlock screen and then reboots.
I cant seem to stop this reboot cycle. Is there any way to stop it from crashing repeatedly?
My Sunday morning is a mess indeed!
yanic123 said:
Motorola Xoom Wifi Only, 1.4.4 3.1
I just popped Set CPU back on my xoom after putting on 1.4.4 and set it to "interactive"
I cranked the max up to 1.7ghz and checked set on boot.
It restarted and now, it boots and then crashes every time I get to the pattern unlock screen and then reboots.
I cant seem to stop this reboot cycle. Is there any way to stop it from crashing repeatedly?
My Sunday morning is a mess indeed!
Click to expand...
Click to collapse
OK...first rule. NEVER select Set On Boot for JUST THIS REASON. It just isn't worth it, unless you have a set up that you are absolutely certain is totally stable and the extra 15 seconds at boot up to overclock it again is just too much of a bother for you to bear.
I know there are some scripts that can be run from Recovery to clear overclocking, but I don't have the technical bones to direct you to them, or even the knowledge if they would work on the Xoom.
Personally I would try installing a lower frequency Tiamat kernel or the stock kernel and then rebooting. When SetCPU cannot achieve the frequency you have it set for now, it will either FC, just overclock the device to the kernel maximum, or bootloop you. Therefore, I doubt it would hurt and may solve your problem pretty easily.
yep, just flash a different kernel.
just flash tiamat 1.4.3
Sent from my Xoom using XDA Premium App
thanks guys! really glad you lot are here to support
Yeah, for anyone else reading this... I had the exact same problem with the never ending boot loop.
I just flashed tiamat 1.4.3 through cwm. It then booted correctly, so I reflashed 1.4.4 but this time I got rid of SetCPU in favour of 'No Frills'. It doesn't have the profiles I was used to with SetCPU, but it does seem to do a much better job with the xoom.
It's still a bit unstable at 1.7, but runs beautifully at 1.6.
Good times!
Wish I had seen this 15 minutes ago
I had the same issues and did a factory reset. Oh well I guess that is what backups are for
I did the following on my MyTouch 4G, but it should work for the Xoom if you have ClockworkMod Recovery and Android SDK on your PC.
1. Boot into CWM recovery.
2. adb pull /data/data/com.mhuang.overclocking/shared_prefs/setcpu.xml D:\setcpu.xml
3. I opened D:\setcpu.xml and set the following:
- startBoot setting from "1" to "0".
- max setting to equal min.
4. adb push D:\setcpu.xml /data/data/com.mhuang.overclocking/shared_prefs/setcpu.xml
5. Unmount data and reboot.
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.
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.