Skip to content
This repository has been archived by the owner on May 18, 2022. It is now read-only.

iOS not seeing ~50% of nRF52 modules #56

Open
fmckeogh opened this issue Apr 28, 2019 · 6 comments
Open

iOS not seeing ~50% of nRF52 modules #56

fmckeogh opened this issue Apr 28, 2019 · 6 comments
Labels
area: beacons Code Area: BLE beacon advertisement, scanning, and advertising data structures area: hal Code Area: Radio hardware interfacing code hardware: nordic Things specific to Nordic nRF5x devices status: needs code An implementation or a bugfix need to be written type: bug Something isn't behaving as intended
Milestone

Comments

@fmckeogh
Copy link
Collaborator

On 2 out of 4 tested chips, when running the example code, the device is not visible to iOS (tested on iPhone 7 and XS). All chips work with Android devices. Currently believed to be due to inter-frame spacing issues during scan events.

@fmckeogh fmckeogh added type: bug Something isn't behaving as intended area: beacons Code Area: BLE beacon advertisement, scanning, and advertising data structures status: needs code An implementation or a bugfix need to be written hardware: nordic Things specific to Nordic nRF5x devices area: hal Code Area: Radio hardware interfacing code labels Apr 28, 2019
@jonas-schievink jonas-schievink added this to the 0.1.0 milestone Sep 28, 2019
@jonas-schievink jonas-schievink changed the title iOS not seeing ~50% of nRF52810 modules iOS not seeing ~50% of nRF52 modules Oct 25, 2020
@jonas-schievink
Copy link
Owner

Note that this issue only affects scan events, which are used when a device is sending connectable (or scannable) advertising PDUs. It does not affect beacons, which are non-connectable advertising PDUs.

@dthoma
Copy link

dthoma commented Oct 30, 2020

I've got the same issue on Android (Pixel 3a).
If I change the code to send a non-connectable PDU, Android does find the device, but it fails to for a connectable PDU. I can see the scan requests in the trace. From my laptop the device works just fine.

@valpackett
Copy link

valpackett commented Jul 23, 2021

Trying the characteristic demo here, Android does not discover it at all while my desktop (FreeBSD with Intel Bluetooth) does. An ESP32 also does see it. UPD: can confirm the "If I change the code to send a non-connectable PDU" thing

@nebelgrau77
Copy link

BLE n00b here. The demo works fine for me, but it's only visible to my kubuntu machine with an EDUP brand Bluetooth/WiFi dongle. Neither Rasperry Pi 4, nor two Android phones with nRF Connect can see it. I tried it with two different boards, Arduino Nano BLE Sense (u-blox chip) and Adafruit ItsyBitsy (Raytec chip).
So... how do I change it to send a non-connectable PDU, then?

BTW no luck with the beacon demo, no device can see it.

@valpackett
Copy link

how do I change it to send a non-connectable PDU, then?

Doing what beacon does.

no luck with the beacon demo, no device can see it

Very weird, that's with the interfaces that show everything (like nRF Connect), not just various OS built-in device scanners that only show connectable devices?

@nebelgrau77
Copy link

Doing what beacon does.

which would be what exactly? broadcast instead of advertise?

Very weird, that's with the interfaces that show everything (like nRF Connect), not just various OS built-in device scanners that only show connectable devices?

yes, nRF Connect on two different Samsung Axx phones, as well as bluetoothctl on the Linux machine, the one that can see the other demo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: beacons Code Area: BLE beacon advertisement, scanning, and advertising data structures area: hal Code Area: Radio hardware interfacing code hardware: nordic Things specific to Nordic nRF5x devices status: needs code An implementation or a bugfix need to be written type: bug Something isn't behaving as intended
Projects
None yet
Development

No branches or pull requests

5 participants