TUI-ConsoleLauncher

Linux CLI Launcher for Android

Could not verifysource: GitHubJavaMITcommit 058f54116c41

Java, MIT licensed. The project labels itself: android, cli, console, launcher, linux, shell and terminal.

Argusic could not get TUI-ConsoleLauncher running. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Both fdroid-debug and playstore-debug APKs build successfully from source with Gradle 8.2, Android SDK 34, and a self-signed dev keystore.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
80 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
1,427
forks
316
open issues
188
watchers
141
size
22 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing TUI-ConsoleLauncher, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Android SDK not found4 minutes
  • No Java runtime available2 minutes
  • Missing signing keystore for debug builds1 minute
Install time
8 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
./gradlew assembleFdroidDebug exited 0 producing a valid 7.4 MB APK at app/build/outputs/apk/fdroid/debug/app-fdroid-debug.apk (906 entries, 13 DEX files, valid zip/APK)
Model tokens used
65,123
Exact commit tested
058f54116c41
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Environment**: Ubuntu 24.04, x86_64, no JDK or Android SDK pre-installed, no root access.
**Errors encountered and fixes**:
1. **No Java installed** → downloaded Temurin JDK 17.0.12, set `JAVA_HOME` and `PATH`
2. **No Android SDK** → downloaded Android command-line tools, installed SDK platform `android-34` …
3. **Missing signing keystore** → created a self-signed `release.jks` keystore and `local.propertie…
**Final builds**: Both `assembleFdroidDebug` and `assemblePlaystoreDebug` completed successfully, p…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 8…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8, "errors": [{"msg": "No …
tokens used
65,123

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.
  • Took 8 minutes to install, slower than the median of the 17 comparable projects Argusic has measured.

Of the 18 android projects Argusic has installed and timed, TUI-ConsoleLauncher was the 10th fastest to reach a running state, and 13 of 18 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Unverified80.000.08
Argusic Runner1/3Unverified80.000.18

Topics (from GitHub)

androidcliconsolelauncherlinuxshellterminal

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/TUI-ConsoleLauncher.svg)](https://argusic.com/subject/tui-consolelauncher)

Questions

Does TUI-ConsoleLauncher run?
Argusic could not verify that TUI-ConsoleLauncher runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test TUI-ConsoleLauncher?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 058f54116c41. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test TUI-ConsoleLauncher?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does TUI-ConsoleLauncher take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does TUI-ConsoleLauncher need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing TUI-ConsoleLauncher?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does TUI-ConsoleLauncher compare with the alternatives?
Of the 18 android projects Argusic has installed and timed, TUI-ConsoleLauncher was the 10th fastest to reach a running state, and 13 of 18 reached one at all.
Where is the evidence for TUI-ConsoleLauncher?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion