Skip to content
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

Support bluetooth renaming #54

Closed
FederAndInk opened this issue Jun 11, 2021 · 6 comments · Fixed by #90
Closed

Support bluetooth renaming #54

FederAndInk opened this issue Jun 11, 2021 · 6 comments · Fixed by #90
Labels
enhancement New feature or request

Comments

@FederAndInk
Copy link

When I renamed my Pinetime to distinguish it from others that I have, I wasn't able to pair it.
Could it be possible to choose from the Bluetooth discovery list? Or keep/specify an address?

@theironrobin
Copy link
Owner

you changed the source code of infinitime to make your device advertise under a different name?

@FederAndInk
Copy link
Author

Actually, I just renamed it in the Bluetooth parameters (on KDE Plasma, but I think we can do that on Gnome).

@theironrobin
Copy link
Owner

post steps to reproduce and i will take a look.

@FederAndInk
Copy link
Author

  1. Pair the Pinetime
    2021-06-11_16-48
  2. Go to the paired device settings
    2021-06-11_16-50
  3. Rename it
    2021-06-11_16-51
    2021-06-11_16-52
  4. Disconnect it
    2021-06-11_16-53
  5. Siglo can't find the pinetime (I've disconnected it)
    2021-06-11_16-54

Siglo finds it again if I reconnect it, rename it to InfiniTime precisely, disconnect it, then lunch Siglo

@FederAndInk
Copy link
Author

2021-06-11_17-05
well, the main point is to make use of the name, because it's not useful at this moment if I understand correctly, because it will always show "InfiniTime"

@FederAndInk
Copy link
Author

cool, thanks 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants