Nothing displayed on screen

[advilivda]

Starting the app, the Computing notification pops up, and once that is done, i'm left with the two drop down options. No matter what I do, nothing is shown.

Android 2.3.5
BetterBatteryStats 1.1.1.0

[asksven]

could you give me more details on the setup? what device/kernel are you on?

[advilivda]

Samsung Galaxy S GT-I9000
Kernel Version
2.6.35.12-g4a2814b
atinm@wolverine #1

ROM: MIUI Android 1.9.30

On 4 October 2011 08:26, asksven <
reply@reply.github.com>wrote:

could you give me more details on the setup? what device/kernel are you on?

Reply to this email directly or view it on GitHub:

#42 (comment)

[asksven]

There is a known issue with MIUI: have you tried aneabling/disabling the "battery monitor"?

[advilivda]

Do you mean the system's battery usage monitor? I've switched that off but
didn't seem to make a difference.

On 5 October 2011 07:59, asksven <
reply@reply.github.com>wrote:

There is a known issue with MIUI: have you tried aneabling/disabling the
"battery monitor"?

Reply to this email directly or view it on GitHub:

#42 (comment)

[asksven]

There is a discussion ongoing about this problem with MIUI. You may want to follow / contribute: http://forum.xda-developers.com/showpost.php?p=18142471&postcount=1341

I seems that for some people anabling battery monitoring in MIUI helped. Could you provide a logcat for the timeframe when you open the "partial wakelocks" view in BBS? What I am looking for is the logged sequence of BatteryStatsProxy to see if the data retrieval fails, returns nothing of wrong data.

The problem with MIUI is that there is no source code that I could check so see what changes have been made to the services / system classes so I rely on logs to try to marrow down the problem. Once this is done I could try alternatives to make BBS compatible with MIUI as I am interested in supporting as many devices / ROMs as possible.

[asksven]

oops, wrong button, I was not supposed to be closed that fast ;)

[advilivda]

Logcat extract when I selected Partial Wakelock and since unplugged

http://pastebin.com/CCGVx2Yw

I think the part you are most interested in is on line 650 onwards:

E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=275, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=258, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=266, events=0x8

On 5 October 2011 17:52, asksven <
reply@reply.github.com>wrote:

oops, wrong button, I was not supposed to be closed that fast ;)

Reply to this email directly or view it on GitHub:

#42 (comment)

[advilivda]

Strangely enough, after sending you the extract, I went and enable battery
monitoring in MIUI, and suddenly BBS is working now. Will keep you posted if
the situation changes.

On 6 October 2011 11:19, Alvin Leong advilivda@gmail.com wrote:

Logcat extract when I selected Partial Wakelock and since unplugged

http://pastebin.com/CCGVx2Yw

I think the part you are most interested in is on line 650 onwards:

E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=275, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=258, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=266, events=0x8

On 5 October 2011 17:52, asksven <
reply@reply.github.com>wrote:

oops, wrong button, I was not supposed to be closed that fast ;)

Reply to this email directly or view it on GitHub:

#42 (comment)

[advilivda]

It has stopped working again, this time a different message is captured in
the logcat:

http://pastebin.com/download.php?i=20Ag86vQ

It does appear if I just go and switch off battery monitoring, and then
switch it back on, then it will work again, but it loses all the historical
data.

On 6 October 2011 11:28, Alvin Leong advilivda@gmail.com wrote:

Strangely enough, after sending you the extract, I went and enable battery
monitoring in MIUI, and suddenly BBS is working now. Will keep you posted if
the situation changes.

On 6 October 2011 11:19, Alvin Leong advilivda@gmail.com wrote:

Logcat extract when I selected Partial Wakelock and since unplugged

http://pastebin.com/CCGVx2Yw

I think the part you are most interested in is on line 650 onwards:

E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f7d348
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 164): channel '40f92258
com.asksven.betterbatterystats/com.asksven.betterbatterystats.StatsActivity
(server)' ~ Channel is unrecoverably broken and will be disposed!
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=275, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=258, events=0x8
E/InputDispatcher( 164): Received spurious receive callback for unknown
input channel. fd=266, events=0x8

On 5 October 2011 17:52, asksven <
reply@reply.github.com

wrote:

oops, wrong button, I was not supposed to be closed that fast ;)

Reply to this email directly or view it on GitHub:

#42 (comment)

[asksven]

The first logcat seems to tell that there is something broken in the communication between the app the the battery service. I would be interested in knowing if the battery graphs from MIUI stop working at that time as wll and if this happens independentely from BBS being used.

[advilivda]

I'm not 100% sure if I understood you, so hope I got this right. Whenever
BBS stops having data for display, the MIUI battery graphs does appear to
continue to work. I'm not certain if BBS runs in the background whenever I
switch out, but I do perceived it works the longest if I kept BBS app in
display.

On 9 October 2011 20:59, asksven <
reply@reply.github.com>wrote:

The first logcat seems to tell that there is something broken in the
communication between the app the the battery service. I would be interested
in knowing if the battery graphs from MIUI stop working at that time as wll
and if this happens independentely from BBS being used.

Reply to this email directly or view it on GitHub:

#42 (comment)

[asksven]

After adding some more logging in 1.5.1 we now know more about this issue:

[CODE]com.android.internal.app.IBatteryStats$Stub.asInterface
I/BatteryStatsProxy(29817): invoking getStatistics
D/dalvikvm( 1093): GC_FOR_MALLOC freed 720K, 44% free 8481K/15111K, external 0K/0K, paused 62ms
E/JavaBinder(29817): !!! FAILED BINDER TRANSACTION !!!
I/BatteryStatsProxy(29817): retrieving parcel
I/BatteryStatsProxy(29817): reading CREATOR field
E/TAG (29817): An exception occured in BatteryStatsProxy(). Message: Bad magic number
I/BatteryStatsProxy(29817): invoking android.os.ServiceManager.getService("batteryinfo")
I/BatteryStatsProxy(29817): android.os.ServiceManager.getService("batteryinfo") returned a service binder[/CODE]

At some late point in time after many calls to the service this error "bad magic number" occurs. It is consisitent to the behavior reported by users that on MIUI the data stops being displayed after some time.