On my first FSD beta 10.5 drive only, I had some “red hands takeover immediately” warning but I missed the text of the alert to know whether it was in-cabin camera detected inattentiveness, or just the old regular hands on the wheel alert. It was a small access road between the parking lot I’d exited and the “real” road. I’d started navigation & engaged FSD beta by that point already just fine in the past, but this time it slowed down and said I’d arrived, then freaked out and disengaged. For whatever reason, the grey AP auto steer and TACC available symbols disappeared, as well as the green/blue and grey path finding snake of dots. I tried stopping while still on that small access road without cars around, shifting to park, then back into drive, but even getting on the road with clear lane markings, the grey auto steer and TACC available symbols wouldn’t show, causing me to wonder if I’d just gotten my first strike.
It was a road with traffic behind me and nowhere to stop safely for a bit so I drove manually, skipping my freeway entrance because I wanted to try stopping and getting out of the car to re-enable AP.
I got to a safe u-turn area, flipped around and pulled onto the shoulder, but just as I came around the grey auto steer and TACC available symbols showed up again, as well as the glorious FSD beta green/blue & grey pathfinding snake of dots emanating from the car graphic. It had maybe been a mile of driving without them. So I didn’t bother shifting into park and just continued onto the freeway with no AP issue. I was able to use it and FSD beta after exiting the freeway 10 miles later.
That weird behavior only happened the first FSD beta drive after upgrading to 10.5. Did you get confirmed feedback somehow that you received a first strike? Or of AP jail?