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

Long device names cause trouble #1

Closed
amakuzaze opened this issue Jan 31, 2022 · 2 comments
Closed

Long device names cause trouble #1

amakuzaze opened this issue Jan 31, 2022 · 2 comments

Comments

@amakuzaze
Copy link
Contributor

The bluedroid stack accepted most device names I threw at it just fine, but nimble seems to have tighter restrictions. I'll investigate and update this issue as I go.

@amakuzaze amakuzaze changed the title Long device names that were no problem with bluedroid cause trouble Long device names cause trouble Jan 31, 2022
@amakuzaze
Copy link
Contributor Author

My findings so far: Name is limited to 19 octets. The menuconfig entry appears to make this configurable (and also the 31 octets there aren't correct, since some of that payload length is used for flags and other management fields) but raising the limit currently does nothing.

Also see: apache/mynewt-nimble#835

@amakuzaze
Copy link
Contributor Author

For reference: The menuconfig entry only affects the GAP attribute and has no influence over how the advertising / scan response packets are woven.

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

No branches or pull requests

1 participant