20 August 2026
Abdullahand which kernel su manger with this
Файл
KowSU_v3.2.5-80-g72bd8405_32605-release.apk · 11.6 MB · click to show
KowSU_v3.2.5-80-g72bd8405_32605-release.apk · 11.6 MB · click to show
Manager
Branch: master
#ci_2605
Compare
Workflow run
KâriDФайл
Hi dev and everyone,
I've been testing the 4.19.404R kernel on my device (lmi), and I'm experiencing a few critical stability issues. I have attached the full log file (ELR_LogD_260821-011934.txt) for reference.
Here are the main issues I noticed from the logs:
Constant Atrace HAL Crash Loop: The vendor.atrace-hal-1-0 service is continuously crashing with a SIGABRT. It fails with the following assertion: Check failed: stat(tracefs_event_root_.c_str(), &st) == 0 tracefs must be mounted at either/sys/kernel/tracing or /sys/kernel/debug/tracing. This causes an infinite loop of crash_dump64 and tombstoned processes.
Cgroup / Memory Controller Errors: During init, there are continuous errors regarding cgroup memory controller activation: Activation of cgroup controller +memory failed in path /sys/fs/cgroup/system/uid_1000: Invalid argument.
Highly Aggressive LMK: simple_lmk is killing background apps and services extremely aggressively right after boot (e.g., Maps, Dialer, Docs, etc.).
The log file is attached. Let me know if you need any further testing or information!
Anisur Rahman#about_bpf
BPF for A16 QPR1+ ROMs
Cl are for anything below A12 to A16 QPR0 (the ROM will mention if it needs BPF kernel)
KâriDHi dev and everyone,
I've been testing the 4.19.404R kernel on my device (lmi), and I'm experiencing a few critical stability issues. I have attached the full log file (ELR_LogD_260821-011934.txt) for reference.
Here are the main issues I noticed from the logs:
Constant Atrace HAL Crash Loop: T
1. kernel don't have tracefs and debugfs (no it doesn't trigger tombstoned. process handled and exit cleanly)
2. cgroup uid_100 invalid argument is because the referenced process by android is being killed when it tries to access, so it no longer valid at that time. normal.
3. slmk is killing on boot. normal. if it doesn't kill, the boot will be very slowwwww and can stuck.
deu1. kernel don't have tracefs and debugfs (no it doesn't trigger tombstoned. process handled and exit cleanly)
2. cgroup uid_100 invalid argument is because the referenced process by android is being killed when it tries to access, so it no longer valid at that time. normal.
3. slmk is killing on boo
Thanks for your answers. AI can be confusing. 😁