No BLE or WiFi on T-Deck Plus 0.9.12 #254

New Issue

2026-10-27T15:46:05+01:00

adam commented

2026-10-27 15:46:05 +01:00

Describe the bug
Neither BLE nor WiFi functions on T-Deck Plus using the 0.9.12 firmware. Downgrading to 0.9.11 fixes the issue.

Which device are you using
LilyGO T-Deck Plus

Which Firmware are you using
0.9.12

To Reproduce
Clean install. Ensure BLE is enabled. Attempt to scan for BLE devices.
Turn off BLE, and WiFI on. Search for SSID, try to enter SSID manually.

**Describe the bug** Neither BLE nor WiFi functions on T-Deck Plus using the 0.9.12 firmware. Downgrading to 0.9.11 fixes the issue. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** 0.9.12 **To Reproduce** Clean install. Ensure BLE is enabled. Attempt to scan for BLE devices. Turn off BLE, and WiFI on. Search for SSID, try to enter SSID manually.

adam commented

2026-10-27 15:46:06 +01:00

me too, tried on two separate t-decks

me too, tried on two separate t-decks

adam commented

2026-10-27 15:46:07 +01:00

Worked both on BLE and WiFi out of the box, but only the very first time. At the second connection with BLE, BLE stopped working. Wasn't advertising a recognised device anymore. Tested with two or 3 smartphones with fresh smartphone companion app. WiFi still working though. It's possible that WiFi will stop working too...
Does someone know how to reset BLE/(possibly WiFi) without reflashing the firmware? Could possibly solve the issue. I'm on T-Deck Plus. I did change the BLE PIN without success.

Worked both on BLE and WiFi out of the box, but only the very first time. At the second connection with BLE, BLE stopped working. Wasn't advertising a recognised device anymore. Tested with two or 3 smartphones with fresh smartphone companion app. WiFi still working though. It's possible that WiFi will stop working too... Does someone know how to reset BLE/(possibly WiFi) without reflashing the firmware? Could possibly solve the issue. I'm on T-Deck Plus. I did change the BLE PIN without success.

adam commented

2026-10-27 15:46:08 +01:00

Datapoint from me:

For me (MC Term version 0.9.12 on LilyGo T-Deck Plus), WiFi works. I can connect to my local network, tile download works, and I can connect from an external companion app via TCP to the T-Deck running MC term version 0.9.12.

I also just tried BLE, using "meshcore-open" on GNU/Linux. It did also work.
But I also observed/ was told that you can re-connect with a different app to BLE only if you remove the MeshCore device before from your operating system's BlueTooth management.

Regards!

*Datapoint from me:* For me (MC Term version 0.9.12 on LilyGo T-Deck Plus), WiFi works. I can connect to my local network, tile download works, and I can connect from an external companion app via TCP to the T-Deck running MC term version 0.9.12. I also just tried BLE, using "[meshcore-open](https://github.com/zjs81/meshcore-open)" on GNU/Linux. It did also work. But I also observed/ was told that you can re-connect with a different app to BLE only if you remove the MeshCore device before from your operating system's BlueTooth management. Regards!

adam commented

2026-10-27 15:46:08 +01:00

I retested the BLE-Connection:

With the Android App BLEHero I could find and bind the LilyGo T-Deck Plus.
Also I had to shorten the Name in the Global Menu to make the device appear in the companion app. (I could change it back to the full name after successful binding). I think there could be a problem with the length of the advertised device name. For best interoperability it should be shorter than say 19-21 chars. But with the prepended "MeshCore-" there is not so much room left.

In case it helps.

I retested the BLE-Connection: - With the Android App BLEHero I could find and bind the LilyGo T-Deck Plus. - Also I had to shorten the Name in the Global Menu to make the device appear in the companion app. (I could change it back to the full name after successful binding). I think there could be a problem with the length of the advertised device name. For best interoperability it should be shorter than say 19-21 chars. But with the prepended "MeshCore-" there is not so much room left. In case it helps.

adam commented

2026-10-27 15:46:09 +01:00

I retested the BLE-Connection:

* With the Android App BLEHero I could find and bind the LilyGo T-Deck Plus.

* Also I had to shorten the Name in the Global Menu to make the device appear in the companion app. (I could change it back to the full name after successful binding). I think there could be a problem with the length of the advertised device name. For best interoperability it should be shorter than say 19-21 chars. But with the prepended "MeshCore-" there is not so much room left.

In case it helps.

BLE Hero was a good idea. I just tried that with my T-Deck and I was able to pair it with my phone. MCTerm says that BLE is connected. However, neither meshcore-open nor the official MeshCore app are able to actually recognize the device. I also tried changing the device name to just be one character, for testing. My phone gets the bluetooth device name MeshCore-m, so I feel like that's not entirely the issue here, at least for me.

I wish I was able to manually input a MAC address...

> I retested the BLE-Connection: > > * With the Android App BLEHero I could find and bind the LilyGo T-Deck Plus. > > * Also I had to shorten the Name in the Global Menu to make the device appear in the companion app. (I could change it back to the full name after successful binding). I think there could be a problem with the length of the advertised device name. For best interoperability it should be shorter than say 19-21 chars. But with the prepended "MeshCore-" there is not so much room left. > > > In case it helps. BLE Hero was a good idea. I just tried that with my T-Deck and I was able to pair it with my phone. MCTerm says that BLE is connected. However, neither meshcore-open nor the official MeshCore app are able to actually recognize the device. I also tried changing the device name to just be one character, for testing. My phone gets the bluetooth device name `MeshCore-m`, so I feel like that's not entirely the issue here, at least for me. I wish I was able to manually input a MAC address...

adam commented

2026-10-27 15:46:09 +01:00

Okay, nevermind (partially), I had to reboot my phone for some reason, but I can get it to work by pairing with BLE Hero with the short name, and then pairing. However, it doesn't work with meshcore-open, only the official app.

Okay, nevermind (partially), I had to reboot my phone for some reason, but I can get it to work by pairing with BLE Hero with the short name, and then pairing. However, it doesn't work with meshcore-open, only the official app.

adam commented

2026-10-27 15:46:10 +01:00

Not working properly for me either on 0.9.12

WiFi will connect intermittently at best, usually after several disable/enable cycles, and even then, sometimes it will stay connected for just a minute or 2, sometimes maybe 30-60 minutes.
Bluetooth straight up does not work, even with a short device name, I can never find the device to pair to it.

Brand new T-Deck Plus device, received it today, flashed the 0.9.12 firmware and had immediate problems.

Downgraded to 0.9.11 and Bluetooth immediately works, but WiFi still doesn't want to behave.

Not working properly for me either on 0.9.12 WiFi will connect intermittently at best, usually after several disable/enable cycles, and even then, sometimes it will stay connected for just a minute or 2, sometimes maybe 30-60 minutes. Bluetooth straight up does not work, even with a short device name, I can never find the device to pair to it. Brand new T-Deck Plus device, received it today, flashed the 0.9.12 firmware and had immediate problems. Downgraded to 0.9.11 and Bluetooth immediately works, but WiFi still doesn't want to behave.

adam commented

2026-10-27 15:46:11 +01:00