ch
Feedback
APatch_s_build

APatch_s_build

前往频道在 Telegram

APatch_s_lightly_build 非官方构建,仅供测试

显示更多
未指定国家技术与应用26 630
2 733
订阅者
+1324 小时
+1257
+79430

数据加载中...

相似频道
无数据
有任何问题?请刷新页面或联系我们的客服
进出提及
---
---
---
---
---
---
吸引订阅者
六月 '26
六月 '26
+637
在1个频道中
五月 '26
+1 564
在5个频道中
Get PRO
四月 '26
+126
在0个频道中
Get PRO
三月 '26
+141
在0个频道中
Get PRO
二月 '26
+308
在0个频道中
日期
订阅者增长
提及
频道
26 六月+11
25 六月+13
24 六月+14
23 六月+19
22 六月+23
21 六月+26
20 六月+18
19 六月+16
18 六月+25
17 六月+23
16 六月+35
15 六月+14
14 六月+15
13 六月+22
12 六月+17
11 六月+31
10 六月+23
09 六月+41
08 六月+47
07 六月+23
06 六月+33
05 六月+45
04 六月+27
03 六月+23
02 六月+34
01 六月+19
频道帖子
+1
23e473a manager: fix TransactionTooLargeException crash on large module install logs When installing modules that produce large log output (e.g. theme modules with thousands of icons), the install log text state grows unboundedly, causing TransactionTooLargeException when the Activity's saved state Bundle exceeds the Binder transaction limit (~1MB). This was previously reported in #927 and fixed in cb684e6 by switching from rememberSaveable to remember, but that caused the log to reset on navigation (#1308). Fix both issues by: - Using rememberSaveable for text state (preserves log on navigation) - Truncating text at runtime to 100K chars when it exceeds the limit - Keeping full log in StringBuilder (remember) for saving to file - Also fixing ExecuteAPMActionScreen which had the same issue The 100K char limit (~100KB) is well below the Binder limit and still covers ~2000-3000 lines of install log

2
https://github.com/Admirepowered/selinux_hook selinux_hook已开源,由于作者没有那么多设备适配,故此公开方法以便自己适配。开源意味着作者不会将太多精力放到此工作上了。官方的KernelPatch可能只会支持4.19以上的设备
14 167
3
+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
23 501
4
支持更多kernel版本,4.19及以上应该没问题了,4.14仍然不可用
14 634
5
fix sequence,test with 6.12.23
14 509
6
+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>
7 047
7
修复由内核内联引起的部分5.10 5.4 5.15失效的问题
56 509
8
使用Release版本必须升级到此版本,这是最后一版保留superkey认证+管理器双重认证版本,也是支持天机+hoot_patch的版本
7 057
9
https://t.me/aplitelog 反馈问题前请加入,群里有些信息可能不会关键频道,回复比较复杂
6 907
10
Magisk+ap方案仍然会无效,请不要安装magisk,后续可能会支持某些特定版本
6 441
11
修复部分内核不生效的问题,此模块是为了解决 https://github.com/LSPosed/DirtySepolicy 检测的kpm模块,不开机或者无效请提交APatch bugreport或者last_kmsg,嵌入生效
12 987
12
Kernelsu上游以及下游都有解决方案,不需要kpm方案兼容
6 496
13
再次重申,自1.0.1版本以后只有嵌入才能生效,加载是无效的,原理是开机的时候会保存干净的sepolicy,app轮询的时候返回干净的policy,理论支持ap或者magisk,使用kernelsu系请不要反馈,kpatch-next不确定会不会生效
6 468
14
+1
fix kernel6.1 bootloop
11 692
15
纠正,并非MIUI问题,A11的问题
5 949
16
https://github.com/hamjin/DirtySepolicy/blob/e18c692732393823202e94b1fc0b07c79f42d02f/app/src/main/java/org/lsposed/dirtysepolicy/AppZygote.java#L89-L91 如果你用的是小米设备并且是4.19内核,那么报告neverallow violated;是正常的,因为MIUI不规范不安装root也有
5 851
17
+1
支持4.19 (由于手里有设备直接测的),已在6.12 6.6 4.19测试过,其他内核版本照着源码树写的,可以不用填写事件了。6.1内核和5.4理论也能行了
5 345
18
修复目前已知所有检测,不开机的请提供内核以及开机后的bugreport(实在没有可以不发),hook了一堆东西,目前不知道应该怎么合并到kernelpatch,hook成塞子了
30 015
19
喜报 新的检测还没修完
4 256
20
都怪E学长,疯狂加班,一计害三闲,等到正式合并还要一段时间,还有一些兼容性问题
6 435