fw: add new PPS characteristic to reset PPoGATT#857
Open
gmarull wants to merge 1 commit intocoredevices:mainfrom
Open
fw: add new PPS characteristic to reset PPoGATT#857gmarull wants to merge 1 commit intocoredevices:mainfrom
gmarull wants to merge 1 commit intocoredevices:mainfrom
Conversation
We sometimes run into the case where the watch is subscribed to the PPoG data characteristic on the phone and a PPoG session is initialized - then the phone app dies. But the BLE connection still lives (because of ANCS), and the watch does not realize that the PPoG session is dead until it next attempts to send a PP packet. When the phone app restarts, it is waiting for the watch to initalize a PPoG session, which doesn't happen. We need a way for the phone to tell the watch that it needs to re-initialize PPoG. Proposed solution: - Add a new characteristic in the Pebble Pairing Service - UUID 00000006-328E-0FBB-C642-1AA6699BDADAm - Writable with response. - Characteristic value is 1 byte, boolean flag, set to 1 when phone wants watch to re-initialize PPoGATT The mobile app will always write to this when connecting on iOS, but will not use it on Android where it isn't required. Mobile can also remove some of the existing workarounds e.g., sending PPoGATT resets at various times, when this characteristic is supported on the watch. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
sjp4
approved these changes
Feb 20, 2026
Member
sjp4
left a comment
sjp4
left a comment
There was a problem hiding this comment.
Implemented in mobile and and tested - seems to work well!
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
2 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.
We sometimes run into the case where the watch is subscribed to the PPoG data characteristic on the phone, and a PPoG session is initialized - then the phone app dies. But the BLE connection still lives (because of ANCS), and the watch does not realize that the PPoG session is dead until it next attempts to send a PP packet.
When the phone app restarts, it is waiting for the watch to initalize a PPoG session, which doesn't happen. We need a way for the phone to tell the watch that it needs to re-initialize PPoG.
Proposed solution:
The mobile app will always write to this when connecting on iOS but will not use it on Android, where it isn't required.
Mobile can also remove some of the existing workarounds, e.g., sending PPoGATT resets at various times, when this characteristic is supported on the watch.
Fixes FIRM-1268