This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
OnPositionUpdate being called with same LocationPosition Coordinates for 10+ times #27
Open
1 task done
Prerequisites
My beacons have Estimote Location packet enabled (Check it in the Estimote Cloud, or via app)
My Android device/devices supports BLE and has Android OS version >= 5.0.0
My Android device/devices have bluetooth enabled
My app has Location Permissions granted
Basic information
Estimote SDK version: [('com.estimote:indoorsdk:2.5.3')]
Android devices affected: [Samsung galaxy Tab A (2018) , Samsung galaxy S7 ]
Android OS version affected: [('Oreo 8.0.0', 'Oreo 8.1.0')]
Beacon hardware version: [(4.14.4).]
Description
[
we are facing a serious lag at producing new coordinates after receiving bluetooth packets and feeding them to IndoorLocationManager
onPositionUpdate call back gets called with same coordinates for 10+ times before passing new coordinates.
knowing that we tried to use a manual BluetoothScanner set-up and configured with every power mode from 'com.estimote:scanning-plugin:0.25.1'
]
Steps to reproduce:
this occurs using the sample android app for indoorLocationSDK, even with a standalone app using either JAVA or Kotlin
Expected behavior: [locate phone inside the map with updated coordinates every time onPositionUpdate gets called]
Actual behavior: [onPositionUpdate gets called with same locationPosition(coordinates) for 10+ times]
IOS SDK works fine and updates position's coordinates every second
The text was updated successfully, but these errors were encountered: