12-15-2009 11:47 AM
This idea came via another thread, but I thought it might be useful to note here...
Rather than putting a volume control between your phones and your Clip, you could try using the EQ to lower all bands -- you could then use the custom EQ for radio, and switch back to normal otherwise.
12-15-2009 11:51 AM
From what I recall, the EQ doesn't work with the radio.
iPod Touch 5G 32GB, Touch 4G 32GB, Clip Sport 8GB.
Rockbox-> Clip Zip 4GB, iPod Nano 2G 4GB, iPod 5.5G 80GB
2012 Nexus 7 32GB, Asus MeMoPad 8 16+64GB, LG Optimus G Pro, Nokia Lumia 900, Nokia Lumia 520
12-15-2009 12:34 PM
You're right, bummer, nevermind!
12-21-2009 11:21 PM
I also look forward to this issue being resolved with a firmware update. They did it for the original clip, They should do it for the clip+ as well.
I'm surprised they didn't think to fix it from the get-go.
12-21-2009 11:26 PM
I sent a message to their support people. I recommend others do as well, maybe that'll encourage them to fix this.
12-24-2009 04:24 AM
This is the response I got:
12-24-2009 04:26 AM
This is the reply I sent:
I tried all that, and it did not take the volume down enough to be comfortable to me.
12-24-2009 10:49 PM
And here's the latest email I got from them:
12-24-2009 11:00 PM - edited 12-24-2009 11:00 PM
The new Clip+ firmware includes components from both the original Clip and Fuze. The radio (analog) gain is adjustable, and no doubt will be trimmed a wee bit in the future, when firmware updates become available. No worries!
The FM chip feeds an analog signal to the processor. Based upon the past revisions, it looks like the original gain setting was used for the first release.
Oh, and your response seems to be referring to the original Clip too, as we now have the volume buttons on the left side.
To err is human...
Message Edited by neutron_bob on 12-24-2009 11:00 PM
02-25-2010 05:59 PM
Just got this message from Sandisk technical support regarding this issue (FM volume too high at lowest setting) with the Clip+:
"Please be informed that we are aware of this issue. We already forwarded this case to our firmware development team and we are expecting that the issue will be resolved on the next firmware update."