Amaral Driver Lab v0.13.0-alpha12
Amaral Driver Lab alpha12 is now promoted to a public release. This version combines a more demanding Recommended Full benchmark with clearer, correctly localized diagnostic results, making driver comparisons more useful for both users and Amaral driver development.
What's new
- Recommended Full v5: nine focused stages covering visual correctness, shaders, frametime, mixed graphics/compute/synchronization behavior, and correctness checks before and after load.
- GPU Stress 3D: a new mandatory 1280×720 visual stage with 768 procedural cubes, depth, four lights, multi-octave materials, and heavy post-processing. It carries 20% of the Recommended Full score.
- Comparable history: Full profiles v1–v4 remain separate and verifiable; v5 results are never mixed into older ranking series.
- Correct report language: Portuguese app locales generate Portuguese human-readable results. Every other app locale generates them in English.
- Consistent exports: the language rule now applies to the result preview, detailed Full log, HTML report, and generated GitHub issue. Technical JSON fields, IDs, hashes, metrics, and benchmark contracts remain unchanged.
Quick tutorial: compare drivers
- Download and install the APK attached below.
- On the home screen, tap Import Turnip ZIP and select a valid AdrenoTools driver package.
- Choose Android system driver × Turnip candidate to compare against the stock driver, or Turnip reference × Turnip candidate to compare two imported drivers.
- Select the candidate and, when applicable, the reference driver.
- Prepare the device: close other apps, keep the same performance and cooling mode, stabilize temperature, and avoid charging during the run.
- Tap Start selected Full test and complete the nine stages, including the visual checkpoints.
- Open Test log to review the recommendation, performance and compatibility indices, weighted gain, blockers, and technical evidence.
- Use Export diagnostic ZIP to save the complete evidence package, or Send to project issue to prepare a report for the Amaral Driver Lab repository.
Quick tutorial: analyze emulator logs
- Open Emulator log report on the home screen.
- Tap Select log (.TXT / .LOG) and choose a log generated by your emulator.
- Review the detected device, emulator, game, GPU, graphics API, driver, and relevant errors. Sensitive data is redacted before the issue is prepared.
- Tap Open GitHub issue and review the report before submitting it to the project.
How these logs help Amaral drivers
Submitted benchmark and emulator evidence helps identify driver regressions on specific GPUs, Android versions, emulators, games, and graphics APIs. Driver hashes and controlled A/B comparisons show exactly which package produced each result, while visual checkpoints and performance metrics help separate rendering errors from shader, frametime, synchronization, or compatibility problems.
This evidence gives Amaral driver development a reproducible basis for prioritizing fixes, validating experimental changes, and deciding whether a new driver is safer or faster without sacrificing rendering correctness. When reporting a problem, include the diagnostic ZIP whenever possible and describe the emulator, game, tested driver, and steps needed to reproduce it.
Validation
- Unit tests cover Portuguese and non-Portuguese report-language behavior.
- Android tests, Vulkan shaders, native arm64 C++, and the APK were built in GitHub Actions.
- APK SHA-256:
6b15f8eef261a782f0f73d794b8905411a933899f2f803ef00361bf2ad380f8a
The Advanced Full crash reported for RedMagic 11 Pro remains under investigation and still requires a reproducible diagnostic bundle or stack trace.