PROJECT OVERVIEW · REVISED 30 September 2026

Tech 2 menus. More places to use them.

Original diagnostic menus on Android, macOS and Windows, with touch or keyboard controls and a direct USB connection to Chipsoft Pro.

I wanted to use a Tech 2 on my phone. That turned into OpenSAAB T2—and a lot of late nights.

A permanent reference for forum posts. This page and the download catalog are built together. Posts on external forums stay as written until their author edits them.

CURRENT RELEASES

Choose the build for your device.

Introduced in ARM64 preview.28: visible app version and optional daily update checks while idle. Older builds need one manual update to gain reminders. Updates never download or install automatically. The richer reviewed reports and security-handoff alert correction from preview.27 are included; field crash investigations remain open.

WHAT THE TESTS ESTABLISH

Working examples, with limits.

NG 9-3 Android testing has included vehicle identification, DTC reading and saved reports, Engine Data and security access—including re-adding reverse parking sensors. Pixel 7 and Huawei Mate 20 X are among the tested phones. These are particular test results, not a promise of every module or procedure.

Chipsoft Pro is the current tested adapter path. Please use genuine hardware. VCX Nano remains experimental on Android; MDI, Mongoose and other adapters have no supported public OpenSAAB connection. A VIN read over HS-CAN does not establish full module access: original-firmware workflows can also require SW-CAN on OBD pin 1.

Turn the key to ON before identification and follow the firmware prompts. Security processing needs internet and shares the VIN and required security data with the selected service. POST-AUTH describes data imported into the working card; the vehicle must still accept the operation. Read the privacy information →

HELP US IMPROVE IT

Tell us what happened.

Current Android and Windows previews can prepare and send a private support report. Review it first. Include the app version, device and OS, adapter and firmware version if known, exact menu steps, and whether this was a car, bench ECM or offline test. The public Mac 0.2.8 package does not include this reporting feature.

A report is not necessarily a crash: successful tests and connection problems are useful too. Keep VINs, security data and raw logs private; share the receipt through the project support channel.

OpenSAAB Collector helps owners of other adapters record traffic from an existing Tech2Win setup. Stop capture saves locally. Sanitization is optional and creates a separate copy for review; Upload is a separate choice. Some identifiers and security exchanges can remain.

Next priorities: field-report investigations, head-unit reliability and broader vehicle testing. More adapters, Linux and older SAAB/pre-CANdi support remain development work. Introduction videos show an earlier build.

ACKNOWLEDGMENTS

Thanks to the SAAB community.

Thanks to Matthias Claesson, creator of TrionicCANFlasher, for his pioneering community SAAB tools; Bojer for mentorship; and roffe84 and rogue33 for their advice.

Special thanks to tpw_rules for his earlier Tech2Win for SAAB work, including addressing the “I-Bus Missing” communication problem on 2003+ 9-3s. These acknowledgments recognise independent work and guidance, not a claim that they developed or endorse OpenSAAB.

FOR FORUM AUTHORS

A short introduction you can paste.

Link to this page for maintained details. Download the BBCode below or select and copy it. Preview it in your forum before posting; supported formatting varies.