[3.0 Beta 11] RileyLink appears not to be scanned (legibility problem)

[rustymonkey]

Upon launching 2.8.2.18-dev, no connection to the OL was possible. Clearing cache, restarting the phone and reseting the OL had no effect. Deleting the OL and initiating a scan didn't resolve the issue either because AAPS failed to find the OL (I've never observed this before)!

This was previously working with all earlier builds (last tested was 2.8.2.16).

Tested with 2.8.2.18-dev = B11 / S7 running Android 11 / OL firmware 2.5 / MDT 554

EDIT: this log was taken immediately after attempting to Scan for the OrangeLink. AndroidAPS_LOG_1639632763003.log.zip

EDIT2:

• On launch, there was no prompt for any new Bluetooth permissions
• The Setup Wizard didn't prompt for any new Bluetooth permissions either

[rustymonkey]

Note: reverting to 2.8.2.16 solved the problem confirming that it's a recent regression.

[rustymonkey]

Further investigation reveals that this issue occurred due to a combination of: 1) #474 : this issue sometimes occurs on reboot, the workaround requiring deletion/addition of the RL/OL 2) On attempting the above workaround, a cosmetic bug in Beta 11 in the RileyLink configuration dialog caused the scanned OrangeLink to display almost invisibly, making it appear as if scanning didn't work. In other words, when the user presses [Scan] on the RileyLink configuration panel, the RL is scanned, but displays so faintly that it's almost invisible! See below:

[Philoul]

@rustymonkey can you test PR #1120 and tell me if it fix your issue (black text...) ?

[rustymonkey]

Verified in 3.0 RC2. Thanks!