Hi - I am experiencing very similar issues on two devices. I am able to pair with the device, however the Bluetooth connection drops after 5-10 seconds. Interestingly the Bluetooth paring PIN is not requested at paring.
I have experience the error on two devices - a Samsung S20 FE and also a Google Pixel 6 Pro.
The error occurred following the update of the Samsung to android 12 (the google pixel 6 is only available from factory with android 12)
@andrew.belov - is there an update for these issues? unfortunately it has rendered my workflow completely unusable.
We’ve released an update of reach firmware, 28.2, with improved Bluetooth stability. It should help your units to keep a connection to Android devices.
Yes, you did it. Awesome. Excellent. Thank you very much. The test with QField on a Samsung Active Tab 3 was successfull. No drop of bluetooth connection anymore.
Can you give a brief summary what google or samsung has changed on the bluetooth stack to break bluetooth connection and what you had to do to compensate for it?
To put it in a nutshell, the recent Android patch stopped accepting some default Bluetooth settings of external devices. We’ve tuned these settings to be aligned with Android’s new Bluetooth link policy.
Simultaneously with Samsung devices, we have tested the Fix on the Pixel 6 with Android 12 with Reach RS+ and Reach RS2. Both setups worked fine in the office.
There is a variety of Android versions and devices in the market. As you can see, the same Android version can behave differently on various devices. It significantly complicates our work on the compatibility of our devices and software.
That is why we always ask to provide feedback on our fix releases.
If you still experience Bluetooth disconnections, please share full system reports from units to support@emlid.com. We’ll check what else we can do from our side to improve the Bluetooth connectivity.
