Skip to content

Latest commit

 

History

History
120 lines (69 loc) · 17.5 KB

COMPATIBILITY.md

File metadata and controls

120 lines (69 loc) · 17.5 KB

🧭 Compatibility / 兼容性

English · 简体中文

English

Support targets and observed tests are separate. Passing an emulator test does not establish support for every OS version, ARM phone, vendor derivative or VR viewer.

Targets

Component Target and requirements Evidence / limits
Windows host Windows 10 / 11 x64; Microsoft Visual C++ v14 x64 runtime Local physical machine runs Windows 11 build 26200. Windows 10 has not been physically tested.
Android client Android 6.0 / API 23 or later, OpenGL ES 2.0, APK-compatible system Java application with no bundled ABI-specific native library. v0.2.0, v0.3.0 and v0.3.2 were installed and streamed over USB on a physical HUAWEI Pura 70 Ultra reporting Android 12 / API 31 compatibility; other derivatives require device testing.
iOS client iOS / iPadOS 15+, landscape, Metal, local-network permission Native Swift / UIKit client. Xcode on macOS builds and signs it; the Windows host serves both phone platforms. See iOS guide for exact installation / test limits.
Google services Not required First-release API 23 emulator uses no Google services.
Full screen Network and graphics support No rotation sensor required; verified on the sensor-less API 23 emulator.
Cinema tracking / gyro control in both first-person modes Compatible Android rotation sensor or iOS Core Motion Enhanced viewing itself can render without a sensor; real gyro axes, drift and headset tracking still need a physical phone.
First-person mouse input Desktop/apps/games accept ordinary relative mouse input; enabled PC gyro preference, validated poses and F8/Resume Real FPS games and anti-cheat / raw-input combinations remain unverified.

Enhanced mode compatibility (v0.4.0)

Enhanced viewing uses the existing Android GLES 2.0/iOS Metal requirements and can render without a rotation sensor; mouse input still needs valid rotation data. Every eye stays physically square irrespective of JPEG or viewport aspect. Keep both current clients/host updated for negotiated fps_enhanced; new-host/old-phone and new-phone/old-host paths fall back to ordinary fps on the wire, with new phones retaining local enhanced presentation. Windows/Android software/build/signature checks and iOS native Simulator tests/pixels passed; Android graphics instrumentation was only compiled. Huawei/PCVR hardware testing is explicitly deferred; no old result proves this mode's physical rendering or input. See Validation and the mode guide.

Interface language

All applications offer English / 简体中文; English is the default and the choice is saved locally. The PC stores language in language.json independently of preferences.json. Changing the PC language keeps streaming active and retains the input preference/pause latch. Changing the phone language disconnects the stream and requires reconnecting (Android recreates its Activity; iOS rebuilds its controls). Language choice is independent on each device.

What has actually been checked

The first release and final v0.1.1 APK were installed and streamed on a Google-free Android 6.0 / API 23 emulator. The same-signer upgrade retained settings; English remained the default even on a Chinese system, and both language choices persisted after restart. Both-eye rendering, hidden controls / Back recovery, boundary sliders, no-sensor cinema / FPS fallback, background disconnect and explicit reconnect passed. One transient EGL_BAD_SURFACE occurred during old language-popup recreation; subsequent rendering was normal. See the exact observation in validation.

A physical ASUS portrait display was captured from Windows 11; 2160 × 3840 became 720 × 1280 at longest-edge limit 1280. The desktop language controls were tested on the actual ASUS display: English default, Chinese selection, persistence after reopen, switching during streaming, and scrolling at 1060 × 680.

The final v0.1.1 APK also upgraded the Google-free Android 16 / API 36 AOSP emulator from v0.1.0, started with English UI, retained Chinese after force-stop / reopen, and switched back to English. It received the original 1280 × 720 card over a real WebSocket and rendered both eyes. Host-selected cinema / First-person modes remained selected; sensor-service Game Rotation Vector registration and full-screen unregistration were observed. Hidden controls / Back recovery, disconnecting on background, and explicit reconnection after language changes, background or server close 1001 passed. No AndroidRuntime / OpenGLRenderer / libEGL errors were observed. These are emulator observations, not physical-gyro, real-game or latency tests. See validation.

v0.2.0 physical Android USB check

A HUAWEI Pura 70 Ultra reporting Android 12 / API 31 compatibility upgraded in place from the previous local APK to v0.2.0 (code 3). English and USB were the defaults. Authorized USB host discovery, automatic connection on a fresh launch, reception of the original 960 × 540 calibration stream and both-eye rendering passed. The phone transmitted rotation poses in First-person mode; the test used a fake input sink, with no operating-system mouse output. Chinese persisted after force-stop / reopen, and switching language disconnected the stream as designed. This does not establish its marketing OS version, every Huawei model, gyro axes or headset comfort. See the complete validation record.

USB support requires official Platform Tools / Android debugging authorization, or Apple's Windows device software / Trust for iOS. Neither driver stack is bundled. The iOS relay is tested with simulated USB devices; there is no real-iPhone USB result. See USB prerequisites.

The original Windows DXGI / D3D11 capture backend uses system DLLs, with GPU crop / rotation / resize before small pixel readback. On the ASUS portrait desktop, the default 640 / 60 / Q45 USB stream reached 57.7–59.9 decoded FPS on this Huawei phone. The stable and quality preset readings were 30.2 and 30.0 FPS. Initial unsupported GPU selections retain exact-region GDI / MSS fallback; layout or access changes stop the session. Other GPUs and Windows 10 hardware remain untested. See performance.

Still unverified

Other Android phones / derivatives, physical iPhones / iPads including the oldest target iOS 15, actual viewer optics, gyro-axis accuracy / drift / comfort, real FPS games, Windows 10 hardware and measured end-to-end video latency. Windows ARM64 / x86 native builds are not supplied. Please submit device results with version, settings and measurement method through contributing.

v0.3 editor / preferences scope

Targets are unchanged. The new flat editor, shared geometry with dynamic seam limits, Save / Discard, explicit reset and committed phone profile restoration are documented in editing. The message envelope remains v1, but negative eye separation requires v0.3 on both sides; v0.2 only accepts 0…0.2. Existing nonnegative profiles remain valid. v0.3 phones restore saved profiles only after a valid hello. Historical results remain evidence for their named versions. The final v0.3 APK passed physical Huawei editor / mirrored-direction / small-image contact, Save / Discard, PC ↔ phone persistence, restart, language and reset checks, plus 14 real UI checks on an API 23 emulator. PC consumer / commit handlers were exercised headlessly, not by actual new Windows GUI interactions. Final CI passed 65 Swift core tests / three native Simulator UI cases, both SDK builds and LAN / simulated-USB signed-seam checks; physical iPhone USB and headset optics remain unverified. See exact validation.

v0.3.2 compatibility scope

The new First-person stabilization setting defaults to 0, preserving previous behavior. Full ten-field profiles migrate to eleven fields with stabilization 0; current clients negotiate settings schema 2 inside protocol v1 and omit the new network field for legacy hosts while retaining its local value. A newer host is needed for stabilization to take effect. Windows / Android / iOS targets above are unchanged.

On the physical Huawei, the v0.3.2 slider synchronized 50% to the host; a 65% host update persisted on the phone, survived restart and restored to the host. The previous committed profile was retained and OS mouse moves stayed zero. A custom GLES runner on the phone passed 288 offscreen mask cases across both eyes, not headset-optics checks. Phone-first USB connection succeeded when the host started 6.08 seconds later, at 7.67 seconds from phone startup.

The final packaged Windows EXE found one authorized physical device using a separately installed portable SDK with SDK variables cleared and fresh preferences; diagnostics completed without errors. SDK lookup and ADB / phone-authorization availability are separate: shared debugging-session / authorization drops were also observed, and the original historical faults are not all attributed to MSIX storage. Windows / Android / iOS / documentation CI jobs passed; iOS passed 77 Swift core tests / five genuine UI cases and both SDK builds on an arm64 iOS 26.2 Simulator. Both-eye LAN / simulated-USB color / row checks and exact seam-boundary checks passed; there is still no real-iPhone USB result. Earlier results retain their original version scope. See current release status, validation and stabilization.


简体中文

支持目标与已经观察到的测试结果分开记录。模拟器通过不代表全部系统版本、ARM 手机、厂商衍生系统与 VR 盒子都兼容。

支持目标

部分 目标与要求 已有证据 / 限制
Windows 电脑端 Windows 10 / 11 x64;Microsoft Visual C++ v14 x64 运行库 本机实际运行 Windows 11 build 26200;未在 Windows 10 实机测试。
Android 手机端 Android 6.0 / API 23+、OpenGL ES 2.0、可安装 APK 的兼容系统 Java 应用,不附带 ABI 专用原生库。v0.2.0、v0.3.0 与 v0.3.2 已在报告 Android 12 / API 31 兼容层的 HUAWEI Pura 70 Ultra 真机安装并经 USB 串流;其他衍生系统需分别实测。
iOS 手机端 iOS / iPadOS 15+、横屏、Metal、本地网络权限 原生 Swift / UIKit 客户端,macOS 用 Xcode 构建和签名;Windows 主机同时服务两类手机。安装与实测边界见 iOS 教程。
Google 服务 不需要 首版 API 23 模拟器不含 Google 服务。
全屏模式 网络与图形支持 无需旋转传感器,已在无传感器 API 23 模拟器检查。
大屏幕追踪/两种第一人称陀螺仪控制 兼容 Android 旋转传感器或 iOS Core Motion 加强观看本身无传感器仍可显示,真实轴向、漂移与头部追踪仍需手机实测。
第一人称鼠标输入 桌面/应用/游戏接受普通相对鼠标;电脑启用偏好、合法姿态与 F8/恢复 真实 FPS、反作弊与原始输入组合尚未验证。

加强模式兼容性(v0.4.0)

加强观看沿用 Android GLES 2.0/iOS Metal 要求,无旋转传感器仍可渲染,鼠标仍需合法旋转数据;不论 JPEG/视口比例,每眼物理上均为正方形。当前手机/电脑更新后协商 fps_enhanced,新电脑/旧手机与新手机/旧电脑线上回退普通 fps,新手机保留本地加强显示。Windows/Android 软件/构建/签名及 iOS 原生模拟器测试/像素通过,Android 图形 instrumentation 仅编译;华为/PCVR 真机明确留待下次,旧结果不证明本模式实际渲染或输入,见 验证 与 模式教程。

界面语言

所有客户端可选 English / 简体中文,默认英文,分别在本地保存。电脑语言存于 language.json,独立于 preferences.json。电脑切换语言保持串流和输入偏好/暂停锁;手机切换语言断开串流,需要重新连接(Android 重建 Activity,iOS 重建控件)。各设备语言独立选择。

实际检查范围

首版与最终 v0.1.1 APK 均在无 Google 的 Android 6.0 / API 23 模拟器安装并串流。同签名升级保留设置,系统中文时仍默认英文,两种语言重开均保留。双眼显示、隐藏 / 返回恢复、边界滑块、无传感器大屏幕 / FPS 回退、后台断开与显式重连通过。旧语言弹窗重建期间有一次临时 EGL_BAD_SURFACE,随后渲染正常,具体见 验证记录。

Windows 11 采集真实 ASUS 竖屏,2160 × 3840 在最长边 1280 时输出 720 × 1280。电脑语言界面已在真实 ASUS 显示器检查默认英文、切换中文、重开后保留、串流中切换及 1060 × 680 小窗滚动。

最终 v0.1.1 APK 已在无 Google 的 Android 16 / API 36 AOSP 模拟器从 v0.1.0 升级,默认英文,切中文后强制停止再开仍保留中文,可切回英文。真实 WebSocket 接收 1280 × 720 原创卡并显示双眼画面。电脑切大屏幕 / FPS 后客户端保留对应模式,传感器服务注册 Game Rotation Vector、全屏时注销;隐藏 / 返回恢复、后台断开,以及语言切换 / 后台 / 服务端 1001 关闭后的显式重连均通过。未观察到 AndroidRuntime / OpenGLRenderer / libEGL 错误。这些是模拟器观察,不是实机陀螺仪、真实游戏或延迟测试。详见 验证记录。

v0.2.0 Android 真机 USB 检查

报告 Android 12 / API 31 兼容层的 HUAWEI Pura 70 Ultra 从此前本地 APK 覆盖升级到 v0.2.0(code 3)。默认英文和 USB,授权后的 USB 服务发现、新启动自动连接、960 × 540 原创校准串流接收与双眼渲染通过。第一人称模式手机可发送旋转姿态;测试使用假输入接收器,没有操作系统鼠标输出。中文在强制停止 / 重开后保留,切换语言按设计断开串流。这不推断其营销系统版本,也不代表全部华为型号、陀螺仪轴向或盒子舒适度。详见 完整验证记录。

USB 需要官方 Platform Tools / Android 调试授权,或 iOS 的 Apple Windows 设备软件 / 信任,均不在包内附带。iOS 中继通过模拟 USB 设备测试,尚无 iPhone 真机 USB 结果。详见 USB 前提。

原创 Windows DXGI / D3D11 后端使用系统 DLL,先在 GPU 选区 / 旋转 / 缩放,再读回小画面。ASUS 竖屏桌面的默认 640 / 60 / Q45 USB 串流,在此华为手机达到 57.7–59.9 解码 FPS,稳定与画质预设分别为 30.2、30.0 FPS。GPU 首次不支持时保留相同选区的 GDI / MSS 回退;布局或访问变化会停止会话。其他 GPU 与 Windows 10 硬件尚未实测,见 性能说明。

仍未验证

其他 Android 手机 / 衍生系统、真实 iPhone / iPad(包括最低目标 iOS 15)、真实盒子镜片、陀螺仪轴向 / 漂移 / 舒适度、真实 FPS 游戏、Windows 10 硬件及端到端视频延迟测量。未提供 Windows ARM64 / x86 原生构建。欢迎按 贡献说明 提交版本、设置与测量方法完整的设备结果。

v0.3 编辑器 / 偏好范围

支持目标不变。新增平面编辑器、带动态接缝限位的共用几何、保存 / 放弃、主动重置与手机已提交配置恢复见 编辑文档。消息封装仍为 v1,但负间距需两端均为 v0.3,v0.2 只接受 0…0.2;已有非负配置仍有效。v0.3 手机只在合法 hello 后恢复保存配置。历史结果只证明注明版本。最终 v0.3 APK 已通过华为真机编辑 / 镜像方向 / 小画面接缝、保存 / 放弃、电脑 ↔ 手机持久化、重启、语言和重置检查,以及 API 23 模拟器 14 项真实界面检查。电脑接收 / 提交处理器为无界面调用,不是新 Windows 界面真实交互。最终 iOS CI 通过 65 项 Swift 核心 / 三项原生模拟器界面、两种 SDK 构建及局域网 / 模拟 USB 有符号接缝检查,真实 iPhone USB 和盒子镜片仍未验证;见 精确验证范围。

v0.3.2 兼容范围

新增第一人称防抖默认 0,保留此前行为。十字段完整配置迁移为十一字段时添加防抖零值;当前客户端在协议 v1 内协商配置 schema 2,面对旧主机只从网络去掉新字段,本地值保留。防抖生效需新版电脑端,上表 Windows / Android / iOS 目标不变。

华为真机 v0.3.2 滑块 50% 同步主机;主机更新 65% 后手机保存,重启保留并恢复到主机。此前已提交配置保留,操作系统鼠标移动为零。手机自定义 GLES 检查通过双眼共 288 项离屏遮罩用例,不是盒子镜片检查。手机先启动,主机 6.08 秒后启动,手机启动后 7.67 秒连接成功。

最终打包 Windows EXE 在清空 SDK 变量、使用新偏好时,通过另行安装的便携 SDK 发现一台已授权真实设备,诊断完成且无错误。SDK 查找与 ADB / 手机授权可用性属于不同问题:另观察到共享调试会话 / 授权掉线,不把全部历史故障归因于 MSIX 存储。Windows / Android / iOS / 文档 CI 任务通过;iOS 在 arm64 iOS 26.2 模拟器通过 77 项 Swift 核心 / 五项真实界面用例与两种 SDK 构建,双眼局域网 / 模拟 USB 的颜色 / 行方向及准确接缝边界检查通过;仍无 iPhone 真机 USB 结果。较早结果保留对应版本范围,见 当前发布状态、验证记录 与 防抖说明。