fix: restore direct source and functional bounded Range acceleration - #12
Draft
Zhanfg wants to merge 140 commits into
Draft
fix: restore direct source and functional bounded Range acceleration#12Zhanfg wants to merge 140 commits into
Zhanfg wants to merge 140 commits into
Conversation
- replace encoded bootstrap generation with ordinary Gradle source - upgrade to an API 36-compatible Android build stack - preserve the original DownloadProvider hook return value - prevent wrapper-module APK downgrades while allowing upgrades - remove unused package-install permission and disable backup of download history - add direct source validation, lint, APK verification and module packaging
Bring the default-branch removal of the two missing-bootstrap workflows into the direct-source repair branch without changing the recovered source tree.
Load the reviewed pass-through entry instead of the experimental ranged writer, reset legacy enabled state during app startup, and make CI reject any reintroduction of the real engine into java_init.list.
Require a signature-level permission for confirmation and notification-control receivers, then verify the exact libxposed entry list, API metadata, scope, and embedded APK bytes in the final package.
Remove the unvalidated concurrent Range writer from the compiled source tree, enforce its absence in CI, report candidate certificate fingerprints, and preserve old installations when APK signatures differ.
Owner
Author
最终三轮审查与候选验证第一轮:恢复与构建事实源
第二轮:运行时与 IPC 边界
第三轮:发布链与产物
候选哈希Release APK 当前使用 Android Debug 证书,SHA-256 指纹: PR 继续保持 Draft。尚未完成 Android 16 / ColorOS 真机上的 LSPosed 加载、下载确认、系统进程重启、Live Update 控制、模块覆盖升级和异常恢复验证;分段下载引擎仍未启用。 |
Replace the Alpha 13 pass-through hook with a bounded parallel Range InputStream. Range workers spool temporary chunks, while the original ColorOS copy loop remains the only writer to the destination file. Unsupported or unverifiable servers fall back before any accelerated bytes are exposed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修复目标
恢复默认分支缺失的 Android 工程,并重新实现真正可工作的系统下载 Range 加速链,而不是仅做安全透传。
主要改动
0.3.0-alpha14/versionCode 15。ModuleMain重新启用真正的并行 HTTP Range:2–16 worker、默认 8、默认 16 MiB 分片、默认 32 MiB 启用阈值。pwrite:worker 只写有界临时分片;分片按顺序组成InputStream并交回 ColorOS 原始 copy loop,目标文件始终只有系统一个写入者。Content-Range、相同总长度和验证器。active / fallback / complete / error / disabled,不再静态显示“模块已启用”。su -c id -u。signature-mismatch。最终验证
5bd2a39fa35bd467008f461b8f21b0700c6c1c5131156636832Range hooks ready、parallel Range input、严格 Range 探测路径;历史RealDownloadAcceleratorModule/pwrite标记不存在。Alpha 14 候选哈希
验证边界
本 PR 继续保持 Draft。CI 已确认当前实现是真实 Range 引擎而非透传,但仍需要 Android 16 / ColorOS 真机验证:目标混淆方法签名、并行连接数量、最终文件 SHA-256、暂停/取消、断网、DownloadProvider 重启、设备重启续传、非 Range/压缩/DRM/未知长度回退,以及临时分片空间和清理行为。