OpenXPlay Relay for Android 0.2.4

Android 0.2.4 — smoother app screens, a Home button that answers the first tap, hotspot details to copy into the phone's settings, and a Bluetooth fix for MIUI on Android 12 · Android 0.2.4 — 应用界面更流畅、首页按钮第一次轻触就响应、热点名称和密码可复制到系统设置、修复 Android 12 MIUI 手机的蓝牙连接

New

• Settings > Network, when the iPhone connects through this phone's hotspot, offers two ways to set it up. Copy to settings (recommended) suggests a name (OpenXPlay-A-…) and a 16-character password; each button copies one of them and opens the phone's hotspot settings. Use my existing hotspot keeps a hotspot you set up yourself: enter its name and password here. The setup guide offers the same choice, and hotspot details you already saved stay as they are.

Changes

• Smoother app screens. The figures below were measured on a Redmi 14C (HyperOS) with Home open and no car connected; other phones will differ.
• While the relay looks for the car, Record all Bluetooth advertisements (Experimental) no longer works on the thread that draws the screens. That thread's idle CPU time drops from 64–119 ms to 25–27 ms per second, 60–77% less.
• The button on Home acts on the first tap. Before, a tap within 0.5 s of the button appearing, for example right after returning from Settings, was ignored; now 4 of 4 such taps act.
• Until the car's Carlink session is ready, the two Carlink output threads wake every 50 ms instead of every 5 ms and use 5 ms of CPU per second each instead of 24–27, about 80% less.
• The app's own screens are compiled ahead of time when it is installed, so pages open a little faster the first few times: the longest frame when opening Settings is 80–96 ms instead of 99.6 ms.
• In total, the idle app uses 220–234 ms of CPU per second instead of 245–336, 10–30% less.
• Bluetooth: the app keeps Android's older Bluetooth permissions on Android 12 and later. Some MIUI phones on Android 12 still check them when the iPhone connects over Bluetooth, and the connection failed straight away.

Notes

• Known issue: opening Settings still holds one frame for 80–96 ms (about five frames at 60 fps) before the page slides in.
• The Bluetooth fix has not yet been checked on the phone that showed the problem (Redmi K30 Pro, Android 12).

新增

• 「设置 > 网络」：iPhone 通过这台手机的热点连接时，热点有两种设置方式。「复制到系统（推荐）」给出建议的名称（OpenXPlay-A-…）和 16 位密码，每个按钮复制其中一项并打开手机的热点设置；「填写已有热点」保留你自己设置的热点，在这里填写它的名称和密码。设置向导提供同样的选择，已保存的热点名称和密码保持不变。

变更

• 应用界面更流畅。以下数字在 Redmi 14C（HyperOS）上停在首页、未连接车机时测得，其他手机会有差异。
• 寻找车机时，「记录所有蓝牙广播」（实验功能）不再占用绘制界面的线程。这个线程空闲时的 CPU 占用从每秒 64–119 ms 降到 25–27 ms，减少 60–77%。
• 首页的按钮第一次轻触就响应。以前按钮出现后 0.5 秒内的轻触会被忽略（例如刚从设置返回时）；现在这样的轻触 4 次全部生效。
• 车机的 Carlink 会话就绪之前，两个 Carlink 输出线程每 50 ms 醒一次，不再是每 5 ms；每个线程每秒占用的 CPU 从 24–27 ms 降到 5 ms，减少约 80%。
• 应用自己的界面在安装时预先编译，头几次打开页面稍快：打开设置时最长的一帧从 99.6 ms 降到 80–96 ms。
• 应用空闲时总的 CPU 占用从每秒 245–336 ms 降到 220–234 ms，减少 10–30%。
• 蓝牙：在 Android 12 及以上版本也保留旧版蓝牙权限。部分 Android 12 的 MIUI 手机在 iPhone 通过蓝牙连接时仍会检查这些权限，以前连接会立即失败。

说明

• 已知问题：打开设置时仍会停顿一帧，约 80–96 ms（60 fps 下约 5 帧），之后页面才滑入。
• 蓝牙权限的修复还没有在出问题的手机（Redmi K30 Pro，Android 12）上验证。

---

Built from OpenXPlay-Relay@e711695c603f, OpenXPlay-Stream@bf1959648578 and OpenXPlay-DiPlay@37833a068c87.

• openxplay-relay-0.2.4.apk: the Android app. Signing certificate SHA-256: fca7b492d0feb3a8401eba8dec5b71766415ea6154aed36c9d1838c4c6a186db
• openxplay-relay.apk: the same app under a fixed name, for the latest-download link.
• SHA256SUMS: SHA-256 checksums of these files.

Setup: https://openxplay.org/en/quick-start · 设置：https://openxplay.org/quick-start. No build contains an Apple accessory (MFi) identity; supply your own.