Skip to content

Releases: ImL1s/telltale

Telltale v1.0.4-beta.2

Pre-release

Choose a tag to compare

@github-actions github-actions released this 23 Aug 17:58

Pre-release. What has been verified, and what has not:

  • The protocol layer passes the simulated ELM327 rigs, including
    framing and fault-injection checks.
  • A physical Samsung phone completed a real Bluetooth LE/GATT session
    over the phone's and Mac's actual radios against the Mac-hosted rig.
  • Not yet verified: the purchased CAR25 adapter, any other physical
    ELM327 adapter, a vehicle ECU/CAN bus, or a real vehicle.
  • docs/verification/test-evidence.md and
    docs/verification/device-verification.md record the exact boundary.

If you have an adapter and a car, this is the build to try. Settings →
匯出紀錄 exports a verbatim transcript of everything the adapter said;
an issue with that file attached is the most useful thing you can send.

預發行版本。 模擬 ELM327、分段與故障注入測試已通過;Samsung 實體手機
也已用真實藍牙無線電與 Android GATT,連上 Mac 主機的 BLE rig。
但 CAR25/購買的實體轉接器、車輛 ECU/CAN 與真車仍未驗證。
詳細證據界線見 docs/verification/。有轉接器又有車的話,這就是該試的版本;
出問題請到「設定 → 匯出紀錄」把逐字紀錄存下來,附在 issue 裡送回來。

Telltale 1.0.4+5

English | 繁體中文 below

A ready-made APK for anyone who would rather not run a Flutter
toolchain. Same source, same features as the Google Play build —
nothing is held back.

File telltale-v1.0.4-beta.2.apk (56M)
SHA-256 adc99d7c49a72247ddaefdedd8512fa6b0eef7ada986988b367ced8ea8d0fb27
Signing certificate 7e97b3dd0b3f11a9a593cf8d182d49032490022938cecaafde90b53d5825414d

This build is signed with the community key, not the Google Play
key.
It therefore cannot update — and cannot be updated by — an
install that came from the Play Store; Android will refuse with a
signature mismatch. Export any diagnostic records you need before
switching: uninstalling removes Telltale's local app data. The two keys
are separate on purpose: sharing them would let anything that compromised
CI publish a replacement for a store install.

Verify before installing:

sha256sum telltale-v1.0.4-beta.2.apk

給不想自己架 Flutter 環境的人的現成 APK。原始碼相同、功能與 Google Play
版完全一致,沒有閹割。

這份是社群簽章金鑰簽的,不是 Google Play 的上架金鑰。 所以它無法用來更新
從 Play 商店安裝的版本,反之亦然 —— Android 會以簽章不符拒絕。要換過去請先解除
安裝;解除安裝會刪除 Telltale 本機資料,請先匯出要保留的診斷紀錄。兩把金鑰刻意
分開:共用的話,任何入侵 CI 的人就能發布一個能取代商店安裝的版本。

安裝前請先核對 SHA-256。

Telltale v1.0.3-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Aug 09:00

Pre-release. What has been verified, and what has not:

  • Every screen walked against the built-in demo simulator, and the
    protocol layer run in CI against an ELM327 simulator this project did
    not write — plus a second one, on the private side, whose server
    cannot be published.
  • Never connected to a real vehicle. Bluetooth LE is verified as
    far as scanning and permissions; no ELM327 adapter of any kind has
    been connected to this build.
  • TEST_EVIDENCE.md and DEVICE_VERIFICATION.md record exactly what
    was checked, including the checks that turned out to be worthless.

If you have an adapter and a car, this is the build to try. Settings →
匯出紀錄 exports a verbatim transcript of everything the adapter said;
an issue with that file attached is the most useful thing you can send.

預發行版本。 每個畫面都對內建模擬器走過,協定層在 CI 裡跑過一個
第三方 ELM327 模擬器(私有端還有第二個,它的 server 無法公開),
從未連過真車 —— 藍牙 LE 只驗到掃描與權限,
沒有連過任何一顆 ELM327 轉接器。有轉接器又有車的話,這就是該試的版本;
出問題請到「設定 → 匯出紀錄」把逐字紀錄存下來,附在 issue 裡送回來。

Telltale 1.0.3+4

English | 繁體中文 below

A ready-made APK for anyone who would rather not run a Flutter
toolchain. Same source, same features as the Google Play build —
nothing is held back.

File telltale-v1.0.3-beta.1.apk (56M)
SHA-256 3de70872334e3e5a8436dfa3cb50c62e1ddfbc75d83f7fa06024bc3ce0335b1b
Signing certificate 7e97b3dd0b3f11a9a593cf8d182d49032490022938cecaafde90b53d5825414d

This build is signed with the community key, not the Google Play
key.
It therefore cannot update — and cannot be updated by — an
install that came from the Play Store; Android will refuse with a
signature mismatch. Uninstall one before installing the other. The two
keys are separate on purpose: sharing them would let anything that
compromised CI publish a replacement for a store install.

Verify before installing:

sha256sum telltale-v1.0.3-beta.1.apk

給不想自己架 Flutter 環境的人的現成 APK。原始碼相同、功能與 Google Play
版完全一致,沒有閹割。

這份是社群簽章金鑰簽的,不是 Google Play 的上架金鑰。 所以它無法用來更新
從 Play 商店安裝的版本,反之亦然 —— Android 會以簽章不符拒絕。要換過去請先解除
安裝。兩把金鑰刻意分開:共用的話,任何入侵 CI 的人就能發布一個能取代商店安裝的版本。

安裝前請先核對 SHA-256。

Telltale v1.0.2-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Aug 07:34

Pre-release. What has been verified, and what has not:

  • Every screen walked against the built-in demo simulator, and the
    protocol layer run in CI against an ELM327 simulator this project did
    not write — plus a second one, on the private side, whose server
    cannot be published.
  • Never connected to a real vehicle. Bluetooth LE is verified as
    far as scanning and permissions; no ELM327 adapter of any kind has
    been connected to this build.
  • TEST_EVIDENCE.md and DEVICE_VERIFICATION.md record exactly what
    was checked, including the checks that turned out to be worthless.

If you have an adapter and a car, this is the build to try. Settings →
匯出紀錄 exports a verbatim transcript of everything the adapter said;
an issue with that file attached is the most useful thing you can send.

預發行版本。 每個畫面都對內建模擬器走過,協定層在 CI 裡跑過一個
第三方 ELM327 模擬器(私有端還有第二個,它的 server 無法公開),
從未連過真車 —— 藍牙 LE 只驗到掃描與權限,
沒有連過任何一顆 ELM327 轉接器。有轉接器又有車的話,這就是該試的版本;
出問題請到「設定 → 匯出紀錄」把逐字紀錄存下來,附在 issue 裡送回來。

Telltale 1.0.2+3

English | 繁體中文 below

A ready-made APK for anyone who would rather not run a Flutter
toolchain. Same source, same features as the Google Play build —
nothing is held back.

File telltale-v1.0.2-beta.1.apk (56M)
SHA-256 9c3e21ec94720e10d85cc2b44261f43939f31f0016cd17a3630f132b56299f67
Signing certificate 7e97b3dd0b3f11a9a593cf8d182d49032490022938cecaafde90b53d5825414d

This build is signed with the community key, not the Google Play
key.
It therefore cannot update — and cannot be updated by — an
install that came from the Play Store; Android will refuse with a
signature mismatch. Uninstall one before installing the other. The two
keys are separate on purpose: sharing them would let anything that
compromised CI publish a replacement for a store install.

Verify before installing:

sha256sum telltale-v1.0.2-beta.1.apk

給不想自己架 Flutter 環境的人的現成 APK。原始碼相同、功能與 Google Play
版完全一致,沒有閹割。

這份是社群簽章金鑰簽的,不是 Google Play 的上架金鑰。 所以它無法用來更新
從 Play 商店安裝的版本,反之亦然 —— Android 會以簽章不符拒絕。要換過去請先解除
安裝。兩把金鑰刻意分開:共用的話,任何入侵 CI 的人就能發布一個能取代商店安裝的版本。

安裝前請先核對 SHA-256。

Telltale v1.0.1-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Aug 04:22

Pre-release. What has been verified, and what has not:

  • Every screen walked against the built-in demo simulator, and the
    protocol layer run in CI against an ELM327 simulator this project did
    not write — plus a second one, on the private side, whose server
    cannot be published.
  • Never connected to a real vehicle. Bluetooth LE is verified as
    far as scanning and permissions; no ELM327 adapter of any kind has
    been connected to this build.
  • TEST_EVIDENCE.md and DEVICE_VERIFICATION.md record exactly what
    was checked, including the checks that turned out to be worthless.

If you have an adapter and a car, this is the build to try. Settings →
匯出紀錄 exports a verbatim transcript of everything the adapter said;
an issue with that file attached is the most useful thing you can send.

預發行版本。 每個畫面都對內建模擬器走過,協定層在 CI 裡跑過一個
第三方 ELM327 模擬器(私有端還有第二個,它的 server 無法公開),
從未連過真車 —— 藍牙 LE 只驗到掃描與權限,
沒有連過任何一顆 ELM327 轉接器。有轉接器又有車的話,這就是該試的版本;
出問題請到「設定 → 匯出紀錄」把逐字紀錄存下來,附在 issue 裡送回來。

Telltale 1.0.1+2

English | 繁體中文 below

A ready-made APK for anyone who would rather not run a Flutter
toolchain. Same source, same features as the Google Play build —
nothing is held back.

File telltale-v1.0.1-beta.1.apk (56M)
SHA-256 7ccff183842c426d4b21e415925741784e9ca0528c84dbbf3c1b986f8d521a1c
Signing certificate 7e97b3dd0b3f11a9a593cf8d182d49032490022938cecaafde90b53d5825414d

This build is signed with the community key, not the Google Play
key.
It therefore cannot update — and cannot be updated by — an
install that came from the Play Store; Android will refuse with a
signature mismatch. Uninstall one before installing the other. The two
keys are separate on purpose: sharing them would let anything that
compromised CI publish a replacement for a store install.

Verify before installing:

sha256sum telltale-v1.0.1-beta.1.apk

給不想自己架 Flutter 環境的人的現成 APK。原始碼相同、功能與 Google Play
版完全一致,沒有閹割。

這份是社群簽章金鑰簽的,不是 Google Play 的上架金鑰。 所以它無法用來更新
從 Play 商店安裝的版本,反之亦然 —— Android 會以簽章不符拒絕。要換過去請先解除
安裝。兩把金鑰刻意分開:共用的話,任何入侵 CI 的人就能發布一個能取代商店安裝的版本。

安裝前請先核對 SHA-256。