This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52, HID mouse example and Android 7.0 - Service discovery issues

Hi! I'm working on HID mouse example on SDK 13.0.0. I'm supposed to use this as a low power media button control.
I've done a few modicifations on the code for power optimizations, such as setting TX power, and set the preferred connection paramaters slightly according to Android spec.
This setup has been operational for a good time now, but I seem to have issues connecting the nRF52 as peripheral to my Huawei P9 Plus, running Android 7.0.
The issue seems to be service discovery when the phone connects to the nRF52 initially. From the nRF log of the phone it seems like the service discovery suddenly stops, even a service refresh stops. I've cross-checked with a Samsung Galaxy S5 running Android 6.0.1, an iPhone with unknown iOS version, and a Windows 10 computer. All of them seem to connect to and function with the nRF52 without any issues. This is a non-constant problem, because I am sometimes able to succesfully connect to the device, and use it as a remote for the Huawei. When they are able to bond and succesfully do a service discovery I can have them operating for hours, even reconnecting after the Huawei has been out of reach is successfull.
Could this be a problem related to service discovery on Android 7.0? Any help would be appreciated.

The project file is located here:

https://github.com/petter15/ble_app_hids_mouse

nRF log from service discovery attempt on Huawei P9 Plus. Service discovery apparentally failed.

nRF Connect, 2018-03-21
nRF_media_ctrl (C4:CA:86:06:6B:7A)
V	18:41:50.758	Connecting to C4:CA:86:06:6B:7A...
D	18:41:50.759	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE)
D	18:41:50.780	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I	18:41:50.780	Connected to C4:CA:86:06:6B:7A
D	18:41:50.781	wait(1600ms)
V	18:41:52.400	Discovering services...
D	18:41:52.400	gatt.discoverServices()
D	18:41:52.421	[Callback] Services discovered with status: 0
I	18:41:52.425	Services discovered
V	18:41:52.460	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
- Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- PnP ID [R] (0x2A50)
Battery Service (0x180F)
V	18:43:40.394	Refreshing device cache...
D	18:43:40.395	gatt.refresh() (hidden)
I	18:43:40.398	Cache refreshed
V	18:43:40.400	Discovering services...
D	18:43:40.400	gatt.discoverServices()
D	18:43:40.406	[Callback] Services discovered with status: 0
I	18:43:40.409	Services discovered
V	18:43:40.447	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
- Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- PnP ID [R] (0x2A50)
Battery Service (0x180F)
V	18:43:57.987	Refreshing device cache...
D	18:43:57.987	gatt.refresh() (hidden)
I	18:43:57.989	Cache refreshed
V	18:43:57.989	Discovering services...
D	18:43:57.989	gatt.discoverServices()
D	18:43:57.999	[Callback] Services discovered with status: 0
I	18:43:58.001	Services discovered
V	18:43:58.038	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
- Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- PnP ID [R] (0x2A50)
Battery Service (0x180F)
V	18:44:19.629	Refreshing device cache...
D	18:44:19.629	gatt.refresh() (hidden)
I	18:44:19.630	Cache refreshed
V	18:44:19.630	Discovering services...
D	18:44:19.630	gatt.discoverServices()
D	18:44:19.633	[Callback] Services discovered with status: 0
I	18:44:19.635	Services discovered
V	18:44:19.665	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
- Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- PnP ID [R] (0x2A50)
Battery Service (0x180F)
V	18:44:23.305	Refreshing device cache...
D	18:44:23.305	gatt.refresh() (hidden)
I	18:44:23.309	Cache refreshed
V	18:44:23.309	Discovering services...
D	18:44:23.309	gatt.discoverServices()
D	18:44:23.319	[Callback] Services discovered with status: 0
I	18:44:23.321	Services discovered
V	18:44:23.356	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
- Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- PnP ID [R] (0x2A50)
Battery Service (0x180F)

Wireshark sniff file from connection between nRF52 and Huawei P9 plus. Connection succeeded and device operational. 

nrf_media_ctrl_21.03.18_nRF52_P9Plus_fullfuctional_reference.pcapng

Wireshark sniff file from connection between nRF52 and Huawei P9 Plus. Three attemps of connecting were made. The two first failed, while the last connection attempt succeeded and was able to make the device operational.

nrf_media_ctrl_21.03.18_nRF52_P9Plus_start-failure_then_functional.pcapng

  • A quick look into the logs didn't show anything in specific. 

    Are you using S132v4.0.5? You can download and program it from (no changes required to the application firmware):
    http://www.nordicsemi.com/eng/nordic/Products/nRF52832/S132-SD-v4/58803 

    You may also take a look at the known issues with nRF5 SDK v13.x.0:
    https://devzone.nordicsemi.com/f/nordic-q-a/27082/what-are-sdk-13-x-0-known-issues 

    Does the same happen with any of the nRF5 SDK examples "as-is" using S132v4.0.5?

     

  • Hi. 
    I've been using S132 v 4.0.2 during the development period. I've tried S132 v4.0.5 for some time now, and the issue seems to occure there as well. 
    From what I've read of the "known issues" tab I didn't find any directly relevant to my issue.

    I've tried some examples "as is" from the SDK v 13, running S132 4.0.5, and the issue seems to occure there as well. From what I saw of the nRF log running "as is" examples, the service discovery suddenly stops. 

  • I suggest to still continue to use S132v4.0.5 in any case, due to improvements overall.

    Seems like some sort of bug on the Android side here, but we can still try to investigate a bit further, are you able to print out all events occuring on the UART, just to see if there is any event that is out of sequence/missing when it fails compared to when it works?

    So basically you need to print out 'p_ble_evt->header.evt_id' here, feel free to add other debug information also, but make sure to highlight these in the output.

  • I'll stick with S132 4.0.5 =)

    I've tried to enable UART log in sdk_config.h, from which I get this output. 

    APP:INFO:HID Mouse example started.
    APP:INFO:Fast advertising with whitelist.
    APP:INFO:HID Mouse example started.
    APP:INFO:Erase bonds!
    APP:INFO:Fast advertising.
    APP:INFO:Connected
    APP:INFO:Connection secured: role: 1, conn_handle: 0x0, procedure: 1.
    APP:INFO:New Bond, add the peer to the whitelist if possible
    APP:INFO:       m_whitelist_peer_cnt 1, MAX_PEERS_WLIST 8
    

    I've also tried to set uart_config_log_enabled 1, and set the uart_config_log_level to 3. From which I get this output. 

    UART:INFO:Transfer tx_len: 32.
    APP:INFO:HID Mouse example started.
    APP:INFO:Fast advertising.
    UART:INFO:Transfer tx_len: 37.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 28.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 32.
    UART:INFO:Function: nrf_drv_uart_tx_for_uarte, error code: NRF_SUCCESS.
    UART:INFO:Transfer tx_len: 73.
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    UART:INFO:Transfer tx_len: 32.
    Overflow
    Overflow
    Overflow
    Overflow
    Overflow
    Overflow
    Overflow
    

    I'm probably using the wrong syntax here, could you give me an extra hint? From what I've looked I haven't found anything specific for 'p_ble_evt->header.evt_id' fort UART in any devzone posts 

  • It seems to be an issue with Android/Huawei here, and I don't think anything can be done seen from the peripheral, other than possible do forced disconnect within a few seconds if the central has not enabled notifications. 

Related