Evothing Estimote Beacon Plugin - Ranging Anomoly on Android 5.0
Posted: 00:10, 18 Apr 2015
Hey
We have been using evothing's phonegap plugin for estimote beacons in one of our projects. We started our project using version 0.6.0 till recently when we upgraded the plugin to version 0.7.1 .
Previous version of the plugin was causing our app to fatally crash when we try to start beacon ranging on any Android 5.0 (Lollypop) devices. It was working perfectly for other android i.e. 4.3 , 4.4.2 devices. We were getting all the beacon during beacon ranging . In our app, beacon ranging is done for a duration of 3 seconds and it is repeated after every 5 second. During each interval we get the beacons.
After updating to newer version (0.7.1) our app didn't crash on Android 5.0 but we have detected that the behaviour of beacon ranging was very different from what we use to have. Currently when beacon ranging is started , it runs for 10 seconds giving us the beacons in vicinity and then it automatically stop for random amount of time. Time varies from 30seconds to over 5+ minutes.
Is there any new configuration or settings that we are missing ?
Has there been any change in the core functionality of Estimote SDK that could have caused new beacon ranging behaviour ?
Is there any way we can achieve the same beacon ranging functionality on this version of plugin ?
We are at a very critical stage of this project in which your plugin is play a very crucial part and your immediate help would be very much appreciated.
Thank you.
We have been using evothing's phonegap plugin for estimote beacons in one of our projects. We started our project using version 0.6.0 till recently when we upgraded the plugin to version 0.7.1 .
Previous version of the plugin was causing our app to fatally crash when we try to start beacon ranging on any Android 5.0 (Lollypop) devices. It was working perfectly for other android i.e. 4.3 , 4.4.2 devices. We were getting all the beacon during beacon ranging . In our app, beacon ranging is done for a duration of 3 seconds and it is repeated after every 5 second. During each interval we get the beacons.
After updating to newer version (0.7.1) our app didn't crash on Android 5.0 but we have detected that the behaviour of beacon ranging was very different from what we use to have. Currently when beacon ranging is started , it runs for 10 seconds giving us the beacons in vicinity and then it automatically stop for random amount of time. Time varies from 30seconds to over 5+ minutes.
Is there any new configuration or settings that we are missing ?
Has there been any change in the core functionality of Estimote SDK that could have caused new beacon ranging behaviour ?
Is there any way we can achieve the same beacon ranging functionality on this version of plugin ?
We are at a very critical stage of this project in which your plugin is play a very crucial part and your immediate help would be very much appreciated.
Thank you.