yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] luizlee86:
Hi there!

I searched the thread, but no one posted anything about AudioOut_3?

I saw it for the first time today... I'm attaching a log file. Any tips?

Thanks in advance!
[BetterBatteryStats] CazeW:
Yep, the screen was on during that time because I was afraid of losing the reference point.

I updated to Beta 3 and the reference point stays now but unfortunately beta 3 only dumps empty files.

EDIT: Checked logcat when pressing the dump to file button. StatsProvider just throws Exception: null and nothing more happens. In the included logcat I first press the refresh button and then right after that the dump to file.
[BetterBatteryStats] It_ler:
Better to provide a BBS dump file.

Charge the phone, unplug it and let it do nothing for about 4 hours.

Then unlock the screen, open BBS app, go to menu and choose "Dump to File".

Attach this dump file here.

That might give us better basis for giving some recommendations.
[BetterBatteryStats] taz1458:
Here it is. Only done a few things on it since I came to work and unplugged it.

http://db.tt/gxW6MD8d
[BetterBatteryStats] It_ler:
Oh ... looking at your fingerprint: "FINGERPRINT: samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/XXLPQ:user/release-keys"

XXLPQ is Android 4.0.3 ... right?!

Have you changed something in your build.prop?

Nevertheless:

1. Facebook, "Wecker11 (com.splunchy.android.alarmclock.AlarmDroid)", "com.splunchy.android.alarmclock", Google quick search box, etc. are active. Disable / freeze all apps/widgets that you don't need every day.

2. I see some Fast Dormancy wakelocks. Try to change the FD state on your phone. You can use Fast Dormancy app from gokhanmoral (from Play store).

3. About the AudioOut_3 wakelock ... it could be something related to voice/Text to speech, etc. Try to disable all those options in ROM and Google settings.

Good luck !

---------- Post added at 12:56 PM ---------- Previous post was at 12:43 PM ----------

Ok ...

1. "UpdaterService (com.protrade.sportacular.Sportacular)" is busy on your phone. Something you should disable/freeze just to check its influence on your battery life.

2. "AlarmManager (cloudtv.hdwidgets.HD Widgets)", Gmail, Google quick search box, Google voice, "org.mikebannion.fbnotifications", "com.espn.espnfantasyfootball", "com.yinzcam.nfl.broncos.Broncos", "com.prowresnet.android.ProWrestling.Net", GoSMS, etc. are active as well. Disable/freeze all apps/widgets that you don't really need every day.

3. Maybe you could gain more battery life when disabling wifi. I have changed my wifi policy so that it is tunred off when screen is off, as there should be not much mobile data traffic when screen is off. This saves much power on my phone.

4. AudioOut_2 wakelock could be related to Music Player or voice/Text to speech ... so please disable all those settings.

Good luck !
[BetterBatteryStats] noizy1234:
Anyone know what sns_periodic_wakelock is? I'm constantly getting this and is draining my battery all the time

Sent from my Nexus 4 themed with Goog Le Bean
[BetterBatteryStats] skivnit:
Sns, if im not mistaken, is rrlated to social sites. So facebook must be it

Swyped from another galaxy
[BetterBatteryStats] noizy1234:
I have Facebook uninstalled.. So can it be Google +? Here's my dump file http://db.tt/UYjLzfU0

Sent from my Nexus 4 themed with Goog Le Bean
[BetterBatteryStats] Casanoaa:
Firstly install latest bbs app and not beta. Second idle dump
[BetterBatteryStats] It_ler:
1. Please install latest stable BBS app version, which is ATM v1.11.0.0.

2. Disable/freeze Google+.

3. Disable all location serivce options in ROM and Google settings.

4. Have a look at ROM menu Settings > Applications > All and search SNS. try to disable it.

5. Your phone seems to be rooted, but there are no alarm and network stats. Please check in BBS app menu that the root featrues (in Advanced) are enabled.

Then try again.

Good luck !
[BetterBatteryStats] Dsteppa:
Anyone can help me with my locks please?

It seems that the battery life is normal when I use the device, but when it should go into sleep mode it doesn't some times.

http://pastebin.com/2SyHV7jn
[BetterBatteryStats] noizy1234:
Will try thank you

Sent from my Nexus 4 themed with Goog Le Bean
[BetterBatteryStats] It_ler:
1. Please install BBS app v1.11.0.0.

2. Create an idle dump - while doing nothing/screen off all the time. Then it's easier to find the real battery "drainers".

Then try again.

Good luck !
[BetterBatteryStats] noizy1234:
Ok I'm back.. Here are my new stats http://db.tt/z7hJwTU9

Sns_periodic_wakelock is still happening even after disabling Google plus

Sent from my Nexus 4 themed with Goog Le Bean
[BetterBatteryStats] It_ler:
Still no alarm and network stats.

Please charge your phone, then, when turned on, unplug the charger/USB cable and start a new recording for at least 4 hours.

Do nothing with your phone during this time - leave the screen off.

Then save the BBS dump and attach the file into a new post here.

You should check if all location service options are disabled ... if not, please disable all location service options.

Good luck !
[BetterBatteryStats] picollo78:
YesI think i reset the battery stats.
[BetterBatteryStats] jrollette:
Try this now. Hope it is as great as it looks.
[BetterBatteryStats] Dsteppa:
Here you go sir:

http://pastebin.com/cnT2uJR0
[BetterBatteryStats] ikjadoon:
Hi! So, I'm trying to fix this problem: Wi-Fi set to turn off when I go to sleep, but being constantly on:

View attachment 1545150

View attachment 1545150

The few times Wi-Fi did turn off was when I disabled location update in Maps. But, now it's back to being permanently on?! :(

I don't have root, so no network stats. Will BetterBatteryStats be able to help me figure out what's keeping Wi-Fi on?

If so, here's an overnight log: http://db.tt/6Lc10L6c :)

For some reason, though, on my phone it says it's empty? Don't you just hit Dump to File? Or did I bugger this?
[BetterBatteryStats] ikjadoon:
Err, THIS is the problem. Image upload is broke on the app and my laptop is broken, too, lol.
[BetterBatteryStats] It_ler:
Oh ... "Since 31 s" that's short.

I think BBS didn't get the plug/unplug correctly.

Please try again with plug and unplug the charger/USB cable and then let the phone "sleep" for at least 4 hours to have a good duration for analysing.

---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------

Sorry, I can't get your BBS dump file - it's only 0 KB when I try to download it from dropbox.

Maybe you can attach it directly to your post when on a working PC ... or try to re-upload the dump file to dropbox.

P.S.:

Maybe wifi is only shown as on all the time as the wifi toggle was on. But the wifi active/using was interupted when phone was "sleeping"?!
[BetterBatteryStats] Dsteppa:
Argh! That damn thing.

I wish I had more time, going on vacation for 5 weeks, good thing I got 2 batteries.

Thanks for the help.

Who knows... by the time I'm back official JB is out for the Note and it has fixed most of these things.

Thanks anyways:):good:
[BetterBatteryStats] ikjadoon:
Thanks for the reply! :)

Shoot! It really is empty. I just hit Dump To File and copied the file from my root folder. Did I miss any steps? Do you need to be looking at "Since Unplugged" when you hit Dump to File? I picked each one and saved, but they're all empty! I'll try again when I get home.

I'm not sure I understand what you're saying about the Wi-Fi? It didn't turn off when I was using it... However, it's not just the toggle: when I wake up my phone, Wi-Fi was connected 99% of the time.

I'm pretty sure this was caused by the JB update I did last week. :( but, just can't pinpoint it.
[BetterBatteryStats] sirrah86:
Hey there,

i got a problem with my battery since a few days now. Its draining pretty damn fast from 100 to 30% in half a day with "normal" usage. I didnt do anything extraordinary or something that would drain my battery so fast as i didnt change anything on my usage.

I could nail it down to the process Google Framework Services. I tried to freeze it with Ti Pro which worked. But the drawback now is my Google Play store aint working anymore. So i enabled it again, but now it keeps sucking on my battery like the girls from brazzers... My Play store still aint working.

I pretty much tried anything already to get my Play Store back running again (Force Closed, Wiped Data Cache, Wipe Dalvik Cache, installed new, deleted Google Account and made it new, all the things i found on the internet) and nothing worked so war. First i had the RH-01 error and now i get "Server Error".

Also my phone wont go into Deep Sleep anymore.

I attached the dump file. Its only 30 mins long but if i'd make a longer one, it'd look the same.

- Rah
[BetterBatteryStats] carlos67:
Tasker and app synch'ing?

Hi Nobnut, very interested in this post. I use Tasker and have various profiles set. Was wondering how you set tasker up so that it only connects to data network when "the app requests data transfer". Sounds like such a profile would be the holy grail for keeping data off (and saving juice) and yet still allowing apps to update while screen is off.

I'm curious how such a profile would work - does the app broadcast it's intention to connect and tasker listens for that broadcast and activates the profile? or does tasker interogate the app to find out it's sync schedule and switch data accordingly to suit the app. Or, neither and some other way.

Can you post or pm a sample tasker profile that I can adapt to suit my own apps like stock email -3hr / Launcher pro friends widget - 3hr / stocks widget - 3hr / weather widget - 3hr. That's all I have looking for data (as far as I can tell :rolleyes:)

Actually, 2 things follow from my ramblings above........

1. Could tasker get everything to synch at the same time so only 1 data on session where all the apps synch at the same time. This would save multiple on-off data sessions. (I doubt this is possible, even though tasker is very versatile).

2. Thinking about it, what's the benefit of all this? It's the fact that while the data connection is disabled by tasker, the phone is not using juice trying to keep connected to the cell towers while screen off. Does a disabled data connection (i.e. airplane mode) reduce the amount of radiation emitted by the device?? That would be another benefit.

Look forward 2 your thoughts.
[BetterBatteryStats] fostirop:
Hi all

Can any one, please, help me understand what the Dialer wakelock I keep seeing refers to and if there is something I can do to stop it?

Ty
[BetterBatteryStats] carlos67:
Ha! Lol, you sarcy bugger you. :p

---------- Post added at 10:57 AM ---------- Previous post was at 10:45 AM ----------

So, forgive my naivety Nobnut, but this screams opportunity for a super dooper kernel developer (Supercurio, Hacre, Hardcore, Chainfire etc etc) to run the processor down much quicker following the release of a wakelock. Do different kernels handle this transistion to sleep state differently. Hmmm, I wonder about that. Maybe the kernel is passive in that it only does what's passed to it by the OS. In that case, it becomes ROM dependant.

Why does the OS/kernel take a "relatively" long time to put the device back to sleep following a wakelock release??? Is this an inherent flaw with Android?

Like I said, please forgive my naivety and annoying enthusiasm :o
[BetterBatteryStats] bu2askoor:
Hello guys,

while i am overall happy with my battery performance after using this app few weeks ago, but like everyone else i try t squeeze the battery as much as possible.

I have noticed that ratio on my awake vs screen on is about 2:1. For example right now i have 56 mins Awake (in the last 5 hours) vs 32 mins screen on. Btw my battery is at 80% (at work cannot play on the phone :) )

Does this look healthy? what is a good ratio of awake vs screen on?

Looking at my wake locks, nothing looks alarming. I will continue to run the battery down for another 9 hours and see result then and post a log file.
[BetterBatteryStats] nobnut:
I don't know to be honest, I'm out of my depth here.

Is it that the device itself is taking too long to go back to sleep... or that the process (app) is taking longer than necessary to satisfy the requirements for the device to enter sleep?

In other words, is the fault of the device (Android), or the fault of the app?

I don't know but I would say that mostly it is the app's fault. That's why we see some apps in BBS with literally thousands of patial wakelock counts but relatively low amounts of wake time attached... and other times we see apps with very few partial wakelocks but causing loads and loads of wake. If it was the Android system, I wouldn't expect to see this disparity. An example might be that one partial wakelock equates to 5 seconds of wake. Therefore 100 partial wakelocks would equate to 8.3 minutes of wake. We know it doesn't work in that linear manner.

I am suggesting also that different types of wakelock are causing different levels of 'sleep prevention'. E.g. a coarse network location request will cause less wake than perhaps a partial wakelock that requires both a coarse network location request AND some data to be downloaded and then an app updated (weather request).

It might be that something could be done kernelside but I am not sure how much effect it would have.

Another thing to consider is that when a user sees lots of partial wakelocks in their BBS results they have two choices (assuming it is not system related), they can either adjust the app's settings or remove the app altogether. This is not however where the biggest gains in battery life can be made. The biggest gains can be made when BBS identifies an app that will not allow the system to enter sleep (see attached screenshot I found on Google).
[BetterBatteryStats] vineetksirohi:
i needed such app
[BetterBatteryStats] chamonix:
I hope you guys don't think I am cheating on you :P

In fact I've just finished code freeze for 1.1. Features and Bug fixes on my list:

https://github.com/asksven/BetterBatteryStats/issues?milestone=5&state=open

The most important feature will be knowledge base. The first version will be in-app but is was designed to be scalable to fetch data from a wiki and I have one on github waiting.

It's a little too soon for a call for authors/pagers but I'd like to read your feedback on the structure of a KB article.

Here's my first thoughts, as always open for discussions (you guys are the power users)

ID: name derived from the wakelock name/package

Author(s): credits

Ranking: for future feedback through app

Speaking Name (of the class if not clear from ID)

Rationale: description of the origin / cause / root cause

Know actions: pattern for reducing / removing the wakelock. Goes from "deinstall, crap" to any instructions about further analysis (e.g. for AlaramManager) or settings to reduce / remove the cause (if any)

Known conditions of occurence: if the wakelock is known to occur under certain conditions (e.g. if using JD, if net coverage bad, if raoming, if data off and GPS on)

Related wakelocks: known inter-dependencies

References: list of links to more reading, solutions etc.

As always I'd be happy to read your feedback
[BetterBatteryStats] nobnut:
Sounds good. I've given it some thought and I can't add anything meaningful to that list right now.
[BetterBatteryStats] chamonix:
Very interesting points.

One one side it's the same discussion as about a super alaram manager for the kernel that clusters alarms to be processed as batches when the kernel wakes up anyway. This kind of strategy can be transposed to our problem when it comes to wake up the device and there are research on this. The basis is to define classes of alarms. Some are time-bound and can not be moved a bit because somehow critical "tics". On the other hand we have many things that are not time critical and if a mecahnism could cluster them to be triggered at once the device is awake it would reduce the number of wake/sleep cycles.

Note this discussion is not related to wakelocks at all.

My opinion is that wakelocks are misused in certain cases; a wakelock is required to make sure something happens before the phone gets asleep again. Updating the weather in a widget (no relation to waking up but an example to make my point) is not required to be handeled with a wakelock. If it succeeds while the phone is awake then fine, if not it may the next time while the user interacts more.Extending this we could also think of asynchronous wakelocks: an app like email wanting to send an IMAP keep-alive tells the system it should complete within 10 seconds. Either it succeeds within 10 seconds because coverage is good (waiting longer makes almost no sense) or the app is "lucky" because in parallel to that wakelock another longer coming from another app allows it to try a little longer.

Finally we have wakelocks that are required and should be there: when something is being synced (maybe after a conditional wakelock to try to get a connection) the process should be kept going as long as it needs to get finished at once.
[BetterBatteryStats] carlos67:
One thing is clear from Nobnut's, yours and my comments about wakelocks - there is a LOT of room for improving how they are handled by the system. Hell, I'm not even a dev but give me a day and I bet I could come up with a vastly more efficient method of handling them. Of course I couldn't code it to save my mother, but the logic of it would be much more battery friendly.

Why can't google manage this with their army of supergeeks :rolleyes:

Me thinks that google see battery life as an after thought.
[BetterBatteryStats] Plopz:
Hey guys, I'm back again with another problem...

Last night, I charged my phone to full just before I hit the sack, so I took it off the AC power to see how much nightly drain I get. (For the record, 2% overnight :P)

When I woke up in the morning I found I had a large period of awake time on my phone (as seen on the screenshot) in the middle of the night, but the wakelocks from BBS don't show anything out of the ordinary at all.

The largest contributor of wakelocks was AlarmManager, for 8 seconds. Surely I can't be reading the graph wrong, but that bar of awake state in the middle of the night can't be the span of 8 seconds. Looks more like 10-30 minutes to me.

Can anyone suggest how I go about finding what caused this period of awake?
[BetterBatteryStats] nobnut:
Not from the information you posted. It is possible that the wake wasn't caused by a wakelock.

Did the processes' battery usage screen (the one before the battery graph screen you posted) show any apps as having consumed extra juice? If the app causing the wake used a sufficiently high amount of power, it may have showed up in that list.

It also may have been a one off, in which case there is nothing you can do to control it. Besides, with that level of drain in just under a 10 hour period... do you really care? That equates to a battery life (in standby) of approximately 500 hours, or 20.8 days. Stop being greedy! :p
[BetterBatteryStats] shadowcaster31:
anyone experiencing the facebook app (latest version 1.7.1) causing wakelocks?

com.facebook.katana.Facebook is causing me 2-3 minutes of partial wakelocks even though i've set sync to never and notifications to off.
[BetterBatteryStats] sowen222:
Yup, third night in a row. GPS disabled at night (along with wifi+data), and 11 hours with only 2m total awake time. Looking more and more like an aGPS bug in Sensation's Android 2.3.4.

I'll turn GPS on again to see if the Awake time re-appears tonight, and report back...
[BetterBatteryStats] nobnut:
You could try freezing it and using a different Facecock client to see if it is any better.

I don't use Facecock, I can't comment on your findings.

Good find!
[BetterBatteryStats] KennyLegend:
I found this too but I also discovered if u click on chat and then go offline, the wakelocks stopped for me.

I also uninstalled BMW and my android os decreased. I know this is a Samsung bug that they have to fix and there's nothing we can do for it. just thought id report it as I get little or no wakelocks but my android os is high.

A little OT but might interest some.
[BetterBatteryStats] shadowcaster31:
that is an interesting suggestion. i will test it out. THANKS!
[BetterBatteryStats] sowen222:
Facecock? What a mess when you blow your nose! ;)
[BetterBatteryStats] nobnut:
Facecock®

Very messy.
[BetterBatteryStats] sowen222:
When facebook first came out, I thought, wouldn't it be great if instead of just a network of friends, you could also have a network of enemies... I would call it, sitonmyfacebook.com... unfortunately somebody had beaten me to the domain registration :eek:

(sorry for the OT ;))
[BetterBatteryStats] Dsteppa:
For people to really help you it's best to post a log while the phone attempts to sleep for at least 4hours.

(During that time don't use the phone)
[BetterBatteryStats] thechaoz:
Weird I let phone sit all night with its usual terrible battery drain. Saved logcat and dumpfile, dumpfile is empty for some reason though...hmmm

edit: tried doing several dumpfiles and nothing shows up in the text. Any reason or setting for this?
[BetterBatteryStats] chamonix:
What version are you using? If not 1.11 change versions, if 1.11 please provide a logcat when I can look at why the dump file creation fails
[BetterBatteryStats] chamonix:
Google Checkin (maps/places) keeps your phone awake. Using auto Checkin?
[BetterBatteryStats] thechaoz:
K I am using 1.12 b3...just tried again with stats but betterbattery stats is blank. Having over 20-25% drain per hour. Really need help, trying to google terms etc but I don't know whats legit, what's not and what I can do. So should I download 1.11, let it sit overnight and use that log for accurate interpretation?
[BetterBatteryStats] sirrah86:
Well, thats what i guessed but how can i check that? Im not certain about auto Checkin.
[BetterBatteryStats] CazeW:
Yes, that is what you should do. There is a bug in 1.12B3 which you've already noticed that it outputs empty dumps.

Switch to 1.11 if you are using 1.12B3.
[BetterBatteryStats] ikjadoon:
I have the same problem on 1.12, beta 3. I'll use 1.11 tonight and report back.

Thanks, CazeW.
[BetterBatteryStats] kainas555:
all done as requested here's a new dump
[BetterBatteryStats] kainas555:
all done as requested here's a new dumpView attachment BetterBatteryStats-2012-12-07_210212038.txt
[BetterBatteryStats] chantoine:
3 minutes for your dump is way too short...

Envoyé depuis mon GT-N7000 avec Tapatalk
[BetterBatteryStats] kramsac:
Hey

Hey guys.

First of all, thanks for the app; it give lots of information, and really worth the price :)

I have been losing around 2% per hour with screen off (airplane mode) on my nexus 7. Would anyone be kind enough to have a look at the log for me, and explain to me what is causing this drain? Thank you very much :)
[BetterBatteryStats] yahyoh:
com.ebay.mobile (): Wakeups: 331
Alarms: 331, Intent: com.ebay.mobile.service.DO_POLL
Alarms: 0, Intent: com.ebay.mobile.service.SET_PREFERENCES
Alarms: 0, Intent: com.ebay.mobile.service.POLL_SAVED_SEARCH

ur probelm with ebay ;)
[BetterBatteryStats] sirrah86:
Okay for some reason the problem fixed itself over night... Xmas miracles still happen! :D At least the "Checkin Handoff" process aint draining my battery anymore. I'm now down to 1.1%/hr and about 95% deep sleep.

I still got a problem with Play Store and Server Errors though...

Heres my actual dump file.

-Rah
[BetterBatteryStats] Casanoaa:
install latest bbs app. not beta.. and post an idle dump..

Genie (com.google.android.apps.genie.geniewidget.News & Wetter): 2 m 1 s (121 s) Count:3 1,0%
3gwp.ServiceLifeCheckr (net.rgruet.android.g3watchdogpro.3G Watchdog Pro): 1 m 4 s (64 s) Count:14 0,5%

disable the google geniewidget news & wetter ..

uninstall watchdogpro

---------- Post added at 04:43 PM ---------- Previous post was at 04:38 PM ----------

Install autostarter or gemini app manager.. and disable all autostarters in ebay app..

Search this thread next time before asking what is wrong after you read your dumb, Because many issues are discussed.