[Bug]: Heltec V3 has broken BLE on 2.7.17

[QuadrifoglioVerde]

Category

BLE

Hardware

Heltec V3

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.17.83c6161

Description

After updating to version 2.7.17, BLE connectivity on the Heltec V3 stopped working. The device boots normally, the serial debug output looks fine, but when attempting to connect from the Android app nothing happens—there is no error on the phone or in the serial log. After flashing back 2.7.16 then BLE works fine. Tested twice, same result.

Relevant log output

[ccchdro]

Same bluetooth connectivity problem on Heltec E213 and T190, if I delete the pairing with the phone it connects in 2.7.17.83c6161.

[QuadrifoglioVerde]

Re-Pairing works! thank you.

[ccchdro]

It's annoying to have to delete the pairing every time you connect. I went back to 2.7.16 which works fine.

[shalberd]

might have to do with change ae8d3fb

that was merged into 2.7.17 on Dec 9. Then again, maybe not, that's only for nRf52 based devices.

I can confirm problems with BLE pairing / bluetooth connection after it is lost for RAK 4631 device with firmware 2.7.17 as well. Had to even reboot the phone and restart the Android App for connection BLE to work again.
Went back to 2.7.15, no problems anymore.

It's be interesting to know why this "tip" appears above the release notes for 2.7.17:
"If you experience immediate bluetooth pairing failures after updating, this likely indicates that you need to forget the bluetooth pairing and/or perform a full erase and flash"

What are the commits that changed BLE that much in firmware 2.7.17?

Cause, the thing is, the problem wasn't even immediate, but random, on an existing pairing. Why would it work, nothing else changed, after an Android phone restart, but not after closing the Android App and opening it while not restarting the phone?

[phaseloop]

@shalberd that commit was later reverted due to issues with iPhones. AFAIK there was migration to NimBLE v2 some time ago - maybe this is it.

[dblaber]

might have to do with change ae8d3fb

that was merged into 2.7.17 on Dec 9. Then again, maybe not, that's only for nRf52 based devices.

I can confirm problems with BLE pairing / bluetooth connection after it is lost for RAK 4631 device with firmware 2.7.17 as well. Had to even reboot the phone and restart the Android App for connection BLE to work again. Went back to 2.7.15, no problems anymore.

It's be interesting to know why this "tip" appears above the release notes for 2.7.17: "If you experience immediate bluetooth pairing failures after updating, this likely indicates that you need to forget the bluetooth pairing and/or perform a full erase and flash"

What are the commits that changed BLE that much in firmware 2.7.17?

Cause, the thing is, the problem wasn't even immediate, but random, on an existing pairing. Why would it work, nothing else changed, after an Android phone restart, but not after closing the Android App and opening it while not restarting the phone?

I am seeing the same behavior on Heltec V4. Even after a fresh flash after erase-flash from esptool, it immediately works after bonding/pairing, then disconnecting or switching devices, it won't connect at all. I tried @thebentern 's PR, it does not change the behavior at all, and still can find no way to get it to work on any of my heltec v4s. Downgrading to 2.7.16 (after erasing flash once more) bluetooth works as expected.

[madeofstown]

Got 2 V4s on Sunday. Flashed them both with 2.7.17. I can connect once with BLE and then never again until I forget and re-pair the nodes. Brand new, never had Meshtastic firmware.

[dblaber]

Is there any option to pull or at least suggest rolling back this 2.7.17 until this is resolved? This is a major issue, and isn't going to look great with people receiving new devices for the holidays, and BLE is just plain not working (most people I am aware of install the alphas)?
Factory reset does not work, full erase and reflashing does not fix on the heltec v4 as confirmed by at least myself (and my 2 heltec v4s) and @madeofstown , likely others.

Is heltec v4 BLE working properly for anyone on 2.7.17 after initial pairing/bonding?

[Xaositek]

2.7.17 has been revoked, please backup your keys, downgrade to 2.7.16 and restore the keys. Shouldn't have any further issues at that point.

[dblaber]

2.7.17 has been revoked, please backup your keys, downgrade to 2.7.16 and restore the keys. Shouldn't have any further issues at that point.

Just a quick note, you have to do a Full Erase when downgrading, otherwise it bootloops.

[mecworks]

I have to forget the Bluetooth device in iOS settings and re-pair daily or more often in order to connect to my ESP32 v3 and v4 devices. Reconnecting throughout the day becomes slower and eventually, no connection is made and the app goes into a connecting loop. At that point, I need to forget the device and re-pair. I'm using the released iOS app on iOS 26.2.

[vidplace7]

#9117 🙏