Today I was midway into an hour and twenty minute long drive, mostly highway but several times traffic came to stop for quite some time. Unfortunately I received a few phone calls and I could hear the caller through the Tesla speakers but they could not hear me talk. While stopped in traffic I disabled autopilot, I then disabled full self driving beta in settings, then reengaged autopilot (normal highway stack) to deal with stop and go traffic. I figured maybe the phone was at fault so I grabbed it turn bluetooth off then on, of course autopilot complained right away even though I had a hand on wheel, was moving 1-2 mph and coming back to a stop and was looking forward so I torqued the wheel. No problem there. Bluetooth did not fix the issue and the caller called back same problem, could hear them, they couldn't hear me. This time I reset my phone, of course this requires me to grab phone to do pattern since you cant use fingerprint on reboot. Again autopilot noticed this, nag me, and I acknowledged immediately. My calling feature was still not resolved - in traffic there was no way to answer phone or exit freeway. This time I had take the call so I disabled bluetooth on tesla screen and put the phone itself on speaker. This time, with only a second notice, autopilot disengaged and told me I could not use for rest of drive. Fine. While sitting in more traffic I restarted the tesla computer by holding the steering wheel buttons and used my phone's speaker to take the call. After the tesla rebooted it took control of the call and worked fine, so the problem was with Tesla bluetooth side of communication not the phone after all that All things fine I thought. and I continue driving home for another 30 minutes without autopilot since I didnt want to get off the freeway, pull over, park and start a new 'drive'.
Unfortunately I got back in the car for another trip a bit later and was greeted with a FSD beta strike for forced autopilot disengagement. Basically I learned it doesn't matter if you have FSD beta turned off in the settings you still get a FSD beta strike if you get a forced disengagement with normal highway autopilot. (or at the very least you do if you disabled FSD beta during the same 'drive' like I did, its possible the 'strike' and 'aggressive monitoring' function checks to see if FSD beta is enabled at the beginning of the 'drive' and assumes it is one the entire 'drive', even if you turn it off during that drive, dunno and I am not going to try to start with it off and intentionally get a forced disengagement on non fsd autopilot).
Unfortunately I got back in the car for another trip a bit later and was greeted with a FSD beta strike for forced autopilot disengagement. Basically I learned it doesn't matter if you have FSD beta turned off in the settings you still get a FSD beta strike if you get a forced disengagement with normal highway autopilot. (or at the very least you do if you disabled FSD beta during the same 'drive' like I did, its possible the 'strike' and 'aggressive monitoring' function checks to see if FSD beta is enabled at the beginning of the 'drive' and assumes it is one the entire 'drive', even if you turn it off during that drive, dunno and I am not going to try to start with it off and intentionally get a forced disengagement on non fsd autopilot).
Last edited: