I integrated Estimote Android SDK into my project. The client purchased several Estimote beacons.
Now I can detect them with Google Nexus and Asus Zenfone 6 but can’t do it with Samsung devices and Lenovo.
Android version: 4.3, 4.4 and 5.0.
Estomote SDK: 0.6.1
Also, I installed the nRF Master Control Panel (BLE) app. It detects beacons on Samsung S3 eventhough OS didn’t recognise them.
We have updated our SDK to v0.7 which makes significant updates to speed of discovery of beacons. There was a bug which might have affected you on those devices. Can you give it a try?
There are 2 things you can do in order to speed up discovery:
1/ Decrease advertising interval of the beacon. By default it is 950 ms, with Estimote app you can set it to 300ms.
2/ BeaconManager by default returns result every 1 second. You can configure it to return results more ofter via setForegroudScanPeriods.
My samsung S5 don’t recognize any beacon I put 3 beacons in 3 different parts and try to walk near this beacons with the app open but nothing happens also I have a beacon near me and it pass 20 minutes and the app didn’t find the beacon.
@Vlad This Lenovo looks very strange. It returns list of Bluetooth Low Energy devices but packet that is sent from our beacon looks truncated. We observed similar thing on Micromax devices.
1/ Does your up24 band works with this device?
2/ Can you rerun this test for Samsung S5 as nRF Master Control Panel shows properly packet from our beacons.
My client has Samsung S5 but can’t debug the device. So he can’t read log files from system. In order to read logs he need root access to the system. What do you recommend?
BTW: Samsung S3 detects beacons sometimes, sometimes no.