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 38 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
AnExplorer Android app builds successfully with AGP 7.3.0 + Gradle 7.4.2 using JDK 17 and Android SDK 28. The otherFree release variant compiles without errors, passes R8 minification, and produces a valid 3.4MB APK. Debug dex and multi-flavor builds are blocked by the 64K dex method reference limit, which affects older AGP versions.
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.
- Android Gradle Plugin 3.3.0-alpha12 incompatible with JDK 17 (ExceptionInInitializerError)6 minutes
- Android SDK not installed5 minutes
- No Java installed4 minutes
- Dead Fabric dependency (io.fabric.tools:gradle:1.25.4) blocking Gradle config4 minutes
- Dex merge fails due to 64K method reference limit (68,810 > 65,536)4 minutes
- SigningConfigs and Fabric references in app/build.gradle blocked build3 minutes
- Install time
- 38 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- cd /work/repo && export JAVA_HOME=/tmp/amazon-corretto-17.0.21.0.11-linux-x64 && export ANDROID_SDK_ROOT=/tmp/android-sdk-root && ./gradlew --no-daemon clean :app:assembleOtherFreeRelease exited 0; 42 tasks executed; produced 3.4MB APK (repo-otherFreeRelease-4.0.0.apk) with 883 files including classes.dex and AndroidManifest.xml
- Model tokens used
- 300,338
- 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.
The project is now working. Here's a summary of what was done: **Issues found and fixed:** - Installed Amazon Corretto JDK 11 and 17 (no Java was available) - Removed dead `maven.fabric.io` / `io.fabric.tools:gradle` dependency and JCenter repo - Fixed `-XX:MaxPermSize` JVM flag removed (incompatible with JDK 17) - Installed Android SDK CLI tools and downloaded `build-tools` (28.0.2, 28.0.3, 30.0.3) + `platform… - Upgraded AGP from 3.3.0-alpha12 → 7.3.0 and Gradle from 4.10.1 → 7.4.2 (JDK 17 incompatibility) - Created dummy `keystore.properties` for build config fields - Removed `signingConfigs` block and Fabric conditional from `app/build.gradle` - Created `local.properties` with `sdk.dir` for Android SDK discovery - **64K dex method limit**: The debug dex merge fails (68,810 > 65,536 refs). Release builds succee… **Verified:** Clean build from scratch produces a valid 3.4 MB APK with 883 files. The `compileOthe…
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 38 minutes.
- Recovered from all 8 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.
- Measured 2 times, so the result is not a one-off.
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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 1.48 | |
| 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 38 minutes, hitting 8 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. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test AnExplorer?
- The run that produced this verdict cost $1.48: 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?
- 38 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?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for AnExplorer?
- 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.