Related
Hello,
I have a high battery drain because of "Android System". I lose about 3-5% per hour of my battery in idle state. I turn screen off and didn't use it.
I'm using Slim ICS ROM with franco kernel #174.
Badass Battery shows me that following included processes are in Android-System:
Code:
com.android.systemui
system
android:ui
com.tmobile.themechooser
surfaceflinger
com.android.settings
servicemanager
So anybody know what's the problem here?
I'm already disabled Google Photo Sync, NFC and GPS because I didn't need that. Also googling for the problem doesn't help.
Hope you can help, thanks!
You hit the "Yes this is a question" box
Guess where this thread belongs?
Thread Moved
Friendly neighborhood Moderator
you must install your rom again
this is based on your luck
luckydude said:
you must install your rom again
this is based on your luck
Click to expand...
Click to collapse
Again, I've mentioned this twice today: Bullsh**, I don't mean to be disshonouring, or anything, but please, give proper answers,. It's all good, that you want to help, but only with proper and correct answers.
Right, back to topic;
Go into your dev. settings, and uncheck everything that doesn't need to be checked (Stay Awake, Strict mode, etc.) Undervolt the CPU, that should save a ton of battery charge, and underclock to 900-920 MHz, that is definitly enough, on a dual-core
Thanks for your answer =)
I think my phone is already undervolted through Smartreflex in francos app and I also tried underclocking by setting max cpu to 1036 Mhz (instead of 1200 Mhz).
The problem disappeared after 1-2 charges (don't ask me why..).
And now after flashing Slim ICS 3.9, battery time seems to be ok (for me at least).
Per hour in idle state the phone consumes ca. 2-3%.
I ask myself how do others get 1% drain over night. Is that even possible? Tried very much kernels (franco, trinity, glados and leankernel) and didn't even get near that.
Any tips?
OP Im glad you mentioned the issues went away after a few charges. this has been an issue for some who do not believe that a few charge cycles does anything. well im with you as i always see things sort of "settle down" after a few days of flashing a new rom.
I have the same problem on my Nexus S.
The process consuming battery is surfaceflinger. I can see it on battery screen before the name change to Android System.
Pik3no said:
I have the same problem on my Nexus S.
The process consuming battery is surfaceflinger. I can see it on battery screen before the name change to Android System.
Click to expand...
Click to collapse
I doubt you will find much help here for the Nexus S.
adrynalyne said:
I doubt you will find much help here for the Nexus S.
Click to expand...
Click to collapse
I guess this is an Android problem. Not related to any device.
Android
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this
konsolen said:
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this
Click to expand...
Click to collapse
You need to read this. Also you, OP.
General Crespin said:
You need to read this. Also you, OP.
Click to expand...
Click to collapse
This. People, just give it 2,3 days for the rom to settle after flash. Same for a kernel.
konsolen said:
Yes, i think your prob comes to every Android phone after flashing New rom.
Just wipe Battery stets after flashing. It needs few complete chargings to calibrate the battery.
There are also many apps in the market for this
Click to expand...
Click to collapse
I don't know if was the new kernel I flashed or was the battery stats wipe I did, but seems now my phone have no more RILD/RILJ wakeclocks.
GNexor said:
I ask myself how do others get 1% drain over night. Is that even possible? Tried very much kernels (franco, trinity, glados and leankernel) and didn't even get near that.
Any tips?
Click to expand...
Click to collapse
Yes, it is possible. I get 1 or 2% drain overnight with wifi and mobile data disabled, and up to 5 to 6% if mobile data is enabled overnight.
My record with it is 1 day and 20 hours from 100% to 3%.
I had a LG Optimus Black before and didn't last a day. I'm loving this Galaxy Nexus.
Nuno
One Power Guard can help the system into a deep sleep,Reduce battery drain
downloaded from http://forum.xda-developers.com/showthread.php?t=1889740
Nuno_PT said:
Yes, it is possible. I get 1 or 2% drain overnight with wifi and mobile data disabled, and up to 5 to 6% if mobile data is enabled overnight.
My record with it is 1 day and 20 hours from 100% to 3%.
I had a LG Optimus Black before and didn't last a day. I'm loving this Galaxy Nexus.
Nuno
Click to expand...
Click to collapse
I would like to achieve battery drain like that, seems like what it should be.
I am running AOKP Build 2 and I feel like my battery life is ok but not great. I let my phone sit overnight last night with sync off, but LTE on and it drained roughly 4% an hour. I actually turned off LTE in the middle of the night to see if there would be a difference, and no, it drained at the same speed on 3G as well. I live in an area with pretty good reception actually, GSam says I spend the vast majority of my time with a signal strength of 4/5.
GSam reported that roughly 34% of my battery drain overnight was due to Phone Radio. Another 52% was due to app usage. Drilling into that it tells me that over 40% of the battery drain from apps came from "Android System", "Phone" and "Kernel". Under Android System, which was by far the greatest drain of the apps, it only kept the phone awake 1m18s overnight so that doesn't seem excessive. However, I'm confused as to why, with a good signal/connection my battery would drain at nearly 4% an hour whether connected to LTE or CDMA. Unless the radios in this device are poor, I have a hard time believing there isn't a way to fix this without using something like Juice Defender.
I can't recall because it's been so long, but I don't really remember any ICS ROMs draining this fast. I'm on a clean install of AOKP B2 and I've tried a few different kernels with the same results. Any ideas anyone?
So I wanted to let you all know that after trying a few different ROM/Kernel combinations all with similar idle battery drain, I installed the latest (9/21) CM10 nightly and I only lost about 10-12% overnight last night connected to LTE. That is a much better drain than the 30% or so I was seeing previously. Not sure why but my phone just hasn't been handling the latest AOKP builds very well. I am afraid to try a different kernel right now as I'm leaving town tomorrow for most of the week so I'll leave it as is until I get home next weekend, and see if I get this good of battery life with the latest Leankernel.
Surfaceflinger
The same happens to me, this app appear in BetterBattery stats, Surfaceflinger appear as the culprit of my 45%+ battery consumption caused by Android Sys
When I first rooted my phone (xperia S) I noticed an 31%+ energy consumption by Android Sys, I reflashed and re-rooted and stoped for 2 weeks or so, now 2 days ago I woke up to find that 81% of the battery is being drained by Android Sys, then it lowered to 31-43%. I noticed that when I refreshed the stock "Battery" app ,"Surfaceflinger appear for a moment, I seem that I confirmed with the BetterBatteryStats, Surfacaflinger appears at the top.
Why is this happening? Can something be done about it?
PS: I cannot change kernel, bootloader is locked...
Surfaceflinger and android.process.acore are top battery drainer. I mean how to make them not sucking on battery?
How much "miscellaneous" battery drain is normal after google fixed the lollipop bug?
I've read about the initial bug in lollipop causing high battery drain under the entry "miscellaneous". I'm using a 5.0.2 rom (as far as I've understood from the information about it) so the bug should be fixed. Yet I'm seeing quite some battery drain going to this "miscelanous" entry. Right now it's 9%, screen is first at 10% but I still feel 9% sounds like quite a lot or is this correct? What's "normal" here?
TigerSoul925 said:
I've read about the initial bug in lollipop causing high battery drain under the entry "miscellaneous". I'm using a 5.0.2 rom (as far as I've understood from the information about it) so the bug should be fixed. Yet I'm seeing quite some battery drain going to this "miscelanous" entry. Right now it's 9%, screen is first at 10% but I still feel 9% sounds like quite a lot or is this correct? What's "normal" here?
Click to expand...
Click to collapse
Im seeing the same - Misc is at 14% now and Screen at 10%. not sure if its WiFi related, as was the case with the early 5.0 release for the nexus 5, or if its related to NFC / something else?
smack_t said:
Im seeing the same - Misc is at 14% now and Screen at 10%. not sure if its WiFi related, as was the case with the early 5.0 release for the nexus 5, or if its related to NFC / something else?
Click to expand...
Click to collapse
What bothers me is that we do not know if this is "rediscovered" battery use that previously just wasn't reported, or if it's a new drain coming with lollipop. I like lollipop but there are quite a few things about the code that has me concerned.
TigerSoul925 said:
What bothers me is that we do not know if this is "rediscovered" battery use that previously just wasn't reported, or if it's a new drain coming with lollipop. I like lollipop but there are quite a few things about the code that has me concerned.
Click to expand...
Click to collapse
I dont think its the same bug. The Miscellaneous Drain encompases many things that run in the background that don't have their own status group in the battery stats. Usually, they are small drains compared to the screen, apps etc... it will be hard to determine whats causing it, unless you are a developer i think. Still the battery life isnt bad, so not really bothering me too much.
smack_t said:
I dont think its the same bug. The Miscellaneous Drain encompases many things that run in the background that don't have their own status group in the battery stats. Usually, they are small drains compared to the screen, apps etc... it will be hard to determine whats causing it, unless you are a developer i think. Still the battery life isnt bad, so not really bothering me too much.
Click to expand...
Click to collapse
I had some battery issues coming to lollipop as compared to kitkat so I guess that made me more doubtful. On my device misc always use up about as much as the screen which sounds like a whole lot that the cell has no idea where it went.
did you have it after flashing? or is it always there?
it only appears for me after using TWRP.
rhystagram said:
did you have it after flashing? or is it always there?
it only appears for me after using TWRP.
Click to expand...
Click to collapse
I'm not sure as I started flashing pretty much the first thing I did with the LG G3 that is affected by it. Do you think TWRP itself is to blame or rather an incompatibility with custom roms? I've not flashed stock to compare, but I could check my wifes phone, she is stock wout any root or hacking.
I am very upset with low battery life. It holds the charge ok while I am not doing anything, but overheats when I use the internet, GPS or camera. Power loss is about 20% per hour, which is unacceptable. I am shocked how come they can even bring such products to the market.
I recall that power consumption significanlty increased when I upgraded Sony Xperia Z1 from Android 4.4 to 5.
I have a rooted LG G4.
I want to install android 4.4 on it. Is it possible to install standard version of Android 4.4 or the phone will stop working?
I can definitely relate to the bad battery life, I lose 20%+ when using my phone during my lunch break, it's insane.
Unfortunately the bootloader is locked with no workaround currently, so there is no way to flash custom ROMs. If there was, you'd be hard pressed to find a developer working on an older Android OS as most tend to use the stock ROM and customize it or use a newer version of AOSP Android.
geoff5093 said:
I can definitely relate to the bad battery life, I lose 20%+ when using my phone during my lunch break, it's insane.
Unfortunately the bootloader is locked with no workaround currently, so there is no way to flash custom ROMs. If there was, you'd be hard pressed to find a developer working on an older Android OS as most tend to use the stock ROM and customize it or use a newer version of AOSP Android.
Click to expand...
Click to collapse
Thank you for information. I hope they will come up with something, like downgrade capability or Android 5 fix.
Go into battery stats and see what's draining your battery. Try installing GSAM battery monitor or BetteryBatteryStats.
Maybe you have email set up to constantly check or something else, but there is something draining the battery. Your drain is not normal.
I am getting easily 24 hours between charges. I'm getting a few hours of screen on time each day. My battery drain overnight is about 1% or 2% per hour. For example, I may go from 78% to 68% overnight. I think that's high because I had my G3 on Lollipop doing 2% or so most nights. I leave on WiFi and data all night.
I have been suffering this issue since I updated to N (screenshots attached).
Atm, SOT is about 3 hours.
Are you guys experimenting this battery drain caused by this two processes too?
In case this also happened to you. Were you able to solve it?
I installed latest RUU 2 days ago and nothing seems to have improved.
Your kernel and android system usage look OK to me... Google services are OK too IMO. Looks like you've used chrome and YouTube a bit.. Awake time up a little, that would be mainly from apps running in the background. You could try servicely to try and improve that...
Sent from my SM-P605 using Tapatalk
jbm76 said:
Your kernel and android system usage look OK to me... Google services are OK too IMO. Looks like you've used chrome and YouTube a bit.. Awake time up a little, that would be mainly from apps running in the background. You could try servicely to try and improve that...
Sent from my SM-P605 using Tapatalk
Click to expand...
Click to collapse
It doesn't look ok to me. Comparing it with the phone i use for working, it seems there is a problem in here.
As i was saying, the phone i use for working averages 10% combined kernel+android os consumption while my htc 10 averages 30%+.
I have the exact same issue. I just unplugged my phone and I'm already down 3%.
Sent from my HTC 10 using Tapatalk
Jyro275 said:
I have the exact same issue. I just unplugged my phone and I'm already down 3%.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Why not use Better Battery Stats, let the phone sit idle for 6 hours, download the dump file to your SD, and see what exactly is killing your battery.
There are too many variables to test your device reliably while it's in use. With GSAM, all you see is what's happening while the device is in use, and what 'Eats' your battery, but no 'Why' your battery life is poor, is it background processes/ notifications/ poor reception/ bad Wi-fi??
GSAM creates a guessing game. Logs never lie. If your battery is going bad, it will be reflected in your log(s).
I know, our device has really great battery life and I don't have anything to complain about that, but a friend of mine just got himself a new phone and his values make me a bit jealous and most of all: surprised and stunned.
He got himself a Xiaomi Redmi Note 4 (SD 625 variant, MKT variant really sucks), it has the same processor, same display and not even 700 mAh more (4100 mAh) and he got with some "dev rom" (made by Xiaomi, seems to just be the beta of that ugly MIUI 9, based on Andorid 7.0) 6h of SOT, doze seems to haven't really kicked in in that time. in their forum in the SOT thread I see people getting normally about 8-10 with up to over 12 h of SOT, most of them on stock ROM without any additions. And I'm quite irritated about that huge of a difference with not that much more battery. And he seems quite convinced that it's not on the cost of performance, you should notice that quickly on such a heavily skinned ROM.
Now my question is: how in hell is that even possible? I mean our devices seem quite comparablewith just a slight bump in battery but near-stock AOSP Android against pretty much an iOS clone. Does anyone have any idea what could cause that big of a difference? And if it's software based could that be done on our device? Because my experience and from different posts our device lasts about 5-6 h normally.
I mean I'm already lucky about my 2 days of usage with up to about 2.5 days on some weekends where I have a lot of stuff to do. But I wouldn't mind a bit of extra. But my biggest problem with that is as simple as: how? I could really use some explaination right now...
I don't have issues with device.. stock 7.1.1 with dec.patch, unlocked bootloader, with latest magisk. Also installed greenify.
Then you are one of very rare cases. My experience is about half of that.
And I also meant on stock ROM, without any modifications. So I don't know which apps you greenified, but that was not the point. I use Greenify too but more for apps that aren't supposed to run constantly in background when I only use it very seldomly.
The norm for this phone is 8+ hours SOT. Sometimes I get 10 and a few have had up to 12. Unless you're gaming 8 should be easy. 5 hours means something is wrong with your phone hardware, you have a rogue battery eating app or you're gaming. I rarely charge my phone over the weekend even when I use it a lot.
Well, neither of that is the case and I rarely see people claiming more than 6h of SOT
So the answer to your question is, it's the wrong question. The question should be, why does my battery not last very long and what apps or usage causes me to have such poor battery life? Compared to the Redmi Note 4 the Z Play is exactly where it should be.
Here's a link to the SOT thread: https://forum.xda-developers.com/moto-z-play/review/screen-time-t3643959
gsmarena battery life test 100h endurance rating: https://www.gsmarena.com/battery-test.php3?idPhone=8310#show
Here's an app to help diagnose battery condition (Accubattery): https://play.google.com/store/apps/details?id=com.digibites.accubattery&hl=en
also betterbatterystats is really helpful.
I sincerely hope you get it sorted out!
Well, gsam isn't detecting any app that's off even with root so I don't think there is any. I installed that AccuBattery app, let's see what it has to say
Removed because of ****ty q&a system...
Oh, and another thing I noticed: I get very randomly reboots, and every time the battery percentage drops massively. Just had a 30% drop. And after the reboot the battery percentage seems like frozen. Now I rebooted and plugged in the cable and got 44% again... No fast charging. Do that detection seems very off
Motorola forum isn't helpful at all. Clearing cache and dalvik didn't change anything and running around for a week in secure mode (that's how random they mostly are) or even doing a factory reset without restoring apps is out of question for obvious reasons.
That's pretty weird. Did you try a factory reset and after restore your apps? There's not a lot you can do if you're not rooted, but you shouldn't need to do much anyway on stock rom.
Only other option is full RSD lite OS restore as a last resort.
I am rooted for long, that's why I use Greenify. I know it also works without but then it's a joke. As RSD lite is, it just refuses for everyone to detect anything on Windows 10.
Factory reset is out of question for the moment, it takes way too long to do it properly (with titanium and NANDroid backup first) and I won't have that much time probably for the whole of this month. Otherwise I would most likely already have went off to the next best custom ROM since Motorola just can't get their **** together and still work on 8.0 in test for 2.5 month with searching testers for another one.
I think the next thing I'll do is to try the good old battery calibration, just have to find the file storing the statistics. I know many say that won't work but that's rubbish, it worked for me already a few times
Update: no, no change. Don't know if that funky battery percentage bug on random reboots still happen since I haven't had any again yet, but they come too random and unpredictable.
And that AccuBattery just proves to be worthless. It tries to estimate the rest capacity, but then it even fails to detect original capacity by 500 mAh. The battery sucker stats are also unrealistic. It puts chrome first with 10%, while GSam with root puts it 5th at 4.6% after kernel, Spotify, Android system and fight services. Android itself even puts it 9th with screen, phone idle, cell standby, Android OS and Bluetooth in-between.
So let's see what happens first. Motorola releasing 8.0, which I will flash through the .xml.zip, this time using flashfile.xml which should force a factory reset... Or me finding the time to switch to a custom ROM
Edit: so I got another one, bit this time no crazy battery drop. But the other times I killed of the soft reboot sequence because Magisk can have some problems with that. This time I didn't
Yesterday I was finally able to do the factory reset since those darn random reboots became too annoying and Moto's support is had just the most ridiculous ideas... In the worst way.
Either way, now OTA looks better, let's see how it will turn out in the next days