Okay, never mind, it likely doesn't matter. According to Google search the warnings do come up in people's logs, perhaps even fairly often, but don't seem to be related to any perceived problem. Thanks anyway.
On Mon, Sep 12, 2011 at 3:40 PM, Latimerius <[email protected]>wrote: > Hello, > > I'm slightly worried about SensorService warnings I sometimes get when I > call SensorManager.unregisterListener(). They look like this: > > W/SensorService( 88): listener with binder > android.os.BinderProxy@4670c9f0, doesn't exist (sensor=BMA150 3-axis > Accelerometer, id=0) > W/SensorService( 88): listener with binder > android.os.BinderProxy@46804af0, doesn't exist (sensor=AK8973 3-axis > Magnetic field sensor, id=1) > > I googled for the parts of the message that don't vary but pretty much the > only relevant hit I got was the SensorService source. It says in a comment > that this usually happens if registration fails but the client doesn't > handle the failure properly and still tries to unregister later on. > > Well I'm pretty sure that's not my case - I do check the registerListener() > return value and take note if something goes wrong. However, it never seems > to go wrong, and I'm still getting the warnings. On top of that, they don't > come up reliably and so far I've been unable to see a pattern. > > I also checked my code for inadvertent double unregistration but that > doesn't seem to be the case, either. > > Has anyone got this too and dealt with this successfully? I most certainly > don't want to mess up my sensor listener unregistration and drain people's > batteries ... > > Thanks in advance! > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
