My brother and I both have Model 3's. A few days ago he mentioned that he ran into a problem were he was getting zero audio from any of the speakers -- no music, no chimes, no beeps, no turn signal "clicks"... No nothing. Everything else seemed normal, but it was as if the speakers were simply disconnected.
A scroll wheel reset didn't fix it. But it eventually went back to normal on its own after turning the car off.
Then today the same thing happened to me. Again a scroll wheel reset didn't fix it. I tried to submit a bug report at the time, but voice commands were non-functional.
After turning the car off and leaving it and coming back a couple hours later, it had reverted back to normal operation.
I found a few sparse mentions in forums of similar (temporary) issues in S's and X's, but nothing specific to the Model 3 or specific to the last few days or recent software versions. Given that this happened to both of the only two Model 3 owners I know in a span of just a few days, it seems like an awfully big coincidence, so I'm wondering if there might be a bug introduced in a recent software update. (I believe we were both on 2018.42.3 when it happened.)
Anyone else run into the same problem, either recently or ever?
A scroll wheel reset didn't fix it. But it eventually went back to normal on its own after turning the car off.
Then today the same thing happened to me. Again a scroll wheel reset didn't fix it. I tried to submit a bug report at the time, but voice commands were non-functional.
After turning the car off and leaving it and coming back a couple hours later, it had reverted back to normal operation.
I found a few sparse mentions in forums of similar (temporary) issues in S's and X's, but nothing specific to the Model 3 or specific to the last few days or recent software versions. Given that this happened to both of the only two Model 3 owners I know in a span of just a few days, it seems like an awfully big coincidence, so I'm wondering if there might be a bug introduced in a recent software update. (I believe we were both on 2018.42.3 when it happened.)
Anyone else run into the same problem, either recently or ever?