Feature Request: Daylight Saving Time Handling – Leapmotor B10

We’ve identified an issue with time synchronisation on the Leapmotor B10 in regions that observe daylight saving time, specifically in Melbourne, Australia. Problem: The vehicle’s automatic time setting (based on geolocation) does not correctly apply daylight saving time (DST). As a result, the displayed time is consistently one hour behind during DST periods. Attempts to manually correct the time are not persistent. The system appears to override manual changes after a reboot, sleep cycle, or system update, reverting to the incorrect automatically set time. Impact: Incorrect time displayed in vehicle Potential confusion for scheduling, navigation, and time-dependent functions Poor user experience due to lack of control or persistence Suggested Improvements (Simple Fixes): Manual DST Toggle Add a user-accessible setting to enable/disable daylight saving time. This would provide a quick and reliable workaround where automatic detection fails. Improved Time Server / Timezone Handling Review and update the backend time source (e.g., NTP/timezone database) to ensure accurate DST handling for Australian regions. Ensure the system correctly maps Melbourne to AEDT/AEST transitions. Respect Manual Time Overrides If a user manually sets the time, provide an option to prevent automatic override. Alternatively, prompt the user before reverting to automatic time. Explicit Timezone Selection Allow users to manually select their timezone (e.g., “Melbourne / AEDT”) rather than relying solely on GPS-based detection. Requested Outcome: Accurate and persistent time display regardless of DST, with user control as a fallback.