AdguardTeam / AdguardTeam/adguardcert

Module starts before zygote64 process causing adguard certificate not to be mounted

未關閉
#59 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Shell
星號
421
分支
34
PR 合併指標
30 天內沒有已合併 PR

描述

The magiskd process always seems to start before the zygote64 process (which causes the post-fs-data.sh or service.sh script to be started before the zygote64 process), and it may be the case that the pid of the zygote64 process is not available resulting in the failure to mount the adguard certificate. This results in the module not working as expected.
![Screenshot_20240521-224834_Termux](https://github.com/AdguardTeam/adguardcert/assets/20317782/02216fee-40c5-4261-aabc-773dfb0d2cc2)
![Screenshot_20240521-230008_AdGuard](https://github.com/AdguardTeam/adguardcert/assets/20317782/b62376ad-10d8-4d21-879d-5752994b2ce7)

OS version : Android 14 (LineageOS 21)
device : OnePlus 7t pro
adguard version : 4.4.184
magisk version : 27.0

As I am a native Chinese speaker, the above English content was translated using translation software. Please understand and point out any inaccuracies in the original Chinese text below.
magiskd进程似乎总是先于zygote64进程启动(这将导致post-fs-data.sh或service.sh脚本先于zygote64进程被启动),可能会出现无法获取zygote64进程的pid导致无法挂载adguard证书。导致模块无法按预期工作。

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。