Yes, this. I didn’t think much of it at the times I’ve tried voice commands, but yes, under 20.8 they a really worse than previously, much more non-responsive in areas of known good cellular coverage. Another joyous update.
I was playing with voice commands yesterday and everything worked fine for me over WiFi. I guess the issue is with cellular coverage/reception.
Yes, it does seem to work fine some times (like in my garage with WiFi). But it also fails when I'm streaming music while driving. So it might be a cellular coverage problem, but then I would expect that I couldn't stream music either.
From my experience they buffer some of the streaming in advance. I know I can drive through a dead cellular area and my Spotify playlist continues. But if I try to pick something else to play it complains about no network being available. (I don't know how much it buffers.)So it might be a cellular coverage problem, but then I would expect that I couldn't stream music either.
I wouldn't read that much into it.
Here's an interesting short discussion concerning that topic:
Really interesting. I see parallels in hardware dev as well. But, Teslas are cars, not games or productivity apps for Windows. They need to function consistently and reliably, and fail safely.Here's an interesting short discussion concerning that topic:
OK. Best available vs. very reliable. I'll accept that. But 3 or 4 versions behind, which is what it had been, suggests that at that time they didn't trust the newest versions with the new owners. For now, they do.
That post confounds counts of bug reports vs. bugs vs. other issues. Bugs are when the code doesn't do what it's supposed to do. Other issues include feature requests. Yes, more users means reporting more of the bugs and other issues in the code -- if there's a way to report bugs.Here's an interesting short discussion concerning that topic:
Absolutely.
Completely agree. And we can tell that the author of that article doesn't work anywhere near safety critical systems, or they would have a dramatically different perspective.
In an aerospace environment??
Or how about the medical field? The development process in safety-critical fields is exceptionally methodical, to ensure that bugs DON'T happen. And closing genuine bugs (again, feature requests are not bugs) in the bug tracker is essential.
The longer I've been at this, and read other people's experience, the less confident I am that anything works consistently. 50% pause is very common, perhaps more common than otherwise. I think if the car goes to sleep before it continues that's not good. But nothing that seems to have worked works consistently. for me. Almost always it continues after a few hours, but for those who see it go more than a day, it might be worth requesting a reset from the service center.
Another datapoint here: I’m on the other side. Every update for me (now at 108 of them) has worked to completion without major interruption, usually in about 20 minutes. One of them (perhaps the V11 debacle, can’t exactly remember) took about 45 minutes. All that said, I’ve stopped updating at v2022.20.8 even though I’ve had 6 newer versions downloaded trying to hold onto my radar and reduce the nannyworks.
I watched it pause at 50% while sitting in the car with the heat going during the most recent update. But I will try turning on on Sentry Mode next time.
