I know that CM7 is a WIP so i dont expect much..but is everyone having significant battery drains on CM7? My battery is running out within 4-5 hours of normal use, surfing web, texts, google music etc. My display is all the way down. What is draining the battery alot? Right now im on a fresh install of mookOSmtd build1. Other than battery and camcorder everything is extremely smooth on CM7 so far..
I'm working on some tweaks for miui and mokee which both share the cm7 boot.img. Be patient. Some advice for now, turn off background data in accounts and sync settings when you don't need it, as well as data and wifi and auto sync...
Your battery might be on it's way out. That is really bad life. How are other ROMs doing in comparison? I haven't been on CM7 in a week or so but I was getting at least a day out of it.
Same bad battery life here. As it's been been figured out in another thread, it's about modem. Flashing other modem did not help me though. So it's up to developers when it'll be fixed.
Until then, the only workaround I found was to turn off synching, data and wifi. Then I'm getting good battery life.
It's a work in progress ROM, we know what we're getting into. Nevertheless, it's still one of the best ROMs around.
Sent from my SGH-T959V using XDA
Some things I have found with CM7 based ROM (MIUI more specifically)...
So, I have been working on trying to improved battery life for MIUI MTD and have found some things that help.
The modem seems to be the biggest culprate. I had notice that it was switching from 3G to H every couple of seconds. So the first thing I did was flash an older modem (KD1). and that fixed that issue. But, my battery life was still a bit below par. I pulled a logcat and saw that delvik was dumping and refresh quite often. This is where it may be different if you are using any CM7 ROM other than Team Kick Asses MIUI. I edited the governor tweak by turning the up_threshold to 80. Unfortunately I sacrificed a little bit of performance, but the battery life was becoming more desirable. I also took my own advice and performed steps 1 thru 3 of the Gremlin Remover process (link in my signature, just follow the OP. No need to run the 1-Click as it is only meant for worst case scenarios). For me, the Gremlin Remover process yielded the best results (mainly the battery pull and complete power down method). Thru further investigation, I noticed something would connect to data (little up and down arrows next to signal bar) every time I would unlock the screen. It seems that google services is the guilty one in this case. So I turned off automatic sync in accounts & sync settings. Again, a little bit of a boost there as well. You can always sync manually. But then there is background data that is connecting a lot as well. So I turned it off too (a well known trick that has been around... don't forget about turning off wifi when not using it and data). Unfortunately, by turning off background data, certain things like google voice mail and gtalk don't work, so I had to turn it back on. Now, after reviewing the logcat again, dalvik is refreshing and clearing A LOT. So I edited the build.prop by changing heap size to 128 and removed any other entries in the build.prop that dealt with dalvik (for testing purposes ONLY), rebooted to recovery via the button method, cleared cache and dalvik cache, rebooted an let phone sit for a while. Things seem to be running wuite smoothly, and the battery is lasting about 12 hours for me now (which included 4, 1 hour long phone calls, about 5 quick calls, lots of texting, web browsing, and playing a fwe games while I sat and waited a few times). Do not edit the build.prop if you don't know what you are doing. I will post more comprehensive details later as it is getting time for me to head to work.
I completely understand and recognize that CM7 is a WIP, but these are just some suggestions and ideas that I am passing off to you.
also, I haven't looked into the CM build prop, so i don't know the default dm heap size.
It might be low.
FOR PEOPLE TO GET BETTER LIFE::::go to settings-->Cyanogenmod Settings-->Performance-->set DM Heap size to allowable maximum.
airfluip1 said:
also, I haven't looked into the CM build prop, so i don't know the default dm heap size.
It might be low.
FOR PEOPLE TO GET BETTER LIFE::::go to settings-->Cyanogenmod Settings-->Performance-->set DM Heap size to allowable maximum.
Click to expand...
Click to collapse
It's 64mb
thomas.raines said:
It's 64mb
Click to expand...
Click to collapse
That is odd on mokee 48 is the largest available.
ditto on CM, just looked into it.
I thought the default for cm7 was 48? Which is low...
Sent from my SGH-T959V using XDA
Related
DO NOT POST QUESTIONS IN THIS THREAD. If you don't know how to perform certain steps then search for how to's elsewhere or pm me or jump into the irc Channel and ask. The point of this thread is to post fixes you've used for issues in cm7 or while trying to flash cm7 without all the clutter in a general cm7 thread to make it easier to find answers and to keep a little clutter out of the other threads. If you have a solution to a problem pm me and ill put it in this thread credit to you. It can be anything from major issues to small annoyances, if you have a fix ill input it here. If you see an error in something I post go ahead and post it so it can be corrected.
INDEX
THE BASICS
GPS ISSUES
FACEBOOK BIRTHDAYS SYNC
THE BASICS
One thing to keep in mind if you're having a problem is that you should not assume its a problem with the ROM you are running. Some things to check if you're having issues after flashing a new ROM:
1. If you cant get your rom to flash or boot up correctly, check to make sure the md5 sum of the rom you downloaded matches that of the rom posted. If not, you need to download it again.
2. Boot into recovery by shutting the phone off and holding the volume down+power buttons. Sure you can flash a rom no problem by booting into recovery other ways, but if you do it this way you can be sure you that the recovery booted correctly.
3. Make sure your phone is NOT plugged into anything. Doing this is almost guaranteed to cause headaches. This is very easy to overlook, especially when transfering zips from your computer to your sd card via usb.
4.Patience...After flashing a new rom, especially if you wiped dalvik and/or have a lot of apps can take some time.
5. Before you panic, reboot. If something isnt working it could just be that you need to reboot your phone. [credit to cHarley04 for suggesting this for connection issues via USB cable]
6. If all that checked out and you're still having problems, and you havent already, wipe the cache and wipe the dalvik cache and reflash the rom. And to take it a step further you can do a full data wipe/reset. I generally recommend wiping cache/dalvik cache, but would say that a full data wipe isnt neccessary unless you run into a problem or the developer tells you to do it before flashing a new/different version.
7. Boot issues after flashing Gapps? If you checked all the above then go back and make sure you downloaded the correct Gapps for this ROM.
8. Im saving this one for last so I can put it in a nice big bold text: READ READ READ A quarter of the posts in the CM7 threads are people asking the same questions over and over again that have already been answered. Another chunk is people answering those questions over and over again (nothing wrong with helping others). Its that kind of clutter that makes those threads so hard to read through to get the information you want. Im not saying dont ask questions, but atleast make an effort to read through the threads to try and see if you can find if the question has already been asked/answered. It gets to a point where a thread has thousands of posts and a newcomer sees that and says to themselves that theres no way they're going to read through all that to find the answer to a minor annoyance issue. And I can almost say I dont blame them. But at the same time, if the problem isnt a big enough deal that you dont want to put in a little work to try to find the answer then it cant be that big of an issue...fair enough? Every time a question gets re-asked it just buries some other piece of information even deeper into those thousands of posts. Ok...enough ranting
My GPS doesn't work (at all)
1. Make a nandroid backup of your current cm7 setup.
2. Download and flash cm6 and the proper gapps.
3. Boot up the phone and get a GPS lock using maps or GPS test.
4. Shut phone off.
5. Boot into recovery.
6. Restore the cm7 backup you made.
Your GPS should now work. Install the GPS test app from the market and run it. You should see your GPS icon flashing in your notification bar. If it is then you just have to wait for a lock. This may or may not take some time. If your icon does not show up at all then you can either try the process again or seek another fix.
Sync Facebook Events/Birthdays to Google Calendar
FROM YOUR INTERNET BROWSER:
1. Install the fdCal app for Facebook by clicking on the Google Calendar Icon under 'Subscribe to your friends' Birthday'.
2. Now in your Google Calendar you will see 'fdCal' under 'Other Calendars', Click it and your Facebook birthdays will appear on your calendar on this page.
FROM YOUR PHONE:
3. Now on your phone, go to the calendar app and click 'Settings>More>Calendars. From there ensure that fdCal Birthdays is 'synced, visible' and press 'ok'. (if you dont have auto sync on you will need to go into 'Settings>Accounts & Sync>Google>Google Calendar 'click to sync')
Your facebook birthdays are now synced to your google calendar! No extra apps needed. The link above also has the option to sync your Facebook Events as well.
EDIT: if you were using an app to sync birthdays (such as ebobirthday) than you will want to do the following:
XRange said:
Menu -> Settings -> Applications -> Manage applications -> All -> Calendar Storage -> Clear data
Then i synced my phone again with Google, and everything was OK - and synced!
Click to expand...
Click to collapse
Sent from my Liberty using Tapatalk
...Update...
EboBirthday, Delete from Google Calendar to use FdCal from Above
Menu -> Settings -> Applications -> Manage applications -> All -> Calendar Storage -> Clear data
Then i synced my phone again with Google, and everything was OK - and synced!
How about the battery fix?
Fully charge battery
Clockwork, delete battery stats.
Drain battery until the phone shuts of auto.
Then fully charge it....
Sent from my Liberty using Tapatalk
ValkyrieLiberty said:
How about the battery fix?
Fully charge battery
Clockwork, delete battery stats.
Drain battery until the phone shuts of auto.
Then fully charge it....
Sent from my Liberty using Tapatalk
Click to expand...
Click to collapse
While this will definitely calibrate the battery meter and is the way you'll usually find in forums for calibrating, I dont personally completely agree with it. Im strongly against letting these li-ion batteries fully drain. It degrades the cells of the battery. Charging the battery causes deposits to form inside the cells that take up space inside the cells. This is what causes these batteries to last for shorter periods of time in between chargings until eventually they just wont hold a charge anymore. The lower you let the battery get before charging the more you excellerate the process. I try not to let my battery below 40% and generally only charge it to 100% before going to work. I try to keep it between 40-80% most of the time with bump charging here and there.
The battery meter will calibrate itself over time with regular use. Sure it takes a bit longer. This is usually the strange battery drain people see when first trying a new rom (along with all the playing around they do checking out all the features) that eventually levels out. Often referred to as the ROM "setting in". To keep things level, I try to fully charge my phone before flashing a new rom. Does it make a difference? I dont know, but my battery drainage has remained steady across every nightly Ive flashed.
So again, Im not saying you're wrong in the battery calibration. Because you're absolutely correct that that will calibrate the battery. I just dont subscribe to doing it that way and believe in just letting the phone do its thing. But thats just my opinion.
CallMeAria said:
While this will definitely calibrate the battery meter and is the way you'll usually find in forums for calibrating, I dont personally completely agree with it. Im strongly against letting these li-ion batteries fully drain. It degrades the cells of the battery. Charging the battery causes deposits to form inside the cells that take up space inside the cells. This is what causes these batteries to last for shorter periods of time in between chargings until eventually they just wont hold a charge anymore. The lower you let the battery get before charging the more you excellerate the process. I try not to let my battery below 40% and generally only charge it to 100% before going to work. I try to keep it between 40-80% most of the time with bump charging here and there.
The battery meter will calibrate itself over time with regular use. Sure it takes a bit longer. This is usually the strange battery drain people see when first trying a new rom (along with all the playing around they do checking out all the features) that eventually levels out. Often referred to as the ROM "setting in". To keep things level, I try to fully charge my phone before flashing a new rom. Does it make a difference? I dont know, but my battery drainage has remained steady across every nightly Ive flashed.
So again, Im not saying you're wrong in the battery calibration. Because you're absolutely correct that that will calibrate the battery. I just dont subscribe to doing it that way and believe in just letting the phone do its thing. But thats just my opinion.
Click to expand...
Click to collapse
That makes pure and COMPLETE sense. Thanks for teaching me that! All the scientific evidence is lying there! I always wondered why i ate through batteries like a kid through candy!
Hi everybody!
So I am using CyanogenMod 7 Beta5.1 And I'm having huge battery problems...
It's draining abnormally fast (30% lost during night).
It started to happen when I got problems with my Defy and flashed 3.4.3-11
And now updated to 3.4.2-117.
Before these problems it usually drains only 3% during night!!
Also everytime I boot my phone, when it's completely booted I hear the camera sound (when you open camera app,it makes a physical sound).. It never happened before...
I overclocked my phone to 1100Mhz but I don't think it really affects the battery (when screen off it's set to 500Mhz)
Please help me!....
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
fast boot? The one from setvsel?
schultzy001 said:
I was having that problem and I turned fast boot off and it solved the problem for me. The phone doesn't really shut down all the way if fast boot is on.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
how can u shutdown fastboot? wanna give this a try...
schultzy001 wrote
"Sent from my Desire HD"
um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.
Hi guys,
I'm having this issue too, and i note since a few days ago. I don't know why, but my Defy is sucking his battery too fast. Could it be a bug ?
it's a little bit difficult to follow the bugs and the solutions in a huge thread like the other one. so i think that this that could be a mayor problem for all of us should be treated in a differente thread.
I use Motocharge since 1 day to follow how it discharge during the day.
I say it in the other thread, the phone loose a lot of battery when i don't touch it. sometimes it loose like 5% in 15mins and i don't touch it. maybe it doesnt sleep well, i don't know..
I hope that Quarx can solve this, because in the other betas of him i don't have the problem. only in the 5.1.
battery draining
I think It´s a bug, because I used before BETA 5.0 and without any battery life was almost 3 days in normal use, bur now with BETA 5.1 only two days or less.
By the way I´d proved with 3 or 4 diferent roms, but the same result.
But I´m sure Quarx will deleted this bug in the next version
same problem for me,but b3 and b4 is ok
Sent from my MB525
apart from low battery life.....i noticed substantial increase in battery temp..normally its 32-34 deg cel.....but wid CM7 it raises to 42-45 deg cel.....waiting for a solution so that i can come back to CM7...
I use Toggle 2G/3G to switch to 2G when phone goes to sleep. I set wifi to never sleep and use it as much as possible over 3G. I also set brightness levels long time on 16 so that in the shadow I always use just a little energy. This way I almost get double battery live.
+ it's better for battery to charge every night, empty or not, and let it go lower just occasionally.
Link to Toggle app:
http://forum.xda-developers.com/showthread.php?t=739530
yes, this issue is really annoying, 30% battery drain overnight.
something is definitely running unreasonably... hope find it.
I think it depends upon what "type" of defy u have. My battery that only used to last for 12-14 hours in eclair now went for 2 days last 2 charges.
Also depends upon how many widgets and apps u running... hard with mobile phones to judge battery as so many independent variables.
Sent from my MB525 using XDA App
OK Guys, this is an old thread, but I think it should be deleted or at least people should read this before registering this thread in their mind:
The battery drain 'issues' were almost always due to two things:
1- For the beta 6 version or older of CM7- there was a bug with the auto-brightness which was heavily stressing the cpu and making the system lag badly - hence: the battery drain. To fix this: you have to stay on auto-brigthness. So just make sure that the auto-brightness box is checked and ON. Additional info: some users also complained about the 4 action buttons (menu, home, back and search) not lighting up ---> fix: un-check auto-brightness and re-select it: done!
2- Users did not set their Network baseband properly. Fix: use the Defy Baseband Switcher application and select the newtwork that applies to you. If you don't do this, your phone might have signal reception (phone and sms) but it will use more power to communicate and get a proper lock to your phone service provider.
I don't know what is the exact build # that brought the Defy Baseband Switcher (as far as I can remember, CM7 beta 4.1 had it) but all the 'newest' CM7 will have it anyway.
And if you want to further decrease your battery consumption, you can still do it like this:
- use the bootloader cpu settings: OC'ing and governernor type to change the cpu speed. [From CM7 default 1000MHz to the Defy's stock 800MHz] and change the governor type from "interactice" default to "on demand" [OK: I'm not sure about governor change will improve or not but that is the Froyo's default I believe].
- install SetVsel to underclock --> by lowering cpu Vsel upon the 3 cpu frequencies. Do some reading; you might need to uncheck its "[email protected]" option AND also have Milestone Overclock installed for it to work properly.
- USE a recent nightly (post May 29th: there was a possible problem with custom recovery backup restoring prior to that) and you will be able to set your screen display brightness as low as you want [fix the bug described in point 1- above].
- use DroidWall and/or the CM7 built-in applications' permissions control to block some apps' access to internet and networks. BE WARNED though: changing permissions CAN make an application stop working or create problems - don't submit bug reports if you do that.
- Avoid high usage of apps that drain battery quickly (TuneIn radio is power-thirsty one that comes to my mind...) and apps that have to create catalogs and thumbnails (ex: Photoshop, Titanium Backup, Gallery, ...)
- If possible: use 2G network only, disable data synch, auto updates of apps and social networks.
- set your WiFi sleep policy to "Never" [while in Wi-Fi settings, press menu button/ Advanced] and avoid frequent Wi-Fi ON/OFF switching.
- Lower your display brightness and switch that screen off at any chance you got!
There are many other ways I'm sure, but those are the main ones anyway...
I've seen high temps yesterday on my Defy, but I later realized that I forgot to re-set my Baseband after a CM7 nightly install... It 'could' also happen when a (background) service goes "beserk" and overload the cpu: absolutely not necessarily related to CM7 --> faulty apps and bugs happen... Just stop and clear the cache of that app and/or reboot your phone and problem should be gone.
CM7 is now really stable; a VERY FEW little hickups remaining still (like with the camera, but negligeable), but the large amount of new user controls that it brings clearly overcomes the 1 or 2 minor bugs left --> IMO, just having control over each and every applications' permissions justifies forgetting about using Eclair and Froyo. Problems in CM7 are being actively sorted out and new user controls and other useful options are added in almost daily manner through the nightly builds.
I'm categoric: on CM7, I now have more control over where my battery juice goes that I've ever had on Froyo....
So please stop alarming people with high battery usage drainage on CM7 and give it a try by following the right proper steps; I'm sure that you won't regret it.
marhensa said:
um... a new thread? really?
by the way, i have this problem too since beta 1.. i don't know why..
but i still like it because CM7 is so fast without OC.
i try to compare froyo and CM7, with same apps and same apps settings,
CM7 lost the battery faster than froyo, even when in flight mode.
the strange one is, even the memory usage is so low on CM7 (no motoblur crap),
but why battery still drains so fast..
in battery usage statistics,
on CM7, it shows that "Display" is the one who responsible drinking so much juice (60% and the other is just 3-10%).
on froyo, is not the "Display" which responsible drinking most of the juice, it is "Cell Standby".
i thought gingerbread should have good battery management, and the battery should last much longer than froyo.
i'm sure it is a bug on CM7 for Defy.
but whatever, at least we have a Gingerbread on Defy from a great dev like Quarx.
while motorola working so slow on releasing froyo with its motoblur crap.
Click to expand...
Click to collapse
Display instead of cell standby showing up first in battery consumption means that Froyo (or CM7) uses less battery. The display just stayed the same of course, unless it's tuned brighter, the percentage increased because it's a relative measurement.
I installed @dwitherell's TweakStock 1.4 on my Charge about 5 weeks ago, and I've mostly been happy with it. The one problem I kept running into was deteriorating performance over time, leading to frequent hard lockups requiring hard reboots. I'd gotten to the point where I needed to reboot the phone nearly every day. Having multiple active apps also tended to cause problems, for example Cardiotrainer + Rhapsody music.
Sometimes when the lag hit I was able to get a CPU usage report before the phone fully locked up. At such times I'd see kswapd0 eating a large portion of CPU. That suggested memory problems. I tried tweaking my OOM kill thresholds, to no avail.
This morning, based on some research, I took a look through my build.prop and noticed that this ROM's default VM heap size is a whopping 72MB. That sounded very high, compared to my previous phones where it was 24-32MB. I installed the VM Heap tool, knocked the heap size down to 48MB, and rebooted. My phone has been running as smooth as silk since, even with multiple simultaneously active apps running.
I'll keep watching to see how this holds up over time, but the difference even over a few hours is noticeable enough that I thought I'd report my findings right away. Regrettably, XDA discriminates against new members, so I can't post into the TweakStock developer thread as I would prefer. HTH!
thanks for the tip... just installed Eclipse, at its VM is 48MB.
tweakstock was running great for me though, so real problems like you said. my only problem (minor) was my Scrabble app being such a battery and data hog...
Thanks for the tip -- I had noticed this too, will give it a try. Though I'm on a different version of TweakStock I noticed the heap size is 72 here as well. Trying 48 for a while... will chime in if there's improvement.
- A
It is likely set high because it was found that increasing the VM heap size helped curb hot boots on heavily modified ROMs.
Interesting, thanks for the history @imnuts! I did encounter the hot boot issues some months back on earlier iterations of Gingerbread ROMs for the Charge. I will keep an eye out for hot boots to see if my 48Mb VM heap size is too low, or swap lag if it is still too high. Perhaps we will all have to try to find the best heap size for our usage patterns, as there may be no best one-size-fits-all setting.
Can't remember where, but I think I once read something that said 40 MB is the absolute best size to go with for a variety of reasons. For what that's worth...
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
jco23 said:
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
Click to expand...
Click to collapse
Just set the value in the build.prop.
jco23 said:
Back on tweak stock.... can I just edit the build.prop or do I have to download VM heap?
Thanks!
tappin' that....
Click to expand...
Click to collapse
Only change back only when you have issue. I currently using 72m since day one and it's working fine, super fast launching apps.
Fwiw stock settings are 64
Was so thrilled to see this recommendation, as I observed that my phone is really struggling to memory, and then kswapd0 kicks in. Tried to change it to 48MB, then to 64MB. Did not see any improvements. It looks like all apps get pre-loaded into memory, and once free memory hits less than ~80MB, the phone becomes sluggish. Once I kill all apps, the phone is back to normal snappy lag-free operation. Free memory at that point is around 135MB. This is even worse when I insert the phone into car dock. Re-draw takes about 5-7 seconds, swiping is about 2-3 seconds. In few moments it becomes ok, but still laggy.
No problems here
Been on TS1.4 w/ PBJ for about a month now, everything is still as snappy as day one. Thought I was having issues at one point but it turned out it was actually an app, Stitcher Radio, that was eating CPU and draining battery (even though I never launched it). I've over/under clocked with SetCPU at various times but never messed with the voltages.
Nonetheless, thanks to OP for this little tidbit, I'll remember it if I ever start experiencing problems.
ddavv said:
Was so thrilled to see this recommendation, as I observed that my phone is really struggling to memory, and then kswapd0 kicks in. Tried to change it to 48MB, then to 64MB. Did not see any improvements. It looks like all apps get pre-loaded into memory, and once free memory hits less than ~80MB, the phone becomes sluggish. Once I kill all apps, the phone is back to normal snappy lag-free operation. Free memory at that point is around 135MB. This is even worse when I insert the phone into car dock. Re-draw takes about 5-7 seconds, swiping is about 2-3 seconds. In few moments it becomes ok, but still laggy.
Click to expand...
Click to collapse
ddavv, sorry it didn't work for you. Some of the other things I've done to my Charge to help with the lag:
Changed io scheduler to bfq (from sio)
Tweaked my memory manager kill thresholds to 6,8,20,28,32,40 (WIP, YMMV!)
Removed some apps that kept heavy services in memory all the time, e.g. Accuweather & Lookout Security, and streaming media services I didn't use much (Last.fm, Slacker)
Turned off Google location services to stop the k3g_wq CPU runaway bug (this may be fixed in Google Maps > 6.4.0)
Switched to ADW.Launcher
Trimmed widgets I wasn't using frequently (down from 20 to 15)
I still do get a bit of lag after the phone has run for a while, so daily reboots are still a good idea for me - but I'm slowly improving my situation. I'm probably going to take a few hours to do a full wipe & reload once the FP1 ROMs start dropping, and be much more careful about indiscriminate app restoring from Titanium Backup this time. Good luck!
Hello,
I've been flashing a bunch of AOSP roms and with all of them, i tend to get terrible battery life while idling. I've narrowed it down to my phone not sleeping while the screen is off. In the battery chart menu awake seems to be almost the same as the battery up time and the bar graph is almost a full solid blue. while i was searching i came across a post in cm forums blaming this on something to do with the gps and that disabling it and rebooting would fix it but this does not seem to work for me. Does anyone else have this and has anyone found a way to fix it?
I've also discovered a post whereby someone was running advanced task killer on an sgs2 to fix the same issue i'm having but i would rather not rely on a task killer if i don't need to. Any info, ideas, help, links etc are greatly appreciated!!
Your friendly neighbourhood Spiderman.
So, to narrow things down, I started off fresh
- Flashed stock 1.11 hboot from Telus RUU
- relocked then RUU
- unlocked, flashed TWRP 2.4.4
- Wiped SD, Cache, Dalvik, System, Factory Reset
- Flashed PA 2.54/Gapps (my fave ROM)
- Installed few apps. Friendcaster, Tunein Radio and Swiftkey
- Left it at 60% over night not charging
Low and behold, Awake time and screen on time were almost on par. However, I used it on the bus to listen to some tune in radio, browse the web etc and it seems as though one of the apps or maybe multiple are keeping the phone awake more than it has to be and it started draining again. not as bad as before, mind you. Most likely due to there being less apps. So at this point if I want to continue using AOSP ROMS it seems as though I will need to set up a task killer so nothing keeps my phone awake.
Tonight I will set it up and see what happens with my awake/screen on bars. I am fairly certain they will sync up afterwards. I tried to avoid a Task Killer but it seems as though I cannot! I will post my findings after for anyone else in this same boat though it seems very few are!
Get a program like better battery stats or Gsam battery monitor to tell you what your wake locks are
Sent from my VENOMized HoxL
Hey everyone!
I flashed CM 10.1 yesterday (cm_p500-userdebug-cm-10.1 from jenkins. androidarmv6.org/job/android/ and I'm amazed how smooth and perfect it is working (A huge 'Thank you!!' to the developer )
The problem is that my battery drain is awful. It took less than 8 hours today to completely discharge, though I hardly touched it.
I used Battery Calibration and also installed "WakeLock Detektor" to see where the problem is, and it stated that my phone isn't asleep 99% of the time though the display is turned off most of the time :crying:
The main reason is a kernel-related thing named "suspend_backoff" that keeps it awake.
I wanted to install a different kernel, but I got no clue which one... I actually planned on installing the recent DorimanX-Kernel, but then recognized that this is only available for the Galaxy SII
Can anyone recommend a Kernel that keeps my system running smooth but the battery drain at a minimum? I basically need my phone for Messaging (SMS, WhatsApp, E-Mail), Calendar and once in a while as navigation system. So no need for spectacular game performances or so.
Are there other Ways to improve my battery life on that phone (I've read all the general tips for improving battery life)? Maybe some OC things I can change manually?
I'm grateful for any help. Thanks!
Helbelinc said:
Hey everyone!
I flashed CM 10.1 yesterday (cm_p500-userdebug-cm-10.1 from jenkins. androidarmv6.org/job/android/ and I'm amazed how smooth and perfect it is working (A huge 'Thank you!!' to the developer )
The problem is that my battery drain is awful. It took less than 8 hours today to completely discharge, though I hardly touched it.
I used Battery Calibration and also installed "WakeLock Detektor" to see where the problem is, and it stated that my phone isn't asleep 99% of the time though the display is turned off most of the time :crying:
The main reason is a kernel-related thing named "suspend_backoff" that keeps it awake.
I wanted to install a different kernel, but I got no clue which one... I actually planned on installing the recent DorimanX-Kernel, but then recognized that this is only available for the Galaxy SII
Can anyone recommend a Kernel that keeps my system running smooth but the battery drain at a minimum? I basically need my phone for Messaging (SMS, WhatsApp, E-Mail), Calendar and once in a while as navigation system. So no need for spectacular game performances or so.
Are there other Ways to improve my battery life on that phone (I've read all the general tips for improving battery life)? Maybe some OC things I can change manually?
I'm grateful for any help. Thanks!
Click to expand...
Click to collapse
I found SweetnSour's version 11 kernel quite good with cm10.1.
However, the ROM needs some help to get good battery life:
Install 2xBatterysaver. It will turn off data and WIFI when the screen is off (turn them on periodically to allow syncing). There are various apps like this one.
Control WIFI. Use Y5 battery saver or Whiz WIFI manager. Y5 is tiny and effective but crashes on cm10.2. Both check for favorite hotspots, leave WIFI on and turn it off when leaving the hotspot.
Thanks for your quick response!
Just tried to flash Sweetnsour's Kernel, but it won't work. I flashed this one --> versionFINAL-CFS.zip
Is that the correct one or rather one of those? -->" version11-CFS-TWRP.zip" or "version11-CFS.zip"
Edit: What actually are CFS respectively TWRP? Searched the forums but couldn't find an answer
[solved] or rather [solvished]
After days of trial and error, cutting and re-enabling all connections from WiFi to 3G and hibernating, un- and re-installing basically all of my apps and trying loads of other roms I didn't love as much as this in the least, I found the source for my phone being awake basically 100% of the time.
The changelog of the mod stated that there's still this WiFi-issue that keeps the phone awake.
Well, though I've tried before, It now works: switching off the WiFi connection finally gets my phone to sleep.
I think I'll just be running on my mobile data for the followin days or weeks until this bug has been fixed.
Btw: A little hint for the developer (I'm posting here, since I'm a noob and can't post in the developers forum): When switching the WiFi options to turn out WiFi whenever screen goes dark, it won't connect afterwards. I always needed to reboot my phone when I wanted WiFi to work again. (This bug also caused my mobile data not to work. It apparently thought WiFi was running, though it couldn't connect.)