Related
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
You need to update your PRL ...
twigums said:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
Click to expand...
Click to collapse
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.
do i need to check set on boot under the scaling option
twigums said:
do i need to check set on boot under the scaling option
Click to expand...
Click to collapse
No. I would leave it unchecked. This has been known to cause some issues.
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.
on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.
most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.
having said that, i don't use setcpu unless i'm benchmarking and want to overclock.
kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.
Here's what I would hit up..
set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.
then for advanced i have sampling rate at 50000
Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed
Down threshold at 70% <- when the load hits 70% turn it down
That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.
just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand
My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").
Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.
I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g
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.
I just wanted to confirm my understanding of eugene's sleeper script since I never fully got a handle on it. As I understand it, prior to this our phones second core never truly went offline (even though system tuner read it as offline). Now, our second core always goes offline when the screen is off (even though system tuner reads it as running at 192mhz). Is this right? Also, does it go offline at low load time periods when the screen is off?
yoft1 said:
I just wanted to confirm my understanding of eugene's sleeper script since I never fully got a handle on it. As I understand it, prior to this our phones second core never truly went offline (even though system tuner read it as offline). Now, our second core always goes offline when the screen is off (even though system tuner reads it as running at 192mhz). Is this right? Also, does it go offline at low load time periods when the screen is off?
Click to expand...
Click to collapse
On stock rooted ICS (though de-bloted) second core goes into deep sleep no problem when task scheduler/governor commands so and regardless if screen is On or Off.
What Eugene's script is doing: constantly looping every 2/4 sec (or whatever) and checking if screen is On or Off and then force CPU1 to go offline regardless what Linux Governor think is appropriate for current CPU load.
It might very much happened that next moment (in between loop cycles) governor would turn CPU1 back online if load on CPU0 is above threshold.
If script loop would be too short then script itself would burn battery juice... so, I think best thing to improve battery life is just keep phone clean from unwanted background processes.
Also, it might happened in reverse, when screen is on and there is no load - governor would turn CPU1 off, but script will continue to force CPU1 online.
Vlad_z said:
On stock rooted ICS (though de-bloted) second core goes into deep sleep no problem when task scheduler/governor commands so and regardless if screen is On or Off.
What Eugene's script is doing: constantly looping every 2/4 sec (or whatever) and checking if screen is On or Off and then force CPU1 to go offline regardless what Linux Governor think is appropriate for current CPU load.
It might very much happened that next moment (in between loop cycles) governor would turn CPU1 back online if load on CPU0 is above threshold.
If script loop would be too short then script itself would burn battery juice... so, I think best thing to improve battery life is just keep phone clean from unwanted background processes.
Also, it might happened in reverse, when screen is on and there is no load - governor would turn CPU1 off, but script will continue to force CPU1 online.
Click to expand...
Click to collapse
So if I understand you right, the script does nothing radically different, all it does is override the original cpu handling to force cpu1 offline when screen is off? It doesn't put cpu1 offline a different way than before?
yoft1 said:
So if I understand you right, the script does nothing radically different, all it does is override the original cpu handling to force cpu1 offline when screen is off? It doesn't put cpu1 offline a different way than before?
Click to expand...
Click to collapse
What do you mean by "different way"? (Script writes 1/0 into Linux CPU driver)
Vlad_z said:
What do you mean by "different way"? (Script writes 1/0 into Linux CPU driver)
Click to expand...
Click to collapse
I'm not sure, I just remember Eugene saying that cpu1 wasn't truly going offline before his script?
I don't pretend to understand any of it, but I will tell you that when the screen is off, it eats much less battery then before using it.
Vibrantnew-b said:
I don't pretend to understand any of it, but I will tell you that when the screen is off, it eats much less battery then before using it.
Click to expand...
Click to collapse
that's very possible. If you have some background processes, using this script, you basically trying to make from dual core CPU single.
or this is just placebo effect... how did you test it? My phone goes to deep sleep no problem, overnight 4% for 8 hours.
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.
chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake
Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?
Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back