barjohn
Member
I just sent the bug report email below to Tesla. I thought I would share it. I'm sure I didn't cover all of the bugs but thought I hit on the major ones.
Dear Customer Service,
I’m not sure if this is the correct email to send bug reports; however, the voice method in the car does not seem to result in anything happening or any response from Tesla so it does not appear to be of much value. Additionally, it can be difficult to submit a bug report while driving. Having to compose your thoughts and provide a meaningful report doesn’t come naturally under those conditions unless comments like “bug report, holy crap I just got the *sugar* scared out of me and my wife say don’t use AP again” counts as a bug report.
I’m sure you are probably aware of most of these bugs but in case you aren’t here is my list:
1. Phantom braking continues to be an issue. I will say that it doesn’t appear as often and it wasn’t as jarring this last time but it is something that needs to be addressed before it causes an accident.
2. AP still gets confused on freeways when it encounters an exit (and here in CA the exit lanes do not have dashed lines as in some other states). If the exit is to the right and you are in the rightmost lane, it will attempt to exit, display confusion and may correct itself or may require manual intervention. It can be confusing to the drivers behind you. If there is a merge lane on the right coming onto the freeway, it confuses AP and ping ponging is a frequent result. If you are in the left lane and the exit is a Y junction, AP will try to take the exit and then become confused and straddle between the exit and the normal continuation path. I was really hoping that V9 would be map aware and recognize it location and the proper course of action absent a turn signal or with a turn signal (continue on main route or exit).
3. AP on turns to the right when traveling next to a solid barrier tends to go to the outside left rather than the inside right or even center of the lane and this requires manual intervention as there would not be sufficient time to correct when inches from a wall at 70+mph. HOV lanes here in southern CA are really bad about that. Similar issues exist on exits where the car doesn’t slow down quite enough for the sharpness of the turn.
4. The new DASHCAM feature need a way to safely eject the memory device to avoid corrupting files and the same is true when stopping and starting the vehicle. I pressed the icon to perform a Save and instead of saving the last 10 minutes it saved only the last minute.
5. The Homelink function to use geofencing to close the garage door on leaving is hit and miss. Most of the time it doesn’t work and I must manually perform the function. Now that the Homelink button is far right on the screen it is hard to reach to manually utilize. This is a function used almost everyday and should be more readily available and on the left side of the screen.
6. The web browser seems to hang every-time it losses a connection which is very frequent on LTE. It’s performance on LTE is slow and sluggish but actually usable on WiFi in my garage when not hung. The only way to unhang the browser is to reboot the screen. This is a pretty serious software bug.
7. The animated visualizations of surrounding objects (different types of vehicles, bicycles, motorcycles, etc.) lacks stability as objects jitter around, appear to go into your lane or run over you etc. even when stopped at a traffic light. Rather than use all of the computing needed to do this display, why not just stitch together the the camera feeds to create a birds-eye view showing the actual video images and boxes around objects being tracked. Some objects may appear distorted because of the different perspectives captured by each camera but the images should be much more stable and all the data a driver needs would be there to know the car was aware of each object and its location. One other difficulty with the animated views is they don’t provide an adequate perspective of distance to the objects. For example, one doesn’t see a car behind you unless it is very close and the car in front appears to be much further away than it actually is. The scaling perspective is just off.
8. The media player is frequently hung and needs to be restarted in some unintuitive ways to get it connected again and working. This bug (though not as pronounce) has been here for version 8.1 too.
9. AP Parking: Parking assist very rarely identifies parking opportunities even when driving slowly by spaces of either orientation. When it does display the P there is no conceivable parking space to be had. It will do this when in the middle lane stopped at a traffic light and you are surrounded by cars with no space that would fit a vehicle between them. However, you can drive by what is clearly an open space with cars at both ends and room for the car and it doesn’t see it as a parking space. As a result, I haven’t found this feature to be of much use. Further, it needs to identify parking spaces by the markings on the pavement or by the physical space available of adequate size and then let the human override its selection if for some reason it isn’t a suitable space to park in.
10. This is more of a feature request. Navigation needs two important features, 1) Waypoints so we can plan out a complete trip (like a abetterrouteplanner.com provides) and 2) give us alternate routes to chose from including a scenic route when available.
Thank you for looking into these bugs and hopefully providing a fix in a future update.
Dear Customer Service,
I’m not sure if this is the correct email to send bug reports; however, the voice method in the car does not seem to result in anything happening or any response from Tesla so it does not appear to be of much value. Additionally, it can be difficult to submit a bug report while driving. Having to compose your thoughts and provide a meaningful report doesn’t come naturally under those conditions unless comments like “bug report, holy crap I just got the *sugar* scared out of me and my wife say don’t use AP again” counts as a bug report.
I’m sure you are probably aware of most of these bugs but in case you aren’t here is my list:
1. Phantom braking continues to be an issue. I will say that it doesn’t appear as often and it wasn’t as jarring this last time but it is something that needs to be addressed before it causes an accident.
2. AP still gets confused on freeways when it encounters an exit (and here in CA the exit lanes do not have dashed lines as in some other states). If the exit is to the right and you are in the rightmost lane, it will attempt to exit, display confusion and may correct itself or may require manual intervention. It can be confusing to the drivers behind you. If there is a merge lane on the right coming onto the freeway, it confuses AP and ping ponging is a frequent result. If you are in the left lane and the exit is a Y junction, AP will try to take the exit and then become confused and straddle between the exit and the normal continuation path. I was really hoping that V9 would be map aware and recognize it location and the proper course of action absent a turn signal or with a turn signal (continue on main route or exit).
3. AP on turns to the right when traveling next to a solid barrier tends to go to the outside left rather than the inside right or even center of the lane and this requires manual intervention as there would not be sufficient time to correct when inches from a wall at 70+mph. HOV lanes here in southern CA are really bad about that. Similar issues exist on exits where the car doesn’t slow down quite enough for the sharpness of the turn.
4. The new DASHCAM feature need a way to safely eject the memory device to avoid corrupting files and the same is true when stopping and starting the vehicle. I pressed the icon to perform a Save and instead of saving the last 10 minutes it saved only the last minute.
5. The Homelink function to use geofencing to close the garage door on leaving is hit and miss. Most of the time it doesn’t work and I must manually perform the function. Now that the Homelink button is far right on the screen it is hard to reach to manually utilize. This is a function used almost everyday and should be more readily available and on the left side of the screen.
6. The web browser seems to hang every-time it losses a connection which is very frequent on LTE. It’s performance on LTE is slow and sluggish but actually usable on WiFi in my garage when not hung. The only way to unhang the browser is to reboot the screen. This is a pretty serious software bug.
7. The animated visualizations of surrounding objects (different types of vehicles, bicycles, motorcycles, etc.) lacks stability as objects jitter around, appear to go into your lane or run over you etc. even when stopped at a traffic light. Rather than use all of the computing needed to do this display, why not just stitch together the the camera feeds to create a birds-eye view showing the actual video images and boxes around objects being tracked. Some objects may appear distorted because of the different perspectives captured by each camera but the images should be much more stable and all the data a driver needs would be there to know the car was aware of each object and its location. One other difficulty with the animated views is they don’t provide an adequate perspective of distance to the objects. For example, one doesn’t see a car behind you unless it is very close and the car in front appears to be much further away than it actually is. The scaling perspective is just off.
8. The media player is frequently hung and needs to be restarted in some unintuitive ways to get it connected again and working. This bug (though not as pronounce) has been here for version 8.1 too.
9. AP Parking: Parking assist very rarely identifies parking opportunities even when driving slowly by spaces of either orientation. When it does display the P there is no conceivable parking space to be had. It will do this when in the middle lane stopped at a traffic light and you are surrounded by cars with no space that would fit a vehicle between them. However, you can drive by what is clearly an open space with cars at both ends and room for the car and it doesn’t see it as a parking space. As a result, I haven’t found this feature to be of much use. Further, it needs to identify parking spaces by the markings on the pavement or by the physical space available of adequate size and then let the human override its selection if for some reason it isn’t a suitable space to park in.
10. This is more of a feature request. Navigation needs two important features, 1) Waypoints so we can plan out a complete trip (like a abetterrouteplanner.com provides) and 2) give us alternate routes to chose from including a scenic route when available.
Thank you for looking into these bugs and hopefully providing a fix in a future update.
