Wanted to migrate some our mass production FW to new BLE Single connection SDK for B85 v3.4.2.2 (chip is tlsr8258, same as in EVK TLSR8258DK48). Previously it was developed using early v3.4.2.1 with patch 0004.
I build slave samples vRemote and vSample, see them advertising. But can't connect with Samsung Galaxy S20 FE phone. It is hanging on Discovering Services.
However other cheap Realme Android and I-phone 13 seem connecting fine. I use nRF Connect app. Previously these samples worked OK (on 3.4.2.1 SDK). I try many changes: set preferred conn intervals in gatt table, build different clock speeds (16, 24, 48) MHz, try to disable BLE Security features and PM unit, build with 16k and 32k retention data boot and asm file (the samples are tested using both EVK black board and usb dongle green board). But result the same with Samsung phone - see advertising, but can't connect.
Can you give me advise what could be changed between the 3.4.2.2 and 3.4.2.1 SDKs, so that demo slave apps not working properly with some Android phones?
| No related topics |
Ok, i spent time for some experiments. Looks like this is related with some changes of Android 13 policy (there are a lot of complaints on the Internet, that lots BLE peripheral devices begin working buggy after update to Android 13).
Also, another issue someone reporting, claimed devices with specific standard SIG 2-byte UUID services (numbers like 0x18xx) present in GATT table (which vSample and vRemote demos utilize) can also cause connection issues on some phones when updated to Android 13.
So now, what i could find out:
-My issue on Samsung with Android 13 only seen for both 3.4.2.1 and 3.4.2.2 Sample and Remote slave demos with latest nRF connect app (v4.26.1). If you find and install older version (which i could manage via apk) - the issue is gone. Connection and service discovery is OK.
-Using another popular BLE scanner app from Play Market doesn't give this bug as well.
-The latest nRF connect app on Android 10 device doesn't give this issue as well.
So i guess this is some mix of bugs of both v4.26.1 nRF connect App and Android 13 system. Because, as i said, my old FW (based on 3.4.2.1 SDK) works fine with latest nRF connect as well. But, to know, it has different than demo apps GATT table (all are custom UUID 128 bit units, except Device Information Service).
So for now i just ignore the issue and use older nRF app to debug and test after migration.
Hi，
We found the same problem,when we use high version NRF and Android.