diff --git a/FIRMWARE.md b/FIRMWARE.md index 99bd678..c74c5a0 100644 --- a/FIRMWARE.md +++ b/FIRMWARE.md @@ -11,23 +11,12 @@ development. It must not be treated as a vendor specification. | Android | 9 (Pie) — **API 28** | | Chipset | MediaTek **MT2712** | | Device | `mt2712_saic_eh32` (eh32 = MG4) | -| Display | Sources disagree, see below. The Logs tab's **SCREEN** line shows what the car reports. | +| Display | **1920×720 px @ 160 dpi**; the app window is **1778×720 px** (≈1778×640 dp for layouts), the car's own sidebar taking the rest. Confirmed on the car 2026-10-18 (Logs → SCREEN, `SWI68`). | | Emulator display profile | **1920×720 @ 160 dpi** | +| `ro.build.mtk2712.vehicle_type` | `AS28` (a vehicle type code; the paint colour is not among the system properties) | -**Display, unconfirmed.** Three figures are in circulation: - -- **1920×720 px**, the figure this project has used (emulator profile, layouts). -- **1280×480**, from [EVProfile's README](https://github.com/malys/EVProfile) ("forced - landscape"). That is exactly 1920×720 px at 240 dpi expressed in dp, the unit layouts use — - so it may be the same panel at a higher density. EVProfile also notes that this platform lets - the density be changed per app. -- An app window of **1778×720**, reported upstream: the car's own sidebar taking part of the - width. - -The app has worked on the car with layouts designed at 1920×720 dp, which fits 160 dpi better -than 240 (checked on the emulator: at 240 dpi the sidebar needs scrolling and the Overview's -cards no longer fit). Since 2.16.2 the Logs tab shows the panel's pixels and density and the -app window in px and dp; a photo of that line settles it. +EVProfile's README gives the display as 1280×480. That is 1920×720 px at 240 dpi expressed in +dp; on this car the density is 160 dpi, so it does not apply here. ## Signing caveat @@ -58,5 +47,5 @@ follow the same path. See `AGENTS.md` for the full per-signal split. ## Emulator fidelity The `mise` emulator tasks use an API 33 automotive AVD for the car service and an API 28 -AVD at **1920×720 @ 160 dpi** for the screen (see "Display, unconfirmed" above). Neither exposes the SAIC vendor properties, +AVD at **1920×720 @ 160 dpi** for the screen, as on the car. Neither exposes the SAIC vendor properties, so vehicle-specific behaviour still requires on-vehicle validation. diff --git a/SPECS.md b/SPECS.md index e4e28a9..af3ee3e 100644 --- a/SPECS.md +++ b/SPECS.md @@ -48,10 +48,12 @@ Current: app 2.14.2, server 2.5.0 (pinned by digest in `k8s/server.yaml`). dashboard queries return data). - [x] Manifests validated offline (kubeconform, with Traefik CRDs). **Applied by Nils only.** - [ ] Check Grafana's host in `k8s/ingress.yaml` (placeholder `car-grafana.k8s.stinnesbeck.com`). -- [ ] Screen size and density on the car: Logs → SCREEN (2.16.2), see FIRMWARE.md. +- [x] Screen on the car: 1920×720 px at 160 dpi, app window 1778×720 px (Logs → SCREEN). +- [x] Car-colour probe on the car: only `ro.build.mtk2712.vehicle_type = AS28`; the paint colour + is not in the system properties. It may be in the VHAL (a debug-build VhalProbe listing + would tell); until then the accent is chosen by hand. - [ ] Not yet tried on the car: live data straight to ABRP (2.11), Enter on phone (2.12), accent - colours and the car-colour probe on the Logs tab (2.14; a photo of its list decides whether - the accent can follow the paint automatically), right-aligned values (2.14.1). + colours (2.14), right-aligned values (2.14.1). ### Signals the car does not provide @@ -110,6 +112,9 @@ tyre pressures, GPS (lat, lon, elevation, heading) and the is_* flags. It does * INGEST_TOKEN) into git and pushed it. Commit amended and force-pushed; both values regenerated in the now gitignored `k8s/secrets.yaml` (since moved to `k8s/secrets/secrets.yaml`, outside `kubectl apply -f k8s/`). Filled-in secrets live only there from now on. +- 2026-10-18 — From the car (2.16.2): screen 1920×720 px at 160 dpi with a 1778×720 px app + window, so EVProfile's 1280×480 does not apply; colour probe found only `vehicle_type = AS28`. + FIRMWARE.md, mise.toml and SPECS.md say so. - 2026-10-18 — App 2.16.2: Logs → SCREEN shows the panel's pixels and density and the app window in px and dp. The MG4's display figures disagree (1920×720 px used here; EVProfile lists 1280×480, which is 1920×720 at 240 dpi in dp; upstream reported a 1778×720 window); FIRMWARE.md diff --git a/mise.toml b/mise.toml index 89865a6..b9e8889 100644 --- a/mise.toml +++ b/mise.toml @@ -56,8 +56,8 @@ BUILD_TOOLS = "36.0.0" # car build installs there as the system user.) # # None of this replaces a test on the car. -# Target density: 160 dpi. Screen 1920x720 px; the density on the car is not confirmed -# (FIRMWARE.md, "Display, unconfirmed"). Reference firmware: SWI68-29958-1300R69. +# Screen 1920x720 px at 160 dpi, as on the car (app window 1778x720). Reference firmware: +# SWI68-29958-1300R69. EMU_CAR_AVD = "evabrp-car" EMU_CAR_IMAGE = "system-images;android-33;android-automotive;x86_64"