Repository navigation
Rescue: 3 s per notification subscription, only the channels it needs - #109
Merged
Merged
Conversation
…nes it doesn't need On a Watch 3 Pro stuck in a boot loop, every attempt now stalls on the first startNotifications — the first step the watch itself has to answer, since Windows can serve the service list from its cache — until the watch restarts about 17 s later. Rescue now listens only on the command and data channels (plus the shell when it has to pair) and gives up on a subscription after 3 s, so a dead try ends fast and leaves time for more tries in the windows the watch is up. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8Nr9jJ3ALiRfiDuC6m
…il answered Found in the Watch 3 Pro firmware and confirmed in the cmf-watch-utils emulator: - the watch ignores a factory reset until a time write (0x8004) has marked the link live, and a clock more than 2 min off takes the time only on the second write — so the reset now goes out after the time, twice, in the reference client's format; - the watch drops every frame for its first 200 ms on a link, so the first authName was lost whenever rescue connected quickly; rescue now re-sends it every 100 ms until the watch answers. Before this, the rescue page's reset could not have worked on any watch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8Nr9jJ3ALiRfiDuC6m
…or timings The cmf-watch-utils emulator (WP3 firmware) puts numbers on both: a live watch answers a subscription in 8-11 ms, while one past its crash keeps advertising and accepting a link but answers nothing until it reboots, so waiting 3 s only delays the next try. And authName re-sent every 20 ms lands 5-6 ms after the 200 ms gate instead of 38-61 ms, with exactly one handled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8Nr9jJ3ALiRfiDuC6m
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
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.
Already deployed to fmc.tools from this branch; merging so main matches prod.
A Watch 3 Pro in a boot loop stalls every attempt on the first
startNotifications, the first step the watch itself has to answer, until it restarts about 17 s later. Rescue now subscribes only to the command and data channels (plus the shell when it has to pair) and gives up on a subscription after 3 s, so failed attempts end quickly and more fit into the windows when the watch is up.Test:
tests/ble-within.test.ts. Not verified on a real watch.🤖 Generated with Claude Code
https://claude.ai/code/session_01CQSU8Nr9jJ3ALiRfiDuC6m