Record successful authorized real-device ADB smoke test

This commit is contained in:
tongtong committed 2026-11-12 12:38:25 +08:00
1 parent e1c152a657
commit 82adce545d
1 file changed
+4 -2
+4 -2
View File
@@ -14,8 +14,10 @@ Read-only real-device smoke test:
- Remote ADB Server `192.168.5.222:5037` listed `192.168.100.141:5555` as online.
- Started a temporary relay and both Rust daemons, with the gateway using the existing remote ADB transport.
- Local `adb connect` reached the phone through the new three-program path, but Android returned `unauthorized` for the local computer's key.
- Consequently, real `adb shell`, app installation, Android Studio and scrcpy have not been verified through the new path. Approve the local key on the phone, then rerun `tests/real_device.py`.
- Initial attempt reached the phone but returned `unauthorized`. After the user approved the local computer's key, the same test was rerun successfully.
- Ordinary local `adb devices -l` listed `127.0.0.1:51847` as `device`, with product `aosp_crosshatch` and model `AOSP_on_crosshatch`.
- Remote `adb shell getprop ro.product.model` returned `AOSP on crosshatch`; the read-only shell echo marker also matched. All three release programs were involved in the successful test.
- App installation, Android Studio and scrcpy have not yet been exercised through the new path.
- Temporary processes and local ADB endpoint were disconnected after the test; unrelated local ADB devices were preserved.
No public server was deployed. Production WSS certificates, real Internet latency, and Linux/macOS runtime behavior still need deployment-environment validation. The Linux Go server is cross-built separately; cross-building is not a Linux runtime test.