AnExplorer
📁 Another Android Explorer ( File Manager ) is an All-in-One Open source file manager. AnExplorer File Manager (File Explorer) is designed for all android devices including Phones, Phablets, Tablets, Chromecast, Wear OS, Android TV and Chromebooks. It's a fully designed with Material guidelines by Google.
Runs with mockssource: GitHubhomepageJavaApache-2.0commit e856926de57c
Java, Apache-2.0 licensed. The project labels itself: android tv, anexplorer, chromebook, chromecast, file explorer, fileexplorer, filemanager and ftp client.
AnExplorer runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
AnExplorer Android app compiles and produces a valid unsigned APK (4MB) for the otherProDebug variant; the static marketing website in web/public/ serves correctly; the built-in AndroidTest has a pre-existing compilation error
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 92 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.
- No Android SDK installed3 minutes
- MaxPermSize JVM option not recognized by JDK 171 minute
- maven.fabric.io:gradle:1.25.4 returned 4031 minute
- JAXB Injector InaccessibleObjectException on JDK 171 minute
- keystore.properties values interpreted as bare identifiers1 minute
- ApplicationTest.java cannot find ApplicationTestCase
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- gradlew compileOtherProDebugJavaWithJavac succeeded, gradlew assembleOtherProDebug produced APK zip with 798 valid files, python3 validated zip structure
- Model tokens used
- 101,466
- Exact commit tested
- e856926de57c
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**What I did:** 1. **Setup JDK 17** — Downloaded and extracted Temurin JDK 17 (no system Java was available). 2. **Setup Android SDK** — Downloaded command-line tools + Android SDK platform 28 and build tools … 3. **Fixed build errors:** - Removed `MaxPermSize` JVM flag (not recognized by JDK 17) - Removed `io.fabric.tools:gradle` dependency (maven.fabric.io returned 403) - Added `--add-opens` flags to `gradle.properties` for JDK 17 compatibility with old Android Gra… - Fixed `keystore.properties` — values need to be quoted strings for the `$props.*` Groovy inter… 4. **Built successfully** — Java compilation passed, tests target compiled (NO-SOURCE), and APK was… 5. **Validated APK** — 798 files, 4MB, valid zip structure. 6. **Verified static website** — Served `web/public/` via HTTP, returned 200 on `/`. **Pre-existing issue not fixed:** `ApplicationTest.java` extends `ApplicationTestCase<Application>`…
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
- Installed in 7 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.11 |
Topics (from GitHub)
android-tvanexplorerchromebookchromecastfile-explorerfileexplorerfilemanagerftp-clientftpd-servermaterialphone-storagerootstoragestorage-providertext-editorusb-devicesusb-otgwatchappwear-os
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/anexplorer)Questions
- Does AnExplorer run?
- AnExplorer runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test AnExplorer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e856926de57c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test AnExplorer?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does AnExplorer take to install?
- 7 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 AnExplorer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing AnExplorer?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for AnExplorer?
- 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.