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.
Automatic Mac desktop matching estimates size from available displays. Existing settings are preserved; native 5K video is not supported and two-Mac hardware acceptance remains unverified. Android and macOS verify updates before installation.
Drag DisplayWeave into Applications; later releases use EdDSA-authenticated Sparkle updates. Signed with a fixed Apple Development identity, not notarized; the first upgrade from an ad-hoc version may need permission grants again.
DisplayWeave-macOS.dmgInstall over the existing app once. Later downloads are checked by size, hash, package, version, SDK, and pinned signing certificate before system confirmation.
DisplayWeave-Android.apkNot directly installable. You must lawfully sign it with your own Apple identity before device installation.
DisplayWeave-iOS-unsigned-resigning-input.ipaVerified means exercised on available physical hardware. Experimental means implemented with hardware-dependent performance. Deferred work is stated plainly.
HEVC/120 and H.264/60 over wired ADB forward; unplug/replug, ADB restart, authorization revoke/reallow, foreground return, and Auto fallback recovery verified.
Prior Preview 2 evidence covers tap, drag, cursor, two-finger scroll, and one iPhone WiFi receiver running beside one Android receiver; this physical matrix was not rerun for this release.
Release APK v2 signature, certificate identity, first install, and upgrade install verified without a Google developer account.
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.
30/60/90/120fps negotiation with HEVC and H.264 fallback. A prior OnePlus WiFi HEVC/120 run measured about 109–111 rendered FPS; stable 120 FPS is not guaranteed.
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.
The Mac sender relies on CGVirtualDisplay. Future macOS versions may change private behavior.
Two simultaneous Android devices, controlled same-condition USB/WiFi benchmark, and 30-minute/2-hour endurance runs are not complete.
One install identity anchors the handover, so a wireless-debugging endpoint cannot masquerade as a second USB device.
Only a device row with wired USB metadata is eligible.
Each serial receives its own Mac-local TCP port to Android :9000.
Protocol grace and bounded 0.5/1/2/4/8 second retries avoid hot loops.
Auto uses WiFi only for the same Android app installation.
Cable return atomically ends WiFi before wired reconnection.
Historical OnePlus HEVC/120 WiFi run; a device-specific result, not a guarantee.
Observed after socket reset, protocol grace, and the full bounded recovery sequence.
Prior Preview 2 evidence: iPhone over WiFi and Android through an independent session at the same time.
Video streams outward while touch, drag, cursor, and two-finger scroll return to macOS.
DisplayWeave does not require an account or project-operated cloud relay. That does not make every transport production-secure yet.
Apple and Android default to certificate-pinned mutual TLS. Pair current devices with an invitation, or select main-screen OpenDisplay compatibility. Explicit legacy compatibility is unencrypted and requires a trusted network.
Android USB debugging authorizes the Mac as a debugging host, not only DisplayWeave.
DisplayWeave is GPL-3.0 software derived from OpenDisplay, with SideScreen technical-reference notices retained.
Yes. Enable installation from the source you use to open the APK, then verify its SHA-256 and project certificate fingerprint before installing.
Mac uses signed Sparkle updates; Android can check in Settings & Help and requires system installation confirmation. Metadata is hosted on GitHub Pages and packages on GitHub Releases. Older apps without this update channel need one manual installation.
This release uses Apple Development signing to keep its identity consistent across upgrades. It is not Developer ID signed or notarized, so macOS may still require approval. Verify the checksum and follow the documented first-install steps.
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.
Yes on the validated path. The receiver restarts idempotently when its surface returns, and the Mac resends stream configuration before requesting a keyframe.
It avoids LAN variability, but the controlled same-condition benchmark remains pending. The published benchmark document defines how to compare them without inventing numbers.