Pictures from nrf connect android application :
what does this ms time mention means ?
Signal strength is same on both boards .. but this time seems different.
Could that be causing this problem .. ?
If yes, how can i fix it !?
On custom board, the BLE on reader, doesn’t even connect to BLE App on Android Phone.
Same Android Phone connects to BLE MCU running the same Application on Development Board.
For Custom Board :
For DK :
Error 133 is a generic error on Android and could be caused by multiple different things. However, the most common reason when having this issue only on a custom board, is that the custom board does not implement the external 32.768 kHz crystal the application will try to use it by default and result in crystal drift that can end up like a 133 error when connecting to an Android device.
If this is the issue, try adding
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC
=y to your prj.conf file.
Best regards,
Simon
Your solution works.
Yes, that was the issue.
The DK board has external 32 khz crystal (LFXO) and nrf connect sdk by default is configured to use this LFXO.
I used the same sdk using LFXO but my custom board doesnt have external crystal. So, i have to change my application to use internal RC.
Perfect and on to the point answer that described the issue and had the solution.
Thanks.
The time in ms highlighted in previous screenshots was the advertising interval (time between BLE advertisements).
Due to this disconnect between whats present on custom board and whats configured in application for using 32 KHz, the advertising interval was much faster than expected and may be establishing a connection got failed.
After the solution was applied in application to configure the correct source for 32 KHz, the advertising interval seems now correct as seen for DK.
