Wear OS

Wear OS

URSA's optional Wear OS companion is a separate APK with an attention-first dashboard, monitor detail, status tile, SHORT_TEXT/LONG_TEXT complications, and confirmed pause/resume for eligible private sessions.

Public mode

Public mode needs no phone pairing or credentials. Enter a published Kuma status-page URL on the watch. The dashboard and detail screen show current state, latency, uptime, recent checks, groups, and tags; the tile and complications summarize the same fleet.

1. Install ursa-wear-<version>.apk from the GitHub Release on the watch.
2. Open URSA on the watch and enter a full status-page URL such as https://kuma.example.com/status/home.
3. Save, then add the URSA tile or complication from the normal watch-face editor.

The watch polls only while its surfaces refresh. It is not a continuous background monitor and does not replace UnifiedPush alerts from the phone.

Private paired mode

The GitHub phone APK is built with the optional Wear Data Layer sender. In phone Settings, choose Pair Wear OS, read the disclosure, and confirm. The active server URL, session, and up to eight access headers go only to a reachable same-package, same-signature watch app. The watch revalidates and encrypts the bounded payload with Tink and Android Keystore before using it.

Private mode enables the same dashboard/detail surfaces plus confirmed pause/resume. Credentials are never typed, logged, or displayed on the watch. Self-signed private connections are refused because the phone's session-lifetime certificate trust cannot be transferred safely.

The F-Droid phone app intentionally omits Play Services and hides pairing. Public mode still works, and Android may mirror ordinary URSA phone notifications to the watch.

Troubleshooting

• Tap to set up: no valid public page or private paired session is stored.
• No data: verify the page is published, the full URL is correct, and the watch can reach it. Base paths are supported.
• No phone found: open both apps, confirm the same release signing identity, and verify the phone/watch are genuinely paired. Independent emulator AVDs do not form a real Wear Data Layer pair.
• Private action unavailable: self-signed connections are intentionally view-only; pair a normally trusted HTTPS server or use public mode.