Original menus
The emulator boots the SAAB Tech2 card image. Its menus generate the diagnostic requests and display the vehicle's replies, exactly as the handset did.
OCTOBER 22 · ANDROID DEVELOPMENT PREVIEW
Four adapters. One normal Full-session entry.
Android 0.1.1-preview.40 is available. MX+, Chipsoft, Classic MDI and Nano retain their existing Full-session bindings. Chipsoft service reset/readback, module DTC reads, changing T8 traffic and one warm reconnect were observed on this exact APK.
Chipsoft cleanup, MX+ reconnect/DTC coverage, live-value accuracy and exact MDI/Nano repeats remain open. This is a development preview with known issues.
Download for 64-bit Android → · Changes, results and known issues →
OCTOBER 20 · MAC DEVELOPER PREVIEW
Intel and Apple silicon · 0.2.28-mxplus.5.
Matching Mac builds add card-derived security-transfer recognition, a read-only OBDLink MX+ route and optional local MCP. Both exact native apps passed installed software and offline menu/Stop checks. Fresh vehicle and complete non-English collection tests remain pending.
OTHER PLATFORM CHANNELS
Android 0.1.1-preview.40 · separate Windows experiment.
Android and Windows have separate releases and test limits. The new Android Full-session preview does not change the separate Mac MX+ read-only scope. All platform downloads →
§ 1 · WHAT IT IS
Original SAAB menus. On your phone.
OpenSAAB T2 emulates the original Tech2 diagnostic firmware on Android. Its menus are the real ones; its requests go to your car through a selected USB or Bluetooth adapter. No Windows laptop, no vendor driver.
Developer preview · Android 8+ with 64-bit ARM app support · 32-bit head unit or unsure?
F0: Diagnostics
F1: Service Programming System (SPS)
F2: Tool Options
F3: Diagnostic Strategy
F4: Release Notes
Software Version: 9.250
North American Operations
S1S2S3S4
§ 2 · HOW IT WORKS
The firmware drives. The app carries.
Direct connection
Android → USB → car. The app speaks the adapter's own USB protocol directly. Chipsoft Pro is the current development focus; the same transport is being brought to macOS, Windows and Linux.
Keep the evidence
Save DTC reports. Review a private support report before you decide to share it. Real failures, documented, become fixes.
§ 3 · START HERE
Three steps from download to diagnostics.
01 · INSTALL
Install the app directly.
Download the 64-bit Android app and approve Android's installation prompt. A 64-bit processor alone is not enough — Android itself must support 64-bit ARM apps. Unsure? Use the optional compatibility check, or choose the separate 32-bit head-unit build.
02 · PREPARE
Set up your software.
The app guides you through version and language selection, download and extraction. English SAAB NAO is the default. Existing installations keep their firmware and settings.
03 · CONNECT
Connect and explore.
Use a compatible USB adapter, allow Android USB access and follow the original firmware prompts. Start with information and code reading. Offline emulation works without an adapter.
The emulator source is MPL-2.0. The APK includes three original support files; the larger SAAB card image is downloaded during setup. Security access requires internet access to the OpenSAAB security-access API. Installed USB diagnostics work offline.
§ 4 · TESTED SO FAR
Where we are today.
Status is recorded from what has actually been observed on our bench and test vehicles, in the same terms we use internally. "Tested" means it has worked on real hardware; it is not a compatibility guarantee.
| Area | Status | What that means |
|---|---|---|
| Chipsoft Pro · Android | Working paths; cleanup issue | Exact preview.40 completed fresh security collection/import and showed service-reset completion with matching oil-life/day readback. An ordinary module DTC scan, T8 Read Values and one warm reconnect were observed. Stop reported protocol cleanup failure despite host USB release. Complete qualification is pending. |
| OBDLink MX+ · Android | Targeted development reads | Exact preview.40 reached key-status and T8 Read Values screens. Intermittent Bluetooth socket connection failures and incomplete ordinary DTC scanning remain unresolved; seamless sleep/reconnect and security workflows are not qualified. |
| Desktop · macOS, Windows, Linux | Separate platform previews | Mac 0.2.28-mxplus.5 is available for Intel and Apple silicon. Both exact native apps passed installed software, generated localized-prompt and offline MCP menu/Stop checks. Fresh physical MX+/USB vehicle and complete non-English security tests remain pending. Windows retains its separate 0.2.18-preview.5 experiment; Linux has no current public binary. |
| GM VCX Nano · Android | Developer preview | Nano remains included with its existing Full-session binding. Earlier boot/service-reset results retain their exact earlier-build scope. The complete preview.40 golden-path repeat is pending. |
| Classic MDI · Android | Experimental USB | Classic MDI remains included with automatic native USB startup and its existing Full-session binding. Earlier service-reset/USB-release results retain their older-build scope. The complete preview.40 golden-path repeat is pending; MDI2 remains unqualified. |
| Live data and programming | Limited evidence | Changing T8 ECU traffic was observed on exact preview.40, but an implausible airflow value and an unnamed row still need investigation. Numeric accuracy, wider modules/vehicles and dependable programming remain unqualified. |
Read the dated Android DTC research notes for earlier evidence; the table reflects subsequent findings.
§ 5 · WATCH
Meet the app. Learn the first steps.
Introducing OpenSAAB T2
A captioned overview of the project and the community preview. Transcript
Your first launch
Select software, understand download and extraction, and recover from an offline error. Transcript
Captioned walkthroughs from a development build, not live vehicle demonstrations. No private VINs, security codes or traffic logs are shown.
§ 6 · BUILT TOGETHER
Help shape what comes next.
Follow releases, ask questions, share test results or help develop openSAAB in our Discord community. Longer discussions and repeatable bugs can also go on GitHub.
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. No VIN, logs or security data are attached to the link.
§ 7 · NEWS
A busy weekend on the test bench.
· Development update
Classic MDI is now inside the Android app. Original SPA Add and ignition key-status proof join our Nano, Chipsoft and Bluetooth development results.
vLinker MC+ and Carista EVO have returned real Trionic 8 engine information and codes in scoped tests. Full original-firmware Bluetooth scans still need the exact single-wire wake. Preview.64 adds automatic Classic MDI initialization without a profile import or serial entry. Fresh Huawei setup, VIN, original menus and Stop passed; earlier owner Pixel7 SPA Add proof remains separate. Wider qualification and full physical power-loss startup remain work in progress.
§ 8 · RELEASE LOG
What changed, and when.
- Android ARM64 0.1.1-preview.40: normal Full sessions for all four adapters, MX+ lifecycle/readiness work and clearer stop/cleanup evidence. Chipsoft service reset/readback, module DTC reads, live traffic and warm reconnect were observed. Cleanup, MX+ reliability/DTC coverage, live-value accuracy and exact MDI/Nano repeats remain open. Release and exact test scope →
- Paired Intel and Apple-silicon Mac 0.2.28-mxplus.5 previews: card-derived security prompt recognition, read-only MX+ route and optional local MCP. Both native installed apps checked; fresh vehicle and full non-English collection tests remain pending. Downloads and exact test scope →
- We caught an error in preview checks—sorry for the confusion. Corrected Android preview.98 and Mac 0.2.27-preview.3 downloads are available, with no operator password step. Exact checks and remaining limits are recorded. Update and test scope →
- Platform downloads reconciled: Intel Mac 0.2.26-intel-preview.7 is now linked with its verified DMG hash and scoped live Nano results. Separate Windows 0.2.18-preview.5 adds translated-card startup and no operator password prompt. Android remains on preview.92 while the next preview is prepared. Versions, test scope and next changes →
- Android ARM64 preview.92 adds Rust panic source locations to reviewed support reports and retains panic headers after routine logs reach 2 MiB. Pixel 7 upgrade, offline firmware navigation and report checks passed; real-panic and password checks passed on the signed APK in an emulator. No adapter/vehicle tests were run for this release. Release scope and privacy details →
- Android ARM64 preview.90 is available with Nano dual-bus/read-profile fixes, Chipsoft readiness and firmware guidance, Classic MDI USB support, authenticated MCP controls and mandatory security processing/import password checks. Recent vehicle development reads are separated from exact signed-package checks; vehicle repeats remain pending. Intel 0.2.26-intel-preview.3 is a separate language/CANdi startup experiment. 48-hour progress summary and limits →
- Android ARM64 preview.70 incorporates the Chipsoft, Nano and Classic MDI test-round fixes: fresh manual/guided security collection, Nano import/resume recovery, Reboot Nano and bounded MDI recording. Software and installed-package checks pass; live repeats of the new fixes remain pending. Intel Mac 0.2.24-reporting.2, Apple silicon and ARM32 retain their separate releases. Downloads, source and testing limits →
- Mac 0.2.23-ui-parity.3 clarifies the first chooser: select USB adapters or Bluetooth adapters, then an available model. MDI is unavailable on macOS; OBDLink MX+ has no implemented profile. Legacy EVO/vLinker remains limited to VIN and Trionic 8 engine reads, without native I-bus diagnostics or SW-CAN wake. Each Intel and Apple silicon package passed 83 native synthetic assertions; the transport and security implementations are unchanged. Earlier owner-operated private Intel SPA Add and accepted code clearing remain separate evidence. Fresh exact-package vehicle workflows and the SSA collection/API/import path are pending. Downloads, matching source and test limits →
- Mac 0.2.23-ui-parity.2 developer previews for Intel and Apple silicon share the Android-reference chooser, anchored menus and saved auth_status/history display. Each exact package passed 83 native synthetic assertions on its own architecture. A later audit confirms original manual SPA Add and accepted DTC clearing in an earlier private Intel session, with six clean shutdown replies; the saved 17-code report is partial and later nonzero faults were observed. This is historical private-build evidence: fresh public-package vehicle tests and the SSA collection/API/import workflow remain pending. Saved security state is not a current ECU grant. Downloads, matching source and test limits →
- Android ARM64 preview.64 removes Classic MDI connection-profile import and manual serial entry. Huawei passed two fresh development installs and an exact signed public APK fresh setup/VIN/Main Menu/Stop check. We are looking for Classic MDI owners to test other Android phones. Download and test scope →
- Android ARM64 preview.63 retrieves the MDI serial first and prompts for a connection key after clean USB release when needed. Pixel7 passed key-only/no-profile startup tests and exact public APK upgrade, fresh VIN, firmware and Stop. No SN entry is required; base-key import, recorder and partial DTC-export limits remain. Download and test scope →
- Android ARM64 preview.45, Mac 0.2.22 for Apple silicon/Intel, and Windows 0.2.17 portable previews add shared EVO/vLinker VIN and read-only Trionic 8 ECM/code workflows. The exact Android release upgraded Pixel 7; Mac M4 EVO CLI reads passed over BLE and Classic. Windows software checks passed, while physical radio, Intel and iPhone qualification remain pending. Downloads, source and test limits →
- Collector 0.5.5 fixes adapter selection behind USB hubs. Windows build and regression checks passed; a fresh Windows 8 Pro 32-bit / MongoosePro GM II capture remains pending. Select the adapter itself, start before Tech2Win, then stop, review and choose whether to upload. Collector download and instructions →
- Android ARM64 preview.29: reviewed reports survive rotation, upload consent resets after a cold relaunch, sent reports retain their receipts, and ended sessions clear the live display. Offline Actions adds ECU information with an accurate connection prerequisite. Pixel 7 read-only Chipsoft/ECM bench checks passed; full vehicle and SW-CAN coverage remain separate.
- Android ARM64 preview.28: visible app version and optional daily idle update reminders, with separate architecture channels, a one-day snooze and manual opt-out.
- Android ARM64 preview.27: richer reviewed diagnostic reports, Chipsoft firmware identity and expected-stop handling for security processing. Field retesting is still required; ARM32 remains on its separate release.
- Collector 0.5.3: create a sanitized copy, review counts of supported text redactions, then confirm upload. Originals stay local and unchanged. Split identifiers and security exchanges may remain. Collector download and privacy limits →
- Collector 0.5.2: stop and save locally, review your capture, then choose Upload. Fresh bundles preserve your edits; no automatic upload or automatic redaction. Collector download and review instructions →
- Windows 0.2.15 preview: Chipsoft direct USB/CDC, shared security-data processing, firmware continuation and private issue uploads. Removes a legacy private bench identifier before publication. Known adapter-parser limitation is documented. Windows download and release notes →
- Branded Collector 0.5.1 and Mac 0.2.8 betas: separate Apple-silicon and Intel downloads, matching source, checksums and a scoped test guide. Persistent Donate controls are being brought to every platform. Mac beta downloads →
- Mac 0.2.7 development checkpoint: Connect and start now reads the bench VIN and launches the original SAAB firmware with a deferred native Chipsoft bridge. Real CAN reception, clean shutdown and successful retry verified on M4. The original single-wire wake still fails on our bench without diagnostic pin 1/SW-CAN; original ECU-information and DTC success are not confirmed. Apple-silicon and Intel packages archived privately; Intel 0.2.7 native hardware retest pending. Read the progress update →
- Desktop previews: the macOS Apple-silicon build identifies a Chipsoft Pro and reads the VIN over HS-CAN natively, without the vendor driver. Windows and Linux previews exist offline. Nothing desktop is downloadable yet.
- Setup 0.3.4 opens the verified app automatically after installation. ARM64 preview.22 and 32-bit headunit.17 share the shorter software-preparation flow and the Chipsoft Connect and start action. Installer cleanup is optional. Install updates over the existing app to keep firmware and settings.
- 32-bit head-unit build keeps its optimized startup and defers CANdi initialization until communication is needed. On our ECM-only bench the VIN reads; the missing single-wire bus still stops the full vehicle workflow.
Full release notes, source archives, signing identities and checksums are on GitHub Releases.