Add connecting time-out or auto reconnect after failing to connect #2271

Open
opened 1 year ago by Gar-onn · 3 comments
Gar-onn commented 1 year ago

Before requesting a new feature, please confirm the following:

  • I have read the wiki, and I didn't find a solution to my problem / an answer to my question.
  • I have searched the issues, and I didn't find a solution to my problem / an answer to my question.
  • If you upload an image or other content, please make sure you have read and understood the Codeberg Terms of Use

Your wearable device is:

Mi-band 5
HW: v0.44.18.2
FW: 1.0.2.58

Your android version is:

10
Moto G8

Your Gadgetbridge version is:

0.56.1

Issue:

After wandering too far from my phone, my MiBand loses its connections and won't connect for hours until I manualy disconnect en reconnect it. It get's stuck in the 'connecting' state.
This appears to happen with my girlfriend's phone as well.

#### Before requesting a new feature, please confirm the following: - [x] I have read the [wiki](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki), and I didn't find a solution to my problem / an answer to my question. - [x] I have searched the [issues](https://codeberg.org/Freeyourgadget/Gadgetbridge/issues), and I didn't find a solution to my problem / an answer to my question. - [x] If you upload an image or other content, please make sure you have read and understood the [Codeberg Terms of Use](https://codeberg.org/codeberg/org/src/branch/master/TermsOfUse.md) #### Your wearable device is: Mi-band 5 HW: v0.44.18.2 FW: 1.0.2.58 #### Your android version is: 10 Moto G8 #### Your Gadgetbridge version is: 0.56.1 ### Issue: After wandering too far from my phone, my MiBand loses its connections and won't connect for hours until I manualy disconnect en reconnect it. It get's stuck in the 'connecting' state. This appears to happen with my girlfriend's phone as well.

I see the exact same behaviour daily using Gadgetbridge 0.58.0 and Samsung A70 running Android 10.

In addition, this issue looks like it's closely related to #877, if not a duplicate.

I see the exact same behaviour daily using Gadgetbridge 0.58.0 and Samsung A70 running Android 10. In addition, this issue looks like it's closely related to #877, if not a duplicate.

I have been using Gadgetbridge for about two years, and have experienced this same issue (on nearly a daily basis) across all versions over that time period, with two different Amazfit watches. This would be a huge quality of life improvement if the app would timeout and attempt a reconnect if it is stucking in either "Connecting" or "Activity Fetching" states for more than 30 seconds. As others have noticed, this problem appears to be brought on primarily, by walking far enough away from the phone to cause a disconnect, though this does not seem to be the only cause, but it may be that I simply blocked the antenna or something causing a disconnect.

I have been using Gadgetbridge for about two years, and have experienced this same issue (on nearly a daily basis) across all versions over that time period, with two different Amazfit watches. This would be a huge quality of life improvement if the app would timeout and attempt a reconnect if it is stucking in either "Connecting" or "Activity Fetching" states for more than 30 seconds. As others have noticed, this problem appears to be brought on primarily, by walking far enough away from the phone to cause a disconnect, though this does not seem to be the only cause, but it may be that I simply blocked the antenna or something causing a disconnect.
vanous added the
one of the 1000 issues about disconnection
label 7 months ago

Same thing with my Amazfit Neo

Same thing with my Amazfit Neo
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.