Awesome guide, worked perfectly. Unfortunately all of my music is in the iTunes format which doesn’t seem to work with Tesla, presumably because it’s restricted. Oh well. If I can find my old CDs I might rip them to mp3s and see if that works, but for now streaming off my phone is fine.
Yep, protected iTunes files will not work. There are ways to convert them to a non-protected format and they should work then.
I finally got my USB drive to work and not corrupt: Get a 32gig USB drive (Has to be USB 3.0) Format drive (Fat 32) Partition the drive in 2, 16 gigs each (MUSIC / DASHCAM) Inside the DASHCAM partition, create a folder (TeslaCam) This worked for me, and it has not crashed yet. I tried this same method with all kinds of USB drives, but the only thing that worked was a USB 3.0 drive.
I got this Samsung drive and has been working for a week with no issues https://www.amazon.com/gp/product/B07D7PDLXC/ref=oh_aui_detailpage_o06_s00?ie=UTF8&psc=1
I had a similar problem, but once I made both partitions GPT instead of MBR all the problems went away. It's been working flawlessly for over a week now.
Thank you Thank you Thank you! Great guide. I have used it to create 2 different USBs (instead of 2 partitions on one drive.) Will test this out next week when we get our car. Thanks for putting together such a detailed guide.
I delete the FSCK*.rec files when I get the X. Plug the USB back in and it works. No need to reformat.
I’m using a different ixpand flash drive and have formatted it on my Mac, but the M3 will not see it, I also have the San Disk wirelss connect flash drive and that works perfectly, I don’t understand why the ixpand doesn’t work they are formatted the same and the folders were created as directed
I have both of these San Disk flash drives, as I wanted a way to easily view the video quickly if necessary, I can report that the wireless model records without issues and then you can eject the drive and unplug it from the USB port and then connect to it wirelessly and choose the video and transfer to your phone with the San Disk app, the ixpand doesn’t work, will not show up when plugged into the car. The Lexar also won’t show up in the car and is also formatted as FAT32 with the TelaCam folder
It will be great if San Disk develops their wireless product for TeslaCam storage so you didn’t have to unplug the drive first to get it out of USB MODE, or better yet Tesla could make it so we could just view the recorded files on our vehicles display screens directly.
Seems like sending the saved videos (generated by tapping the icon) to our Tesla account wirelessly would be a perfect feature for the premium connectivity they're charging for these days.
I forgot to say convert to GPT, thanks. so far it's been almost a week and no X. BTW, thanks SomeJoe7777 for the advice.
Thanks for the write up. It worked perfectly for me with a cheapie 256Gb Sandisk Cruzer Glide USB 3.0 available at Costco for $40. The only issue I had was trying to increase the size of the TeslaCam partition to 32GB (to provide for future enhancements so I don't have to reformat and copy back all my music). The 32GB partition wasn't recognized correctly in Win 10 (used "create partition primary size=32768 align=1024"). Not wanting to mess with it anymore I wiped it and set it up following the instructions exactly. Works great for both the dashcam and music. Don't know if this is mentioned anywhere but the Model 3 supports high resolution audio files to 24/192 in Flac and wav formats (in addition to MP3's). Didn't test any other formats (ALAC, APE, etc.). DSF files aren't supported though. Sounds so much better than music from the phone via BT. Thanks @SomeJoe7777
These instructions don't work as described in my Win7 PC. I cannot delete the partitions from the Storage Manager (grayed out), and once I delete them within DISKPART it will let me create 1 partition, but not a 2nd one. When I try to create the 2nd partition, I get this error: CREATE PARTITION PRIMARY ALIGN=1024 Virtual Disk Service Error: The operation is not supported in a non-empty removable disk.
When you created the first partition did you specify the size of the partition? If not then it will use all of the available space on the drive leaving no free space left for additional partitions. Add the “size=XXXX” parameter to the create partition command where XXXX is how large you want to create the partition in MBs.
Mine built per this thread worked fine until I used the save function (which worked). Then I got the X and corrupted files. Looking forward to the next software iteration.