Problems with Refresh / Deleting Tracks and Album ...

Question

There are times when refreshing the Music Player library either won't complete (eg: after you've dropped the phone popping out the battery in the middle of a refresh .. or is that just me?) or deleted tracks and album art won't disappear from the Music library after a refresh.
These problems are often down to corruption of the library and  the only thing to do is to delete the library files and start over.  Even a hard reset of the phone won't fix this as the files are stored on the card / mass memory.
To delete the library files:
- Ensure you can see hidden files in Windows Explorer:
Windows Explorer .. Tools .. Folder Options .. View
Select "Show hidden files and folders"
- Connect the phone to your PC using the USB cable in "Data transfer" mode
- Find and rename (or delete if you're really brave) files with names like:
E:\private\101FFC31\mpxv1.mpd
E:\private\101FFC31\pcv5.mpd
E:\private\101ffca9\harvesterdb.dat
(assuming the phone's mass memory / card has been connected as E
Note that the folder names may be different and the files may have prefixes - eg: mpxv1.mpd could be called abcmpxv1.mpd.  Basically, you need to search under the Private folder for any files that look similar.
If you rename files - eg: by adding a ".o" to the end of the name - instead of deleting them, you can always just change the name back if you find you need those files back.
- Refresh the Music Player library
This will take longer than normal as it's a complete refresh, but it should now work.
Message Edited by patc on 12-Feb-2009 08:38 AM

Answer 1

Hi,
What version of Workspace Manager are you using ? I tested this with 9.2.0.4 and everything worked as expected. I was unable to update the row from the WK2 workspace after refreshing it.
Please note that after removing WK1, all locks that had been held by the WK1 workspace are dropped. So, when you update the row for a second time, you are actually locking the row that had been merged(which is contained in the TOP workspace) and not the row from the LIVE workspace. So any workspace that references the row from the LIVE workspace, and not the one from the TOP workspace, would be able to update the row.
This is the case that exists before refreshing WK2. However, after refreshing WK2, it will then use the row from the TOP workspace. Since this row is locked it would be unable update the row.
Ben