Skip to content

Rescue: targeted shell lookup and step timings - #112

Merged
freethinkel merged 1 commit into
mainfrom
rescue-shell-timing
Nov 21, 2026
Merged

freethinkel merged 1 commit into
mainfrom
rescue-shell-timing

Conversation

@freethinkel

Copy link
Copy Markdown
Collaborator

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.

  • shellBlast now asks for the shell's service directly with getPrimaryService(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.
  • The log now has the time to 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

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
@freethinkel
freethinkel merged commit 1913505 into main Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant