GSam stopped working properly (also BetterBatteryStats, Wakelock Detector lite) - General Questions and Answers

I got a new Motorola phone (running Android 7.0) a few weeks ago and installed GSam on it, including giving it BATTERY_STATS permission via adb. It all worked flawlessly for maybe 2 weeks. But, after last time I charged my phone, no matter what I do it behaves as if the BATTERY_STATS permission is gone. That is, all app usage is grouped together, and it has no info on wakelocks, sensors, etc. I see a similar behavior (e.g. no stats info whatsoever) on other apps: BetterBatteryStats and Waklelock Detector Lite that used to work fine, but now have no stats.
What I've tried:
1. Rebooting the phone several times - no effect
2. Clearing cache - no effect
3. Re-granted permission via adb just in case.
4. Used a 3rd party app (Permission Dog) to check that those apps actually have BATTERY_STATS permission - they do
This happened once before where after charging my phone there were no stats / GSam behaved badly, but then it recovered after rebooting. Has anyone else run into this? Any idea why it's happening / how to fix it? Thanks!

Related

[Q] Battery Drain while not using the phone

I have got a battery drain issue with my nexus s I9023 working on android 4.1.2 default factory image , no rom no kernet edited
While sleeping in 6 hours battery Drain down from 55% to 5%
The was the last day , I have this issue over two weeks ago , I have used BetterBatteryStats trying to find the process causing that ,
and I found the suspend backoff process cause that , I have changed the wifi with a static IP instead of a dynamic one and the problem still there
any suggestion ?
And thanks in advance for any help.
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Oogway13 said:
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Click to expand...
Click to collapse
Mine does it with wifi off and fresh reboot not opening any apps. I seem to get between 4 hours and 12 hours of lifetime from 100%. I should be upgrading this year but it would be nice if someone could figure this out because I know I am not the only one having an issue.

Oneplus One - Poor battery

Hi guys,
I got a really annoying issue with my 1+1, got my phone for 2/3 months.
I did already a lot to fix this issue but couldn't find a fix.
Battery status: battery savings..
Pics:
http ://imgur.com/a/dMmVb
Does anyone know a trick to fix the android system draining bug?
Your screenshots show absolutely no information. You need root and one of the following apps,
- BetteryBatteryStats
- GSam
- Wakelock Detector
Root required. From that point on, you'll know what app is causing your battery to drain via partial wakelocks and alarms.
Have you tried a fresh stock install of 38 r? Ota seems to result in poorer performance. Assuming your using 11s?
Disable "wake lock" and "stay awake" in Privacy guard to Google play services.

Android OS consumes my Mate's battery! Wakelock problem [screenshots].

Hi Guys!
I need your help. My Mate 8 (model NXT-L29 on custom ROM no. NXT-L29C432B192) makes me crazy because of battery drain. The problem is unknown for me. I've tried almost everything: turned off WiFi and BT scanning, turned off sync and backup of Google account, hard resets (via hidden menu). I even logged in via different e-mail - nothing has helped.
Generally I know only that it's connected with Android OS and Android System services - it shows me the default Huawei management app. Both of them can consume more than 1000 mAh of my battery! It's crazy! The phone is constantly awake.
I don't have root, but I decided to install Wakelook Detector [Litle] to access more sophisticated data. I assume that the problem is process PowerManagerService - just have a glance at provided screenshots. It's running more than 17 hours !
Please help me! I don't know what to do. My best SOT was 7,5 hours on WiFi without any hardcore apps like 3D games. In such conditions I should achieve circa 10 hours on Mate 8, but because of the battery drain it can't.
Thanks a lot and happy new year for all folks!
i had this problem a few days ago with the "adroid system" process. i unchecked almost all apps from autostart, and made only 2 exceptions (whatsapp and viber) for doze. And only 5 protected apps.
finally i rebooted my phone holding the volume up button, entering recovery mode. there i cleaned the cache and rebooted again. that fixed it for me.
My experience is, that the more protected and doze exceptions for apps you have, the more your phone get's unreliable.

[Q] Weird Battery Drain + Indicator Problem

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.

Android O and BBS (or wakelock detector)

Does BBS or wakelock detector not work with Android O? After giving the app root permissions and letting the phone sit for a few hours, it isn't finding any partial wakelock data.
BetterBatteryStats 2.3 (beta, currently 2.3-109) works for me on my Pixel XL (on Fi) running OPR1.170623.026, rooted with Magisk. It's said to not require systemization anymore, but I have it systemized anyway (systemlessly, with Magisk, via Terminal App Systemizer and Privileged Permission Whitelist). For full effect, it requires doze whitelisting, as it always did. As far as I can tell, SELinux Enforcing mode is said/suspected to interfere with some BBS stats, so I'm using the SELinux Permissive Script (Magisk module) until/unless I find out otherwise. The BetterBatteryStats forum thread is very active and contains loads of info related to troubleshooting and making use of the data.
BetterBatteryStats 2.2.2.0 doesn't work. I believe this is (at least in part) because it can't handle the large size of the battery info packets that it is fed by the system's battery info service.
Wakelock Detector Full 2.0.4 doesn't work for me. I've tried setting it up essentially the same way as BBS (altering its privileged app permissions to suit it). It recognizes that it's a system app, but its stat pages are all blank and a toast that says:
Failed to perform this task at the moment, try again later
Click to expand...
Click to collapse
Its forum thread is much less active and contains no mention of Oreo.

Categories

Resources