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.
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
Seems like whenever I install a custom kernel that is OC 'd, any launcher force closes after sleep... any ideas?
cuban88 said:
Seems like whenever I install a custom kernel that is OC 'd, any launcher force closes after sleep... any ideas?
Click to expand...
Click to collapse
Never seen this myself. I run at 1.4GHz and have tried all of the custom launchers with none of them doing this. Also, can report the same for my wife's phone.
Yea it lags a lot.. then says wait or force close .. could it be a set CPU setting? ?
cuban88 said:
Yea it lags a lot.. then says wait or force close .. could it be a set CPU setting? ?
Click to expand...
Click to collapse
Hmm...What is your CPU set at? I have seen this when I boot occasionally but never when waking from sleep.
Netarchy / 1300-800 on demand.
Screen off 1000-800 on demand.
Anything under 800 makes it worse..
Clean flash every time. Wipe>Rom > Kernel
cuban88 said:
Netarchy / 1300-800 on demand.
Screen off 1000-800 on demand.
Anything under 800 makes it worse..
Clean flash every time. Wipe>Rom > Kernel
Click to expand...
Click to collapse
Have you tried not using any profiles? I run 1400/100 with Netarchy's 1.2.4 CFS and the ondemand governor (lately I've been trying conservative just to see what kind of life I get out of that but I'll probably wind up using ondemand again). Also, which launcher are you using?
ADW.
I have not tried to run 100-1400 w/o profiles .. I will try this for 24 hours or so and leave feedback for anyone else out there with this issue ..
Are you saying that battery life is 12+ without profiles?
I have been using CM nightlys with netarchy 1.4 kernel at 1300-800 on demand and profile set to 1000-800 on demand (with the force close problems) and have been averaging 8-10 hours heavy use and 12-14 moderately .. how about yourself?
(I just got a random force close for ADW as I type.... I'm starting to think I should uninstall it and reinstall)
cuban88 said:
ADW.
I have not tried to run 100-1400 w/o profiles .. I will try this for 24 hours or so and leave feedback for anyone else out there with this issue ..
Are you saying that battery life is 12+ without profiles?
I have been using CM nightlys with netarchy 1.4 kernel at 1300-800 on demand and profile set to 1000-800 on demand (with the force close problems) and have been averaging 8-10 hours heavy use and 12-14 moderately .. how about yourself?
(I just got a random force close for ADW as I type.... I'm starting to think I should uninstall it and reinstall)
Click to expand...
Click to collapse
Personally, I've never been a fan of ADW always or ADW ex...always been a LPP man to be honest. I get between 14-16 hours of moderately heavy use (a few texts, a lot of XDA browsing, Engadget reading, and email, a few phonecalls, and almost always on WiFi and sometimes a few flashes as well). I have been on RC1 since it was released also.
Waw that's good .. I will try 100-1400 w/o profiles and get back to you and post results
I'm getting the same issue with the stock launcher running Modaco R11 and Netarchy 1.2.4 & today on 1.2.5.
I'm running profiles:
Screen off 400 powersave
Battery 1300/100 ondemand
I'll run no profiles 1300/100 on demand for 24 hrs and report back if issue is still present.
I always get past one day. No profiles, OC.
You should try http://www.appbrain.com/app/screen-filter/com.haxor if you want some more battery life. Works very well Only complaint is that when you have it on and theres sunlight reflecting on the screen its going to be difficult to see whats happening on the screen, but you can always toggle it off via notification bar.
So far so good without profiles being set.. moderate use(email, maps, phone calls). I'm going on 4 hours and I'm at 87% without any force closes ..
Within 4 hrs, plenty of stock launcher FC's for me running previously posted setup (no profiles)
Sent from my Nexus S using XDA App
cadguy said:
Within 4 hrs, plenty of stock launcher FC's for me running previously posted setup (no profiles)
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you're getting force closes of the stock launcher then something else is causing it to force close. A lot of people seem to be having issues with MoDaCo, my wife included. Might try a different ROM. I'm actually starting to really like stock 2.3.3 or GingerCollab.
zephiK said:
I always get past one day. No profiles, OC.
You should try http://www.appbrain.com/app/screen-filter/com.haxor if you want some more battery life. Works very well Only complaint is that when you have it on and theres sunlight reflecting on the screen its going to be difficult to see whats happening on the screen, but you can always toggle it off via notification bar.
Click to expand...
Click to collapse
This is off topic. There are settings is cm7 to do the same thing as this app. I use it along with the auto brightness to never need to manually change anything. It's under cm settings*display*automatic backlight*light levels.
Update
No problems with either ADW/Launcher Pro.
It has been 10 hours; automatic backlight, internet, email, phone calls. I'd call this moderate use (no games, lots of work relates online searches and maps use). Battery life is currently at 65%.
What I did....
Wiped>Flashed CM nightly#7 / GAPPS>reboot/setup>recovery> flashed Netarchy 1.4> reboot
Not one FC. Thanks Kenvan19 for the no profile suggestion. I was used to using profiles on my N1, guess it isn't needed on NS!
cuban88 said:
No problems with either ADW/Launcher Pro.
It has been 10 hours; automatic backlight, internet, email, phone calls. I'd call this moderate use (no games, lots of work relates online searches and maps use). Battery life is currently at 65%.
What I did....
Wiped>Flashed CM nightly#7 / GAPPS>reboot/setup>recovery> flashed Netarchy 1.4> reboot
Not one FC. Thanks Kenvan19 for the no profile suggestion. I was used to using profiles on my N1, guess it isn't needed on NS!
Click to expand...
Click to collapse
No problem man! Glad you got it figured out
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.
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.
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Does it seem to happen at a certain time? After opening a certain app?
Does sound odd though.
The only certainty I can say is that it happens when no applications are open and the screen goes into lock mode. It also happens regardless of the launcher being used (I use FX, my brother uses HTC Rosie, the other uses Go).
gotpriest said:
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Click to expand...
Click to collapse
+1 I have this issue too...I lowered my overclock and it's been working fine since
Sent From My HTC Sensation 4G
I assume that is performed through SetCPU? Or Daemon.
In Daemon, there's only four options, Sleep and Wake Max, Sleep and Wake Min - how did you fix yours?
Anyone offer a tip on this?
I don't have SetCPU on my phone (looks like it was replaced?)
Don't want to bork my phone, just wondering how to dial down the overclock slightly to prevent this hard crash.
Thanks
ARHD has Daemon Tools I think, with this you can reduce your overclock.
However my suggestion would be to increase the Maximum sleep CPU speed. [Sleep Max]
I can't remember but I think be default it is at ~440MHz, increase it by around 600MHz and see if that fixes the problem. If so you can reduce it gradually to save battery, stopping if the problem redevelops.
Thankee very much!
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
tk_xda said:
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
Click to expand...
Click to collapse
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Grandelama said:
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Click to expand...
Click to collapse
Does this particular known issue apply if the screen turns off on its own due to inactivity time? What about if camera app is in background?
Does faux kernal need a camera fix similar to the one for bricked?