uz
Feedback
APatch_s_build

APatch_s_build

Kanalga Telegram’da o‘tish

APatch_s_lightly_build 非官方构建,仅供测试

Ko'proq ko'rsatish
2 481
Obunachilar
+1424 soatlar
+2127 kunlar
+1 53630 kunlar
Postlar arxiv
+1
4c113e9 build(deps): bump the action-dependencies group across 1 directory with 3 updates (#1431) Bumps the action-dependencies group with 3 updates in the / directory: [gradle/actions](https://github.com/gradle/actions), [android-actions/setup-android](https://github.com/android-actions/setup-android) and [actions/upload-artifact](https://github.com/actions/upload-artifact). Updates `gradle/actions` from 5 to 6 - [Release notes](https://github.com/gradle/actions/releases) - [Commits](https://github.com/gradle/actions/compare/v5...v6) Updates `android-actions/setup-android` from 3 to 4 - [Release notes](https://github.com/android-actions/setup-android/releases) - [Commits](https://github.com/android-actions/setup-android/compare/v3...v4) Updates `actions/upload-artifact` from 6 to 7 - [Release notes](https://github.com/actions/upload-artifact/r

支持更多kernel版本,4.19及以上应该没问题了,4.14仍然不可用

fix sequence,test with 6.12.23

+1
f4ca7d3 apd: fix some module scripts won't add AP_MODULE environment var (#1474) AP_MODULE environment var will only pass in exec_script, that's cause only stage-scripts, action.sh and uninstall scripts have this environment var So, it cause customize.sh, and meta*.sh won't have this envionment var And module developers will see them can't use apd module config set command, because apd throw `This command must be run in the context of a module or passed --internal <name>` Taking the magic_mount_rs module as an example: before: ``` APATCH='true' ``` after: ``` APATCH='true' AP_MODULE='magic_mount_rs' ``` Co-authored-by: AlexLiuDev233 <wzylin11@outlook.com>

修复由内核内联引起的部分5.10 5.4 5.15失效的问题

使用Release版本必须升级到此版本,这是最后一版保留superkey认证+管理器双重认证版本,也是支持天机+hoot_patch的版本

https://t.me/aplitelog 反馈问题前请加入,群里有些信息可能不会关键频道,回复比较复杂

Magisk+ap方案仍然会无效,请不要安装magisk,后续可能会支持某些特定版本

修复部分内核不生效的问题,此模块是为了解决 https://github.com/LSPosed/DirtySepolicy 检测的kpm模块,不开机或者无效请提交APatch bugreport或者last_kmsg,嵌入生效

Kernelsu上游以及下游都有解决方案,不需要kpm方案兼容

再次重申,自1.0.1版本以后只有嵌入才能生效,加载是无效的,原理是开机的时候会保存干净的sepolicy,app轮询的时候返回干净的policy,理论支持ap或者magisk,使用kernelsu系请不要反馈,kpatch-next不确定会不会生效

+1
fix kernel6.1 bootloop

纠正,并非MIUI问题,A11的问题

https://github.com/hamjin/DirtySepolicy/blob/e18c692732393823202e94b1fc0b07c79f42d02f/app/src/main/java/org/lsposed/dirtysepolicy/AppZygote.java#L89-L91 如果你用的是小米设备并且是4.19内核,那么报告neverallow violated;是正常的,因为MIUI不规范不安装root也有

+1
支持4.19 (由于手里有设备直接测的),已在6.12 6.6 4.19测试过,其他内核版本照着源码树写的,可以不用填写事件了。6.1内核和5.4理论也能行了

修复目前已知所有检测,不开机的请提供内核以及开机后的bugreport(实在没有可以不发),hook了一堆东西,目前不知道应该怎么合并到kernelpatch,hook成塞子了

喜报 新的检测还没修完

都怪E学长,疯狂加班,一计害三闲,等到正式合并还要一段时间,还有一些兼容性问题

好像不填也可以,但是最好还是填

完整版实现,需要将嵌入事件填写为 post-init-first-stage