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

Document best practices on Android #973

Open
peitschie opened this issue May 30, 2023 · 0 comments
Open

Document best practices on Android #973

peitschie opened this issue May 30, 2023 · 0 comments

Comments

@peitschie
Copy link
Collaborator

peitschie commented May 30, 2023

Spawned from discussion on #963

The best approaches found on Android are:

  1. Use autoConnect and don't explicitly scan (i.e., let the OS schedule this itself)
  2. Explicitly scan and then use connect
  3. (Maybe) for a non-bonded device, it's safe to just use connect without an explicit scan (to be confirmed)

Additional things worth documenting:

  1. Permission flows and differences per Android version
  2. Location services & impacts on scanning
  3. Background processing
  4. Impacts of scan latency settings (Android: Scan only detects the device after the third consecutive attempt or more #959)
  5. Use of neverForLocation on Android 12+
  6. Android disconnect supervision timeouts, and why rapid reconnects can often fail

Documenting the known caveats and quirks would help implementors more effectively use this plugin.

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

No branches or pull requests

1 participant