Related
Hey all, I don't know if anyone has even noticed on their Evo's but on mine, the Android system usually eats most of the battery. I noticed there is a ton of processes under Android system that are running compared to like five on my Hero. I've never seen the core system processes take up more than maybe 15% of the battery, but right now, I'm at like 41% with 16m 6s of CPU total and 47s of CPU foreground. If anyone knows why this is or a way to fix it, please let me know. I'm on the first MR update. I've been able to get a lot of battery stuff figured out, if I can get the system to calm down, then I should be able to get even better battery life than my Hero.
I'm seeing the same thing, android system is at 96% battery use after letting the phone sit overnight. Never saw that on my nexus, this is strange.
Could be related to the fact that everything is syncing up, I just activated last night too.
-------------------------------------
Sent via the XDA Tapatalk App
Yeah, the system seems to have calmed down a bit today, though I also have the OC widget running to keep the processor lower during sleep. I'm guessing its helping, but I'm not sure if there is something else to get it down. I almost never even saw the System show up in usage on my Hero, now its one of the top contributers. I got used to having custom roms on the Hero, but so far all I need on the Evo is unrevoked. I know a lot of people around here don't like it, but I found I only needed a couple of apps that require root and so far love it. That OC widget really comes in handy.
maybe i can clear things up a little bit for you guys...what you see in the battery use section is distributed across 100% of the time since you last had it plugged in. if you notice all the percentage numbers add up to 100%.
if you plug your phone in and turn it on and off on you will see that android system is probably around the 90's thats because android system has used 90+ percent of the phone since you plugged it in....over time that number will lower, becuase other things will start using the battery power... what you see is a percentage based on time. not based on whats actually working RIGHT THEN AND THERE do you guys understand?
I too am having that problem and at 15% battery life warning - it still shows my Android system @ 40-44% usage after 8hrs of work.
I mostly text message all day long due to work - make phone calls and recieve calls from work every hour. GPS on for no more than 15min all day long to get direction when my keymap book doesnt help.
4g off, bluetooth off, background data 15 min only (gps) than off, gps off when not in use, mobile network (3g) off when not in use.
I would have figured my screen being on would have drained my battery life since I check text message every 10-15mins for 8hrs...
So went to work at 9am, 100% life
got off work 6pm, 25% life
I've done all the tricks, cdma only, force stopped a bunch of apps, goggle talk off, sync off, making sure maps/gps has been closed (forced or not)
still disappointed with battery life.
Unrooted Evo
My crappy AT&T Razr lasts me 2-3days with text message + call + 1.5hr of playing Bejeweled a day
*facepalm* you guys don't get it....
grrgrrgrr said:
I too am having that problem and at 15% battery life warning - it still shows my Android system @ 40-44% usage after 8hrs of work.
I mostly text message all day long due to work - make phone calls and recieve calls from work every hour. GPS on for no more than 15min all day long to get direction when my keymap book doesnt help.
4g off, bluetooth off, background data 15 min only (gps) than off, gps off when not in use, mobile network (3g) off when not in use.
I would have figured my screen being on would have drained my battery life since I check text message every 10-15mins for 8hrs...
So went to work at 9am, 100% life
got off work 6pm, 25% life
I've done all the tricks, cdma only, force stopped a bunch of apps, goggle talk off, sync off, making sure maps/gps has been closed (forced or not)
still disappointed with battery life.
Unrooted Evo
My crappy AT&T Razr lasts me 2-3days with text message + call + 1.5hr of playing Bejeweled a day
Click to expand...
Click to collapse
check your hardware version there is a thread about different types of evos and it seems like everyone who has the hardware revision 0001 has really bad battery life. i would exchange your device.
Yes we know, Freelancerx, or at least I do. But after over 8 hours and the system is still using more of the battery than anything else is a little disturbing. Never seen that on any other device. I have Hardware 0002.
I have this same issue with hardware version 0002. I run Fresh 1.0.1, i use Netarchy-toastmod kernal, have latest radio. I have also tried Damage Control (did get slightly better battery life out of DC but not amazingly different)
after 7 hrs since unplugged my andriod system is at 39%, cell standby 28% phone idle 20% display 9%.
i dont have bluetooth, wifi or 4g on. I use juicedefender+ultimate to turn off apn when screen is not on. I use set CPU to underclock when i am unplugged and go down to 128 when screen off and i am Stilll lucky if i make it all day with moderate usage.
Every day it is the same andrioid system is around 40% of the usage for the time it was unpluged.
the following is listed under included packages (not sure if this shows the same for everyone or if it shows what packages are running)
BRCMBluetoothService - Bluetooth is not on so if it shows packages running this may be an issue
Sync Feeds - I have all android syncs off and mail at 6 hours
settings storage
Rosie Utility
Acounts & syync
Account and sync settings
settings
HTC Widget Download Manager
Network Location
Setup
HTC Checkin service
Checkin serivce
VPN services
Android system
Wonder if there is something to the android system on these (ie something not turning off that should) or if we are all just crazy and happen to get the same results.
I had a hardware 0002 model and often experienced the same thing with high system % usage.
My phone was replaced, due to a screen issue, and now I have the 0003 model and seems system % is much lower so far.
I haven't installed any system update yet, so I am on the first original release rom (not rooted yet).
Going to be testing it for a few days before I update and root, so I can make a fair comparison between the original and current oem's.
If your phone is on....Android system is being used.
satch12 said:
If your phone is on....Android system is being used.
Click to expand...
Click to collapse
I think everyone here understands this. the question i think we are trying to figure out is why with similar usage and configurations some people get 40-60% android systems usage while others get 10% over the same period of time.
Android system is way too high.
satch12 said:
If your phone is on....Android system is being used.
Click to expand...
Click to collapse
Yes but if it is configured in an optimal way then android system is always beneath cell standby and phone idle.
For example, today after 15h 28m 23s since unplugged I have...
Cell stanby 38%
Phone idle 37%
Android System.....12%
That is with background processing with auto syncing every hour or so.
I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.
Anyone? Bump? No one else is having the issue? Still happening to me on RC3.
I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.
Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Solved using Calkulin's wipe method
I'm getting pretty good results from my setup.
1. Myn's Warm rom rls4
2. New kernel- I just downloaded last night but the battery stayed on 100% for quite a while. Here's the link- http://forum.xda-developers.com/showthread.php?t=876590&highlight=calkulin's
3.Riptide9's ColorNclear theme with several of the addons, speedo batt, blue dialer, launcher pro (the update for warm2.2 themed).
I myself have tried probably every rom out there that has working 4g, I dont see owning an evo and not having 4g, and found this one to be the best. You do have to do an update to the wireless tether, can be done through the app itself. Hit me up if you need assistance. If it is the batt life you're primarily concerned with, this kernel is supposed to be awesome. Check it out, mine is overclocked to 1152000 and it still stayed at 100% for a good amount of time after being taken off charge. If you try it and like it let me know. I like to know that I was able to help someone.
Try removing your SD card and see if it still has that issue.
I suppose I should have mentioned why I need a fix so badly...
I'm only getting ~4 hours of battery life. I go into work at 6:30am and when I leave for lunch at 11:30, my phone is dead (with absolutely no use).
I need to figure out what this "0" is in "Network usage" because that's what is keeping my phone awake 100% of the time. Like I said though, even Airplane mode doesn't fix it (I don't see why something is using my network in airplane mode).
I tried removing the SD-card, that didn't help.
I've already tried the kernel that you linked to, that didn't make a difference... Same issue, my battery just drops.
If I'm doing something, I can literally just watch it drop in front of my eyes. If I'm using the phone (browsing the web, checking email, etc...) it drops one percent about every 20-25 seconds (I get something like 40-45 minutes if I'm using the phone before it dies).
maybe you have a faulty batt. I dont know.
Have you tried completely starting from square one?
titanium backup, then wipe everything, wipe again, and flash the stock rooted rom (or maybe even the OTA and re-root later).
After flashing, reboot your phone but dont restore your backup yet. See what happens, then slowly restore apks and files, etc, one at a time and see how the battery acts.
I don't know what the "0" means, sorry. But maybe this will help you figure out what is causing the problem.
Harfainx said:
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Click to expand...
Click to collapse
You need to do caulks format all as it will wipe everything that the recovery misses. Hope that helps
Sent from my PC36100 using XDA App
Excellent, I got it working!
Performing Calk's wipe, and doing a fresh install seems to have it working again. I was thrilled to see that I wasn't at 100% after setting my phone down for 20 minutes to let it sleep.
I've been installing apps one by one hoping that something doesn't break it again.
I still have no idea what was causing the problem, but it's fixed now. Thank you for the help everyone, especially Craigbailey for the advice and Calkulin for the fix.
So I'm having this exact same problem (100% time running), but Calkulin's format all did not work for me. I ran it, flashed a brand new ROM, and I was still at 100% run time. I did nothing other than sign in to google, and download spare parts to check my run time.
Any other suggestions?
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
After finally flashing my phone with EVIo Cailukin's Rom I have endured some problems and I've search for them and coudln't find anything. I rooted my phone with the latest UnrEVOked program. Noticed this morning my phone was running 100%...
upon other problems, my phone internet speed is lagging. and my battery is really hot!
Pneuma1985 said:
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
Click to expand...
Click to collapse
I tried the removing the battery thing, and I'm still getting 100% run time, with a nandroid restored rom, and 2 different newly installed roms. I am so confused now. Anyone have any suggestions?
UPDATE: Looks like my phone is not at 100% run time anymore. All I did was redo Calkulin's format_all, flash a new ROM, and then reflash the new radios and PRI, and now my phone is not 100% running anymore.
Yay!
The battery on my Evo has been plummeting recently. A while ago I could make 36 hours easy, and now I am lucky to get 12. The reason it seems is cell standby/phone idle, according to battery info. Over the course of last night I went from 85% to 28% while I just slept, and according to battery info these two things are responsible for that.
I'm not sure what they are or how to decrease, however. I read that NV and PRI 1.90 was causing problems for a lot of people so I tried downgrading to 1.77 as suggested, but I have no idea where to find the information to see if I successfully downgraded. I am running CM7 nightly build 23, I have wiped battery stats once and I am currently waiting for the phone to die before charging it again, but this has been going on for quite a few days over numerous roms and battery wipes. If I put my phone into airplane mode, the battery is hardly touched overnight. During the day I need my phone on however and the battery drains just as fast, whether I am using it or not.
Any suggestions?
ps. under accounts and sync the only thing I have set to sync is email by push, I receive only a few emails a day and a couple at night so I don't think that would be the problem. Facebook is also set to sync contacts, but only find status updates and the like when I refresh manually. Twitter, and my google account in there but both of those are set to sync manually.
Have you checked your partial wake lock in spare parts?
teh roxxorz said:
Have you checked your partial wake lock in spare parts?
Click to expand...
Click to collapse
I have never used spare parts in my life so bear with me; but when opening it now all I see is device info including battery history, battery info and usage stats, and general options which all have to do with animations, font size, haptic feedback, or compatability mode. I don't see anything that talks about wake lock in here
You click battery history, then on the first tab, click partial wake lock, and on the second, you can click since last boot.
teh roxxorz said:
You click battery history, then on the first tab, click partial wake lock, and on the second, you can click since last boot.
Click to expand...
Click to collapse
thanks! under partial wake usage since last boot, it's hardly nothing.
Android system is by far the winner with almost 11 minutes of usage, email is next at just under 2 minutes, facebook at about 1.5 minutes, and a couple other things (dialer, sms, google voice, google services) all coming in between 5 and 30 seconds.
Hmm...are you in a bad signal area or leave your radios [3G,wifi, 4G] on all the time?
I suppose I have 3g on. I never leave wifi or 4g on and my signal is between -85 and-96, according to battery info my time without signal is 0%
Well you should turn your 3G off when not using it, that'll definitely save your battery.
I will try that in the future, but it still does not explain why I am getting 1/3 the battery life I used to while doing much more to conserve battery. Could it have to do with my pri and prl and such? Maybe I need to update profile and such, like it's not looking for the right towers? I don't know much of anything about how polling and service works.
What's your wake time vs. your up time?
It sounds like you have something staying awake.
Have you gone to menu>setting>About Phone>software information to see if your PRI version & NV have been downgraded?
What kernel are you using?
Are you using RA or Clockmod for recovery?
countryfried said:
What's your wake time vs. your up time?
It sounds like you have something staying awake.
Have you gone to menu>setting>About Phone>software information to see if your PRI version & NV have been downgraded?
What kernel are you using?
Are you using RA or Clockmod for recovery?
Click to expand...
Click to collapse
I'm not sure how to check wake time vs up time, but it would likely be useless right now, as I nandroid backup, flashed a sense rom, updated my prl and profile, checked to make sure i did downgrade pri/nv and then went back to cm7, so any battery info it is going to give me right now will be inaccurate while I wait for it to charge/discharge again over the course of the night. It does still have my previous information though since it was a nandroid backup and I've had it plugged in entirely since then.
I did succesfully downgrade to 1.77 PRI
kernel is savagedzen 0.2.1 cfs havs wimax GB (2.6.37.4)
RA for recovery.
I also uninstalled a few programs including facebook and twitter in case there was anything like that interfering with my services. I still use Go contacts and Go sms however, but I have unchecked any options with them to have facebook integration. If you could tell me how to check up/wake I can check that tomorrow morning when I wake up to see and go against whatever I had. Currently I'm just trying a few things out before tonight to see if anything had helped. An idle phone sitting on my window sill for 8 hours should not drain the battery THAT much, so something is off.
Go back into men>settings>about phone>battery (you can check it now)
If your up time and awake time are the same, you have a program that's stuck in wake. I also use a program called "system panel" that will show me live time which programs are using the most resources. OR you can use "Battery Monitor".
If you have wifi at home I would suggest you set up your phone to connect to wifi and shut your 3g off. I use a program called "Y5-battery saver". It automatically connects me to wifi at home and disconnects and switches to 3g when I'm away from the house.
attached is a screen grab of the graph from battery info
if needed:
cell standby says time on 15h 44m 47s (same as time listed on battery)
phone idle says 14h 46m 58s
(these 2 items used 47% and 44% respectively
thanks for the wifi tip, i used it on sense a lot but with most aosp roms it causes problems unless you set it to never sleep, and i didnt know what that affect it had on battery so i usually just turned it on when necessary or when in a low-signal area like school.
That doesn't seem that bad for ~14hrs on battery.
my problem is that it's while I'm sleeping. I used to get 36 hours of battery before getting to 15% and being told to plug in, and now I used it a little last night, went to bed and woke up to it being at 28% and was told soon after to plug it in. I just dont remember sleeping destroying battery life like that in the past. granted 15 hours isnt that bad, but when 10 of the 15 hours the phone is just sitting there it worries me because if I were to go through a normal day, where I charge it at night and use it during the day, there is just about 0% chance that I'll be able to make it through the day without plugging it in sometime in the middle.
teh roxxorz said:
That doesn't seem that bad for ~14hrs on battery.
Click to expand...
Click to collapse
yeah, that's not bad. You're still at 87%? LOL. Maybe I need to switch to AOSP ROM!
I'm Back to 87%, I've been on the charger all day, hence the battery graph raise. the dramatic raise was from when I flashed the sense rom to update my profile/prl. (obviously it wasn't monitoring during that time and when i came back and started monitoring again the battery was much higher)
it actually died after ~15 hours, with 10 of those 15 hours having doing nothing. I got systempanel to see if it gives me any more info and the main reason i use aosp is because of the terrific backlight handling. I like it to be super dim while inside and bright outside, and find on sense roms the auto backlight is too bright under normal conditions. I should be getting much better battery life than this. I'll try again tonight with the battery being monitored to see whats up and I'll try going into airplane mode tomorrow to see what that does at night for comparisons sake. hopefully there is just some program using lots of data that I don't know about. i'd love a quick fix lol
It's almost as if there's an Evo "battery curse"!!!!!! It has been HELL finding a ROM that I love that has great battery life. I really liked Myn's but for some reason I could NEVER find a kernel that would give me great battery life. I'm currently using ultrablakk 3 by King's and love the interface, just trying to find the right kernel myself. I think I'll do a nand and try an AOSP for a change. Vaelpak looks stable. Good luck with the battery life issues!
I'm using an unrevoked-rooted evo and at 10% wake time, it lasts for about 15 hours unplugged. That is why I usually keep it plugged in whenever possible. I have task killer and do not synch anything except for weather and news. I do have 3G running all the time as well. I wouldn't do that if it weren't for the email checks (4 accounts checking every 30 min). If the 3G could be automated to turn on during the checks, that would save more battery life, but I don't know of anything to do that yet.
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Checkout this thread to see if the gsiff_daemon is your problem. tl;dr when the system is hot and tearing through the battery, go to system settings -> Developer options -> and check Show CPU usage. If gsiff_daemon is the top or second highest on the list, then that is your problem. To solve it for the moment, use system tuner, or something else, to kill gsiff_daemon. There is no permanent cure at the moment, other than to delete gsiff_daemon. Both of those fixes require root, the non-root fix is to reboot.
If gsiff_daemon is not on the list, then something else is the problem, but Show CPU Usage should give you an idea of what system process is running hard.
Samsung Push problem
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
dansushi said:
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
Click to expand...
Click to collapse
Interesting, I installed "micro cpu monitor" shows thin line at top of screen showing both cores.
I haven't had this happen for some time now but after playing with google play and maps downloading offline maps etc I noticed my 2nd core pegged out.
Having seen this in the past & ignoring it I now realize that majorly drains the battery as well as it getting warm.
A simple reboot seems to be the only thing that fixes it. Clearing ram and closing recent screens dies nothing to clear the "cpu jam".
If left alone, it always shows the culprit as "android system"
As to what part of "android system" I don't know.
But until we figure this out for good, that little micro cpu monitor. App is sweet for peace of mind to know all is well or whether a reboot is needed. For what it's worth, I also noticed that after the event, that my auto rotate to landscape was mysteriously unchecked?
If it jams again, I'll have to see if it gets unchecked again, unknown if there is a relation.
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
That happened to me too. But for me, flashing another rom fixed it.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Swaggernaut said:
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No there is a cwm flashable fix floating around here for that
Galaxy SIII via XDA premium
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Contact sync?
i noticed this today and while troubleshooting, noticed contact sync from google says "sync is currently experiencing problems..." maybe?
dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
I read the thread about gsiff_daemon culprit. I had it listed as a possible battery drain culprit. The thread says the issue may happen after a hot reboot...which I did have. Killing gsiff_daemon was not immediately effective. I renamed the file so it wouldn't get used...like the thread recommended. I had to reboot to get normal battery drain back and have yet to see the issue again. But i wont know for some time...or maybe when/if i get a hot reboot...which is really rare. Do yourself a favor, and buy better battery stats. Its a must have tool...and it's not expensive.
I wonder if this problem has been solved with latest lj7 jellybean from sprint
Sent from my SPH-L710 using xda app-developers app
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
eatonjb said:
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
Click to expand...
Click to collapse
My experience with froyo/gb/ics is that things have been getting progressively better over the years. But with each so called UPGRADE of an OS or even APPS, we often have to deal with bugs or incompatibilities. I am eager to upgrade to a stock based JB soon, but wisdom says, for 20 things improved, there will be 5 things broken....or hurting in some way. Early adopters suffer the most as usually these issues get ironed out...most of them.
BUT...these stuck drains...wake locks etc., it seems they will happen when they do no matter how many issues get fixed. Over the years, I've had random standby drains caused by Maps/Nav. Maybe it's ok for months, then after a particular update, it's back...and unpredictable. The YES...a reboot, just like with a PC, is a quick short term workaround.
Finally, with the App CURRENT WIDGET, there is a provision to watch for high drain in standby. It watches MilliAmp (ma) readings over time..to determine if you have a rogue drain. That's different than monitoring the CPU. (Some drains do not cause much CPU activity) BUT UNFORTUNATELY, that app won't work with our S3's because of a lack of hardware support. Works great with HTC and many others. It's a bummer because I used to use it and have my HD2 reboot if a 15min consecutive high drain was recorded in standby....thereby saving the battery and usually killing the bug.
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app