Open KedynsCrow opened 5 months ago
For me, this happens using simple pairing but works as expected using secure bonding with a pin.
For me, this happens using simple pairing but works as expected using secure bonding with a pin.
Same for me. My connection was stable once I paired.
Hi all,
looks like a bit related: https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/3741 . This issue describes the same with Android 14 Pixel (Stock) phone. Also, I do have issues with Nothing Phone 2 (Android 14, Stock).
Gadget bridge 0.80.0
@KedynsCrow, @qw3r3wq, @pbone64 Can you please try this procedure (please do it precisely) and let me know whether it resolves the issue?
Before beginning this procedure, please ensure a properly working version of InfiniTime has been installed on the watch and validated.
@DavisNT I have performed your method and it seems stable so far, though when I had connection issues they would take a couple of days to start happening each time that I connected to my watch.
To be clear, though, my connection has been stable ever since pairing to my pinetime (instead of connecting without pairing), regardless of what steps I perform after pairing. Are your steps meant to provide a stable connection? In my experience it has been enough to just pair.
Experiencing this as well. Just to note with this, there's a loss of data like steps. I only notice every few days myself. A hard reset of the watch reconnects, but by then all data is lost.
I wonder if there should be some connection status on the watch itself that can inform the user outside of pulling open the app.
Experiencing this as well. Just to note with this, there's a loss of data like steps. I only notice every few days myself. A hard reset of the watch reconnects, but by then all data is lost.
I wonder if there should be some connection status on the watch itself that can inform the user outside of pulling open the app.
There is, at least on the terminal watchface. I believe the analog and digital faces have a Bluetooth symbol when connected, but I'm not certain as I haven't used them a while.
Regardless, at least in my experience, when this bug occurs the watch believes itself to be connected while the companion app (gadgetbridge in my case) believes it to be disconnected.
Verification
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