@sr_rox wrote:
Havent people had problems with constant database refreshing?
Thanks,
SR
I’ve got an e260 v2 & Fuze v1. I’ve never seen that.
My 4G Fuze + 8G class 2 uSD takes about 2m 10s to refresh. I have ~2200 tracks (all MP3), and both sets of memory are nearly full.
I noticed early on that there are differences in the way ID3 tags are handled between internal memory and the uSD. This post is about what I discovered for the e260, but it also appears to be valid for the Fuze. It may have changed for the Fuze with the latest firmware that supports v2.4 tags - but I haven’t re-run my tests…
There is another difference in the way the uSD is treated - content on the card is visible to a host PC in both MTP and MSC modes, whereas content in internal memory is only visible in the mode it was transferred to the Fuze.
The only real uSD problem I had was with the e260, where the detent mechanism started to fail, and the reader would shoot the uSD card across the room when it felt like it! They are quite difficult to find if you didn’t spot where they land… Anyway, SanDisk fixed that under RMA 
