Troubleshooting

Find what you see, then follow the fix. The messages in quotes are the exact words the app or the computer shows.

Wi-Fi: the device can’t find or reach the computer

The app lists no computers, or says it can’t find yours

Cause: the device and the computer are on different networks (a guest network, a second router, mobile data), PixelBridge isn’t running on the computer, or the network stops devices seeing each other (some guest, hotel and office networks).

Fix: put both on the same Wi-Fi and check that PixelBridge is running (tray icon on Windows, menu bar icon on a Mac). If the network still hides the computer, tap Scan code to connect and scan the code from the computer, or use the cable.

“Your computer didn’t answer over Wi-Fi” with a Windows PC

Cause: Windows treats the network as Public, and its firewall drops incoming connections there. PixelBridge shows “Wi-Fi blocked: this network is Public — fix it…” in the tray.

Fix: click that tray item and choose Make it private (Windows asks for administrator permission). On a public network such as a café’s, use the cable instead. Details: Connecting over Wi-Fi.

Windows: the Pair over Wi-Fi window says “Listener unavailable (port in use?)”

Cause: Wi-Fi connections are turned off in PixelBridge (the current default on Windows), or another program is using the port.

Fix: tray › Settings… › Connection › turn on Allow connections over Wi-Fi, then restart PixelBridge. If it’s still unavailable, change Wi-Fi port there.

A Mac isn’t answering over Wi-Fi

Fix: if the macOS firewall is on, allow incoming connections for PixelBridge in System Settings › Network › Firewall. When macOS asks whether PixelBridge may find devices on your local network, allow it.

“That computer has a new connection code. Scan the code it shows again.”

Cause: the one-time key in the code changed, for example because PixelBridge restarted on the computer. Fix: show the code again (Pair wireless… / Show connection QR…) and scan it.

“That computer no longer recognizes this device. Pair it again there.”

Cause: the computer forgot this device: someone chose Forget, or on Windows you’re signed in as a different user. Fix: pair again. See Pairing.

USB: nothing happens when you plug in

The device charges but never connects to a Windows PC

Cause: the device’s USB mode is charge only, so the PC has nothing to connect to. Fix: pull down the USB notification on the device and choose File transfer.

“This cable may be charge-only. Try a different USB cable.”

Fix: use a cable that carries data, such as the one that came with the device.

Android asks “Open PixelBridge?” every time

Fix: tick Always open in that dialog once.

My phone disappeared from File Explorer

Cause: while PixelBridge runs on Windows, it uses a plugged-in phone’s file-transfer connection as the display link. Fix: quit PixelBridge from the tray and file transfer comes back.

Mac: permissions

The device connects but stays black, or the Setup assistant keeps coming back

Cause: Screen & System Audio Recording isn’t allowed, or macOS removed the permission. Fix: menu bar › Setup Assistant… › Allow…, switch PixelBridge on in System Settings, then click Already allowed it? Relaunch PixelBridge.

Touch and the pen don’t move the pointer

Fix: allow Accessibility: menu bar › Setup Assistant… › Accessibility › Allow….

macOS asks again whether PixelBridge may keep recording the screen

That’s macOS re-checking, about once a month. Allow it.

Picture and performance

“Connected — laggy”

Use the cable, set Settings › Display › Resolution to Auto, or close busy apps on the computer. On a Mac, turn off AirDrop and Handoff while you work.

The picture looks soft or low-resolution on a Windows PC with AMD graphics

Cause: PixelBridge encodes in hardware on NVIDIA and Intel graphics. On AMD graphics it uses a software encoder, which limits the picture to about 720p and uses more processor time. Fix: none yet; it’s a known limit.

“The picture froze… asking your computer for a fresh frame”

It recovers by itself. If it keeps happening, restart PixelBridge on the computer.

“Connected — your computer is struggling”

The computer’s encoder is overloaded, often by several displays at once. Disconnect other devices or close other virtual displays.

“Your computer is sending a picture larger than this device can play”

Another connected device made the shared display bigger. Disconnect the other device and try again.

“Connected to your computer, but its display driver isn’t running. Waiting for it to come back…”

The session is held, not dropped. Wait; it resumes by itself when the driver returns.

Pen

No pen pressure in Krita on Windows

Cause: Krita was open before the device connected, or Pen in Krita and other Qt apps is off. Fix: connect first, then restart Krita. Check the tray item is ticked; if it reads “(… took it back)”, click it to turn it back on.

Settings and power

A setting I changed did nothing

Most settings apply on the next connection: use tray › Reconnect. Connection and pairing settings need a restart of PixelBridge; the Settings window says so.

The PC went to sleep during a session

Turn on Keep this PC awake while serving (Settings › Advanced; on by default).

The PC’s screen locked during a session

That’s on purpose: Keep this PC’s screen awake too is off by default so an unattended PC still locks. Turn it on only if you need it.

The Windows Settings window opens a text file instead

The Microsoft Edge WebView2 runtime is missing. Run PixelBridge setup again; it installs WebView2.

“PixelBridge on your computer and on this device are different versions”

Update both: the app from Google Play, the computer program from the download page.

Still stuck?

Write to support@bytehavenstudios.com and a person will answer. On a Mac, attach the host log (Settings › Advanced › Open log).