I had an old cognition rom (whichever was the last 2.x ROM) and it worked great for weeks. Then after a while, I noticed my battery was dying extremely fast. After some examination, I realized the system process of kswapd0 was running an average of 25% of my CPU and heating up my phone. Worst off I was going through 100% of battery life in 2 hours instead of the normal 24.
Well I flashed 3.01 and it stopped and all was great again. I updated up to 3.03. 3.03 ran great for a week or 2. Now my battery life is starting to go down to about a 5 hour life span and guess what.... kswapd0 is already up to 10% of my total CPU useage, and I predict tomorrow will be already up to the 25% and killing my battery. I plan to flash the phone again with 3.04, but does anyone know why this happens, or if you have similar issues investigate (I use SystemPanel) and confirm this may be an issue with Froyo or maybe the lagfix. Thanks.
After flashing again KSWAPD0 is back down to 1%... wonder why this happens.
ya that definitely is strange.most people who flash usually do not leave a rom on there for more then a week so this problem may not happen to most people. I would recommend posting this in the cognition thread you might be able to get more help there from a dev
Sent from my SAMSUNG-SGH-I897 using XDA App
erickit said:
I had an old cognition rom (whichever was the last 2.x ROM) and it worked great for weeks. Then after a while, I noticed my battery was dying extremely fast. After some examination, I realized the system process of kswapd0 was running an average of 25% of my CPU and heating up my phone. Worst off I was going through 100% of battery life in 2 hours instead of the normal 24.
Well I flashed 3.01 and it stopped and all was great again. I updated up to 3.03. 3.03 ran great for a week or 2. Now my battery life is starting to go down to about a 5 hour life span and guess what.... kswapd0 is already up to 10% of my total CPU useage, and I predict tomorrow will be already up to the 25% and killing my battery. I plan to flash the phone again with 3.04, but does anyone know why this happens, or if you have similar issues investigate (I use SystemPanel) and confirm this may be an issue with Froyo or maybe the lagfix. Thanks.
Click to expand...
Click to collapse
Hey guys,
try this.
1. Go to terminal
2. su
3. busybox sysctl -w vm.dirty_ratio=10
(or 5)
Also set your minfree to something like strict.
Let me know if that works out for you.
EDIT: I am not a kernel hacker so I cannot provide you a correct explanation why this fixes it.
My rough non-kernel-programmer guess is that you are running a lot of apps and background services at the same time. I think this is happening because of the way Linux handles file cache but I am not entirely sure. I am hoping a kernel hacker can give me a correct answer.
Related
i need to get better battery life out of my phone
i will take any suggestions that does better than this, especially if its running cog 4.
thankssss
ps. 1006 build but i dun think that matters too much
There is already a tread about this
Sent from my GT-I9000 using XDA App
vaiol123 said:
There is already a tread about this
Click to expand...
Click to collapse
thank you for your informative response but i believe that peoples experiences may differ and im just looking for someone to chime in and say:
"hi. ive used perc 10.2 but im getting better battery life now that im using..." rom+kernel+modem
hope its not a bad question
maybe my gallery sensor battery usage shouldnt be as high as it is and i should change it with xxx.apk?
thanks
When I went from Percept10 to Cog4, my battery life about doubled. I didn't realize how bad it was until I got to Cog4. Now it is excellent.
Before it would go 7AM to 5PM and be drained.
Yesterday it went 7AM to 7PM and was at 70% when I threw it on the desk dock.
the answer is in your picutes, top right,
advanced task killers, antivirus, ect KILL THE BATTERY
I know I know task killers are supposed to help...
they dont, i was running a task killer and voltage control, had it to under clock with screen off, underclock default, stock speed under certain contitions and overclock when plugged in only. That had the system "running" slower and less power than stock only doing stock speeds when needed, and my battery was DEAD in 8 hours. Removed them and Im going 24 hours between charging. (battery swap).
and i just dont see the point of antivirus.
try removing them and see how your battery does. also the first month of the phone it will be all over the place....
I've run the following setups:
Cog 3.04 w/: Good battery life once I swapped in JK4 modem and Speedmod Kernel, still had random shutdown error, switched to Paragon.
Paragon 5.1: Again, JK4 and speedmod get me the best battery life so I made sure I had this set up. Ok battery life, phone screen would occasionally go black with no response until I removed and re-inserted the battery, switched to Firefly.
Firefly 2.1-2.3: Battery life is great (JK4 and speedmod by default), I usually get through the day with moderate use and 50% remaining. I'd say that's about 50% in 15 hours. It's fast and the GPS is much better than cog or paragon. I'll wait to see what the devs do with Firefly but I'm curious about cog 4 running on the KB1 Froyo. I also use CPU Tuner to eek out the most battery life when it starts running low.
@G35tr
thanks im gonna give it a try
@Trusselo
yeah, i definitely had 10.2 since the beginning (christmas?). i feel like the sensor gallery issue could be a culprit as well the the task manager and lookout programs but the battery stats info just doesnt reflect the latter.
on top of that its a reoriented i9000 kernel so i feel there are some inherent battery performance losses in that.
i got my phone pretty well customized at this point so it may be time to take that step in search of better battery and flash something new.
a farewell homage:
That not all that bad but seriously get rid of the taskiller and antivirus. Been using android for 3 years and never had a need for antivirus. Newer android versions don't need taskillers as they store unused apps in memory without cpu usage.
I am using torch 1.5 and did a full charge overnight and have been using it this morning for 20 mins with wifi and it is still at 100 percent. if you search around or download a few of the roms...there is a modded gallery.apk that fixes that battery drain. And im using whatever the torch 1.5 setup is didnt pay attention to kernel or modem but it is using the new official froyo.
Change modem file or try super power tht extend life of bettry.
Sent from my GT-I9000 using XDA App
kamesen said:
thank you for your informative response but i believe that peoples experiences may differ and im just looking for someone to chime in and say:
"hi. ive used perc 10.2 but im getting better battery life now that im using..." rom+kernel+modem
hope its not a bad question
maybe my gallery sensor battery usage shouldnt be as high as it is and i should change it with xxx.apk?
thanks
Click to expand...
Click to collapse
Why not post in the stickied thread in q&a
Tried nearly every rom here and, in my experience, Cog 3.04 has given me the best battery life by far. Kept default kernel and modem.
My usage is generally as follows:
-2 hours playing music
-10-20 sms
-1-2 hours browsing on mixture of wifi and 3g
Battery drain is generally about 30-40% during the day. Very minimal batter drain when idle.
What did you use to show your battery history? the second screen print.
Thanks.
i get between 25-39 hours of battery life running SuperNova JS5, SpeedMod Kernel K13C, ZNKP1 Modem. I run my phone hard all day long and can't ever seem to get it to die.
when was the last time you cleared the battery stats?
1. Connect the phone to the charger with the phone powered on, and allow the phone to charge until it shows 100%
2. Disconnect the phone from the charger, and power it off.
3. Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the battery indicator shows 100% (you can use vol-up/vol-down to make the indicator come back up when the screen goes to sleep).
3a. Repeat step 1, 2, 3
4. Disconnect the phone from the charger and power it on.
5. Once the phone is powered completely on, power it off again and reconnect it to the charger until the battery indicator shows 100%.
6. Disconnect the phone, power it on, and use it.
7. Use ADB or a Terminal Emulator to run the following command:
Code:
su
rm /data/system/batterystats.bin
7a. Reboot into clock work Recovery, and choose advanced CWM features and select wipe battery stats
do that, then let it die completely before you charge it again.
Glad to see this thread because it has taught me a couple of things. I was one of those people who made the mistake of running Advanced Task Killer. Got rid of that. I also run AVG, but I think I will try to get rid of it and see if it helps me any. I am glad to hear several say that an antivirus is not necessary.
I've used a number of roms and kernels since I got the phone a week ago. I let the phone fully charge while off to get to 100% and then I wiped the battery stats in recovery. Proceeded to fully drain the battery to recalibrate. Left the house the phone at the usual 96%. Drove to work and about an hour later the phone was down to 83%. My wakelocks aren't crazy. Probably about a few seconds total. I think the hottest the phone has been was 35°C. It did freeze the other day while trying to do the calibration process. Don't know if that helps any. The battery doesn't look bad. Phone was second hand. I bought an extra battery which should be here soon. Any ideas? Thanks in advance.
Hi,
what android version are you using?
If you're using ICS, go ahead and try the following combinations:
ROM:
AndroidMe (http://forum.xda-developers.com/showthread.php?t=1421564)
Bugless Beast (http://download.peteralfonso.com/crespo/rom)
Kernel
Eugene's kernel Speedy-3 (http://forum.xda-developers.com/showthread.php?t=1401455)
With this combination I'm getting at least a day battery.
Sorry for the late reply. I'll give this a go. I've been running 2.3 for a while and was actually looking for an ICS rom to try out.
Try disabling auto-rotation in Settings > Display
It is said to be the cause of battery drain in stock ICS.
I am running ARHD 6.5.5 with faux kernel at stock cpu freq. I also have the ICS AOSP aroma theme, with mostly AOSP apps.
You can see from my screen shots that my battery life is terrible, and that is with juice defender on too!
Can someone tell me if theres anything i can change to get better battery, or if there are any ics ROMs out there that will give better battery?
I have wiped battery stats off a full charge but that made no difference. One thing I thought it could be is that I may not have had full battery when flashing the ICS firmware update - but this would have been fixed by battery stats wipe right??
Thanks to anyone who took the time to read this!
Could be a few things....
First thing is to make sure you give it time to get a good battery profile. Let it charge all night, then clear the battery stats in the morning. Then let it go all the way down to 0 and shut off without interruption. (Meaning don't restart it if you can avoid it)
The first day will be pretty bad. The second day should be much better. The 3rd day should be really good.
If you've done that properly and you're still getting 10 hours of battery life, something's wrong.
You could have a wakelock, something that's keeping the phone running all the time even with the screen off. An app could cause this, but it doesn't look like the case based on your screen shot.
The battery could be bad. This can be tested with another ROM to see if the problem replicates itself.
The ROM install could have gone screwy somehow. (Though for the life of me I can't think of how.) But wiping clean and starting over might help.
You can also underclock the CPU. Make it run at like 350 mhz when idling. That'll help a lot.
Skipjacks said:
Could be a few things....
First thing is to make sure you give it time to get a good battery profile. Let it charge all night, then clear the battery stats in the morning. Then let it go all the way down to 0 and shut off without interruption. (Meaning don't restart it if you can avoid it)
The first day will be pretty bad. The second day should be much better. The 3rd day should be really good.
If you've done that properly and you're still getting 10 hours of battery life, something's wrong.
You could have a wakelock, something that's keeping the phone running all the time even with the screen off. An app could cause this, but it doesn't look like the case based on your screen shot.
The battery could be bad. This can be tested with another ROM to see if the problem replicates itself.
The ROM install could have gone screwy somehow. (Though for the life of me I can't think of how.) But wiping clean and starting over might help.
You can also underclock the CPU. Make it run at like 350 mhz when idling. That'll help a lot.
Click to expand...
Click to collapse
Thanks a lot for the reply, you seem to know what your talking about... What about the firmware bit I mentioned, could that have anything to do with it?
I will re-try the battery calibration procedure you suggested - if it does not help what rom do you think I should flash to rule out a bad battery?
Sent from my HTC Sensation XE with Beats Audio using XDA
You didn't mention anything about firmware. But that should be a factor either.
Also, now that I think about it I think ARHD 6.5.5 might have had battery issues. I know one of the 6.5.x versions had poor battery life.
I run 6.5.3 myself and it's super ultra ridiculously battery efficient. I mean like 2 days between charges efficient. And I plug it in at the end of the 2nd day with like 20% left still.
Try starting over with 6.5.3. Or bump up to 6.6.2 that's out now.
I also never had luck with those juice defender things. But that's me. Some people swear by them. I found them to just be in the way.
I have the same issue with battery and I don't understand why the battery is so crap
I'm also using ARHD 6.5.5 with faux kernel. The first two three days were not spectacular but after that stabilized. I first ran it at the faux stock Cpu freq of 1.5 ghz and when I plugged for charging at night was usually at 40-55% depending on use. I'm running it now at 1.2 ghz (is a sensation 4g after all) and is usually 65-85% when I'm back home, depending on use.
I might add that I ran Rom Cleaner 3.5 to slim down the rom and also shnizlon AOSP them with the option of removing HTC apps and widgets
Sent from my Kindle Fire using Tapatalk 2
The problem was ARDH 6.5.5, updated to 6.6.2 and now got awesome battery life! Also re flashed the firmware off a full charge, that could have helped but I'm not sure cos I did it all at once.
Thanks guys
Sent from my HTC Sensation using XDA
***Just want to clarify this is Beans 6 discussed in this initial post***
Hey guys. Been a member for awhile now, but haven't posted much so can't post in Dev section. I've seen quite a bit of discussion in the Beans thread about clock speed and hot phones, so I thought I would create a quick thread to share my experience and observations.
Unfortunately at this time I'm not 100% sure about my initial observations since I didn't know what I was looking for at the time. But the basics are that Beans uses Imoseyon's Lean Kernel and it comes in clocked at 1900Mhz. The tricky bit was that at first on Beans, I was experiencing the behavior that my settings in SetCPU were not being respected. With clock set at 1512 Max it was still spending time at 1900.
So first thing I did was reflash the Kernel from Imoseyon's thread. Realized it was a test/beta kernel at that point, so was expecting it to not be completely perfect. Not exactly sure which version is in Beans 6, but once I reflashed 12.2, my setcpu setting seem to be respected. Until I plugged it in to charge. Then it once again jumped up to 1900. So I made a profile in setcpu for when on the charger and locked it down to a lower level and it's has stayed at the levels specified in setcpu since then.
Now I'm just using more battery that I want to be, but still have to track down whether is a kernel thing, an app thing, or a phone thing...guess I should have baselined the new phone before flashing...
Anyway, just updated to Beta v0.1 and will report back on my battery findings.
I had amazing battery life with beans. The thing you have to do for sure is lower the CPU. 1.9 is way to much and the phone runs extremely hot. I just started synergy 1.6 and battery script today. I'm going to compare my battery life tomorrow. I recall on beams r6 it took 3 hours of screen off time for me to even lose 1% battery!
The only thing I don't like about beans is the scrolling wallpaper..wish he'd give us a flash to remove it . Also sucks not being able to charge your phone while its off with the custom kernel.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I had amazing battery life with beans. The thing you have to do for sure is lower the CPU. 1.9 is way to much and the phone runs extremely hot. I just started synergy 1.6 and battery script today. I'm going to compare my battery life tomorrow. I recall on beams r6 it took 3 hours of screen off time for me to even lose 1% battery!
The only thing I don't like about beans is the scrolling wallpaper..wish he'd give us a flash to remove it . Also sucks not being able to charge your phone while its off with the custom kernel.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
While I'm hoping for better battery life, I'm not expecting anything like that 3 hrs of screen at 1% battery would equate to 100 hrs of battery lift with the screen on. No, I'm just wanting to get less that 1% an hour drain at idle. It bugs me when the phone drops so much at night. I never did a good test on Beans 6, but there were a couple of night where in a 7-8 hour period it dropped double digit percentages....up to 15%. But I also found later I was battling an occasional wakelock issue. So I wanted to wipe and flash and try again...
So, when Beans 7 dropped, I did just that. Loaded it up last night and forced myself not to restore apps until I got some baseline information.
The initial clocks in the kernel seem good... As an aside, I almost want to install Beans 6 again and see if the overclock happens initially or if it had something to do with restoring SetCPU with data from my previous phone... This time I restored App Only and clocks look good. Even when charging, no extra profile needed like with kernel Test 12.2.
Idle battery life with just a couple extra apps installed was acceptable. Lost 6-7% over 8.5 hours. I was thinking stock was better, but now that I think back on it, the only night I was pure stock I didn't get to bed until 3am. So it lost, I think, 4% in about 5 hours...So given my fuzzy memory on the numbers, probably about the same at idle, maybe a little bit better with Imoseyon's Beta 0.1 Kernel...
So I've restored apps now and will fuss over battery life and other stuff for a few days more and then settle down and just use the thing.
Final note. Beans 7 looks awesome. The 15 toggle and notification looks nicely polished. Gone is the little nagging issue of having trouble grabbing the notification bar. So thumbs up all the way around so far...:good::good:
Im on beans b7, currently running stock settings...my device is running at 30*c, and my battery life is at 23hrs @ 49%. 1.5hrs of screen on time.
Hi, so I recently got an Infuse from someone that is still on Froyo and I figure I might as well upgrade to a custom rom.
Since I care about battery life the most, I figure I would ask which version of Android provides the best battery life for the Samsung Infuse: Gingerbread or Ice Cream Sandwich.
I probably won't be running apps that fetch/push for data a whole lot, which obviously helps the battery life. But I thought I'd ask to get someone's opinion on this specific phone and a comparison between Gingerbread vs ICS before picking a rom.
And the winner is... Gingerbread!
Sent from my sweet & buttery Infuse
abc617 said:
Hi, so I recently got an Infuse from someone that is still on Froyo and I figure I might as well upgrade to a custom rom.
Since I care about battery life the most, I figure I would ask which version of Android provides the best battery life for the Samsung Infuse: Gingerbread or Ice Cream Sandwich.
I probably won't be running apps that fetch/push for data a whole lot, which obviously helps the battery life. But I thought I'd ask to get someone's opinion on this specific phone and a comparison between Gingerbread vs ICS before picking a rom.
Click to expand...
Click to collapse
Gingerbread is a better battery saver. Although i get decent battery on ics and jellybean. I know i perfer all that ics/jb has to offer in features over having battery life. But for what your asking id suggest AEON or the stock gb. Aeon is very stable and has some cool extras without much battery drain
Sent from my SGH-I997 using xda app-developers app
andros11 said:
And the winner is... Gingerbread!
Click to expand...
Click to collapse
Really? I got faaar better battery life on Scott's Paranoid Android ICS build than I EVER did for any Gingerbread rom...
Honestly, I don't even remember by now
I have never payed that much attention to battery life..
usually lasts all day for me on JB, that's all I need
Sent from my sweet & buttery Infuse
the more recent ics and jelly bean kernels get great battery life due to fixed bt and wifi drivers (the wifi driver and binary were taken from another device from what i understand) and more stable cpu clock code than it had initially. not too much more than stock but i have to say it is better for me. but i guess it all depends on usage. one may have better standby vs awake battery life or something. the available kernels have been this way for atleast a month. when we start to see more kernels with undervolt it should get better yet.
I'm using CM10 8/23 and my battery life is good.
One of the best I even made a snapshot (can't upload right now): 51% left after 12 hours 46 minutes.
That's why I'm in a dilemma between jelly bean and gingerbread. I do appreciate JB a lot, way better functions. But still the battery life and compatibility are big issues. I can get 2 days under gb but only less than 12 hours in JB, that's a big issue.
I have been getting great battery life with the latest JB ROMs I have been using. Pretty much on par with the GB ROMs I used.
Sent from my SGH-I997 using xda app-developers app
Can't say i've had good luck with battery life, I used to average 3 hours of screen on time in Gingerbread, but since moving to ics/jb that has dropped to anywhere from 30 mins (if i leave the phone and standby drain eats it) to 1 hour 45 mins on a single charge...not good.
No rogue apps, no media scanner (i constantly check these things with betterbatterystats, i don't install anything i didn't install on gingerbread). Just the cell phone standby drain eating my battery alive (BBS reports it as GTALK_ASYNC and RILJ wakelocks).
I've been researching it for months now and get various answers (the wakelocks are caused by bad APN settings for example), tried all the fixes, still no luck. I suspect that it's probably a Rogers thing but who knows.
threi_ said:
Can't say i've had good luck with battery life, I used to average 3 hours of screen on time in Gingerbread, but since moving to ics/jb that has dropped to anywhere from 30 mins (if i leave the phone and standby drain eats it) to 1 hour 45 mins on a single charge...not good.
No rogue apps, no media scanner (i constantly check these things with betterbatterystats, i don't install anything i didn't install on gingerbread). Just the cell phone standby drain eating my battery alive (BBS reports it as GTALK_ASYNC and RILJ wakelocks).
I've been researching it for months now and get various answers (the wakelocks are caused by bad APN settings for example), tried all the fixes, still no luck. I suspect that it's probably a Rogers thing but who knows.
Click to expand...
Click to collapse
did you try cm9?
qkster said:
did you try cm9?
Click to expand...
Click to collapse
Yup, it's all been the same since ICS, I absolutely cannot get acceptable battery life, no matter what i do.
threi_ said:
Yup, it's all been the same since ICS, I absolutely cannot get acceptable battery life, no matter what i do.
Click to expand...
Click to collapse
are you getting AOS drain while on wifi?
you may consider a factory reset and sdcard format
when you reinstall, decline all google locations and backup services.
qkster said:
are you getting AOS drain while on wifi?
you may consider a factory reset and sdcard format
when you reinstall, decline all google locations and backup services.
Click to expand...
Click to collapse
I have done a factory reset, i formatted my sd card not too long ago (I also suspected this)
I also make sure google locations is disabled, never keep backup enabled (i did once by mistake and the auto restore nearly killed all my monthly data)
I am going to toggle wifi tonight and set a marker in BBS, i'll check the drain overnight (I did this a while ago and it did improve standby drain somewhat, but I am going to try it again)
threi_ said:
Can't say i've had good luck with battery life, I used to average 3 hours of screen on time in Gingerbread, but since moving to ics/jb that has dropped to anywhere from 30 mins (if i leave the phone and standby drain eats it) to 1 hour 45 mins on a single charge...not good.
No rogue apps, no media scanner (i constantly check these things with betterbatterystats, i don't install anything i didn't install on gingerbread). Just the cell phone standby drain eating my battery alive (BBS reports it as GTALK_ASYNC and RILJ wakelocks).
I've been researching it for months now and get various answers (the wakelocks are caused by bad APN settings for example), tried all the fixes, still no luck. I suspect that it's probably a Rogers thing but who knows.
Click to expand...
Click to collapse
i do notice battery drain in some areas. but not others. some people seem to think certain modems are effecting the cell standby drain, not sure myself. but there are many compatible modem.bins to try from att and t-mobile(t959v)
Just an update: wifi didn't help much.
threi_ said:
Just an update: wifi didn't help much.
Click to expand...
Click to collapse
I've been playing around a bit with different gb kernels, odex and deodex.
I found the drain issue much less on stock uclb3 kernel and rfs file system.
Almost all drain were associated with being on wifi...wakelocks and something else kills the battery.
If I have wifi off, there is usually not any issue.
You may have to play around a bit to see. My experience on cm9 and cm10 has been limited. I have noted several users noticing drain on cm9 and cm10 as well.
To avoid drain:
1. Use it to the max and constantly.
2. Leave the phone on airplane mode when not in use.
3. Turn off data (wifi and mobile data) and background data when not in use. I use this last mode.
Thanks for the tips man :good:
Airplane mode of course makes batt life better (disabling data doesn't), but when I start having to make sacrifices I didn't have to on GB it becomes a problem for me. Why should I jump through hoops and gimp my convenience for battery life that still isn't even as good as GB?
Instead of that i'd rather try to find the root cause of the problem. Doing so then allows us to help others that may have the same problem.
It definitely is an issue with the radio (or rather CM code overlooking something concerning the radio). What exactly, i'm not too sure. I've tried different modems as well, UCLB3 on JB was awful for battery life, UCKL2 and UXKG3 are slightly better but still not that great.
I don't want to complain about these things, I always try to research first, but damn....i'm stumped.
threi_ said:
Thanks for the tips man :good:
Instead of that i'd rather try to find the root cause of the problem. Doing so then allows us to help others that may have the same problem.
I don't want to complain about these things, I always try to research first, but damn....i'm stumped.
Click to expand...
Click to collapse
Yeah, I agree with you there. The techniques I use is pretty simple. Pose the hypothesis. Start with a full deck and slowly eliminate or start minimal and add.
ex: flash jb without gapps; without microSd. try different modem; try a different kernel. different kernel from different build.
have to use it for a few days to find out.
do the same for cm9.
add gapps...
add microsd
etc..
at some point, you will find out contributing factors.
There are a few battery thread that may be helpful if you havent looked:
http://forum.xda-developers.com/showthread.php?t=1408433&page=9
Ryo Misaki said:
Really? I got faaar better battery life on Scott's Paranoid Android ICS build than I EVER did for any Gingerbread rom...
Click to expand...
Click to collapse
This is true, and you can save battery life w/ customization and now Scott is up to JB being one of the best battery life roms I've run
or just turn down your screen brightness