Got in the car in the AM - all screens were blank. Waited 30s.. no change, so rebooted (10s). This time the system didn't come back as expected. Called SC and per their direction I let the system sleep for 10-15 mins. Tried to wake up again and still no dice.
Car is with SC now - they are looking into it.
However, in the interest of science, I observed the following
- Car was drivable (R / P/ D) . However did not foster confidence. While still in park, I got the rear steer failed error, and the hot coffee icon ( driver error?) . Coffee icon went away but rear steer error was permanent (you can see on the video below).
- Perhaps it is just my perception, but without the screens
- Overall, drivability suffered. I cant pinpoint what exactly, but the handling was off. May be the rear active steering is really that good - or perhaps the car was only working with the front motor. It was a strange feeling.
- The ride quality went from ethereal "glide" feeling, to a more, manual, unpolished groaning (for reference, I have a 99 Ducati Monster that struggles to maintain anything above 60MPH and has the same high RPM low torque feeling) I could feel the engine overworking - loud and sluggish. It is hard to describe it. I definitely think the rear drive unit was disengaged (you can see it on the video linked below).
- While driving to the SC, I had to go past a trailer at a higher speed (70/75) and I started hearing a dim booming type of a sound. Here is a recording - you can hear the sound starting the 10-11 second mark. I could replicate it consistently in multiple stretches and ensured it wasn't being caused by surrounding traffic. The sound was more pronounced when I took the foot off the accelerator pedal. I am not sure if it was due to wind buffeting across the windshield, or motor regen kicking in. This is part of the service request.
- FWIW My initial hunch was that when the system reboots, the android system looks for the OS boot drive. So perhaps it was stuck trying to read from the USB drive Im using for Halo Secure. I was unable to confirm this hypothesis since the glove compartment was closed and the screens were off ... I was not able to open it and remove the USB to check.
- However, the SC tried to look up similar incidents and mentioned that this might be a module change (not sure which module). So looks like my hunch was likely wrong.
Anyhow.