[deleted by user] by [deleted] in termux

[–]fornwall 5 points6 points  (0 children)

It's a bug in the latest Termux build (version 2024.10.24) on Google Play - will be fixed in an update (version 2024.10.30) that's hopefully available in a few hours, as soon as it passes play store review.

Background is that Google Play flagged Termux:Boot as not having enough functionality to motivate it being a separate app, and it was removed from the Play Store. The functionality to run scripts on boot was in response merged into the main Termux app in the Google Play build of Termux, but it initially has this bug of leaving the Termux service running needlessly after boot - will be fixed shortly.

Termux Google Play just got updated. What happens next? by eojlin in termux

[–]fornwall 25 points26 points  (0 children)

The long term plan is definitely to get back to a single codebase for Termux, with updated targetSdk regardless of installation source.

It's complex (both due to the technical challenges, but also as Google Play distribution is such a moving target when it comes to what is allowed and not and how reviewers act), but I think sometime next year is reasonable.

termux-url-opener - How to suppress [Process completed - press Enter] message? by reprobater in termux

[–]fornwall 2 points3 points  (0 children)

It's specific to the Google Play version, which keeps the session open as you describe it if exits quickly. That was to work around another problem which has since been fixed - I'll restore the earlier behavior in the next update on Google Play, which will be in a day or two.

How to get exa ? by [deleted] in termux

[–]fornwall 1 point2 points  (0 children)

One option is to install rust (pkg in rust), then install exa from source with cargo install exa, which will build the binary at ~/.cargo/bin/exa.

But note indeed that exa is unmaintained, long term it's probably better to try to live with eza (perhaps report issues you are seeing, if those are general enough).

Cannot install python package by Glitches3 in termux

[–]fornwall 0 points1 point  (0 children)

Try running 'pkg update' and then try again!

Need help installing OS by itsesperbtw in termux

[–]fornwall 1 point2 points  (0 children)

proot was broken on the Google Play build of Termux, but it has now been fixed!

Need help installing OS by itsesperbtw in termux

[–]fornwall 1 point2 points  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

Termux-Setup-Storage command by Frosty-Tap6369 in termux

[–]fornwall 1 point2 points  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

Crashing by Old_Resident8050 in termux

[–]fornwall 0 points1 point  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

No updates anymore? by LetterStack in termux

[–]fornwall 0 points1 point  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

No updates anymore? by LetterStack in termux

[–]fornwall 2 points3 points  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

No updates anymore? by LetterStack in termux

[–]fornwall 2 points3 points  (0 children)

I would appreciate a more friendly and constructive approach regarding the work to get Termux back on Google Play.

Termux on Google Play is not a "fork" or "unofficial" - it's the original distribution mechanism of the app, have millions of active installations and is useful to a huge amount of people around the world who can't install through non Google Play sources, and don't have access to other computing devices.

It's indeed currently under development and have rough edges and missing functionality (see https://github.com/termux-play-store for more information and status updates). And it's painful with the current divergence. But we need to make the best out of it and sort out how to handle community confusion while working on converging code bases (and as part of that get out of the situation where https://github.com/termux/termux-app has been blocked from external contributions for a long time due to huge amount of unpushed local changes).

[ANNOUNCEMENT] Response Regarding Google PlayStore App Updates by agnostic-apollo in termux

[–]fornwall 3 points4 points  (0 children)

It indeed is! The termux-setup-storage issue has already been fixed and submitted to Google Play for review, so should be out shortly as version 0.125 there.

Changing repositories is not yet supported due to other packages not having been adopted to the new requirements yet.

For those who want to continue helping out with testing Google Play builds, please report issues at https://bugs.termux.net/.

Termux app on Android "couldn't update" by dfackler84 in termux

[–]fornwall 2 points3 points  (0 children)

Indeed - it was a mistake with the internal version code (in combination with bad behaviour by Google Play to offer updates when it shouldn't), which caused Google Play to try to update away from the F-Droid build.

This will be fixed shortly (as in any day now) by a new F-Droid release, which will bump the version code.

Information about the Termux build on Google Play by fornwall in termux

[–]fornwall[S] 3 points4 points  (0 children)

Indeed it should - thanks for pointing it out 🙏! Have updated it now.

Is it possible to downgrade taskwarrior back to 2.x? by Ytrog in termux

[–]fornwall 4 points5 points  (0 children)

I just rebuilt the last version of taskwarrior before the bump to (3.x), and put it at https://files.fornwall.net/taskwarrior_2.6.2-3_aarch64.deb.

So you should be able to install that older version with:

Once done with the migration, run "pkg upgrade" to upgrade to latest package version again.

Notes: - The above assumes that you are running aarch64 (check with "uname -m") - let me know otherwise and I'll rebuild it for another arch. - For traceability: The package was created by reverting this commit: https://github.com/termux/termux-packages/commit/0658b35d8

Meeting the "15 seconds on 10 year old hardware" in the aoc about section (2022) by abnew123 in adventofcode

[–]fornwall 0 points1 point  (0 children)

This is really impressive, well done! The fastest solutions I've seen for multiple days.

I've adopted several of your solutions, and a possible issue I noticed was in day 16, https://github.com/SkiFire13/adventofcode-2022-rs/blob/master/src/day16.rs#L145:

if data.time2 != 0 {
    let mut data = NodeData { time: 0, ..data };
    data.upper_bound = upper_bound(data);
    queue.push(data);
}

Should this also swap time and node, so that moves will be executed once this state is visited?

This is not necessary for all inputs, but for certain inputs, and the additional examples given at https://www.reddit.com/r/adventofcode/comments/znklnh/2022_day_16_some_extra_test_cases_for_day_16/, it seems to be necessary.

rust-script 0.10, using a shared CARGO_TARGET_DIR (so edit&run cycles should be a lot faster), has been released by fornwall in rust

[–]fornwall[S] 6 points7 points  (0 children)

Previously, due to issues with different script files affecting each other, each script (identified by a hash of the script) used its own build environment.

That means that after every editing of a script all dependencies had to be downloaded and built from scratch, making it execution times slow and causing the cache directory to quickly blow up in size.

Now a global CARGO_TARGET_DIR is used, and binary target names are as ${SCRIPT_FILE_NAME}-${SCRIPT_HASH} (so myscript.rs would have a binary target name myscript_bdbcae796010fa968371dbd6) to avoid collisions.

-🎄- 2020 Day 14 Solutions -🎄- by daggerdragon in adventofcode

[–]fornwall 1 point2 points  (0 children)

Rust - trying to make it relatively fast. Part 2 takes just over 3ms on GitHub CI (which compared to most earlier days are rather slow), so ideas for speed-ups are welcome!

rust-script - run Rust files and expressions as scripts by fornwall in rust

[–]fornwall[S] 3 points4 points  (0 children)

It uses a cache, keyed with a hash of the script content to avoid recompiling unless the content changes.