Does Power saving mode still work when using an app like SetCPU, or do the OC apps overrule the CPU underclock setting of that mode?
I understand that power saving mode does other things as well as just underclock the CPU (ie lower brightness etc), but I was specifically thinking about the clock settings.
I've not decided whether I will OC or not yet. I will definately play with the voltage settings though. I'm finding that my tablet gets extremely warm in the lower left hand side when put under intensive use. But back to my original point. Id like to be able to underclock it on the fly at a push of the button and find im enabling that setting alot with the stock set up...
Thanks
Related
So basically I just rooted my phone and flashed to cyanogen mod 6.1 and I'm loving it. Thanks xda for the rooting and flashing process. I decided to go into overclocking my mytouch slide and everything seems to work perfect except for the fact when I turn off my screen and turn it back on the screen is at the dimmest setting it can get. I reset the brightness back to how I want it and then turn off the screen again and turn it on, and it reverts back to the dimmest setting. I booted up without having setcpu running and the screen settings stay the same after I turn the screen on and off. has anyone found or seen this before?? And if so, is there a solution to this problem??
Thanks
I've never heard of setCPU causing that problem. You may want to trouble shoot a bit more before pinning it on that. We need to knock some things off the list of possible culprits too.
What is the brightness set to, automatic?
Custom oc kernel (dumfuq's) or what's integrated into CM?
What are your clock settings in setCPU?
What governor are you using in setCPU?
Do you have profiles set, if so, what are they?
Have you messed with the light sensor or done any custom brightness tweaks (CM settings)?
You need to answer some of those first so we can narrow it down, you may have something set up wrong. There is also the issue of the phone not coming to full brightness when you try to catch it on the screen time out (screen is off - but not locked). That's fixed by locking it and unlocking.
I am having screen wake issues with my evo. Basically for those of you who don't know it's when you press the power button to unlock the phone and the screen doesn't turn on. Sometimes the buttons light up and sometimes they ddon't but I have to clclick the power buttons a few times before the screen wakes up. The following is my configuration:
Running CM7.0.1.2 with SavagedZen 2.0.2 CFS min CPU speed 245 Max 998 OnDemand governor.
I've tried to wipe and reinstall and it didn't help. Clearing Dalvik Cache didn't help either. Any help would be greatly appreciated because this is killing me!
Sent from my PC36100 using XDA App
This is a well known problem with savage-zen kernels. Try toastcfh new kernel in the dev section
This happens to me too, that's why I usually end up back on a sense ROM. Do you use a lock screen widget? Im thinking that might have something to do with it. I wasusing no lock, and it was doing that real bad, I removed the widget and wake up seems to be behaving normally now.
Edit: I too am using a savage kernel, I'll flash a different one and see if I still have the problem.
Try turning these on. Go to settings, then cyanogenmod settings, then display.
Also you could bump up your min frequency to 460 and max to 1113 with the governor on conservative.
Sent from my PC36100
When you turn it on, push the power button slowly, I find if I do that it seems to more reliably wake up. Also, when the screen is black but the bottom lights are on, a quick tap anywhere on the screen always wakes it up for me.
I had the same issue. My fix was to turn on both the Screen-On and Screen-Off animation in Cyanogen Mod Settings.
dirkyd3rk said:
Try turning these on. Go to settings, then cyanogenmod settings, then display.
Also you could bump up your min frequency to 460 and max to 1113 with the governor on conservative.
Sent from my PC36100
Click to expand...
Click to collapse
+1
Sent from my PC36100 using Tapatalk
Screen goes black wont turn on power button and volume rocker unresponsive. Have to pull battery everytime. Disabled the lockscreen. Any suggestions
Turn on screen animation, turn min CPU up from 128 or whatever. If it keeps up you might have to reflash
Sent from my PC36100 using xda premium
Has anyone consistently had this problem, and then had it permanently fixed by raising the minimum CPU speed or re-flashing their phone? My friend and I both have Nexus S, both on CM7, and both have this issue of perma-black screen with non-responsive volume rocker/power button. The 4 capacitive buttons at the bottom (turned on due to a notification?) respond to touching and blink (turn) off when pressed and re-light when released. Screen animations are on, lockscreen is enabled. This has only started happening after rooting and flashing the CM7 mod, and not on an unrooted stock rom.
Should I be increasing the minimum CPU speed, or increasing the maximum CPU speed? I have SetCPU and am currently on smartassV2 when screen off, which has CPU speed from 100-200 MHz. Since the phone goes to deep sleep anyways, would I need to be raising the deep sleep cpu speed (is it 0?) to over 128, or what? The maximum speed is already over the 128 MHz, and the min speed of 100 MHz shouldn't have an additional effect (since deep sleep is already lower than 100 MHz).
Is a reflash necessary, or just a wipe of the cache/Dalvik cache?
Anyone with personal experience in fixing this issue?
I had a a similar issue and I found that for some reason with my phone and particular roms I just could not use them. Not 100% sure Y. I would try a different Rom and see if the problem happens again.
Oh and if you are going to re-install the same one again to make sure it was completely done I would wipe both caches and user data just to be sure.
I've already got a few power saving options checked with Suite Tools, what does the "Save Power" do in Quick Settings?
I didn't notice screen brightness adjust when I activated, just wondering what else it does.
Ignition75 said:
I've already got a few power saving options checked with Suite Tools, what does the "Save Power" do in Quick Settings?
I didn't notice screen brightness adjust when I activated, just wondering what else it does.
Click to expand...
Click to collapse
I think it's conserves the cpu usage, reduces the brightness, turns off haptic feedback and disables data when screen off.
dr9722 said:
I think it's conserves the cpu usage, reduces the brightness, turns off haptic feedback and disables data when screen off.
Click to expand...
Click to collapse
I've already limited CPU to 1 core & 1Ghz, reduced brightness and disabled data/gps when screen is off through Suite Tools, just didn't do haptic feedback.
Thanks for the clarification.
1 core with 1GHz will not save any power.
In single core mode, cpu will be clocked max, almost all the time to hande all tasks. It will take longer for cpu to compute = more time cpu stressed = more power consumption.
Limit cpu to dual-core 1-1,2GHz.
Ignition75 said:
I've already limited CPU to 1 core & 1Ghz, reduced brightness and disabled data/gps when screen is off through Suite Tools, just didn't do haptic feedback.
Thanks for the clarification.
Click to expand...
Click to collapse
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
BasicallyCP said:
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
Click to expand...
Click to collapse
Only thing I've noticed is when I have my phone set to Extended and I've set Max Brightness to 80%. However, I've seen my Brightness go over 80% on Auto especially when I was outdoors (saw it hit 100% and Boosted). Under Manual Brightness, I can have it go to 100% too. So that 80% is misleading?
Good find. I was wondering too since the prediction page instantly applies a gain in standby hours (and a significant one at that) by just enabling the "max brightness" feature. Since it can not know when or for how long the display will be on and what range the "auto" feature will use in a given situation, it seems like a very optimistic value, especially if you just use a limit of 95% for example.
But regarding your question, it's indeed strange to see "auto" exceeding the max brightness limit. I mean, the limit is there for the auto mode only. Might be a bug, unless we struggle to see the logic behind acting like that.
Personally, I would leave max brightness alone since it's more useful to have the display ramp up to max in order to actually see something when needed. If "auto" generally sets up the display as being too bright, one can still adjust the slider (even in auto mode) to tune the point of optimal brightness. I think it acts as an offset to the actual (internal) value the automatic comes up with. At least, that's how I perceived the feature on this and other phones so far.