yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] jdt352:
Check your Call settings- is TTY Mode checked? You don't need TTY unless you are communicating with a deaf person.
[BetterBatteryStats] dragunbayne:
I can't seem to find any tty settings, is it directly under call settings? I will also post in the thread for my rom as it may have been removed and causing an issue. Thanks for your help.
[BetterBatteryStats] stuart0001:
Could it be an app causing the issue because I don't get the error until several hours after a reboot?
[BetterBatteryStats] betoNL:
In fact Maps was already removed from my device....

So I froze back as many as Google stuff as I could, my phone is now deep sleeping as a baby, is even more responsive and I am getting even more battery juice...

Only side effect is that Market is nonfunctional, but I can live without it, till I am in the mood for a fresh firmware instal...

Google is not always your friend ;
[BetterBatteryStats] fetteente:
Problems after Update under MIUI

I have MB MIUI installed and bought BBS 1.5.1 over market. After Update to 1.6.1 there was no list shown in process and the other lists were not updated. If I changed i.e. from process to partial wakelock, there was no fast blinking "computing". After reinstalling 1.5.1 it is all oK. Anybody else under MIUI with the same problem? B.t.w: after first installation of BBS, I have had to stop the MIUI battery service and start again. Only after this, I could see something in BBS.
[BetterBatteryStats] hackeron:
Hi, thx for this app.. Im wondering about these 2 things..

I have uninstalled gtalk but I still see this when I check wakelocks.. What should I do to remove this or should I ignore it?
[BetterBatteryStats] nickname_marco:
can anyone help me with my stats?

i did three logs and i changed a few things in-between (modem version, installed/frozen apps, etc).

still, i am not much satisfied; what do you think about my results?

kernel= phenomenal 4.0 extreme (known to be very aggressive on battery saving)

removed and frozen many apps, including samsung's ones

2000mah battery

..i have seen nice numbers with the same kernel, i guess i can expect more.

anyway, i am testing the same system with some more optimizations so i will post more stats during the next days.

thanks.
[BetterBatteryStats] jeremysherriff:
You really need to do a log for just the time when your phone is (should be) asleep.

Charge it before you go to bed, remove from charger, and in the morning take a dump from BBS. Use the setting "since unplugged" if you didn't charge fully.

It's hard to wade through the stats and seperate your usage of the phone (and apps) from rogue background activities when you use a dump that covers the daily usage.
[BetterBatteryStats] nickname_marco:
didn't think about that.. thanks, i am going to do it.

:)
[BetterBatteryStats] jeremysherriff:
I believe GTALK_CONN and GTALK_ASYNC_CONN are also used as transport to back up to google if you have that option enabled, and also to check and notify you of market app updates. There's possibly other uses to - it's pretty integral to the whole Google framework stuff. Unless it's very high or causing an issue, you can ignore it.

Without further info (like "since" information) it's hard to say, but 22m might be a bit high. Do you want to post up a dump file?
[BetterBatteryStats] glennkaonang:
Could you provide steps to lower down this gtalk async conn wakelocks?

What I've done is this:

1. Disabled Gtalk

2. Disabled Maps

3. Turn off auto sync

4. Turn off auto backup

5. Turn off market notification

Is this enough to lower down gtalk async conn?

Thanks.
[BetterBatteryStats] mattallica76:
Audio_Out

Does anyone know what this Audio_Out wakelock is. It's almosy always at the top of the list and usually averages about a minute of wake time per hour unplugged. The sample dump I've included is over a relatively short period, but hopefully it helps identify the culprit.
[BetterBatteryStats] jopherr:
hi! at the moment i am having 2 hours 56 minutes of partial wakelock due to

AudioOut_1

1013

and 12 minutes of

AlarmManager

android system.

what are these and how would i decrease the wake lock time?

also, what is media server? * under battery usage*
[BetterBatteryStats] yhrn:
Maybe a bit too obvious but, regarding AudioOut_1, were you guys listening to music?

AlarmManager - check the Alarms view in BBS for info on what apps were triggering alarms.

Also, attaching a dump file is always a good idea. It needs to be over a couple of hours where you did not use the phone (or a at least used it very little) as well.
[BetterBatteryStats] mrjuniork:
I can also very much recommend 3G Manager.

Hasn't been updated for more than 2 years, but works like a charm for me (OOS 4.5.10, OP5).

3G will be completely switched off after a delay that can be set up. Then the reconnection times can be set up as well (starts with 7 minutes). Is a great battery saver and the app can also switch off data when connected to wifi. And there is no battery drain at all....(but I don't think it's for free though)
[BetterBatteryStats] fossils-n-dents:
I had a friend with 'qpnp_fg_memaccess, qpnp_fg_update_temp and qpnp_fg_update_sram' issues last year. Being naive and uninformed at the time, I attempted to look into it even though documentation is scarce on the issue. I always go for 'Something network/ app wise is making this happen' as opposed to hardware failure.

The upshot was Google Now in an 'Always On' state was not playing well with his device, along wih his entire family (5 phones, 3 laptops, one printer, and one tablet) were all on the same network. Turned off GN, reset Wi-Fi networks, and switched him to 5GHz, problem solved. In my supreme ignorance, I concluded Google Now running constantly somehow threw something off along with a crowded network. Only later in did I discover these wakelocks are related to possible Battery Controller problems, connectivity problems, and/ or charging issues. I always err on the side of connectivity problems first. I am an optimist.

It's possible that your 2 year old device could be losing it's mojo, but I'd rather rule out certain things first before we throw in the towel. Last ditch, I would do a factory reset before throwing the device away. If you still have your old router, set it up, and see if this relieves your issue. Just a thought.

I use EX Kernel Manager with ElementalX kernel. I don't see that being a problem unless in cases of overckocking.

I meant 'Connectivity' insomuch as far as your Wi-Fi network was concerned. My apologies for not specifying.

I believe you'll get "No Data Signal" while on WiFi to save battery. Also, your Facebook wakeups weren't that bad. I just don't trust the FB app to be battery efficient.
[BetterBatteryStats] chamonix:
I'd recommend moving to 2.3 (either the beta on gplay or the xda-edition). The reason is in 2.3 there is a change to handle "large" parcels of data coming from the battery_info service that was sometimes failing in 2.2, leading to the app behaving as if it had no data. Links for both editions are in post #2
[BetterBatteryStats] Bubba:
First thanks again for the response. I turned off Battery Temp Monitor and CPU Temp monitor in EX Kernel manager just as a test after my last reply. Since then 'qpnp_fg_memaccess, qpnp_fg_update_temp and qpnp_fg_update_sram' are at 2%, 2% ans 1% after 1.5hrs. of mostly rest. Wake time screen off is now 12%. I am going to give it a good test tonight again with those off. The time I have had that wakelock coincides somewhat with when I enabled the CPU temp monitoring. Will be interesting to see.

I am far from giving up my 6P although it will get a new battery soon due to what I have seen about early shutdown with these phones. I really don't change anything with the kernel settings so it shouldn't be an overclock issue (I wouldn't think).

Thanks for the info on connectivity. I always wondered why the numbers were high, I guess it's because I am on WiFi most all day lol.

I'll grab another dump tomorrow and see if indeed disabling the 2 temp monitors had any effect.
[BetterBatteryStats] PeQuEsan:
Thanks a lot. I applied for the beta some hours ago and it's working and seems stable as of now.

Sorry, I wasn't aware there was a beta program for BBS.

Bye!

Desde el móvil...
[BetterBatteryStats] paco_ramirez:
No one knows what is the BTLowPower wakelock and how to avoid it?
[BetterBatteryStats] OfficerJimLahey:
Having watched TK Bay's feature on XDATV I tried the rootless method with the Play Store app, since I have been getting horrible battery life for about a month now on my Acer T08 (seems as thought ever since Google Assistant rolled out for the device, something I had since disabled).

The telltale heart to me seems like:

PostLocationService (Android System): 13 h 18 m 37 s Count:1129 91.0%

(uptime would have been around 14 hours)

But, since it's related to Android System, I cannot surmise an adb appops command to ignore that component's wakelock.

Attached is my full BBS dump if anyone wants to take a look for a better scenario (it would be appreciated).
[BetterBatteryStats] OfficerJimLahey:
To me by name it sounds like sleeping, but still active while in airplane mode, Bluetooth. Which would be strange since the point of flight mode is to turn off all radios.
[BetterBatteryStats] paco_ramirez:
Thanks for the answer. Everytime I put it on airplane mode I check all radios (wifi, bluetooth) are switched off. I have also location services disabled (which sometimes uses BT or WIFI)... Not sure what could be the cause
[BetterBatteryStats] Bubba:
[MENTION=4138220]fossils-n-dents[/MENTION] I'm not going to post a complete log as I am still experimenting but I wanted to give some feedback about last nights BBS dump with the only change being turning off the EX Kernel Manager Battery monitor and CPU monitor. Listed are the biggest differences I can see as compared to the night before. Tonight the only change will be placing the WiFi on the 5.0 where nothing else is connected. I just thought this was interesting and would share:

Screen off time was 1/2 hr longer

Batteery level lost was 5% less

Percent per hr was 1% less

Deep sleep was 1 hr longer

qpnp_fg_memaccess was 2%less

qpnp_fg_update_temp was 1.5% less

qpnp_fg_update_sram was .6% less

So it seems to me at least that the live monitoring of the CPU and Battery temps in the notification area had some effect on it. Again I am going to try switching the WiFi bands tonight and see what difference it makes. Thanks again for pointing me in the correct direction.
[BetterBatteryStats] fossils-n-dents:
I am researching your issue. Stay tuned...:good:
[BetterBatteryStats] hollal:
New phone, new installation time. Running Nougat. Version 2.2.2 from the store does not seem to find any alarms. I tried the XDA version too but it's the same. The phone is rooted with Magisk 11.6 and I have also granted BATTERY_STATS permission with PM. The log says it requires BATTERY_STATS under the alarms section and is then blank. I've attached the log file in case it helps.

I also tried v2.2.0 and left it for 15 minutes or so and no alarms. I know, it's not long, but something would have triggered it by now I'm assuming.
[BetterBatteryStats] fossils-n-dents:
'PostLocationService'- A partial wake lock becomes stuck if it is held for a long time while an app is running in the background (No part of the guilty app is visible to the user). This condition drains the device's battery because it prevents the device from entering lower power states. An app(s) is not releasing the wakelock back to Powermanagement Lock after getting location info.

I would start with disabling Wearables and Google Fit, then any app requiring location. One by one.

You're being polled, scanned, updated, tracked, geofenced, and analyzed into oblivion by Google and app devs. App(s) requiring location/ data are very busy on your device. *Net Scheduler*, (Cell tower tracking through data), and NlpCollectorWakeLock (Network location provider triggered when GPS is enabled) are running unchecked. With root, these effects can be lessened.

If no relief is found through disabling, I would suggest Safe Mode observation for a time, run on data only, then Wi-Fi only (No Bluetooth). If relief is found, the slow task of disabling/ re-enabling apps (With Wi-Fi, Bluetooth, Location enabled) until the culprit(s) is found begins. One rogue app can bring down the house.

Try clearing Data/ Cache in Google Play Services. Try clearing cache in Google services Framework Engine. Check app settings for lowering update frequency. Maybe reset app preferences in your device settings. It helps sometimes.

LTE (without data transfer) or WiFi (without a connected access point) is trying to do something (looking for a network or trying to connect with a timeout). At this point, a lot of wakelocks (EINT wakelock, m1_cldma_peer, ttyc0, ccci_fs, ect) could come into play. Your device does the heaviest data lifting through mobile opposed to Wi-Fi. Let's look at the router...

Try a static IP instead of DHCP. Switch networks (2GHz> 5GHz), Check your router for failure/ settings/ possible firmware upgrade. Turn off Bluetooth/ Sync/ Location/ GPS when not in use (Optional). Disable/ remove unused/ little used apps. Every bit helps.

Factory reset is the last resort. Even then, careful app selection upon re-installation while monitoring network activity will be required.

I really could not nail anything down to a specific event, as this is a little over my head. I apologize if I could not be more specific/ helpful. Good Luck.
[BetterBatteryStats] OfficerJimLahey:
Will try again without Bluetooth (and as result without the Pebble) in the next day or two - as a start. I forgot that the Pebble app updated around that time as well - It may be needing location data a little too much now (truth be told, they would all be gathering too much for what is needed).

That may be due to how I spent those 14 hours - at work, where it may or may not have been trying to pick up the wifi six floors up. I think that access point is "forgotten" these days, however may not be the case. Also, if weak cell signal as well, the thick walls may play a part there.

At home (last few hours of the dump), I do have a close-to "dead zone" in my office that may still be an issue. I have two routers over three floors - the 2GHz/5GHz one (Linksys EA2700) in the basement, and an older Linksys WRT54GS (2GHz only) running Tomato on the main floor. Both share the same SSID (but different channels) on the 2GHz band and interestingly (I use the 2GHz band as it has much better range as a result), one is pretty much directly above the other. Unfortunately, due to the wired bandwidth of the older device (100Mbps which acts more like 40Mbps), I cannot swap router positions or move the older router into the office without suffering serious performance issues. At some point (long term strategy) I will need to figure out and acquire a newer, inexpensive gigabit router to reconfigure as a repeater - like the old Linksys - to either replace that or to place in the office as an additional AP.

A static IP will be a good idea. Much food for thought here, better than just being obsessed over one thing thus trying to "spite my face" with an appops command.

Thank you for the pointers! :cowboy:
[BetterBatteryStats] fossils-n-dents:
I'm glad you cleared that up for me. Your log file pointed to pure device insanity. It literally drove me crazy trying to figure out so many inconsistencies on so many levels.

*A proper idle dump is required.

6+ hours of idle (No touching the device), Your 'Screen On' time must be under one minute. Screenshots of your dump are helpful also.
[BetterBatteryStats] kgirlx:
Services

Where is this services list. Would you happen to have a link. Thank you.
[BetterBatteryStats] Bubba:
https://xdaforums.com/showthread.php?p=73693320

Cowboy from Hell on a twisted trail.

Koffed From my Big Ass Outlaw Phone.
[BetterBatteryStats] hollal:
I don't mean to sound ungrateful but a longer sample time still shows the same issue, albeit with more information about everything else. All other stats appear to work, except for the fact that nothing is logged under alarms.

======================
Alarms (requires BATTERY_STATS permissions)
======================
======================
Network (requires root)
======================
10077 (Wifi) (com.android.chrome.Chrome): 297.0 KBytes 60.0%
...

I suppose I was hoping someone would instantly recognise the issue and just say something like, 'Oh yeah, try doing x, y, z". I have attached the logcat that was generated at the same time in case it reveals something to the more knowledgeable than myself.
[BetterBatteryStats] TNSMANI:
Read a couple of pages before. Chamonix was explaining why you don't get stats sometimes and recommended using v2.3x. Try that.
[BetterBatteryStats] hollal:
That's what I'm currently on, I signed up as beta earlier this morning and so far it has not collected any alarms.
[BetterBatteryStats] mondohow:
You are not alone my friend. I only get alarms when I enable "Alarms using API" in the Advanced section of settings. There are at least 2 threads in the main BBS forum about this.

What's your selinux status, permissive or enforcing? If you are rooted with Magisk I think there is a module to change from enforcing to permissive but not sure the trickle down ramifications of doing such. I didn't bother since I get the alarms with API access enabled. I ask based on the below Q & A.

Question here: https://xdaforums.com/showpost.php?p=73738100&postcount=32762

Response: https://xdaforums.com/showpost.php?p=73744010&postcount=32772
[BetterBatteryStats] hollal:
Thank you for your reply. I had only glanced at the settings menu when I first installed it. I have enabled the Alarms using API and now at least I am presented with alarms. Quite a few in fact. What would appear to be the same process/app listed multiple times. I've plugged/unplugged to reset and now I'll wait an hour or two and see what stats I have.
[BetterBatteryStats] fossils-n-dents:
That's my fault, I was under the assumption your alarms didn't kick in yet, and you wanted to know why. I misunderstood what I read.

I'm glad someone was able to help you with your issue.

if you need further assistance, please don't hesitate. Again, my apologies.
[BetterBatteryStats] manalicream:
Can anyone help. I'm getting 3%+ idle drain and used to be getting around 0.5%

Any help greatly appreciated!
[BetterBatteryStats] cpasoft:
As many times said before, you must upload only idle log. In this log you have more than 30 minutes of screen on...

Enviado desde mi LG-H870DS mediante Tapatalk
[BetterBatteryStats] manalicream:
OK I will do that tomorrow sorry
[BetterBatteryStats] cpasoft:
NP

There is a topic with directions for doing right...

Let me search it for you...

Enviado desde mi LG-H870DS mediante Tapatalk

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

Here you have :

https://xdaforums.com/showpost.php?p=72467976&postcount=32150

Enviado desde mi LG-H870DS mediante Tapatalk
[BetterBatteryStats] ridhi:
Can some one help me with my Dumps.

1. This one there is no deep sleep overnight something don't let my device go into deep sleep.

http://cloud.tapatalk.com/s/59bdfbe29b533/BetterBatteryStats-2017-09-17_093643676.txt

2. The second attachment is of my day usage where it did not went into deep sleep the whole day but in the evening it started to go into deep sleep for like 2 hours don't know how.

http://cloud.tapatalk.com/s/59bdfdc8ab5f0/BetterBatteryStats-2017-09-16_215953524.txt

I would be really grateful of someone can help. Thanks
[BetterBatteryStats] manalicream:
Thanks. See attached.
[BetterBatteryStats] Oswald Boelcke:
Sir/Mam, you didn't follow the given procedure again. Forth bullet states the log must at least capture six hours and not less than two like yours.
[BetterBatteryStats] manalicream:
Oh sorry. Will try again tonight
[BetterBatteryStats] atarek:
Hello,

I noticed recently that mobile is kept awake while screen off as attached screenshots.

Attached idle dump.

Appreciate any advise or support.

PS: below screenshots is current status from BBS and idle dump was while sleeping and screen was off.

Regards,

Ahmed
[BetterBatteryStats] fossils-n-dents:
Looks like a network traffic jam to me. Do you have a weak cellular signal? Is Wi-Fi available?

Push notifications and backups possibly all fighting for a limited signal. The Context Manager (In your 'Alarms' Section) is responsible for allocating resources within a single block of code. That is, it can, for example, allow execution of some additional operations along with the main operation without creating a separate code for this additional operation. This is not being allowed to happen. Not being a programmer, I can not say why this is used in Google services, I can only advise clearing the cache/ reset data in Google Play services and Google Services Framework Engine to see if that provides relief.

And/ or, you could 'Reset App preferences' in your 'Apps' section of your device settings. After reset, check all apps notification frequency, and lessen them in those apps that are able.

I would also advise reducing some the stress Google Play Services adds to Android System. The process can be found here...https://xdaforums.com/showpost.php?p=73693320&postcount=32709

Afterwards, try another idle run. Good Luck.

---------- Post added at 12:13 PM ---------- Previous post was at 12:03 PM ----------

You need a minimum of 6 hours idle time to gain an accurate picture of your system as per the OP.
[BetterBatteryStats] atarek:
Hello,

Thanks for your reply.

I followed attatched steps as stated in OP and my dump is for 4h 40m.

This issue became annoying for last week i was gaining 6h SOT and now i loose battery while screen is off.

I wished my report could find the culprit.

I will try to capture another dump ASAP.

Regards,

Ahmed
[BetterBatteryStats] fossils-n-dents:
Yeah, the OP concerning idle time was not updated. My apologies.
[BetterBatteryStats] manalicream:
How's this?
[BetterBatteryStats] squicky:
Hi, I have some issues with deep sleep. My N7100 stays awake most of the time. I'm using Resurrection Remix v5.8.4 ROM. Any help is much appreciated :)

View attachment BetterBatteryStats-2017-09-18_093401262.txt
[BetterBatteryStats] pjadec:
One of them

logd (0): Uid: 0 Sys: 9 m 33 s Us: 4 h 47 m 25 s Starts: 0

seems to keep your phone awake

+ probably also kernel problems
[BetterBatteryStats] TNSMANI:
Your screen was on ie. phone was being used for 18+ minutes before saving the dump. It should be less than one minute.
[BetterBatteryStats] fossils-n-dents:
Your 'Screen On' time must be under one minute during the idle run. Bullet #2 as per the OP

Bullet #2 as per the OP- "Leave the phone alone when generating the idle dump". Interaction ruins idle stats.
[BetterBatteryStats] manalicream:
How do a get the phone down to 95% from full then as per the instructions?