Question 1

Why does OpenDisplay Linux receiver freeze on the last frame after sender reconnects or stream resolution changes (Extend to Mirror)?

Accepted Answer

This was a bug where any sender reconnect froze the picture: the decoder reset flushed the live pipeline with `reset_time=true`, causing the keyframe to be stamped with the old running time while subsequent frames used the new base time, so the GL/GTK sink silently stopped presenting frames (stats show `renderFps: 0.0` and a flat `rendered` counter while `decErr` stays 0). Fixed in od-receiver v1.28.2 — upgrade to that release or newer. As a temporary workaround on older versions, restart `od-receiver` so the sender reconnects and announces the new stream size on a fresh pipeline.

Question 2

Why do taps land at twice the touch position (2x offset) on a GNOME Wayland virtual display with scale 2, and how to fix it?

Accepted Answer

This is a coordinate-mapping bug in od-sender versions before v1.28.2 (fixed in PR #428). On GNOME/Mutter (versions 44 through 50.1), `NotifyPointerMotionAbsolute` coordinates must be sent in the view's logical layout units, but the sender was sending physical pixels. With a scale-2 receiver (e.g., an iPad at 2360x1640), taps therefore landed at roughly 2x the correct position and the right/bottom halves were unreachable.

Fix: upgrade to od-sender v1.28.2 or later — re-run `install.sh` with the new release tarball, then run `od-sender run` with the default `--scale passthrough`. The GNOME backend now maps touches over the logical size (physical size divided by the applied scale, e.g., 1180x820), or the physical size when `layout-mode` is set to physical.

Workaround on affected versions: run `od-sender run --scale 1`. Touch becomes accurate, but everything appears tiny since the Linux sender has no display-size option to combine scale 1 with a smaller desktop.

Question 3

How to fix OpenDisplay "no receiver found" error when connecting over Tailscale VPN?

Accepted Answer

OpenDisplay's automatic device discovery relies on local-network broadcast, which does not traverse Tailscale's overlay network, so the sender fails with `ERROR no receiver found within 10s` even though `tailscale status` shows both devices online. Workaround — bypass discovery and connect directly to the receiver's Tailscale IP on port 9000:

1. Open the OpenDisplay receiver app on the phone and keep it in the foreground.
2. Get the phone's Tailscale IP (100.x.x.x address) via `tailscale status` on the computer or the Tailscale app on the phone.
3. Run: `od-sender run --to <tailscale-ip>:9000`

You can also verify whether broadcast discovery works at all on your network with `od-sender list --timeout 10` before falling back to the direct IP connection.

OpenDisplay

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects