yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Mongopusher42:
Thank you for the fast reply! i will try these things right away.. what kernel do you recommend? Im really new with Sgs2 , just changed my Sgs1 to this less than a week ago :X , Btw i use Juice Defender to shut off my data when screen is off, any subsitute apps to do this?

P.S What is the nag feature of Gosms?
[BetterBatteryStats] jeremysherriff:
I can't recommend a different kernel, I'm a fan of stock myself. Maybe one of the other guys can make a recommendation.

The "nag" feature of go sms is the "reminder" part of the notification settings. It keeps your phone awake, reminding you with a sound or lights or a pop-up window if you have a new message. But it literally keeps your phone awake to do so.

By shutting off your data when your screen is off you are using more battery. Consider this situation: Facebook tries to check for new messages, but the screen (and therefore data) is off. It sits there trying and retrying, for possibly several minutes. The whole time your phone is awake. This is much worse battery usage than if you simply let facebook check for a message.

This is an acknowledged drawback of Android - there is no central way to indicate to all apps and system components to not use the network at all. By simply removing the network connection, you make the issue worse.
[BetterBatteryStats] Karpfenhai:
I would recommend to not use siyah but I assume you are on aosp?

If not, use phenomenal kernel, if yes, limit your cpu to 800 and set governor to on-demand.

Use another modem, try ki3, ki4 or kh3.

Apply screen filter.

Anything else seems to be perfect.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Hilmesh:
hi there you can also go for Hirox 0.32 Extreme. it is based on Phenomenal Kernel only :). try it out.
[BetterBatteryStats] Mongopusher42:
@jeremysherriff

Thanks for the info, i didnt know all that!

@ Karpfenhai

Yes im on aosp, what is an ideal cpu state considering i play some heavy games once in a while.. atm im on min:200 max:1200 , governor: pegasusq
[BetterBatteryStats] It_ler:
Bad result on and good suggestion.

As the battery draining issue and l2_hsic wakelock is in JB (4.1.2) and stock ICS (4.0.4) ROM, it seems not to be a software/firmware issue.

If you are still on warranty, go to a store/service center and ask for a repair/replacement.

If no warranty, try another battery ... but i think that it's not the battery.

Good luck !
[BetterBatteryStats] Casanoaa:
It looks pretty good without touching it yet
[BetterBatteryStats] chamonix:
The fix is in latest beta, at least I hope so. I tested it on my device and got proper warnings. Could you retest and confirm. If it doesn't fix it for you I'll reopen.
[BetterBatteryStats] chamonix:
Hey, that is my speech on not assuming that error handling is the solution for less drain ;) ack on the missing central instance as well, that's why all tools like green power or jd can't fix the problem
[BetterBatteryStats] picollo78:
It looks bad... I used 3 batteries So as you said it is not that :crying:

testing other kernel? maybe?
[BetterBatteryStats] jeremysherriff:
It's not what you know, it's who you can repeat and sound clever ;)

---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------

I'm not sure what you are talking about, did you read the thread I linked to? It's an acknowledged issue in kernels based on stock.

I experience something similar on my Galaxy tab if Power Savings mode kicks in. This is not a hardware fault, it's clearly a software fault.
[BetterBatteryStats] Karpfenhai:
@Sven, the latest beta is re introducing the kernel wakelock get not reset on unplug issue:

Tapatalked from my Samsung GT9100
[BetterBatteryStats] It_ler:
Ok ... I am just guessing what could cause the issue and trying to help picollo78 ... I think just like you.

(Just an assumption that you are also guessing, as you wrote "I think this is a hardware/kernel bug..." first and now "This is not a hardware fault, it's clearly a software fault.")

I read the thread that you linked, and I hope that picollo78 also has read it.

So I assume that he already tried the "workaround" with "turn on your screen, unlock your phone, before unplugging the cable" and still has the l2_hsic wakelock.

That's why I thought about other possible causes.

The symptom "l2_hsic" can have the same cause ... but it could also be caused by something different.

But thanks for reminding me not to "guess" and "assume" too much.

---------- Post added at 10:25 PM ---------- Previous post was at 10:19 PM ----------

Please read the suggestion of jeremysherriff - especially the linked thread.

There is a kind of workaround ("turn on your screen, unlock your phone,

before

unplugging the cable") to avoid the l2_hsic wakelock for some cases ... maybe it works for you/on your phone too.

Good luck and report back !
[BetterBatteryStats] EvanVanVan:
Just wondering, you're getting some "normal usage" in now as a control? And then going to test Google Now against it? (And I'm just thinking Google Now since you mentioned it a few pages ago)
[BetterBatteryStats] chamonix:
You have two good point here (didn't notice heh ;) )

First is of course a bug: "current" frozen need to be invalidated upon e.g. unplug -> https://github.com/asksven/BetterBatteryStats/issues/303

Then there is the handling of "current" as opposed to "real time" (needed for widget) requiring a design decision and a clear experience yet to be defined -> https://github.com/asksven/BetterBatteryStats/issues/304

I feel the clearest distinction should be to define a new reference "frozen" being updated when the user wants it to be (copy of current) and a "current" that is real-time. I also believe that introducing "frozen" and "current" is an expert matter so it should not be the default behavior (as it is in current beta) but something that should be enabled as an advanced pref.

Feel free to discuss! I will start by fixing 303 and will take 304 when we came up with something consistent from a user point of view
[BetterBatteryStats] cowman4000:
Help!

Can someone take a look at my dump file? I'm barely getting 1 hour of on screen time... Rezound, stock battery running Nil's v6.3 sense ROM.
[BetterBatteryStats] jeremysherriff:
It took me three attempts to read this and understand what was going on, the context etc etc :)

@picollo78 if you are still reading (I might PM you anyway) it looks like Karpfenhai has found better and more details reasoning behind the wakelock you see.

Yes it appears to be kernel related, it's to do with the handling of the SDcard in some situations, especially sleep-related.

Several things come to mind:

do you haev any apps moved to sdcard? if so, move them back or get rid of them.

are you able to format your sdcard? copy everything you need off first obviously.

you should format your internal storage too - boot into cwm without your sdcard in place, and format whatever stroage you can find. ideally, have a ROM zip on your sdcard, so when you're done formatting all avalable partitions, you can then insert the sdcard, reboot to recovery again, and flash a ROM.

If this "bug" was introduced via a genuine kernel code update, it explains why you are seeing it on all ROMs. I assume if you went backwards to a stock GB ROM it would probably be OK, and then be introduced somewhere around 4.0.3. But try cleaning your system up first by formatting the various storage locations one by one, as per the list above, as it might not be a bug that shows on all ROM's/kernels but rather some local issue that is simply handled badly.

Good luck dude!
[BetterBatteryStats] picollo78:
If i understand I have to format my sd card and the internal storage then install a gingerbread rom from cwm. one question, what's Kmsg?

Thank you I'll try that and I'll let you know.
[BetterBatteryStats] jeremysherriff:
kmsg is the kernel message log tool.

Don't go back to GB.

1. Make sure you have no apps running from on your sdcard - they may be preventing the sleep state.

2. Copy off important data, then format your sdcard. Copy the barest essentials back onto the card.

3. Check for content on your internal storage area, format it once you've copied anything important off it.

This should be enough - if you have problems after this, try running without an sdcard for a bit and see if the issue remains.
[BetterBatteryStats] abbz123:
Ok made some changes -

So looks like 1.9 percent drain on stand by with LTE on.. i guess thats not to shabby?
[BetterBatteryStats] jeremysherriff:
The v1.12 beta's aren't fit for diagnosing stuff yet (see the "since" time is 0s?) so this is not entirely useful.

However yes it looks pretty good, and appears to even cover your normal day to a degree.

The only thing that stood out to me was the Go Weather widget which is waking up a bit too frequently for my liking.

you have two weather services (Go, and WeatherEye) you should set one to update manually only. Remember that these services often also try and figure out your location so updates for weather services can be quite a heavy background activity.

Well done!
[BetterBatteryStats] abbz123:
Hey thanks for the quick reply, I'll download the different version of battery stats and see if I can improve by eliminating one weather widget.

Cheers

Freshest nightly/kt747
[BetterBatteryStats] jeremysherriff:
Use my thanks button, I wanna see if I can catch up to @chamonix (jokes :))
[BetterBatteryStats] It_ler:
1. Please install latest stable BBS app version, which is ATM v1.11.0.0.

2. Disable/freeze Google+. Just to see its influence on your battery life.

3. Disable auto sync of your accounts. You can update/sync manually when needed/wanted. Your current sync settings produce a massive wakelock and prevent the phone from entering into deepsleep state.

4. We can see more information, when your phone is rooted, the root options are enabled in BBS and you plug/un-plug the charger or USB cable before begining to record your BBS dump.

Then try agian.

Good luck !

---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------

mmc2 and mmc1 detect wakelocks have something to do with your internal and external sd card.

jeremysherriff has already described what to do it this case ... it's just one post above yours.

Please give it a try and report back.

If it helps, don't forget to hit jeremysherriff's Thanks button :good:
[BetterBatteryStats] picollo78:
thank you for all that you do guys,:o

after formatting my sd card and my internal drive, I installed the rom that Karpfenhai recommended me.

I have not started bbs for 4 hours but my battery runs out as always.

I let it run for 4 hours and post the dumb file.

thank you for your efforts.
[BetterBatteryStats] Karpfenhai:
Take out the sdcard!

if its faulty.. it will go away

and you can be sure the reader itself is not causing the trouble

Furthermore the rom you flashed is pre-rooted, so please send us a logcat and do this on a terminal:

su

#dmesg > /storage/sdcard0/dmesg.txt

append this file here.

Good luck!
[BetterBatteryStats] EvanVanVan:
What's more important for drain? The "count" or the total time/percentage of time the program is awake/running?

For example in ashwinv11's dump:

"PowerManagerService" (): 3 m 44 s (224 s) Cnt:(c/wc/ec)657/0/0 2.0%

"KeyEvents" (): (0 s) Cnt:(c/wc/ec)1904/0/0 0.0%

I don't even mean they have to be the exact same processes,but if I see something like that on my dump. Would it be better to try and remove the higher count or the higher time(percentage) awake process?

Thanks
[BetterBatteryStats] Xelstyle:
Alright, took the pointers given and hope this works. Pretty impressed that my phone managed only 2 percent drain over 6 hours. Never had that happen before.

Also I know I was told to disabke/freeze the quick search box but took a guess about which to remove. Wondering if I should be freezing Google Search overall?
[BetterBatteryStats] Karpfenhai:
You can freeze all this with no issue:

Tapatalked from my Samsung GT9100
[BetterBatteryStats] cowman4000:
Thanks for your input! I am actually rooted as I'm running a custom sense ROM. I'll try your recommendations and see if I notice a difference! Thanks!
[BetterBatteryStats] yahyoh:
i have one bug with B2 sometimes statue's didn't refresh automatically :rolleyes:
[BetterBatteryStats] Casanoaa:
SIII users don't freeze badgeprovider.Stock messaging app would crash when you open it.
[BetterBatteryStats] Tungstwenty:
Mmmmm, a bit of a wildshot here :confused:

Could anyone with the affected devices (Nexus * with 4.2.1, I guess), look at /d/wakeup_sources (or /sys/kernel/debug/wakeup_sources, which is the same) and post its contents?

I have a feeling that kernel "sleep suspenders" might start being handled by this linux-wide mechanism instead of the android specific mechanism which never made it to the main Linux branch, as it was.
[BetterBatteryStats] stuart0001:
http://db.tt/kCcBs2YZ

Both files in those locations look identical
[BetterBatteryStats] Tungstwenty:
0 bytes???

Did you query the contents as root?

On my 4.0.3 I have this:

name active_count event_count hit_count active_since total_time max_time last_change
usb1 0 0 0 0 0 0 0
exynos-rtc 0 0 0 0 0 0 0
max8997-rtc 0 0 0 0 0 0 0
gpio-keys.0 0 0 0 0 0 0 0

I was hoping the newer kernels would have more entries and non-null counters.
[BetterBatteryStats] picollo78:
I'm back,

I struggled to have the logcat but here it is.

Thank you all again for your help
[BetterBatteryStats] picollo78:
There is the kmsg.txt file.

The sdcard removal didn't work.

Here is the dumbfile after removing the sdcard, maybe it will help you.

Thanks.
[BetterBatteryStats] Kocai:
Using Solid Explorer, this is the content on my GN.

It's 0 bytes. I'm using a custom kernel though (can't stand stock kernel Google colors)
[BetterBatteryStats] CazeW:
Here's the contents of my wakeup_sources on my Nexus 10 with 4.2.1. Also attached it as a txt file.

I don't know if it is related to this but BBS doesn't show me any info at all (tried both the one on market and the latest in this thread).

name	active_count	event_count	wakeup_count	expire_count	active_since	total_time	max_time	last_change	prevent_suspend_time
GPS	7	7	0	0	0	555018	172949	34010959	31436
PowerManagerService.Broadcasts	62	62	0	0	0	32991	1095	34777661	5161
event0-388	6013	6042	1	0	0	341703	340	34776710	341688
event1-388	0	0	0	0	0	0	0	18378	0
event3-388	8216	8216	2029	0	0	50187	289	34776710	50187
event2-388	350075	350121	0	0	0	36994	15	35169860	0
KeyEvents	370469	370469	4724	0	0	44792	226	35169860	4159
PowerManagerService	6853	6853	2381	0	393155	28675052	8236014	34776709	6027375
android-ac	5	5	0	0	0	3	1	33579655	1
android-usb	5	5	0	0	0	6	2	33579656	3
android-battery	2831	2832	507	0	0	152767	164	35139024	133072
android-chargerdetect	4	8	0	4	0	8060	2033	33581655	373
android-battery-monitor	2829	5948	1522	0	0	114608	213	35138975	104363
vbus-manta_otg	1	1	0	1	0	2004	2004	7755	0
wlan_ctrl_wake	1164	27519	4163	1164	0	2789844	6489	35150225	1524089
wlan_rx_wake	2458	299371	337	2458	0	7928847	215728	35162565	226168
wlan_wake	1041477	1041477	16992	0	0	648270	2184	35168165	83262
vbus	4	4	0	4	0	1986	498	33580150	372
manta-board	1	1	0	0	0	0	0	3154	0
alarm	9753	16075	3657	0	0	590477	3485	35164528	585981
mmc1_detect	2	4	0	1	0	601	544	6130	0
mmc0_detect	10834	10836	2029	0	0	5264	257	34776715	5067
ds2784-fuelgauge	1	1	0	0	0	47	47	2781	0
smb347-battery	6	6	0	0	0	2685	2604	33579665	2648
smb347-usb	4	4	0	0	0	3491	2578	33579641	2580
smb347-mains	1	1	0	0	0	0	0	913	0
exynos5-fimc-is2	0	0	0	0	0	0	0	849	0
max77686-rtc	0	0	0	0	0	0	0	740	0
vibrator	4367	4367	0	0	0	125030	501	35169807	1004
alarmtimer	2029	2029	2029	2029	0	4066267	2004	34774175	4066267
BTHostWakeLowPower	0	0	0	0	0	0	0	290	0
BTWakeLowPower	0	0	0	0	0	0	0	290	0
5-0009	0	0	0	0	0	0	0	255	0
gpio_input:manta-keypad...	0	0	0	0	0	0	0	225	0
gpio_input:manta-keypad...	133	133	1	0	0	1348	12	34776689	503
dock_pd	1	1	0	0	0	250	250	505	0
dock	0	0	0	0	0	0	0	210	0
manta-chgredetect	0	0	0	0	0	0	0	210	0
manta-chgdetect	3	3	0	0	0	4675	3446	33579653	4061
serial-debug	1	1	0	0	0	500	500	625	0
autosleep	63	63	0	0	0	1	0	34776730	1
[BetterBatteryStats] ryvandal:
So I did a better battery stats little test the past couple days.... My phone is Samsung Galaxy S2-X SGH-T989.

I know alot of you must be busy so please take your time I don't want to intrude on anyones busy life... Especially around the holidays... But if you have some time please I could use some insight on things I can do to make my battery last longer.

A couple little notes to add:

1: 3600 mah NON OEM battery is currently installed... Is this good life for this kind of battery? (It's brand new... if that makes a difference)

2: I did calibrate battery.

3: Brand new kernal was booted on... Wiped cache/system everything accordingly... Here is the rom I am on

http://xdaforums.com/showthread.php?t=1849748&highlight=koodo+v3

I chose that because its close to stock and I heard it had good battery life (If you know of any that are better please tell me!)

4: Yes I am aware instagram is WAY higher then anything else... That is because I use my instagrams for about an hour a day (I get like 200-300 new followers a day... about 100 of them are bots that I have to individually block to get rid of so that takes some time)

5: I do have cpu tuner installed. Pretty much 1 cpu is being used. And under clocked all way around. Not too sure how THRESHOLD works though so any insight would be great.... I just went with the governors and the settings... and dropped the MHZ down to some low numbers (Which can be seen in the dumpfile)

So any tips as to what I can do to make my battery better would be awesome!

Thanks for the help in advance guys and i'll be glad to help out as much as possible!
[BetterBatteryStats] Karpfenhai:
@ Sven, latest Beta does always loose its reference on JB around 10 mins after unplugging, means first time opening BBS is working, after sleep second call fails.

Hope you find the cause:

View attachment logcat-2012-12-05_083045135.txt
[BetterBatteryStats] jeremysherriff:
Same issue here. GNex on 4.2.1, BBS 1.12b2.
[BetterBatteryStats] picollo78:
So we can not do anything

Anyway thank you all for helping me
[BetterBatteryStats] jeremysherriff:
Any chance of warranty repair or replacement?
[BetterBatteryStats] It_ler:
1. Please install latest stable BBS app version, which is ATM v1.11.0.0.

2. Provide an idle dump while doing nothing/screen off all the time to find the battery drainers easier.

3. I see Fast Dormancy wakelock, so check if your mobile carrier provides FD. If yes, then enable FD, if not disable it on your phone. There is a Fast Dormancy app from gokhanmoral on Play store to toggle this setting.

4. Disable Battery Monitor Widget, as it generates many alarms (wakes up the phone from deepsleep).

5. Disable all location service options in ROM settings.

Then try again.

Good luck !
[BetterBatteryStats] ryvandal:
1. Ok done

2. Ok i'll do an 8 hour dump or so when I sleep

3. I have no idea but i'll call my provider tomorrow

4. Didn't know that... Widget is gone... Is the program itself alright to have on my phone?

5. This is the confusing one.... I don't know how to do that... Could you lead me to something that can help me disable this? (A guide or maybe its easier then I think?) Also what are the pro's/cons of this... Would this disable gps? (Not sure what it is... :P )

Thanks :)
[BetterBatteryStats] Tungstwenty:
Indeed this doesn't seem to have nothing to do with mmc. Despite the high count of locks (~ 8K), this is merely an indication of the number of times the device almost suspended and when it came back the driver briefly acquired the KWL to make sure the device was back to working state. During resume it aquires the KWL, schedules the appropriate work to be done, and returns so the next driver does the same and so on.

Se approximate same counts are there for l2_hsic, power-supply, sec-battery-monitor and KeyEvents which probably follow the same pattern.

And that also explains the kworker* lines in the processes, which are the threads that handle that scheduled work not synchronous with the resume chain.

The problem is indeed the fact that when pretty much everything has been shutdown, during the final step immediately before the CPU shuts down it checks if there are active wakeup sources (otherwise it would be a permanent sleep) and also if some of those wakeup sources happen to already have triggered some work to do that hasn't been serviced in the meantime. This does happen and the deep sleep is pretty much instantaneous, let's put it that way.

The drivers are then all resumed, and here we can see the suspend_backoff logic kicking in. Whenever there are 10 consecutive suspends all with less than 1s duration each (even if they happen with a big interval between them; what matters is the fact they're consecutive), the backoff will be triggered and lock a KWL with an expiry time of 10s. The C is ~800 which matches 8K/10, and all of them were ECs as expected.

All that's left is understanding what the heck is keeping pending interrupts right when the CPU is about to sleep, and this is the root cause of the issue.

It's probably an HW issue, but I don't have a clue which.

Karpfenhai, why do you point to RAM issues? Is it just a suggestion or did you find any specific references for this?

I couldn't find a way to trace the interrupt bit (0x00080000) to the physical device...
[BetterBatteryStats] It_ler:
1.+2. Fine :good:

3. You can change the state of your phone's Fast Dormancy state and chack if the FD wakelock(s) are gone (then it's Ok) or going bigger (then switch FD back to the previous state).

4. BMW usually produces alarms when you have activated the widget. Just remove the widget and check your BBS dump.

5. Depends on your ROM. In SGS2 (GT-I9100) stock ROM, you can find the location services in menu "Settings" > "Location services" > [UNTICK] all options.

Good luck !
[BetterBatteryStats] superleeds27:
Im seeing 10-15 Mins of syncloopwakelock.

Heres the thing.

I have no accounts/sync options activated. None of my apps have notifications enabled.(Checked and doubled checked)

Any ideas?
[BetterBatteryStats] It_ler:
Please post your BBS dump.

Without more information it is very hard to make a good guess :p
[BetterBatteryStats] superleeds27:
Attached
[BetterBatteryStats] s2dh:
Could someone take a look at my dump file and tell me what is causing battery drain and what i can do to improve these stats?
[BetterBatteryStats] It_ler:
Hmm...

1. I see "com.maxmpz.audioplayer.player.PlayerService". Maybe it was the audioplayer. Leave the audioplayer off and make a new dump.

2. I see "GpsLocationProvider". Someone wants to now where you are?! Check if all location service options are disabled.

3. Your phoen seems to be rooted, but I don't see any Network or Alarm stats. Please enable root options in BBS app menu "Settings" > "Advanced" > "Root features" [TICK].

Then try again.

Good luck !
[BetterBatteryStats] Steven Seagal:
Where I can see the time I have left the battery? . I not find that information ...:confused: