-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[NOTICE]: Termux Processes Killed On Android 15 For OnePlus Devices #4219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Works fine on latest android 15 avd.
Issue is |
I have this problem too |
Read the installation docs again. |
But it still says |
Disable phantom process killer as mentioned above. |
Seems like you already have. Generate a full system log right after process gets killed. |
I executed this command, but it had no effect:
|
The result of this command returns
|
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 But your logs didn't contain execution history. Exit termux, then run |
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 Run |
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: ***@***.***>
|
Another report. Report to OnePlus.
|
|
Crash log: |
The latest update to termux from Google Play Store (not f droid) seems. To resolve the issues |
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? |
Unlock the Bootloader and everything goes well on OnePlus 13 |
Which version did you install, playstore? Do you mind testing if proot works? |
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. |
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
…cond stage has already been run before" error if `ln` process used to create lock file got killed instead of failing to create lock file if it already existed Related termux/termux-app#4219
من جاي ينزل فيديو ما اقدر استخدمه في اي برنامج تصميم او اعدل علي بنفس هاتف ما يسمح بذلاك لماذا |
Why can't I use the video with design programs after downloading it so that I can edit it without programs from the same phone? They don't allow it. They say it doesn't allow that. Why? |
Does this have anything to do with termux? @mnbjhk if not you probably need to contact the distributor |
لازم اكو حل مشكلة ما بعدا تنزيل الفيديو لان من ينزل فيديو بالهاتف ما يمكنك استخدامه باي تعديل حتى من تريد تعدل عليه من داخل هاتفك بدون برامج ما تفدر |
it is not clear what you are referencing, or how this relates to Termux, the terminal emulator. |
اخي تحميل الفيديوهات روعه سلس بس المشكله من ينزل فيديو بالهاتف تريد تعدل على فيديو مثلا تسخدم ادوات هاتف مالك تعديل فيديو ضيف فلاتر مثلا او حركات الفيديو يقول هذا فيديو غير مسموح الي بالتعديل اما نفس فيديو تنزله من غير برنامج تنزيل يسمح الك بالتعديل |
...either off topic or possibly trolling? Either way this thread isn't the right place for this... I'd consider asking your device vendor or app vendor. |
Those are related to phantom process, not current issue. |
@agnostic-apollo Did you manage to solve it? |
The current issue of oneplus and related devices can only be solved with system update, which should have been released long ago. Phantom process killer will cause similar killing on all android 12+ devices, and needs to be disabled too, but not related to OnePlus issue. |
If you have a recent system update, then no solution for commands getting killed in proot, like |
I'm plenty certain it's all fixed in the latest updates. |
Yes it is. It's already fixed on 701 update of OOS15 on CPH2609.
…On May 14, 2025 11:47:14 PM GMT+08:00, Arkuarius ***@***.***> wrote:
Arkuarius left a comment (termux/termux-app#4219)
I'm plenty certain it's all fixed in the latest updates.
--
Reply to this email directly or view it on GitHub:
#4219 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Unpin the issue? |
Uh oh!
There was an error while loading. Please reload this page.
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
The text was updated successfully, but these errors were encountered: