Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beacon ranging consistently times out for older Android phone #107

Open
victorcassone2 opened this issue Apr 7, 2021 · 1 comment
Open

Comments

@victorcassone2
Copy link

Summary

I was testing out the new beacon functionality on a Google Pixel XL and I was unable to range any beacons that were nearby. It looks like the ranging timeout is set to 5 seconds and on the Pixel XL it consistently goes over 5 seconds. I used a stopwatch and another BLE ranging app(kontakt.io's app) and it took about 7.5 seconds.

I then tested on a Pixel 4 XL and the ranging consistently came back as successful.

Either setting a higher ranging time or having the ability to increase the time myself via the SDK would help alleviate the problem.

Steps to reproduce

  1. Create a Button that calls trackOnce with beacons = true
  2. Trigger button and observe no beacons are returned on the RadarUser.

OS version

Android 10

SDK installation method

via Gradle.

SDK version

3.1.1

@nickpatrick
Copy link
Contributor

@victorcassone2 Thanks, that's great feedback. Yes, we'll look into making these timeouts customizable in a future release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants