HyperConnect Toolkit v1.6.0

Fixed

• Restored fresh phone discovery after MiLink data is cleared by installing the
  LyraDiscover compatibility hooks in their actual owner process,
  com.milink.service:ui.

Changed

• Split device discovery and notification-click circulation into independent,
  exact-process Hook groups.
• Cross-device notification status is reported as applied only after both process components have
  installed successfully.

HyperConnect Toolkit v1.6.0-diagnostic.2

Fixed

• Restored fresh notification-device discovery after MiLink data is cleared by installing the
  LyraDiscover compatibility hooks in their actual owner process, com.milink.service:ui.

Changed

• Split device discovery and notification-click circulation into independent, exact-process Hook
  groups instead of resolving both contracts in com.milink.crossdeviceservice.
• Cross-device notification status is now reported as applied only after both process components
  have installed successfully.

HyperConnect Toolkit v1.6.0-diagnostic.1

这是专门用于排查“小米平板强开跨设备通知后仍搜不到手机”的诊断预发布版，不是正式更新。

测试步骤

1. 直接覆盖安装 APK，不要卸载正式版，以保留 LSPosed 作用域与功能设置。
2. 在 LSPosed 确认 HyperConnect Toolkit 的作用域至少包含 MiLink，并开启“输出日志到守护进程”。
3. 打开 HyperConnect Toolkit，开启“记录详细日志”。
4. 点击“重启服务”，然后重新进入“系统跨设备流转设置页”。
5. 保持故障发生时原本的账号、WLAN、蓝牙和手机状态，点击刷新并等待至少 30 秒。不要先通过桌面快捷方式建立串流，也不要临时改变认证状态。
6. 返回 HyperConnect Toolkit，点击“导出诊断日志”，保存并发送生成的 .txt 文件。
7. 复现结束后关闭“记录详细日志”，再次重启服务。

报告内容

报告会一次性包含模块版本、Android/HyperOS、LSPosed 框架/API/作用域、MiLink、Xiaomi Mirror、Continuity SDK、系统设置组件版本，以及以下发现链判定：

• 是否真正调用 startDiscovery，监听器是否注册；
• 本机 NotificationTrans 服务数据与能力位；
• 发现回调是否收到候选手机；
• 设备类型过滤结果；
• 远端 MiLink 与 Cast 能力位；
• 区域判定与候选设备是否最终进入列表。

详细观察 Hook 仅在开关开启并重启目标服务后安装，关闭时不注入。日志有按事件限流和进程总量上限；真实设备 ID 与通知来源包名使用会话内哈希，导出时还会再次脱敏。模块没有上传能力，日志只通过系统文件选择器保存到测试者指定的位置。

文件校验

Release 同时提供 .apk.sha256。APK 由与正式版相同的专用发布密钥签名，可直接覆盖安装。

HyperConnect Toolkit v1.5.0

Added

• One Modern LSPosed module for cross-device notification circulation, portrait application streaming, and MiLink Multi-Channel.
• Independent feature settings with fail-closed target-process registration and validated per-feature runtime reports.
• Native PIN_APP notification-click bridge, portrait first-message geometry correction, and official Host-binding recovery for HostNotBound (215).
• Material 3 companion UI, hidden system circulation-settings entry point, in-app About page, privacy/security documentation, issue templates, CI, and signed tag-release workflow.

Changed

• Default configuration enables only cross-device notification circulation.
• Notification feature names and system-settings wording now match the user-facing circulation flow.
• Runtime status no longer performs unused Secure Settings probes.

Security

• Target-process reports verify sender identity, package, process, module version, feature bit, and current boot before updating the UI.
• Root access is limited to fixed commands for a probe, one audited system activity, and two explicit target-service stops.
• Incompatible reflection bindings preserve the stock system path rather than registering a partial hook group.

Validation

• Unit tests cover settings, status policy, feature masks, notification transaction lifetime, orientation policy, and Host-binding/channel policy.
• testDebugUnitTest, lintDebug, assembleDebug, and git diff --check pass before the initial public publication.