I've noticed significant battery drain on all the CM7 ROMs available at the moment. Some users report better battery usage (6-7 mA) than others (anywhere between 14-70 mA), so my questions are:
1. what is your idle usage? Use battery monitor widget to find out
2. what radio do you use?
3. do you find mobile standby/cell standby always consuming the highest drain, even when you have been actively using your phone?
djsubtronic said:
I've noticed significant battery drain on all the CM7 ROMs available at the moment. Some users report better battery usage (6-7 mA) than others (anywhere between 14-70 mA), so my questions are:
1. what is your idle usage? Use battery monitor widget to find out
2. what radio do you use?
3. do you find mobile standby/cell standby always consuming the highest drain, even when you have been actively using your phone?
Click to expand...
Click to collapse
1. Iddle consumption seems to be at 7ma
2. 20.28I.30.085AU_3805.06.02.03_M
3. Android System is highest at 56%, Mobile Standby follows it with 16%.
I'm on Superkid's CM 1.3 + Tiamat 1.0.4.1 with 2G only, sync off and CPU at 652 min and 1190 max, smartass.
Not running cm7 myself running with lbc but weve also identified a battery drain issue recently, we have come to conclusion that its intermittent and happens when wi fi is enabled.
See http://forum.xda-developers.com/showthread.php?t=1194786
Running with the latest radio 06.02.03
Sent from my HTC Desire S using XDA Premium App
rubbish said:
1. Iddle consumption seems to be at 7ma
2. 20.28I.30.085AU_3805.06.02.03_M
3. Android System is highest at 56%, Mobile Standby follows it with 16%.
I'm on Superkid's CM 1.3 + Tiamat 1.0.4.1 with 2G only, sync off and CPU at 652 min and 1190 max, smartass.
Click to expand...
Click to collapse
I'm using SuperKid's 1.3 + Tiamat 1.0.4.1 with 2G, sync off as well. However I'm using radio 20.28b.30.0805U_38.03.02.11_M, and my idle usage never drops below 14mA. I tried using the radio you use, however my idle fluctuated around the 20s and 30s with that. I'm so baffled as to why this is the case. Could it be dependent on the type of SD card?
ben_pyett said:
Not running cm7 myself running with lbc but weve also identified a battery drain issue recently, we have come to conclusion that its intermittent and happens when wi fi is enabled.
See http://forum.xda-developers.com/showthread.php?t=1194786
Running with the latest radio 06.02.03
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I am experiencing drains regardless of the WiFi. Every radio I've tried except hte default one it came with (in the post above) the idle power usage fluctuates heavily. But no matter what it never drops below 14 mA. I'm trying to figure out why it never hits single figures like some people are getting. It's not intermittent, it just refuses to drop below 14 mA.
djsubtronic said:
I'm so baffled as to why this is the case.
Click to expand...
Click to collapse
I'm not an expert for sure but please try the following as there'll be no harm anyway. Go into recovery, wipe cache + dalvic cache and then reflash Tiamat 1.0.4.1.
I wasn't doing any measurements before but I'm pretty sure that my battery drain used to be higher before I've done that. See if it helps.
rubbish said:
I'm not an expert for sure but please try the following as there'll be no harm anyway. Go into recovery, wipe cache + dalvic cache and then reflash Tiamat 1.0.4.1.
I wasn't doing any measurements before but I'm pretty sure that my battery drain used to be higher before I've done that. See if it helps.
Click to expand...
Click to collapse
Thank you. Trying that now.
Can you let me know if you did the boot image fix posted by NeoLojik after doing the above?
No, I didn't. I've tryed it at the earlier stage but since it broke wi fi I reflashed the original kernel (which was Carniab's test version at this time I think) and never got back to it.
rubbish said:
No, I didn't. I've tryed it at the earlier stage but since it broke wi fi I reflashed the original kernel (which was Carniab's test version at this time I think) and never got back to it.
Click to expand...
Click to collapse
Thanks. I'll try to clone your config and post with my results.
Tried your method above, but it doesn't go below 14 mA. I also tried a different SD card and still no luck.
Bump..........
Hi,
with CM 7.1.0 RC 1 and tiamat kernel v1.0.4.1, my Desire S consumption in sleep mode (no wifi, no bluetooth, Edge/3G enabled) is going down to 10-12 mA.
My best figure was with LBC mod 0.5.4 where it was 9 mA.
My radio is 20.28I.30.085AU_3805.06.02.03_M
Mobile Standby is 24% (which i find a bit weird too, with virtous/lbc never had that).
CPU is set to: smartass, 268-1036 Mhz
Overall i have no issue with CM 7 beta 1.1
zas666 said:
Hi,
with CM 7.1.0 RC 1 and tiamat kernel v1.0.4.1, my Desire S consumption in sleep mode (no wifi, no bluetooth, Edge/3G enabled) is going down to 10-12 mA.
My best figure was with LBC mod 0.5.4 where it was 9 mA.
My radio is 20.28I.30.085AU_3805.06.02.03_M
Mobile Standby is 24% (which i find a bit weird too, with virtous/lbc never had that).
CPU is set to: smartass, 268-1036 Mhz
Overall i have no issue with CM 7 beta 1.1
Click to expand...
Click to collapse
Thanks for the reply.
When your mobile standby was on 24% what was your phone usage like since you unplugged it?
Gsm only and almost no data since it was using wifi for data. No phone calls. ATM it is 25% ...
Sent from my Desire S using XDA App
i'm also use this radio & cM7 , but my gf found that my sound is lower than the sense rom while making a phone call
djsubtronic said:
Tried your method above, but it doesn't go below 14 mA. I also tried a different SD card and still no luck.
Click to expand...
Click to collapse
Hi dj
The difference between our measurements could be due to us using different tools? I've been using Battery monitor widget which, as I've read today, tends to give inaccurate (lower than in reality) figures. I'm currently on 1.3.2 version of CM from Superkid and BMW was also showing 6 or 7 mA. So I've installed Currentwidget and it displays figure of 12mA in sleep mode. This isn't far off from what you get.
rubbish said:
Hi dj
The difference between our measurements could be due to us using different tools? I've been using Battery monitor widget which, as I've read today, tends to give inaccurate (lower than in reality) figures. I'm currently on 1.3.2 version of CM from Superkid and BMW was also showing 6 or 7 mA. So I've installed Currentwidget and it displays figure of 12mA in sleep mode. This isn't far off from what you get.
Click to expand...
Click to collapse
I was using Battery Monitor Widget as well, and was getting 14 mA on that.
How do you check idle power on Current Widget? I just put it on my home screen using default settings, switched my phone to sleep for a minutes, then turned on the screen and it said 28 mA..
how about your battery?
is it a fake one?
djsubtronic said:
I just put it on my home screen using default settings, switched my phone to sleep for a minutes, then turned on the screen and it said 28 mA..
Click to expand...
Click to collapse
That's how I do it as well. 12mA. Could it be that you have poor signal coverage in your area? I can't think of anything else.
labstar said:
how about your battery?
is it a fake one?
Click to expand...
Click to collapse
Nope, brand new phone with the original battery. Maybe it's defective?
rubbish said:
That's how I do it as well. 12mA. Could it be that you have poor signal coverage in your area? I can't think of anything else.
Click to expand...
Click to collapse
I kept it on forced 2G mode, and the signal was very good..
Related
Just seen this on the front page.
It watches how much current your battery is using during standby or normal use. It writes a log with a time stamp and current.
Check it out. Download it and install from the market. Look for "CurrentWidget".
http://forum.xda-developers.com/showthread.php?t=797037
I'm running CM6.1 nightly with Collin's battery script and my log is showing as low as 31mA in standby. Anyone got lower running other ROMs?
I got a 18 running Extremely Blue OCT25th and OC widget set to 352 with screen off. Not sure if I did it right though, I set phone down for close to 10 minutes, picked it up and looked at widget, said 18mA.
cordell12 said:
I got a 18 running Extremely Blue OCT25th and OC widget set to 352 with screen off. Not sure if I did it right though, I set phone down for close to 10 minutes, picked it up and looked at widget, said 18mA.
Click to expand...
Click to collapse
Got down-to 4mA or even 2mA in plane mode... using magldr with HD2 Android 2.2.1, tried many other builds always got such figures, with a few pikes with varying frequencies depending on builds.
I'm using Battery Monitor Widget which consumes less battery and allows more precise investigation, this tool is recommended by Motorola support group!
ccounotte said:
Got down-to 4mA or even 2mA in plane mode... using magldr with HD2 Android 2.2.1, tried many other builds always got such figures, with a few pikes with varying frequencies depending on builds.
Click to expand...
Click to collapse
Just set up my buddy's HD2 phone with that yesterday
... >_> but how did you wander into the CDMA Hero sub-forum
Wandering for good widgets
kyouko said:
Just set up my buddy's HD2 phone with that yesterday
... >_> but how did you wander into the CDMA Hero sub-forum
Click to expand...
Click to collapse
Searching for battery monitoring widgets... and now using also Process Monitor Widget to get a recording of activities. hopefully will get a link between the 2 apps working soon
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Profondo_Rosso said:
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Click to expand...
Click to collapse
I do the same.. just 1 screen off profile to underclock it to 216/216 when the screen is off
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
Android does regulate the cpu, but I don't think it will take advantage of more conservative governor modes unless you tell it to. That's only relevant if the kernel supports more conservative governor modes. And, as the other responses have pointed out, you can force Android to be more conservative by capping the max clock speed.
Hmm... Guess its worth a shot. Good lookin out guys.
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
charlieb620 said:
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
Click to expand...
Click to collapse
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
regP said:
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
Click to expand...
Click to collapse
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
jayohwhy said:
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
Click to expand...
Click to collapse
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
rhinology said:
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
Click to expand...
Click to collapse
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
jayohwhy said:
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
Click to expand...
Click to collapse
Once we get some custom kernels, we should be able to change the governors in setCPU, dependent upon on what the kernel supports.
SetCPU Custom Frequencies for G2X
I got SetCPU today and was playing around with it and it looked like it was limiting my CPU all the time due to lack of profile, not just when I had the screen off per my profile so I looked into making a text file for custom frequencies and am posting it here since there doesn't seem to be any help for g2x with it.
This is a really simple file, tell me if you guys have any better ideas, I just put in:
216000,528000,712400,1000000
I'm attaching it. I put the file in my dropbox, grabbed it via the app and then moved it to /sdcard/setcpu.txt via astro file manager then loaded custom profile from within setcpu. Hopefully this saves someone some time or you can tell me if I'm going about this the wrong way
I'm sure it could be fine tuned more but I was getting irritated at how much of a pain it was to unlock the phone with it set too low, so for screen off I have it set to 216->528. You could add 254000 in or something. The phone seems to be as usable as before now with setcpu enabled like this while it should be limiting the cpu when the screen is off. It sucked (well not the battery) without a custom profile.
socalTNT said:
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
Click to expand...
Click to collapse
rooted?????? what is that?
TheMightiest1981 said:
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
Click to expand...
Click to collapse
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Profondo_Rosso said:
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Click to expand...
Click to collapse
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
charlieb620 said:
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Actually, your assumption is wrong, as is often the case.
I'd quantify it more as normal use. Lots of texts, some games of Pro pool, a few phone calls, checking Pulse 3-4 times during the day for 10 minutes at a time, some mild web browsing and watching a few youtube videos.
I ended up at around 18-19 hours of of use.
Today, I'm off the charger for 8 hours, and I still have 45% left, and I would say that's with some moderate to heavy use.
regP said:
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
Click to expand...
Click to collapse
Try upping it to 216/312 or a tad higher and you should be fine.
Hey guys, i 've been using setcpu for a while and the widget too. Usually, my phone's temperature is 30-35 C. My question is how much heat can this phone take? What us the optimal temperature? What is the Max temperature you have ever seen?
Sent from my HTC Desire S using XDA App
well desire s and desire hd got same cpu, and my dhd went unstable when it hit more than 55°C so i would use at least a temp > 50°C profile with taking speed down
Blezz said:
well desire s and desire hd got same cpu, and my dhd went unstable when it hit more than 55°C so i would use at least a temp > 50°C profile with taking speed down
Click to expand...
Click to collapse
I'm more cautious and limit the CPU to normal (stock) running speeds parameters when it hits 40°C and then lower the max further if it ever reaches 45°C.
I thought with the newest update of LBC's ROM you shouldn't be using SetCPU as it disables the new virtuous overclocking daemon? I'm running the Virtuous Unity ROM on my DS. IMHO, the battery life is great compared to Coredroid v1.2 with SetCPU. Not sure if it has any settings for temperature like SetCPU though..
tankos said:
I thought with the newest update of LBC's ROM you shouldn't be using SetCPU as it disables the new virtuous overclocking daemon? I'm running the Virtuous Unity ROM on my DS. IMHO, the battery life is great compared to Coredroid v1.2 with SetCPU. Not sure if it has any settings for temperature like SetCPU though..
Click to expand...
Click to collapse
You are quite correct, I only upgraded to the latest version of LBC v0.5.2 earlier this afternoon and as the install instructions recommended promptly un-installed setCPU.
Too early to tell anything...............
Hoping that next version of the virtuous O/C Daemon will incorporate temp and battery profile switching.
They're talking of using a GUI in the future for this feature, fingers crossed it'll have the extra settings! Once you've run LBC for a couple of days any chance you could post how you're battery life is getting on?
tankos said:
They're talking of using a GUI in the future for this feature, fingers crossed it'll have the extra settings! Once you've run LBC for a couple of days any chance you could post how you're battery life is getting on?
Click to expand...
Click to collapse
Yep, I read that and I'm hoping that they incorporate criteria like setCPU does, the phone is certainly more responsive from lock screen which is a great improvement.
I'll happily report back, but, it usually totally depends on how much use I give the phone during the day which varies massively, I also have a mugen high capacity battery 1800mAh high capacity battery.
If I don't touch the phone, it will loose just 10-20% over the day, even less if I'm at home and only have wifi on, where as other days I stream radio for an hour and use the internet XDA a lot and it looses 50-60% over the day.
I also use the great application tasker to automate the switching of my radios and don't have auto sync enabled. I simply sync first thing in the morning, at lunch and in the late afternoon.
If I notice any significant change from v0.5.1 I'll re-post.
original RUU_Saga_FET_TW_1.31.950.2_R_Radio_20.28b.30.0805U_38.03.02.14_M_release_180347_signed
and the highest temperature is 48.6°C
Hi, first to defend myself, I did search and found that everybody says good things for every kernel. So every kernel is best for Stock ICS?
I got confused. Yes I'am total noob and recently learned how to root and flash custom rom's.
I just want to hear your opinion for best kernel running on Stock ICS.
I need kernel that is good for the battery but also snappy for the system. I don't play games and I use my phone for calls, reading news, working on excel files, google maps, mail and taking pictures.
My phone is Nexus S GT-I9020T on Wind network.
IMO ezekeel kernels
Has lats of featured including voodoo color
http://forum.xda-developers.com/showthread.php?p=20520270
Sent from my Nexus S using xda premium
Thank you. Is this kernel stable?
Im just trying to set it up as we speak, will let you know how stable it appears once I figure it out
Stuck on trying to flash an unsecure boot image at the moment.
*shrugs* The stock kernel?
Unless you want the functions third party kernels bring to the table, I don't see a good enough reason to swap the stock kernel for another.
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Just managed to get ezekeels CFS on there and I get the reboot bug after going to standby.
Looking for updates but the thread is huge. Yet to try BFS.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Click to expand...
Click to collapse
You can try and turn off deep idle for your reboots.
Solves the problem 99% of the time (totally made up stat that could actually be true)
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
darko.baruh said:
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Deep idle gives more battery time under certain conditions (screen off but not completely idle, playing music for instance). It won't really give you more battery time if your phone is actually idle with the screen off.
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel.
Click to expand...
Click to collapse
Same here but not bad at least for me just one reboot since i installed yesterday when he posted. 2.1 kernel I never got any reboots
Sent from my Nexus S using xda premium
darko.baruh said:
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
Click to expand...
Click to collapse
The first post that you linked actually just confirms what I said.
Ezekeel said:
Since this is just theory and Morfic noted that his experience seems to indicate otherwise and that limiting the CPU frequency does actually decrease the battery drain, I put this theory to the test and logged the battery charge over 10h of FLAC playback in Airplane mode with the screen switched off.
Click to expand...
Click to collapse
1) Playing FLAC (not idle)
2) Screen off
Pre-requisites are met.
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
darko.baruh said:
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
Click to expand...
Click to collapse
Deep idle only shows savings if there is tasks running while the screen is off VS the same situation without deep idle.
So for someone doing commuting (like simms22 for example) and listening to music for around an hour, they'll lose less battery with deep idle than without.
You won't actually save battery if your phone is actually idle with deep idle enabled.
It's not some kind of magical function that makes your phone use less battery doing tasks with the screen on, deep idle disables certain components of the phone while executing tasks with the screen off, instead of having it "at full speed" as if the screen was on.
Now I understood. Thank you very much.
darko.baruh said:
Now I understood. Thank you very much.
Click to expand...
Click to collapse
No problem. I think Deep Idle is probably the mod by Ezekeel surrounded by the most misconceptions.
Most new users want it absolutely but don't seem to know why.
On His Glados kernel I noticed that Android OS was using 20%-21% of the battery and on the stock kernel 30%-31%.
Android System was using around 14% and on the stock around 19%.
Ok, have you decided to give the Glados 2.2 another go? I believe I have finally tweaked it so that it is stable for me.
Before I was getting restarts within 30 seconds of the screen turning off. I have cornered this (on my phone at least) to a problem with NSTools auto-setting the lower frequency to 100mhz. Changing it back to 200mhz and I have yet to see the system restart itself. Im not overclocked, because I dont see the point as everything is fairly snappy with this new kernel. I dont really play games on it so Im not fussed.
I did used NSTools and the frequency was set to 200mhz and I had system restarting on screen off. Using stock ICS with Glados 2.2
Also I had green annoying flickr on locking and unlocking the screen.
I just got upgraded from CM 9 stable to CM 10 stable and I love it. Only problem is battery life. I feel about a 10-15% reduction with the new upgrade. I've had CM 10 for about 4 days now. I don't want to touch the performance settings without knowing what I'm doing. Is there a way to change my performance settings to extend the battery life? Also has anybody played with a different kernel with CM 10 stable? Thanks
abehbeh said:
I just got upgraded from CM 9 stable to CM 10 stable and I love it. Only problem is battery life. I feel about a 10-15% reduction with the new upgrade. I've had CM 10 for about 4 days now. I don't want to touch the performance settings without knowing what I'm doing. Is there a way to change my performance settings to extend the battery life? Also has anybody played with a different kernel with CM 10 stable? Thanks
Click to expand...
Click to collapse
Don't worry about changing the cpu and governor settings. There is an option to set at boot. Make sure that is disabled, so if you have any problems a reboot will go back to default settings. I use the conservative governor, and have my minimum cpu speed set to 192. I've read that that speed is not entirely stable for many people, but seems to be working fine for me. That has been pretty good for battery life for me. I believe the default governor is interactive now, and the minimum cpu speed is set to 384 by default.
Do you just "feel" a battery difference, or do you have any actual numbers to back up that assertion? Keep a close eye on Settings / Battery and use Better Battery Stats to record solid numbers and identify what's actually eating your battery.
Also turn off google now location settings if ur not using it. They are really hard on the battery.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Disable Google now and battery should be back to normal here is some pics. Cm10 default kernel,stock clocks, no UV, on demand governed, and deadline as scheduler
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Thanks for the replies.
It seems to be my screen that is responsible for eating up my battery. Have had the phone disconnected from the charger for 4 hours now and all I've done is 20 min with screen time doing a little bit of texting and facebook and my charge is at 75. I have the automatic brightness setting off and put my setting at pretty low.
The cell stand-by battery usage is 8% during these 4 hours. Should I maybe try another radio or is this normal? It lost signal for about 10 min today.
Just turned off google now and selected the conservative governor. Let's see if this makes a difference.
I used to be able to go all day with my phone with CM 9 and I even have the nexus battery.
Thank you for all your help
That's most definitely not normal, at least in my experience. Are you using the vanilla CM10 or some variant?
Some things to try:
Install Better Battery Stats (find the free version on XDA via a search) to see if any apps are causing wakelocks. This is a must.
Use CPU Spy or something similar to see if your phone is entering Deep Sleep. This is a must.
Turn off Google Now unless you actually use it
Turn off all unnecessary radios (WiFi, Bluetooth, GPS) unless you're actually using them
Turn off all auto-refresh settings in every app you have -- all social apps and weather are the biggies
For me, turning off the default auto-refresh in Facebook, Google+ and Twitter are massive savings alone, then Settings / Battery & BBS will help you locate the remainder of the headaches quite easily.
You might want to consider swapping kernels too, or at the very least reconsider your CPU governor and scheduler settings.
I would stay away from conservative governor you won't get much performance out of that, stick with what comes stock and use on demand.... even the default interactive sucks my battery down
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
abehbeh said:
Thanks for the replies.
It seems to be my screen that is responsible for eating up my battery. Have had the phone disconnected from the charger for 4 hours now and all I've done is 20 min with screen time doing a little bit of texting and facebook and my charge is at 75. I have the automatic brightness setting off and put my setting at pretty low.
The cell stand-by battery usage is 8% during these 4 hours. Should I maybe try another radio or is this normal? It lost signal for about 10 min today.
Just turned off google now and selected the conservative governor. Let's see if this makes a difference.
I used to be able to go all day with my phone with CM 9 and I even have the nexus battery.
Thank you for all your help
Click to expand...
Click to collapse
Don't use conservative, your phone is gonna be very slow and suck
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I'm currently running the vanilla CM10
Turned off google now location access and set the govern to on demand early this morning and it is performing a little better most def.
I have noticed that my phone lost signal 4 times during the day for periods varying 5-10 min. I am currently on the I727UCLF6 radio. I'm thinking maybe I should try another one. Could that help with that battery maybe?
I have been thinking about switching kernels but I am a little doubtful because I don't want to mess up my phone too much since I so heavily depend on it. I loved the hotcakez kernel that came with AOCP, maybe i'll give it a shot this weekend.
Thanks for all the help people! Def the best forum by far on the web.
abehbeh said:
I'm currently running the vanilla CM10
Turned off google now location access and set the govern to on demand early this morning and it is performing a little better most def.
I have noticed that my phone lost signal 4 times during the day for periods varying 5-10 min. I am currently on the I727UCLF6 radio. I'm thinking maybe I should try another one. Could that help with that battery maybe?
I have been thinking about switching kernels but I am a little doubtful because I don't want to mess up my phone too much since I so heavily depend on it. I loved the hotcakez kernel that came with AOCP, maybe i'll give it a shot this weekend.
Thanks for all the help people! Def the best forum by far on the web.
Click to expand...
Click to collapse
Just do a nandroid backup of the entire phone first before installing a new kernel and your risk drops to zero. If you install it and it all goes to hell, just boot back into recovery and restore your backup.
As for radio ... if you drop signal that often and your phone is constantly searching for one, I suppose that could impact the battery, sure. Are you certain you're in an area with solid coverage, though?
Learn more about the different governors and schedulers: http://forum.xda-developers.com/showthread.php?t=1950084
Yea I might have to play around with some kernels this weekend. Luckily it is a long weekend so I'll have some time if I mess up
My phone will go from 4 bars and a good signal at -78 dBM in my apartment and then randomly I'll lose signal for abut 5-10 minutes. A restart usually does the trick or I can just wait until it regains the signal which can be frustrating. I never had any problems with my signal at home running CM 10 so that leads me to think that there might be some problems with the radio.
Just want to confirm that these are the 5 radios I can use for AT&T even though I'm running JB.
http://forum.xda-developers.com/showthread.php?t=1754473
I've been using a UCLI3 modem I found on XDA a couple of weeks ago, it has been incredibly stable and strong for me. But as many people far wiser than me have said elsewhere, everyone's mileage with radios varies and it really just takes some testing to see what works best for you.
so I should be able to run the 5 ICS radios I found eventho im running jb right?
thanks for your help
abehbeh said:
so I should be able to run the 5 ICS radios I found eventho im running jb right?
thanks for your help
Click to expand...
Click to collapse
Yeah if they are for the skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2