Question about BLE discoverability using Nordic NRF Connect Mobile

[oeigj56q]

I am trying to use the NRF connect mobile app on android 8.1.0 to try and connect to a Bluetooth server serving GATT request to verify functionality.

The server is running Linux using the Bluez stack version 5.5.0, I have enabled discoverability using hcitool as shown below:

$ hciconfig
hci0:    Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:FD:EE:3C  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:1550 acl:0 sco:0 events:118 errors:0
    TX bytes:7530 acl:0 sco:0 commands:118 errors:0

For some reason, the NRF connect app does not appear to able to see the device while scanning. The weird thing however, is that if I scan from the bluetooth settings (Settings -> Bluetooth), the device shows up and I can pair with the device. If I force a connect manually inside the NRF connect app, it says GATT Error (0x85).

Is there some setting to Bluez that I can adjust to support the NRF connect app?

[Turbo J]

Bluetooth classic != Blueooth LE.

Your hci setup is used for bluetooth classic connections, while nrf connect only scans for bluetooth low energy advertisements.

Setting up BT LE advertising in bluez requires additional commands in order to set the advertized data correctly.