Fatih'sMG4 — ABRP telemetry for an MG4 EH32 on SWI69

A fork of malys/EVABRPUploader (itself a fork of Leon Kernan's ABRP_Uploader)
carrying the changes that make it work on this car. History starts here: the
tree is what matters, and the upstream projects are where the earlier work
belongs.

EVHardware is vendored rather than tracked as a submodule, so one clone
builds.

Telemetry. SOC, battery power and range read as unavailable on SWI69 because
the vendor fallbacks were gated to SWI68 alone, while the property ids they
use are the ones this car publishes — the gates now admit SWI69. Tyre
pressure, the odometer and charge status come from the vendor block too,
since the generic properties for all three are declared here and never
publish. Tyre pressure is confirmed on the vehicle; the other two are not
yet.

Vehicle page. Every signal the car answers, in a table. One that it does not
publish shows a dash: an unimplemented VHAL property returns zero, and
"0 °C" would read as a measurement.

Wi-Fi page. Joins a network the unit already has saved, so a phone hotspot
does not need a trip into Settings on every drive. Tried on the upload tick
and from a button, skipped while already associated. This leans on the unit
being API 28 and the build being platform-signed — getConfiguredNetworks and
enableNetwork are closed to ordinary apps from API 29 — and fails quietly
where that does not hold.

The OTA updater points at this repository. An APK from upstream is signed
with a different key, which Android will not install over a platform-signed
build.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
TCFDONMEZ
2026-09-22 10:45:00 +03:00
co-authored by Claude
commit 2fd7b2dde1
245 changed files with 35594 additions and 0 deletions
+96
View File
@@ -0,0 +1,96 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- EVSuite - component styles. See DESIGN.md section Components.
Generated by tools/sync-tokens.mjs: identical in all six apps, edit only
tools/tokens/styles.xml. The application theme itself stays in values/themes.xml,
because its name changes from one app to the next.
These styles carry the same names everywhere, so a screen can move between
repositories without being renamed. -->
<resources>
<!-- Dialogs inherit the same contrast as everything else: without this they fall
back to Material's default palette, an indoor grey-mauve that is the first
thing to wash out in sunlight. -->
<style name="ThemeOverlay.EV.Dialog" parent="ThemeOverlay.Material3.MaterialAlertDialog">
<item name="colorSurface">@color/ev_surface_raised</item>
<item name="colorOnSurface">@color/ev_text_primary</item>
<item name="colorOnSurfaceVariant">@color/ev_text_secondary</item>
<item name="android:textColorPrimary">@color/ev_text_primary</item>
<item name="buttonBarPositiveButtonStyle">@style/Widget.EV.DialogButton</item>
<item name="buttonBarNegativeButtonStyle">@style/Widget.EV.DialogButton</item>
</style>
<!-- 72dp touch target: the finger aims badly on the road and the screen is far
away. This is the minimum used everywhere in the suite, including where
Material offers something much smaller. -->
<style name="Widget.EV.Button" parent="Widget.Material3.Button">
<item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
<item name="android:minHeight">@dimen/touch_target</item>
<item name="android:textSize">@dimen/text_body</item>
<item name="android:paddingStart">@dimen/spacing_lg</item>
<item name="android:paddingEnd">@dimen/spacing_lg</item>
</style>
<style name="Widget.EV.Button.Outlined" parent="Widget.Material3.Button.OutlinedButton">
<item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
<item name="android:minHeight">@dimen/touch_target</item>
<item name="android:textSize">@dimen/text_body</item>
<item name="android:paddingStart">@dimen/spacing_lg</item>
<item name="android:paddingEnd">@dimen/spacing_lg</item>
</style>
<!-- Dialog buttons are the smallest thing in any app and the easiest to miss:
pulled up to the same target as the rest. -->
<style name="Widget.EV.DialogButton" parent="Widget.Material3.Button.TextButton.Dialog">
<item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
<item name="android:minHeight">@dimen/touch_target</item>
<item name="android:minWidth">140dp</item>
<item name="android:textSize">@dimen/text_body</item>
</style>
<!-- A switch that needs a precise tap is a switch that gets missed at 90 km/h. -->
<style name="Widget.EV.Switch" parent="Widget.Material3.CompoundButton.MaterialSwitch">
<item name="android:minHeight">@dimen/touch_target</item>
<item name="android:textSize">@dimen/text_body</item>
<item name="android:textColor">@color/ev_text_primary</item>
</style>
<!-- The only tracked type in the suite. The tracking is what lets it work at the
16sp floor without shouting. -->
<style name="Text.EV.SectionHeader" parent="TextAppearance.Material3.LabelLarge">
<item name="android:textSize">@dimen/text_label</item>
<item name="android:textColor">@color/ev_accent</item>
<item name="android:letterSpacing">0.12</item>
<item name="android:textStyle">bold</item>
</style>
<!-- One Display element per screen: two 32sp numbers competing for attention are
two glances, and the glance is the budget. -->
<style name="Text.EV.Display" parent="TextAppearance.Material3.HeadlineSmall">
<item name="android:textSize">@dimen/text_display</item>
<item name="android:textColor">@color/ev_text_primary</item>
</style>
<style name="Text.EV.Title" parent="TextAppearance.Material3.TitleLarge">
<item name="android:textSize">@dimen/text_title</item>
<item name="android:textColor">@color/ev_text_primary</item>
</style>
<style name="Text.EV.Body" parent="TextAppearance.Material3.BodyLarge">
<item name="android:textSize">@dimen/text_body</item>
<item name="android:textColor">@color/ev_text_primary</item>
</style>
<style name="Text.EV.Secondary" parent="TextAppearance.Material3.BodyMedium">
<item name="android:textSize">@dimen/text_secondary</item>
<item name="android:textColor">@color/ev_text_secondary</item>
</style>
<!-- The suite radius applied to buttons. Material3 buttons are fully rounded by
default, which reads as a different design language from every card and dialog
around them. This lived in EVSwipe only, in a generated file, so the first sync
deleted it — one radius across the suite has to be a token, not a local edit. -->
<style name="ShapeAppearanceOverlay.EV.Button" parent="">
<item name="cornerSize">@dimen/ev_corner</item>
</style>
</resources>