To be honest (after a bit of OF let down with .18), I’ve also installed Rockbox on top of it out of curiosity. While my Rockbox is from -git (I needed to build one tool manually, as I’m not on Windows/Linux/Mac) so far I have experienced one hang in 4:30 h of playback which looks on par with .16 behaviour. But I hope it will not become common occurrence, as with .18.
FWIW, I’ve tested playback time with Rockbox- 13h 30min (not bad, player is far from new) until first power-off, 13h 46 min total playback time, not a single hang.
Thinking of it, total power-on time could be even more, as I’ve reset counter after pulling usb plug, not taking into account, that after 100% recharge, player could be de facto on battery, and only trickle charging if going under e.g. 99% That’s the case now, I see it already has 2h running time, 99% battery while I pulled the plug just moments ago…
Hi, im not good at english but i hope you guys and the firmware developer can understand what i mean…
okay. i just realzed that everytime i play a music and i lock my sansa clip+ by hold the home button after a few seconds my clip+ is restarted itself, when im checking the version ( settings> System settings > Info)my clip+ is hang and it restarted itself again…
OK, I have diagnosed a very inconvenient problem in audiobook playback that I hope can be bug-fixed. Recently my audiobook files show up with incorrect duration on the playback bar; that is it will show you are half way thru when only quarter thru, and fully thru filled bar when only half thru. This has a disasterous side effect, so that if I rewind a bit (which I do every minute to pick up a missed word) in the second half the darn thing seems to look at the world thru that incorrect bar and place me at the actual end of the file (maybe an hour ahead and totally losing my actual place).
This happens both in the clip and clip+ with latest firmware. Maybe some stupid tag was incorrectly coded at recording time, but please don’t point fingers to something I and most folks can’t fix. Just would like it to play logically, just like if I put the same file thru mortplayer audio book app under android. Please make it error tolerant and robust.
I just want to inform that, by my recent experience, this new firmware has som problems playing .FLAC files, which the .15 and .16 didn’t.
When I just received my Sansa Clip+ I ripped one of my cds and put it in… all perfect. It came with the 01.02.15 firmware, and then, the same day I updated the 01.02.18 firmware manually. All i listen is FLAC, so I continue to rip my cds using EAC for perfect tagging. Suddenly the sansa got frozen at track 5 on one of the albums, and after experimenting with different rip methods just the untagged rips were rid of this problem. Some more albums with all their tags continued to frozen at track 5 or 6, always those at those numbers.
Yesterday, tired of it, I downgraded the Sansa to 01.02.15, and then listen to a copule of those same troubled albums and NO FROZEN SANSA… it flowed perfectly. I originally thought It was the USB MODE, but no. It was the 01.02.18 firmware itself. It has problems with FLAC files on tagged albums or something. The funny thing is that the problem is either with track 5 or 6 at first, not before them, at least with me. When one of those tracks ends, the Sansa player freezes or reboot itself.
I re upgraded the unit to 01.02.18 firmware and presented the probem again, then I downgraded to 01.02.15 again and no problem, then upgraded to 01.02.16 and no problem. I let my sansa in the .16 firmware from now on.
One thing got my attention: with the . 15 and . 16 firmwares, the sansa does not freez, but there is one “click” sound at the end of either one of those same “troubled” tracks (5 and 6 track of the albums) that caused the sansa to frozen on the 01.02.18 firmware.
PD: there has been some other reported problems about this issue. Here es one from a couple of months:
I have updated to .18 from .16. Since I have had problems with some .flac files. The clip freezes and I have to restart again.I have returned to .16 and everything seems all right
Oscarilbo, Thanks, I had the same problem, and a downgrade to 01.02.16 seems to have made the problem go away.
Please fix the bug with FLAC files on 01.02.18, when Clip+ got a freezing or rebooting between the songs. 01.02.16 haven’t this problem, but sound quality is best on 01.02.18.
Please fix the bug with FLAC files on 01.02.18, when Clip+ got a freezing or rebooting between the songs. 01.02.16 haven’t this problem,but sound quality is best on 01.02.18.
Sound quality is exactly the same in both firmware versions. Nothing was changed in the later update to affect it at all.
Please fix the bug with FLAC files on 01.02.18, when Clip+ got a freezing or rebooting between the songs. 01.02.16 haven’t this problem,but sound quality is best on 01.02.18.
Sound quality is exactly the same in both firmware versions. Nothing was changed in the later update to affect it at all.
Can drive a nail into my head, but I still hear the difference)))))
I changed firmware three times (16 to 18 and back). The low frequency is deeper on 01.02.18 for me. Maybe I’m wrong, maybe that’s just a glitch in my head))))
Please, if you have a chance, listen more carefully to any of your favorite instrumental tracks with bass line, on both versions of the firmware. Or for example you can listen to “B.B. King & Eric Clapton - Worried Life Blues.flac”
P.S. I use my Clip+ with the Pioneer HDJ-2000 closed type headphones.
You forgot to mention that the updater needs to be ran as administrator in the post. I tried to just use it regurlarly the 1st 2 times but it wouldnt run and it never asked for mermissions either. So I killed the process in task manager and ran it as administritor (in my windows 7 64 you do this by right click the exe and then left click run as administrator but your windows must be logged into an account that has administrator privliges). After that it worked but not everyone could have figured that out and so you really should put it somewhere where they will see it (like the download page).
Hello to all. I have the clip+ 8gb. I´ve noticed when I use a SD card with less than 8gb, the player sometimes hangs, and the player doesn´t like the 4gb ones (hahahahahahaha). After the update (last year, approximately 10 or 11 months ago), the same thing. I´m using the 8gb sd card since then, and no problem appeared. Thanks.
Just to mention that this card is not working with 01.02.18 (and don’t work whith .15, and .16 too)
Transcend TS16GUSDC10 microSDHC Class 10 16Go
Yes, many people have problems with Class 10 cards (and it’s not only the SanDisk brand). It’s the wrong card for mp3 players. You need a Class 4 (or even Class 2 is OK).
One little strange bug to report. Changing the time causes the minutes to jump about 3 ahead of where you actually set them. In case it hasn’t been posted yet.
Hi, player Sansa Clip+ was pulled from the sockets for data transmission thereafter player ON and writ “FAT is corrupted Please connected device to Pc” and immediately turns off,Sansa Clip+ Firmware Updater writes an error,plz help!
Rockbox only seems complicated before you get used to it. Once you are used to it it seems simple. I was reluctant to try Rockbox for a long time, but hated the firmware in the Clip Zip so much that I forced myself to get used to Rockbox. Now it is on my Clip+, Clip Zip and Fuze players.
The auto updater does not work for me even when right-clicking and selecting “Run as Administrator”. I’ve downloaded the manual bin file but don’t know where to put it. (I don’t understand what the term “root directory” means.) When I click to view the Sansa files I see only one folder called “Internal Memory”.
I got a new clip+ to replace an old clip+ that broke. I use it it my car and my old one would continue where it left off when I turned it back on. The one one doesn’t. I have to start back up.
How would I go about downgrading to an older firmware?
…a lot of us absolutely LOVE 
, when I say “we” I mean “my son and I”, but it’s true it’s a nice project. The interface seems a bit complicated.