Android-Proximity-SDK icon indicating copy to clipboard operation
Android-Proximity-SDK copied to clipboard

Published 20 hours ago • verified publisher icon Estimote

Samsung Galaxy A8 does not detect beacons

Open OscarCanek opened this issue 7 years ago • 3 comments

Prerequisites

  • [ ] Put an X between the brackets on this line if you have done all of the following:
    • [x] My beacons have Estimote Monitoring enabled
    • [x] My Android device/devices supports BLE and has Android OS version >= 5.0.0
    • [x] My Android device/devices have bluetooth enabled
    • [x] My app has Location Permissions granted

Basic information

Estimote SDK version: 1.0.0, 0.5.1

Android devices affected: Samsung Galaxy A8. Model number: SM-A530F

Android OS version affected: 7.1.1

Beacon hardware version: F3.3

Description

The onEnter and onChange events are not triggered in a Samsung Galaxy A8

(Optional) Steps to reproduce:

  1. Create the observer
  2. Create the zone
  3. Start the zone observation
  4. Put the cellphone inside a beacon range

Expected behavior: Trigger the onEnter/onChange event when the phone is inside the beacon range

Actual behavior: It won't trigger any event when the phone is inside the beacon range

OscarCanek avatar Aug 06 '18 21:08 OscarCanek

Only works if I leave enabled the telemetry at the SDK. In other words, on our Samsung A8 the beacon detection only works if you don't put the withTelemetryReportingDisabled at the proximity observer

OscarCanek avatar Sep 27 '18 22:09 OscarCanek

I have this problem too.

Estimote Proximity SDK version: 1.0.3 Android devices affected: Samsung Galaxy A8. Model number: SM-A530F Android OS version affected: 8.0.0 Beacon hardware Revision: J1.9_B1.1

With Telemetry disabled I cant see any beacons (but the same code works fine on e.g. a Galaxy S8). As soon as I enable Telemetry, the beacon shows up in my app on the Galaxy A8.

Martinsbl avatar Apr 05 '19 13:04 Martinsbl

Im not sure whether it is relevant to this bug, but i noticed in my logcat that the TelemetryReporting feature seems to start 8 separate scanners in addition to the Proximity scanner:

2019-04-25 15:55:41.798 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 8, reportDelayMillis=1
2019-04-25 15:55:41.822 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 9, reportDelayMillis=1
2019-04-25 15:55:41.851 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 10, reportDelayMillis=1
2019-04-25 15:55:41.887 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 11, reportDelayMillis=1
2019-04-25 15:55:41.918 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 12, reportDelayMillis=1
2019-04-25 15:55:41.958 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 13, reportDelayMillis=1
2019-04-25 15:55:41.997 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 14, reportDelayMillis=1
2019-04-25 15:55:42.050 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 18, reportDelayMillis=1
2019-04-25 15:55:42.100 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_START, appName: my.app, scannerId: 19, reportDelayMillis=1
2019-04-25 15:55:47.452 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 8, reportDelayMillis=1
2019-04-25 15:55:47.459 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 10, reportDelayMillis=1
2019-04-25 15:55:47.467 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 11, reportDelayMillis=1
2019-04-25 15:55:47.474 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 12, reportDelayMillis=1
2019-04-25 15:55:47.482 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 13, reportDelayMillis=1
2019-04-25 15:55:47.507 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 14, reportDelayMillis=1
2019-04-25 15:55:47.518 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 18, reportDelayMillis=1
2019-04-25 15:55:47.529 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 19, reportDelayMillis=1
2019-04-25 15:55:47.538 26812-26867/? E/BtGatt.GattService: [GSIM LOG]: gsimLogHandler, msg: MESSAGE_SCAN_STOP, appName: my.app, scannerId: 9, reportDelayMillis=1
2019-04-25 15:55:47.600 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.609 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.616 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.625 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.631 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.638 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.643 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently
2019-04-25 15:55:47.647 26812-26932/? E/BtGatt.GattService: App 'my.app' is scanning too frequently

If I restart my app (or just restart my scanning logic) this then very quickly leads to the error: BtGatt.GattService: App 'my.app' is scanning too frequently which is also mentioned in this issue: Issue 48 If I disable Telemetry Reporting using withTelemetryReportingDisabled(), only one scanner is started and I am free to restart the scanning a handful of times before I still eventually get the "is scanning to frequently" error.

EDIT: I saw this when using this setup: Estimote Proximity SDK version: 1.0.3 & 1.0.4 Android devices affected: Samsung Galaxy S8. Android OS version affected: 9.0.0 Beacon hardware Revision: J1.9_B1.1

Martinsbl avatar Apr 25 '19 14:04 Martinsbl