This page arrived over plain http. Browsers refuse the
camera, microphone, motion sensors, compass, location, battery and the
fingerprint prompt on any address that isn't secure — and they hide the phone's
model too. Nothing is wrong with the device. Three ways out, fastest first:
Prove it works, on a shop test phone, in two minutes. In Chrome open
chrome://flags/#unsafely-treat-insecure-origin-as-secure, paste
this page's origin into the box, set it to Enabled and
relaunch Chrome. Every test below comes alive. A shop device only — never
ask a customer to do this, and turn it back off afterwards.
Give the bench a certificate. The real fix, and it's a one-time job:
Let's Encrypt over DNS-01, no ports opened, renews itself.
webtest/README.md has the whole recipe. Note a
.local name can never get a public certificate — the bench needs a
real hostname like bench.yourdomain.com pointed at its LAN address.
Serve the page from a site you already run. Any https host works; the
results come back by the result QR at the end instead of posting to the bench.
Identifying…
reading the browser
POINT THE PHONE HERE
What this browser will let us touch
Run
Works best added to the home screen — the browser's own top and bottom bars sit over roughly 15% of the panel, so a tab can never sweep the true screen edges.
Out of reach from any browser
Test queue
Finish
Verdict
—
Findings
Hand-off
Hand the result to the bench: hold the QR up to its scanner, or copy the JSON and paste it into the Device tests page. When this page is served by the bench itself it posts straight through.