OpenSAAB T2SAAB diagnostics · open source
OpenSAAB T2 · Developer previews · October 2026ARM64 0.1.1-preview.40 · ARM32 0.1.0-headunit.17 · Setup 0.3.4 · page revised 2026-10-22

§ 1 · COMMUNITY

Good questions. Better tools.

Join the openSAAB Discord for release updates, questions, testing feedback and development. GitHub Discussions and issues remain available for longer discussions and repeatable bugs.

Start in #welcome, follow #releases for new builds, ask in #general, share results in #testing-feedback, or join #development to contribute. The invite does not expire; a Discord account is needed to participate.

Share observations. Keep private vehicle data private.

QUESTIONS & HELP

Get unstuck.

Ask about setup, adapter selection, navigation and what a screen means.

Browse questions ↗

IDEAS

Make a suggestion.

Describe the task you want to make easier and what a useful result would look like.

Share an idea ↗

ISSUES

Help reproduce a bug.

Include app version, phone, Android version, adapter and the steps that failed.

Start an issue report ↗

§ 2 · A USEFUL REPORT

What makes a report useful?

Describe what you tried and what you expected. Include the app build, phone model, Android version and adapter model. Write the menu path and the exact visible error; include ignition state if relevant.

Use Report issue in the app, then review its contents before sharing. Start with the summary; only attach a file after checking it.

Public posts are visible to everyone. Do not upload VINs, seed/key or SSA data, raw USB captures, firmware, passwords, API tokens or unredacted screenshots. Keep sensitive security reports private.

Be constructive and respect other contributors. Reproducing a failure is useful progress. Never run vehicle changes solely to generate a report.

§ 3 · ANDROID TESTING

Volunteer when you're ready.

We want testers with different phones and adapters. Join now and choose which testing rounds fit your equipment.

Beta interest list

Reply to the welcome discussion with your phone model, Android version and adapter. Do not post your email or VIN. We'll announce a build and a short checklist when a testing round is ready.

This records interest only. No Play closed test is running yet; a future Play test requires a separate Google opt-in link, and a GitHub post does not count toward Google's testing requirements.