BLE Loses connection to T1000-e

[4a4b3837]

The Bluetooth connection to the node frequently enters sleep mode. Opening the app should restore the connection, but this doesn't happen. I tried setting the device to "none" and then back to the desired device (or switching to another device and back), but the connection still fails to establish. When using the scan button, the device is detected and listed. However, selecting it closes the selection window, returning me to the paired devices list without establishing a connection.

If the node is detected as "within range," it should be possible to establish a connection.

In the previous app version, toggling Bluetooth off and on in the Android settings sometimes resolved the issue. In the current version (2.6.30), this no longer works. The problem occurs across multiple nodes, including:

• T-Deck, Seeed P1, and T1000-E (2.7.2)
• Heltec v3 (2.6.11)

How can I force the connection to be established?

[n0qbh]

I'm seeing similar behavior from two different Lenovo tablets with my Meshtastic nodes.
I have to reboot the tablet to re-establish a connection. One node is FW 2.6.4 the other 2.6.11
The Android ware is 2.6.3
Nodes are RAK4631 and T-echo.

[overkillthemighty]

I just submitted a bug report, I think it is the same/similar problem? I will be connected to my T1000-E, but it shows 0 nodes connected (Including my node).

I can try to disconnect in the node list (see screenshot) but it continues to say it is connected. Trying to connect to the node again does nothing.

Rebooting the phone seems to fix it. As well as force closing the app, nothing else does though.

It did not do this when I first got my T1000-E (I got it on release) a while back it started disconnecting, and I was able to use the disconnect option, then re-select the node to reconnect, now I have to do this. I feel like the disconnects started when the app UI refresh that added the disconnect button was released. I have updated from beta to alpha to see if it fixes the issue, but it has not.

[n0qbh]

One more clue. This behavior has gone on since my original post.
When the Bluetooth locks up between the tablet(s) and the node(s) and I try to scan for a Bluetooth connection, it returns a Android error saying Bluetooth seen an unexpected error and has closed. The only solution for me is reboot or shut down and restart.