xrscreen

Documentation

Overview

Command xrscreen paints frames from Go onto the glasses and says how many of them Android took.

It is the OUTPUT half of this package, and the only one that cannot be proved from a cable. cmd/xrwide and cmd/xrwall read back what Android rendered and sample the pixels; there is nothing to read back here, because an ordinary application may not capture a display it does not own. The glasses are the only instrument, and the person wearing them is the only witness.

APP=./cmd/xrscreen host/build.sh && adb install -r host/out/xrhost.apk
adb shell am start -n org.goxrkit.androidhost/org.goxrkit.android.XrDemoActivity --ez capture false
adb logcat -d -s xrcapture xr-wall
adb shell run-as org.goxrkit.androidhost cat files/screen.txt

⛔ AN ACKNOWLEDGEMENT IS NOT LIGHT. Every frame this reports was copied into the host's bitmap and handed to the view — that is what the count means, and it is worth having, because it separates "the mechanism works" from "the mechanism runs and shows black", which is this whole feature's silent failure. It does NOT say a photon left the panel. What is drawn is therefore deliberately unmistakable — flat quadrants of known colour and a bar that sweeps — so that ONE GLANCE through the glasses settles the rest.

⚠ THE BAR IS NOT DECORATION. Colour alone refutes a black panel. The bar refutes a screen FROZEN ON ITS FIRST FRAME, which is what a host that showed one bitmap and then stopped copying looks like: 3600 acknowledgements and one picture. The two failures need two different things to look at, so a witness has to be asked about both — and on the Pixel 11 Pro Fold with VITURE Beast glasses, both were reported: colour, and movement.