yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] honest1212:
/sdcard/
[BetterBatteryStats] Rob2222:
Sending set of files to debug via PN.

BR

Rob
[BetterBatteryStats] M.A.K:
No other roms available for my phone I'm afraid.
[BetterBatteryStats] Miche1asso:
So let's say that as it is now it is still mandatory to plug/unplug it…It's creating issues otherwise (at BBS level, not at battery level, sure). Hopefully it will be fixed.
[BetterBatteryStats] kmetek:
my .txt
[BetterBatteryStats] Karpfenhai:
That dump is useless as it contains only 5 mins..

Read post 3 how to produce a valid isle dump.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] alexinna:
I think it depends what reference you plan to use. In all cases action is required to generate the reference.

since_boot - should be created automatically after you boot.

custom_ref - you need to create one

since_charged_ref - should be created automatically after you disconnect from charger

since_screen_off - should be created automatically

since_unplugged_ref - should be created automatically after you plug/unplug

I think you are referring to "since_boot " reference that would be used as a fallback if for example "since_unplugged_ref " is not there. Agree this one always will be there. But to use it box needs to be checked in preferences.
[BetterBatteryStats] chamonix:
What I see now:

I/References(11533): Create ref custom_ref at 6 h 11 m 18 s

on the other hand I see

D/StatsProvider(11533): Processing wakelocks since

D/StatsProvider(11533): Reference used: Reference is null

the abnomaly here is that the code says:

Log.d(TAG, "Processing wakelocks since " + statTypeToLabel(iStatType));

meaning that there should be something after the since (the name of the ref).

What stat / stat type did you select?

Could you please provide a logcat where I can see:

- creating of "custom ref"

- using the custom ref
[BetterBatteryStats] M.A.K:
That's exactly what this log is. I created the custom ref then selected the custom ref.
[BetterBatteryStats] chamonix:
OK. Could you create a dumpfile and check the creation Date of the ref file for custom ref. The log say it creates it and it should show a valid creation date not equal to 01.01.1970

If this is fine then we need to look into the next process steps
[BetterBatteryStats] Karpfenhai:
Might not be helpful but no issue with custom ref on my 4.0.3 ROM at all..

Set and working as expected :(

Can't help with that.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] M.A.K:
Well I've got 1.8.1 installed again now but as you can see from the B6 dump I did here, the ref's are dated 01.01.1970.
[BetterBatteryStats] chamonix:
I am aware of that. The logcat also showed bbs didn't save because of the leaked window/progress dialog. Last logcat shows a save action but you didn't provide a dumpfile for that. Any chance switching back and providing a logcat and dumpfile for the same test case?
[BetterBatteryStats] chamonix:
Me neither on 4.1, in am getting home now and will have access to a 2.2 and 2.3 device till Monday.
[BetterBatteryStats] Xdenwarrior:
dumb file attached
[BetterBatteryStats] chamonix:
As a first step I suggest turning wifi off, it causes a lot of overhead, including location. Then take an idle dump and repost
[BetterBatteryStats] Karpfenhai:
You are suffering the usual candidates, maps and location based services.

read the faq for maps and sign out/disable all location services.

Furthermore you made calls and listened to music, so please provide a clean idle dump (overnight).

Regards.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] M.A.K:
We have a name for this in UK, we call it faffing.

We already know that BBS is no longer successfully creating any of the references on my phone - and you can't blame them all on dialogs.

It may be useful if you include a debug routine that retrieves references at different points during the creation/storage/retrieval and writes the info to a bbs_debug.log. This way we can see exactly which part of the process fails.
[BetterBatteryStats] Rob2222:
For any strange reason I just recognized, that I had BBS 1.10b4 and 1.10RC1 installed BOTH at the same time.

I have no idea, how this happened.

I think thats the cause for my tasker dump problems.

@Chamonix:

Sent you some more details via PM.

BR

Rob
[BetterBatteryStats] Tricks25:
I cant stand it anymore so i now ask for your help guys.. i lose 6-8% overnight hope someone can help analyse my bbs log..
[BetterBatteryStats] alexinna:
According to dump file your stats are not that bad at all:

Since 10 h 59 m 14 s
Awake (): 3 h 41 m 18 s (13278 s) Ratio: 33.6%
Screen On (): 3 h 33 m 26 s (12806 s) Ratio: 32.4%

Also after almost 11 h with 3.5 h screen on you only lost 60% of battery life.

I don't see anything unusual in attached file.

Can you please use latest stable version (version used for attached dump is 1.9.0.0RC2) and provide idle dump file (as described in post #1) for us to take a look.
[BetterBatteryStats] Tricks25:
^

^

big thanks sir.. also i couldnt find anything much unusual in my bbs.. so that makes me think that it is indeed possible that bad/weak/poor signal in our place could drain my battery..

and sorry, will use the latest stable version hehe :D
[BetterBatteryStats] alexinna:
O yes week signal will eat your battery that is a known fact. You can try to disconnect data when you don't needed as you did for this test and only start it periodically to check e-mails and so on. Good luck!
[BetterBatteryStats] alexinna:
Testing 1.10RC1

Some values are still negative. Examples:

Screen On (): (-1247 s) Ratio: -2.5%
No Data Connection (): (-941 s) Ratio: -1.9%
No or Unknown Signal (): (-941 s) Ratio: -1.9%
CDMA (Phone): 12 s (12 s) Count:-39 -0.1%
ActivityManager-Launch (Android System): 3 s (3 s) Count:-154 -0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 s (2 s) Count:-2 -0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:-201 -0.0%
sleep_broadcast (Android System): (-5 s) Count:-192 0.1%
[BetterBatteryStats] vkk178:
Probably a silly thing to ask, but I am not able to set custom references or see kernel wake locks with the symbiosis kernel. But strangely it works with the etana kernel. Any idea why? I am noticing large drains possibly because of wake locks..

Fyi : I also tried installing the app as a system app..
[BetterBatteryStats] kmetek:
couldn't find the info how to produce a valid isle dump :D
[BetterBatteryStats] Karpfenhai:
:banghead::screwy::D

Auto correction sucks.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] chamonix:
If you don't tell me what faffing is I can't tell whether it's good or bad.

My request is not to bug you or to try to discuss bugs away that are obviously there. I requested the dumpfile and logcat to be synchronous for one single reason: in the last logcat I saw an entry telling that the ref was created. This was not there the previous logcat as bbs failed showing the dialog. Now as I am blind I wanted confirmation (or not) if the reference was really created.

To put it in other words : I can only help you if you help me. If you are pissed and don't want to it is fine, I can accept that and move on to other open issues

Edit: typos
[BetterBatteryStats] chamonix:
I guess I did a mistake in naming the package for b4. I'll check it and remove if required
[BetterBatteryStats] chamonix:
Does the raw kernel Wakelocks work? If not we should look closer into permissions / format of /proc/wakelocks
[BetterBatteryStats] vkk178:
I can see raw kernel wake locks
[BetterBatteryStats] gogol:
The CPU States only shows:

Since xxxx

1 kHz

---%

My device is Galaxy Nexus, stock ROM, stock Kernel, not-rooted, 4.1.1.

Is this known issue with the latest version?

It used to be working fine. I can see all the CPU states.

I rebooted my phone, same issue.

On the other hand, the "CPU Spy" is able to show correctly.

PS: I am using the donated version.

Thanks.
[BetterBatteryStats] M.A.K:
Faffing is doing pointless tasks just for the sake of doing something. Such as installing an app so you can dump a file that shows no custom ref when the app has already told you there's no custom ref...

The custom ref is only one. All of the ref's are broken so focusing on the effect of a dialog which couldn't possibly be affecting most of the ref's is faffing to the point of distraction; Especially as the app still says there's no custom ref anyway.

Some simple debugging around the whole referencing procedure should show straight away where the problem lies and I'll be more than happy to help out with this.

Please understand that in expressing my opinion I mean no offense at all, but it is my opinion none the less. And if I do offend, please remember that I'm not the only one that this problem affects.
[BetterBatteryStats] Stileth:
Testing RC1 and when I enable root functions the app stops working and closes. After running again the check box is enabled, but when I try again to disable/enable it does same thing, stops.

Also shows no reference, fallback to since boot, but still nothing there.

Edit: after phone reboot getting all these errors in screenshots.. logcat included

Odoslané z GT-I9100 cez Tapatalk 2
[BetterBatteryStats] xelra:
I just installed superuser again to check if the problem with it still persists.

Yes, the confirmations still don't get saved. SuperSU works fine though.
[BetterBatteryStats] alexinna:
At this point we all know that a new version has some fundamental changes and not everything is working for everybody (not yet!). So let's not get frustrated and try to help chamonix to finish what he started. I think at the end we all will benefit from it.
[BetterBatteryStats] chamonix:
I am not offended :)

But you must know one thing:if I could reproduce I would debug. Now the problem is I can't reproduce on any of my devices covering android 2.1, 2.2, 2.3, 4.0, 4.1

So I need logs and reports, and the possibility to exclude and confirm. That's debugging old-school based on traces, tedious but it works
[BetterBatteryStats] chamonix:
What superuser version and what bbs version? I have superuser 3.2 on 4.1 and with rc1 it asks only once as I Ave completely rewritten the su code to work around the superuser problem of not handling multiple su -c commands
[BetterBatteryStats] chamonix:
What version exactly? Please provide a logcat
[BetterBatteryStats] chamonix:
I will be pushing rc2 later today, focusing on the FC occurring when checking the root features and a few other fixes. After that I will immerge in logcats
[BetterBatteryStats] vkk178:
Would this fix the issue with the symbiosis kernel I raised about in my earlier 2 posts. Thx
[BetterBatteryStats] chamonix:
Release 1.10RC2

New version is up with some minor fixes (see post #2)
[BetterBatteryStats] chamonix:
No, you didn't get me enough info. Please tell me what reference you are using (if it's since unplugged I assume that you have plugged/unplugged after boot), tell me if the problem that you have is the same with all references, provide a dumpfile and a logcat
[BetterBatteryStats] chamonix:
What I see in the logs:

dumpfile: Since unplugged: Reference since_unplugged_ref created 10 d 20 h 29 m 11 s

logcat:

08-22 22:03:53.804 D/StatsProvider(17521): Current value: Deep Sleep 10 d 14 h 56 m 6 s (917766 s) Ratio: 93.0%

08-22 22:03:53.804 D/Misc (17521): Substracting Deep Sleep 10 d 2 h 16 m 4 s (872164 s) in 10 d 20 h 29 m 11 s (937751 s) Ratio: 93.0% from Deep Sleep 10 d 14 h 56 m 6 s (917766 s) in 11 d 10 h 5 m 40 s (986740 s) Ratio: 93.0%

08-22 22:03:53.804 D/StatsProvider(17521): Result value: Deep Sleep 12 h 40 m 1 s (45601 s) Ratio: 93.1%

Clearly the reference "since unplugged" has not been update for a long time.

Has your phone been running without reboot for 10 days?

Anyway I assume that you have plugged/unplugged your phone since then because if not you would have sold it and be rich :)

Could you please plug/unplug once, check it the dumpfile has updated the reference timestamp and if no (the values will be negative again) provide a logcat. I am looking for WriteUnpluggedReferenceService logging that is has been called.
[BetterBatteryStats] chamonix:
I have never seen this error:

E/StatsActivity( 3473): android.content.ReceiverCallNotAllowedException: IntentReceiver components are not allowed to register to receive intents
E/StatsActivity( 3473):	at com.asksven.betterbatterystats.StatsActivity.onCreate(StatsActivity.java:338)
E/StatsActivity( 3473):	at android.app.Activity.performCreate(Activity.java:4470)
E/StatsActivity( 3473):	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1052)
E/StatsActivity( 3473):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1931)
E/StatsActivity( 3473):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1992)
E/StatsActivity( 3473):	at android.app.ActivityThread.access$600(ActivityThread.java:127)
E/StatsActivity( 3473):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1158)
E/StatsActivity( 3473):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/StatsActivity( 3473):	at android.os.Looper.loop(Looper.java:137)
E/StatsActivity( 3473):	at android.app.ActivityThread.main(ActivityThread.java:4511)
E/StatsActivity( 3473):	at java.lang.reflect.Method.invokeNative(Native Method)
E/StatsActivity( 3473):	at java.lang.reflect.Method.invoke(Method.java:511)
E/StatsActivity( 3473):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:980)
E/StatsActivity( 3473):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:747)
E/StatsActivity( 3473):	at dalvik.system.NativeStart.main(Native Method)

I feel I'll learn something today.
[BetterBatteryStats] fede_79:
Ticking "add debug info to logcat" solve my issue that "since" value show always 0s. If I untick that option in advanced settings no longer works and "since" value returns to 0s.

Inviato dal mio GT-I9100 con Tapatalk 2
[BetterBatteryStats] chamonix:
:good:

confirmed, #258, fixed for RC3
[BetterBatteryStats] chamonix:
Please test if RC2 has this problem. I tried a better fix to an bug handling that preference
[BetterBatteryStats] chamonix:
First I recommend that you enable the "debug" advanced preference to get more info to your logcat.

Second I see that all your references are empty. Have you booted or plugged/unplugged your phone after installing BBS?
[BetterBatteryStats] chamonix:
Except that you use a task killer (bad!) this logcat does not show anything about BBS
[BetterBatteryStats] Stileth:
Great, all works fine now. :highfive: No FC after enabling and also after reboot it started to collect data. I like the real icons of the programs :good:
[BetterBatteryStats] chamonix:
Release 1.10RC3

RC3 is up, see changelog in post #2 for fixes
[BetterBatteryStats] bataya:
+1, rc2 after reboot work ok. :)
[BetterBatteryStats] mahercs:
With 1.10RC3, Process is still showing up with "No reference since unplugged yet". Silly question, but would I need to plug it in to get a fresh read after updating or should the app carry the values over from RC2 (which also had this message)?
[BetterBatteryStats] Rob2222:
Hello,

can you check if you have BBS installed twice, like I had? There was a problem with 1.10b4, which could cause this.

BR

Robert
[BetterBatteryStats] alexinna:
I think if you see such message "since unplugged" reference was not set in RC2 so nothing could be carried over. Suggest to plug/unplug now and check.

Just installed RC3 and it shows stats since unplug without actually plug/unplug. So yes BBS should be able to read references from the previous version but only when reference was set.
[BetterBatteryStats] mahercs:
While that makes some sense, I can't figure out why RC2 didn't have a reference point. First time it's happened to me, but I'll see what happens when I get a chance to plug/unplug it
[BetterBatteryStats] vkk178:
Kernel wake locks are not displayed for any reference I choose. Attached below are 2 log files. The first log is when I tried to set a custom ref ( the one with the error ). The other one was when I select kernel wake lock for unplugged event

Also here below is the contents of the directory with the error..

# cd /sys/devices/system/cpu/cpu0/cpufreq/

# ls

UV_mV_table

affected_cpus

cpu_temp

cpu_volt_max

cpu_volt_min

cpu_voltage

cpuinfo_cur_freq

cpuinfo_max_freq

cpuinfo_min_freq

cpuinfo_transition_latency

frequency_voltage_table

related_cpus

scaling_available_frequencies

scaling_available_governors

scaling_driver

scaling_governor

scaling_max_freq

scaling_min_freq

scaling_setspeed

scaling_step_freqs

scaling_step_volts

Ps do let know if you need anything else
[BetterBatteryStats] alexinna:
Testing 1.10RC3

I think so. Even more now. About shows up time 299:54:20. Do you think I need to reboot to make BBS work correctly?

Installed RC3 and plugged/unplugged but reference is not set correctly:

08-23 23:08:02.568 I/BroadcastHandler(10486): Received Broadcast ACTION_POWER_DISCONNECTED, serializing 'since unplugged'
08-23 23:08:02.588 I/WriteUnpluggedReferenceService(10486): Called at 2012-08-23 23:08:02
08-23 23:08:02.588 D/Globals (10486): Wakelock BBS_WAKELOCK_WHILE_SAVING_REF aquired
08-23 23:08:02.588 I/References(10486): Create ref since_unplugged_ref at 12 d 11 h 9 m 48 s
...
08-23 23:08:02.828 D/StatsProvider(10486): Processing Other since
08-23 23:08:02.828 D/StatsProvider(10486): Reference used: Reference is null
08-23 23:08:02.828 D/StatsProvider(10486): It is now 2012-08-23 23:08:02
08-23 23:08:02.828 D/StatsProvider(10486): Substracting [Misc [m_name=Deep Sleep, m_timeOn=1000857973, m_timeRunning=1076988267], Misc [m_name=Awake, m_timeOn=76130294, m_timeRunning=1076988267], Misc [m_name=Screen On, m_timeOn=2208519, m_timeRunning=1076988267]]
08-23 23:08:02.828 D/StatsProvider(10486): from
08-23 23:08:02.828 D/StatsProvider(10486): Current value: Deep Sleep 11 d 14 h 57 s (1000857 s) Ratio: 92.9%
08-23 23:08:02.828 D/StatsProvider(10486): Current value: Awake 21 h 8 m 50 s (76130 s) Ratio: 7.1%
08-23 23:08:02.828 D/StatsProvider(10486): Current value: Screen On 36 m 48 s (2208 s) Ratio: 0.2%
08-23 23:08:02.848 D/StatsProvider(10486): Processing CPU States since
08-23 23:08:02.848 D/StatsProvider(10486): Reference used: Reference is null
[BetterBatteryStats] xelra:
With RC2 superuser works fine now.

Sorry I was still on the beta when I reported. I just can't keep up with your fast development.

You code faster than I install apps. ;)
[BetterBatteryStats] Stileth:
RC3 after another phone reboot went crazy again. Logcat attached.

EDIT: strange thing, after I posted and the phone was with screen off for several minutes BBS catched up and now is showing proper stats in all windows with reference since boot. Logcat attached.
[BetterBatteryStats] mmm286:
Hi,

I have Galaxy s2. Today at 07.20 I have 100% battery. At 13.20 I have 35%. I cant understand. Could you see the logs? Many thanks and sorry for my english!
[BetterBatteryStats] alexinna:
Please read post #1 and follow instruction to produce idle dump file. Attached file shows

"vbus_present" (): 3 h 49 m 14 s (13754 s) Cnt:(c/wc/ec)1/0/1 39,2%

that usually happens when phone connected to charger/USB. In a mid time I can suggest you start looking at TweetTopics Lite that wakes your phone way too may times.
[BetterBatteryStats] chamonix:
In this specific case you need to plug/unplug as the bug fixes that specific problem, that ref's created with previous versions did not contain the baseline data for processes.
[BetterBatteryStats] chamonix:
Thanks for confirming. I am happy that this is being solved, coding are the problem superuser has with multiple commands from one app. This I guess will make a lot of users happy
[BetterBatteryStats] chamonix:
I am a little confused. Are you referring to kernel Wakelocks or cpu states?
[BetterBatteryStats] vkk178:
I was referring to kernel wake locks. I listed the contents of the cpu directory as additional info because, in the first log it pointed to some path missing ..
[BetterBatteryStats] chamonix:
The problem is not that BBS can not read the cpu states but the fact that there is no reference to substract to:

Since charged: Reference since_unplugged_ref created 2012-08-24 08:43:20 (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)

If it was there in the morning and lost after that there are two explanations:

- the reference got lost / overwritten

- your phone booted at 08:43

You may want to try the last RC from post #1. You can install it without interference with the 1.9.2.2 you have installed.
[BetterBatteryStats] chamonix:
About cpu states. The file used to get the states is /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state and it's not in that directory. Does CPUSpy give you any joy?

I'm checking the logcats and will give you a separate feedback on those.
[BetterBatteryStats] chamonix:
Unfortunately the logs are shortened and do not contain the whole sequence. Could you provide a non truncated log? I have no problem in reading 10000 lines of logs as I use grep.
[BetterBatteryStats] gogol:
I might have rebooted the phone in the morning.

But then, why the BBS still cannot have the correct value few hours after that?

The dump file should be created after 16:00 afternoon.

How come the reference got lost?

I dont use BBS in any strange way.

I will try to reinstall BBS, see if that fix the issue.

And I might try the RC later.

Thanks for your feedback, really appreciated :)
[BetterBatteryStats] ybres:
Quick question:

In a period of 2d 17h with normal usage (mostly phone calls with minimal 3g and WiFi) my Awake - Screen On = 30min. (No out of the ordinary Partial Wakelocks or Alarms)

Is this a good amount?