InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Not reconnecting to Gadgetbridge
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar bug reports (including closed issues) and found none was relevant.
What happened?
When the watch disconnects from Gadgetbridge, then reconnects it no longer reports batter level or sends notifications to the watch.
What should happen instead?
After disconnecting I expect the watch to automatically reconnect and keep working as it did before.
Reproduction steps
I connect the watch to the Gadgetbridge app on the phone. It shows the watch's battery level, the watch receives notifications from the phone and everything works as I expect. Then I put the phone down and walk away. It disconnects as I would expect. When the phone comes back into proximity of the watch the Gadgetbridge app says it has connected again, but no longer shows the battery level of the phone, the step count is out of sync, and the watch no longer receives notifications. This state continues until I go to the Gadgetbridge app, disconnect the watch, and then reconnect it.
More details?
I have a Samsung phone running Android 13. The watch had this issue with Infinitime 1.11 and it continued when I updated to 1.14. The Gadgetbridge app has all permissions allowed from the phone. Gadgetbridge is set to "Connect to Gadgetbridge device(s) when Bluetooth is turned on" and in the device specific settings it is set to "Auto reconnect to device."
Version
1.14
Companion app
Gadgetbridge 0.79.1a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the disconnect and automatic reconnect sequence described for InfiniTime 1.14 with Gadgetbridge 0.79.1a on Android 13, then trace the firmware's reconnect behavior and the battery, step-count, and notification updates. Done means those functions resume after the watch reconnects without manually disconnecting and reconnecting it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100