With roughly 150k+ S/X units that run v1 MCU hardware, at least, I've been pretty disappointed with the interface interactions in general of v9. In particular:
1. The choppiness of switching between screens
2. The extra steps do things (for example, if you had the cold weather screen up in v8 in recent options, it would take one press to access, now it takes 2 / long press to shut off HVAC instead of quick-press)
3. The movement of features to the bottom along with the reduction in size of the buttons. This causes the user to have to hunt for settings, correct mis-presses, AND all while having their eyes lowered to be bottom of the touchscreen which is real time away from the road.
Tesla is the only one that can fix these problems permanently, but with regards to the interface choppiness, I found a work around to improve performance. Because the NAV is constantly up in the background, this is additional processing power being used to update that screen. But opening the drawing Easter egg and leaving it up while you set your screens makes NAV go away completely and you can go back to enjoy some semblance of smoothness. Try it out for yourself and see.
I've heard both sides of the issue to having NAV up all the time, but owners should be given a choice, like before. 98% of the time, most of us either:
1. Know where we are going already and don't need directions
2. Use NAV just for arrival times and therefore don't need the map either (this would be an actually useful feature: use that top 1" for arrival time estimation, maybe even a re-route button to adjust the re-route threshhold without hunting for the setting, and nix the map until the user pulls down or selects NAV)
1. The choppiness of switching between screens
2. The extra steps do things (for example, if you had the cold weather screen up in v8 in recent options, it would take one press to access, now it takes 2 / long press to shut off HVAC instead of quick-press)
3. The movement of features to the bottom along with the reduction in size of the buttons. This causes the user to have to hunt for settings, correct mis-presses, AND all while having their eyes lowered to be bottom of the touchscreen which is real time away from the road.
Tesla is the only one that can fix these problems permanently, but with regards to the interface choppiness, I found a work around to improve performance. Because the NAV is constantly up in the background, this is additional processing power being used to update that screen. But opening the drawing Easter egg and leaving it up while you set your screens makes NAV go away completely and you can go back to enjoy some semblance of smoothness. Try it out for yourself and see.
I've heard both sides of the issue to having NAV up all the time, but owners should be given a choice, like before. 98% of the time, most of us either:
1. Know where we are going already and don't need directions
2. Use NAV just for arrival times and therefore don't need the map either (this would be an actually useful feature: use that top 1" for arrival time estimation, maybe even a re-route button to adjust the re-route threshhold without hunting for the setting, and nix the map until the user pulls down or selects NAV)