[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

[256-1]

I had the same issue on my OnePlus 13 with ColorOS 15 when using the github version Termux. After trying GooglePlayStore version it now works, no killed info.
But when I tried to use proot-distro to intall ubuntu, it failed. Here enclosed with the capture and log when using the GooglePlayStore version.

[agnostic-apollo]

proot-distro is not going to work, it unsets $LD_PRELOAD that has libtermux-exec.so, which internally is what uses the system_linker_exec hack to normally run executables so that they appear to be run from the system partition instead of the app data directory, the later is what's detected to be malicious, and proot-distro would be running processes the same way.

https://github.com/termux/proot-distro/blob/2abfb39d2e3e17e00a9a57187a036cd10a1e3742/proot-distro.sh#L96

[chongxs]

在使用 github 版本 Termux 时，我在装有 ColorOS 13 的 OnePlus 15 上遇到了同样的问题。尝试 GooglePlayStore 版本后，它现在可以工作了，没有杀死的信息。但是当我尝试使用 proot-distro 来安装 ubuntu 时，它失败了。此处包含使用 GooglePlayStore 版本时的捕获和日志。

google play 安装的版本比 F-droid 的版本低，但至少能打开。F-droid 安装版本受限于网络，需要bootstrap……同一加13用户，还没找到比较好用方式

[dipankr]

在使用 github 版本 Termux 时，我在装有 ColorOS 13 的 OnePlus 15 上遇到了同样的问题。尝试 GooglePlayStore 版本后，它现在可以工作了，没有杀死的信息。但是当我尝试使用 proot-distro 来安装 ubuntu 时，它失败了。此处包含使用 GooglePlayStore 版本时的捕获和日志。

google play 安装的版本比 F-droid 的版本低，但至少能打开。F-droid 安装版本受限于网络，需要bootstrap……同一加13用户，还没找到比较好用方式

Avoid using the play store version as it is clearly mentioned on the termux github repo that there are some known issues with that version and it is suggested to use the version from github or fdroid

[ascopes]

Is there a way to get this working without ADB? Or is this a complete issue with running subprocesses on any Android device now with OxygenOS?

Disabling process restrictions in developer settings makes zero difference for me.

[ascopes]

Crash log:
termux-crash_report.log

[rjose-evertz]

The latest update to termux from Google Play Store (not f droid) seems. To resolve the issues

[SplicedNZ]

proot-distro is not going to work, it unsets $LD_PRELOAD that has libtermux-exec.so, which internally is what uses the system_linker_exec hack to normally run executables so that they appear to be run from the system partition instead of the app data directory, the later is what's detected to be malicious, and proot-distro would be running processes the same way.

https://github.com/termux/proot-distro/blob/2abfb39d2e3e17e00a9a57187a036cd10a1e3742/proot-distro.sh#L96

Do you think it's possible to prevent proot-distro from overriding $LD_PRELOAD? or is that required for proot to work?

I wonder if rooted, moving termux to the system partition might be a quick fix?

[hamjin]

Unlock the Bootloader and everything goes well on OnePlus 13

[SplicedNZ]

Unlock the Bootloader and everything goes well on OnePlus 13

Which version did you install, playstore? Do you mind testing if proot works?

[256-1]

Good news ! I just received the latest OS update, termux(github version) works again, seems OnePlus fixed this issue.

[agnostic-apollo]

That's great news, what's the security update/patch date? You should likely be able to see it by clicking the right arrow in your last image or in Termux settings about.

[laughingwater]

What does this mean for those not using ColorOS? E.g. I'm on a OnePlus 12 Pro with OxygenOS (no root)... what are the steps to get this working?

update your system. The problem is already fixed on latest oos15.

In the OOS15 CBT, termux nor winlator work for me, (termux had the issue of getting killed (code9) so I tried reinstalling and now it fails to install bootstrap packages) [OnePlus 12 (IN version)]

[twaik]

@laughingwater install to internal memory, not to sdcard or expanded storage.

[ascopes]

@twaik OnePlus 12 devices only have internal storage by default though.

@weaponmasterjax so if OxygenOS is reporting itself as up to date, we have to assumably wait until the next OS update (usually every month or two)?

[laughingwater]

@laughingwater install to internal memory, not to sdcard or expanded storage.

I don't have external storage, it's installed to internal memory.

[laughingwater]

@twaik OnePlus 12 devices only have internal storage by default though.

@weaponmasterjax so if OxygenOS is reporting itself as up to date, we have to assumably wait until the next OS update (usually every month or two)?

Yeah if anything ends up happening in the CBT I'll let you guys know

[ascopes]

@laughingwater thanks

[DayDve]

I have same issue.
termux-report_issue_from_transcript.log

[DvdBr3o]

Same issue on OnePlus Pad Pro. My pad has recently been updated to ColorOS 15 (xxx.201 tho).

The f-droid version termux failed to install bootstrap packages, while the google play version can be installed right. But the google play version still receivd signal 9 when installing proot-distro distributions (something with tarball child process):

btw, in ColorOS 14 it will pop up a warning when it encountered permission denied. In ColorOS 15 it is just killed without warning...

[paulmorabito]

Same issue with Android 15 on OnePlus Pad 2.

[ascopes]

Can confirm the Google Play version worked for me.

[laughingwater]

Guys, I just got the .305 update, termux and winlator work as before again!!

[Arkuarius]

Awesome

[carbolymer]

@laughingwater which version is this? from play store or standalone?

[laughingwater]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

[agnostic-apollo]

What's output for getprop ro.build.date?

[agnostic-apollo]

Closing as resolved.

[Arkuarius]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

[haldi4803]

Guys, I just got the .305 update, termux and winlator work as before again!!

Not yet available for OnePlus Pad 2 :(

[laughingwater]

What's output for getprop ro.build.date?

The update is now also available in Oxygen updater (available on the playstore)

[laughingwater]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

https://github.com/brunodev85/Winlator/releases , honestly I am not knowledgeable about all the winlator versions, but this is the one I used.

[Arkuarius]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

https://github.com/brunodev85/Winlator/releases , honestly I am not knowledgeable about all the winlator versions, but this is the one I used.

That's Proot. Did you try any games inside Winlator?

[agnostic-apollo]

@laughingwater Thanks

[laughingwater]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

https://github.com/brunodev85/Winlator/releases , honestly I am not knowledgeable about all the winlator versions, but this is the one I used.

That's Proot. Did you try any games inside Winlator?

Not yet, I'll get steam real quick and test out some games I do have

(Ok future me here, my "real quick" turned into half an hour of 0 progress since steam doesn't want to co-operate, I'll test out a game later by putting it on a harddisk and connecting it externally so I wouldn't have to bother with steam, sorry guys.)

[SplicedNZ]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

https://github.com/brunodev85/Winlator/releases , honestly I am not knowledgeable about all the winlator versions, but this is the one I used.

That's Proot. Did you try any games inside Winlator?

Not yet, I'll get steam real quick and test out some games I do have

(Ok future me here, my "real quick" turned into half an hour of 0 progress since steam doesn't want to co-operate, I'll test out a game later by putting it on a harddisk and connecting it externally so I wouldn't have to bother with steam, sorry guys.)

Yeah steam not working within winlator is a known issue not specific to Oppo/ OnePlus. Usually the original winlator version will let you launch the container but will exit out when a game is launched, if that's fixed then that would be great news

[Arkuarius]

@laughingwater which version is this? from play store or standalone?

Fdroid version, they definitely fixed the issue since winlator is working too

"since Winlator is working too" just GlibC Winlator, or regular/Proot Winlator as well?

https://github.com/brunodev85/Winlator/releases , honestly I am not knowledgeable about all the winlator versions, but this is the one I used.

That's Proot. Did you try any games inside Winlator?

Not yet, I'll get steam real quick and test out some games I do have

(Ok future me here, my "real quick" turned into half an hour of 0 progress since steam doesn't want to co-operate, I'll test out a game later by putting it on a harddisk and connecting it externally so I wouldn't have to bother with steam, sorry guys.)

Oh lmao I forgot to tell you that Steam won't work on official Winlator. Just save yourself the trouble and get a SMALL DRM free from GOG just for testing purposes at this point.