fix(tandem): re-assert BLE connection priority to stop Mobi disconnects - #219
Draft
haarisedhi102 wants to merge 1 commit into
Draft
Conversation
The Tandem Mobi renegotiates the BLE connection down to its power-saving profile (interval=30ms, latency=29, timeout=2s) ~15s after connect. The 2s supervision timeout causes frequent CONNECTION_TIMEOUT drops, breaking bolus/TBR delivery and the startup history download. Re-assert CONNECTION_PRIORITY_HIGH every 10s while connected so the link stays at interval=15ms/latency=0/timeout=5s (5s supervision window), eliminating the drops.
haarisedhi102
marked this pull request as ready for review
August 18, 2026 17:07
haarisedhi102
marked this pull request as draft
August 19, 2026 04:20
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
1 participant
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.
The Tandem Mobi renegotiates the BLE connection down to its power-saving profile (interval=30ms, latency=29, timeout=2s) ~15s after connect. The 2s supervision timeout causes frequent CONNECTION_TIMEOUT drops
Re-assert CONNECTION_PRIORITY_HIGH every 10s while connected so the link stays at interval=15ms/latency=0/timeout=5s (5s supervision window), eliminating the drops.
added logs here to show the first full day of stable connection i had because of this change
AndroidAPS_LOG_1787060961591.log.zip