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

Possible BLE Conflict with Garmin Connect Android v4.29 #55

Open
jakobtobias opened this issue Apr 24, 2020 · 0 comments
Open

Possible BLE Conflict with Garmin Connect Android v4.29 #55

jakobtobias opened this issue Apr 24, 2020 · 0 comments
Labels
prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation.

Comments

@jakobtobias
Copy link

After a new BLE Device is added to Garmin Connect, DP-3T will not allow to enable Tracing anymore.

Steps to reproduce:

  1. Install Garmin Connect
  2. Install DP^3T / Next Step for Android
  3. Enable Tracing in DP^3T
  4. Add a BLE Device to Garmin Connect (in my Case Vivomove Style) - Hint: Contact Tracking may have to be disabled for this
  5. Result: unable to (re)enable Tracing

Work Around:
Reinstall DP^3T

@simonroesch simonroesch added the prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation. label May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prestandard This issue is referring to the "prestandard" solution and not the current GAEN implementation.
Projects
None yet
Development

No branches or pull requests

2 participants