[NOTICE]: Termux Processes Killed On Android 15 For OnePlus Devices

[Mubanjun]

Update: ColorOS update with build date of 9th Nov 2024 and OxygenOS with build date of 23rd Nov 2024 has fixed the issue. Build date can be checked with getprop ro.build.date. Disabling phantom process killer will not work and that is a separate issue.

---

Problem description

When opening Termux,it will throw "signal 9"directly.

Steps to reproduce the behavior.

Open Termux

What is the expected behavior?

No response

System information

• Termux application version: latest
• Android OS version:15
• Device model: OnePlus 12 with ColorOS 15

[agnostic-apollo]

Works fine on latest android 15 avd.

Termux application version: latest

latest is not a version. Generate a report and post.

• https://github.com/termux/termux-community/blob/site/site/pages/en/rules/how-to-ask-report-and-request.md#include-versions-and-device-info

Issue is likely not phantom process killer.

• https://github.com/agnostic-apollo/Android-Docs/blob/master/en/docs/apps/processes/phantom-cached-and-empty-processes.md#commands-to-disable-phantom-process-killing-and-tldr

[leafmoes]

I have this problem too
termux-report_issue_from_transcript.log

[agnostic-apollo]

TERMUX_APP_PACKAGE_VARIANT: APT_ANDROID_5

Read the installation docs again.

[leafmoes]

TERMUX_APP_PACKAGE_VARIANT：APT_ANDROID_5

再次阅读安装文档。

But it still says Killed.

termux-report_issue_from_transcript.log

[agnostic-apollo]

Disable phantom process killer as mentioned above.

[agnostic-apollo]

Seems like you already have.

Generate a full system log right after process gets killed.

https://github.com/termux/termux-packages/blob/site/site/pages/en/projects/docs/repos/main/packages/termux-tools/logcat/index.md#to-get-full-system-logs-of-other-apps-and-the-android-system

[leafmoes]

I executed this command, but it had no effect:

adb shell "settings put global settings_enable_monitor_phantom_procs false"

[leafmoes]

The result of this command returns false

adb shell "settings get global settings_enable_monitor_phantom_procs"

[agnostic-apollo]

libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 6273 (init), pid 6273 (init)
libc    : crash_dump helper failed to exec, or was killed
linker  : error: unable to open file "/data/data/com.termux/files/usr/bin/bash
"

There is unexpected newline at end of bash path, might be related.

But your logs didn't contain execution history. Exit termux, then run adb shell "logcat -c", then restart termux again and wait for killing and then generate log again.

[leafmoes]

logcat.txt

[agnostic-apollo]

W login   : type=1400 audit(0.0:6583): avc:  granted  { execute } for  path="/data/data/com.termux/files/usr/bin/dash" dev="dm-74" ino=602426 scontext=u:r:untrusted_app_27:s0:c57,c258,c512,c768 tcontext=u:object_r:app_data_file:s0:c57,c258,c512,c768 tclass=file app=com.termux
E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3
E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash
I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list
W login   : type=1400 audit(0.0:6584): avc:  granted  { execute } for  name="bash" dev="dm-74" ino=602768 scontext=u:r:untrusted_app_27:s0:c57,c258,c512,c768 tcontext=u:object_r:app_data_file:s0:c57,c258,c512,c768 tclass=file app=com.termux
E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3
E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash
I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list
E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3
E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash
I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list

The logs didn't reveal anything new. The linker error doesn't exist now. It could be OnePlus specific killer via OPLUS_KEVENT_RECORD that's killing the process, its known to kill processes running with proot, but there should be some additional entries for the killing, maybe they are not being logged due to rate limit. If its a OnePlus issue like it is for proot, there is nothing we can do, report to OnePlus.

Run adb shell "logcat -c" again and then get bash killed 5-6 times and then generate a dump again. Also try going into failsafe session and running /system/bin/ls and $PREFIX/bin/ls and see if they work.

[Mubanjun]

Android15的应用权限缩得很紧，即使从Outlook打开网页都会崩溃 * Android 15 has significantly tightened app permissions. Even opening a webpage from Outlook can cause the app to crash. 获取Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: agnostic-apollo ***@***.***> Sent: Wednesday, October 30, 2024 3:46:15 PM To: termux/termux-app ***@***.***> Cc: 木板菌 ***@***.***>; Author ***@***.***> Subject: Re: [termux/termux-app] [Bug]: Android 15 will directly print "killed" and return signal 9 (Issue #4219) W login : type=1400 audit(0.0:6583): avc: granted { execute } for path="/data/data/com.termux/files/usr/bin/dash" dev="dm-74" ino=602426 scontext=u:r:untrusted_app_27:s0:c57,c258,c512,c768 tcontext=u:object_r:app_data_file:s0:c57,c258,c512,c768 tclass=file app=com.termux E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3 E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list W login : type=1400 audit(0.0:6584): avc: granted { execute } for name="bash" dev="dm-74" ino=602768 scontext=u:r:untrusted_app_27:s0:c57,c258,c512,c768 tcontext=u:object_r:app_data_file:s0:c57,c258,c512,c768 tclass=file app=com.termux E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3 E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list E OPLUS_KEVENT_RECORD: oplus_kevent Receive message from kernel, event_type=3 E OPLUS_KEVENT_RECORD: OPLUS_KEVENT payload:10569,path@@/data/data/com.termux/files/usr/bin/dash I OPLUS_KEVENT_RECORD: oplus_put_exec_kevent_to_list The logs didn't reveal anything new. The linker error doesn't exist now. It could be OnePlus specific killer via OPLUS_KEVENT_RECORD that's killing the process, its known to kill processes running with proot, but there should be some additional entries for the killing, maybe they are not being logged due to rate limit. If its a OnePlus issue like it is for proot, there is nothing we can do, report to OnePlus. Run adb shell "logcat -c" again and then get bash killed 5-6 times and then generate a dump again. Also try going into failsafe session<https://wiki.termux.com/wiki/Recover_a_broken_environment> and running /system/bin/ls and $PREFIX/bin/ls and see if they work. ― Reply to this email directly, view it on GitHub<#4219 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2JO5Q3EU2ERNLVAELK2BMLZ6CFEPAVCNFSM6AAAAABQICARHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGA4DKMRUG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[agnostic-apollo]

Another report. Report to OnePlus.

Bootstrap Error
/data/data/com.termux/files/usr/etc/termux/bootstrap/termux-bootstrap-second-stage.sh: line 91: 26680 Killed ln -s "termux-bootstrap-second-stage.sh" "/data/data/com.termux/files/usr/etc/termux/bootstrap/termux-bootstrap-second-stage.sh.lock" 2> /dev/null
RELEASE: 15
BRAND: OnePlus
MODEL: CPH2619