Service crashes when stopping a scan about android-fleet-management-sdk

[cmelchior]

It might be related to the same issue in the Radius Network SDK as I didn't see the behavior when just around a few iBeacons (at home), but at the office where we have many including a lot of Gimbals, it crashes constantly.

RadiusNetworks/android-ibeacon-service#16
https://code.google.com/p/android/issues/detail?id=67272

[wiktor]

It is the same bug you are seeing.

Please do read:
http://developer.radiusnetworks.com/2014/04/02/a-solution-for-android-bluetooth-crashes.html
https://github.com/RadiusNetworks/bluetooth-crash-resolver

[mohitb117]

Hey Wiktor
So I am assuming the fact that Estimote does not expose any BluetoothLE Device Handles , then in the next releases you will handle the above using the RadiusNetworks BluetoothCrashResolver??

[wiktor]

Not sure yet, I need to check it thoroughly.

[cmelchior]

As far as I can tell, there is nothing I can do about this bug when using the EstimoteSDK in the current version (0.4.1) as the scanning part of the SDK is closed source.

Using the 3rd party app from Radius Network seems to fix this temporarily, although it comes back rather quickly in a environment with many iBeacons.

This is IMHO a blocking issue for using the Estimote SDK as you cannot control when the user encounters such an environment, and I hope you consider either adding a hook to the scanner code or implement the fix (which admittedly is not 100% foolproof according to RadiusNetworks description).

But waiting for Google to fix their Bluetooth stack is not an option IMO.

[wiktor]

Christian, currently all iBeacon libraries are unfortunately affected by that.

Having said that all BLE on Android community is working on that and Radius Network (with Stack Overflow people) is so far the best we as community come.

[cmelchior]

I know. I'm sorry if my comment sounded harsh.

I am experiencing this problem on a brand-new Google Nexus 5, after testing it for a few days with four Estimote iBeacons. Strangely, the error showed up with this morning at around 11:00 while the app had been dealing with these four beacons just fine in the preceding hours.

[francisdb]

I can confirm the temporary fix mentioned on the Radius blog post: letting the Radius iBeacon Locate app scan for a while to trigger their crash resolver that truncates the device list.

https://play.google.com/store/apps/details?id=com.radiusnetworks.ibeaconlocate

[QuentinGregoire]

I have same problem with only 1 beacon (estimote)

Radius BLE Crash resolver Fix doesn't help for me.

Estimote app crash the bluetooth after 25-30 minutes with 1 beacon (estimote)

I try a force fluch with the Radius BLE Crash resolver app but it's doesn't help, it's crash after few second.

Phone : Galaxy Nexus with BLE support
Android : 4.3

Any idea ?

[wiktor]

It does not always work immediately so give it some time to operate.

[mohitb117]

so there is still no progress on the bluetooth adapter?

[wiktor]

There is only workaround from Radius Networks. Android L release fixes that though.

On Fri, Aug 29, 2014 at 7:28 PM, Mohit [email protected] wrote:

so there is still no progress on the bluetooth adapter?

Reply to this email directly or view it on GitHub:
#44 (comment)

[diegoboruc]

Hi, we are using the Estimote android component for Xamarin. When we try to use the bind for the solution (https://github.com/chrisriesgo/xamarin-android-ibeacon-service) it seems that is expecting a BluetoothDevice object as a parameter, but the estimote library discover method returns objects of type EstimoteSdk.Beacon. Do you know some workaround?

[wiktor]

The library you are using is not wrapper around Estimote SDK so it will not work.

I have the same problem ... anyone solve this ?