BertL
Active Member
Thx for the update. Yes, try the directory name change. Symptoms sound to me more and more like a MP firmware bug perhaps triggered by an underlying hardware problem or something unique HW-wise to your MX compared to some of our older MS, especially since no-one else has yet reported the same issue. I do believe though a lot of Tesla owners just go with the flow and are happy using streaming or bluetooth for their music sources, while some others that care about listening to their own music like us have thrown in the towel, perhaps come up with their own workarounds and may not be coming to this thread any longer, or just don't expect MP to deliver as well as a cheap boom box.Taking out the TeslaCam USB device and moving the music USB to the other port did not work.
I then tried a 2g drive with about 40 songs on it and it did not work.
I then reformatted the drive I was using for TeslaCam, so no TeslaCam folder anymore, put all the music on it and it is not working either.
When I say not working, I am only referring to the USB music source starting up properly. In every case now TuneIn is the default. If I press USB and manually pick a folder and music to play it all works. The car just does not remember that I was using USB as my source.
Oh, I also failed to mention that all the music is MP3.
Also since the car is only 8 months old and I have not taken any trips in it yet, there are almost no navigational destinations in the memory.
I guess I will try changing the directory name.
I may be wrong, but IIRC doesn't a current MX have USB ports both in the front center console and another pair in the back seat? (My MS only has 2 ports in the front console.). If so, be sure you try the scenarios in both the front and back physical ports -- IDK how the physical wiring works and if all the ports end-up running off the same USB chips or even a partially different interface some way back to the CID... worth a try perhaps, but I've now stretched as far as I can trying to come up with other things to try.
At that point, I suggest you call Tesla Service and report the problem -- especially as it appears to be reproducible with two different USB devices (be sure to take both to your service appt.), in multiple ports, and began after the last firmware update. We'll hope you are one of the few with a failing piece of HW that can be replaced and resolves your issue, and you don't get the infamous "We're sorry, but the problem is closed. Hopefully a future firmware patch will resolve your problem." response. (At least in my experience, Tesla never keeps those sort of problems open against your VIN, and then follows-up if it gets resolved like I had both Lexus and MBZ do for me in the past. Similarly, a SvC does not seem to be able to peer into open MP firmware bugs -- or maybe they just no longer take the time to do that extra research with all they have to do -- as well as other mfgr service may be able to.)
Good luck.