This post is more informational than anything else. Perhaps my experiences will help someone else fix these problems permanently.
I have had numerous issues with my 8.4 system since I picked up my 2014WK2 in June. Much of my problem is around the SD card reader. All the following experience is while the system was running 13.15.4, and my card is a 32GB SANDisk which Uconnect has told me is fully compatible, and for the purposes of these tests, I have had only around 100 songs on the card.
I am currently using doubletwist for windows to transfer my desired MP3 to the card. Doubletwist does a GREAT job, allowing me to select tracks, artists, albums, or playlists and just drag it to the card which appears as a destination on the left menu. It it creates folders for the artists and albums and recreates the playlists as they are written to the card so that the playlists point to the right location on the card. Easy Peasy
. (FYI, for itunes users, doubletwist gets it library from itunes, including the playlists, so this is a VERY easy way to move your itunes collection to the SD Card or USB stick)
When I insert the card into the truck, everything works GREAT
... for a while. Eventually, it just stops reading the card. Sometime it happens after a few days of success, sometimes after a few weeks. With no real explanation as to why
. Usually when it fails, it is able to see there is a card, but is just not finding anything on it, and has a lot of lag trying to read it. Up until now I have simply resorted to reformatting the card and copying the music back on, which fixes it until it happens again
. So I have been assuming either the card has a physical issue or the reader is defective or the uconnect system is writing something to the card to corrupt it.
I had come to the latter conclusion because on one occasion, the card started showing multiple copies of the same playlists, sometime 5 or more listings of the same playlists
. And it seemed to accrue more copies on a daily basis. So I was assuming that the uconnect was writing something to the card. However, when I inserted the card into the computer, there was only 1 playlist file and it was still accurate as the day it was created.
Anyway, after the card failed yet again. I left it in for a couple of weeks, randomly ejecting & inserting to see if it came back to life (which it had done in the past sometimes). Today I was finally frustrated enough
to take some time and upgrade the system software to 13.19.0 (Thanks Willx
). Interestingly, when I had completed the upgrade, I put the same card into the system which was NOT working earlier, and it worked just fine (welcome back Jason Aldean!
). So in my opinion this proves there is nothing wrong with the card or the reader, because nothing has changed there during the upgrade process.
Which brings me back to the duplication issue as a clue. My current belief is that the Uconnect system builds some local cache within itself as to the content of the SDcard, which probably facilitates faster SDcard access after the initial insert. And I believe that this cache is where those duplicate playlists were residing, and furthermore I believe that this cache is what is getting corrupted when the cards ceases to work. So my guess
is that my card is now working because the cache was wiped out during the upgrade process, allowing the cache to be rebuilt cleanly when I reinserted the card.
I do not know if the new version I installed today will solve the problem permanently, but based on today's experience I know what I am going to do if the card ceases again. My guess is that the uconnect system does a simple scan of the card upon startup to see if it was the same card that was inserted the last time the truck was running. And if that scan shows the same card, it probably just works off the currently cached information, rather than rebuilding. So if this happens again, instead of wiping the card, I am going to add a single song. To see if that forces the uconnect to view the card a "new" and build a new cache
. Unless someone has any other thought on how to force the uconnect to re-read the card?
Of course all my jabbering relies heavily on the assumption of a cache within the system. Can anyone confirm or deny any of this??
Thanks in Advance, and I hope I haven't bored anyone to death