The firmware drives.
The emulator runs the diagnostic firmware. Its own menus generate requests and show the vehicle’s replies.
Built for enthusiasts. Developed in the open.Your Saab.
Your Saab.
Your tools.
OpenSAAB T2 brings the original diagnostic menus to Android, with a Rust emulator and a direct USB connection to your adapter.
Developer previewPublic community now open. Source publication and a signed Android download are being prepared.
Original diagnostic menus. Direct Chipsoft USB.
Pixel 7 · development build
Android → USB → car.
Chipsoft Pro is our current development focus. A Windows computer is not required for the direct Android path.
Keep the evidence.
Save DTC reports. Review a private support report before you choose to share it. Help us turn real failures into fixes.
A clear path from first launch.
Get the right build.
The public signed APK is not available yet. Follow the project for release notes and download instructions when it is ready.
Follow on GitHub ↗Set up your software.
The development app guides you through version and language selection, download and extraction. English Saab NAO is the initial default.
Watch the setup walkthrough ↓Connect and explore.
Use a compatible USB adapter, allow Android USB access and follow the original firmware prompts. Start with information and code reading.
Read the community guide ↗The emulator source and original vehicle software are separate. Firmware distribution and public-build packaging are under review. The videos show the current development build.
Where we are today.
| Area | Status | What that means |
|---|---|---|
| Chipsoft Pro · Android | Vehicle-tested workflows | ECU information, DTC and selected security workflows have worked on our test vehicles. Wider compatibility needs testing. |
| VCX Nano · Android | Under investigation | Earlier successful runs; a later channel-initialization regression remains unresolved. |
| MDI and other adapters | Not supported yet | No claim of a working Android backend. |
| Live data and programming | Incomplete coverage | Not ready to advertise as dependable across vehicles and modules. |
Read the dated Android DTC research notes for earlier evidence; the status above reflects subsequent findings.
Meet the app. Learn the first steps.
Introducing OpenSAAB T2
A captioned overview of the project and the community preview.
Read the transcriptYour first launch
Select software, understand download and extraction, and recover from an offline error. Actual Android emulator screenshots.
Read the transcriptCaptioned walkthroughs, not live vehicle demonstrations. Screens were captured from a development build. No private VINs, security codes or traffic logs are shown.
Built together
Help shape what comes next.
Tell us what works, describe what fails, or volunteer to test on Android.
A place for every question.
Use the forum for help and ideas. Use an issue report for a repeatable bug. Beta participation is voluntary and never a condition of using the project.
Voluntary support
Buy me a beer.
I’ve put my own time into OpenSAAB T2. If it helps you, consider supporting development and adapter testing on Ko-fi. Support is voluntary — it does not unlock diagnostics, purchase vehicle security access, or guarantee compatibility.
Support the project
Contributions fund hardware, documentation and ongoing work. Testing and code are equally welcome.
No VIN, logs or security data are attached to the donation link.