Display should update from "Ready to Pair" to "Frame is Paired" when pairing completes

[CitizenOneX]

When pairing with a host (tested on Windows 10 and Android 14, and firmware v24.310.0800) the text "Ready to Pair" doesn't change to "Frame is Paired" when bluetooth pairing completes.

After pairing, if Frame is put in the cradle and taken out again, it will correctly display "Frame is Paired".

This might go some way to explaining some of the pairing challenges for developers (pairing is actually working, but the display gives a misleading message so they keep trying to un-pair and re-pair.)

Possibly a "red herring" but I'll mention it here:

• I noticed today that this reboot (Frame back in the cradle and out again) appeared to be necessary within a mobile app for the first bluetooth.connect() call after pairing to succeed. Immediately after pairing, connect() didn't seem to work, but after a reboot of Frame it did. Maybe there is some other state that gets set properly on a reboot which could potentially be set on a successful pairing to allow connects to happen immediately. If true this also might explain some developer difficulty, if connect() calls after successful pairing won't work until a reboot in the cradle occurs. Developers might keep un-pairing and re-pairing because the device can't be connected to, but a simple reboot of Frame might have fixed it. (We can also document that developers should put Frame in and out of the cradle after pairing as a workaround, if this really is an issue.)
• When trying to reproduce in Python, the first call to bluetooth.connect() caused the system pairing popup, but it doesn't block until pairing completes so the program already ran to completion and had an exception The attribute requires authentication before it can be read or written. A subsequent run of the program without putting Frame in its cradle and out again succeeded, which suggests that Frame's bluetooth state to accept connections is fine (except for the message on the display being misleading), so the mobile app's failure to connect might be a client side issue.