IssueTracker

Description: According to the documentation for the invalidate() method, UI throttling is expected in driving mode, which makes sense. However, I am encountering a consistent 10-second delay between calls to invalidate() and the subsequent response in onGetTemplate(), even when the car is parked. This issue has been reproducible across multiple apps on the Google Play Store, both on a physical Polestar 2 vehicle and in emulator environments.

In addition, the transition from setLoading(true) to setLoading(false)—intended to display loaded data—is also being throttled, which impacts the UI’s responsiveness and makes the app appear sluggish.

Steps to Reproduce:

1. onGetTemplate() is called with setLoading(true) to show a loading template when a new template is displayed.
2. Load data asynchronously, and call invalidate() once the data is ready.
3. onGetTemplate() is called again, updating the template by setting setLoading(false) and filling it with the loaded information.

Expected Behavior:

• In parked mode, there should be no UI throttling between invalidate() and onGetTemplate().
• The transition from setLoading(true) to setLoading(false) should occur smoothly, with no unnecessary delays.

Actual Behavior:

• A 10-second delay is observed in parked mode between invalidate() and onGetTemplate(), contrary to documented behavior.
• The transition from setLoading(true) to setLoading(false) is also throttled, further delaying the UI response and affecting app usability.

Environment:

• Device: Polestar 2 and Android Automotive emulator
• Apps: Multiple apps from Google Play on Android Automotive OS

This persistent throttling in parked mode severely affects user experience, rendering the apps nearly unusable. Resolution of this issue would significantly improve the platform’s usability across Android Automotive apps. Thank you for your attention to this matter.

Thank you for your help.