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.

Sign up for GitHub

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

Jump to bottom

Switch from 128-bit to 16-bit service UUID #18

Open
c19x opened this issue Nov 12, 2020 · 1 comment
Open

Switch from 128-bit to 16-bit service UUID #18

c19x opened this issue Nov 12, 2020 · 1 comment
Labels
enhancement New feature or request question Further information is requested
Milestone
Unscheduled

Comments

@c19x
Copy link
Contributor

c19x commented Nov 12, 2020

Use of custom 128-bit service UUID prevents transmission of TxPower and PseudoDeviceAddress in advertising packet. Switch to standard 16-bit UUID (0x1201 General Networking) will enable inclusion of TxPower and PseudoDeviceAddress.
@adamfowleruk
Copy link
Collaborator

16 bit service UUIDs require approval by the Bluetooth SIG, I believe. I'd strongly advise reviewing the potential options to ensure we don't inadvertently interfere with any existing Bluetooth kit out there.

@c19x c19x mentioned this issue Nov 12, 2020
Closed
@adamfowleruk adamfowleruk added question Further information is requested enhancement New feature or request labels Nov 12, 2020
@adamfowleruk adamfowleruk modified the milestones: v2.1, Unscheduled Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
Unscheduled
Development

Successfully merging a pull request may close this issue.

Switch from 128-bit to 16-bit service UUID - Validated c19x/herald-for-android
2 participants
@adamfowleruk @c19x