mirror of
https://codeberg.org/Freeyourgadget/Gadgetbridge
synced 2024-06-24 05:50:47 +02:00
ab306b1352
Pairing some devices requires a PIN to be entered. E.g. the flow is: confirm you'd like to pair, pass off to Android which prompts for a PIN to pair with (typically shows up on the non-phone device's screen or is hard coded in the manual), then return back to the app. When this pairing request screen pops up, it takes focus. This invokes onPause and onStop in the DiscoveryActivity, which removes the BlueTooth broadcast receivers. Returning focus (after successful pairing), there's nothing to listen to the event. Practically speaking, GadgetBridge last saw the device as BOND_BONDING, so it's out of sync. If queried, the device is BOND_BONDED, so it's good to move on to the next step. Many existing pairing activities (Lenovo, MiBand, Pebble, Watch9) have an implementation of onResume() to presumably tackle this issue, this adds it to `DiscoveryActivity` as well. Testing with some other supporting code, this allows a Garmin vivosport to appear in Gadgetbridge. |
||
|---|---|---|
| .. | ||
| activities | ||
| adapter | ||
| contentprovider | ||
| database | ||
| deviceevents | ||
| devices | ||
| entities | ||
| export | ||
| externalevents | ||
| impl | ||
| model | ||
| service | ||
| util | ||
| GBApplication.java | ||
| GBEnvironment.java | ||
| GBException.java | ||
| LockHandler.java | ||
| Logging.java | ||
| LoggingExceptionHandler.java | ||
| SleepAlarmWidget.java | ||
| Widget.java | ||