#2090 Infinite sync loop after reconnecting to device with auto fetch enabled (Amazfit Bip)

Open
opened 2 weeks ago by Synyster · 4 comments
Synyster commented 2 weeks ago

Before reporting a bug, please confirm the following:

I got Gadgetbridge from:

If you got it from Google Play, please note that version is unofficial and not supported here; it's also often quite outdated. Please switch to one of the above versions if you can.

Your issue is:

I have auto fetch enabled. When I open the app while the device reconnects to the Smartphone the app tries to fetch the data from the device and gets stuck in an infinite loop. The loop won't let me fetch the data manually, until I disconnect and reconnect the device again.

Your wearable device is:

Amazfit Bip V0.11.19.5, Firmware version 18344,eb2f43f,126 (from the internal database)

Your android version is:

Android 10

Your Gadgetbridge version is:

0.48.0

#### Before reporting a bug, 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. - [ ] 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) ### I got Gadgetbridge from: * [x] F-Droid * [ ] I built it myself from source code (specify tag / commit) If you got it from Google Play, please note [that version](https://github.com/TaaviE/Gadgetbridge) is unofficial and not supported here; it's also often quite outdated. Please switch to one of the above versions if you can. #### Your issue is: I have auto fetch enabled. When I open the app while the device reconnects to the Smartphone the app tries to fetch the data from the device and gets stuck in an infinite loop. The loop won't let me fetch the data manually, until I disconnect and reconnect the device again. #### Your wearable device is: Amazfit Bip V0.11.19.5, Firmware version 18344,eb2f43f,126 (from the internal database) #### Your android version is: Android 10 #### Your Gadgetbridge version is: 0.48.0
Synyster commented 2 weeks ago
Poster

I don't know how to check the checkboxe. I have read the wiki and searched for issues. I got Gadgetbridge from F-Droid

I don't know how to check the checkboxe. I have read the wiki and searched for issues. I got Gadgetbridge from F-Droid
izzy commented 2 weeks ago
Poster

I don’t know how to check the checkboxe.

I've done that for you; enter edit mode to see how it's done: [x]

And before you ask: No, I don't know – but someone of the crew will certainly jump in shortly to help you out with the issue itself.

> I don’t know how to check the checkboxe. I've done that for you; enter edit mode to see how it's done: `[x]` And before you ask: No, I don't know – but someone of the crew will certainly jump in shortly to help you out with the issue itself.
vanous commented 2 weeks ago
Poster
Collaborator

@Synyster is there a step by step way to replicate this issue? I have the Bip as well and this happens very rarely and it's hard to know if this is due to bluetooth stack rot, which requires the phone to be restarted every 2-3 weeks, or if this is another issue. I also am not in the position to be able to fix this, but at least replicating is something i can try. Thank you.

@Synyster is there a step by step way to replicate this issue? I have the Bip as well and this happens very rarely and it's hard to know if this is due to bluetooth stack rot, which requires the phone to be restarted every 2-3 weeks, or if this is another issue. I also am not in the position to be able to fix this, but at least replicating is something i can try. Thank you.
Synyster commented 2 weeks ago
Poster

Yes I could recreate it:
-Have auto fetch enabled
-Go out of reach of the smartphone that is connected with the Bip
-Come back in reach, unlock the smartphone and open the app by clicking on the notification

After this steps the Bip should connect with the smartphone, start the fetching and gets stuck there (the indication for the synchronisation should go on until the Bip is dis- and reconnected)

Yes I could recreate it: -Have auto fetch enabled -Go out of reach of the smartphone that is connected with the Bip -Come back in reach, unlock the smartphone and open the app by clicking on the notification After this steps the Bip should connect with the smartphone, start the fetching and gets stuck there (the indication for the synchronisation should go on until the Bip is dis- and reconnected)
vanous added the
pairing/connecting
label 2 weeks ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.