Project status

[Srinuyadav149]

Is this project still in active development, or has it been discontinued?

[tareksander]

I don't have time to work on it currently, but it should be mostly stable and usable by now.

[Srinuyadav149]

It is usable when termux is downloaded from GitHub. But failing when downloaded from play store. Might be signature issue.

[twaik]

We do not maintain GP version. Also it has different signature.

Termux on the Play Store is a fork of an old version with additional, unmerged changes, and is not controlled by the dev team at https://github.com/termux. Despite its existence and version number, it is not the newest or latest version, and is significantly less functional than either the current F-Droid release or Github builds. More detail: termux/termux-app#4000

Unless you know exactly what you're doing, you should not use the Play Store fork. Install the suggested release from F-Droid :fdroid:.
Direct link: https://f-droid.org/en/packages/com.termux

If you have currently have the Play Store fork installed and want to install an official build from F-Droid or Github, you must uninstall Termux and all companion apps first.
That means uninstalling the main app, as well as Termux:API, :Styling, :Widget, :Task, :Float, and :Boot. Termux:X11 works differently and can be left installed.
If you need help with backing up your files: https://wiki.termux.com/wiki/Backing_up_Termux

[brandyn]

I just did this: https://sifter.org/~simon/journal/20250329.html

The one sore spot is the startup time is ~7 seconds. Any idea why that would be? If it's fixable, I am game to do the work and submit a patch.

Also, I note this in the docs: "Due to Android limitations, methods that return a value fail when the Activity isn't visible"

I suspect this is behind some issues I'm having... Likewise, is there a work-around I could help with?

[tareksander]

AFAIK termux-am should fail instantly, so the delay you're experiencing is the combined time of am and the plugin startup.

[brandyn]

It does fail instantly, but the connection.py code ignores the failure (no check for exit status) and then waits for 5 seconds for it to connect to the sockets before timing out and retrying with am. As a quick fix I just commented out the run() of termux-am and then immediately raise timeout just inside the first try block in order to move straight to the fallback, and this has greatly improved the startup time. (I did it that way so it's easy to revert.)

[tareksander]

Oh, seems I forgot to do the proper fallback. The proper way would be to check .returncode from run and skip straight ahead if the exit code wasn't 0.

[brandyn]

Is there a way to bring an already-running termux-gui applcation to the foreground (i.e., when I tap the shortcut on the homescreen, have it bring the existing one up rather than starting a new instance)? [I've spent the last few hours looking and trying things to no avail...]

[tareksander]

Is there a way to bring an already-running termux-gui applcation to the foreground

The bringTaskToFront method is what you're looking for.