-
-
Notifications
You must be signed in to change notification settings - Fork 952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firmware update with pinetime-mcuboot-app-dfu-1.14.0.zip and GadgetBridge fails #2084
Comments
@luto65 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.
|
I've seen this problem reported multiple times and there is a similar issue on the Gadgetbridge repo too. I am also affected by the same issue unfortunately, without being able to solve it. It started when I upgraded to 1.14.0. I believe it's been broken for a long time now. This is the similar issue I was talking about. Looks like the bug is known at least for 4 months and being reported yet it's not clear why is that happening. I think it should be fixed before 1.15.0.. |
This kind of issue is not easy to diagnose as there are a lot of moving parts. The issue could be caused by the PineTime, InfiniTime, the companion app, the BLE stack on the host device, the hardware of the host device,... This is not a formal proof, but the fact that InfiniLink works makes me think that the issue does not necessarily come from InfiniTime. Gadgetbridge also works fine on my Samsung S21 smartphone. |
Here is more hardware variation, and strange but reproducible results, in case it gives you any new clues. I just updated to 1.14.0 from 1.7.0, which created similar problems. My phone is a Google Pixel 6a running latest GrapheneOS. Gadgetbridge is 0.81. After inability to connect, I rebooted the watch, rebooted the phone, deleted device from GB, and unpaired from phone. I also did the disable, 3 presses, reenable thing. Pairing New Device sees the watch. However, it fails to bond. It first just darkens the screen, which eventually returns "Bonding with %1$s failed immediately". I then tried with a OnePlus 8 running LineageOS 21 and GB 0.81.0, but got the same results. I tried a Galaxy Pixel Tablet running GrapheneOS, same as above. It failed Then tried with a Samsung Galaxy Tab running Android 9, which paired. I deleted the device from GB. Now, when I tried again, I could pair with the Pixel Tablet, but not the Pixel 6a. Repeated attempts showed the same results: after pairing once with the Samsung Tablet and then deleting it, I could pair it with the Pixel Tablet. Finally, I discovered that I could pair it with the Pixel 6a, but only if it is not made a companion device. |
I installed 1.14.0 on Jan 4 2024. Since then I was not able to connect anymore, despite upgrading Gadgetbridge. EDIT: |
Verification
What happened?
GadgetBridge reports "connection problems"
What should happen instead?
GadgetBridge should connect
Reproduction steps
Installed GadgetBridge 0.80.0 on a HUAWEI
PineTime hardware
downloaded on the HUAWEI the pinetime-mcuboot-app-dfu-1.14.0.zip
More details?
I received the PineTime and with my iphone and InfiniLink i connected to it and updated with the latest version 1.14.0
Then I wanted to try out how the updating of the pinetime through DFU would work and therefore i installed GadgetBridge on the HUAWEI
I tried to connect several times , and while the PineTime shows up in the BLE devices, often the connection last few seconds and then disconnect.
A only time I was able to connect, then started the upload of the firmware but then the connection broke again.
Version
v.1.14.0
Companion app
GadgetBridge v 0.80
The text was updated successfully, but these errors were encountered: