yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Perseus:
Typically 2 hour Logs are not sufficient to identify issues. I'd prefer to see overnight or at least 5 hours of Idle Log.

I see Google Now using Location service a lot. That does drain battery. You choose between benefits and loss there. Turn Off Location Service if you wish. Find My Phone is another big user of Location Service. Again your Call.Do you really need Gmail Syncing so frequently ?

Last but not the least change to a different Modem if possible.
[BetterBatteryStats] IODroids:
Tested for not more then 2-8 hours, but battery drain is too much (granting su permissions via chainfire)

I am not sure, why rest are not having this issue ??

I was using lollipop 5.0 russia version
[BetterBatteryStats] chamonix:
What version are you using?
[BetterBatteryStats] chamonix:
What battery drain is too much and how does that relate to BBS?
[BetterBatteryStats] suku_patel_22:
Why does this say no or unknown signal as 100% when I had solid signal strength through the night.

Sent from my Nexus 6
[BetterBatteryStats] Tzfardaya:
That's a mobile data indicator... If you were on wifi all night, that's normal...
[BetterBatteryStats] suku_patel_22:
Both wifi and mobile data off.

Sent from my Nexus 6
[BetterBatteryStats] Tzfardaya:
Then how can you say you had solid network all night? You had both network types turned off...
[BetterBatteryStats] suku_patel_22:
I had mobile data off but was connected to network. It should say no connection only when there is no network.

There are the two indicators, "No data connection" and "No or Unknown Signal", the former should be 100% while the latter should be 0%.

Sent from my Nexus 6
[BetterBatteryStats] Tzfardaya:
You had the msm_hsic_host wakelock turned off, didn't you? Think that might be a side-effect?
[BetterBatteryStats] suku_patel_22:
Yup had msm_hsic_host wakelock turned off and that can be a possible side effect. I will turn it on tonight and see how it behaves tonight :)

Sent from my Nexus 6
[BetterBatteryStats] Tzfardaya:
I've been doing some digging, looks like the GSM radio on the n6 is connected to the USB bus like on the nexus 4... I remember the n4 had msm_hsic_host issues too... Had to do with the radio not sleeping properly after being triggered... (and the GSM radio is used for voice as well as data, lte is Data only for most networks) I messaged Franco about it when I was digging, haven't heard back from him yet.. Maybe the n4 fix can be tweaked to fix the n6...
[BetterBatteryStats] zach_95:
system tuner right? Why does mine look nothing like that? Sorry, but can you guide me to get there? And are the ticked boxes the disable ones?
[BetterBatteryStats] Malhavoc Blackdrake:
Version 2.0.0.0
[BetterBatteryStats] Karpfenhai:
Nope, the unticked ones are disabled, the new system tuner looks slightly different but the approach remains the same.

Regards.
[BetterBatteryStats] whiper:
Too much MCS_HEARTBEAT alarms (every 50 seconds)

I've got too much MCS_HEARTBEAT alarms. I've got 4020 Alarms total and 2145 are MCS_HEARTBEAT.

This causes a high suspend_backoff time. Nearly 55% of all alarms are HEARTBEAT.

What can I do to solve this problem?

Every 50 seconds a MCS_HEARTBEAT. Thats too much. Any Ideas?
[BetterBatteryStats] chamonix:
This is most probably a kernel matter that you should take to the proper thread. Google shows lots of discussion around this matter and related to SMD drivers.
[BetterBatteryStats] chamonix:
Very strage indeed, especially as I don't see any wakeups. To me it looks like something prevents your phone to go to sleep, thus the count. Could you provide a logcat a dmesg if this persists?
[BetterBatteryStats] chamonix:
Time is one thing, count is different. Knowing the overhead of waking up and getting back to sleep (I always the parallel with doing stop and go with a car). Frequent short wakeups may result in short times but still be a problem bcause your phone does not stay in it's stable deep sleep state
[BetterBatteryStats] chamonix:
Those are really good and important questions:

1. Depends.... if your SMS app keeps obcessing at trying to notify you this may result into a sequence of more or less long wakeups to vibrate/beep/notify you and can really drain your battery very fast.

2. even in push the phone does not stay awake, push uses a "keep-alive" concept making sure that there is always traffic on the connection before the server times out. There is no constant traffic though. A common keep-alive is 25 minutes so that would be the sleep time between wakeups. Some experiences show bettery battery with push, some with poll so you must check what works for you

3. Background data is a threshold that can be handeled (or not) by apps. Unticking background data may lead some apps to calm down and to not try to do anything in the background but it's a convension no restriction.
[BetterBatteryStats] jeremysherriff:
Hi dude, thx for the response. Just FYI for you to add to your massive knowledge :) I reverted back a version (no wipe, just flash the ROM in CWM) - all OK.

Then, I re-flashed the updated ROM using CWM and included a wipe of dalvik cache + "fix permissions" - because the original upgrade had been done using the in-phone "updater" app. I checked inside the ZIP and the updater-script did wipe /cache but not dalvik. Anyway... result was a stable phone with no battery problems. The rpcrouter_smd_xprt kernel wakelocks still exist, the numbers are still very high, but it's not causing drain.

PS This is still the MIUI Portugese-English rom from our previous conversations.

Thanks bro, appreciate your efforts as always!
[BetterBatteryStats] chamonix:
Have you analysed the dump? and what were your findings?
[BetterBatteryStats] chamonix:
Obviously your main problem are with alarms. What have you found out in that area?
[BetterBatteryStats] chamonix:
5 minutes per hour are less that 10% awake, that is weird considering the drain. Have you only looked into the times or checked the counts too?
[BetterBatteryStats] moccor:
Does anyone know of a reason that this app doesn't work on this Droid X MIUI build?

http://rootzwiki.com/topic/11858-rommiuius-defx-part-2-2012-1-8/

It force closes before being able to show anything.
[BetterBatteryStats] yhrn:
Please use the search function. I really don't want to be rude but a simple "search this thread" with "miui" as search term would have kept this thread 2 posts shorter.
[BetterBatteryStats] dyetheskin:
apks in op are down I assume?
[BetterBatteryStats] dirtyreturn:
here is the latest .apk
[BetterBatteryStats] moccor:
Actually, if you knew the answer it would have kept it at least 4 posts shorter, but you don't so why waste both our time? I did search. And the change log says it works with MIUI.

Edit: it seems it had a update released that actually fixed it. I know for a fact that with v1.4 it said it was compatible with MIUI but still force closed.
[BetterBatteryStats] jeremysherriff:
Not on any change log I've seen. I run MIUI and it's been a problem that i hoped would be fixed.

So, with that said, v1.5.1 works with MIUI but it took a while to get any info. I had to go looking at the MIUI battery stats info (not turn it on, it was in already) before i got any info from bbs.

Chamonix: awesome work, you're good dude.
[BetterBatteryStats] Hrithan2020:
I have checked the count as well. There was nothing alarming. Will be monitoring it today, with just 2g enabled which will guarantee a better signal and then try today. If it doesn't work, will attach a dump tomorrow.
[BetterBatteryStats] polobreaka:
so the miui battery monitor doesnt cause wake issue anymore? i have left mine off ever since i read that it does plus it was conflicting with BBS.
[BetterBatteryStats] jeremysherriff:
The "conflict" has been solved but no, the drain by the battery info system is still there. To be honest it's pretty minimal, I'll grab some screenshots..

Edit - added screenshots. Note the flat spot about 3 hours from the right-hand side - when the phone's not being used, there's very little drain. I lose about 6% overnight with battery info service running. Also, it's been more than 12 hours since I unplugged, and still 44% remaining - and the phone's been used a fair bit as you can see.

PS I have wifi on "sleep - never" and Bluetooth always listening as I am always in and out of my car and it connects automatically to my car kit, so it gets a fair bashing.
[BetterBatteryStats] chamonix:
Correct and sorry for that. 1.4 was a first attempt but still left one error situation that was fixed in 1.5.1
[BetterBatteryStats] jastonas:
is it normal to have almost 95% deleted_wake_locks !!!?
[BetterBatteryStats] yhrn:
@Chamonix - I have an idea. Is there some kind of event raised when the battery reaches a very low level (say 5%) that BBS could listen for? If there is it could be useful to be able to configure BBS to dump a stats file when this happens. At a couple of occasions I have woken up in the morning to find my phone dead with a flat battery. After plugging it in a starting it I have been able to see that something kept my phone awake for hours but since kernel wakelocks have been reset I have not been able to determine what it was.
[BetterBatteryStats] Perseus:
HeartBeat is well Heart Beat. Some App is counting them so it can trigger its own Alarm after a preset Period. Find out who's counting.
[BetterBatteryStats] chamonix:
Well that's relative: these counters are 1:1 what android collects. BBS does not interpret data, it exposes it. Of course this does not mean the google's engineers always have the most logical way to sum/aggregate data or chose counters
[BetterBatteryStats] chamonix:
heart beats are keep alives. How do you draw the parallel between Alarms (wakeups) and suspend_backoff (sometime preventing your phone to go back to sleep?
[BetterBatteryStats] chamonix:
then I really need more testing / logs. The false positives were supposed to be fixed on 2.0 and we're confirmed by tests. Please send me a logcat+dumpfile whenever you have the chance to reproduce
[BetterBatteryStats] whiper:
Because the suspend_backoff state is activated when there is an alarm / sleep / alarm / ... situation in a short period. MCS_HEARTBEAT is an alarm. And it is not a 50 second interval, sometimes there are a few alarms in a very short period causing suspend backoff.

I need to know how i can find out why the period is so short. Normally there should be an MCS_HEARTBEAT only every few minutes.
[BetterBatteryStats] chamonix:
I would rather hint you at dmesg: suspend back off if something that happens when an event or state prevents the suspend cycle to go through the different stages from awake to full sleep
[BetterBatteryStats] Malhavoc Blackdrake:
Got another 12546% (or something like that). I was just turning the screen on after I connected it to the AC charger (was idle for just some minutes).

I'm attaching the export from your app. Not sure if first I have to select a specific query interval, or the export contains everything anyway. Just let me know, in case, for the next time.
[BetterBatteryStats] Malhavoc Blackdrake:
Happened again this morning:

- phone was fully charged from night

- unplugged phone

- changed profile from night to day (to activate network and sound). BTW, I am running CM11 Nightly on a I9100

- turned screen off

- then turned screen almost on immediately

- received a 702% active warning

I can understand that it may have been active 100% in the few seconds the screen was off, but 702% is a bit awkward :D

Openeed BBS and checked from unplugged to current. You can find attached both the logs and a screenshot
[BetterBatteryStats] anishmohandas:
Can anyone help me identify what is causing the drain in my Nexus 4

https://docs.google.com/file/d/0B81a7XRCG1EMM3lKQkpqUFdGUDg/edit?usp=docslist_api
[BetterBatteryStats] prateekgupta128:
Deleted BBS and phone bootlooped :(

I installed BBS on galaxy S4(i9500) rooted Touchviz lollipop 5.0.1 ROM as a system app....But when I uninstalled it, it got disabled. So I went ahead and uninstalled it from Link2SD app...

Immediately I got many errors and when I restarted my phone, It doesn't go beyond Samsung logo...:crying:

Please help me resolve it :(

I don't care about the data...I just want my phone working again...I went to stock recovery and tried factory reset, wiped cache and all but nothing worked...It shows that android guy with red triangle....

Any help is greatly appreciated...
[BetterBatteryStats] Karpfenhai:
Simply reflash your Rom.. not hard, Odin is your friend, you don't even need to wipe data.

I highly doubt it's related to bbs.

Regards.
[BetterBatteryStats] atomomega:
If both wifi and mobile were turned off, it's normal to get those readings.

No data connection= no mobile

No or unknown signal= no nothing

Instead of saying what the app "should" do, why don't you first understand how the app works?
[BetterBatteryStats] prateekgupta128:
Thanks mate !! It worked....And I guess it was because of forceful deletion of BBS...Phone was working fine before it...

I would immediately install CWM and take nandroid backups so that I don't lose my data again...

Thanks again :)
[BetterBatteryStats] usmani:
Can you add an option for gpu frequencies also in your next version if it's possible?
[BetterBatteryStats] ymDroid:
Anyone tested to see if BBS works with the most recent 5.0 build on the Verizon GS5?

Do you still have to install it as a system app?
[BetterBatteryStats] FadeFx:
You will always have to do so...

tapatalked from lollipopped i9300
[BetterBatteryStats] aitvariux:
Hello everyone!

I am asking for help because I am out of ideas what is going on with my android.

The problem: can't go to deep sleep in about one cycle of charge. After rebooting everything is good for some time but it start to drain the battery again when screen is off. I hate to reboot every day...

What I have done till now: rerooted,changed ROMs,kernels,ref lashed twrp recovery. Even tried to change modem but I couldn't for some reason. Tried to understand myself but I am lack of knowledge.

I really appreciate your help with this and sorry for not perfect English!

BBS file attached.
[BetterBatteryStats] Perseus:
Yes.

28 Minute Log is way too less a period. Can you please post an Idle Log of at least 3 to 5 hours ? Even for that period, the Phone was on Lowest Frequency 300 MHZ for the most part (26 Minutes). Do you have any Kernel Control App going on that does not let CPU Frequency bellow 300 ? Do turn off Location Service when not needed.
[BetterBatteryStats] :
Hi Sven,

I have just noticed a weird bug in latest BBS on lollipop, well at least on my device :)

The alarms are not being categorized correctly it seems. For example, a BBS alarm is showing under whatsapp!

I attached a Screenshot, in case this is something that peaks your interest ;)

Also, partial wakelocks don't look correct to me (the times are unrealistic), but i guess that's already known.

A dump is also attached to show what I mean.
[BetterBatteryStats] chuakid:
Could someone provide insight into this issue?
[BetterBatteryStats] aitvariux:
Thanks mate for the answer. Will do few hours file. I am using trickster app for kernel configuration. Deleted it and I will we is there any changes!
[BetterBatteryStats] chamonix:
thanks, that IS helpful. I have added issue #675
[BetterBatteryStats] IronTechmonkey:
Interesting. I'm not having this problem but notice that it involves a little CM glitch I have seen ... so for what it is worth.

In all CM nightlys I've used (many dozens) there are instances where powering the phone off by power button and immediately powering it back on causes the interface to become unresponsive although apps still run and information posts to screen. A slower power off and on restores normality. The behavior can be reproduced reliably but not 100% of the time. Furthermore, the aforementioned glitch relates to another CM glitch where the countdown timer runs past zero with no alarm (the former glitch can be used to induce the latter glitch).

It may be stretch but if that odd percentage you are seeing only happens after rapid power off and on there may be a direct diagnostic connection twixt those two events.
[BetterBatteryStats] Malhavoc Blackdrake:
I've also noticed that it has happened a lot at work, where I keep my phone almost always connected to USB for charging, due to the bad signal and fast discharge it gets. While it has not happened in these days I'm home with the flu ( (where I do not keep it under power, since signal is good). That's to say that it may have something to do with the under charge state, but it's just a guess.
[BetterBatteryStats] smart-t78:
thanks...good work
[BetterBatteryStats] chamonix:
I will need to check if there is some file in the kernel where I can read from. I have never seen that but if a kernel guru reads this he could give me a hint.
[BetterBatteryStats] mdamaged:
Not sure if it will give you what you want but you can try this:

su

busybox find . | busybox grep gpu
[BetterBatteryStats] usmani:
Awesome. Thanks
[BetterBatteryStats] Hammerhand.17:
Lastly, I've been seeing that my phone wastes a lot of battery. I think HDWidgets is very nearly related to it, but I think there is something more. Tonight, I've made this log. Hope you can help me.
[BetterBatteryStats] Nimueh:
Would someone happen to know if adding the BBS widget still causes every launcher to fc on CM12-based Roms?

I'd hate to try and flash a couple of them just to find out it still happens - would be nice if somebody that has tested it already (on one of the newer Rom builds) could report back. It works fine on my GPE LP Rom, but I'd like to try a CM12-based one again :angel:
[BetterBatteryStats] :
Since Lollipop my phone wakes up constantly while display is off. Didn't have this in KitKat with same apps, so battery life decreased.

Please could you look into my logfile and help me out? Thanks!

Seems like a sensor (ssp_sensorhub_wake_lock) plays a role in here. S-Health is disabled. Any ideas where this comes from?
[BetterBatteryStats] Poeta:
The same happens in my Moto G (2014) after install the BBS as System App and reboot. Stock rom, Lollipop 5.0.2, rooted.
[BetterBatteryStats] Klaus_Aut:
If I will take a widget on my home screen, I get a Nova Launcher FC on my N5 and N6 with Dirty Unicorns. Anyone can help me?
[BetterBatteryStats] Nimueh:
OK thank you - that answers the question I asked 4-5 posts before yours ;)

That's a problem in CM12-based Roms and it sounds like they still didn't fix it. The widget works fine on non-CM12 Roms like GPE :)
[BetterBatteryStats] Klaus_Aut:
Ups, sorry... I should read more. ? but thank you very much for answering.
[BetterBatteryStats] Flashvetrin:
Under wifi advanced turn "allways scanning" turn it off.. if you havnt.. do you use greenify??? I reccomend it. I believe its avalible for lolly now..

---------- Post added at 10:58 PM ---------- Previous post was at 10:46 PM ----------

Your hd widgets are 4.3% usage and over 22 minutes on the nlpwakelock.

9 hours on acuuweather is a hardhit as well.. widget related.

Your fingerprint scanner has 9 hours on it as well.

Under wifi advanced due you have "allways scanning" turned off?? If not do so..
[BetterBatteryStats] oediv:
Hi guys

I am having Dome heavy wakelocks on my Nexus 9 Lte running dirtyunicorns and fire and ice kernel

The system screen was not from the same Day but it Shows the wakelock really good

Hope someone can help me

Thanks
[BetterBatteryStats] Flashvetrin:
Can you produce a log???
[BetterBatteryStats] oediv:
Yeah, is this Right?
[BetterBatteryStats] Flashvetrin:
Better battery stats log is what i was after..
[BetterBatteryStats] oediv:
Now the Right one? :/

If not Can you explain how to generate the bbs log
[BetterBatteryStats] Flashvetrin:
Thats the one it will be under review..

Hang tight...[emoji16] [emoji106]
[BetterBatteryStats] Flashvetrin:
You should start by turning location services off when not in use.

Also google now has a tendency to cause powermangment to kick in on standby.

I would install greenify and hibernate.

the key is to see how long the apps/system files have been running in the background. Clear your cache in playservices and update your version if you havnt allready.

Also under wifi advanced turn "allways scanning" off.

Your google play books needs to be greenified as well.. its a start im sure someone else will chime in and add more.. [emoji16] [emoji106]
[BetterBatteryStats] oediv:
Well that's funny cause i disable location Service and I am turnen wifi off when i am Leaving the house also Google now is disabled and I am using Nova launcher

Well I am going to Try all you say Maybe i am going to make a full wipe to be Sure :)

Thanks for your work, I will let you know if you help solving the Problem :)
[BetterBatteryStats] Hammerhand.17:
I am using CM12+Nova and adding BBS widget results in crash, too.

- I've uninstalled hd widgets for now.

- acuuweather is not installed. Maybe it is Weather Widget from CM!2?

- My phone is a LG G3. It has no fingerprint scanner! Maybe a service believes that it has and it spends battery? I'm gonna search it.

- Wifi "allways scanning" is already turned off.

- I have greenify installed, too
[BetterBatteryStats] AdiSimpson:
I had massive Alarms/Wakeups trough fastdormacy.wakeupserver, up to 100/h.

I disabled fastdormacy, had no alarms anymore, but more battery drain. That's means there are also "good" Alarms/Wakeups? I'm a little bit confused.
[BetterBatteryStats] aaronito:
Any idea what caused my battery drain

Or wich app?

Thanks
[BetterBatteryStats] aitvariux:
Second round.

Please help me guys,this time more then 3 hours idle phone with no deep sleep!

changed everything what i can.Rom,kernel etc. But sometimes its just stuck on 300 MHZ.

BBS file attached
[BetterBatteryStats] Flashvetrin:
Question on your kernel.

Are you using a controller app? Is this a custom kernel?? Or stock..
[BetterBatteryStats] :
Location scanning was on indeed but didn't do the job.

I will take a look at greenify but honestly there has to be a reason for the wakeups (busy sensors) I can solve without an additional app since it wasn't the case in KitKat.

In KitKat I didn't use fingerprint scanner. Could this be related?
[BetterBatteryStats] Flashvetrin:
I need to re-review your log.

Im in hopes that someone else may also have some feedback...

Please stand by...

[emoji16] [emoji106]
[BetterBatteryStats] Flashvetrin:
Your proxy sensor has a wake. With quite

A bit of run time i see in your log

Are you running a cm build i forget.

Theres actually two wakes on your proxy sensor. This definitely would prevent a deep sleep.. im not sure what the fix for this is... someone who knows more about cm may have more insight...if you look under your kernel wakelock youll see what im saying look under line #1 And line #2 youll see the locks. if you google the line item you may find some info.

Your at 73.9% deep sleep its not to bad..

Also freeze samsung push service if you can using titanium backup...

Have you updated your modem??
[BetterBatteryStats] aitvariux:
I am on stock xxuend5 kernel now and not using any kernel controller. Was using lean and ael kernels too. But it's the same issue with 300 MHz!
[BetterBatteryStats] Perseus:
Yeah I think So. It could be related. Remove Shealth.
[BetterBatteryStats] Flashvetrin:
Try cleaning out your init folder.

Everything except super su.

boot to recovery and flash your kernel again..

When you ran ael what controller did you use???

When you flash a rom is it a clean flash??

Or dirty???

Stock is fine when theres no remnants left behind.. having your cpu stuck on 300MHZ @80% usage isnt right at all..

I bet your phone lags bad.[emoji32] .. I would recommend doing a clean wipe, (THIS INCLUDES INTERNAL) and start fresh with a clean rom download. Flash a custom kernel with a controller such as synapse or faux. Give it time to settle in and see how goes..

someone on this thread may chime in and have more to add... but its were i would start...