v0.1.0-preview.2LOCAL DISPLAY FABRIC

Weave everyspare screeninto yourMac workspace.

DisplayWeave turns iPhone, iPad, and Android devices into local extended displays—with Apple USB/WiFi, Android ADB USB, automatic WiFi fallback, touch input, HEVC, and experimental high refresh.

macOS 14+iOS / iPadOS 17+Android 8+GPL-3.0
Live transport map
ACTIVE
SOURCE 00Mac senderCapture · Encode
USB 01Android receiverADB USB
LAN 02Apple receiverLocal WiFi
AUTO FALLBACKUSB ↔ WIFI

Choose the sender and receiver you need.

Every package is distributed directly from GitHub. Read the signing boundary before installing.

01
SendermacOS

Mac sender preview

Universal ad-hoc signed app. It is not Developer ID signed or notarized; Gatekeeper approval may be required.

DisplayWeave-Preview-0.1-macOS.zip
Download macOS ZIP
02
ReceiverAndroid

Offline signed APK

Installable outside Google Play. Signed with the project Preview key and verified with APK Signature Scheme v2.

DisplayWeave-Preview-0.1-Android.apk
Download Android APK
03
Receiver inputiOS / iPadOS

Unsigned re-signing input

Not directly installable. You must lawfully sign it with your own Apple identity before device installation.

DisplayWeave-Preview-0.1-iOS-unsigned-resigning-input.ipa
Download re-signing input
v0.1.0-preview.2Development preview — no App Store, Google Play, Developer ID notarization, or universal iOS signing.Verify all downloads with SHA256SUMS.txt

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

Tap, drag, cursor and two-finger scroll return to macOS. One current iPhone WiFi receiver and one Android receiver ran concurrently.

Offline Android distribution

Release APK v2 signature, certificate identity, first install, and upgrade install verified without a Google developer account.

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.

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.

  1. 01

    Discover wired ADB

    Only a device row with wired USB metadata is eligible.

  2. 02

    Forward a dynamic port

    Each serial receives its own Mac-local TCP port to Android :9000.

  3. 03

    Recover with limits

    Protocol grace and bounded 0.5/1/2/4/8 second retries avoid hot loops.

  4. 04

    Fall back by install ID

    Auto uses WiFi only for the same Android app installation.

  5. 05

    Upgrade back to USB

    Cable return atomically ends WiFi before wired reconnection.

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

Current 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.

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.

01

Trusted LAN only

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.

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.

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.