Related
I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
webber2109 said:
I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
need help....
what other profiles do you have?
i have 2 profiles.
one is 245 min 245 max when screen off (priority 100)
the other is 245 min 998 max when charging or full when charging (priority 50)
did i do anything wrong?
Has ur SetCPU got granted by SuperUser?
lpachuong said:
Has ur SetCPU got granted by SuperUser?
Click to expand...
Click to collapse
yup it is. in fact it was working properly until i leave it to charge. i tried uninstalling and re-installed but still it clocks at 998. the sleep profile doesnt seem to work well too
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
amf said:
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
Click to expand...
Click to collapse
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
webber2109 said:
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
Click to expand...
Click to collapse
Yup it works. Screen off profile--> Max=384 // Min=245
Try a ROM that supports interactive governor.
EDIT:
My "Time in State"
245 = 1352167
998400 = 18389
Ok .. so, seeing many questions w/o real answers regarding the power consumption of the GN under various circumstances, I decided to create some testing conditions and generate some data.
The original idea and requirement started on Franco's kernel development thread but as this topic might be of interest I decided to create its own thread.
Test conditions:
- device: Galaxy Nexus i9250 - GSM version
- rom: bigxie's rom
- kernel: Franco kernel
*************************
1. IDLE test
2. MP3 play test
3. DISPLAY test
4. CPU Power test
5. Still image test
6. MKV play
7. Additional Display, MP3 play, YouTube and TuneIN media streaming
*************************
If you have any suggestions of tests you would like to see, please drop me a PM so I can make a list and implement them (depending on my possibilities).
*** Original post was heavily modified due to inaccurate measurements. The replacement posts linked here are the ones that matter ***
Why exactly did you decide not to run tests with wifi and 3G/2G, like grabbing and playing a youtube video?
That was the plan but seeing that I don't have enough resolution for this run, I decided to keep the test as simple as possible.
In few hours I'll do a more detailed run, with 1mA reasolution and I'll include online media too, as well as wifi versus 3g power comparison. It looks like a long friday night for me
// sent from my green robot //
ro_explorer said:
It looks like a long friday night for me
Click to expand...
Click to collapse
Haha! Well... I'm already looking forward to those higher res tests... don't forget to include 3G vs 2G as well, because I'm really not sure if there is much of a difference since you take so much longer to load... oh, maybe not a late friday but an early saturday?
thanks for doing these tests, its a great idea and cant wait for more results.
Yes. Thanks. Definitely need more.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Thank you for support guys .
I've managed to build the new test circuit. I can now read the current with 1mA steps.
As a first set of measurements with the new setup - idle power .
Kernel and rom - see first post.
HotPlug function is a feature of Franco's kernel to turn off CPU 1 while phone is in sleep mode (in case some of you are wondering). It is supposed to be a feature to save power while phone is idle.
Voltage constant at 3.9V over all set.
1. AIRPLANE MODE - any governor, both 350-1200 and 700-1200 frequency range:
1.1. HotPlug OFF - 3 mA steady
1.2. HotPlug ON - 3/4 mA - the multimeter was unable to choose a value
So .. in airplane mode, the standby power is between 11.7 - 15.6 mW
2. 3G mode,WiFi - OFF, interactive governor
2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
2.2. Freq: 700-1200, HotPlug - OFF - 4/5-8 mA
2.3. Freq: 350-1200, HotPlug - ON - 4-8 mA
2.4. Freq: 700-1200, HotPlug - ON - 4-7 mA
3. 3G mode,WiFi - OFF, conservative governor
3.1. Freq: 350-1200, HotPlug - OFF - 3-8 mA
3.2. Freq: 700-1200, HotPlug - OFF - 3-8 mA
3.3. Freq: 350-1200, HotPlug - ON - 3-7 mA
3.4. Freq: 700-1200, HotPlug - ON - 3-6/7mA
4. 3G mode,WiFi - ON, conservative governor
4.1 - 5GHz WiFi
4.1.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.1.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.1.3. Freq: 350-1200, HotPlug - ON - 4-7/8 mA
4.1.4. Freq: 700-1200, HotPlug - ON - 4-6/7 mA
4.2 - 2.4 GHz WiFi
4.2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.2.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.2.3. Freq: 350-1200, HotPlug - ON - 4/5-8 mA
4.2.4. Freq: 700-1200, HotPlug - ON - 4/5-8 mA
When NOT in airplane mode, my phone has data and sync ON, and (over night at least) only Google services are being synced - gmail, g+, gtalk.
The measurement with data on/off, sync on/off are identical to the data on, sync on, when there is no activity that is. So, the the only way the phone will consume more power when data/sync is on is exactly when an event is being synced .. the rest of the time the radio being idle, identical with data/sync off.
Conclusion regarding IDLE (in my case at least): best power saving while phone idle is with WiFi off while screen off (or on only when plugged), conservative governor, 700-1200 freq. range and HotPlug - ON. Of course these values are experimental and are specific to my device but the numbers are looking reasonable.
I did not take any video of the above measurements because it was really boring .. put device at sleep and wait for it to really sleep (about 2 minutes for each test). But I'm attaching a photo of the test bench .
... to be continued with awake tests with video capture also ...
Awesome work!
I can think of one more scenario that's worth testing: when the screen is off but there is a wakelock keeping the CPU awake. This would give us a baseline of CPU awake but screen off, which would tell us exactly how much juice is going to the screen and CPU when the device is on.
Would MP3 play in background meet your expectations?
ro_explorer said:
Would MP3 play in background meet your expectations?
Click to expand...
Click to collapse
Wakelock but idle would be ideal I think, but actually an MP3 playing might be perfect if you can compare MP3 playing with the screen on in one of the previously tested states and MP3 playing with screen off. Then some simple subtraction should tell us everything we need to know.
I'd like to be able to calculate how much is used when the CPU is awake due to a wakelock, and how much power is saved by getting out of that wakelock ASAP to get back to power collapsed state. It might turn out that ideal screen off profile is 920 or even higher.
Good stuff. Glad someone is taking their time to collect this data.
Something to try: Loop a program to browse site content with white (light) heavy colors vs black (dark) heavy colors.
excellent info. if anyone's interested we did a similar test with the nexus one where we were able to use the actual resistor in the fuel gauge chip within the battery. so we did various testing scenarios, and that phone pulled very high currents. seems like our galaxy nexus is actually more efficient with some of those screen tests.
here's the link, prob boring though since it's not our shiney new GN.
http://forum.xda-developers.com/showthread.php?t=998544
This is my simple, yet efficient circuit (and quite precise I might say).
As you can see, the sense resistor is quite small not to interfere with normal operations and I think the 1% tolerance is making it perfect.
MP3 test
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off, no mp3 play and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
The above values are with 350-1200MHz freq range, conservative gov.
The frequency CPUs have used during screen-off play was 350MHz. If I'm increasing the min. frequency to 700, the average consumption is increasing with an average of 2-3mA.
ro_explorer said:
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
Click to expand...
Click to collapse
Perfect. Thanks so much for taking the time to do this. I had been trying to come up with a semi-scientific way to measure some of this stuff and you just hit it out of the park with this.
Do you know what frequency the CPU was at when playing the MP3 with the screen off?
Display test
This is the hi-res (1mA) display test: http://www.youtube.com/watch?v=cqSQ5QE-4S0
Values (with device awake, of course):
- auto brightness, relative low light conditions, dark homescreen: 162mA / 3.87V = 0.14W
Maximum brightness:
- white screen: 380mA * 3.8V = 1.44W
- red screen: 287mA * 3.83V = 1.1W
- green screen: 295mA * 3.82V = 1.127W
- blue screen: 327mA * 3.81V = 1.246W
- gray screen (50%): 240mA * 3.84V = 0.92W
- black screen (but awake): 147mA * 3.87V = 0.57W
aron7awol said:
Do you know what frequency the CPU was at when playing the MP3 with the screen off?
Click to expand...
Click to collapse
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
ro_explorer said:
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
Click to expand...
Click to collapse
Thanks, my guess is that this CPU can play an mp3 at 350 MHz just fine
I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
ro_explorer said:
I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
Click to expand...
Click to collapse
Sorry to keep bothering you for more, but do you also know the CPU usage playing the mp3 at each frequency?
The final question I'd like to be able to answer is: Is getting to idle faster at the expense of using a higher frequency to get there beneficial?
I guess to answer that question we need to separate how much power the CPU uses at 100% CPU usage at 350 MHz, 700 MHz, 920 MHz, etc.
Hi all, first post here at xda, am fairly new to android devices and am wondering if someone could share some knowledge please? After installing my first Rom (m1ndh4x3r 2.3.5) I haven't been receiving any calls... A friend today said I may be underclocking the phone too much for it to wake on time to ring? Had it set at 200mhz with screen off. After setting it to 480mhz I received a call straight away, question is, have you had this problem too and what's the lowest setting advised that I can have it on please?
Thanks in advance for any help/advice
Your phone is built to run at 600 MHz. Not at 200. You can use apps like setcpu and no frills cpu control to control your phone. These apps let you set the minimum and maximum value of the cpu frequency. You should let it run at its full capability. Optimal settings would be something like
Min: 320
Max: 600
Governor: smartass2
You can underclock more when you are not using it or not expecting calls ( in the night).
You can also set your minimum to 120 MHz, but usually, it'll go into deep sleep mode, rather than stay on 120 MHz. Also, when listening to music, I've noticed, it stays on 320 MHz.
My minimum setting is 120 independently from which ROM (i tried 5 ROMs) I use (3month use = 0 problems).
Ive got blu Kuban 1.0.4.3 ROM on my phone with the attatched Kuban Kernal 3.0.15 and am having battery issues. I just recently deleted my facebook widget thinking maybe thats doing it, but it will last about 4 hours before it dies. Im downloading bad ass battery monitor to see if I can further look into whats sucking the battery power.
GO to developer option and click do not keep activities
maybe there something runing on the background you have to look at under battery or in appliication
OK I did that ill see if it changes anything. As of 72% battery left, battery monitor shows 69.8% app usage, and 51.8% is the Kernel. All of the apps listed don't use much under app usage its the kernel that is killing it. Does this mean I need a new Kernel? This cant be normal right? Can I use just any Kernel? Thanks
51% kernel is high, yes. See if other people have the same percentage with that kernel. If not, then maybe try a different kernel. agat's or sleshepic's kernels are also good and built from source. Btw, I wouldn't advise doing the Developer Options setting change to close all activities. That setting isn't meant for ordinary use and severely limits your multitasking abilities. "Closing apps" also has a minimal effect because of the way Linux deals with RAM. It turns out that opening and closing apps takes away more battery than keeping one running in the background.
If your battery isn't good, diagnose why with the following apps:
Betterbatterystats - Download this app and check your "Partial Wakelocks". Basically this checks what apps are waking your phone up when it's sleeping.
CPU Spy - This allows you to easily see how much time your phone has spent in each state. You get really bad battery life if your phone idles on 200 Mhz instead of Deep Sleeping. Your phone should be on Deep Sleep when the screen is off, or else your idle battery drain will be fast.
Other ways to save battery life:
Tweaking system settings
Get SetCPU/Tegrak/Voltage Control/Any other CPU Settings app and undervolt each of your processor states to -50 mV. By stock your phone's states come "overvolted" and you can conserve battery without loosing performance if you slightly tweak them. Don't go too low or your phone may get unstable and crash.
Use those same apps to underclock or set profiles to underclock under certain circumstances
Use those same apps to change your governor. Read up on different governors and how they scale your processor when needed. Here is a link that explains different governors - http://forum.xda-developers.com/showthread.php?t=1369817 . Usually "conservative" and "SmartassV2" and "Lulzactive" are pretty good with battery life. It all depends on how much performance you are willing to give up for low battery life.
Use those same apps to change your I/O scheduler. The scheduler, in simple terms, basically describes in what order apps will run, which will be prioritized, etc. The "SIO" scheduler is probably the best balanced one. "Deadline" I believe saves more battery life but maybe slow you down a little.
Apply tweaks that do it for you
In the general section of our forums, a developer named PhAkEer has posted some tweaks. His "dietpill" battery ones are really good for keeping your phone fast but saving battery life. If you have these tweaks though, they automatically choose a governor and I/O scheduler so manually changing them will only interfere if you decide to do this.
Change simple unneeded settings
Another reminder is that simple things can save you a lot of battery life. Turn off haptic feedback. Take off pulse light notifications (there are reports that these wake up your phone from Deep Sleep and put the processor back into the 200 Mhz state... thus taking away battery life). Turn off 3G when not needed (3G and 4G are huge drainers). Set WiFi to turn off when your screen is off. There is a ton of other stuff you can do.
Well I hope this long post helps you in your quest to find better battery life. Good luck
Tried putting the new agatas kernel on my phone and nothing has changed. CPU Usage shows 200MHz is 79% of sleep while deep sleep is only9. How to I go about dealing with this?
Check your wakelocks with Betterbatterystats. Otherwise just play around with some settings. For me it's usually WiFi that keeps my phone in 200 Mhz. I set WiFi to turn off when the screen is off. Maybe you have an app running that actively requires your phone's processor or something.
partial wavelocks is MAIL SERVICE - at 6.5% 5m 54s count 1953, AudioOut_! is 4.9% count 7 5m 54s, Juice defender 1.6% count 447 2m. So is it my email then? What is Kernel wavelocks?
any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...
I saw a post saying these are stock voltage -- is it correct?
200 MHz = 950 mV
500 MHz = 975 mV
800 MHz = 1075 mV
1000 MHz = 1175 mV
1200 MHz = 1275 mV
1400 MHz = 1275 mV
1504 MHz = 1350 mV
1600 MHz = 1425 mV
1704 MHz = 1475 mV
bhollehday said:
any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...
Click to expand...
Click to collapse
What is your awake time versus you screen on time. If you are having signal problems test out other modems which are in the updater. Make sure you update prl and profile afterwards in about phone. Not having signal/service will kill your battery no matter what because it then tries to search for it constantly. Last week I was somewhere that had no service in my hotel room. For 18 hours in my lab it only drained 10% with about 2 hours of usage, then I went to sleep for 6 hours and it was down another 40%. I turned it on airplane mode to save battery. Hopefully trying a different modem might help. If not I have some suggestions for that too.
So when my phone screen is off, and I receive a call, the ringtone plays for about 3-4 seconds and then half way through the ringing, the screen turns on. I'm running ktoonsez kernel version 6/10
Do I need to increase a setting or something?
Have your off screen MHz too low I bet.
stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.
Skipjacks said:
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.
Click to expand...
Click to collapse
stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)
Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...
kevinrubio1 said:
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)
Click to expand...
Click to collapse
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
stevessvt said:
Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...
Click to expand...
Click to collapse
Okay I increased it to 378 Mhz and my screen off to 594 Mhz! I'll leave my phone to the side for a couple of minutes and see if it has the delay or not!
Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?
kevinrubio1 said:
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?
Click to expand...
Click to collapse
Yes. Same thing.
Skipjacks said:
Yes. Same thing.
Click to expand...
Click to collapse
It worked! Thanks skip
Sent from my SGH-M919 using xda app-developers app
Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.
elesbb said:
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.
Click to expand...
Click to collapse
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?
kevinrubio1 said:
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?
Click to expand...
Click to collapse
Yes you would save battery. And that should be high enough to let the processes carry out.
Sent from my SGH-M919 using Tapatalk 2
where is the screen setting menu??
i have the same problem how do i find the setting?