-
Notifications
You must be signed in to change notification settings - Fork 67
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
Bluetooth issues #163
Comments
I have found also ttblue. Using it i was able to connect to my phone from a linux system. So my assumption above is not correct - i guess. |
Yes, you should be able to tell the watch to forget previously-paired codes by deleting or overwriting file I alluded to this in the reverse-engineered Bluetooth protocol docs: Unfortunately, I no longer have a working TomTom GPS watch to test with myself, but I remember doing this a couple times with v1 devices (I think you have a v2 device) and it worked fine to reset or overwrite the pairing codes. |
From https://github.com/dlenski/ttblue/blob/master/tt_bluetooth.md Issue ryanbinns#163 reminded me of this
Need to apologise before anything else, i think this is probably not the best place to ask for help.
As many others, i have issues pairing tomtom adventurer to the app on android. During pairing the watch would display the pin but the phone won't ask for it, keeps searching all the time.
Having read a bit on the tomtom forums, at the moment i believe that the watch somehow remembers the last pairing, with a different phone, and hence somehow it won't work correctly with a new phone - i base this assumption on the fact that somebody with that issue, 'forgot' the watch from the previous phone and then was able to pair again in the new one.
I do not have access to my old phone to try this solution.
Could it be that ttwatch could somehow inform the watch to be forgoten on the previous phone?
Again, just an assumption.
If anyone cares, thanks in advance
The text was updated successfully, but these errors were encountered: