Quick reminder that a complete power down is sometimes required to fully 'reset' a 3rd gen HDX ... especially radios, sensors and some kernel related issues (eg: restore default governor tunings).
A recent trouble shooting exercise involving unexplained battery drain served as a potent example. Performed numerous full (vs hot/soft) reboots over the course of several days chasing a zombie battery drain. Eventually powered down for 5 sec and restarted which full resolved the issue. I have had similar experiences with TWRP where some actions could not be performed until the device cold booted into recovery. YMMV.
Related
Does anyone know if it is still necessary to power off Android then restart instead of rebooting from Android? A while back it was suggested that we power off instead of reboot to reduce high battery drain. I haven't seen this discussed in a while and I'm curious if it is still an issue.
I always reboot from Android instead of switching off.
Done it alot of times, seen no difference though.
It doesn't matter. It wasn't an issue just a precaution. Have fun
I did some searching and reading and only found speculation on this subject, and during the holidays I have been mostly desk-bound at my home office with very little phone traffic, so I thought I'd post my results after doing some testing.
For those who don't want to read, the bottom line is, if you swap batteries, (especially using batteries of different capacities) I believe you definitely should wipe your batterystats.bin file each time you swap them if maximum runtime is your goal.
Why did I question this in the first place? I saw a dev post a comment that the battery drivers do not reference this file at all. I wasn't able to find any clear explanation of what is actually in this file. I'm running Nero v3 with Voodoo, and after I flashed it, my fully-charged stock battery only lasted about 45 minutes. All these things made me wonder whether it made a difference, and since my previously-fine stock battery suddenly wouldn't last an hour, I had to do something anyway.
For test purposes I attempted to eliminate as much random activity as possible. I shut down my e-mail client and data sync and forwarded my cell calls to my home office land-line. I'm in the camp that believes (from experience) that a good strong WiFi signal to the closet ten feet away uses far less juice than trying to maintain radio contact with a cell tower 2 or 3 miles away, so in this case I switched off WiFi to ensure *faster* power usage. I didn't want to do a crazy-fast maximum-extreme battery drain, though, so I found that streaming radio at full volume using TuneIn resulted in noticeable drain, but also surprisingly extended runtime. I made sure the phone was in the same physical location for the duration. (I know there are still a million-and-one variables at play, but I believe the "big picture" conclusion is valid.)
The battery I'm referring to as G9 is the original "good" battery that shipped with the phone. The G7 batteries are those cheap Chinese knock-offs, the ones with the duplicated serial numbers. These have very different capacities. I believe the G9 is 1500mAh and the G7 has been estimated at 700 to 900 (it is marked as 1200 but this is clearly false). I have two G7s. All batteries were fully charged on an external stand-alone charger. The batterystats.bin file was wiped using Clockwork Recovery. I ran the application with the display off, only turning it on about once an hour to check the battery level. I let it run until the phone shut itself down.
First test:
Install G9, wipe stats: 7 hours 14 min to shutdown
Install G7 #1, no wipe: 4 hours 2 min to shutdown
Install G7 #2, no wipe: 4 hours 4 min to shutdown
Install G9, no wipe: 6 hours 59 min to shutdown
Second test:
(I already saw [above] what the G9 does with a clean wipe)
Install G7 #1, wipe stats: 5 hours 31 min to shutdown
Install G7 #2, wipe stats: 5 hours 27 min to shutdown
As an aside, I'm pretty surprised that playback of streaming-data radio at full volume will last more than 7 hours. I figured I might get 3 hours or so. This suggests to me that both the phone hardware and Android itself is actually very power efficient -- streaming radio is not exactly optimized for power saving, and the stock speaker is quite loud.
Since the phone actually shuts itself down -- it doesn't simply bleed the battery dry until it just dies from power-loss -- I suspect it uses this data to profile how the battery drains to predict when it will become nearly depleted so that it can perform a clean shutdown. And swapping batteries with very different "behaviors" simply throws that off completely. You can see I got a full hour and a half more out of my G7 batteries just by wiping, and my G9 lost about 15 minutes of uptime after the stats were "contaminated" by a pair of G7 runs. I also thought the consistency of my back-to-back G7 runs was interesting.
The probable (and unavoidable) downside to frequently wiping your battery stats is that it also probably defeats any long-term battery management strategies designed to extend the life of your battery. You see this kind of thing most obviously on laptops where the battery management software intentionally runs on battery power even when you're plugged in, letting the battery drain to some point based on the software's evaluation of your battery's health before allowing it to charge again. I'm not sure if Android or the Vibrant does this, but it seems likely it does based on people's complaints about things like the "15% charge drop" issue when they unplug from the charger or USB.
It doesn't appear that our batteries have electronically-readable serial numbers, and I have to assume knockoffs like my G7s wouldn't bother to implement those correctly anyway. But optimally we'd have different profiles for different batteries. Maybe in Galaxy's successor...
Why doesn't the driver reference batterystats.bin? I don't know, but what would be interesting is to scan the released source to see what DOES access it. I suspect it also tracks all that other power-related data (like the detailed battery history information in the *#*#4636#*#* menu), and so I further speculate the file is managed by some centralized logging-style interface, and the battery driver is just one piece among many which communicates with that interface. But I've never bothered to actually grab the code from Google and that's nothing but pure speculation.
Anyway -- wipe it when you swap it.
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.
Battery issue, just replace it
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
I guess you have bad habit of charging your phone when it reaches to 5-6%? Am I right? If not and you charge your phone in a healthy basis, then I guess change the ROM or re-flash it. It might work. Or else replace the battery.
I've posted in the Android General Q&A and
in the custom ROM forum itself, but have gotten no responses.
A search on XDA and other sites yielded nothing similar to my issue, so here—
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.
EDIT: 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?
Borat38 said:
I've posted in the Android General Q&A and
in the custom ROM forum itself, but have gotten no responses.
A search on XDA and other sites yielded nothing similar to my issue, so here—
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.
EDIT: 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?
Click to expand...
Click to collapse
Try XOSP. was very good by tech mashido for battery.
And 1% don't last that much. It's a long prediction.
hardikkchavda said:
Try XOSP. was very good by tech mashido for battery.
And 1% don't last that much. It's a long prediction.
Click to expand...
Click to collapse
What exactly do you mean by "long prediction"?
Borat38 said:
What exactly do you mean by "long prediction"?
Click to expand...
Click to collapse
For me 1% never stayed for less than a min.
Hello,
I had an exynoss note 4 for over 3 years now and was always happy with it.
Recently I started to feel the phone getting hot and battery is not lasting as long as before (this battery was bought last year).
I checked with CPU Z and the exynoss was reaching 57 degrees just by scrolling in different screens like home and chrome.
What do you think the issue might be ?
Boot your device into Safe Mode and see if that still happens. If it doesn't then a rogue app is using all the resources on your device.
Try wiping the cache partition in Recovery Mode and performing a hard factory reset.
Mine was messing me about earlier this year, did a factory reset and clean setup - back to like-new! You may also need a new battery, but I'd try the factory reset first if the battery is a good one and only a year old.
could be emmc fault this is how it normally starts. battery drain and the issue you have.
Here is a video showing how to fix emmc fault.
https://www.youtube.com/watch?v=jLPHWtb0StI