This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Android App not discovering Nordic's Bluetooth NUS Service (Bluetooth Peripheral UART)

Hi

I am positing this here - although maybe that is cheeky of me, as the issue I am having is with an Android app, which I want to use to communicate with a Nordic device.

I am trying to get an Android App working / communicating with an nRF52 DK board running Nordic’s Bluetooth Peripheral UART example.

The Android app I am running (built and run via Android Studio) is from Punch Through

(Blog: https://punchthrough.com/android-ble-guide/)

(GitHub: https://github.com/PunchThrough/ble-starter-android)

The app scans for devices, discovers the Nordic device, and allows the user to connect. The app then displays the discovered BLE characteristics.

This is where I would expect to see the two characteristics that are defined in the Nordic UART Service:

Service UUID: 6E400001-B5A3-F393-E0A9-E50E24DCCA9E (16-bit offset: 0x0001).
RX Characteristic: 6E400002-B5A3-F393-E0A9-E50E24DCCA9E
TX Characteristic: 6E400003-B5A3-F393-E0A9-E50E24DCCA9E


However, the app displays the following characteristics instead (I’ve only included the leading 16 bits here, and UUID descriptions I found online):

0x2a00 - GAP Characteristic Device Name UUID value
0x2a01 - GAP Characteristic Appearance UUID value
0x2a05 - GATT Characteristic Service Changed UUID value
0x2b29 - Client Supported Features UUID value
0x2b2a - Database Hash UUID value


Has anyone used this app to communicate with a Nordic device? I really want to get this app to discover the Nordic UART Services, so I can use it to send / receive data via the UART.

(I am new to Android development and finding my way through slowly. The nRF Toolbox Android App is far too complicated for me to tackle - even though I did manage to build it in Android Studio and install it from there on to my tablet. The Punch Through app seems more manageable as far as learning through modifying)

( By the way, to conform the Nordic board’s firmware, I successfully used the nRF Toolbox Android App, selected the UART utility service, the Nordic device discovered, and then a connection established. I can only assume that the device advertised the NUS service, and that the nRF Toolbox app discovered this service, because the app allows me to send ad receive data. )

  • My bad :(

    The app IS discovering the UART service / characteristics.

    The device I was running the app on has a small screen, and the other discovered characteristics were off screen.

    Can someone cancel this post please :)

    Garrett

Related