s132_nrf52_6.1.0_softdevice abnormal behaviour about connect param update

[zhangys]

Hi All,

  We found a problem about the NRF52832AA connect parameter update problem on some cell phones.

  1. While the app connect to our device, parameter update not only one time, is this correctly?

   

  2. I set the NEXT_CONN_PARAMS_UPDATE_DELAY to 30s, but it update parameter after 2.5s sometimes, is this correctly?

  3. While our program run in a scheduler task, the connect parameter update event happened, but it not correctly back to my task procedure and back to the command that ever executed.

    

[Vidar Berg]

Hello,

1. Some Android phones prefers to do the service discovery at a fast connection interval (eg. 7.5 ms), then update to a slower connection interval as soon as the discovery is complete. However, I'm not sure why the MTU/DLE events are repeated. Could you try the stock ble_app_uart example and see if it behaves similarly with this particular phone?

2. Like mentioned above, the connection update request may be issued by the phone as well.

3. Sorry, not sure I understand what I'm looking at here. Are Softdevice events reported in the interrupt context or put in a scheduler queue? Also, are you using an RTOS or just the SDKs app_scheduler?

Best regards,

Vidar

[zhangys]

Hello，

1. Ble_app_uart example is the same behavior.

2. ...

3.I just run the app_scheduler, my task is running in scheduler task in main function, the "connect parameter update" event is trigered(interrupt context) while i communication our cloud server with wifi module(It happens in a very low , about 1 time in 1330 times test when i set broadcast power as -12dbm, and 0 times in 5000 times test when i set broadcast power as 0dbm).

[Vidar Berg]

Hello,

Could you provide a list of the phones that show this behaviour (also include the Android version)?

3. Is the problem that you're getting a "connection paramater update" event in 1 out of 1330 tests? You highlighted some other events in the screenshots you posted.