Increase bluetooth 5.0 PHY speed and MTU on esp32_s3#8261
Merged
thebentern merged 12 commits intoOct 12, 2025
Conversation
Rebase with upstream
Member
|
Amazing! |
Contributor
|
Related to #7880 |
Contributor
|
@h3lix1 can we enable this for ESP32-C6 targets as well? |
Contributor
Author
|
@thebentern Added, but I'm unable to test. If anybody from MTools is reading this 😉😉 |
|
tested on my esp32c6,works perfectly |
Contributor
Author
|
Tested with #8263 to be compatible. |
Member
|
Tested on Heltec v4 on Google Pixel 8a && Asus Zenfone 8, worked well. |
fifieldt
approved these changes
Oct 11, 2025
Member
|
For good measure, this did not break a Heltec T114 (not ESP device, so should observe no change) |
jeek
pushed a commit
to jeek/Meshtastic-Exploiteers-Hacker-Pager
that referenced
this pull request
Jun 30, 2026
* Increase Bluetooth speed to 2MB, increase MTU * Adding esp32c6 * trunk fmt..
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added ESP32-S3-only startup tuning so we explicitly request MTU 517 (was stack default 23), a 2 M PHY (was 1 M), and 251-byte PDU suggested data length (was the legacy 27-byte default) when bringing up NimBLE
On every new connection we now immediately re-request 2 M PHY (instead of leaving the link on 1 M) and 251-byte data length, while logging the initial/target MTU to confirm the negotiation
Will negotiate down if needed for devices that do not support Bluetooth 5.0
Tested on ESP32-S3 hardware and observed the BLE logs to confirm the negotiated MTU/PHY/data length
🤝 Attestations
Heltec (Lora32) V4
Tested on the following phones: