Bug fixes

1.0.11 (Jul 26, 2017)

• Bug fixes

"Here and Now", Cloud GPIO, Reflect GPIO_0 state on LED

1.0.10 (Jul 21, 2017)

• Add "Here and Now" feature support. Now, "Here and Now" related settings are synchronised from Cloud in to the Beacon.
• Synchronise GPIO settings from Cloud.
• Make it possible to reflect GPIO_0 state on Beacon's embedded LED.

The one with support for Nougat devices and fixed old D3.4 beacon scanning.

1.0.9 (Jul 19, 2017)

• Old proximity beacons (D3.4) iBeacon packets are now properly scanned using BeaconManager
• Major improvements to monitoring/ranging on Nougat. The scanning relies now on internal Android mechanism, so scanning periods may slightly differ from those you set with setForegroundScanningPeriod and setBackgroundScanningPeriod.

The one with fixes again

1.0.3 (May 2, 2017)

• BeaconRegion should be now properly ranged/monitored. Related to #211
• Added Mirror Access Control flag to packet.
• Fixed NPE being thrown by KitKatScanScheduler on API 18 devices.

The one with improvements for Nougat (and fixes)

1.0.2 (April 19, 2017)

• Fixed #211 when SecureBeacon region with null UUID thrown NPE. Also fixed problem with filtering secure regions on some devices.
• Fixed #207 where Nearables and old Proximity beacons were not scanned as a ConfigurableDevice.
• Fixed #213 where temperature values in Estimote Telemetry were wrongly parsed.
• Added improvements for Nougat+ devices. Since Nougat, every application is allowed to start/stop BLE scan a maximum of 5 times per 30s. New improvements prevents many scan start/stop events, which resulted in "App XXX is scanning too frequently" logs. All start/stop requests are buffered and the most recent is executed after the delay time. You can play with the setting by yourself using new method in BeaconManager class, but we recommend using the default one (1,5s)

beaconManager.setScanRequestDelay(delayInMillis);

The one with fixes

1.0.1 (April 11, 2017)

• Fixed #206 when changing scan period after starting scan was not applied
• Fixed #205 when scan results were not sorted by RSSI.
• Fixed #187 when Estimote telemetry packets were reported as duplicates after getting out of beacon's range.
• Fixed "ClassNotFoundException" being thrown on pre-Lollipop devices when using ScanFilter class.
• Improved low-level filtering for Estimote devices.

The one with mesh

• Added support for mesh via MeshManager
• Added firmware update through mesh
• Fixed Motion Only broadcasting problems
• Added minor fixes for stability and bugfixes.

The one with Storage and fixes

0.15.0 (December 19, 2016)

• Added minor fixes to Secure UUID resolving.
• Fixed wrong parceling in EstimoteTelemetry packets

Merged from beta branch:

• Added fixes for NFC

• Added MOTION_ADVERTISING_DELAY setting.

• Added support for key-value storage on devices with firmware 4.9.0+

  • You can now push your key:value map via our SDK to device in the same way as typical setting:

  Map<String, String> map = new HashMap<>();
  map.put("myKey", "myValue");
  connection.settings.storage.writeStorage(map, new StorageManager.WriteCallback() {
    @Override
    public void onSuccess() {
      // HANDLE SUCCESS
    }
  
    @Override
    public void onFailure(DeviceConnectionException exception) {
      // HANDLE FAILURE
    }
  });

  • Reading stored values can be done without user being authorised - this will allow client apps to read stored data. For this purpose, there is a new method for quick connection to beacon: deviceConnectionProvider.getConnectionForStorageRead(ConfigurableDevice)
  • Bear in mind that the more data is stored on device the more time it takes to read it.

• Improved Estimote Analytics precision and data persistence.

The one with bulk updater

• Added support for Shake-to-connect:
  • Enabling/Disabling this setting on device via sdk
  • ConfigurableDevice has now property isShaken
• Added support for Near-to-connect:
  • Enabling/Disabling this setting on device via sdk
  • ConfigurableDevice has now property isClose
• Added Bulk Updater functionality to ConfigurableDevicesScanner:
  • You can enable it via configurableDevicesScanner.enableBulkFirmwareUpdate(BulkUpdater.BulkUpdaterCallback);
  • When enabled, bulk updater will update firmware and settings to all devices around you. This will make sure your beacons are always up to date.
  • Availabe for use in foreground, or in background if you run your ConfigurableDevicesScanner in a service/or non-main thread.
  • Returns result via one callback, so you are able to be constantly notified about process.

The one with Android Nougat support

• Added support for monitoring and ranging on Android Nougat devices.
  • Due to new Android restrictions, we can only start/stop scanning no more than 5 times per 30 seconds.
  • It is strongly recommended, to set your foreground/background scanning periods according to the new specification. If you forgot to do so, SDK will automatically update periods to avoid scan block by Nougat.
• Flag DISABLE_BATCH_SCANNING is from set to 'true' from now on. Batch scan implementation varies on many phones, and it is usually causing badly delayed scan results. If you really want to use it, just set it to 'false' in your android manifest file.
• Fixed (#168) - FATAL EXCEPTION: BeaconServiceThread