luma-tv
A calm, tvOS-inspired home screen for Android TV and Google TV. No ads, no tracking.
Runssource: GitHubJavaMITcommit 8ce68387cb69
Java, MIT licensed. The project labels itself: android, android tv, google tv, home screen, java, launcher, smart home and tvos.
luma-tv runs. An Argusic agent installed it in 12 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
From a clean checkout, ./luma.sh build (build.sh) succeeds and yields a valid signed dev.luma.tv v2.4 APK at dist/luma-tv.apk (6.8M, apksigner-verified, all Luma classes in classes.dex), and the DevicesTest suite runs and passes all 26 device cases (exit 0); installing/launching on a TV still requires adb and connected Android TV hardware that this container lacks.
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 95 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Android SDK absent (no aapt2/d8/apksigner/build-tools 36.0.0, no android-34)3 minutes
- java/javac not found (JDK absent in container)2 minutes
- build.sh: line 31: zip: command not found2 minutes
- No adb and no Android TV/device/emulator in container
- Install time
- 12 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- Fresh 'bash build.sh' from a cleaned checkout exited 0 and produced dist/luma-tv.apk (7100991 bytes); 'apksigner verify --verbose' returned 'Verifies, Verified using v2: true, v3: true, 1 signer'; 'aapt2 dump badging' showed package dev.luma.tv versionName 2.4, minSdk 26, targetSdk 34; 'javac + java dev.luma.tv.DevicesTest' exited 0 with all 26 HDMI-CEC device cases 'All passed.'
- Model tokens used
- 106,963
- Exact commit tested
- 8ce68387cb69
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc "cd /work/repo && java 2>/dev/null; python3 tools/generate_sounds.py 2>&1 | head -2; py… succeeded in 0ms: soft_step.wav: 145 ms, peak -12.7 dBFS, RMS -27.2 dBFS soft_open.wav: 195 ms, peak -11.6 dBFS, RMS -27.9 dBFS final git status: dist: -rw-rw-r-- 1 runner runner 7100991 Oct 31 07:41 luma-tv.apk -rw-rw-r-- 1 runner runner 62868 Oct 31 07:41 luma-tv.apk.idsig The repo's git status is clean (build/, dist/, .signing are gitignored). Everything is verified. Le… tokens used 106,963 The repo's git status is clean (build/, dist/, .signing are gitignored). Everything is verified. Le…
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
- Reached a running state on a clean machine, with the session recorded.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 28 comparable projects Argusic has measured.
- Hit 4 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 29 android projects Argusic has installed and timed, luma-tv was the 20th fastest to reach a running state, and 20 of 29 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
androidandroid-tvgoogle-tvhome-screenjavalaunchersmart-hometvos
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/luma-tv)Questions
- Does luma-tv run?
- Yes. luma-tv runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test luma-tv?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8ce68387cb69. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test luma-tv?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does luma-tv take to install?
- 12 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 luma-tv need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing luma-tv?
- 4 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 luma-tv compare with the alternatives?
- Of the 29 android projects Argusic has installed and timed, luma-tv was the 20th fastest to reach a running state, and 20 of 29 reached one at all.
- Where is the evidence for luma-tv?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.