DisplayWeave turns iPhone, iPad, and Android devices into local extended displays—with Apple USB/WiFi, Android ADB USB, verified Mac/Android update channels, touch input, HEVC, and experimental high refresh.
Install once, then update Mac and Android in place.
Release packages are mirrored as immutable static files through Cloudflare. Android p6 uses Cloudflare first and falls back to the matching GitHub Release when the mirror is unavailable.
01
SendermacOS
Guided Mac first install
Drag DisplayWeave into Applications; later releases use EdDSA-authenticated Sparkle updates. Ad-hoc signed, not notarized, and may require Gatekeeper approval.
Install over the existing app once. Later downloads are checked by size, hash, package, version, SDK, and pinned signing certificate before system confirmation.
A release status board with the edges left visible.
Verified means exercised on available physical hardware. Experimental means implemented with hardware-dependent performance. Deferred work is stated plainly.
Verified
Android USB and recovery
HEVC/120 and H.264/60 over wired ADB forward; unplug/replug, ADB restart, authorization revoke/reallow, foreground return, and Auto fallback recovery verified.
Touch and mixed receivers
Prior Preview 2 evidence covers tap, drag, cursor, two-finger scroll, and one iPhone WiFi receiver running beside one Android receiver; this was not rerun for v0.2.
Offline Android distribution
Release APK v2 signature, certificate identity, first install, and upgrade install verified without a Google developer account.
Update and iPhone display paths
Mac EdDSA and Android package/certificate verification reject tampered updates. Metal drawable synchronization fixes the reported iPhone black-screen path without changing the receiver protocol.
Experimental
Android high refresh
30/60/90/120fps negotiation with HEVC and H.264 fallback. OnePlus WiFi HEVC/120 measured about 109–111 rendered FPS; stable 120 FPS is not guaranteed.
Measured performance controls
Short CSV/JSONL benchmark recording, target/actual bitrate separation, Auto/Manual/Benchmark bitrate, bounded adaptive changes, low-latency queues, and transport-aware GOP are implemented. The controlled USB/WiFi matrix remains pending.
Private macOS display API
The Mac sender relies on CGVirtualDisplay. Future macOS versions may change private behavior.
Deferred
Remaining matrix
Two simultaneous Android devices, controlled same-condition USB/WiFi benchmark, and 30-minute/2-hour endurance runs are not complete.
Transport logic
Auto follows the cable—without trapping the session.
One install identity anchors the handover, so a wireless-debugging endpoint cannot masquerade as a second USB device.
01
Discover wired ADB
Only a device row with wired USB metadata is eligible.
02
Forward a dynamic port
Each serial receives its own Mac-local TCP port to Android :9000.
03
Recover with limits
Protocol grace and bounded 0.5/1/2/4/8 second retries avoid hot loops.
04
Fall back by install ID
Auto uses WiFi only for the same Android app installation.
05
Upgrade back to USB
Cable return atomically ends WiFi before wired reconnection.
Measured path
Input and pixels travel both ways.
109–111rendered FPS
Historical OnePlus HEVC/120 WiFi run; a device-specific result, not a guarantee.
≈26 sUSB → WiFi fallback
Observed after socket reset, protocol grace, and the full bounded recovery sequence.
1 + 1mixed receivers
Prior Preview 2 evidence: iPhone over WiFi and Android through an independent session at the same time.
2-waylocal interaction
Video streams outward while touch, drag, cursor, and two-finger scroll return to macOS.
Local-first boundary
Your screens stay on your local link.
DisplayWeave does not require an account or project-operated cloud relay. That does not make every transport production-secure yet.
Current WiFi video and control TCP is not production-encrypted. Use a network you trust.
02
ADB trust is broad
Android USB debugging authorizes the Mac as a debugging host, not only DisplayWeave.
03
Transparent origin
DisplayWeave is GPL-3.0 software derived from OpenDisplay, with SideScreen technical-reference notices retained.
Install and operate
Important questions before you connect.
Can I install the Android APK without Google Play?+
Yes. Enable installation from the source you use to open the APK, then verify its SHA-256 and project certificate fingerprint before installing.
Will later Mac and Android releases require reinstalling?+
After manually installing this update-capable release once, Mac can use Sparkle and Android can check in Settings & Help. Android still shows its system installer, and Mac remains ad-hoc signed and not notarized.
Why does macOS warn about the app?+
The Preview is ad-hoc signed and not notarized because this release does not use a paid Developer ID. Inspect the source and checksum, then follow the documented Gatekeeper steps only if you trust the package.
Can I install the IPA directly?+
No. It is deliberately an unsigned re-signing input. A user must provide their own valid signing identity; third-party signing services carry their own security and legal risks.
Will Android reconnect after returning from the desktop?+
Yes on the validated path. The receiver restarts idempotently when its surface returns, and the Mac resends stream configuration before requesting a keyframe.
Is Android USB faster than WiFi?+
It avoids LAN variability, but the controlled same-condition benchmark remains pending. The published benchmark document defines how to compare them without inventing numbers.
