WristviaWristvia controls the Android phone’s active media player. Track display and controls have physical test results; audio remains on the phone’s chosen output.
How the prototype works
Start playback in a compatible Android media app and enable Wristvia’s Media controls. Notification access lets Wristvia use Android’s public media-session interface. Open Media on the linked watch. Controls depend on what the current session advertises.
The current implementation supports a nearby Bluetooth path and separately approved internet fallback. Track, artist and artwork sharing have a privacy control. No Spotify account login or Spotify Web API connection is required for this media-session route.
Controls and their limits
Play, pause, previous and next depend on the active session. Volume and app-specific More buttons are available only when that session provides them. Commands target that session and expire; a stale or unavailable session should not become a different player.
Wristvia does not copy your music library or stream Android audio through the watch. Availability of an Android app’s session is not a promise that every player or casting configuration works. See the Android media-session documentation.
What was physically observed
On 29 October, tests confirmed playback control, song changes, crown volume and source-app buttons. Following nearby Media recovery on 1 November, Tomas saw a real track and reported working Stop, then reported an image and working controls.
The latest observation did not isolate Bluetooth from authorized internet fallback. Current pause/resume, exact transport, artwork refresh timing, reconnect behavior, battery and watch Back/close still need device checks. Earlier successes do not automatically verify the latest build.
If nothing is playing or controls are unavailable
Check that playback is active on the phone, Wristvia Media is enabled, notification access remains granted and the devices can communicate. “Nothing playing” differs from “Phone not connected.” Opening Wristvia can help inspect the current state, but is not proof of background reliability.
Use Support if the state remains inconsistent. Do not interpret a dispatched command as proof that the player changed.