In this guide, we will show you a nifty method to fix the issue of Termux not working on OnePlus/Realme/Oppo running Android 15. The latest iteration of the OS build has brought a slew of noteworthy goodies to the fore, with the likes of Partial Screen Sharing, Notification Cooldown, Lockscreen widgets, Battery Health percentage, App Archive, revamped Bluetooth menu, Private Space, the ability to save App Pair, and Privacy Sandbox managing to grab the attention of the masses.
However, as has been the case with the Chinese OEMs, especially the ones associated with BBK Electronics, they have further upped the ante by implementing unnecessary security and privacy restrictions. Don’t get us wrong, having a secure and private environment is the need of the hour but that only makes sense when it is implemented within a controlled environment. However, this has never been the case with the likes of OnePlus, Oppo, and Realme, and this time around, things are no different either.
With the latest Android 15 update, OnePlus, Oppo, and Realme have started killing processes running under proot on older Android versions, apparently by detecting syscalls. Processes that are linked with these apps, such as the likes of Termux, will get killed on shell startup, or even bootstrap installation’s second stage may fail. They have a special security tool that kills specific processes under proot. Making matters worse, the prompt that shows for proot isn’t shown currently when the process gets killed.
Moreover, the issue seems to be going beyond Termux as some ADB apps aren’t working along the expected lines either. When running adb on the phone, the response is along the following lines:
daemon not running. starting it now on port 5037 * ADB server didn’t ACK
failed to start daemon * error: cannot connect to daemon
With that said, there does exist a nifty workaround that should help you address this “issue”. So without any further ado, let’s check it out.
Table of Contents
Fix Termux Not Working on Android 15 OnePlus/Realme/Oppo
To rectify this issue, you’ll have to Enable “Disable Child Process Restrictions”. Here’s how it can be done:
- Head over to Settings > About Phone > Tap on Build Number 7 times.
- This will enable Developer Options. Access it from Settings > System.
- Then enable “Disable Child Process Restrictions” from there.
- Now install Termux and check if it is working or not
NOTE: FDroid is recommended as Play Store doesn't have the latest build.
Apart from that, having the phantom process killing disabled with settings_enable_monitor_phantom_procs is also worthy of a try, however, this is focused on more advanced users and might be beyond the scope of generic users. Talking about advanced users, they could also try increasing the max_phantom_processes as it seems to have spelled out success for some.
This new change could be part of it, either deliberate or accidental, and as of now, not all processes are getting killed. So there does seem to be some light at the end of the tunnel. As and when this light gets bright enough, we will update this guide accordingly. With that said, if you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.
UPDATE 1
ColorOS update with the build date of 9th Nov 2024 has fixed the issue. The OxygenOS update with a fix has not been released yet.
UPDATE 2
The latest ColorOS update for the OnePlus 13 and OPPO Find X8 has fixed this issue. Here’s the source for the same.
