Android os exception fills log

[DaAQVWwV]

Hi Forum,

I got to look in Android system logs and see lot of same exceptions like that:

java.lang.ClassCastException: java.lang.Integer cannot be cast to android.os.Parcelable
android.os.Bundle.getParcelable(Bundle.java:946)
android.app.Notification.fixDuplicateExtra(Notification.java:2888)
android.app.Notification.fixDuplicateExtras(Notification.java:2878)
android.app.Notification.readFromParcelImpl(Notification.java:2207)
android.app.Notification.<init>(Notification.java:2135)
android.service.notification.StatusBarNotification.<init>(StatusBarNotification.java:104)
android.service.notification.StatusBarNotification$1.createFromParcel(StatusBarNotification.java:194)
android.service.notification.StatusBarNotification$1.createFromParcel(StatusBarNotification.java:191)
android.os.Parcel.readParcelable(Parcel.java:2774)
android.os.Parcel.readValue(Parcel.java:2668)
android.os.Parcel.readArrayMapInternal(Parcel.java:3037)
android.os.BaseBundle.initializeFromParcelLocked(BaseBundle.java:288)
android.os.BaseBundle.unparcel(BaseBundle.java:232)
android.os.BaseBundle.getString(BaseBundle.java:1160)
com.fitbit.device.notifications.listener.service.rpc.servicetoapp.a.a$a.a(SourceFile:2)
com.fitbit.device.notifications.listener.service.rpc.servicetoapp.eventlisteners.a.a(SourceFile:3)
com.fitbit.device.notifications.listener.service.rpc.servicetoapp.ListenerServiceMessageHandler$handleMessage$$inlined$forEach$lambda$1.invoke(SourceFile:2)
com.fitbit.device.notifications.listener.service.rpc.servicetoapp.ListenerServiceMessageHandler$handleMessage$$inlined$forEach$lambda$1.invoke(SourceFile:1)
com.fitbit.device.notifications.y.c(SourceFile:1)
com.fitbit.device.notifications.y.a(SourceFile:1)
com.fitbit.device.notifications.w.run(SourceFile:1)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
java.lang.Thread.run(Thread.java:764)

Looks like it is related to fitbit app 2.94 i have installed.

Can someone help to understand what it is and how to fix it?

Thanks,

[AndreaFitbit]

Thanks for getting back to us @DaAQVWwV. I apologize for the delayed response and will be happy to assist you with your Android system logs inquiry. 

We're not able to answer questions pertaining to the code development of the Fitbit app.

Please explain more if you have questions about your Fitbit or the App and I'll provide you with assistance.

Keep on visiting the forums. 

[SunsetRunner]

The exceptions thrown by Fitbit app were there always. This one I see the first time. Without the code, I can only describe what I see. There is a class cast exception thrown as the object obtained during deserialization ( in Android API it's called Parcelable ) is type-casted to the wrong type. It seems to be an unhandled exception or sometimes during lazy development, it's just expected to fail so to prevent the crash it has been wrapped with try/catch block ( but then only by explicit logging it can appear in the logcat output ). Looking from the beginning, the separate thread is listening to incoming RPC communication from another source ( could be Fitbit sync service that I see running ), it receives a message ( serialized object ) and looks like it tries to instantiate status bar notification but it ends up with throwing an exception. I would have to debug it further to find out what's going on there but nobody pays me for that 😄 I expect it should be rather harmless if an exception is caught. Probably, the only missing thing is status bar notification that the App is trying to set. But since nobody pays me for debugging the app I'm not gonna be getting any further into it 😛

[Rich_Laue]

In general the comunity of Fitbit users and @AndreaFitbit are not programmers and know little to nothing on this subject. 

I do have an idea of what an exception is but have no idea where to look even if I figure out how to read the log files. 

[AndreaFitbit]

Thanks for getting back to us and for your comments @SunsetRunner. As @Rich_Laue mentioned, I am not a programmer and really don't understand much about this subject. I can provide you with assistance that is Fitbit product related.

Thank you for your comments @Rich_Laue.

Keep on visiting the forums. 

[DaAQVWwV]

Thanks for replies,

Looks like there is no way to communicate to Fitbit's developers as Forum is community support and no bug tracker/reporter. 

This exception can help to explain why we see complains about battery consumption, as on my phone it is the biggest battery eater (Fitbit is 8%, next one is 3%). 

It is frustrating to own good hardware device with buggy software 😞

But thanks to Community supporters we have some work around for most of bugs

Thanks everyone! 

[Rich_Laue]

Interesting. I see Fitbit at 2.2 at number 7 with Chrome 29.1 in first place 

[DaAQVWwV]

Sure, it depends on use cases. If you play games for hours - fitbit will not be biggest for sure 🙂

I'm talking for my use - this time phone was mostly idle, I did not even check fitbit itself :). So for my use scenario (mostly idle) fitbit is by far biggest power consumer.

Thanks,

[Rich_Laue]

The guy in the phone store says that my usage is low averaging omg 73 gig a month, also with unlimited hot spot so I use the phones network for everything. 

[SunsetRunner]

@DaAQVWwV I remember times when Fitbit synv service and app were at the top of power consumption but from what I see now it isn't h

that bad anymore ( especially when we talk about backgroud activity ). Spotify and Chrome on my phone are lot worse ( and Spotify apparently did something wrong because system wants to put this app to sleep due to power consumption ). But true that errors may lead to the battery drain but there is long way to do so. If error causes infinite loop of retrying and won't give priority to other threads ( spin lock ) that would be not only bad but it would show really lack of skills of developers. Does the Fitbit app shows somehow at the top of CPU usage ( 'top' tool or check through Settings ). If you notice high CPU usage ( with top you can see hardware threads as well ) while the exception is thrown then there is a bug to be reported. I don't think however that Fitbit has channels to do so. This forum is mostly about restarting and factory resets 🙂 Btw. long time ago I had a device that I could use to measure the power consumption of the apps and it showed lots of interesting ways to improve the issue of power consumption, for example in the UI apps introducing dark theme 🙂 I think there was somewhere feature suggestion for that already.

@Rich_Laue power not data consumption. Different things.