Releases: Estimote/Android-Fleet-Management-SDK
Releases · Estimote/Android-Fleet-Management-SDK
The one with Android L
Fixes #85: compatibilty with Android L
The one with remote process
The one with knowing which beacons triggered enter region event
The one with connection
- Introducing ability to change beacon's UUID, major, minor, broadcasting power, advertising interval (see BeaconConnection class).
- Dropping Guava dependency.
The one with fix for simulated beacons
Fixes bug when simulated beacons were not seed even when using Estimote's proximity UUID.
The one with better monitoring and sorting beacons
- Background monitoring is more robust and using AlarmService to invoke scanning.
- Default values for background monitoring were changed. Scanning is performed for 5 seconds and then service sleeps for 25 seconds. Those values can be changed with BeaconManager#setBackgroundScanPeriod.
- Beacons reported in RangingListener#onBeaconsDiscovered are sorted by accuracy (estimated distance between device and beacon).
- Bug fixes.
The one with monitoring support
- IMPORTANT: package changes BeaconService is now in
com.estimote.sdk.service service
. You need to update yourAndroidManifest.xml
service definition tocom.estimote.sdk.service.BeaconService
. - Support for monitoring regions in BeaconManager.
- Region class: it is mandatory to provide region id in its constructor. This matches CLRegion/ESTBeaconRegion from iOS.
- Beacon, Region classes now follow Java bean conventions (that is getXXX for accessing properties).
- Debug logging is disabled by default. You can enable it via
com.estimote.sdk.utils.L#enableDebugLogging(boolean)
.