I've heard that having your screen off setting to 128mhz that it drains more battery than 284mhz and does not let the evo perform correctly. Is this true?
I have mine to 128mhz atm and dont seem to notice qany diffrence in battery loss to when it was at 284. I have only had it this way about 24 hours but so far not a big diffrence one way or the other
Haven't noticed any extra power drawn, only thing I noticed and hate is that when you wake up it can lag bad, until the profile changes to a higher clock
Sent from my PC36100 using XDA App
Im interested in this also. I saw some people say 128 drains more battery but nothing to actually show it. I am running some tests of my own currently. Im sure it will be hard to see a difference unless there is something crazy going on.
It must have been me who posted about the 128Mhz bug first.
I'm running latest ota stock rooted, latest ota radio/wimax with Netarchy's 3.0 or 3.7.3c kernel.
I noticed that when I had 128-998 set on boot, the phone wouldn't sleep properly, and the battery drain in standby mode was ~3x what it normally was.
The normal battery drain for my configuration is about 1% an hour in standby.
If you are running a different rom/kernel, I suppose, it's entirely possible not to see this problem. Test it yourself and find out.
I have had my Evo clocked at 128 for Min and Max for about a day. I initially thought the reports of uneven performance were wrong, but a few runs of Pandora during "Screen Off" did cause some long pauses and some FCs on a couple of occasions. I suspect this is why many recommend increasing the clock to 245, especially when you have process heavy apps running.
I personally don't think the difference in such low clocks will have a significant impact on battery life, but for those of you who get the warm and fuzzies from the absolute lowest setting, I have been playing with my Min @ 128 and Max increased to 245 for a couple of hours. It's jumping out of the low clock much smoother (I can immediately drag the lock bar down) and I haven't gotten any FCs while using Pandora with the screen off. I have ran Pandora with the Screen Off and the "adb shell powertop -d" from my terminal. It is reporting that my Evo is staying in the 128 clock, but, like I said, it's transitioning to higher clocks without a hitch when I turn it on.
Hope that helps.
I've also found that 128 is just too low for things to work properly. It stutters a lot when the screen comes on and things like music also stutter.
Having tested this for a little over 24 hours in response to the increased battery drain, I could not tell any additional battery drain still after 24 hours. On the flip side i could not tell of any additional battery saving either. At the end of the day i was in my normal range.
I do not use the Stock rom but do use Netarchy's latest kernel. So ti may just be a stock rom thing. I will agree that the screen comes on sluggishly and music will skip if you have it playing with the screen off. Since i was unable to tell any significant benefit from lowering it i will be stick to 284.
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Due to some of the instability I've gotten, I've decided to bump up the Min to 245. It runs much smoother and I cannot see a difference in battery life. I think the occasional lag and FCs that 128 might cause will hurt your battery life before the increase in clock will. I'm now with the "128 is not an option" camp.
scriptx said:
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Click to expand...
Click to collapse
What is your screen off profile, min/max? Obviously 285 is min, but what is your max? What about when the screen is on?
I have my screen off setting for 245 min & max. I get no stuttering pandora and it doesn't **** itself when I turn the screen on. The transition to normal is smooth.
I am getting over 40 hours on battery....
with the set-up in my signature below.......
I have Set CPU set to 245/128 with screen off. I get almost no drain with phone resting. Went to be last night and when I picked up my phone this AM, it was still on the same %. This has been consistent for the last 3 nights.
If you go to the baked snack rom thread, towards the last two pages as of today....I discuss my set up. Others are experiencing the same kind of battery results.
I get no hiccups from resting to on. Pandora plays fine. If it needs the 245 for Pandora or such, it's there. If not, it goes down to 125 and uses almost no battery over an extended period of time.
I just tried setting 128 as min and 245 as max for screen off and my phone got stuck in a boot loop. After sitting idle for a few minutes it started rebooting on its own.
I had to remove the battery and was then able to get into the OS. I have since set my phone back to 245 . I will update if I find out this was happening for another reason or if I try 120 again.
Related
I'm running burnt droid with the latest kernel and I have setcpu.
What are you doing in those 5 hours?
That's the problem, my phone is in sleep and still draining. When I'm texting or using any app I can watch my percentage dwindle.
try damagecontrol 3.2.3, i've gotten the best battery life from that rom. are you running 4g during those 5 hours?
No, 4G is not in my area yet. I'm going to recalibrate my battery and see if that helps. Is there any recommended setcpu settings?
I think there's a whole thread listing peoples' preferred SetCPU settings. My advice is to set your highest priority profile as "Screen off" and make it 245 min, 384 max. After that, set one for charging, then one for battery < 100%, all in descending priority. The important one is having the CPU go real low when the screen is off, in my opinion. I have mine 245/245 so it's just bottomed out when the screen is off. It helps.
Side note: I think 245 is the lowest setting most people recommend, 128 causes lots of problems in some cases.
Also, if you change ROMs a lot, I think it wipes your battery stats every time, so you probably do need to recalibrate. Cyanogen wrote up one method a while back. It's the one I used, and I feel like my battery is normal now.
Hey all,
I'm having serious battery drain on MIK 2.56 and pretty much any ROM that I flash. I'm running Chopsuey9.2.7 along with SetCPU profiles. I underclock the majority of the times.
My SetCPU profiles are:
Set on Boot = 691max/245min conservative
Charging = 1152/245 performance priority 100
Screen off = 245/245 ondemand priority 99
In-call = 1152/245 performance priority 98
Battery <50% = 691/245 conservative priority 97
Temp >43.7 degrees = 614/245 conservative priority 96
My evo doesn't like to be clocked at 128 or even 499. It reaches temps as high as 115-120 degrees during charging and while in my pocket (I'm thinking it may have got damaged when I used to run the SBC kernels in the early stages). Im starting to think that i have a bad battery. My battery will drain from 100% down to 80% within 5 minutes and usually will be dead within 2 1/2 hours after being off of the charger with moderate usage such as calls
text and checking email. I have Autokiller running and have set memory Lowmem settings to extreme thru Darktremor a2sd.
Any ideas/suggestions?
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
My stock battery lasts all day with my current setup. I have setcpu as well but don't really mess with it. I use Smartass governor with 1075/245 for normal everyday use. If I have too many drinks and have to crash at a friends house without my charger I'll drop the max speed to about 700 and use conservative or just switch the governor to powersave. Then I've got more than enough time till I need to get back to a charger.
i got good life on that ROM using Aggressive Freedom kernel & using set cpu at 245/768 set at boot....no profiles.
So you think the use of profiles is the issue? I'm not completely sure the profile for screen off is working correctly; I ssh'd into my EVO and took a look at /proc/cpuinfo but it will not show the current cpu speed.
I'll give it a shot without profiles and see. As for the govenors, I believe Smartass was removed and replaced with InteractiveX; is InteractiveX as good?
j7jman said:
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
Click to expand...
Click to collapse
I agree but with the way my profiles are set, I'm underclocking the majority of the time and only overclock when charging or on a phone call.
ive noticed i get wose battery life if i set up profiles. Worth a shot.
Sprint will test the battery for charge free I actually did it today
Sent from my PC36100 using XDA App
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
r.storm85 said:
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
That's correct. Also check your spare parts app for any wake lock.
Also, if you're using a havs kernel, setcpu will conflict with the kernel. And in general, you'll always get better battery life on AOSP.
try using setcpu sometimes that will help save battery.
Disabled Profiles in SetCPU....no luck
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Just left Sprint. They tested the battery and it tested bad and was swollen. I got a stock replacement free of charge although he said they normally would have charged me because the 1yr factory warranty expired. He also went on to say that the battery going bad was possibly caused from my phone being rooted which he may be partially correct. The problem began when SBC first came out and I was testing on the beta stage. It nice to have my phone off of the charger and not be down to 60% within 45 mins!
Sent from my PC36100 using XDA App
lostsoul77 said:
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Click to expand...
Click to collapse
my phone has been doing this exact same thing but i took it to sprint they said my battery was good should i go to another sprint tech and let them test it out?
I'll wake up in the morning to find my phone off and extremely hot. It will also randomly reboot throughout the day and won't stop until I remove the battery. Any ideas on whats going on and what I could possibly do to fix it?
Sounds like either the screen is staying on....or its overclocked waaay to much... A voltage setting.... Or simply just some app or widget running 24/7
Causing the phone to get hot....make sure tethering and wifi are off at night while your sleeping... Kill the GPS if your passed out too...
Sent from my SPH-D710 using XDA App
Wifi may be the culprit for the overheating issue, but throughout the day wifi and 3g are barely on unless I need internet. Kinda frustrating when you're in the middle of something and your phone randomly reboots and doesn't stop rebooting until you pull the battery. lol I was also thinking it could be the rom im on (always used blazer) but no one else is having the issue therefore it's probably not the rom.
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
KCRic said:
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
Click to expand...
Click to collapse
The phone will lock up right before it reboots over and over. When the phone starts up it'll stay on for a couple minutes and then restart. It will keep doing so until I pull the battery.
I'll download one of those apps and see what I can find.
arsmithsr said:
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
Click to expand...
Click to collapse
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
adima said:
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
Click to expand...
Click to collapse
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Android300ZX said:
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Click to expand...
Click to collapse
At night I set it on my nightstand and there is nothing by it, and it only does it about once a week i'd say. Kinda frustrating when you set an alarm to get up at a certain time and it doesnt go off cuz the phones off. I do have a real alarm clock, but I know how to turn it off in my sleep. Using my phone allows me to have to answer an equation to turn the alarm off. It's no big deal if I don't get up with an alarm during the wk, but it is nice to get up early and get a head start on the day. Now that I think about it, maybe the alarm clock app i'm using is causing the phone to overheat at times...
Drat!
I was hoping someone was able to diagnose and solve this issue. I've had this same problem/behavior for the last month now. And it's only getting worse :\ Also worth noting is that when the battery overheats, it smells like dill+mint (very weird) ... so it may be a bad battery. When I get a sec, I'll run to the sprint store and pick up a new one and test that out for a while.
Take the battery out and try to spin it on a flat surface... does it spin freely? If so its bad
Sent from my SPH-D710 using Tapatalk 2
I have had this problem a couple times before but it stopped for a long while. Then last night when I was charging, it overheated and shut off but this time it won't charge again, won't turn on at all and when it's plugged in there is a very dim blue light that flashes where the notification/charging LED is. I can barely see the light flashing but it is there. When I first plug in the charger I do see the battery with the loading animation and the battery is empty but then the screen goes black after a second or less and the dim blue LED starts flashing.
I let the phone and battery cool down for a long while, took it out and set it out for a while and it still won't charge at all. This really sucks because I have a 3-day weekend and I can only play Guild Wars 2 on the hotspot on my phone that won't turn on
I am using Mijjz Blend The Goodness with Sleshepics the governers 1.2.3 kernel that was flashed through the ROM updater, it's been working fine for the past couple weeks. I am not using any overclocking/undervolting profiles or anything like that besides what was put into the kernel already.
Please help D: I really want to play Guild Wars.... Q,Q
hope this helps,
i also have setcpu install in a stock rom with overclock and underclock enable
here is the profile settings in my setcpu that might help you solve your problem
profile1.screen off => cpu speed is set 500mhz(high) to 200mhz(low) in governor.conservative mode
profile2.in call => cpu speed is set 500mhz to 200mhz in gov.ondemand mode
profile3.battery temperature is greater than 44c(111f) degree => cpu speed is set 500 to 200 conservative
profile4.11pm to 7am(sleep time) => cpu speed is set 500 to 200 conservative
profile5.battery percentages drop less than 50% => cpu speed is set 1000mhz to 200mhz in ondemand mode
whenever those conditions hits when the phone is on, setcpu will lower the speed for me and consequently reduce the heat issues for me
because i run my phone in 1.7ghz ondemand mode all the time. my phone is the white version which have a newer cpu and i know for a fact
that the older black version epic4g-touch can only go as high as 1.5ghz before problems arise such as kernel panic and overheat
good luck
I had this issue. Man, after a month of looking for a solution, i think I found a solution, at least for my issue. My phone would reboot at least 5 times in a row, and get very hot. This is what worked for me; when the phone reboots, take the battery out, wait 5 seconds, hold power button and volume down to get to reboot into recovery, wipe out Dalvik cache, and then fix permission and reboot.... Hope this works for you too.
Sent from my Samsung S2 ET4G using Tapatalk
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
hshaikh said:
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
Click to expand...
Click to collapse
I suggest to decrease your max CPU until you feel it affects performance too much. You can also try switching to a governor less aggressive than interactive (try ondemand).
Don't expect magic though. I've played with decreasing max CPU clock, max CPU screen off, governor settings etc with three different kernels. Gathered stats for at least one week each time. Never noticed a difference large enough to actually matter to me. For maximizing battery life, you can gain more by hunting apps that cause a lot of (partial) wakelocks and alarms, and use low screen brightness.
hshaikh said:
and screen off max is 384.
with all that information, what do you suggest?
Click to expand...
Click to collapse
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Darunion said:
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Click to expand...
Click to collapse
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Petrovski80 said:
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Click to expand...
Click to collapse
you are correct. there is a magic middle ground because power consumption doesnt scale in a linear way. but finding that spot would take massive testing and even getting to the center, would still probably only gain about 10-15mins average use on a battery charge :/
bk201doesntexist said:
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
Click to expand...
Click to collapse
what speed show i set to max when screen is off.
did you read anything that Darunion and Petrovski80 wrote? I keep mine at it's max, i don't care, i don't live in the woods with no electricity.
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
hshaikh said:
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
Click to expand...
Click to collapse
Exactly. I get similar performance.
Sent from my Galaxy Nexus using Tapatalk 2
Might seem an odd question, but how much should I expect the battery to drain on the M8 while playing music?
Reason I ask is because I use my phone to help me sleep (brown noise) every night.
I use an app called "Chromadoze" which has been fine for me up until now.
My old Nexus 5, which I partially got rid of because of the battery life, would drain approx 25% in 8 hours using Chromadoze.
However, using the same app on the M8 drains 50% in 8 hours, which seems excessive for a phone touted as having far better battery life (and indeed it normally does under normal use).
Thinking it might be the app, I generated a (59 minute) brown noise file and converted to FLAC and copied to the phone, and set that to play on repeat. This still gave a drain equivalent to 50%. I thought the Snapdragon 801 was mean't to be very economical on the battery for music, but that ain't happening here. I even have the phone in flight mode (as always). The battery stats are telling me that indeed the "music" is to blame.
I'm disappointed with this as I could stream actual music from the cloud all night on the Nexus and get less drain than that.
The other thing thats proved to be disappointing is the time it takes to charge. I have a 2A blackberry charger that I used on my N5 that charged it in just over an hour, but this M8 takes well over 2 hours on the same charger. I realise it has a bigger battery, but its still only 10% difference and it should probably only take an extra 10 minutes or so, not double the time. Can I enable fast charging on this device, after all, the 801 again is supposed to be able to support it.
I am a tad disappointed with my move to the M8 so far because of these issues; it has better battery life overall but these issues make it significantly less useful to me.
I have such an issue with this phone, that whenever I use (so deep sleep isn't allowed) the 50% of the cpu time is always at 1036mhz, which is too much even for listening to music.
Check out by yourself, how the cpu is working, by installing cpu spy (additionally you can install wakelock detector).
If it's the cpu's fault then you may try to set custom settings (max speed) for cpu when the screen is off.
Sent from HTC One m8, or maybe not anymore
Thanks for the reply. I'll check those apps out you recommend.
My next move is to try again with the power saver turned on, and see how it goes, failing that as well, I could try without the boomsound activated, as I'm sure extra EQing will use CPU power.
I hope I can resolve it, as it will be disappointing if not, especially as I really liked the Nexus as a phone but thought this would be a nice upgrade in most respects (bar camera).
I personally think that this power saving mode just sucks, all it does is that it saves data, but not cpu, as it doesn't put apps to sleep, as stamina mode on xperia devices does.
Just make a quick test, turn on your app, then switch to cpu spy, reset the statistics (so you get statistics only while using your app) and turn off the screen and wait few minutes.
Sent from HTC One m8, or maybe not anymore
When your listening to music at night is your WiFi on and connected?
Ive noticed a strange bug on my device.
When my device is in stand by mode and wifi is connected my CPU usage never drops below 30%. I use SystemPanel Pro to check that.
Now with WiFi off and in stand by mode my CPU usage is between 3-7% with spikes to 10-15% every 20-30 minutes. To me that seems normal.
So if you do have WiFi on while its playing music for those 8 hours test it with WiFi off.
Hi, I would normally use Airplane mode, so no radios at all, unless I wanted to stream from cloud, I've not done that yet since I had the phone, though.
I've just done my first test with CPUspy as suggested, Over 35 minutes it spent 10 minutes @ 1,036 MHz and the remaining time (about 67%) @ 300 MHz.
I'm trying it again with the supposed "Power Saving" function on.
Result with Power Saving on
1,036 MHz - 7:32 - 17%
300 MHz - 24:29 - 57%
Deep sleep - 8:29 - 19%
BUT, i have a feeling the power save mode may have killed it off to go to sleep but I couldn't confirm as it hadn't occurred to me until I had messed about.
So it is slightly better provided it didn't kill the music.
All of this was with a program called "7digital" which appears to be built in. Going to try in PowerAmp next.
PowerAmp seems to look much more economical.
95% (just over an hour) spent @ 300 MHz with just 2:26 spent at 1036 MHz.
Tried my brown noise last night and it drained 34% in 6 hours. Still a pretty poor performance.
Looks like I'm going to have to try and find an alternative way to do this.
I do wonder if the Google play ROM would help as I never had a problem on the nexus 5.
Are those the statistics when your phone hasn't been used at all or was your program running at this time?
If the program wasn't running and you have such a cpu usage then it is probably some deep sleep issue (wakelock detector should help identifying the app responsible for that).
Anyway, just use some app to limit the cpu usage while the screen is off.
This phone likes to be stuck at 1036mhz and for example you could limit it to about 500mhz.
Ps. Power saving mode won't kill these apps, so don't worry.
Sent from HTC One m8, or maybe not anymore
mr.loverlover said:
Are those the statistics when your phone hasn't been used at all or was your program running at this time?
If the program wasn't running and you have such a cpu usage then it is probably some deep sleep issue (wakelock detector should help identifying the app responsible for that).
Anyway, just use some app to limit the cpu usage while the screen is off.
This phone likes to be stuck at 1036mhz and for example you could limit it to about 500mhz.
Ps. Power saving mode won't kill these apps, so don't worry.
Sent from HTC One m8, or maybe not anymore
Click to expand...
Click to collapse
Those statistics were with the music player 7digital running a brown noise file, but nothing else was being used on the phone.
Later I used PowerAmp which does give a more efficient performance, but sadly, still not good enough really considering my N5 was OK under the circumstances.
I find myself in two minds as to whether to try the GPE ROM anyway, as I don't find the phone as responsive as the N5 either... and maybe it will help with this issue too.
tameracingdriver said:
Those statistics were with the music player 7digital running a brown noise file, but nothing else was being used on the phone.
Later I used PowerAmp which does give a more efficient performance, but sadly, still not good enough really considering my N5 was OK under the circumstances.
I find myself in two minds as to whether to try the GPE ROM anyway, as I don't find the phone as responsive as the N5 either... and maybe it will help with this issue too.
Click to expand...
Click to collapse
GPE (and other non-stock based ROMs) will be much faster, that's damn sure, however I don't think this will solve the problem, as HTC one m8 has some weird issue with it's CPU.
I also don't know why it's using this 1036mhz continously, but you can't go below 300mhz if the device is working (like playing music).
Tty to limit your CPU at all the time (not only when the screen is off), that should also save some battery, however the battery life is still nothing considering the one from Xperia Z1.
In case anyone is interested, I did the conversion to GPE. Much better, now feels as fast or faster than my n5, but it now charges much faster and the battery life seems as good as before. Will try and test with some music at some point in the coming week to see if there is any improvement but I have my suspicion that it won't make much difference as I think it could possibly be the more powerful output and boomsound that increases battery drain... But.... We'll see.
Final post from me on this thread.
Its been several weeks now since I've had the GPE firmware installed on my HTC One M8, and I don't regret it one bit.
The battery life is at least as good, but I possibly think better, I'm generally always averaging 4+ SOT, whereas it would be just shy of that with the Sense ROM. The phone is also noticeably quicker at all times...
Finally though, the high battery usage during music IS cured. Using the Chromadoze app I talked about in post #1 results in 20% drain in 8 hours (compared to 50% on a Sense ROM). That is much better. I also no longer wake up to a warm / hot phone. And it charges faster.
So, in summary, the GPE ROM turns the M8 into the phone it should have been since day 1. I just wish it had the Sense camera, but the stock one is perfectly usable.