yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
Plug/unplug after a boot is a must. It has always been, at least if you wanted to get consistent readings. As an alternative there will be "since boot" for people needing it.

In next version no dumps will get created as long as the refs are not complete and there will be no more readings while plugged
[BetterBatteryStats] rwelsh09:
Sounds good, thanks!
[BetterBatteryStats] chamonix:
You should ask your favorite kernel dealer if that is on purpose. If the kernel does not deliver that info then there is no way to analyse it
[BetterBatteryStats] brownartist:
i will upload a more detailed dump file soon
[BetterBatteryStats] haloeight:
Thank you for the help and feedback. I am noticing as well overnight when my phone is plugged in, it is spending almost the entire time in 384mhz state, so something seems to be keeping it from sleeping while charging.
[BetterBatteryStats] boboev:
Following your advice, Karpfenhai, I really looked up for some more details about level 2 in OSI model networks.

At some time, however I came across several sources that refer to HSIC as something like an enhanced USB protocol. Here's one quotation:

"In 2007, the USB standard was expanded to allow product developers to use USB as a high speed chip-to-chip interface. This method of short range (under 10 cm) interchip connectivity leverages the existing USB infrastructure to reduce development time and cost. HSIC USB minimizes cost and saves power with a simple two wire interface.

It operates at low-voltage CMOS levels, replacing the traditional USB PHY."

and

"  Low-power digital HSIC interface offers a replacement for onboard host and device connection for analog USB bus cable"

So I was wondering could the l2_hsic wakelock be connected with imternal data transfers rather than wireless data. Any ideas?

Sent from my CleaNote V3.1 powered, GL Notecore v8 Std kerneled GT-N7000
[BetterBatteryStats] Karpfenhai:
wait, that's quite normal, phones do never enter deep sleep while charging!

So don't worry about that mate. :cool:

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Karpfenhai:
I've read this too, but if you search on google you will find lots of users who solved the issue by deleting a certain app, Droid sheep and dolphin are good examples.

Let's do the following, disable wifi, wait 20 sec and pull up bbs, normally the wakelock should disappear. (moved to deleted wl)

I have this wl too and i did not use USB since days.

Please confirm.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Karpfenhai:
I hope i don't forget a thing:D

-------- -------- -------- -------- --------

Silencing maps (preventing non user caused wakelocks)

1. Sign out and /or freeze latitude.

2. Disable all location based services:

3. Deny all maps related autostarts using a certain app like Gemini app manager or autostarts from playstore:

That's it!

Additional information:

-manual startup of maps will work anyhow, don't worry,

-navigation still works

-toggling gps on will show your current position on the map.

If you do it right, your alarm after almost 2 days can look like this:

As you can see, maps does not exist!

Hint: preventing all autostarts from maps should be enough, you probably don't need to get rid of the other stuff, try to start from point 3 in the beginning.

-------- -------- -------- -------- --------

Okay with this Sven?

Tapatalked from my Samsung GT9100
[BetterBatteryStats] chamonix:
Perfect, thanks. Starting from this I'd like to try forbidding Maps to do stuff that makes it go crazy without having to disable location services...
[BetterBatteryStats] Spiralzz:
Chamonix, BBS is asking for root permission repeatedly after plugging out the charger in CM10 (GT-I9100).... dunno if the problem is the app or from CM's side... just wanted to ask...
[BetterBatteryStats] shubham.dhand:
file://localhost/mnt/sdcard/BetterBatteryStats%201.txtl

can you just find out whats wrong with my phone's battery?
[BetterBatteryStats] BillGoss:
It also happens in CM10 on HTC Desire S.

Sent from my Desire S
[BetterBatteryStats] daggerxXxsin:
Hi, I've been reading this thread for quite a while and been following the recommendations for most of the common battery drainers. Can anyone take a look at this dump for me and tell me if there is anything i can improve on?

http://pastebin.com/ST9VHxq7
[BetterBatteryStats] tltan86:
Same for me :(

Sent from my bot crawling all over the web
[BetterBatteryStats] palmy999:
Hi Chamonix,

Please help review my BBS dump file. Wondering what's draining the battery under normal usage.

Thanks

Palmy
[BetterBatteryStats] Karpfenhai:
That's cute! The file is local, we will never see it this way. Please upload it.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] PholkLorr:
I have a syncloopwakelock with a count of 1278. Ive googled and searched on xda for solutions to this problem and there were many threads on this wakelock but 0 solution. Even a link to github doesn't tell me how to solve the problem.

It says:

Remove any unwanted accounts

Check the settings and remove any unwated options (contact sync)

Check the frequency of the sync and see if you really need it as defined <- how to check frequency of sync? Im on ICS and my autosync is set to off, so why is it trying to sync anyway?

Thanks!
[BetterBatteryStats] suku_patel_22:
User Super user 3.1.3 and SU binary 3.1.1

The latest super user 3.2 has issues
[BetterBatteryStats] kongkard:
Thank.:laugh:
[BetterBatteryStats] chamonix:
I am on it. The problem does not occur on every Rom but under certain circumstances the stored perms are not recognized by the su app. What Rom are you on and what su app are you using?
[BetterBatteryStats] chamonix:
3 minutes awake in 4 hours is nearly perfect. It that is you standard use then congrats and enjoy you better smartphone
[BetterBatteryStats] chamonix:
Google cloud backup has kept you phone awake for 11 hours. This may be a one time glitch but if you use an offline backup like titanium you may want to turn Google backup off. Please note that if a backup is running and you turn it off it won't stop so you should reboot after disabling it to make sure it doesn't go on
[BetterBatteryStats] Rob2222:
According CPU Spy, Galaxy S3 does enter Deep Sleep while charging. Is this not correct?

I know, S2 didn't entered deep sleep on charger.

@Chamonix:

If S3 enters deep sleep when connected (as it seems for me), would BBS have correct data in this case?

Or is there still something that prevents BBS from correct work when connected?

BR

Rob
[BetterBatteryStats] nobnut:
It is possible for some phones / ROMs / kernels to allow deep sleep under AC charge. They won't enter deep sleep under USB charge however.

The BBS data is correct :)
[BetterBatteryStats] Rob2222:
Aaah OK, thx. Then it is maybe Siyah Kernel doing this.

BR

Robert
[BetterBatteryStats] nobnut:
No sleep under USB charge is normal, if that is the issue, don't worry about it.
[BetterBatteryStats] daggerxXxsin:
Thank you for taking the time to look into it. You've helped a lot of people with your app but more so with your patience and informative answers. Keep up the good work! :thumbup:

Edit: in your opinion do apps like juice defender or green power make any difference in terms of actual power savings?
[BetterBatteryStats] lcaveyl:
Thank you chamonix,

I removed the above com.sec.spp.push (samsung push service) and Juice defender, BMW, removed all exchanged accounts.. i even swapped from Siyah to the latest CM9 kernel, now it seems slightly better but the OS is still using up a lot of resources which i dont understand why. in the past with those 'offending' software installed my Android OS wasnt as high as it is now, always used to be screen.

Am wondering is there anything more i should remove or should i just redo my S2?

Thanks again.
[BetterBatteryStats] chamonix:
Yes IMHO apps like JD and green power have a big impact on power saving..... in a negative way

n not control

I've explained the reasons many times: apps can not control other aps without telling them... let me take an example: an email app using IMAP push has a keep alive of 28 minutes. JD turns data off without knowing that and without tell that app. Result: the app goes into error handling, trying hard to reconnect and uses more power.
[BetterBatteryStats] chamonix:
For my taste that was a little to much change for one step so we need to start from scratch again as we can't see the effect of removing those apps. You log shows one reason for awake that is GTalk (GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 19 m 25 s (1165 s) Count:237 5.7%). Now GTalk had an outage so that may be a one time effect. You should re-run an idle session once GTalk is up-and-running for you again.
[BetterBatteryStats] chamonix:
Today will be a busy day: the Better Wifi on/off thread is up.

I'm going to flash my gnex now to check on that superuser-app-keeps-requesting-root thing
[BetterBatteryStats] Spiralzz:
I am on CM10, preview 2, with superuser v3.2....
[BetterBatteryStats] chamonix:
Ok we have a pattern here: I have got another detailed report also coming from a CM10 seed... downloading
[BetterBatteryStats] Rob2222:
No, I just say THAT my S3 goes(!) to deep sleep while AC charger connected.

I just don't know if it is cause I use Siyah or if stock FW uses deep sleep while connected also.

BR

Rob
[BetterBatteryStats] mariotme:
Bro I think it only occurs on JB (cm10)
[BetterBatteryStats] lcaveyl:
Sorry Chamonix, perhaps i should also have posted this log attached, it was me prior to me changing to cm9 and removing email accounts and disabling BMW midway.

but ok do as what you suggested above

Thank you.
[BetterBatteryStats] chamonix:
Besides GTalk that I explained earlier this dumpfile shows:

- exchange causing Wakeups and eakelocks

- nextapp.systempanel.r1 (?) looks like an active monitoring app causing lots of wakeups

More once GTalk has settled
[BetterBatteryStats] mammarf:
Fyi, i don't have gtalk installed so don't know why i have so many wakeups for it. How do i get rid of it?
[BetterBatteryStats] chamonix:
This reading is not optimal for a start as it is mixed mode idle and use. That makes it very difficult is isolate causes from symptoms.

One this is for sure: Facebook is the main drainer. Not only does it wake up your device in average about once a minute but it has also transfered more data than any other app. You must decide if you want to live with that.

If you take action to get rid of Facebook and use an alternative please feel free to repost but post an idle dump this time
[BetterBatteryStats] Digital Analogy:
Hey all.

I've gotten most of my battery drainers nailed down and under control. I am down to a few final things that I am having trouble identifying.

In my many google searches I've found the following:

mmc2_detect and mmc1_detect

I've found alot of references to the above entries. However, finding an exact cause has been difficult due to the sheer number of results, most of which are lines of code or other members from this site posting their dump files. All I've been able to find so far is a lot of speculation but no definitive answers.​

bam_dmux_wakelock

This one has been the hardest to find info on. Alot of my google searches return very few results depending on how I word the search. What I did find is that "dmux" is shorthand for "demultiplexer". I'm not sure which apps may require a demultiplexer so this one has stumped me.​

sec-battery-monitor

I found this http://xdaforums.com/showpost.php?p=29347426&postcount=6974

Is it safe to assume I can ignore this entry based on the info in the above post?​

Now for the dump file. I unplugged the phone when I went to sleep and generated the dump file as soon as I woke up:
[BetterBatteryStats] chamonix:
SuperUser problems on some CM10 based ROMs

I have got a few mails and some feedback here about BBS misbehaving in a sense that SuperUser kept on asking for rights again and again (the reports were on unplug). The problem seemed to be related to CM10 based ROMs.

I have flashed my GNEX with one of those ROMs (EUROSKANK based on CM10) and was able to reproduce the problem. Interestingly the log shows that BBS is granted rights again and again but next time 'su' is accessed it still asks.

The version of SuperUser that came pre-installed was 3.2.

Here's what I did:

- I flashed SuperSU (SuperUser got removed): everything worked fine

- I flashed SuperUser 3.1.3 (SuperSU got removed): everything worked fine from that moment

My conclusions:

- either there is a problem with the changes introduced in SuperUser 3.2 (if you see the changelog there are some changes related to CM)

- the way SuperUser was preinstalled is the problem

- the problem is in no way related to BBS

I hope this helped. I won't provide any links to any flashable packages. I suggest that you take this to the ROM threads and let the devs know, they know how to fix it.
[BetterBatteryStats] alexinna:
How did you achieve "3 minutes awake in 4 hours"? Can you please provide basic settings you are using?

Thanks in advance.
[BetterBatteryStats] poundesville:
My apology.. I think my wordings were pretty bad and therefore it gave you the wrong understanding. Let's re-write.

I could not send any latest dump file yesterday, as I was charging my phone and it was still heavily used.

But, I've posted my dump file when I was on ICS ROM - that was the last ICS ROM I had before I decided to move to GB ROM.

Here's the dump file I had on my phone while it was on ICS - I'll be returning to this ICS ROM tomorrow.

If I read this right - in terms of "minutes", my phone wakelocks are not that big. But the number of counts in alarm manager, RIL and exchange were high. The kernel wakelocks are also high on wlan_rx_wake , wlan_wake and l2_hsic.

So what should I do to reduce these ? I 'm no longer using Exhange now, i'm using Touchdown app. not sure what else can be done to reduce the rest..
[BetterBatteryStats] daggerxXxsin:
Wouldn't that be avoided by adding a rule to maintain connection as long as there is data traffic?
[BetterBatteryStats] mzaur:
Not sure if this has already been mentioned. I am on 1.9 and the stats are not displaying correctly. Clearing app data didn't help.
[BetterBatteryStats] chamonix:
And what happens then?

The problem with JD and other apps trying to control data traffic "from outside" is that other apps have no way of knowing that.

Example: JD opens data 5 minutes every hour at the hour.

An app is using poll and wakes up at 15 past, finds no data connection (exception situation). What does the app do; it may set an alarm to wake up 5 minutes later and retry again, repeating that for 45 minutes till it get the connection. The app woke up 10 times (10 alarms) and worst case held a wakelock for retrying during one minute ( that makes 10 minutes of wakelock).

So let's recap: it this app would behave like that it would have caused 10 minutes of partial wakelock and 10 wakeups in 45 minutes. Without JD it would have woken up once, done it's thing and been quite for one hour.

The problem here is that there is no back-coupling from JD to the apps (as JD is not a framework part). If the apps have not been designed in a way that takes into account that JD may run the overhead caused (by exception handling, that is probably not the most tested part of an app) the whole concept fails.
[BetterBatteryStats] chamonix:
You are not the only one reporting this problem but I can't reproduce. Could you please provide a logcat?
[BetterBatteryStats] chamonix:
wlan_rx is the easiest one: turn wifi off

com.android.exchange (): Wakeups: 32

yes you are still using exchange and that causes wakeups
[BetterBatteryStats] daggerxXxsin:
Okay that clears everything up for me :D

Gotta stop being lazy and manage the connections myself. ;)
[BetterBatteryStats] pablo216:
Hey guys. I totally love this program and use it all the time.

But could you please help me understanding this BBS? I think my wakelocks aren't so crazy, it's the kernel ones that puzzle me.

Thanks in advance.
[BetterBatteryStats] chamonix:
I suggest that you move to 1.9, it will help you discover what hides behind multipdp (data tranfer) responsible for most of your awake time.

Are you syncing multiple accounts with touchdown? I noticed multiple occurrences of it in the partial wakelocks
[BetterBatteryStats] meaxx88:
Could someone please check my bbs file? I added last 4 logs. Thanks in advance!
[BetterBatteryStats] Lownita:
Hi,

I used the phone for some time as you said! I attached the logfile, would be great if you could take a look at it again :) I also included some screenshots which were taken during that period (a bit later). Obviously Android OS is eating a looot of battery.

Thanks!!!!
[BetterBatteryStats] chamonix:
Same as my previous remark. Besides the fact that you have been running network speedtests during that run the main cause of awake / data traffic / wakeup is facebook. If you are not ready to look for an alternative there are still some small areas for improvement but as long as the top drain is running it makes no sense to analyse the logs further
[BetterBatteryStats] chamonix:
Why are you posting 4 logs? 3 of them are useless, please read post #2 about idle resdings.

What I see is that

a) you are using an outdated version of BBS

b) your phone detects the charger to be connected event when it's not.

Can you please check if your USB connector is not dusty or if there is something stuck in it.

Then update BBS, study post #2 and provide one representative reading
[BetterBatteryStats] chamonix:
Syncloop wakelock is a wakelock help while your accouts are doing their sync. It can be caused by any account that is active, either google's or some third party accounts like the contact sync from whatsapp. The cause of it is also difficult to nail:

- a sync is supposed to go fast

- a sync will get slow and cause high wakelock times when the phone has a bad connection

- a sync will get slow and cause high wakelock times when the cloud service is under load or non responsive

As for every cloud based service it consists of many tiers and the diag is not simple. If the problem persists the easiest way to proceed is turn off all accounts and on one by one till the wakelock raises
[BetterBatteryStats] chamonix:
That was the old issue (in fact issue #1) as the batteryinfo service from android stopped working. In fact it works but is shows only the stats for the UID asking for it (in the case of BBS it would return only BBS' stats). This bug was introduced and is still present in 4.1, making that part of batteryinfo quite unusable.

Now in BBS 1.9 I have introduced a new method for reading those stats, doing the same thing as the code from the batteryinfo service does but with a su access, allowing me to read all the stats for all UIDs.

Thus is done by reading

/proc/net/xt_qtaguid/stats

If this does not work on a device and assuming the phone is rooted that would mean:

a) the kernel does not implement those stats

b) the file format (or file name) was changed

In that case I would be interested in getting more info about that ROM and on a) and b).
[BetterBatteryStats] chamonix:
What is "this" and what is "perflock"?
[BetterBatteryStats] Karpfenhai:
Not total manually, give Llama a shot, its very battery friendly and can manage your connections as well, time and location based.

Good luck!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] daggerxXxsin:
It says llama is not compatible with my device :confused:
[BetterBatteryStats] pablo216:
Thanks, I already updated and will leave it gathering data again.

Just the one account in touchdown, but the processes seemed ok, my main concerns are in kernel wakelocks, not so much the partial ones that are easy to diagnose.
[BetterBatteryStats] bervin:
https://www.dropbox.com/s/vrs69vrful6jddj/BetterBatteryStats-2012-07-29_050144297.txt

can someone take a look and help me with my alarms.. what are the causes for those wake ups?
[BetterBatteryStats] chamonix:
OK I have been doing some testing and couldn't find the inconsistency yet:

- there are two default stats preferences, one for opening the app from the icon, one for opening the app from the widgets

- there is a behavior telling the app to save the current state and restore it when opened later

For what I have tested:

- first call of app from icon sets the stat as defined in the general prefs

- if I change the stat to another, close the app, reopen it from the icon it gets back to the one I set manually before

- if I open the app from the widget the pref as defined in the widget settings is always restore

Can you confirm in what cases it's inconsistent to these rules in your case?
[BetterBatteryStats] Karpfenhai:
Really? Incompatible with your device or incompatible with your custom dpi settings (market issue)?

Friends of mine are running it on nexus with no issues..

Get a modded market then or the app from another source..

:D

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Karpfenhai:
I would, but...

Tapatalked from my Samsung GT9100
[BetterBatteryStats] daggerxXxsin:
I uninstalled the market update and it went through fine. Tweaking it now :thumbup:
[BetterBatteryStats] Digital Analogy:
I just realized I didn't post my help request as instructed in the original post. I've made the corrections (posted dump as attachment). If you have a moment please see post #7092 and let me know if there's anything you see that I could improve on.

Thanks.
[BetterBatteryStats] boboev:
As a matter of fact I was not thinking of USB as some sort of OTG dongle or USB cable. I was thinking if this HSIC is not in fact the protocol or standard that is used in the smartphone's internal data transfers from and to the sdcard (both internal and external).

Anyway, I have tried what you told me to. The result is interesting:

- after disabling wifi, short plug-in for resering the kernel lock stats I got 7s of l2_hsic wakelock over the next 2 minutes;

- then I disabled 3g data and again reset the KL ststs - 1s l2_hsic wakelock for 2 minutes

- I turned wifi back on and then I got some 8s l2_hsic quite quickly.

There are two things that look strange to me:

1. If this wakelock is intenet data transfer related, why even witbout wifi and 3g I continue having this wakelock. It was 1sec only but it was over only 2 minutes and isn't even 1s strange when there is NO data whatsoever being sent or received

2. If this is something related to data transfer why tgis wakelock does not reach let's say 2 hours over a longer time lapse. It looks as though this happens only sometime soon after device unplugging and then stops being that intense.

Sent from my CleaNote V3.1 powered, GL Notecore v8 Std kerneled GT-N7000
[BetterBatteryStats] Karpfenhai:
Its not that easy, but its worth it, works like a charm later.. Don't give up!

What a pity,i really liked the idea of external storage handled as usb attached storage ..

But even after cross transferring larger data files the wl does not grow.. :confused:

same for dl-ing from browser to external storage, no wakelock..

Please try to work this out somehow, thx mate!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] daggerxXxsin:
It's kinda like Tasker only easier to understand :D

I've setup some basic actions and so far i am enjoying it :)
[BetterBatteryStats] eNemy-:
My battery drains fast with Devil Kernel. I asked on kernels topic and was suggested to use BBS.

Kinda noob here but please can somebody look at my dump file and tell me if anything is wrong?

I can get almost double battery time with an other kernel but it has other issues :S

Thanks in advance.
[BetterBatteryStats] :
I cant get along with the battery life of my Huawei Honor running ICS. The battery drains too fast while screen is off IMHO. I would appreciate if someone can take a look over the dump hoping for advice to fix something.

Screen was off the entire time, lost 8% in 4 hours on 2G. It is way more without network limit.

What is "GTALK" doing in there? Never used it. Also I have no idea what "DATA5" could be.

Thanks in advance!