Android-Debug-Database
A library for debugging android databases and shared preferences - Make Debugging Great Again
Runssource: GitHubhomepageJavaApache-2.0commit bf149df61f03
Java, Apache-2.0 licensed. The project labels itself: android, android debug database, awesome, database, database values, debug, debugging and emulator.
Android-Debug-Database runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
JDK 17 and Android SDK 33 are installed, the full Gradle build succeeds (370 tasks), all 5 unit tests pass across 5 modules, lint produces 0 errors, and both sample APKs and all library AARs are built.
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 90 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.
- Missing Android SDK - SDK location not found4 minutes
- Missing JDK - java command not found3 minutes
- lint error: getColumnIndex may return -1 in CarDBHelper.java (sample-app and sample-app-encrypt)1 minute
- lint error: getColumnIndex may return -1 in ContactDBHelper.java (sample-app and sample-app-encrypt)0.5 minutes
- lint error: getColumnIndex may return -1 in PersonDBHelper.java (sample-app-encrypt)0.5 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- `./gradlew build` exited 0, 370 tasks executed; `./gradlew test` exited 0, all 165 tasks UP-TO-DATE/passed; lint results show 0 errors; sample APKs produced: sample-app-debug.apk (4.9M) and sample-app-encrypt-debug.apk (11M)
- Model tokens used
- 72,200
- Exact commit tested
- bf149df61f03
- 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.
+ }
res.moveToNext();
}
return arrayList;
diff --git a/sample-app/src/main/java/com/sample/database/ContactDBHelper.java b/sample-app/src/mai…
index 9831e71..8129c45 100644
Now I have the complete picture. Here's the final report.
**Summary:** This is an Android library project (Android Debug Database). I installed JDK 17 and th…
tokens used
72,200
Now I have the complete picture. Here's the final report.
**Summary:** This is an Android library project (Android Debug Database). I installed JDK 17 and th…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.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- 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
- Took 8 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Of the 10 android projects Argusic has installed and timed, Android-Debug-Database was the 8th fastest to reach a running state, and 8 of 10 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.
- A quick evaluation: it was running 8 minutes after the clone.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.06 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.09 |
Topics (from GitHub)
androidandroid-debug-databaseawesomedatabasedatabase-valuesdebugdebuggingemulatorroomroom-databaseroom-persistence-librarysharedpreferencessqlite
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/android-debug-database)Questions
- Does Android-Debug-Database run?
- Yes. Android-Debug-Database runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test Android-Debug-Database?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bf149df61f03. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Android-Debug-Database?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Android-Debug-Database 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 Android-Debug-Database need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Android-Debug-Database?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Android-Debug-Database compare with the alternatives?
- Of the 10 android projects Argusic has installed and timed, Android-Debug-Database was the 8th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for Android-Debug-Database?
- 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.