Amazfit Band 5 isn't pairing with Pixel 8 Pro GrapheneOS #3439

Closed
opened 2023-11-29 07:25:13 +00:00 by cyclo89 · 4 comments

If you just have a question, please ask first in the user chatroom in Matrix: #gadgetbridge:matrix.org

Before reporting a bug, please confirm the following:

  • [ x] I have read the wiki, and I didn't find a solution to my problem / an answer to my question.
  • [ x] 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

Where did you get Gadgetbridge from:

  • [x ] F-Droid
  • Gadgetbridge Nightly F-Droid repository
  • Bangle.js Gadgetbridge from the Play Store
  • I built it myself from source code (specify tag / commit)
  • I previously used Gadgetbridge from other sources and then updated to F-Droid version

Your Gadgetbridge version is:

0.76.1

(This can be found in Gadgetbridge - Menu - About: Version and Commit)

Your issue is:

I cannot get my new amazfit band 5 tracker to pair in gadgetbridge on my Pixel 8 Pro running GrapheneOS. I can get it to pair on my S10+ stock android OS. I don't think it is the auth key, I've tried different methods (first method for non-root does not work because the script gets stuck in different stages so I gave up on it, second method apk only works on my s10+ because it says my pixel 8 pro is not a supported device, third method freemyband works on my pixel 8 pro but only once, I also tried a gadgetgeek all in one zep mod that worked reliably on my pixel 8 pro, last method get the auth key from s10+ and use it on pixel 8 pro disconnecting from gadgetbridge but not unpairing on zepp).

I've tried rebooting the pixel and tracker several times, turning bluetooth on and off several times, factory resetting tracker 4 times making new auth keys after each time, I put 0x before the key and checked it, I remove it from my bluetooth android pairing so it is not that. It always says "bonding with %1$s failed immediately" on my pixel 8 pro.

Click to see my log under this fold
16:59:23.179 [main] WARN n.f.g.a.DiscoveryActivity - Amazfit Band 5: 62 16:59:23.180 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Amazfit Band 5, xx:xx:xx:xx:xx:xx 16:59:23.180 [main] DEBUG n.f.g.a.DiscoveryActivity - supports uuid: 0000fee0-0000-1000-8000-00805f9b34fb 16:59:23.212 [main] INFO n.f.g.i.GBDeviceCandidate - Could not get device alias for Amazfit Band 5 16:59:23.214 [main] INFO n.f.g.a.DiscoveryActivity - Recognized device: Amazfit Band 5: xx:xx:xx:xx:xx:xx (AMAZFITBAND5) 16:59:23.215 [main] WARN n.f.g.a.DiscoveryActivity - null: 62

Your wearable device is:

Please specify model and firmware version if possible

Amazfit Band 5
FW: 1.0.1.70

Your Android version/manufacturer flavor is:

Android 14 GrapheneOS
Google

New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.

If you just have a question, please ask first in the user chatroom in Matrix: [`#gadgetbridge:matrix.org`](https://matrix.to/#/#gadgetbridge:matrix.org) #### 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/main/TermsOfUse.md) ### Where did you get Gadgetbridge from: * [x ] F-Droid * [ ] Gadgetbridge Nightly F-Droid repository * [ ] Bangle.js Gadgetbridge from the Play Store * [ ] I built it myself from source code (specify tag / commit) * [ ] I previously used Gadgetbridge from other sources and then updated to F-Droid version ### Your Gadgetbridge version is: 0.76.1 (This can be found in Gadgetbridge - Menu - About: Version and Commit) #### Your issue is: I cannot get my new amazfit band 5 tracker to pair in gadgetbridge on my Pixel 8 Pro running GrapheneOS. I can get it to pair on my S10+ stock android OS. I don't think it is the auth key, I've tried different methods (first method for non-root does not work because the script gets stuck in different stages so I gave up on it, second method apk only works on my s10+ because it says my pixel 8 pro is not a supported device, third method freemyband works on my pixel 8 pro but only once, I also tried a gadgetgeek all in one zep mod that worked reliably on my pixel 8 pro, last method get the auth key from s10+ and use it on pixel 8 pro disconnecting from gadgetbridge but not unpairing on zepp). I've tried rebooting the pixel and tracker several times, turning bluetooth on and off several times, factory resetting tracker 4 times making new auth keys after each time, I put 0x before the key and checked it, I remove it from my bluetooth android pairing so it is not that. It always says "bonding with %1$s failed immediately" on my pixel 8 pro. <details> <summary>Click to see my log under this fold</summary> ``` 16:59:23.179 [main] WARN n.f.g.a.DiscoveryActivity - Amazfit Band 5: 62 16:59:23.180 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Amazfit Band 5, xx:xx:xx:xx:xx:xx 16:59:23.180 [main] DEBUG n.f.g.a.DiscoveryActivity - supports uuid: 0000fee0-0000-1000-8000-00805f9b34fb 16:59:23.212 [main] INFO n.f.g.i.GBDeviceCandidate - Could not get device alias for Amazfit Band 5 16:59:23.214 [main] INFO n.f.g.a.DiscoveryActivity - Recognized device: Amazfit Band 5: xx:xx:xx:xx:xx:xx (AMAZFITBAND5) 16:59:23.215 [main] WARN n.f.g.a.DiscoveryActivity - null: 62 ``` </details> #### Your wearable device is: *Please specify model and firmware version if possible* Amazfit Band 5 FW: 1.0.1.70 #### Your Android version/manufacturer flavor is: Android 14 GrapheneOS Google *New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.*
Member

Hmmm these logs do not say a lot.

I would try this:

  1. Go to the debug menu, add a test device, select Amazfit Band 5 and type the mac address
  2. Go to the device settings, scroll to the end, set the auth key
  3. Attempt to pair manually on android settings
Hmmm these logs do not say a lot. I would try this: 1. Go to the debug menu, add a test device, select Amazfit Band 5 and type the mac address 2. Go to the device settings, scroll to the end, set the auth key 3. Attempt to pair manually on android settings
Author

Wow thanks that worked! Yeah the logs were very long but they kept repeating the different bluetooth MAC addresses in my house, those lines were the only lines that were different. It looks to be working on my end now, thanks so much!

Also side note, for the huami_token script I couln't get to run, you had to delete line 35 from . import errors, urls and then your password cannot have the ampersand symbol & in it. Once I did that, it ran and gave me the same auth key I got before. I'm going to guess your email can't have it too. Also, the place I got the zepp mod from is named geekdoing not geekgadget.

Wow thanks that worked! Yeah the logs were very long but they kept repeating the different bluetooth MAC addresses in my house, those lines were the only lines that were different. It looks to be working on my end now, thanks so much! Also side note, for the huami_token script I couln't get to run, you had to delete line 35 `from . import errors, urls ` and then your password cannot have the ampersand symbol `&` in it. Once I did that, it ran and gave me the same auth key I got before. I'm going to guess your email can't have it too. Also, the place I got the zepp mod from is named geekdoing not geekgadget.

FWIW, I had the same issue with GTS 4 Mini and a phone running LineageOS. The workaround with debug menu and test device worked.

FWIW, I had the same issue with GTS 4 Mini and a phone running LineageOS. The workaround with debug menu and test device worked.
Member

This is being reported across multiple devices - closing this in favor of #3578 to improve visibility.

This is being reported across multiple devices - closing this in favor of #3578 to improve visibility.
joserebelo added the
duplicate
label 2024-02-15 21:28:48 +00:00
joserebelo added the
pairing/connecting
label 2024-02-15 21:42:56 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Freeyourgadget/Gadgetbridge#3439
No description provided.