[EVK] Configure with Bluetooth fails after entering/exiting "Base" mode.

[doug-foster]

Not sure this is a normal use case, but it is an anomaly I've seen with RTK_E v2_2 (from the binaries repo) running on the EVK.

1. Pair Android tablet with "EVK Base-8ECE".
2. Reset the EVK & start in "Rover" mode.
3. Connect "Serial BT Terminal 1.49" on tablet to "EVK Base-8ECE" over BT Classic.
4. NMEA out is displayed, send "+++" to interrupt, serial menu is displayed, "Configure with Bluetooth" () works fine.
5. Use menu to change from "Rover" to "Base". Exit menu.
6. Following is displayed:

Base Mode - SIV:32
Connection lost

1. Attempt to reconnect "Serial BT Terminal 1.49" on tablet to "EVK Base-8ECE" over BT Classic.
2. Following is displayed:

Connecting to EVK Base-8ECE ...
Connection failed: read failed, socket might be closed or timeout, read ret: -1

1. Allow "Survey-in" to complete, run as base for a short period of time.
2. Toggle the front "Mode" button from "Base" back to "Rover."
3. Attempt to reconnect "Serial BT Terminal 1.49" on tablet to "EVK Base-8ECE" over BT Classic.
4. Following is displayed:

Connecting to EVK Base-8ECE ...
Connection failed: read failed, socket might be closed or timeout, read ret: -1

The EVK must be reset for "Configure with Bluetooth" to work again.

Other observations:

• Serial interface and "Configure with Serial" works fine during all BT scenarios above.
• RTK "Correction Priorities" has Bluetooth set as 0 priority to receive corrections from BT NTRIP server when in "Rover" mode. However, the above anomaly happens even when in "Rover" mode and not connecting to an NTRIP server for corrections (i.e. status for Priority 0 BT correction stays "Inactive").