termux-x11 VS fdroidserver

- Termux:X11: plugin for Termux to connect to instance of servers and handle the connection.

As an alternative to the VNC method suggested here, Termux also has a separate app by the name of Termux-X11[1]. It feels snappier and the resolution of the Linux environment is automatically scaled to the available screen space you have

[1] - https://github.com/termux/termux-x11

https://github.com/termux/termux-x11/actions/runs/5108462890 Download the companion packages and your respective os's debug (in my case it was arm64)

Also try this out, way smoother than VNC server, tho you might have to downscale the resolution to make the buttons larger https://github.com/termux/termux-x11

Make a github account then download the file. https://github.com/termux/termux-x11/actions/runs/4524914392

I recommend trying out https://github.com/termux/termux-x11 it performs better than VNC if you don't care about remote access

Download the artifact in the page: https://github.com/termux/termux-x11/actions/runs/3681182476 (you need an account)

For the most part I just followed the Termux-X11 instructions from Github: https://github.com/termux/termux-x11

According to the latest comment on this F-Droid bug report it looks like the problem should be finally fixed in the next F-Droid build server update.

Proprietary: - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11359 - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11361 - https://gitlab.com/fdroid/fdroiddata/-/commit/37e72d45f841b72b334f23f3e15a2e31fa8c4d56 - https://gitlab.com/fdroid/fdroidserver/-/issues/1004

Different solutions may be better for the different file types than a single download centre for everything. For example, for APKs, there's f-droid. You could selfhost fdroidserver and add your own repo to the f-droid client. This way, the APKs are distributed via an app store that's searchable and can be configured to auto update.

They were all on different days. I do test the app on my phone before releasing, and usually only release after not noticing anything for a few days of using the dev version. The reason for the time is a bug in the F-Droid server software that is used to generate the repo. The releases of GitHub have the correct date.

Note that F-Droid uses algorithm at https://gitlab.com/fdroid/fdroidserver/-/blob/2.1a0/fdroidserver/build.py#L746 to automatically detect built APKs, so ensure any modifications to location or file name are compliant. Auto updates are detected by checkupdates bot at https://gitlab.com/fdroid/fdroidserver/-/blob/master/fdroidserver/checkupdates.py

For the source of fdroidserver which creates the F-Droid repository in the end see here: https://gitlab.com/fdroid/fdroidserver

Clone the fork onto your local machine. You'd need to use linux or mac (windows doesn't work). Install https://gitlab.com/fdroid/fdroidserver.

yep, sadly F-droid doesn't have enough people working on it to keep on top of google's "new" app signatures yet. There was some progress, but then I gave up waiting and added their own repo until it's fixed.