-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: T-Deck Bluetooth Won't Start w/ v2.5.19.f9876cf #5876
Comments
Thanks for the report. A couple questions to help us understand:
If you could connect it to a computer and get logs (eg click serial monitor on flasher.meshtastic.org ) that would be very helpful. |
Are you using the new MUI? |
Not using MUI with either of these currently just vanilla v2.5.19.f9876cf. Can fetch logs tomorrow but I didn't see any obvious errors or warnings. |
I just got mine delivered today and got it setup with the app/Bluetooth then I decided to update the firmware. After that I am unable to get it to reconnect. The app does not even detect the device. I have also removed the Bluetooth device from the phone and removed the app. Reinstalled the app issue persists. Not a good first impression.. |
So I just used the website to try and enable Bluetooth but that did not work. Anyway to get the Bluetooth back on? |
Rollback to the stable firmware. 2.18 |
Noticed the same thing last night. I was on 2.5.18ebafc with T-Deck Plus. Flashed to 2.5.20.4c97351 lost bluetooth. Rolled back to 2.5.18 and ran "--set bluetooth.enabled true" to get it working again. |
Category
BLE
Hardware
T-Deck
Firmware Version
2.5.19.f9876cf
Description
I have two T-Decks that work as expected using v2.5.18 but on v2.5.19.f9876cf the Bluetooth functionality stops working and devices never show up in BLE scan.
Using "--set bluetooth.enabled true" does nothing and "--get bluetooth.enabled" returns false always. Need to run "--set bluetooth.enabled true" after reflashing v2.5.18 to get it to work again.
Relevant log output
The text was updated successfully, but these errors were encountered: