Android DJ Tools v0.1.3

Production-launcher / audible-playback packaging repair.

Primary download is now the non-debuggable release variant, not the dogfood/debug harness APK. The release launcher is dev.androidjtools.shell.AndroidDjToolsActivity and routes into the real MediaStore + Media3/ExoPlayer playback path. The debug harness is absent from the release APK.

Temporary gate override: the APK-producing Android CI job and production-launcher verification passed on commit 131b33e. API-35 E2E was explicitly overridden per operator instruction; the screenshot job was still running at publication. See release-provenance.json.

Signing note: this is a release build but currently uses the project development signing profile for sideload installation, not Play Store signing.

Android DJ Tools v0.1.2

Playback repair release.

This release fixes the shipping playback path so device-local tracks discovered through MediaStore are played through real Media3/ExoPlayer rather than the fixture state-only provider.

Release gate override: publication was explicitly forced after the APK-producing CI job passed on commit f81f9fb. The UI screenshot job (Android CI run 35379668261) and API-35 E2E conformance run 35379668292 were not treated as passing gates. See release-provenance.json for the exact override record.

APK SHA-256: 66c5b03783a46ad17af6e4aaec3ed0754b733d36ef3e9a7d0cfd424942d64e09

Android DJ Tools v0.1.0

Android DJ Tools v0.1.0

Release date: 2026-09-15

This is the first SemVer release of Android DJ Tools, a cloudless Android DJ-library preparation client developed fixture-first against the Sample Lib / Sample Lab boundary.

Release gate

The release is publishable only after all of the following are green on the integrated tree:

• protocol/fake-server unit suite;
• Android JVM unit suite;
• Android instrumentation-test source compilation;
• Android lint;
• debug APK assembly;
• Git diff whitespace check;
• GitHub Actions run for the released revision with an uploaded APK artifact.

Evidence boundaries

The local host had no connected Android device, configured AVD, or installed emulator system image during the implementation waves. Device-backed UI tests, notification/lock-screen behavior, and a real runtime launch therefore remain unclaimed unless later evidence for the release revision records them explicitly.

Protocol synthesis revision 1 was independently approved after its counterexamples were repaired. The final integrated release gate must still re-run the protocol and Android suites after all concurrent Wave Three/library changes have settled.

The release snapshot deliberately excludes implementation namespaces still owned by concurrently running Wave Two/Three tasks at tag time: cue/loop preparation, beatgrid preparation, direct Sample Lib transport, offline download/cache, and DJXML interoperability. Those tasks were dispatched before publication but are not silently folded into v0.1.0 while their review gates are open.

Artifact

CI produces app-debug.apk from :app:assembleDebug and uploads it as the androidjtools-v0.1.0-debug-apk workflow artifact. The GitHub v0.1.0 release attaches the APK downloaded from a successful GitHub Actions run for the exact release commit; a locally built APK is verification evidence only and is not the release asset.

Release documentation is published at https://androiddjtools.fkr.dev/ through GitHub Pages.