Repository navigation
Rescue: targeted shell lookup and step timings - #112
Merged
Merged
Conversation
On a real looping Watch 3 Pro (Windows, Chrome) every try connected and then waited on a full service discovery until the link dropped 14-24 s later, so no command ever went out. Ask for the shell's service (77d4e67c, the same as the Pro 2's, per the firmware's GATT table) directly, with full discovery only as the fallback, and log how long the connect, the service and the shell took, to see where in the watch's restart cycle Windows connects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8PSWDYpGNxzMYKE2JL
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.
The first real-watch log from the stock-face button (Windows, Chrome) shows 20 tries over ~8 minutes. Every one connected, then waited in
getPrimaryServices()until the link dropped 14–24 s later, so no command went out.shellBlastnow asks for the shell's service directly withgetPrimaryService(77d4e67c…). That UUID comes from the WP3 firmware's GATT table and is the same as the Pro 2's. Full discovery stays only as the fallback.connect(), to the service and to the shell, plus the write count and the link state. The next log will show where in the restart cycle Windows connects.Full suite passes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CQSU8PSWDYpGNxzMYKE2JL