Amazfit Band 5 isn't pairing with Pixel 8 Pro GrapheneOS #3439
Labels
No labels
device mi band 7
activity post processing
activity/health
Android 12
Android 13
android integrations
architecture
Bangle.js
bug
changes requested
charts
deprecation notice
details not provided
developer documentation
device amazfit band 5
device amazfit bip
device amazfit cor
device Casio
device fossil
device garmin
device gtr 2e
device gts 2 mini
device h30
device hplus
device huami
device Huawei
device liveview
device mi band
device mi band 2
device mi band 3
device mi band 4
device mi band 5
device mi band 6
device no.1 f1
device pace
device pebble
device pebble 2
device pinetime infinitime
device request
device sony
device support
device watch 9
device xiaomi
discussion
documentation
duplicate
enhancement
feature request
Gadgetbridge
good first issue
help wanted
i am developing my own app can you help
icebox
intent api
internationalisation
invalid
needs work
network companion app
new device
no feedback
not a bug
notifications
one of the 1000 issues about disconnection
pairing/connecting
potentially fixed / confirm and close
question
research
security
seems abandoned
Solved, waiting for F-Droid release
suggest to close
task
user interface / UX
wear os
weather
wontfix
Zepp OS
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Freeyourgadget/Gadgetbridge#3439
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Where did you get Gadgetbridge from:
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
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.
Hmmm these logs do not say a lot.
I would try this:
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.
This is being reported across multiple devices - closing this in favor of #3578 to improve visibility.