T-beam with 1.2.52 version installed and android with latest app version installed. I can connect to the t-beam but after a few minutes I get the “connected, but radio is sleeping” message with the cloud/slash icon. Doesn’t seem to wake up when I try to send messages. I tried using the router mode option to prevent it from sleeping but that didn’t seem to work. Any suggestions/ideas?
1 Like
what android OS version are you running?
It is running Android version 11
using is_router to prevent sleep is not recommended but light sleep should be disabled by default anyway since firmware 1.2.52 (upgrading to the latest fw 1.2.53 could help).
- do you have “Nearby devices” listed at: Settings > App > Meshtastic > Permissions?
- try turning bluetooth off then on right after and see if the TBeam connects.
No, ‘nearby devices’ is not listed under permissions, only location is listed.
good. I would set is_router false and update to firmware 1.2.53.
forget the Bluetooth pairing from Android Settings and start fresh. check if that solves your issue.
I updated to 1.2.53 and started fresh. I haven’t got the sleeping error but I get a ‘paring complete, starting service” massage that just hangs and never completes. I can fix it by disabling phone bluetooth and reenabling. Then I get connected message. These are fickle little machines.
first pairing is still rough on some phones. not sure why.
if this happens again or if you can reproduce this behavior, click on “report bug” over the Settings tab and DM me your phone brand & model so I can track this down.
After 1.2.52 firmware you should only see “connected but sleeping” (which means the BLE radio is turned off) when is_low_power or is_router is set to true. Neither setting should be used on a messaging device.
Garth:
I’m on 1.2.53 and I’m still getting the connected but sleeping message. The device has neither low power or router settings as true. How can I troubleshoot what is happening?
You can do a meshtastic --set factory_reset true to reset to default settings which turn off the BLE sleep by default now, or post your meshtastic --info and we can try and figure out which setting is turning off bluetooth.
After multiple reflashing and resetting, now I get “pairing complete, starting service”, which just hangs and never completes.
…and just after I typed that last message, my other t-beam started with the connected, but sleeping message. I will post all the settings to see if anyone can figure this out.
I finally got it resolved. It was a phone setting. Settings, apps, special access to app, battery optimization…show all apps and then disabled battery optimization for Bluetooth and Bluetooth midi service (not sure if I needed to disable this one). It has been running fine, without sleeping now.
2 Likes