This library keeps paying dividends. I've just completed my forth Bluetooth enabled product.

 

This library keeps paying dividends. I've just completed my forth Bluetooth enabled product.

still programming in forth eh?

 

still programming in forth eh?

Too advanced.

 

Forget about the Coronavirus. Here's some important news:

There is a bug in the Bluetooth stack of Android 10 which prevents the RN4020 from connecting properly with the mobile device (so far, Samsung Galaxy S10, Note 10, and S9 devices with the latest upgrade confirmed).

During connection, the Android device thinks it's connected, but the RN4020 never presents the "Connected" string, and the link is not completed.

Hopefully Samsung and/or Android will supply an update to fix this, but in the meantime, here's a work around:

By default, the RN4020 opens a link in both client and server mode. During the link negotiation process, the radio attempts to capture services provided by the Android device. This is where things break down.

The solution is to operate the radio in Server Only mode -- thereby eliminating that part of the negotiation process.

This is done by setting the Server Only bit in the Supported Features register. Use 0x00002000 in the SR command (along with any other desired bits) and the connection completes as expected.

This will not work for you if you expect to access services provided by Android (not my case).

 

Is this from the Android 10 Bluetooth security update?

 

Is this from the Android 10 Bluetooth security update?

No, Android 10 in general -- on Samsung devices -- since it's original inception on the Galaxy S10. We've been getting slowly increasing service calls for a while now (with a corresponding jump in calls with the release of the Android 10 upgrade for S9 devices), and only yesterday did the Microchip guys and me figure this out.

In fact, IIRC there is an insulin monitoring device out there (I don't know that they are using the RN4020) that has been having a very public problem with this. Imagine your medical -- life saving -- device not connecting and monitoring your condition as it should.

 

Another reason not to upgrade critical systems that are working fine.

 

Another reason not to upgrade critical systems that are working fine.

With Samsung, you can only delay an upgrade for so long until it forces the upgrade.

 

With Samsung, you can only delay an upgrade for so long until it forces the upgrade.

That's why (among other reasons) I rooted my S8

 

I got an update for my Note 9/Android 10 this weekend. Seems to have fixed the problem. Finally.