Tired of 'Refreshing your Media' and freezing

What’s the deal with my Fuze freezing 100% of the time now when it goes through the “refreshing your media” process? The status bar goes half way and then the player just hangs on the screen. 

To fix this problem, I have to hold the reset button to turn it off. Then go and plug the Fuze into the computer, and take it out without updating. This bypasses the refreshing your media process. 

Currently my Fuze has 700MB free out of 4GB. 

@lukev wrote:

What’s the deal with my Fuze freezing 100% of the time now when it goes through the “refreshing your media” process? The status bar goes half way and then the player just hangs on the screen. 

 

To fix this problem, I have to hold the reset button to turn it off. Then go and plug the Fuze into the computer, and take it out without updating. This bypasses the refreshing your media process. 

 

Currently my Fuze has 700MB free out of 4GB. 

Don’t get mad, but I have to ask…how long are you waiting before you give up and reset it? I had a couple times where I thought mine froze, like when I deleted something on it, and reset it…then one day I said, screw it, and set it aside…a few minutes later, I saw the “explosion” graphic of the power-off timer taking effect, meaning it had finished refreshing. 

    Of course, I was refreshing 11+GB, not 3+, so I would expect it to take longer for me.

I left the Fuze to refresh one time and came back 20 minutes later and still refreshing! I mean come on now!!

@lukev wrote:
I left the Fuze to refresh one time and came back 20 minutes later and still refreshing! I mean come on now!!

Yeah, something is definitely up with it. Got the newest firmware?

i have firmware v01.01.22a, which i updated two weeks ago

Two steps:

First, connect in MSC mode, and delete the mtable.sys file in the root directory.  Upon disconnect, the refresh database operation will be with a brand new mtable.sys file, built from scratch.

Second, if the first operation made no change, connect in MSC mode again and run chkdsk  on the Fuze, plus the µSD card if one’s plugged in.  Find the logical drives using Windows Explorer.

If there’s a problem in ONE of your music files, the refresh database operation may hang at the problematic file.

Have you checked all of your files for proper ID3 tags?  Download and install MP3Tag, and set the tags to write as ID3v2.3 ISO 8859-1 (Latin-1) tags.

Bob  :smileyvery-happy:

Tried all your methods. Hasn’t worked. Now I will try removing all files and putting them back on Fuze folder by folder to isolate the problem.

@lukev wrote:
Tried all your methods. Hasn’t worked. Now I will try removing all files and putting them back on Fuze folder by folder to isolate the problem.

How exactly do you remove all files from your Fuze.  I’m still getting the hang of mine and have loaded 3 x 60 minute albums - and on the 3rd refresh - the synch loaded like every photo I have in my computer onto my Fuze and I’m trying to get them off my device.  I stopped it like half way through that fuze so it couldn’t load all the photos - but I’m trying to remove the photos - and the synch function from Windows Media Player 11 - is now taking a countrylong time.  About 15 minutes right now and I got 23 % of synch completed.

I don’t want to use my Fuze for anything but audio files.

Message Edited by fireball on 01-19-2009 12:14 PM

@fireball wrote:


@lukev wrote:
Tried all your methods. Hasn’t worked. Now I will try removing all files and putting them back on Fuze folder by folder to isolate the problem.


 

How exactly do you remove all files from your Fuze.  I’m still getting the hang of mine and have loaded 3 x 60 minute albums - and on the 3rd refresh - the synch loaded like every photo I have in my computer onto my Fuze and I’m trying to get them off my device.  I stopped it like half way through that fuze so it couldn’t load all the photos - but I’m trying to remove the photos - and the synch function from Windows Media Player 11 - is now taking a countrylong time.  About 15 minutes right now and I got 23 % of synch completed.

 

 

I don’t want to use my Fuze for anything but audio files.

 

 

 

Message Edited by fireball on 01-19-2009 12:14 PM

Your problem is that you have the Dreaded AUTOSYNC on in WMP. Once you get everything off of it that you want off, With your Device plugged in Go to the Sync tab, Click on the Little arrow below it, goto the device and the flyout menu will have an option that says set up sync, click that, in the top left corner therer is an option that says sync this device automatically make sure the box next to it is not checked. You may need to do this with both internal and external memory.

I have my Fuze set up in MSC mode which allows me the luxury of drag-and-drop to load files. I just do all this in Windows Explorer. I find this the easiest form of file management, and prefer this option to MTP mode.

Okay I think I have fixed the problem, or at least isolated it. The refresh after update is quick now. Takes about 15 seconds. After adding Audible files to it, the Fuze has froze again. Therefore I’m pretty sure this is a problem with the Fuze not recognizing some of the Audible files. I’ve checked and some Audible files seem to be alright and after adding other Audible files it froze again. Still not sure why this occurs with some files.  

I get this “Refreshing your media” stall.   I’m fairly sure it’s a file or directory but how do I tell which one??    This thread was labeled as “solved” but I fail to see a solution.   A revision of the firmware is called for.  

larryj wrote:
I get this “Refreshing your media” stall.   I’m fairly sure it’s a file or directory but how do I tell which one??    This thread was labeled as “solved” but I fail to see a solution.   A revision of the firmware is called for.  

Run ChkDsk to look for and fix corrupted files. It could also be info in an ID3 tag that it cannot de-cypher or the wrong format tag.

Read up on both issues in this FAQ.

Chkdsk doesn’t show a problem  but by trial and error, I think I’ve isolated the error to one  directory of podcasts.    This  has taken several hours and I’ve about worn out the slide switch on the side of my Fuse!!    If the darn little thing is so picky,  how about an external program we can run on our podcasts prior to shooting them onto the Sansa device.  That program would atleast flag the errant file so I could fix or eliminate it.  

  None of my other players have any problem with any of these podcasts so why should Sansa.    Very  discouraging.  I’ll read the FAQ tomorrow.  Thanks for your help.

Yes, there is a program. mp3tag. Once you have it write tags as ID3v2.3 ISO-8859-1 the Fuze should be very happy. 

You can read about it in the FAQ about ID3 tags. 

http://forums.sandisk.com/sansa/board/message?board.id=announcements&thread.id=201&view=by_date_ascending&page=1

And yes, the Fuze is way too picky about tags. 

I had a “refreshing media” problem. I would like to lay out the steps to fix the problem with a Windows PC since I had to scan many posts to find the answers.

  1. Go to MSC mode. With device disconnected from PC switch to “HOLD”. Hold down “<<” on wheel and plug in device. Hold down “<<” until the device indicates “connected”. Now the device is in MSC mode.

2.  Use “My Computer” and note the drive letter that your device has assigned to it.

  1. Open the “Command Prompt” and switch to the drive of the device noted in the previous step. (ie type in E: then ENTER)

  2. Enter this command to find and fix corrupted files on the device, chkdsk /F E: Where E is the drive letter of your device. While in this mode you can also delete files using Windows Media Player that might not show up in AutoDetect mode due to corrupted files.

  3. After chkdsk is done eject your device and see if it will reboot.

 I don’t know what MSC or MTP stands for. If you are unlucky, like I was, and the device failed while in AutoDetect you have to use the above trick to get it into MSC mode which will allow you to edit files that are hidden when in AutoDetect. 

  Another post indicated that a user should delete a certain mtable.sys file, funny thing is my Fuze does not have that file, at least not in the root directory.

Hope this helps.

ejanuska wrote:

 

 I don’t know what MSC or MTP stands for. If you are unlucky, like I was, and the device failed while in AutoDetect you have to use the above trick to get it into MSC mode which will allow you to edit files that are hidden when in AutoDetect. 

  Another post indicated that a user should delete a certain mtable.sys file, funny thing is my Fuze does not have that file, at least not in the root directory.

 

Hope this helps.

 

  • MSC = Mass Storage Class (official) or Mode of Sansa Champions (unofficial). Device appears to computer as a Removable Storage Device (ie. thumb drive or other hard drive)
  • MTP = Media Transfer Protocol (official) or Most Troublesome Pos (unofficial). Computer sees player as media device requiring ‘management’. Needed for DRM-encrypted files such as Rhapsody, Napster or audio books from library (ie. any file that you do not own)
  • AutoDetect = AutoDefect. Self-explanatory. Causes more problems than it solves. Recommended not to use. You’ve already discovered 1 reason why.

The mtable.sys file is a ‘hidden’ file. You can (and should) set Windows to show hidden files & folders. Note it is only visble in MSC mode, not MTP.

Btw, nice explanation of how to force MSC mode and run ChkDsk. :smiley:

ejanuska wrote:

 

 I don’t know what MSC or MTP stands for. If you are unlucky, like I was, and the device failed while in AutoDetect you have to use the above trick to get it into MSC mode which will allow you to edit files that are hidden when in AutoDetect. 

  Another post indicated that a user should delete a certain mtable.sys file, funny thing is my Fuze does not have that file, at least not in the root directory.

 

Hope this helps.

 

  • MSC = Mass Storage Class (official) or Mode of Sansa Champions (unofficial). Device appears to computer as a Removable Storage Device (ie. thumb drive or other hard drive)
  • MTP = Media Transfer Protocol (official) or Most Troublesome P.O.S. (unofficial). Computer sees player as media device requiring ‘management’. Needed for DRM-encrypted files such as Rhapsody, Napster or audio books from library (ie. any file that you do not own). Used in conjunction with another trouble-maker, Windows Media Player. While not a bad protocol in and of itself, the lack of understanding of how and why it works accounts for at least half of all new posts on this forum re: connectivity issues.
  • AutoDetect = AutoDefect. Self-explanatory. Causes more problems than it solves. Recommended not to use. You’ve already discovered 1 reason why.

The mtable.sys file is a ‘hidden’ file. You can (and should) set Windows to show hidden files & folders. Note it is only visble in MSC mode, not MTP.

Btw, nice explanation of how to force MSC mode and run ChkDsk. :smiley:

Updated to V02.02.28A.  Now after dropping my podcasts into the Podcast Folder,  I get the green progress bar saying “Refreshing your Media” but only for a few seconds.  Then the screen goes white.  So much for the firmware update.  Found I must reformat the Fuse to get out of the lockup.  Chkdsk /f never shows any problems were found  nor any problems were repaired.

I used to think I had a bad Tag or some problem with the mp3/ogg meta data.    But from my  test folder (containing 19 sub folders which contain a total of 55 pod casts (mp3  and .ogg))  I can take any individual  folder,  drop it into the “Sansa E:” drive  disconnect and then see the  “Refreshing your Media”  proceed without problem. (Not entirely true… keep reading for later post from me)   But if I take all 1.6 GB and dump the individual folders into the Fuse PODCASTS folder,  I get a brief “Refreshing your Media” green progress bar and then a white screen and lockup.  At that point, I’m forced to hook Fuse to XP and format the internal memory  (Mine shows as E:).    So I conclude that somehow I’ve exceeded the “Refreshing your Media” routine’s maximum limit, what ever that secret is.  How about it Sansa,  what are you limits?

A system setting that turns off the database read (Refreshing your Media) would be helpful to me.   I don’t care if I have a database.   I’m happy going to “Folders” and playing what I want out of a particular folder. 

Message Edited by larryj on 11-29-2009 02:54 AM

Message Edited by larryj on 11-29-2009 02:55 AM

Message Edited by larryj on 11-29-2009 07:29 AM

Message Edited by larryj on 11-29-2009 10:55 AM

I think I finally made some progress after two days.  Sansa Fuze V02.02.28A does not handle pictures inside media files correctly, at least as far as .ogg files are concerned.  You can demonstrate this for yourself by going to http://distrowatch.com/news/oggcast.xml

Podcasts  dww20091026.ogg   and  dww20091109.ogg contain the DistroWatch logo as a 86 x 87 pixel .PNG.   Either of these files dropped in a newly formatted Sansa Disk  E:/PODCASTS folder will cause the  “Refreshing your Media” progress bar to freeze and your Fuze to lockup.

dww2009116.ogg,   dww20091102.ogg  and dww20091019.ogg  do not contain the logo .png  so are sucked into the Fuze database during the “Refreshing your Media” green progress bar without problem.

20092026 and 20091109 all play on several of my “mp3” players without a problem. So why isn’t Fuze happy with them???   So if someone else can confirm this,  I’ll bring this to SanDisk’s attention.

Nearly two whole days working on this!!!   I guess  I’ll have to “adjust” my podcast files before feeding them to Fuze.   This really shouldn’t be necessary.  OK, now I’m off to experiment with EasyTag.

One last note:  The dww20091026.ogg  file contained a logo .png as noted above.  I used EasyTag (Ubuntu Karmic based) to remove the image .png.   I then placed it in the E:\PODCASTS folder.   “Refreshing” green progress bar  ran without lockup and the file was playable in Fuze.  

Also don’t bother looking for the embedded  images using Mp3tag.  They don’t show up!

Finally if you find it convenient to run XP virtualized,  here’s a link to my method using Suns VirtualBox running on Ubuntu Karmic 64 bit.   http://foxgulch.com/WordPress/?p=508  The site contains no advertising.   

Message Edited by larryj on 11-29-2009 09:29 AM