* Tesla: MADS Screen Button Settings
Adds a Tesla vehicle setting (vehicle bus required) to control how many
fingers activate the MADS screen button, or disable it entirely.
Rebased onto current master:
- Migrated the setting metadata from the deprecated params_metadata.json
(removed in #1862) to the yaml SDUI system: added TeslaMadsScreenButton
to settings_ui_src/pages/vehicle.yaml and recompiled settings_ui.json.
Vehicle-bus gating uses the tesla_has_vehicle_bus capability visibility.
- Bumped opendbc_repo to the latest head of sunnypilot/opendbc#459.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JiSH2KAAueUmDe29xvpuAd
* bump
* Tesla: address MADS Screen Activation review feedback
Default TeslaMadsScreenButton to Off for fresh installs and add a param
migration that seeds existing Tesla installs with 3-Finger, preserving the
previous always-on behaviour. Brand resolves from CarPlatformBundle, falling
back to CarParamsPersistent so auto-fingerprinted Teslas are covered too.
Rename the setting to "MADS Screen Activation", hyphenate the finger-count
labels, and reword the description to use <br> (descriptions render as HTML)
with a note that a higher finger count may reduce accidental activations.
Applied both on-device and in sunnylink.
Also fix test_tesla_with_vehicle_bus_uses_param, which broke once
get_mads_limited_brands started reading TeslaMadsScreenButton from the same
blanket params mock, and add coverage for the screen-button-Off path.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X5icDp7zZ49gpyC2mpCfF1
* bump opendbc
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Jason Wen <haibin.wen3@gmail.com>
* custom data handling
* cleanups
* cleanup
* Update opendbc_repo
* fix missing CarParamsIC handling
* ic srv list and duplicate sp cleanup
* divide lists for better visibility
* fix curvatured, missing services, split lists, cleanup unneccessary
* curvatured time correctness after custom IC structure introduction
* hint for future data quality adaption
* point to master before merge
infiniteCable2