yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] jeremysherriff:
Not that I know of. You might be able to use a different app for the same purpose.

If you google-search for "facebook ics sync" there was a whole bunch of discussions around how to get FB to sync on ICS ROM's, including suggestions of other apps that can do the sync. That might be a good way forward.

PS if you find something cool... let us know!

---------- Post added at 12:50 PM ---------- Previous post was at 12:50 PM ----------

Are you using latest version?
[BetterBatteryStats] lexluthor:
Yep, "other usage". I'd love to be able to see that exact data on GB.

Any chance you can dig that out of wherever it is to display in your app? Certainly, running time, being the most important.
[BetterBatteryStats] daveid:
Just for ****s and giggles, I installed this on my Acer Iconia A500 running 3.1. Everything looks good, thanks!
[BetterBatteryStats] thebeardedchild:
So in the future, will there be a more graphical display of battery usage stats and such? It's a little harder for me to see which apps are running rogue when I'm just comparing numbers...

Also, I'm wondering if a "since power on" could be a reference point for stats. Or is it? I'm just seeing since charged, unplugged, then last and current...dunno what all of them mean.
[BetterBatteryStats] chamonix:
We have the original code so it's "only" a matter of porting it and seeing if it runs correctly on GB. Feature request added, I'll keep you updated
[BetterBatteryStats] chamonix:
Thanks for the feedback! I'll add 3.1 under supported versions
[BetterBatteryStats] chamonix:
I'm still a little puzzled by "last" and "current" too; the names come from the original constants but I agree that they are not speaking at all.

Added as a feature request.

I will look into the time axis but I'm not very confident that I can correlate e.g. a wakelock with the time it was set and lifted. Brandall had a similar question and I already looked into the timers without finding anything. But I'll take it up as a feature request anyway.
[BetterBatteryStats] vault1965:
Thanks for great app. One question, what exactly is backup process in Android system? I have this process at top of wakelock activity with one hour where other stuff is barely couple of minutes.
[BetterBatteryStats] chamonix:
I think meant is the "android backup service" (http://code.google.com/android/backup/index.html). It is a service that offers cloud backup/restore of your settings and offers an API for other apps to do the same (http://developer.android.com/guide/topics/data/backup.html).

AFAIK you can turn it off (but will lose the automatic backup) under Setting -> Privacy ->Back up my data.

If it's the right service the wakelocks should stop.

Backups are useful though but no need to do it in the cloud, I'd recommend scheduling a regular backup using titanium instead (that's my setting).

I'd be happy if you could confirm and tell me the exact name of the service for me to take that info up in the how-to post of this thread
[BetterBatteryStats] R3wt3d:
Hi

Just installed this...looks interesting, thanks.

>And here's the point: my SGS2 drains about 2-10 mAh where it was up at 20-100 mAh before I started cleaning stuff up.

Can you tell me how you found out the amount?

I'm using sgs2 aswell and I hate to see that battery drains even I do not use it during work.

Keep up the good work! cheers!
[BetterBatteryStats] nobnut:
There are many apps providing battery data on the Market. Battery Monitor Widget is one of them :)

@Chamonix congratulations on making the XDA news page and tweet!

Sent from my HTC Flyer using vodka
[BetterBatteryStats] chamonix:
I'm using "Battery Monitor Widget" to monitor battery drain (updating first post)
[BetterBatteryStats] solrac.dc:
This combined with Juice Defender, JuicePlotter and Autokiller is doing wonderfully on my HTC Sensation!!!

Gracias Amigo!!! :D
[BetterBatteryStats] fredcom2:
Hi,

Thanks for your application.

I've 2 HD2, both with CM7.

One is experienced battery drain from times to times (say every 2 days) and I can live with that, but the second(my wife's ;-) ) experienced severe battery drains each days, and I never found what was the problem.

But I'm not sure to understand how to use the information given by BetterBatteryStats!

What should I monitor?

With which settings (Wakelocks, since charged, last, current, since unplugged?)

How analyse the information (the more "seconds", the bad)?

I appologise for all these questions, but as a newbies I try to learn swimming.
[BetterBatteryStats] nobnut:
After your (wife's) device has been asleep for an hour or two. have a look at all of the settings. They can all cause battery drain!

When you start to understand what is causing yours, you can either change the app's settings (sync times etc), or you can uninstall the app and use something else instead :)
[BetterBatteryStats] TheNetwork:
No QR code? What the hell dude that would cut the time in half that it takes to get this app on my phone.
[BetterBatteryStats] nobnut:
Thank you for this very helpful post.
[BetterBatteryStats] dryhte:
wakelocks

Thanks for the app, looks interesting.

Am I right to suppose that this ('wakelocks' list) will help me find out why my phone is 'awake' for hours while the screen is off? (sometimes I have that for hours on end, sometimes not at all, without installing or deleting any programs...) :confused:
[BetterBatteryStats] Szczepanik:
Better Battery Apps

First thank you for this Better Battery Stats.

Apps that various people have said that may cause problems and alternatives are:

stock email apk = use k9 instead

google maps = use locus maps instead

old market place = use new market place instead

Cheers

Tom

P.S. Found this thread from mention in xda-developers.com/android/tune-your-androids-battery-life-with-betterbatterystats/
[BetterBatteryStats] cmsc:
Very useful app, thanks!
[BetterBatteryStats] tltester:
Hi.

First - a lot of thanks for a very useful app.

May be you can help me to determine a root of a drain on my newly purchased Galaxy S2. The drain is absolutely enormous. Graph looks like something holds a wake lock for hours. Using your app I've found that the offender is something called network-location-cell-update. Where am I going from here, what to check?

Thanks.
[BetterBatteryStats] jbdeq:
Sorry for the Noobish question but which file do I replace - the only one i see is calendarprovider.apk ? Have tried pasting files like this into system/apps before but always get "installation not done" or something like that..
[BetterBatteryStats] DrunkFuX666:
What's betterln...?? If its a app I can't see it on the market... and uhhh... I wish I could point you in the right direction... ill see what I can find... but im not the brightest of fellows when it comes to this stuff :p
[BetterBatteryStats] DrunkFuX666:
Ok so after using my phone a while after another charge having uninstalled the led thing this is what's happening :S

I accidentally left the wifi on I think but it wasn't connected to any network I believe since I was out...

This is why I thought it wasn't the LED thing cuz when I had previously uninstalled it, the phone still stayed awake...
[BetterBatteryStats] DrunkFuX666:
Im not sure nut I think that is more related to the SGS 2 and wont work for everyone...??? Me either because I have a Atrix... correct me if im wrong...
[BetterBatteryStats] nobnut:
Paste it into system/app and set the file permissions to rw-r--r-- using Root Explorer, then restart.

I am not convinced that this will have much effect. The wakelocks appear to be caused at a much deeper level than just the calendar apk. Give it a try though :)

EDIT: Sorry, I forgot to add that you should freeze the default calendar as well (don't delete it). I have tried this a while ago and I also swapped the Samsung email client for the AOSP email client to try and reduce wakelocks... it didn't work (at least for me).
[BetterBatteryStats] nobnut:
You are right ;)
[BetterBatteryStats] nobnut:
Well, it certainly looks as though Handcent is killing your phone's ability to sleep. I have never used Handcent, but I don't believe that this is normal. I see you are also taking a kicking from the Alarm Manager... have a look back in this thread for advice about that.

As for Handcent, try freezing it, or uninstalling it for 24 hours and see if this solves the problem. I have no idea what you might be able to adjust within the app settings to improve battery life as, like I say, I don't use it. I know it is very popular and I am sure that we would all know about it if it naturally caused this kind of battery grief... everyone would be complaining.

Hopefully someone else will be able to come along and give you some specific Handcent advice as I haven't got a clue about it :o
[BetterBatteryStats] chamonix:
I changed the wording to be more precise: wakelock is a generic term, partial wakelocks are the ones keeping the phone from sleeping.

As per the bars: they tell the same story as the percentages, doc is on the way :)
[BetterBatteryStats] chamonix:
Betterln is a not yet released backlight notification supporting (m) any phones
[BetterBatteryStats] chamonix:
Lol. You found a typo and can keep it ;-)
[BetterBatteryStats] chamonix:
I have used Handcent for a while and never had a problem like that. This behaviour together with AlarmManager and the experience from the calendar app tells me there may something related to repeated notifications like the snooze in cal

If this does not apply I'm on the wrong trail but may it be that you use the function to repeatedly remind you of an unread incoming sms that was not read? If yes it looks like the wakelock is not released between reminders and I bet the dev would like to know about that. Again if it does not apply I am misinterpreting...
[BetterBatteryStats] carlos67:
Wow! I stay away from XDA for a day and come back and find this thread has advanced 5 pages.

I have noticed the following on a regular basis now for 1-2 weeks. After rebooting the phone and letting it sleep (i.e. no usage and screen off) the current drain is initially very low sometimes only 1mA for around 2 hours.

But then it begins to climb and it only gets higher even though the phone stays unused with screen off. If I have not opened any apps and the screen remains off, why does the current draw decide to increase, sometimes up to 30~40 mA from 1mA. When I look at the time of the increase from 1mA to whatever mA, the phone was asleep when the change happens.

Typical usage pattern for me:-

1. Phone powered on, screen off straight away. wifi or 3g on (doesn't matter - same result) long sync intervals set for email(4 hrs) weather(3 hrs) stocks(3hrs) Facebook (4 hrs) nothing else.

2. 2 hours later, screen on to check usage - continous 1mA(every 5 mins) I am happy- screen straight off. Battery still between 100~99%:D

3. 2 hours further on - screen on to check again, current draw now up to anything between 12~48mA. Usually the increase happened shortly after the first screen on but stays high thereafter.

Only way to get it back down to 1mA is a reboot, otherwise stays stubbornly high (relatively, considering the phone is "asleep").

Why does this change happen for no obvious reason?

Could it be that one of my syncs is failing for some reason and just keeps trying maybe, continously drawing Milliamps?

I am using autostarts and have aggresively disabled a lot of things starting up. Also lots of bloat frozen or uninstalled in TB.

Edit: with the phone on but screen off for 13 hours I would expect 0.5~1% drop/hr but it has dropped 2%/hr. This is still ok, but would love to know how to keep it at 1mA draw which it easily manages for 1.5~2.5 hours following a reboot/power on.
[BetterBatteryStats] Szczepanik:
Wakelocks Wiki?

Would a Wakelocks Wiki on xda-developers site be useful to help record info? The wiki format allows anyone to contribute and you can link directly to a topic such as a particular wakelock from a post or possibly even the app.

I would be happy to start the wiki - here are some example wikis I made earlier:

http://xdaforums.com/wiki/index.php?title=Android_Loader

http://xdaforums.com/wiki/index.php?title=Artemis_DumpedRoms

http://xdaforums.com/wiki/index.php?title=Portadroid

http://xdaforums.com/wiki/index.php?title=Xtask

If you like the idea and are willing to contribute to a list of wakelocks with related links and hints to get rid of them simply press the thanks button and if enough people agree then I will create wakelocks for us all to contribute to.

Cheers

Tom
[BetterBatteryStats] Plopz:
The same thing happened to me last night. I stopped using my phone sometime around 22:00 last night and went to bed shortly after. I woke up 8 hours later to find that my battery had dropped 10% (a lot higher than I usually get over night).

Checking my battery monitor widget, it's said that on the stroke of midnight, something's triggered my phone to draw a huge amount of current. The time might be irrelevant and what could be a more relevant point is that it started to draw that current only after it's current draw was down at 1mA in the previous 5 minutes. Weird!
[BetterBatteryStats] nobnut:
Yes, this is annoying and does happen sometimes. I have no definitive proof, but on the rare occasion I see this on my phone, I attribute it to the (any) email app. Specifically an email app on push. I don't seem to get it until I have conducted a manual sync (or just opened the app which syncs it automatically). The truth is however that there could be many other causes.

I notice from your screenshots that you have a frequent wake issue (lots of little blue bars). This is the same pattern as caused by Latitude and some email apps. In your case, it might be caused by the GTalk process as it appears to be your highest contributor to wake.

If you want, to test this, you could freeze it for a while and see how it goes. You could also try the same with email.

To me this sounds like a very useful idea! I don't know however what Chamonix had in mind for future development and whatever level of support. Let's see what he thinks but it gets my thumbs up and a thanks press for your efforts ;)

...and now you need to find out what happened at Midnight. Check your syncs, alarms and anything else which may have triggered activity.

Ask yourself questions like "does it do this every night?".

What were the processes (and partial wakelocks) displayed in BBS?

What did your battery graph look like in the morning? Was it a solid blue line after midnight, or a series of broken thinner lines (the solid ones are easier to track down).

Was WiFi on overnight?

What is your mobile reception like?

At the moment, with the information we have, all we know that there is a problem, we don't have enough to suggest a solution. But the problem is actually an opportunity in disguise... an opportunity to make your battery last longer ;)
[BetterBatteryStats] Plopz:
I've been in the process of figuring out what happened at midnight (while at work heh), but I'm at a loss as to find what application or process was specifically running at that exact time.

My syncs are good, I have nothing periodically updating. Everything is manually updated; I close all my email/fb/twitter apps when I turn the screen off, and I've turned the autorun off on a lot of apps I don't need in the background with Gemini (great prog btw, thanks for the tip!)

My Wifi was off and so was my 3G; mobile reception is really good in my house so I don't think my radio was constantly looking for signals.

Looking at BBS, there isn't anything peculiar looking to me, but then again I've got an untrained eye to these things. I've posted some graphs and data for others to analyse and suggest things to me.

But in the grand scheme of things, over the course of a day, 3 minutes of wakelock is negligible right? Even if it was a continous 3 minutes 38 seconds straight wakelocks (can that happen?) it wouldn't draw 280mA would it? That sort of current draw would be akin to Quadrant running a full benchmark, surely!

Cheers,

P
[BetterBatteryStats] nobnut:
1. True, in the grand scheme of things, that is good. Sometimes we have to be pragmatic and just accept a certain level of (inevitable) drain above our wishes.

2. Yes, that can happen, there are things you can do to prevent your device sleeping altogether if you want ;)

3. If you run some 3D games, you can get drain of over 600mA... sometimes up to 900.

One last thing, you need to adjust the battery capacity within Battery Monitor Widget. You are using an SGSII I believe. If so, go into BMW settings and change it from the default 1,200mA to 1,650mA. It is not automatically detected on all/most Samsung phones. You won't get accurate statistics until you do ;)
[BetterBatteryStats] DrunkFuX666:
Ahh I see... are you the creator of BLN by any chance?? If I remember correctly that was only for the softkey backlights to turn on... atleast on my SGS... not really taking control of the notification LED to change colors assign to apps etc... also think the kernel had to support it to work...

But yea if you can make one for the LED of any phone that would be awesome ...!!
[BetterBatteryStats] DrunkFuX666:
Thanks chamonix... I think your on the right path... I don't have any alarms or even reminders set on my phone... so I don't get what the alarm manager is doing... makes no sense to me... I can't even get facebook calendar to sync with my phones calendar ...!!!

As for the reminders for the Handcent... I have the led notification on to blink the light... that's about it... not sure if that light would cause it to keep the whole thing awake... but im sure you would know... lol

There was recently a update for handcent that had something about ... lemme go see...

"Fix cpu usage and some force close and wait issue when MMS"...

I updated but I think this isn't the same issue... so you think I should say something to the developer or is it normal for a simple led to keep the phone awake...??

Is there any solution to this alarm manager thing by the way...?? Seems to be a GB thing since im having the issue on my Atrix while others on the SGS 2...??
[BetterBatteryStats] nobnut:
Chamonix is better placed to answer this than me, but there is a very strong probability that this is the cause.

You can test this by disbling the notification, restart, leave the device in standby and see what happens.
[BetterBatteryStats] cossax:
I usually get ~3 days out of my phone with light to medium usage (CheckRom v6, speedmod k2-21, KI3 modem, ondemand governor and noop I/O scheduler). However, some days I just seem to get a ridiculous run on my battery (like today) where instead of 1-3% an hour, it drops 10% an hour or more. It was fine for the first 4/5/6 hours but fell off a cliff battery wise at lunch and then again later on in the evening. Android OS is listed at 88% (~8 hours) and display (~15 minutes) at 2%.

I've no idea why this is but it seems to happen every few days and it can usually be fixed by a restart - that, obviously, doesn't solve the root problem.

Looking at the dump (full dump attached) it appears to be kernel wakelocks ("svnet" (3 h 55 m 18 s), "wlan_rx_wake" (2 h 50 m 36 s), "wlan_wake" (2 h 13 m 12 s), "sec-battery-monitor" (2 h 11 m 40 s) and "svnet-dormancy" (1 h 25 s)) that are the issue but they've happened to me (in pretty much identical fashion) on speedmod k2-19, darknight, Siyah and neak so I can't pin it down. I don't have the dumps for them as I wasn't thinking at the time, apologies. It's happened to me on CheckRom v4 and v6 and may have happened on Litening Rom as well (been quite a while since I used it so I don't quite recall). :o

Am I missing some obvious cause or can anyone point a noob in the right direction (changing rom/kernel/modem?) to solve this issue?
[BetterBatteryStats] rdg151:
Just got done syncing my facebook contacts to my gmail contacts on my laptop. Now I can turn the facebook contact sync off on my phone. If you search, "google contact sync heart of angel", you'll find the program I used. It works very well.
[BetterBatteryStats] jeremysherriff:
Hi. You're right with your thoughts, but the root cause is likely to be something you can't control. All those wakelocks revolve around data and cell reception, so modem stuff but also wifi. You have likely got into a situation where there have been incoming data packets that have caused your phone to wake often, or, something has gone awry with a data connection (usually a push-mode connection) that has caused continuous data retries. Could be a misbehaving DHCP server, a server in maintenance somewhere in the gmail cloud, a firewall dropping packets because of some triggered intrusion-protection rule, anything weird like that.

Frustratingly, I expect that Android will capture info as to what user process made the kernel call, so that we could track it easily. Unfortunately not, some apps do and some don't, so in a case like yours we end up making educated guesses.

Given that you have seen the same behaviour in other ROM's, I'm going to suggest that it's some push service that you use on every ROM, like your main email account.

The best way around it is to try and limit your exposure to the problem. Use frequent pull/sync instead of push mode. Set wifi to go to sleep when your screen is off. It could be related to 3g coverage issues, so you could switch to 2g when you aren'ty actively using data (a bit extreme perhaps? but I do have to do this at my work..)

A longer (and harder) road is to work through your various apps that use data, removing/disabling them one by one until you figure out which one it is. But, it could be more than one app, or it could be the way your hardware deals with poor connectivity situations so no specific app will ever be identified.

You could try changing modems, or changing kernels, but I'm guessing this isn't the only kernel you have used? And probably not the only modem either. So it is unlikely to help.

HTH !!
[BetterBatteryStats] glennk:
Wakelock time vs awake time

Hi,

Just for my understanding of this app and the way it works;

In the attached dump, Since unplugged after a night on battery with "nothing on" but not in flight mode you can see that I have, in 6h22min, 137 seconds of awake time, 30 s screen on and a little wifi before I closed that after reboot.

In the Wakelocks section, the AlarmManager have close to 3 hours of wakelock, 43% of time on battery.

Shouldn't the system report awake time during wakelocks?

Otherwise I find my report from BetterBatteryStats as good. To much com.android.email wakelocks, but I can live with that if I just have 3% drain in nearle 6,5 hours.

/Glenn
[BetterBatteryStats] d3l1:
Yes, I even uninstalled it and installed it again, still it FCs sometimes while using it, sometimes after closing it.
[BetterBatteryStats] jeremysherriff:
Can you grab a logcat and post it here?
[BetterBatteryStats] cossax:
Hi,

The reply is much appreciated and I'll give your suggestion a go - the only issue is it normally takes a few days to happen so I shall have to wait!

Given I have only one non-mainstream app that's likely to be using Push so will have a look at that.

Outside of that, my home router is provided by my ISP and locked down so alas I can't (easily) investigate that but will see what I can do.

Thanks!