Dan_LA
Member
Rebooting (pressing down both buttons on the wheel) never worked for me.... Power Off worked 100% of times now.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
No audio bug in Model 3
- Thread starter jsmay311
- Start date
Rebooting (pressing down both buttons on the wheel) never worked for me.... Power Off worked 100% of times now.
Encountered the no audio bug again today. Probably the third time I’ve had this. As with the previous two times I was able to fix it by just exiting the car and closing the door and opening the door again just a second later. This has fixed it for me every single time and is much faster than a full power off.
I’ve recently noticed this radio favorite issue as well in 2018.46.2. The last 2 versions I’ve had have been surprisingly buggy. Hopefully 2018.48.x is more solid.
I’ve recently noticed this radio favorite issue as well in 2018.46.2. The last 2 versions I’ve had have been surprisingly buggy. Hopefully 2018.48.x is more solid.
Does not work. Also I haven’t found any evidence that doing the two button reset while holding down the brake pedal is any different than not holding down the pedal. The only two fixed for this are either a complete power off or just exit the car for a second and re-enter.
dhrivnak
Active Member
No luck for me and I am not sure the brake does anything. It is the two scroll wheels that do the reboot.
Dan_LA
Member
That's called rebooting and never worked for me... I had M3 LR for 10k miles, happeened 200 times No Audio. Power off through menu is working fine on new M3P, and also you can get out of car, lock it and unlock it... sometimes works.
eCharcoal
Member
I reported this to tesla and they came to replace the amp and update the software on Wednesday. 3 days later, it’s happening again. Never thought it was hardware related but Tesla said it was. Got car in July but this never happened until November after an update. Will they ever fix this?
Moose408
Member
I encountered my first "no audio" bug today and it came back as soon as I opened the door, closed the door and opened it again.
jbadger
TR#506, MXP, ~3#1206~
I've had this issue a few times over the last 1-2 months, rebooting wouldn't resolve. Worst was the last two days but disappeared when I installed 48.12 but I am guessing it just got out of state and will happen again unless they specifically addressed the issue.
Can’t say this is the case. I got 48.1 two days ago and the no audio bug happened to me for the FIRST time yesterday.
Scroll button reboot did nothing, but something interestingly dangerous did. It seemed like the ui was lagging badly. I was pulling into my garage after waiting for homelink to automatically open the garage door. Nothing happened so I pushed the homelink button again. Nothing happened. So I got out of the car to manually open the garage door and before I got to the keypad, the garage door began to open. I thought “great, there’s a delay but at least homelink worked”. I get back in the car to pull the car into the garage and boom! It starts to close on the car. Luckily I triggered the sensor and the garage door reopened. I realized that the lag in the ui was finally catching up to the time I pushed the homelink button.
So the moral of the story is that went the ui is lagging, the buttons you push might eventually work so be careful.
eCharcoal
Member
I don’t remember which version it was. I could only remember the no audio happened to me on Election Day. I got back into my car after I had voted in the morning, and all audio was gone. I got the software update the night before.
eCharcoal
Member
After going a couple weeks without it happening, it's gotten me twice in the past 2 days on my first drive of the day.
I had sent an earlier email to Tesla customer support about this, and they replied requesting that I call them next time it happened, so I called them when it happened yesterday. But they couldn't do any diagnostic stuff over the phone, so they asked that I schedule an appointment with a mobile repair tech so they could come out and pull my vehicle logs. So I'm supposed to get a call to schedule that appointment shortly.
Sure would be nice if they could just pull the relevant logs remotely / over the air. (Maybe there would be security issues with that? Or the data files are too large?
)
Anyway... I guess I'll report back if I learn anything further.
I had sent an earlier email to Tesla customer support about this, and they replied requesting that I call them next time it happened, so I called them when it happened yesterday. But they couldn't do any diagnostic stuff over the phone, so they asked that I schedule an appointment with a mobile repair tech so they could come out and pull my vehicle logs. So I'm supposed to get a call to schedule that appointment shortly.
Sure would be nice if they could just pull the relevant logs remotely / over the air. (Maybe there would be security issues with that? Or the data files are too large?
)Anyway... I guess I'll report back if I learn anything further.
Update: After providing the local mobile service coordinator guy with a few specific times/days when this had happened in my car so that they could analyze the vehicle logs, he then talked with a Tesla engineer about the issue who said that it was a known issue and would be addressed with an upcoming software fix. So encouraging news.
Hopefully this fix rolls out soon, as it's been happening to me with daily frequency lately.
Hopefully this fix rolls out soon, as it's been happening to me with daily frequency lately.
This bug is super aggravating. For me, like @TEG it always happens when the screen doesn't respond immediately after getting into the car and does a full boot.
Someone else mentioned that driving off with the screen still booting seemed to trigger the no-audio portion of the bug more often, but I couldn't say for sure, will pay more attention.
What's aggravating is that it doesn't seem to affect all cars - why?
Power off while parked for 5 seconds always fixes the issue for me. It is strange that it seems to occur in waves, it'll happen a lot over a couple days, or it might not happen at all for a while.
Someone else mentioned that driving off with the screen still booting seemed to trigger the no-audio portion of the bug more often, but I couldn't say for sure, will pay more attention.
What's aggravating is that it doesn't seem to affect all cars - why?
Power off while parked for 5 seconds always fixes the issue for me. It is strange that it seems to occur in waves, it'll happen a lot over a couple days, or it might not happen at all for a while.