Potential Bug in the SDK

[mohitb117]

Hi Wiktor,
The Estimote SDK is pretty Solid on working with Estimotes.

I am working around Bluetooth LE beacons including Estimote and Qualcomm Gimbal's and they Estimote SDK does not behave well with Gimbal Bluetooth Beacon Signals.

The Estimote BeaconService tries to scan the nearby Bluetooth LE devices, seems to encounter Gimbals and Fails to parse Gimbal Bluetooth LE devices and throws
NullPointerException and Crashes the BluetoothShare Scanning module and restarts the Bluetooth Adapter...

Here are the Logs:-

02-20 17:48:19.908 15209-15220/com.example.estimote_app W/Utils﹕ Manufacturer specific data should have 26 bytes length: 1107ad7700c6a00099b2e2114c24934a0c960cff8c00f68fd804a9fd63548e00000000000000000000000000000000000000000000000000000000000000
02-20 17:48:19.908 15209-15220/com.example.estimote_app W/BluetoothAdapter﹕ Unhandled exception: java.lang.NullPointerException

02-20 17:48:19.938 15209-20253/com.example.estimote_app D/BluetoothAdapter﹕ stopLeScan()

02-20 17:48:19.948 15209-15209/com.example.estimote_app D/BreadKrumBluetoothReceiver﹕ Transmitting Beacons Entered:- 0 :: []

02-20 17:48:19.948 15209-20253/com.example.estimote_app D/BluetoothAdapter﹕ startLeScan(): null

02-20 17:48:19.948 15209-15209/com.example.estimote_app D/BreadKrumBluetoothReceiver﹕ Transmitting Beacons Exited:-3 :: [Beacon{macAddress=EF:A0:61:44:0F:30, proximityUUID=b9407f30-f5f8-466e-aff9-25556b57fe6d, major=3888, minor=24900, measuredPower=-76, rssi=-68}, Beacon{macAddress=C7:E0:8A:A6:1A:62, proximityUUID=b9407f30-f5f8-466e-aff9-25556b57fe6d, major=6754, minor=35494, measuredPower=-74, rssi=-80}, Beacon{macAddress=F9:57:DA:5A:67:09, proximityUUID=b9407f30-f5f8-466e-aff9-25556b57fe6d, major=26377, minor=55898, measuredPower=-81, rssi=-85}]

02-20 17:48:19.948 15209-15209/com.example.estimote_app D/BreadKrumBluetoothReceiver﹕ Entered region of BreadKrum EF:A0:61:44:0F:30
02-20 17:48:19.948 15209-15399/com.example.estimote_app D/BluetoothAdapter﹕ onClientRegistered() - status=0 clientIf=5
02-20 17:48:19.958 15209-15209/com.example.estimote_app D/BreadKrumBluetoothReceiver﹕ Entered region of BreadKrum C7:E0:8A:A6:1A:62

02-20 17:48:20.959 15209-20253/com.example.estimote_app D/BluetoothAdapter﹕ stopLeScan()

02-20 17:48:21.049 15209-20253/com.example.estimote_app E/BluetoothAdapter﹕ Failed to stop scan and unregisterandroid.os.DeadObjectException

[wiktor]

Does it happen constantly?

[mohitb117]

oh yes.. every scan of the possible beacons in the region, the gimbals are intercepted and hence the problem.

Once the Beacons are out of range.. the exceptions stop ... this is not a big deal as far as dealing solely with Estimotes but Gimbals can cause UnExpected behavior in any application using Estimote SDK in their frameworks!

The Gimbals Manufacturer specific Data Parse fails as far as I can tell from the logs:-

02-20 17:48:19.908 15209-15220/com.example.estimote_app W/Utils﹕ Manufacturer specific data should have 26 bytes length:
1107ad7700c6a00099b2e2114c24934a0c960cff8c00f68fd804a9fd63548e00000000000000000000000000000000000000000000000000000000000000
02-20 17:48:19.908 15209-15220/com.example.estimote_app W/BluetoothAdapter﹕ Unhandled exception: java.lang.NullPointerException

[mohitb117]

I personally like Estimote SDK .. Great JOB +1 , but it seems possible to crash APPS using Gimbals which have different BlutoothLE device params and throw Exceptions while parsing them

[wiktor]

Do you have those blue Gimbals? (http://cdn0.mos.techradar.futurecdn.net///art/events/Uplinq-2013/Beacon/Beacon-08-578-80.JPG)

I'll deep dive into it. I'm a bit worried as this unhandled exception is in BluetoothAdapter which is Android class in their BluetoothStack :/.

[mohitb117]

Yes.. I am working on a project to use Bluetooth LE devices and I am using Estimotes and was thinking using Gimbals.(I have the blue gimbals) but decided against them due to overly complex SDK and rigid usage pattern !