Related
I'm using a Nexus 5, its my first Android device, and so my first time rooting.
I rooted yesterday using the Android SDK, and installed TWRP.
The root worked perfectly, and I have tested it. All I have done since rooting (unlocked boot loader at the same time, so I'm clean on stock), is install a few Play Apps like Twitter, WhatsApp and then BusyBox and dSploit.
I haven't added any customisations or anything, and my battery is now awful!
i.imgur/AkdAKjW.jpg (Can't post links yet)
My screen has been on for 50 minutes...
I have brightness on the lowest setting, have turned off vibrate on touch, turned off Wi-Fi, turned off Location, set to use 3G not 4G, set display to turn off after 15 seconds...
Im sure it can't be anything to do with the root, but I don't really know too much about it. Is there a problem with 4.4.2 and battery life?
What else can I do to improve it?
Ideally I'd like to be able to have a max of 3-4 hours screen time, and the device to last for 14-15 hours.
I was easily getting 14 hours before I rooted/updated, but now my battery life has just screwed up.
Why is the OS using up so much?
7ewis said:
I'm using a Nexus 5, its my first Android device, and so my first time rooting.
I rooted yesterday using the Android SDK, and installed TWRP.
The root worked perfectly, and I have tested it. All I have done since rooting (unlocked boot loader at the same time, so I'm clean on stock), is install a few Play Apps like Twitter, WhatsApp and then BusyBox and dSploit.
I haven't added any customisations or anything, and my battery is now awful!
i.imgur/AkdAKjW.jpg (Can't post links yet)
My screen has been on for 50 minutes...
I have brightness on the lowest setting, have turned off vibrate on touch, turned off Wi-Fi, turned off Location, set to use 3G not 4G, set display to turn off after 15 seconds...
Im sure it can't be anything to do with the root, but I don't really know too much about it. Is there a problem with 4.4.2 and battery life?
What else can I do to improve it?
Ideally I'd like to be able to have a max of 3-4 hours screen time, and the device to last for 14-15 hours.
I was easily getting 14 hours before I rooted/updated, but now my battery life has just screwed up.
Why is the OS using up so much?
Click to expand...
Click to collapse
Is this not the first charge since you first saw the problem? The Android OS bug occurs sometimes. I would reboot and see how it is on the next full cycle.
sreen may be turning in coz some apps might be asking for root access.
I think you try greenify app and hybernate useless apps, m sure this will help you.
Really, it comes down to installing Xposed framework and Greenify.
Sometimes we need to be told straight up what works, and its installing XPosed Framework, and installing Greenify to identify what's waking up and consuming battery - and then telling Greenify to put it to sleep.
I'm doing this write up because it's something I know a lot of us are facing with our Relay's as they age and we try to stay current with new roms.
Like quite a few of us I've sacrificed battery life for an updated rom that looks decent and runs fast. Between builds and Kernels I was lucky to get through the day let alone to 24 hours without my phone needing a charge - even if I didn't play any games.
I tried flashing clean and not using titanium backup - didnt have any effect once I had the apps I desired installed.
I checked OS Monitor, wakelock detector, battery usage things, juice defender... nothing really extended or identified what he true cause, things said Android System UI or Display or Graphics was eating it all up. I started wondering if it was the latest roms with the transparent pull down notifications or the annoying pop ups that show you text messages and emails in the top foreground of the screen ..
Turns out for me, it was my "Transparent Weather Widget" I wanted something that showed a 5 day forecast and this sucker was DRAINING my battery.
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
This may be long winded, but its the steps we've all been mystified on why System UI or Display is the leading cause of battery use.. I think it has to do with the transparency of my widgets .. Food for thought if it helps others.
yohan4ws said:
Really, it comes down to installing Xposed framework and Greenify.
Sometimes we need to be told straight up what works, and its installing XPosed Framework, and installing Greenify to identify what's waking up and consuming battery - and then telling Greenify to put it to sleep.
I'm doing this write up because it's something I know a lot of us are facing with our Relay's as they age and we try to stay current with new roms.
Like quite a few of us I've sacrificed battery life for an updated rom that looks decent and runs fast. Between builds and Kernels I was lucky to get through the day let alone to 24 hours without my phone needing a charge - even if I didn't play any games.
I tried flashing clean and not using titanium backup - didnt have any effect once I had the apps I desired installed.
I checked OS Monitor, wakelock detector, battery usage things, juice defender... nothing really extended or identified what he true cause, things said Android System UI or Display or Graphics was eating it all up. I started wondering if it was the latest roms with the transparent pull down notifications or the annoying pop ups that show you text messages and emails in the top foreground of the screen ..
Turns out for me, it was my "Transparent Weather Widget" I wanted something that showed a 5 day forecast and this sucker was DRAINING my battery.
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
This may be long winded, but its the steps we've all been mystified on why System UI or Display is the leading cause of battery use.. I think it has to do with the transparency of my widgets .. Food for thought if it helps others.
Click to expand...
Click to collapse
Really good post, I can say I using 20140315 version (last working camera) and last kernel for it (don't remember the version) get really good performance and similar battery, using the same xposed
OmniToad now includes methods to turn off specific alarms and wakelocks at a lower level than greenify and/or Xposed.
Magamo said:
OmniToad now includes methods to turn off specific alarms and wakelocks at a lower level than greenify and/or Xposed.
Click to expand...
Click to collapse
You can try the battery performance already?
yohan4ws said:
I'm now running SlimKat initial build (Mar 15 2014) with Xposed framework, Juice Defender and Greenify. Everything is working perfect on my phone now. I keep checking in greenify and sleeping apps that don't need to be using any resources until I execute them. One item about SlimKat is you need to 2 finger pinch together the recent tasks to close all apps at once, other than that it has every feature I wanted, less annoying pop ups than the most recent KitKat's and my battery today - 50% after 14 hours. Usually at the most by a day like today I would have is 15% but more likely 6%.
Click to expand...
Click to collapse
What kind of wireless networks do you use throughout the day and what kind of screen on time are you juicing out in your 14 hours??
hbk.vix said:
What kind of wireless networks do you use throughout the day and what kind of screen on time are you juicing out in your 14 hours??
Click to expand...
Click to collapse
30 second timeout on the screen, i check it to read emails and texts, the odd phone call, sometimes i will run a wifi diagnostic for the networks i support using fing and wifi analyzer.. i keep my phone off and locked otherwise. in the car bluetooth is enabled. i was going wifi diagnostic yesterday when i got such great battery life.
today i have android weather and clock widget (cant recall the exact name) running w 3hour update .. after 8 hours i have 58% remaining, im in an area with horrible cell coverage , stats say 38mins screen on time.
there is nothing different of my usage over the passed cpl weeks, just enabling greenify and sleeping a voip app, facebook, google maps and the weather widget.
yohan4ws said:
there is nothing different of my usage over the passed cpl weeks, just enabling greenify and sleeping a voip app, facebook, google maps and the weather widget.
Click to expand...
Click to collapse
I'm using dashclock with 15min weather update, greader app with over 120feeds (aggregated in feedly) with 15 min update interval too and lots of other apps including the evil facebook+messenger. I switched recently from latest LiquidSmooth to Omnitoad and the result is I got the battery dropped by 9% overnight (10 hours) in idle mode.
Nota bene: without any tweaking.
I installed the Xposed framework and successfully used it to get rid of the "Just Once" app picker annoyance.
Edit: the play store has a Greenify which requires Xposed framework. Tutorial on Greenify use is on Youtube. Up and running now, but noticed that I am not getting a GPS fix now ever since the altrnt app picker MOD. It's always something!
Sent from my SGH-T699 using XDA Free mobile app
How can install xposed on cm 11?
subzerobob said:
I installed the Xposed framework and successfully used it to get rid of the "Just Once" app picker annoyance.
Edit: the play store has a Greenify which requires Xposed framework. Tutorial on Greenify use is on Youtube. Up and running now, but noticed that I am not getting a GPS fix now ever since the altrnt app picker MOD. It's always something!
Sent from my SGH-T699 using XDA Free mobile app
Click to expand...
Click to collapse
Hi! Do you have your relay with CM11 or stock ROM? I can't manage to install xposed with CM11. Thanks!
ninguno2 said:
Hi! Do you have your relay with CM11 or stock ROM? I can't manage to install xposed with CM11. Thanks!
Click to expand...
Click to collapse
I'd be curious to know too. I recently tried to install xposed again (last time I used it was probably a couple of years ago) on my Relay running the last official CM11 nightly, and it didn't work either. First the installer complained that xposed isn't compatible with my version of the Android SDK, but there is a fix for that (I forget where, but it is somewhere on XDA). But even when I applied the fix, it still failed, I started getting bootloops. So yeah, I'd love to know how to install xposed on the Relay too...
I have to say, I have been using my Relay more lately, as my main phone has been having some issues, and the main thing that keeps me from using it more is battery life. I'm not crazy about the screen, but I can live with it, and I have just about everything else running fairly smoothly - and the keyboard is just a joy to use. This thing is a real workhorse. But when the battery plummets down to ~70% or 60% within a couple of hours of use, that's just not cool...
cucumbers said:
I'd be curious to know too. I recently tried to install xposed again (last time I used it was probably a couple of years ago) on my Relay running the last official CM11 nightly, and it didn't work either. First the installer complained that xposed isn't compatible with my version of the Android SDK, but there is a fix for that (I forget where, but it is somewhere on XDA). But even when I applied the fix, it still failed, I started getting bootloops. So yeah, I'd love to know how to install xposed on the Relay too...
I have to say, I have been using my Relay more lately, as my main phone has been having some issues, and the main thing that keeps me from using it more is battery life. I'm not crazy about the screen, but I can live with it, and I have just about everything else running fairly smoothly - and the keyboard is just a joy to use. This thing is a real workhorse. But when the battery plummets down to ~70% or 60% within a couple of hours of use, that's just not cool...
Click to expand...
Click to collapse
Hi, i got it working with the files in this posts
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=210
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=209
I download both files, first I install the apk and got a bootloop, and then flash the zip from recovery. That fixes the bootloop and keep xposed installed.
ninguno2 said:
Hi, i got it working with the files in this posts
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=210
https://forum.xda-developers.com/showpost.php?p=72133164&postcount=209
I download both files, first I install the apk and got a bootloop, and then flash the zip from recovery. That fixes the bootloop and keep xposed installed.
Click to expand...
Click to collapse
So - install .apk, then flash the .zip - correct? And xposed is working well now for you?
[EDIT] So the .apk you posted worked just fine for me, no need to flash the .zip! Odd, but grateful this worked. Thanks!
Just wanted to confirm: Greenify (root) + Greenify xposed module + Amplify xposed module make a huge difference. Battery lasts much longer, and I have this sneaking suspicion the phone is generally smoother and less laggy. Might well be placebo, I know, but with useless background processes being sht down it might well have an effect on performance...
cucumbers said:
So - install .apk, then flash the .zip - correct? And xposed is working well now for you?
[EDIT] So the .apk you posted worked just fine for me, no need to flash the .zip! Odd, but grateful this worked. Thanks!
Click to expand...
Click to collapse
Great! I don't know why, but i had to flash the second one too.
Could you tell me which options have you check in Greenify and Amplify with xposed to get better battery life?
Thanks!
Greenify: Root mode + Xposed, of course. I've got automatic hibernation set, and for xposed features, I set all of them except Deep Hibernation
Amplify: even just selecting the default wakelock blocks in the free version helps a lot, but I use the paid version and I limited just about every wakelock that the app said was safe to limit (but only ones that were also described as safe in their blurb - some in the "safe" list are described as "we don't have any information for this wakelock yet") except for a few that were really light wakelocks.
Before I begin I just want to say that I have been using Android for a while and understand wakelocks etc. I have already made sure none of my apps are causing wake locks by uninstalling them but it has made no difference.
Here are my GSam screenshots: http://imgur.com/a/1Cp9z#0
As you can see, Android System and Android OS are the culprits that are draining my battery, but the phone isn't "awake" when they are draining it, so I am not quite sure what is happening. There is no wake-lock but there is a lot of CPU usage for some reason,
Please ignore the average times shown by GSam at the bottom, I get nowhere near 5hrs screen time, I reset the histories yesterday so its not yet calculated average properly yet.
I have tried - Stock COS11S, the latest COS 12.1 and also CyanogenMod 12.1 nightlies and the recent snapshot and they all exhibit this issue even with no apps installed. Is there a ROM out there that has no issues with this stuff?
Thanks!
Same problem. No idea the solution. No matter what battery app I use to try and tell me what is going on, it's always just listed as "android system" or "system" that is draining battery. I didn't have this on sultan's build so I guess it's back to that.
I dont want to give yo spoilers...
you can try every rom here, every kernel, every mod...
it really up to your personal use... you do this 3 simple things and like me will reach 5, 6 hours SOT.
disable lte and go for EDGE
restrict privacy guards things on apps: keep awake, auto start, wake up... on every app you install
use your social network on browsers... installed apps use background...
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
TheHighLife said:
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Click to expand...
Click to collapse
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
lotherius said:
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
Click to expand...
Click to collapse
You don't need to downgrade TWRP to flash a modem. You can very easily flash a modem without TWRP even installed; fastboot. It isn't even certain that the modem is causing this drain either.
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Roughy said:
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Click to expand...
Click to collapse
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
f41lbl0g said:
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
Click to expand...
Click to collapse
Correct, with the Xposed Mobile Radio Active fix applied.
bacon_firmware_update_2015_04_03.zip from ... <10 posts and am not allowed to post links yet.
It's on Exodus' 5.0.2 download page along with the roms.
As usual the modem will not flash in TWRP, and has to be done manually via fastboot.
Paresh Kalinani said:
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
Click to expand...
Click to collapse
I did all of this but it's still draining battery, should I post new screenshots?
TheHighLife said:
I did all of this but it's still draining battery, should I post new screenshots?
Click to expand...
Click to collapse
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Mr hOaX said:
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Click to expand...
Click to collapse
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
TheHighLife said:
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
Click to expand...
Click to collapse
Boot your device into safe mode https://support.google.com/nexus/answer/2852139?hl=en
Just post some screenshots of the battery (complete overview of graph screen and app list screen) after using your OPO in safe mode atleast for one charge cycle (90%+ down to 10%)
This will help us to figure out what is the exact issue you are facing.
If you are not interested in troubleshooting, just flash fastboot images of this build(CMOS12.1) using following guide
forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
For OnePlus One, about a month ago after systems update, my battery started draining fats and it has gotten worse over the past week. The battery barely holds four hours of after a full charge and the phone gets very hot. Also, over the past week, my main SMS messaging app (SMS) crashes nine out of 10 times -- I can start the app but when I click any of the messages I was to read or type, it freezes and crashes. Also, since yesterday, my phone dilaer crashes very often. Any thoughts/help? I am not familiar with how to flash ROM, etc. Also, since yesterday, charging has been very slow -- overnight, the charge went from 35% full to 74% full. I tried safe mode as well and no luck -- battery still keeps draining at 1% every three minutes.
I have the same issue. Any fixes which work ?
I'm not sure if it's more appropriate to post here
or on the custom ROM forum itself, but here's my battery issue:
Issue: Abnormally fast battery drain. My battery would
be fully charged, and almost immediately start draining until
it'd show 1% within 2 hrs. Screen would be off mostly (normal
use).
Been on a custom ROM since January 2017 (crDroid) and have had no problems with it since,
except 3 days ago, when the problem first appeared.
Things that are ON: LTE data (or Wi-fi), Auto apps update on
Google Play Store (never been problematic before), Location,
Things that are OFF: Bluetooth, ScreenCast, Caffeine
When I check Battery in Settings, the numbers don't add up.
I'd have battery indicator at 70% for example, but Screen,
Android System, all other apps would add up to only 7%. So
that's a whopping 23% unaccounted for.
But here's the weird thing: it drains fast until 1%, then at 1%,
the phone is supposed to initiate automatic shutdown like it has before.
When this issue cropped up, the phone keeps going for about 6 hours
or so before shutdown is started. Checking Kernel Adiutor occasionally,
I'd see a much slower decrease in voltage which probably reflects
more accurately the power drawdown situation.
Things I've done:
-clear cache (both through File Explorer and TWRP Recovery)
-clear batterystats.bin
-calibrate battery after full charge/discharge (via Root Essentials,
which basically does the same thing as manually deleting batterystat.bin,
if I'm not mistaken)
-Resetting App Preferences via Setting/Battery
None of the above has worked. Any idea what might be wrong?
My device is a Zuk Z1, with a 4100mAh battery. It usually lasts me more
than a day on normal use, but as the attached pic shows, it's at 96%
yet without having used any apps yet, has only 2 hrs of juice left.
I've tried reflashing my ROM, wiping everything including formatting data
yet nothing has worked.
I'm a light user, as I don't play games or watch videos on my phone.
Neither do I use graphics-intensive apps. I haven't used processor-intensive apps
that require constant GPS (like Google Maps, Waze) since then.
Borat38 said:
I'm not sure if it's more appropriate to post here
or on the custom ROM forum itself, but here's my battery issue:
Issue: Abnormally fast battery drain. My battery would
be fully charged, and almost immediately start draining until
it'd show 1% within 2 hrs. Screen would be off mostly (normal
use).
Been on a custom ROM since January 2017 (crDroid) and have had no problems with it since,
except 3 days ago, when the problem first appeared.
Things that are ON: LTE data (or Wi-fi), Auto apps update on
Google Play Store (never been problematic before), Location,
Things that are OFF: Bluetooth, ScreenCast, Caffeine
When I check Battery in Settings, the numbers don't add up.
I'd have battery indicator at 70% for example, but Screen,
Android System, all other apps would add up to only 7%. So
that's a whopping 23% unaccounted for.
But here's the weird thing: it drains fast until 1%, then at 1%,
the phone is supposed to initiate automatic shutdown like it has before.
When this issue cropped up, the phone keeps going for about 6 hours
or so before shutdown is started. Checking Kernel Adiutor occasionally,
I'd see a much slower decrease in voltage which probably reflects
more accurately the power drawdown situation.
Things I've done:
-clear cache (both through File Explorer and TWRP Recovery)
-clear batterystats.bin
-calibrate battery after full charge/discharge (via Root Essentials,
which basically does the same thing as manually deleting batterystat.bin,
if I'm not mistaken)
-Resetting App Preferences via Setting/Battery
None of the above has worked. Any idea what might be wrong?
My device is a Zuk Z1, with a 4100mAh battery. It usually lasts me more
than a day on normal use, but as the attached pic shows, it's at 96%
yet without having used any apps yet, has only 2 hrs of juice left.
I've tried reflashing my ROM, wiping everything including formatting data
yet nothing has worked.
I'm a light user, as I don't play games or watch videos on my phone.
Neither do I use graphics-intensive apps. I haven't used processor-intensive apps
that require constant GPS (like Google Maps, Waze) since then.
Click to expand...
Click to collapse
Have you tried flashing another ROM/going back to stock?
Freewander10 said:
Have you tried flashing another ROM/going back to stock?
Click to expand...
Click to collapse
Not yet. Am going to try an AOSP-based ROM later.
I've been deleting apps piecemeal, but have faile to pinpoint the culprit.
I have almost come to the conclusion that it's the ROM that's problematic.
But if that were the case, why haven't I had the same problem since
when I first flashed this custom ROM months ago;
and why is the problem reappearing when that same ROM is re-flashed now?
OK, I've flashed 3 other ROMs: Citrus-CAF, NucleaROM and stock, and the problem persists.
By doing the above, I've crossed out the possibility of it being the ROM. Neither is it the battery
itself, because it would've shut down by itself at 1%, yet at 1% I can last 6 or 7 hours of light use.
Anyone out there have any idea?
If you get the same results, the battery is trashed. Is it aftermarket?
WestCoastSunset said:
If you get the same results, the battery is trashed. Is it aftermarket?
Click to expand...
Click to collapse
The battery? No, it's the factory original.
It would not be unusual for a battery to fail in a month or two. I've had that happen to a couple laptops where I work.
WestCoastSunset said:
It would not be unusual for a battery to fail in a month or two. I've had that happen to a couple laptops where I work.
Click to expand...
Click to collapse
That would be pretty unusual for reputable companies. If ever it did happen in my case, perhaps it's a lemon batch.
Sadly, I bought this without warranty.
Not really, happens all the time in laptop world. Even with oem batteries.