DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Battery life??
- Thread starter asperber
- Start date
Anyone have any ideas why my Android System is using so much power? Thanks
I dunno, man. I still didn't get much of an answer when I posted that article about the super-high Cell Standby numbers I'm always getting:
View attachment 57259
Last edited:
Tailgun said:
Do u have kies enabled, what about s beam? I disabled ALL that stuff that im not gonna use. If i come to a situation where i would use it Ill turn it back on. I want thru n disabled bloat stuff, if it need it to time the phone, leave it. Otherwise disable it.
♕♥♔QUEE₦ BEE ♔♥♕
Rookie mistake.
hammerhead13
Gold Member
I can go a whole day with WiFi on and heavy use since I got mine on Sunday. Love it. My LG Spectrum would die in about 5 hrs.
Strange. I gave my phone a full charge last night and Android System is back to normal but now my Cell Standby is high too.
Found this article about the high Cell Standby numbers. Solution: Samsung Galaxy S3 Cell Standby Battery Drain Problem
Well your cell standby is so high because it's been on standby most of those 10 hours. Even so, 86% charge after what I'm guessing is about 9ish hours of standby, is pretty good. It's when Android System is high that something is happening. What, however, is still a mystery...
squeekybigfoot
Member
Ok so I've been experiencing the android.system drain since my first GS3 around August 5thish. I had to replace that one, but it still happens on the new device. With both phones I had amazing battery life the first few days, even with a bunch of apps installed. With the second, it did start after I restored most of my apps with Titanium Backup, though not immediately. This lead me to believe it was an app. So I went through, uninstalling random apps that I thought might be culprits, battery pull, nothing helped. So I gave up, started researching, then...out of nowhere, it's gone. And I'm back to amazing battery life. This carried over for a few days, without me not doing anything different or installing anything, and suddenly...it's back. Long story short, I don't think it's an app anymore, so much as a system setting, because the app "evidence" is so inconsistent, as evidenced by all these threads on it. Certain apps might "trigger" it, but the problem is deeper. So I messed with everything from GPS to wifi, using a live wall paper, even changing settings in both apps and stock...no change. But again...suddenly gone. Basically I couldn't pinpoint a common denominator except it happened randomly. Or so it seemed...
It happened again on Sunday night, and so I decided to see what happened. Only thing that really changed app wise were updates from the store. No change after those. Then I fell asleep Monday night without plugging my phone in, and android.system drained my battery to 3% from maybe 40ish%. I charge it for the 45 minutes I had before work, got it to like 49%, android.system still close to 25% in Gsam. Watchdog still showed nothing. Used a co-workers charger for a bit at work to make it through the night, finally drained it completely, did a battery pull, charged it to 100% while off, turned it on this morning...no problem. Been opening all kinds of apps today, changing settings...android.system is still around 4%, as opposed to being up to 50%. I found the gsiff_daemon solution, and I did have it at the top of the list, so I renamed it. No change. Deleted it. No change. Definitely gone though.
So now I think it's a battery issue. For those of you who experience it, did you happen to have unusual charging patterns around the time it started? Charging it for a few minutes here and there? Or draining it completely? So I'm thinking it has something to do with how the phone uses the right amount of power for what it's doing. When it's locked, it for some reason still thinks the phone is on and so is taking more power. And remember, as many changes as I could think of didn't help. So maybe it's happening in the hardware (however a phone determines power from a battery :blink
moreso than the software?
And sorry this post is so long, the idea was to show you I've already tried everything suggested and more (short of a FDR). One common denominator is all threads on the issue have the same suggestions and identical screen shots:icon_ devil:
Here are some screenshots I just took of what it SHOULD look like:
View attachment 57525 View attachment 57526
It happened again on Sunday night, and so I decided to see what happened. Only thing that really changed app wise were updates from the store. No change after those. Then I fell asleep Monday night without plugging my phone in, and android.system drained my battery to 3% from maybe 40ish%. I charge it for the 45 minutes I had before work, got it to like 49%, android.system still close to 25% in Gsam. Watchdog still showed nothing. Used a co-workers charger for a bit at work to make it through the night, finally drained it completely, did a battery pull, charged it to 100% while off, turned it on this morning...no problem. Been opening all kinds of apps today, changing settings...android.system is still around 4%, as opposed to being up to 50%. I found the gsiff_daemon solution, and I did have it at the top of the list, so I renamed it. No change. Deleted it. No change. Definitely gone though.
So now I think it's a battery issue. For those of you who experience it, did you happen to have unusual charging patterns around the time it started? Charging it for a few minutes here and there? Or draining it completely? So I'm thinking it has something to do with how the phone uses the right amount of power for what it's doing. When it's locked, it for some reason still thinks the phone is on and so is taking more power. And remember, as many changes as I could think of didn't help. So maybe it's happening in the hardware (however a phone determines power from a battery :blink
moreso than the software?And sorry this post is so long, the idea was to show you I've already tried everything suggested and more (short of a FDR). One common denominator is all threads on the issue have the same suggestions and identical screen shots:icon_ devil:
Here are some screenshots I just took of what it SHOULD look like:
View attachment 57525 View attachment 57526
Last edited:
SteveSchweer
New Member
I had the same experience. I tried to tie the problem to a particular app or battery charging procedure.... No connection. I finally decided that it is an operating system bug. Somehow, on the SIII (but not the SI that I used before this) I think that as apps call for op system services, like GPS for instance, the op system doesn't always get the "stand down" order. This causes what I call "GPS runaway" or the phone to be "held awake" for long periods of time. I can usually tell when this is happening by the phone heating up in my pocket. I think the best thing to do in these situations is to re-boot (turn off and on) the phone.
MailboxHead
Member
I too am starting to get this Android OS battery kiss of death. Usually when I restart the phone it "fixes" itself. However, if I use the GPS on the phone it starts running wild again, even though I turn GPS off. I love this phone, but I'm pretty disappointed that every time I use GPS I will have to restart the phone or risk crappy battery until I do. I realize that it restarts pretty quickly (good heavens, my TBolt took like 10 minutes), but I also feel like it's ridiculous that I should have to constantly be restarting my $600 phone.
Looking back, this problem didn't start until I started using my phone for GPS so I'm convinced that in my case GPS is triggering this problem. I really don't want to root - I'm a lazy coward, but that might be the only option left to me. Sad frownies, because this phone is so fantastic in every other way.
Looking back, this problem didn't start until I started using my phone for GPS so I'm convinced that in my case GPS is triggering this problem. I really don't want to root - I'm a lazy coward, but that might be the only option left to me. Sad frownies, because this phone is so fantastic in every other way.