OpenSAAB 64-bit 0.1.0-preview.28 — version and update reminders

OpenSAAB Android ARM64 preview.28 adds visible version information and optional update reminders. Install over your existing app to retain firmware, settings and reports.

• The header shows the installed version and executable architecture; About and connection details include Android version and phone model.
• While foreground and idle, OpenSAAB can check its public catalog once per 24 hours. A newer matching release displays a nonmodal View update reminder. Remind me tomorrow snoozes it for 24 hours; automatic checks can be disabled in App menu → Check for updates.
• Package and architecture channels are matched locally. No VIN, phone identifiers, adapter information or reports are sent in update checks. Normal HTTP metadata is handled by the website host. Offline errors stay quiet, cached offers expire after seven days, and diagnostics keep working.
• Updates remain optional. No automatic APK download, installation or uninstall; no reminder over an active firmware/security session. View update opens the official GitHub release page.

The preview.27 reporting improvements and security-handoff expected-stop correction are included. Existing older APKs need one manual update to gain automatic reminders. The separate ARM32 public release is unchanged.

Validation: signed APK update tests on Android 9 and 12 cover catalog/package/ABI validation, daily rate limit, snooze, opt-out, already-current and expired offers, offline failure, firmware lease and background/in-flight response handling. Android 12 layout/security/report checks and host regression tests pass. Pixel 7 in-place upgrade, visible version/About, live catalog check, offline Main Menu and normal stop were checked. Future-release offer tests used a fake catalog on a disposable AVD. No new vehicle or affected-model crash qualification is claimed.

Source: 2e16bc3009b38df5c20c79c41365412c299786bc. APK SHA-256: 559b4c0fc64634ec31c9a2a212f91a8b3a821dcc55bcb02d7246c6a96aba61ff. Native binaries are unchanged from preview.27.

OpenSAAB 64-bit 0.1.0-preview.27 — diagnostic beta

Android ARM64 diagnostic beta for users testing security access and reporting problems. Update over the existing app; keep your downloaded firmware and settings.

Changes:

• Reviewed support reports now capture phone model, Android/app versions, testing context, bounded lifecycle/security events and fixed failure categories. Optional follow-up contact is shared only with explicit consent.
• Reports include saved auth_status, advisory Fresh/Stale age and timestamps when the card and receipt match. POST-AUTH means processed card data; it does not prove current vehicle authorization. No raw VIN, seeds, keys or card data are included in this new snapshot.
• Chipsoft firmware version is displayed from the existing identification reply and included in reports. Detection alone does not establish compatibility.
• The deliberate emulator stop before security processing is now registered as expected, avoiding the unexpected-exit alert on that specific path. Cleanup timeouts and genuine unexpected-exit reporting remain.

Validation: host regressions; signed APK reporting/security tests on Android 9 and 12; Android 12 layout/health tests; report form rotation/recreation/resume; Pixel 7 in-place upgrade and offline firmware startup. Native binaries are unchanged from private preview.26. No new vehicle security transaction, affected Samsung/Motorola retest or ARM32 qualification is claimed. Field incidents remain under investigation.

If it repeats: choose Report issue, describe the exact menu/action, select bench/vehicle/offline context, review and send. Share the receipt privately; do not post raw logs or VINs. The separate 32-bit release is unchanged.

Application source: a517ff362f12e4a91b63690f488c038e271d1f5d. Native source is unchanged since 902c46f. APK SHA-256: ac4108539a06c4f33b6b9729e596854b7ea178437cc37128cb0cd8e702fc600a.

OpenSAAB Windows 0.2.15 — Chipsoft developer preview

OpenSAAB Windows 0.2.15 developer preview

OpenSAAB T2 now has a Windows preview with the shared security-access workflow and internet-only issue reporting. Use a genuine Chipsoft Pro on the default direct USB/CDC route.

This package follows the tested 0.2.14 workflow. Version 0.2.15 removes a personal vehicle identifier from a historical OEM comparison helper and closes its obsolete bench-only authority loader. The emulator engine and shared security worker are unchanged. This is an unsigned x64 preview, tested on Windows 10; Windows 8, Windows 11 and Windows ARM have not been qualified by this testing.

Security workflow

• Get Security Access can process a matching existing PRE-AUTH collection without repeating VIN identification or seed collection.
• The app asks for the service password and explains the VIN/security-file submission. The temporary password is OpenSAAB, case sensitive. Optional password storage uses Windows DPAPI for the current user.
• OpenSAAB is contacted first. Bojer is used only with explicit permission for the supported service-outage fallback; your OpenSAAB password is never sent to Bojer.
• The shared worker validates and imports the response into a working card. POST-AUTH records the imported data and timestamp. Firmware continuation uses that card. This label alone is not proof that every vehicle module has granted authorization.
• Report issue lets you review and send a private report directly, without an email app. Successful uploads return a receipt number.

Installation

Close OpenSAAB and run the x64 MSI. Upgrade over the existing installation to retain user data. Connect Chipsoft Pro, keep other adapter applications closed, and follow the app's ignition-position instructions. Use direct USB/CDC. The OEM vendor-DLL route remains explicitly experimental and comparison-only; no broader adapter support is claimed.

Known limitations

A 0.2.14 session stopped with Invalid raw CAN record size during Chipsoft reception. A later report was marked successful by the tester; it does not resolve the earlier parser failure. Version 0.2.15 preserves that limitation. Please send a reviewed issue report with the operation and steps if it recurs.

Windows is an incomplete developer preview, not full Android feature parity or qualification for every vehicle/module. Bench tests do not establish full-vehicle SW-CAN coverage. The most recent user success submission did not include a structured ECU authorization result. Complete fresh collection → processing → automatic continuation on the final package and forced live fallback-outage testing remain separate qualification work.

Download the explicitly named matching-source archive alongside the MSI and checksums. The automatic GitHub source ZIP belongs to the hosting repository and is not the source snapshot used for this Windows package. Original diagnostic firmware has separate licensing terms.

Package verification

Built on Windows 10 x64. Shell self-tests and all 17 offline firmware runtime checks passed. All 19 packaged files passed a scan for the owner's known private vehicle identifiers. Only the versioned shell and the two OEM comparison helpers differ from the 0.2.14 payload; the Rust emulator and shared workers are byte-identical. A new full vehicle session and clean-machine lifecycle test on 0.2.15 are not claimed.

Source revision: ae9efef945a99bb16520172b4cd3918d5a760c57. The matching-source ZIP contains 151 source/build/documentation files verified against that revision; a historical workstation-path receipt is excluded. No private reports, VIN records or credentials are included.

OpenSAAB macOS 0.2.8 — Apple silicon and Intel beta

OpenSAAB macOS 0.2.8 beta

Choose arm64 for Apple silicon (M1 or newer), x86_64 for Intel. Requires macOS 12 or newer. Open the DMG and drag OpenSAAB to Applications. Update over the existing app to retain downloaded software and settings. These builds are ad-hoc signed and not notarized; if macOS blocks opening, review the source/checksum and use the system's Privacy & Security → Open Anyway flow. Do not disable Gatekeeper.

1. Launch OpenSAAB and choose Firmware selection. Download your selected diagnostic software; the app verifies its checksum. The original card is downloaded separately.
2. Try Run without an adapter first. Confirm the original menus and persistent Donate button.
3. Connect one genuine Chipsoft Pro directly by USB and power the bench/vehicle correctly. Close other apps using the adapter. On this Mac path no Windows vendor driver is involved.
4. With ignition ON, select Connect and start. Check for a fresh VIN and correct vehicle year, then original firmware startup.
5. Stop the session and retry. Report Mac model/architecture, macOS version, build, adapter, software selection, and exact steps. Keep VINs, serials and raw diagnostic captures private.

Scope and evidence

Both exact 0.2.8 app bundles pass 16 built-in checks on M4 (Intel executable under Rosetta). The ARM64 app has also been visually checked for its branded shell, optional donation action and offline startup. Native Intel hardware and fresh Chipsoft VIN tests on this exact version remain pending. Earlier 0.2.7 M4 testing proved Chipsoft VIN reading and live CAN reception. This is evidence for the transport, not a claim of full 0.2.8 vehicle qualification.

Mac startup DTC integration, original ECU-information/DTC procedures, security/programming and full-vehicle compatibility are not qualified. An ECM-only HS-CAN bench without OBD pin 1/SW-CAN cannot validate procedures requiring that bus. Start with VIN and read-only information; this beta is not an Android-feature-parity release.

Donations are optional and unlock no features. Matching source and SHA-256 checksums accompany the downloads.

OpenSAAB 64-bit 0.1.0-preview.22

The same shorter setup and connection flow now serves ARM64 and ARM32: choose software, Download and continue, then Connect and start. A single supported adapter skips the picker. Chipsoft reads a fresh VIN and starts the original firmware without a second Start prompt. Optional online vehicle details are unchecked by default and load in the background when selected. Installer cleanup is available later in the app menu. Updates preserve existing firmware and settings.

ECU information is an original-menu shortcut for a freshly identified, known 9440 vehicle. Unknown menus or unavailable model information leave manual controls available. Vehicle-network checks remain in place. An ECM-only bench without single-wire CAN can read a VIN over high-speed CAN but still fail the original vehicle checks; no ECU-information or DTC success is claimed for that bench.

Validation: signed Android setup tests cover actual download/extraction, offline retry, cancellation, automatic return, version-switch backups, no repeated onboarding, Chipsoft startup consent, and optional cleanup. Shared command-gate/menu tests pass. Native ARM64 behavior is unchanged. The Pixel 7 was updated in place, then physically verified at the new connection screen and original Saab 9.250 main menu using its existing firmware in offline mode. No adapter was attached to the Pixel.

Source commit: b8a24a485bda20770fa6c1aba70c6913f7fcda11. APK SHA-256: 3b7d38d55e67286f8bc86c9bc7b630a0d8c5aa4f1f7bb5bc948e658898ffd7d2.

OpenSAAB Setup 0.3.4

Install OpenSAAB now downloads and verifies the selected app, resumes after Android source permission, and opens the verified installed app automatically. Required Android confirmations and signature/hash/package/version/ABI checks remain. Cancellation leaves a retry state; pending installation survives process restart. Cleanup no longer interrupts first use. Setup deletes its own verified installer APK after successful handoff; browser-owned Downloads stay under user control.

Validated on a disposable API36 Android device: real official release download, permission refusal/retry, recovery after stopping Setup while permission settings were open, installation cancellation/retry, successful automatic launch, optional cleanup cancellation and responsive layout/state preservation. Setup contains no firmware or native emulator code.

Source commit: b8a24a485bda20770fa6c1aba70c6913f7fcda11. APK SHA-256: 2b4485de05eaac4b3974f46c98fdc2ad98201dfc411b93a6f123b84117e3e203.

OpenSAAB 32-bit 0.1.0-headunit.17

The same shorter setup and connection flow now serves ARM64 and ARM32: choose software, Download and continue, then Connect and start. A single supported adapter skips the picker. Chipsoft reads a fresh VIN and starts the original firmware without a second Start prompt. Optional online vehicle details are unchecked by default and load in the background when selected. Installer cleanup is available later in the app menu. Updates preserve existing firmware and settings.

ECU information is an original-menu shortcut for a freshly identified, known 9440 vehicle. Unknown menus or unavailable model information leave manual controls available. Vehicle-network checks remain in place. An ECM-only bench without single-wire CAN can read a VIN over high-speed CAN but still fail the original vehicle checks; no ECU-information or DTC success is claimed for that bench.

Validation: signed Android setup tests cover actual download/extraction, offline retry, cancellation, automatic return, version-switch backups, no repeated onboarding, Chipsoft startup consent, and optional cleanup. Shared command-gate/menu tests pass. Native ARM64 behavior is unchanged. The Pixel 7 was updated in place, then physically verified at the new connection screen and original Saab 9.250 main menu using its existing firmware in offline mode. No adapter was attached to the Pixel.

The regular ARM32 launcher now connects adapters normally while keeping optimized native startup and deferred CANdi initialization. On the K2401, the visible Connect path detected Chipsoft, read a fresh VIN, and reached the native main-menu marker in 5.395 seconds. This is a single native-startup measurement, not a universal or full-install time guarantee. Firmware and preference hashes were unchanged by the in-place update. ARM32 remains experimental.

Source commit: b8a24a485bda20770fa6c1aba70c6913f7fcda11. APK SHA-256: 47f3295a3bdcdd4a4f2384b48aefcc2589387295f8215312439a7008d684822f.

OpenSAAB_64_17SEPT26_v0.1.0-preview.21

64-bit ARM update: local emulator health reporting and visible navigation help.

• Offers Send report to OpenSAAB or Keep waiting for suspected unresponsive emulation or an unexpected session exit.
• Detects missing loop heartbeats and unanswered input; a static idle screen alone does not trigger a warning. Slow operations can still trigger a suspected-response warning.
• Records bounded timing evidence. No automatic upload, firmware restart, or vehicle command. Review and explicitly send your report.
• Offers a report after an uncaught Java crash on next launch.
• Restores visible swipe / hold ENTER / EXIT navigation instructions, with tap-for-help.
• Normal user stops no longer overwrite the last error with a shutdown exception.

Install over your existing matching app to retain firmware and settings. Setup 0.3.3 selects the appropriate architecture; no Setup reinstall is needed.

Validation: 99 native tests passed; Android health fault simulations, report-review routing and responsive layout checks passed. New release tested on a disposable ARM64 Android emulator. Physical vehicle and ARM32 performance testing remain user testing.

Source: f0790cd
SHA-256: 1c464ca4d055441af5f2b7aab2df5afcfb978dab426ced6a98b5142f648f0794

OpenSAAB_64_17SEPT26_v0.1.0-preview.20

The Tech2 screen now gets more room. Diagnostic shortcuts are in Actions; tools, reports and updates are in the app menu. Tap the status panel for vehicle and security details. S1–S4, Exit and Keypad stay visible, with responsive portrait and landscape layouts.

Offline menu input no longer waits behind framebuffer decoding. Changed frames use a file observer, hidden-console updates are batched, and arrow navigation avoids unnecessary recovery-state copies. Stale queued arrows expire; Enter/Exit remain ordered.

On the same Pixel 7 offline menu, eight alternating swipes measured a median response of 198 ms versus 459 ms before (57% lower latency, including screenshot sampling overhead). This does not establish live-vehicle or head-unit performance. Mate 20 X testing is pending.

Validation: 99 native tests and Android input, framebuffer, keypad, security-workflow and responsive-layout tests passed. Security transport and SSA processing were not changed.

Install over the existing signed app to retain firmware and settings. OpenSAAB Setup selects the matching architecture; Setup remains 0.3.3. Live support remains Chipsoft with NG 9-3 (9440). Original OpenSAAB source is MPL-2.0; this does not grant rights to third-party firmware.

ARM64 preview.20 was installed and benchmarked on Pixel 7.

OpenSAAB_64_16SEPT26_v0.1.0-preview.18

This update keeps the session shortcuts visible, groups advanced tools, and tracks security collection started directly inside the Tech2 firmware. Get security access, Read DTC, Clear DTC and Engine Data can now continue from the Tech2 “Press ENTER” logo screen. Security details show pre-auth/post-auth timestamps, with advisory Fresh/Stale labels, and the last vehicle connection has its own timestamp.

Turn the ignition ON for the initial vehicle identification, then follow the firmware prompts. Security processing uses the temporary case-sensitive password OpenSAAB; VIN and security request data are shared as explained in the app and privacy notice. Processed security data is imported and firmware restarts automatically. A Fresh label describes data age; it is not an independent confirmation of vehicle authorization.

Install over the existing app to keep settings and firmware. New and existing users can use OpenSAAB Setup to select the correct architecture. Setup remains version 0.3.3.

Current supported live vehicle workflow: Chipsoft with NG 9-3 (9440). Broader adapter/platform support is not established by these tests. Original OpenSAAB source is MPL-2.0; this does not grant rights to third-party firmware.

Validation: Pixel 7 updated in place. The owner reports a successful real-vehicle manual security collection on preview.17, and its receipt confirms OpenSAAB processing and post-auth import. Preview.18 adds the logo-screen shortcut fix; all four shortcut fixtures and Android security instrumentation pass. Connected-vehicle retesting of that final shortcut change remains pending.