Differences

This shows you the differences between two versions of the page.

--- dev [2026/08/09 14:04] – external edit 127.0.0.1
+++ dev [2026/08/18 21:47] (current) – external edit 127.0.0.1
@@ Line 10: / Line 10: @@
 ^ App ^ What it does ^ Download ^
-| **OpenAiways Connect** | Automatically connects to a given Wi-Fi and enables ADB-over-Wi-Fi. | {{:openaiways_connect.apk|openaiways-connect.apk}} |
+| **OpenAiways Connect** | Automatically connects to a given Wi-Fi and enables ADB-over-Wi-Fi. | [[https://codeberg.org/noonscoomo/openaiways/raw/branch/main/android-connect/openaiways-connect.apk|openaiways-connect.apk]] |
 | **OpenAiways Telemetry** | Reads CAN signals and publishes them to MQTT with Home Assistant auto-discovery. | {{:openaiways_telemetry.apk|openaiways-telemetry.apk}} |
 | **OpenAiways Terminal** | A VT100 terminal with an advanced keyboard; runs as system, or as **root** if you press the **su** button . | {{:openaiways_terminal.apk|openaiways-terminal.apk}} |
@@ Line 24: / Line 24: @@
 Add your Wi-Fi networks (SSID + password, as a priority list) and tick **ADB**. After boot it reconnects Wi-Fi and re-enables adb-over-Wi-Fi.
+Source: https://codeberg.org/noonscoomo/openaiways/src/branch/main/android-connect
 ==== OpenAiways Telemetry ====
@@ Line 78: / Line 80: @@
 Several of these apps declare **''sharedUserId="android.uid.system"''** and use ''signature''-level permissions, so they must be signed with the **platform key** — the key the device's own framework is signed with. Android only grants that system identity to an app whose signing certificate matches the platform's.
-**The head unit was never re-keyed.** It is a Freescale/NXP **i.MX6 Android BSP** build, and the OEM shipped it signed with the BSP's **public test key** instead of a private release key — so signing an app with that same public key is enough to run as system. The key is self-signed:
+**The head unit was never re-keyed.** (at least for my 1.7.0 firmware) It is a Freescale/NXP **i.MX6 Android BSP** build, and the OEM shipped it signed with the BSP's **public test key** instead of a private release key — so signing an app with that same public key is enough to run as system. The key is self-signed:
   Subject : C=US, O=Android, CN=Android, emailAddress=android@freescale.com
@@ Line 134: / Line 136: @@
 probe (it already binds ''ICanbusService'') — read or command any [[cansignals|key]] straight from adb.
 See **[[canbus#probing_signals_live|CAN bus → Probing signals live]]**.
+===== Also: the ESP32-S3 companion (separate hardware) =====
+Not a head-unit app — a standalone **ESP32-S3** you wire into the car, for people who don't want to (or can't) get onto the head unit at all. One board does four things at once:
+  * **Talks to the TBox over BLE** (BlueGate protocol) → **preconditioning** and **remote control** (lock/unlock/flash lights/trunk/windows).
+  * **Reads a BLE OBD2 dongle** (ELM327) → SoC, HV voltage/current, cell voltages, temperatures; kept in flash so the last-known values survive when the car is off/unreachable.
+  * **Publishes to MQTT with Home Assistant auto-discovery** — sensors plus Precondition/Lock/Unlock/Flash/Trunk controls appear automatically in HA.
+  * **Runs a Wi-Fi hotspot + web dashboard** at the same time as the home-Wi-Fi/MQTT link, so you can control/monitor from a phone even with no home Wi-Fi nearby. Firmware updates go out **over Wi-Fi** after the first USB flash.
+A prebuilt image and a browser-based flasher (no toolchain needed) are on its own page:
+  https://codeberg.org/noonscoomo/openaiways/src/branch/main/esp32-companion
+//🤖 AI-assisted development — reviewed before trusting it on a real vehicle, same disclaimer as the apps above.//