yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] bugsaci:
Can someone please help me and tell me is there something wrong with my phone?

Im using hyperdroid rom v6 with redpill kernel v1.3 and DXKL1 modem (coz im living in dx region modem type).

I did change my modem to DXKG1 and DXKI1 but both give me same result :(

My phone connect to 3G/H+ daily without auto snyc on.

I dont see anything weird with betterbatterystats but my phone awake almost nearly 3 hours when i dont use it since im sleeping :(

I have 3 email account but i think its not a problem since i turn off the auto sync configuration.

And i got 1 weather and 9s weather installed with 12 hours auto update on.

Thank you and sorry for bad english :(
[BetterBatteryStats] jeremysherriff:
Go SMS seems to do the same, and the "notification light" part of Go SMS isn't better either ;)
[BetterBatteryStats] Alucardis666:
Here's my latest dump... battery is terrible!

Some one please help me...

https://docs.google.com/document/d/1BxNdtOAdgVzlI4z08BKqcYR2vX_keffnhAb_QkAlWPc/edit

Here's a thread where I'd like all responses to be sent please.

http://xdaforums.com/showthread.php?p=22897669#post22897669

Thanks!!!
[BetterBatteryStats] jeremysherriff:
OK I had a look at the thread you insist we post in. Have you carried out the suggestions?

Anyway, the issue seems reasonably obvious to me, but the app itself responsible isn't obvious. You're going to need to do some work to resolve this.

One of your apps is posting a notification - either a notification icon, or notification lights - that is stopping your phone going to sleep. Given that you have so many apps doing background activities, it's up to you to figure out which one it is. I would start by disabling notifications in facebook, and I think also Titanium Backup (are you doing automated app backups using TiBU?). But from experience, the app is likely to be your SMS app - for some reason, they have a bad rap for draining battery once a message is received but not read. Go SMS and Handcent both do this depending on configuration and random ROM/kernel/karma combinations.

Anyway, it's not kernel, it's a userland wakelock.

For your next BBS dump, do what we keep telling other people to do - charge the phone before going to bed, remove from charger, and leave it idle for a good number of hours. Then take a BBS dump with the view "since unplugged". Do this because there is little value trawling through a log that shows you normal work-day activities.

Cheers

---------- Post added at 08:22 PM ---------- Previous post was at 08:06 PM ----------

Hi dude

Suggestion: disable or remove whatsapp unless you are getting a lot of value from it - it often causes your phone to wake up. Your Whatsapp reading isn't bad, so you might not see any improvement from this.

Most likely, your issue is fast dormancy:

Kernel Wakelocks
================
"svnet-dormancy" (): 2 h 18 m 58 s (8338 s) Cnt:(c/wc/ec)1273/0/1272 11.5%
"svnet" (): 58 m 12 s (3492 s) Cnt:(c/wc/ec)4325/0/4326 8.4%
"radio-interface" (): 31 m 30 s (1890 s) Cnt:(c/wc/ec)2380/0/0 4.5%

Google to find a way to disable it. Someone may be able to post a link?

Can I ask that you if take another reading and post it, the reading should just be of the time when you are asleep. The best way to do that is: Charge the phone before you go to sleep. Unplug it. Sleep :). Check BBS in the morning, set the view to "since unplugged", and export the dump file.

Reason is that your usage is clouded by your gaming and daily use.
[BetterBatteryStats] noke955:
Just dial *#9900#
[BetterBatteryStats] look2:
Here's a link to the post with the ststus dump.

http://xdaforums.com/showpost.php?p=22781192&postcount=3413
[BetterBatteryStats] jeremysherriff:
Dude what email app is that? It's killing you!
[BetterBatteryStats] look2:
Yeah, I know, it sucks. it's the built in client from samsung orginal ROM, 2.3.5 using it for active sync. None of my co-workers have this problem, and i was woundering if there is a solution to this problem, because it's the orgininal app, it feels strange if it's only me having the problem.

But i'm not realy sure if it's the email client it self, or if it is the active sync that drains the battery. Is there any other good email clients for active sync? It would be nice if it supported GAL (Global Adress List)
[BetterBatteryStats] jeremysherriff:
I use Touchdown for Exchange, it's not pretty and you need to get used to doing things its way, but it works. I don't use push mode, it is supposed to support the newer C2DM battery-friendly push mode but I still find it drains too much. I sync every 30m instead.

30-day trial in the market. I've also heard good things (as well as bad things) about RoadSync.

Edit - first things first - delete the account, then clear the cache/data for that app. Recreate the account and set it up right from the start with a sync schedule rather than push mode. Make sure you clear the app data though, that's important.
[BetterBatteryStats] look2:
So you think it's the app, not the sync that's the issue here?
[BetterBatteryStats] nola mike:
Yeah, that's why I haven't used either recently. Especially using the lineage privacy guard I thought gave me much of the same functionality of greenify. I'll reinstall. Google always seems like the biggest culprit no matter what. Holy grail has always been to slow google's roll...

Ha ha, isn't that the truth.

What were you looking at for lonelycatgames that was excessive?

And was I correct in where I was looking at dropbox use?
[BetterBatteryStats] vasujahagirdar:
thanks fort reply,

I couldn't post ideal dump, because of some reasons. I'm only interested in that report _wake_lock issue!! Reason for it. Thought this random dumpfile is sufficient! Can anyone through light about it?
[BetterBatteryStats] pjadec:
Kernel doesn't let it go sleep. Try different kernel or wipe cache/dalvik cache and reboot. Something is wrong, but dump file is no good for info
[BetterBatteryStats] DB126:
Greenify and Privacy Guard are very different in operation and objectives. You can't substitute one for the other beyond broad statements.

I don't break down app/service usage or define "excessive" beyond an overall characterization of device performance. That's for you to determine. I simply point out a few potential (operative word) culprits for consideration. Also not interested in numbers optimization game. Your device is fine. If you want to take it further you're gonna have to start throwing breakers to find the faulty circuit(s). Not worth the effort IMO unless there are other symptoms beyond those reported. Good luck on the deep dive.
[BetterBatteryStats] mrjuniork:
How is auch a low idle drain not sustainable? 2 percent in almost 8 hours is pretty impressive, isn't it? And I'm also wondering how this low idle drain is even possible with 8 hours of poor signal?? :confused:
[BetterBatteryStats] hd-patsan:
Sorry to answer so late - thanks again and to be honest I'm not sure what actually had changed on my phone (I followed your advice along with other ones) mostly, but I think all of my actions which was guided by such kind people as you and other guys helping here at least have had their positive effect on battery drain :) Actually I still have the lack of deep sleep problem (it's better now though - 2-3 mins of DS instead of 2-3 sec :D), but it doesn't bother me like it have been doing a week ago, because:

1. I'm almost satisfied with my battery drain level. My phone stays on for one day in my using style, which I find enough (anyways I will be glad if I can even improve it);

2. Now I know that I did a lot with all of these GP services, GeoLoc. services, and other things I've turned off (or not quite, it depends), so thoughts like "you could use it better way and do something to improve it at least" doesn't pursue me anymore. Not that strong at least. And even though I don't have these 0.2% per hour drain that people over here are discussing I'm not actually disappointed.

I wrote a lot, despite my poor english level. Well, I hope my spelling wasn't too bad and everyone got me right :)
[BetterBatteryStats] DB126:
Exactly. Which is why the reported drain rate is likely an anomaly vs. a reproducible event. Typical range for a device of the poster's type/caliber with a well-behaved app portfolio is 0.4-0.8%/hr with mean closer to 0.7%.
[BetterBatteryStats] peterlee928:
glad to hear that the issues have been mitigated! dont worry too much about 0.2%/hr - i definitely dont get those (and likely many others dont either without doing a lot of reconstructive surgery to their phone). but ok, so i dont save maybe 1% when i turn back on my phone? no big deal :)

and that 0.2%/hr can be misleading - sometimes, there can be a flood of wakelocks that occur once those phones are turned on (think water trying to burst out of a dam, then you open the dam... then water comes flooding out). and then the battery life can drop dramatically and quickly after you start using it. not much better, right? so the "real" number may not necessarily be 0.2%/hr anyways!

in any event - as long as your idle time is within a reasonable range and your phone works as you want it to, then life is good :) :good:
[BetterBatteryStats] TNSMANI:
That is the correct attitude.

On Android 7,8 and 9, the best I have seen, without affecting functionality, is 0.3 to 0.4% per hour. The average I have seen is around 0.6 to 0.7% even without any apps to contain the villains. The only condition is that you choose well behaved apps for your portfolio.

Enjoy your device!
[BetterBatteryStats] vasujahagirdar:
Hi it appears latest face book update causing the battery drain! Not allowing the device to sleep. This causing report _wake_lock!! I freezes facebook, drain stopped!!
[BetterBatteryStats] DB126:
Official facebook app is a known 'bad actor' when it comes to power management. Try a 'lite' alternative such as the aptly named Facebook Lite.
[BetterBatteryStats] nola mike:
2 more nights. First one with no deep sleep = 1.1% drain, another with deep sleep = 0.5%. I'm going to take some daily logs for a couple of weeks to see if the readings stay consistent. The non-sleep log showed high sensor use again (though it doesn't always). I froze my pedometer app and it's been sleeping since, so we'll see.
[BetterBatteryStats] lazostat:
<<- adjust from/to references to 'screen off' and 'screen on'>>

How can I do this?
[BetterBatteryStats] DB126:
Use the method outlined in the OP.
[BetterBatteryStats] lazostat:
I don't understand how to do this step..
[BetterBatteryStats] Oswald Boelcke:
Slightly modified quotation from OP:

I hope the screenshots are sufficiently helpful to follow.
[BetterBatteryStats] lazostat:
Now i understand my friend. Thank you!
[BetterBatteryStats] ismtor94:
version 2.2.2.0.apk reporting 2 positives at virustotal instead of 1 as the older versions. Why is that?
[BetterBatteryStats] strongst:
Just ignore it...
[BetterBatteryStats] KidWave:
Hi all, was hoping someone could take a look at my battery log/dump (attached as .txt) and let me know if there's a rogue app or setting I need to adjust to get my previous battery life back?

User Profile

Device: Original Pixel (Sailfish)

Typical Battery Life: 4-5 days normal usage

Typical Usage: Extremely light usage. Basically used for notifications, email, and light Maps/browser usage when on the go (which is rare ...). This usage and battery pattern was consistent throughout Nougat and even through Oreo OTA upgrade. No factory resets/flashing stock images for 2 years, everything was great.

What changed: Pie OTA upgrade. Battery life tanked to barely getting to 2 days with the same usage.

I gave it a couple of cycles to see if the new "Adaptive Battery" feature needed to settle in, but it never improved. Went ahead and factory reset, but no improvement. Proceeded to the full flashing of the stock Pie image and only re-installing about 50% of the apps I previously had, but no improvement. Tried disabling "Adaptive Battery" ... no changes.

I'm now at the point where I've factory reset again and the only non-Google apps I have are the bare necessities (Calculator, Gallery ... So no Google Photos Sync, Ruler Measurement App, Yelp, and randomly needed to install the Panera app to claim a reward).

Is there anything in the log pointing to something that's causing battery drain? Thanks in advance for any info you can provide!
[BetterBatteryStats] strongst:
There are some issues related to health services. Are you using apps for health?
[BetterBatteryStats] KidWave:
Nope, never used any health/body monitoring apps ... I don't even have the stock Google one installed (is it Google Fit?)

Is there anything in Android settings I could turn off to disable health services/monitoring?

edit: after googling "android health services" ... https://www.androidpolice.com/2017/...device-health-services-system-app-play-store/

wait, so is it actually the new battery menu/app causing the drain?
[BetterBatteryStats] strongst:
Don't know which apps pie ships with. But line 83-85 and the process is mysterious :rolleyes:
[BetterBatteryStats] peterlee928:
assuming your phone is rooted, you can try freezing that app. then do another idle dumpfile and see if that guy is gone. :)
[BetterBatteryStats] DiamondJohn:
Not that anyone was following my results, but I ended up finding that it appeared to be something in my boot scripts (for which I have many) was somehow causing it to not enter doze. This was confusing as these same boot scripts have been running on my previous devices without issues. I was basically triggering them using Magisk (v17) in service.d. And by something, I mean any script I ran.:mad:

I tried freezing all my 3rd party widgets & apps to no avail.

I moved the script that then triggered all my other scripts (>10) into post-fs-data, and now my phone is more than happy to enter doze:victory: I have no idea why this step makes a difference, but it does :highfive:, and it has "fixed" it, so for now, I'm happy.:good: thanks for every-ones help.

FYI: simply testing for just over an hour gave me less than 1% drop
[BetterBatteryStats] kamilmirza:
v2.4-262 does not show any stats and shows

"Detected problems with API compatibility (visit g.co/dev/appcompat for more info)"

in-app App Permissions show all GRANTED

tried multiple reboots and clearing app data

1+3 Havoc v2.0 (Pie) ROM, permissive kernel, supersu access granted
[BetterBatteryStats] underskyzx:
Why isn't my device going into deep sleep?

Everything seems fine I think?
[BetterBatteryStats] TNSMANI:
The dump is too short for coming to any firm conclusions. Please post an idle dump for atleast 6+ hours.

Your wifi and mobile data were alternating which indicates an issue with your router. Background downloads were also happening. Still, your drain was 0.0% only.

Don't worry about deep sleep if your drain is less than 0.7% per hour (during idle), as turning dials and knobs blindly in order to increase deep sleep will result in additional drain and may also cause other unintended issues.
[BetterBatteryStats] underskyzx:
I had this option unmarked developer options, I enabled again let's see what's happens
[BetterBatteryStats] TNSMANI:
That will not stop the switching back and forth. It will make the transition quicker, that is all. It is the router that you have to check.
[BetterBatteryStats] underskyzx:
Can you tell how you come to this conclusion please? The router is indeed having issues, when I copy files from PC to the phone via SMB (Solid Explorer app) I can see the transfer rate going up and down constantly, also both iPhones of the house (mom & dad) keep getting disconnected.

I ask how you come to this conclusion because it may help to argue with my ISP.

Probably won't, they won't understand and it will take a month to get the router changed but I have to try :silly:
[BetterBatteryStats] rashidramli:
Hello,

May i know what app is causing this c440000.qcom,spmi:qcom,pmi8998@2:qcom,qpnp-smb2 wakelock?
[BetterBatteryStats] githyanki:
ISP routers are almost always crap. Buy a good one, hook it up and turn off the WiFi on the ISP router.
[BetterBatteryStats] yochananmarqos:
There's more to it than that if you don't want double NAT. The ISP wireless gateway needs to be bridged so it's only acting as a modem and DHCP needs to be disabled. Problem is, if it's a voice gateway as well, the ISP may not allow bridging it. Also, with some ISP's like Comcast, the router control panel is not accessible by the customer.
[BetterBatteryStats] kryzeK:
[MENTION=1330150]chamonix[/MENTION] Please, add an adaptive icon for BBS. It's one of the only applications on my device that does not have it yet.
[BetterBatteryStats] DB126:
Don't concern yourself with random wakelocks unless there is a observed correlation with excessive battery drain. Wakelocks in isolation are not evil; how the receiver responds determines the impact. In most cases wakelocks are ignored unless there is a valid reason to keep the device awake.
[BetterBatteryStats] Oswald Boelcke:
Certainly true but as well pending to your country. As an example, in Germany ISP MUST allow customer to use their own routers by law and technically nothing is allowed to prevent them from this. Obviously, not all customs' routers fulfill the required specifications, or a VDSL-router won't directly work with fibre. For nearly 20 years, I'm using my own AVM routers i.e. the Fritzbox in different versions currently a 7490 that I can absolutely recommend.
[BetterBatteryStats] TNSMANI:
They will NOT understand or pretend that they don't. The stats under Network shows that the wifi is not sticking. The phone loses wifi connectivity very often and switches to mobile data. See how many downloads happened with data as against wifi. The Kernel Wakelocks also point to this.

Reset the router, if possible. Try to assign static IPs to all the devices. These

may

help.
[BetterBatteryStats] Senny0322:
Hi! I'm wondering if the number of wakeups I get from the alarms "Android System" and "com.google.android.gms" is reasonable? I typically get a poor battery life and have narrowed it down to these alarms if there is anything to do about the battery life. Pics of battery stats overnight.

Pics: https://photos.app.goo.gl/aSE9tcc6XCFQRyn3A
[BetterBatteryStats] strongst:
Instead of pics can you please attach the bbs dump file? It's more detailed and better to read/search for anything ;) thanks!
[BetterBatteryStats] DB126:
BBS dump is required for a meaningful analysis. Also note Google is probably not the bad boy; more likely a user installed app is enlisting Google supplied components to perform services on its behalf (eg: location reporting). Android ignorantly attributes utilization and associated battery drain to Google services without noting the caller or beneficiary. Stated another way: "don't shoot the messenger". Need a BBS idle dump (or equivalent) to help identify the real offender(s).
[BetterBatteryStats] senny22:
This file?
[BetterBatteryStats] DB126:
Yes, but contains 1+ hour of screen-on time which depreciates suitability for idle analysis. Read OP for instructions on creating a true idle dump.

A couple preliminary observations:

- Spotify (any streaming service) has an adverse impact on battery endurance

- Drain rate was actually quite reasonable at 0.5%/hr. What are you expecting?
[BetterBatteryStats] senny22:
Ok thanks. I took the dump file just now but the pics are from directly after I wook up. I didn't know what I was expecting but even when I don't use Spotify my SoT usually is under 4 hours on a almost brand new device, at least according to GSAM battery monitor.
[BetterBatteryStats] DB126:
This is not the place for imprecise SOT commentary which is influenced by so many variables it is practically useless as a performance measure (similar to "it's a bright day"). That said, so called SOT can often be extended if battery sucking apps, behaviors and/or services are identified and mitigated where possible. Best way to flush out offenders is via an idle analysis. Hence the request for a properly formed BBS idle dump. See OP for further discussion.
[BetterBatteryStats] senny22:
Ok thank you. Will create an proper idle dump.
[BetterBatteryStats] nsandersen:
A request: Could we have GPU states too?

I am trying to troubleshoot screen-on battery life after an upgrade and noticed my GPU seems to spend most time two steps above the lowest state (320MHz Vs. 133MHz), even with the powersave GPU governor.
[BetterBatteryStats] DB126:
Most GPUs idle efficiently at a mid-range frequency. Dynamic load appropriate frequencies will be selected as needed when the GPU is in use. Lower is not always better.

BBS is not a hardware monitor. There are numerous other tools in that space.
[BetterBatteryStats] nsandersen:
It would be convenient together with the CPU state views, but no problem - any other program you would recommend for the monitoring?

Thanks.
[BetterBatteryStats] infatality:
Is the latest build on hockey app fully Android 9, Pie compatible?
[BetterBatteryStats] hd-patsan:
Hi guys. I've already posted here about my problem with sensor_ind kernel wakelock, but then I was told not to concern because in my case this wakelock didn't drain a lot of battery, so I decided to listen to the respectful and obviously more experienced people around here than me. So, the wakelock gone nowhere, buy it also didn't wasted much phone's battery life, and everything was fine until yesterday night it drained 13% per 6 hours which is not so normal imho. So I started again my search but instead of googling it I asked of it my friend who got the same phone and by the time same custom ROM and even the same custom kernel which I recommended him to flash. Well, he didn't got the problem with that wakelock so it came obvious to me that the problem was either in my software set or in my settings. The software possibly causing the problem was dropped down when I got frozen all of the user apps through Titanium Backup and it didn't changed anything. So I went for the "settings" hunt :] And I found that bastard causing the problem - I turned off the Pocket Mode and right after a minute I turned the screen off the deep sleep started taking it's place. I just reminiscence how one of a good guys helping me then out asked me to write down what solved my problem so we could document it to help somehow another people annoyed with this problem and I got nothing to write because the battery problem disappeared after some system services and settings manipulation but the wakelock itseft didn't. So here it is - don't use the Pocket Mode if you are running AospExtended 5.7-5.8 Unofficial for Redmi 4X. It's broken. Maybe not, but it definitely have relations with sensor_ind wakelock. Thanks again and sorry for my bad english.
[BetterBatteryStats] strongst:
You should post this observation on the device forum - > rom thread ;)

Pocket mode detection is polling the proximity sensor and known for several(not in general) issues depending on device/rom/kernel.

There are devices setups with no impact and others with impact.
[BetterBatteryStats] DB126:
Absolutely agree on all points. Anything that poles the proximity sensor is suspect with variable outcomes depending on device, kernel, ROM, moon phase, etc.
[BetterBatteryStats] strongst:
Yeah, the drain is not recognizable on full moon(my personal observation) :angel:;)
[BetterBatteryStats] belloni:
Not sure if I'm being blind, but I can't see the download for 2.3-150?
[BetterBatteryStats] Oswald Boelcke:
I don't expect you to be blind but WHERE do you want to see BBS v2.3-150?

And why this version? Personally, I'm using v2.4-265!
[BetterBatteryStats] belloni:
Did you download that from here or playstore?
[BetterBatteryStats] Oswald Boelcke:
Google Play Store Beta Programme. For details refer to post #2. And release candidates are available via hockeyapp: https://rink.hockeyapp.net/recruit/e8a901e5d6a04e73a95c53b0fa21ab1a
[BetterBatteryStats] justjr:
09-26 06:18:37.997 E/BatteryExternalStatsWorker(957): no controller energy info supplied for wifi

I'm getting this warn on catlog.

And betterbattery does not record wifi usage. Just reporting, and wanting to know if it's known or anyone encountered that on Oreo Lineage 15.1 or any other ROM?

Device ate hand is the current in my signature.

Enviado de meu SM-G900M usando o Tapatalk