I think someone else mentioned this, but is anyone feeling like the Clip+ is a bit low in volume with the newest, write-enabled rockbox builds?

I know all of our headphones are different, but I've tried my UM3X's with my rockboxed Fuze, Clip v1 and Clip+ and hands down, the Clip+ is much quieter at the same volume and EQ settings.

Interestingly as well, the Clip+ seems to have a harder time powering the UM3X's than the other two players as well. Anyone else experiencing anything like this?

Yes i listen at -20db a lot of the time, and its a lot more quiet than it was with the builds before writing was working. I can crank my S4 up to 6db and it doesn't hurt my ears, before i couldn't get close to that without it being unbearably loud.

Well I had r25896-100505 on my Sansa Clip+ and it worked great and I had no crashes. However I have went into that link you have provided and downloaded and installed r25896-100508. When I boot my Sansa Clip+ it tells me that it is r25896-100507 instead of r25896-100508. Now here is the bad bit...When I switched my Clip+ off and try to switch back on it will not switch back on and is dead I have tried holding the power button for 30 seconds and still there is no life coming from my beloved Clip+

EDIT: I have managed to save my Clip+. Which download really is r25896-100508? Because on the Rockbox site r25896-100508 is actually r25896-100507

I think I'll revert back to r25896-100505. There is nothing but problems with r25896-100507 as it crashes while listening to music and sometimes it will not switch on I had no problems whatsoever with r25896-100505 and my clip+ was very stable running it so I will have to put up with the low volume bug and its back to that for the time being.

Hmm this is strange. I have never had any problems with r25896-100505 and it was rock solid. Since installing r25896-100507 and deleting it because that is unstable I have reverted back to r25896-100505 and now that is unstable aswell which it never was before I tried r25896-100507.

It seems that the "temp brick" bug is back with a vengeance with build 25894. With the previous build (25863) I didn't experience any of the notorious temporary bricking but now it happens about 5 minutes after turning RB on. It is louder though

Perhaps the return of the "temp brick" bug with this build might reveal what causes it in the first place.

Funman: It isn't dependent on the color of my horse (wait a moment... I don't have a horse!). r256869 ran stable for more than 10 hours, without a single crash. r25894 doesn't run any longer than 2 or 3 minutes (same settings, same files)... jupitreas made the same observation, so it really can't be a coincidence. However, we do know by now, that it's build -94 which causes the instable behaviour.

It seems that the "temp brick" bug is back with a vengeance with build 25894. With the previous build (25863) I didn't experience any of the notorious temporary bricking but now it happens about 5 minutes after turning RB on. It is louder though

Perhaps the return of the "temp brick" bug with this build might reveal what causes it in the first place.

Can you have a more precise range than 31 revisions?

Also can you describe what a "temp brick" bug is ?

What you see on screen, what you were doing, which settings you use, which music you play etc..