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

BT_LE_ADV_NCONN_NAME doesn't actually advertise name #25016

Closed
jeremyherbert opened this issue May 6, 2020 · 1 comment
Closed

BT_LE_ADV_NCONN_NAME doesn't actually advertise name #25016

jeremyherbert opened this issue May 6, 2020 · 1 comment
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug

Comments

@jeremyherbert
Copy link
Contributor

Describe the bug
If I use BT_LE_ADV_CONN_NAME as the first parameter to bt_le_adv_start, then the device name (as set in the prj.conf file) shows up correctly when scanning for devices using an iOS or Android app. However, when I use BT_LE_ADV_NCONN_NAME the name does not show up, even though BT_LE_ADV_OPT_USE_NAME is used in its definition in bluetooth.h.

To Reproduce
Steps to reproduce the behavior:

  1. Build and flash the following code with BOARD=nrf52840_pca10056: https://gist.github.com/jeremyherbert/62cbed007f2f0c1b5b1a550fd14726ec
  2. Open a BLE scanning app
  3. Observe that there is no advertised name
  4. Change BT_LE_ADV_NCONN_NAME in main.c to BT_LE_ADV_CONN_NAME, build and flash
  5. Observe that the name is now advertised

Expected behavior
The name should be advertised in both cases

Impact
It makes finding the device very difficult in an area with lots of BLE devices.

Environment (please complete the following information):

  • OS: Ubuntu 18.04
  • Commit: ff214d6
  • Board: nrf52840_pca10056
@jeremyherbert jeremyherbert added the bug The issue is a bug, or the PR is fixing a bug label May 6, 2020
@joerchan
Copy link
Contributor

joerchan commented May 6, 2020

This has already been fixed by: ffa10eb

@joerchan joerchan closed this as completed May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

No branches or pull requests

3 participants