yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Kocai:
On standby whatsapp shouldn't drain your battery. I've been using it for almost one and half year and as far I can tell it's not battery hog. You can check it with BBS. And of course it'll drain your battery if you're using it continuously.
[BetterBatteryStats] Noed:
Yeah, I've tested a bunch of IM apps and WhatsApp is the only one I keep running because it use very little cpu/mem.

I also have IMO and Skype, but with autostarts disabled, I only open eventually.
[BetterBatteryStats] gaui:
I'm not sure what is going on here... mhl_wake_lock? Never heard of it.

http://pastebin.com/6K5FLEXC

Using WanamLite V4.0 w/ stock kernel
[BetterBatteryStats] Karpfenhai:
Whatsapp was a drainer but they continually improved the design and in the meantime (a couple of month) the issues are gone. Don't forget to update :)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] eruben:
Can anyone help translating dump file? I had 10 hour awake over the night.

http://db.tt/lYcSgbsW
[BetterBatteryStats] -earth-:
Hello, i would say, this is the reason:

(com.mobilefootie.wc2010.FotMob): 10 h 37 m 51 s (38271 s) Count:2 43.1%

It is your FotMob app.

the phone goes not into deepsleep.
[BetterBatteryStats] Tungstwenty:
I have also tried this app before and got the impression that after being in monitoring mode (poll for updated results), it will exhibit this behavior instead of stopping the activity entirely once the watched games are over.
[BetterBatteryStats] Kocai:
I think it's okay to use that app if only for checking scores, squad lists, previous results etc. I've been using that app for a while now and never seen it causing a battery drain on my phone. Although I admit that I've never use the monitoring/notifications mode...
[BetterBatteryStats] universed:
USB OTG info

FYI, the following Post and Reply regarding OTG were in the Google Nexus Trinity thread today.....

POST: So my hunch was correct. I had problems with OTG too when I unplugged my USB device. My phone will become laggy and hot even when I leave it idle for a long period of time. And battery drained too. Then after reboot everything back to normal.

REPLY: I would guess that the usb driver doesn't quite realise that otg has been unplugged, and keeps doing something, chewing cpu and keeping the device awake, mort may be able to help fix or nail it down.
[BetterBatteryStats] Rob2222:
Its a known bug in the SGS3, that using the safe unplug feature for a USB OTG device is causing a permanent wakelock bug until your restart the device.

If you just unplug the OTG device/stick that does not happen but you risk data loss.

BR

Rob
[BetterBatteryStats] marko987:
...

Have a big problem with baseband_xmm_power on my one x can. someone tell me how to fix it please. Im using faux kernel and have this problem but on franco all is ok that wakelock is taking 4 sec on franco each time I turn on screen,but on faux it lasts long some times even 3 min it locks my low power core on max and hold it like that. Any sugestion please. Ty in advance
[BetterBatteryStats] zonex5:
thank you

Just what Honeycomb needs. The very best of luck with the app!
[BetterBatteryStats] MattyDip:
Every time I turn on my phone this process drains my battery. This process should remani active only for 1-2 minutes after boot but not on my phone. Why? Thanks

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

http://imageshack.us/scaled/landing/138/screenshot2012102123210.png

Every time I turn on my phone this process drains my battery. This process should remani active only for 1-2 minutes after boot but not on my phone. Why? Thanks
[BetterBatteryStats] Rob2222:
Initial/First mediascan needs longer/long when you have plenty media files on your storage cards.

BR

Rob
[BetterBatteryStats] AestenD:
Shouldn't take 10 minutes though.
[BetterBatteryStats] Rob2222:
If you have a 32/64GB Sd-Card full with video I could imagine that it even needs longer than 10 minutes. But I never checked, how long it takes.

BR

Rob
[BetterBatteryStats] catskin:
I use this app to prevent an SD card scan on startup, gotta say it saved me a lot of battery over time:

https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
[BetterBatteryStats] indigold:
I really need help, lost 17% of battery after 6 hours of not using my phone, rom is rootbox and kernel is dorimanx, device is S2 , this is my dump file from bbs. http://db.tt/C6S91xVc
[BetterBatteryStats] gtizon:
Hi there! May i have some help in interpreting thins pls? Here is the link.

http://db.tt/ixz90jH0

Thank you! I'd like to know what eats up my batt.

Sent from my Galaxy Note II
[BetterBatteryStats] Karpfenhai:
Not explainable by wakelocks, try another kernel + modem combo.

The winner is background data traffic, but the drain looks normal.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] gtizon:
Hi thanks! What does background data traffic mean? Any specific actions I should take to improve my batt performance?

Sent from my Galaxy Note II
[BetterBatteryStats] Karpfenhai:
Your network stats are missing, maybe the data was transferred during the 22 mins screen on, try to post a straight idle dump to see the culprit.

Also 4 mins on 1.6ghz seems quite high, did you play a 3d game?

Maryse another governor can help ..

Tapatalked from my Samsung GT9100
[BetterBatteryStats] gtizon:
Nope. All I did during this time were a few text messages, a few whatsapp messages, and a bit of internet. Screen time was pretty low during that time so really not much action went on.

Sent from my Galaxy Note II
[BetterBatteryStats] noorzaquan:
multipdp

Hye guys, i need some help. i have a strange kernel wakelock due to "multipdp" and "deleted_wake_locks". my data transfer are quite normal and not excessive.

To add on, these multipdp wakelocks only happen during im using mobile data but not when i using wifi. Please someone help me for solutions to solve this battery drain. thanks
[BetterBatteryStats] chantoine:
Your dump is way too short : 2 minutes only, should be hours !
[BetterBatteryStats] noorzaquan:
sorry, i mistakenly set to since unplugged and dump to file. as i just connect usb to my laptop. i will post again tomorrow. thanks
[BetterBatteryStats] gabi11:
Hi guys,

could you take a look at my dump?

I think it's not bad, but there are few thing I'm trying to understand how to take care of...

1. "multipdp" and "l2_hsic"

I didn't see anything unusual with my network section.

Is there anything else that can be done?

2. "secril_fd-interface"

Is it related to fast dormancy?

As far as I know, my network doesn't support it and I already disabled it with *#9900# code.

3. If there's anything else that I missed, I'd like to know... :)

Thanks!!
[BetterBatteryStats] Hilmesh:
All three above are related to data usage. Fast dormancy has a tendency to get auto activated even if disabled by the secret code. You can try the fast dormancy toggle for s3 by gokhanmoral. It works perfect in s2, not had any issue since i disabled with fd with it.
[BetterBatteryStats] Karpfenhai:
No need to dump another file, both of your " issues "have been discussed a million times...don't bother to read or search the thread..plus its also described within the in-app help...

@hilmesh, any news on the screenfilter topic?

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Pinan:
Good morning. I've been trying to track these wake up's to no avail. Any help is greatly appreciated.

This was after 8 hours of sleep.

Thank you.
[BetterBatteryStats] Hilmesh:
Hey karpfenhai,

Yup right now on XXLQ6 with siyah kernel and screen filter. I have also done custom undervolting using voltage control. Check screen shots, my best stand by times till date and still 3% to go. :)
[BetterBatteryStats] Register_:
Hi,

Got my Samsung Note I stolen, bought a Note II, all the application reinstalled themselves, but BBS his showing only one red on all screen where could it be coming from?

Thanx
[BetterBatteryStats] snakefever:
Hi!

I have a problem with a wakelock on my sgs2!

I'm attaching the screenshot.

Could you help me?
[BetterBatteryStats] Markox89:
Today I've booted my phone and after a hour the phone has been fully charged, but that overrides also the on boot reference.
[BetterBatteryStats] ejstubbs:
I've just done some calculations. With the SetVsel settings I currently have, running at 300MHz requires 0.85V whereas 800MHz requires 1.1375V. So a 34% increase in voltage gets something done nearly three times quicker.

If the current drawn stayed the same then the energy used to run the CPU through a given number of cycles at 800MHz would be half that used to do the same number of cycles at 300MHz. Which rather begs the question: why not run the thing at 800MHz all the time, other than when it is sleeping? If the processor behaves like a simple resistor, so that 34% greater voltage means that 34% more current flows, the balance is still in favour of 800MHz when not sleeping. I can only conclude that the current drawn actually rises non-linearly with processor clock frequency, making it worthwhile to run at lower frequencies when possible.

Yep, I get that: if non-sleep time in minimised, then the differences in battery drain between different CPU clock frequencies when it

is

awake will become small enough not to matter.

A similar argument could be made for not limiting the clock frequency when the battery is low: the quicker the phone does what the user wants, the sooner the user can turn the screen off and let the phone go back to sleep. I think the argument is slightly less strong in this case, though, because it assumes that the user will turn the screen off as soon as possible. That might very well not be the case eg if the user is reading and digesting an e-mail, that shouldn't take much CPU time but it could take a lot of real elapsed time, especially if the user is slow on the uptake (like me).
[BetterBatteryStats] ejstubbs:
Suddenly the penny drops - I think. I believe I am correct in interpreting the three options as showing the time that the offending process has had a wakelock in place, expressed as a percentage of:

1) the time in the displayed measurement period that the phone has not been plugged in

2) the time in the displayed measurement period that the phone has been awake

3) the time in the displayed measurement period that the phone has been awake

less

the time that the screen was on

I hadn't twigged that the "-" in "% of time awake - time with screen on" meant "minus". Could the whole dialogue be re-worded to make it clearer? For example, the heading could be "Wakelock expressed as % of time..." and the three options could be "on battery", "awake", "awake, minus screen-on time".

Or maybe I'm just too thick for it to be worthwhile pandering to my stupidity :o since no-one else has had any problem understanding what it meant.
[BetterBatteryStats] nobnut:
Absolutely agree.

Previously, I was assuming that the desire was to limit CPU speeds while the battery is low and the screen is off.

In this scenario, the only battery saving would be made whilst the device ended running processes and the CPU scaled back (seconds rather than hours). This is why it would be of minimal benefit to the battery.

The argument as to whether it is better for the battery to run the processor at a lower speed for a longer time, or a higher speed for a shorter time, for a given task is older than the hills. If you ever find a definitive answer, let me know ;)

...here is another variable for that mix you need to consider - screen on vs off. Is it more battery efficient to run at a higher CPU speed whilst the screen is on, as finishing the task quicker will allow the screen to be turned off, therefore saving more battery (display time) and reduce CPU speeds when the screen is off as battery drain will be less as display time will not be present and the CPU can take longer to finish the task?

^joke ;)

Sent from my HTC Flyer
[BetterBatteryStats] chamonix:
you are right and I'll take your suggestions for relabeling.

tracking that in issue #35
[BetterBatteryStats] Whyzor:
The common formula for Power = c * I * V^2 where c is a constant, I is current, and V is voltage. Power does rise non-linearly as voltage is raised, which is why CPUs are designed to run at lower voltage at lower clock speeds whenever possible. The other concept is "race-to-idle", getting all the calcualtions done quicker so the CPU spends more time idling. This is fine in theory when the CPU is fed with enough data to do useful work, but in real systems, often it's wasting clock cycles waiting for memory reads or other parts of the system, so higher clocks does not result in all that faster processing.

CPU engineers have a better idea of what's best for the systems, and that's why they have the chips idle at lower voltage and lower frequency and scale that up on demand. All these after-market apps are really not taking into effect the hardware as much as the chip desginers have.
[BetterBatteryStats] ejstubbs:
Err, not in any text I've ever seen! Can you provide a reference for the formula you quote? Back in my undergradate days, unless you were voyaging into the murky waters of AC with reactive loads, electrical power was voltage times current: volts times amps gives you watts, simple as that. Multiply by time in seconds to get energy in joules.

Yup, agree with that. Similar in some ways to the example I offered of a putting an e-mail on screen quicker but then still having to sit around with the screen on while the user actually reads the thing.

I have little doubt that that is the case. I'm sure there are other considerations as well, such as processor stability at high clock frequencies, and dealing safely with the heat generated when running at higher speeds.
[BetterBatteryStats] sowen222:
BatteryMonitorWidget reports 125-140mA on my stock HTC Sensation. :-(
[BetterBatteryStats] odub303:
I'm going to hazard a guess here and say that the -2ma stated in your log is not accurate. The only time I've ever seen that is with a rom that had battery driver issues that would cause the battery to stay at 100% for extended periods of time, after which it would drop slightly faster than it should, resulting in the "expected" battery life, only measured by an extended period at 100% followed by a shorter period from 100-0. I consistently saw this using battery monitor widget pro on my Epic 4G on the stock gingerbread leaks that clearly had battery driver issues that caused the indicator to remain at 100% far longer than it should have.
[BetterBatteryStats] nobnut:
Don't worry about it!! BMW doesn't work on the Sensation.

We had another user on this thread a few weeks ago who discovered the same thing.

He actually returned his device for replacement as he had other issues with it.

I can't recall his name now but if you look back/search you will find it.

EDIT: You can try using Current Widget instead.
[BetterBatteryStats] sowen222:
And now I see on his forum that he says the mA is reported incorrectly by the kernel on the Sensation.

I tried Current Widget, but unfortunately it reports the same value as BMW. It does have the ability to apply a conversion factor, but I wouldn't know whether to multiply it by something, or just subtract off 140 or something... :-(

This makes solving my battery drain very difficult, because I can't compare the mA in different scenarios.
[BetterBatteryStats] nobnut:
I would do it the easy (or hard?) way.

Simply use a calculation of % lost per hour sleeping. From that you can calculate your drain as you know your battery capacity :)
[BetterBatteryStats] nobnut:
You are absolutley entitled to that perception. I'm not going to challenge your right to think whatever.

You better tell that to all the other people who get the same drain levels as me ;)
[BetterBatteryStats] sowen222:
Well, I'll give that a shot... if I can get my damned (lovely) phone from waking a couple of times at night :-)
[BetterBatteryStats] pspilot:
Well, obviously you didn't see enough texts and in 'these days' they missed to teach you enough about semiconductors, especially about CMOS logic :D. You know, Ohm's law has little meaning when it comes to a few million CMOS switches. In the meantime, wikipedia always has quite nice texts :).
[BetterBatteryStats] carlos67:
Yep, agree with this. I used to use Current Widget on my HTC Desire and it worked like a charm.

btw......thanks Nobnut for the answer you gave to my post in JKays thread regarding changing png's. However, after extracting the said systemUI.apk or framework-res.apk, don't you then have to re-zip it up and and re-sign it? It's the re-signing bit that I wouldn't know how to do.............(waits hopefully for Nobnut to bestow knowledge.........)

Sorry for going OT :o
[BetterBatteryStats] carlos67:
Thanks guys.

Sorry for double post

Just wanted to say a big

thank you

to Chamonix and Nobnut for helping me get the most from my battery. Screenshot below shows what can be achieved with the help of these guys.

Admittedly, only 30 minutes screen on time but even so, almost 5 days if extrapolated to battery empty. Could never have got this on my old Desire.

Just goes to prove that, for a light user, 3~4 days is possible under the right conditions

FYI > Revolution ROM v2.6 / Ninphetamine 2.0.5 with BLN enabled / No battery savers whatsoever / fast dormancy disabled / some wifi - no gps / weak 2g signal (doesn't help!) / Overclocked to 1.4GHz and undervolted to 825/875/950/1050/1150/1250

If I had a strong 2g signal heaven knows how much extra I could get!!!!!

It's rock stable, fast, smooth and well, I've said enough already!!!

Thanks again chaps. Time to donate me thinks. :)
[BetterBatteryStats] ejstubbs:
I had indeed not seen that formula for power dissipation before, and you're also right that CMOS logic was not part of the electronics module in the syllabus I followed. (It was all analogue in my day - can you guess how long ago that was?)

You might want to have a read of that Wikipedia article again, though, because it doesn't actually support what you say. You offered the formula:

The formula given in the Wikipedia article is actually:

P = C * V^2 * f where C is the load capacitance, V is the voltage and f is the clock frequency.

As the article points out, C * V * f gives the current. Thus the power dissipated is actually current times voltage. QED. Looks like Mr Ohm still has his uses. Humble pie is now being served in the refectory.

To look at it another way: the processor chip has a voltage applied across the supply pins, and a current flows. Regardless of what goes inside the chip, the power being supplied to it is voltage times current.
[BetterBatteryStats] nobnut:
No, don't extract, just open in 7zip and drag the files in. Then flash/install as normal.

Sent from me to you using stuff
[BetterBatteryStats] chamonix:
You are very welcome and Thank you for sharing!

Your graph is quite impressive of your phone doing the right thing when not in use: sleeping :)
[BetterBatteryStats] pspilot:
I didn't have to guess, seeing your assumptions about the digital world (sorry, that was your invitation :D).

I didn't offer any formula - that was Whyzor. I only commented your erroneous assumption, that the power dissipation in semicoductors is a linear function of the voltage. It doesn't actually matter, that one formula talks about the current and the other about the frequency. Since current in CMOS structures is mainly flowing when charging the gates during switching (CMOS doesn't consume while static), the frequency is an important factor for the current. It is the place holder for the current, of course with the added factor 'c' that represents the gate count and other typical chip parameters. So to be precise, the formula C * I ... is also not correct, since once you have I, you don't need C anymore. But that was not our subject at all. The subject was the influence of the voltage on the power. And still the POWER is calculated with the QUARE of the voltage.

P = I*V? Yep, but that's trivial and wasn't the question. The question was, how a change in voltage is influencing the power dissipation. And it is NOT as you were suggesting a linear influence but a square one. That's why it is even more important to lower the voltage than the frequency. Not only is the frequency just a 'linear saving' factor but also lowering the performance, while lowering the voltage costs nothing ... as long as the chip works with it of course.
[BetterBatteryStats] chamonix:
I must guess as you didn't post any message: if there is a message saying "no reference since...." than you need to plug/unplug, charge, boot your device (depending on the reference you are using) to have BBS write the corresponding data on that event.

If I misunderstood the symptoms please post more details.
[BetterBatteryStats] Karpfenhai:
Nice, but what's the screen on time?

Hint, before taking screenshots, disable the filter, otherwise it's getting to dark.. :)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Hilmesh:
Yes it is too dark. I have taken another set of screen shots after the battery reached 3% (My reference point for all tests) and will post them in an hr. :)
[BetterBatteryStats] Hilmesh:
Please see screen shots :)

3 Days Standby

3 Hrs 5 Minutes Screen ON (Almost 2.5 Hrs of 3G usage)

3Hrs 35 Mins Awake time

45 Mins Phone ON

Although i am still not getting the same amount of screen on time as you get. Screen Filter i have used it differently. I set the brightness slider to the middle setting in the stock brightness panel. Then set 3 Screen Filters 35.3%, 41.6% & 75.7% and used as per light requirements. How do you use the screen filter. Last time i had asked about auto brightness , you said you never use it then do you keep the brightness to the lowest in stock? and then use screen filter? Also i have done undervolting and my range is from 100Mhz - 1200Mhz.
[BetterBatteryStats] Kocai:
Would you mind sharing how you achieve that kind of battery life? Do you disable GSF stuff like Karpfenhai post?
[BetterBatteryStats] Register_:
Thanks, it's what I did and got the stats. battery-monitor wavelock seems to be awake a lot of time. I'm charging my phone a Note II to get stat with "Since charged".
[BetterBatteryStats] Hilmesh:
hehehe nope i do not mind at all :).

Please follow the first 3 posts to the dot.

Yup follow the post of GSF by Karpfenhai - http://xdaforums.com/showpost.php?p=29171517&postcount=6822

I was unable to implement it fully, so i have used it partially and my corresponding screen shots are here - http://xdaforums.com/showthread.php?p=31944027#post31944027

Also look if your network supports Fast Dormancy (FD) if not then use the secret code *#9900# and disable it. Even here my phone behaved oddly and used to keep enabling as it seemed fit. so i used Gokhanmorals App for S3, it worked perfect in my phone. Since using it to Disable FD i have not faced any issues.

Also you can go for screen filter app and try the settings which you like.

I am running Siyah with custom Under Volting. Frankly this is something that i tried first time and with trial and error the following are the values which i used without issues, (For Under-Volting now i am moving onto different values and will post results soon. Also i am open to suggestions for others you have tried this)

100Mhz, 200Mhz, 300Mhz, 400Mhz - 850mv

500Mhz, 600Mhz, 700Mhz - 925mv

800Mhz - 950mv

900Mhz - 1000mv

1000Mhz - 1050mv

1100Mhz - 1100mv

1200Mhz - 1150mv

Also look in my signature for the link to my Freeze list.

Hope it helps in achieving your desired values :). All the Best.