Find your way
back to the signal.

Phone cannot pair

Confirm the companion is open and both devices can reach each other on the same trusted local network. Check local-network permissions. Guest/client isolation can block discovery and WebRTC. Scan a fresh code; old pairing codes expire.

Connected, but no picture

Approve capture on the phone. Reopen the companion after an interrupted broadcast. Protected media and secure screens can intentionally appear black.

Movement is wrong

Hold the phone comfortably and calibrate. Re-zero resets heading. Increase smoothing carefully if motion jitters; set movement to 0% if you want a still device.

OBS output is blank

Keep the receiver running on the same computer. Copy a fresh Browser Source URL and check its dimensions. Regenerating the output token invalidates old URLs. For the native plugin, check the OBS version and obs-browser module.

Camera preview unavailable

Choose Add camera and allow camera access for FoneStream in your browser or system privacy settings. Check that the camera is connected and available, then use the camera selector or try again. Some cameras cannot be opened by two applications at once. This local reference is separate from your phone capture and output.

Recording unavailable

Use the desktop app; native MP4 recording requires a compatible H.264 MediaRecorder. Finish capture with Stop & save, then choose a writable destination.

Lost connection or revoked trust

Restore local reachability and reopen capture. A revoked phone must pair again. Diagnostics shows capture state, frame rate, latency and dropped frames.

Report a problem

Check the project issue tracker. Include OS, app version, phone model, reproduction steps and redacted diagnostic details. Exclude pairing codes, tokens and private screen content. Security concerns should follow the security policy.