Sansa Fuze+ Firmware 02.38.06

I have problem with flac format. If I have more albums for one artist, display me only one album - ,RTIST=*name of artist*". (When I have only one album for one artist, sometimes display this too). Have anyone same problem?

Got the same problem after upgrading to the new firmware. I only use the fuze+ for playing flac files. Is there a way to go back to the previous firmware

@weateallthepies wrote:

Ah yes spotted it says for ‘music content’.

 

Still it’s not really folder browsing, it’s just another form of tag browsing dressed up to look like folder browsing, since things in that folder might not appear if they are tagged as audiobooks or podcasts. I don’t really understand what it has solved.

You are right. Audiobooks and podcast do not appear.  I do like the fact that the player treats Podcast special.  This simplifies things for me in another area.    

I have used the music folder browsing and it does work well.  I have files nested 3 folders deep.  They are not labeled Podcast.  I added them via Window Explore.  It works as I would expect.   When I add files via WMP, the Fuse+ sorts these files by author.  So Audiobooks with different authors each chapter are sorted in separate folder on the fuse.  Music folder view has no value in this case. 

So, folder we want to view in the future in music folder view, need to be added  to the music section via Windows Explore.

Thanks for the update.

One of the interesting bugs in this is caused by the looping menus… it’s not a showstopper by any means.  When I navigate by Music->Artist, the looping menus cause some of the album art to be incorrect when I have more than 3 albums.  For instance, I have 5 albums by the same artist, and the third album is always the incorrect album art after looping; it is either the first album’s art, or the last’s.  The art is correct until I loop in the menu.

Like everyone’s said - this is a quirky player.

After updating firmware manually from 02.37.01f to 02.38.06f internal clock doesn’t work correctely any more (24-hour mode).

it looses time after shut down. date doesn’t switch to next day over night, also after turning off for only some seconds, time differs several minutes back (e.g. time was 9:05, when turning on it is 9:01)

Edit: Time bug in 24-hour and 12-hour mode. Switching time between 24-hour an 12-hour mode is sometimes saved as time where clock starts counting after restart, sometimes time differs several minutes.

I mean they should add some kind of submenu near “shuffle all” that lets you decide at least the letter from which you should  start the SLOW scrolling.

I wonder who decided to create the album menu, it’s practically impossible to scroll albums. It does like 1 row per second…unbelievable.

I don’t see any speed improvement

Help Needed

I updated the firmware and now all my tags are screwed up. I only use flac files on my fuze. Instead of the name of the album it shows artist=name.  How can I correct this problem.  Anybody else having this problem?? Is this a bug in the new firmware??

Daniel

I’d check your FLAC tags first with something like MP3Tag.

After the update my Fuze+ is not seeing 131 songs. If I hook it up with USB I can see all the file there that I seen before the update. Somehow after the update even though all files are still pressent 131 are not being read. It reads other songs but not the 131 songs.

What can be done do fix this?

Never mind I found out how to get them to show.

I was not aware of the folders option (thank you for this btw I loved it before). I went to folders and used shuffle instead of songs and it now shows all of the songs.

All I need now for the perfect mp3 player is to get it to not show album art and put the song info up there so it is a bit larger. I want this due to using it at work and in my car all the time. It would make it easier to see what is playing (when I choose to forward to the next song) at a glance.

This version of firmware has following bugs:

  1. There is no option to choose method of locking, I prefer old one with keeping play touched.
  2. Songs in folder selection menu are not sorted properly, I have song without track number in tags, but in file names from 00 to 11, and they are played in very strange order: 1, 9, etc.
  3. Keyboard become too sensitive, too often back button cause too fast return to main menu and sometimes some accidental actions happen or taping in the middle cause to go up.
  4. Translation to Polish is incomplete. This is rather annoying. I can translate all of them for you, for free just send me strings to translate.

I used to have the problem with the sd card not being recognized. It is still not resolved. It is no longer showing an error message, but now it just freezes during ‘loading card’. Also since the first time I plugged in an sd card my clock does not advance anymore. This is not resolved by this firmware update either…

I personally prefer the on/off switch being pushed to work for the lock button.

@manveru wrote:

This version of firmware has following bugs:

  1. There is no option to choose method of locking, I prefer old one with keeping play touched.

This is not a “bug”. And it’s not new with this firmware update. The locking procedure was changed about 3 updates ago due to overwhelming requests and unhappiness with the way it was. Changing it to the power button was not only the majority of customer’s preference, but also one that Sandisk could change and make everyone (except you and 2 others to date) happy.

 I got the time bug again with this firmware too. I just wanna trash this product. seriously I can’t take it anymore

@_sandro wrote:

 I got the time bug again with this firmware too.

The firmware post doesn’t list this as a ‘known issue’.

But then it doesn’t say it was fixed either.

with the previous firmware reapplying it fixed it. Now nothing seems to resolve it

@_sandro wrote:

 I got the time bug again with this firmware too.

same. I’ll stick with it due to lack of money. But all these bugs+how darn easy to scratch the screen is+no official pouch.cover that shipped with it or is available is plan BS seeing as how scratchy it get’s in NORMAL use. Lucky me I got a screen protector on it but not before 3 scratches in 2 days!

@tapeworm wrote:


@manveru wrote:

This version of firmware has following bugs:

  1. There is no option to choose method of locking, I prefer old one with keeping play touched.

This is not a “bug”. And it’s not new with this firmware update. The locking procedure was changed about 3 updates ago due to overwhelming requests and unhappiness with the way it was. Changing it to the power button was not only the majority of customer’s preference, but also one that Sandisk could change and make everyone (except you and 2 others to date) happy.

Does this prevent such feature to be selectable in configuration?

What about other issues?

Bought a Fuze+ to replace a worn-out Fuze. I mostly use these for listening to audiobooks, usually in mp3 format.

I find that playback suddenly returns to the beginning during listening and when attempting to pause playback using the pause button (which is often unresponsive). Returning to my place in the book is excruciatingly slow since the books are hours in length.

Are there fixes for these problems in the works for an update?

@manveru wrote:


@tapeworm wrote:


@manveru wrote:

This version of firmware has following bugs:

  1. There is no option to choose method of locking, I prefer old one with keeping play touched.

This is not a “bug”. And it’s not new with this firmware update. The locking procedure was changed about 3 updates ago due to overwhelming requests and unhappiness with the way it was. Changing it to the power button was not only the majority of customer’s preference, but also one that Sandisk could change and make everyone (except you and 2 others to date) happy.


 

Does this prevent such feature to be selectable in configuration?

 

What about other issues?

No. But until there are more than 3 people desiring this ‘feature’, it’s unlikely to be added (if it’s even possible in the first place).

I was only responding to this issue.