slotmonsta wrote:
niko_sama wrote:
Why did they shelf the work that had already ben done. They have the fix… They did tests on the fix. They had quantifiable numbers regarding the fix. 7 months ago. What happened? I believe Sansa dropped the ball on this one and i can’t understand the logic. You had the fix… Why not take care of your customers, and improve your product.
The improvement for this issue was never actually coded into the firmware. There was a potential improvement identified however this actually never made it in to the code. There is no elusive firmware that is sitting on the shelf.
FYI, sansafix is no longer working with SanDisk. (If you will notice the VIP status was removed from his account and he has not posted lately) Some comments that were made, although well intended, may not have actually made it in to production.
Forum Admin
slotmonsta
Message Edited by slotmonsta on 09-24-2009 04:12 PM
I’m going to ask one last hard question…
Did they or didn’t they fix this issue with the Fuze? The Fuze and Clip share a common ARM cpu, and also most likely simular code structure and routine libraries for playing back 44.1k files? I’m under the understanding the fix was created and implemented for the fuze. And knowning how code is written to be reuseable it makes me wonder… if its true the code doesn’t exit… maybe the fuze never got fixed?
It may just be my misunderstanding.
Slotmonsta?
