Skip to content

NimbleBluetooth misc cleanups#10264

Merged
thebentern merged 2 commits into
meshtastic:developfrom
cpatulea:ble-cleanup
Apr 23, 2026
Merged

NimbleBluetooth misc cleanups#10264
thebentern merged 2 commits into
meshtastic:developfrom
cpatulea:ble-cleanup

Conversation

@cpatulea

Copy link
Copy Markdown
Contributor

Build tested on heltec-v3, m5stack-unitc6l (the only NIMBLE_TWO variant).

🤝 Attestations

  • I have tested that my proposed changes behave as described.
  • I have tested that my proposed changes do not cause any obvious regressions on the following devices:
    • Heltec (Lora32) V3
    • LilyGo T-Deck
    • LilyGo T-Beam
    • RAK WisBlock 4631
    • Seeed Studio T-1000E tracker card
    • Other (please specify below)

@github-actions github-actions Bot added needs-review Needs human review enhancement New feature or request labels Apr 23, 2026
This is a safety net for pioarduino/NimBLE work where there's multiple
similar variants of the same method (eg. onConnect) and it's easy to get
the wrong one and accidentally miss a callback.
@thebentern thebentern merged commit 22d50fe into meshtastic:develop Apr 23, 2026
63 of 66 checks passed
@cpatulea cpatulea deleted the ble-cleanup branch April 24, 2026 05:15
mariotti pushed a commit to mariotti/firmware that referenced this pull request May 6, 2026
* Delete unused clearNVS() (last used in commit 761804b).

* virtual methods: add 'override' to ensure we get the signature right.

This is a safety net for pioarduino/NimBLE work where there's multiple
similar variants of the same method (eg. onConnect) and it's easy to get
the wrong one and accidentally miss a callback.
@cpatulea

Copy link
Copy Markdown
Contributor Author

I wonder if this got reverted accidentally or something? void clearNVS() is supposed to be deleted but show up in #10741

thebentern added a commit that referenced this pull request Jun 19, 2026
… init

- Delete unused clearNVS() (no callers; should have been removed in #10264).

- Move purgeIncompatibleBleBonds() after the "Init the NimBLE" log so bond-cleanup output doesn't appear to precede module init; it still runs before BLEDevice::init() reads the store.
thebentern added a commit that referenced this pull request Jun 19, 2026
)

* NimBLE params overhaul and try-fix for incompatible bond cleanup

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Address PR review: remove dead clearNVS(), defer bond-purge log below init

- Delete unused clearNVS() (no callers; should have been removed in #10264).

- Move purgeIncompatibleBleBonds() after the "Init the NimBLE" log so bond-cleanup output doesn't appear to precede module init; it still runs before BLEDevice::init() reads the store.

* Update MAX_SATELLITE_NODES and WARM_NODE_COUNT definitions for ESP32-S3 PSRAM support

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
raghumad pushed a commit to raghumad/mezulla-firmware that referenced this pull request Jun 25, 2026
…htastic#10741)

* NimBLE params overhaul and try-fix for incompatible bond cleanup

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Address PR review: remove dead clearNVS(), defer bond-purge log below init

- Delete unused clearNVS() (no callers; should have been removed in meshtastic#10264).

- Move purgeIncompatibleBleBonds() after the "Init the NimBLE" log so bond-cleanup output doesn't appear to precede module init; it still runs before BLEDevice::init() reads the store.

* Update MAX_SATELLITE_NODES and WARM_NODE_COUNT definitions for ESP32-S3 PSRAM support

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request needs-review Needs human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants