I've noticed that using copilot a lot has introduced screen burn, as I use it for long distance travelling. This mainly is a problem for OLED screens (e.g. Samsung S8).
I suggest having a screen saver type feature. This kicks in after a user configurable amount of time after the last announcement. The screen saver would stop when someone touches the screen or the next announcement is spoken.
The screen saver should have the next direction, the two readings (e.g. ETA, time remaining) as currently configured by the user, the traffic delay and also speed limit. This should slowly move around the screen on a black background to avoid screen burn.