well, my clip actually drained from 100% too 68% after full charge and leaving it there overnight turned off… why is it like that.
It’s defective, you’ll need to exchange it.
@syaoran wrote:
well, my clip actually drained from 100% too 68% after full charge and leaving it there overnight turned off… why is it like that.
Can anyone tell me how roll back Sansa Clip to the original Firmware? After updating to ver 01.01.29 the device will no longer mount under Linux Fedora 7. Help please…???
Many thanks for the link, I’ll give that a try. The original Firmware on the Clip 4 I purchased this week was .19 (which connected easily to Fedora 7) but hopefully .20 will get it connected.
@virason wrote:
Many thanks for the link, I’ll give that a try. The original Firmware on the Clip 4 I purchased this week was .19 (which connected easily to Fedora 7) but hopefully .20 will get it connected.
When one updates the firmware, the process sets the the Settings to their defaults. I am thinking Linux does not support MTP mode (maybe someone can verify this?). The default is Autodetect. Autodetect tries MTP first. If for some reason, it does not progress on to MSC, the player will not connect.
So, I am suggesting that Linux users try changing the USB Mode Setting to MSC when thier player does not connect as expected.
The downgrade to .20 worked and the device was again able to mount under Fedora 7. Re-upgrading to .21 produced the same results as before (no mount). The clip screen shows “connected” but the depleted portion of battery icon isn’t flashing (just steady on at a random power level not necessarily the actual level) and the device isn’t mounted or shown in the /media folder.
I have attempted connecting both ways, with the USB Mode in AUTO and set manually to MSC, with no difference in the results, but have noticed that the device must be powered on in order to get a successful connection.
It seems that .21 tries to connect much faster than .20 as I noticed that the battery icon flashes several times then glows steady with only the portion being charged flashing until the battery is fully charged when the connection is successful. It works properly with an earlier version of Fedora so I suspect the problem may be with Kernel 2.6.23.15-80.fc7, which I will explore futher.
Cheers
That’s correct, Linux uses MSC mode because MTP is designed to work with windows media player, which Linux doesn’t have.
Tweet wrote:
I am thinking Linux does not support MTP mode (maybe someone can verify this?).
@sasafrass452 wrote:
@sasafrass452 wrote:
A little update… after another 30 minutes of play, it’s still at 85%. Here are my measurements thus far at 30 minute increments:
30 min- 100%
30 min- 100%
30 min- 100%
30 min- 92%
30 min- 85%
30 min- 85%
Ok, another update…
30 min- 78%
30 min- 78%
30 min- 71%
30 min- 71%
30 min- 64%
30 min- 64%
30 min- 64%
30 min- 64%
30 min- 64%
30 min- 57%
30 min- 57%
30 min- 57%
30 min- 57%
30 min- 50%
30 min- 42%
This adds up to 10 1/2 hrs so far, & if my calculations are correct, the battery will be dead with another 3 hrs of use. This is NOT good, IMO. Where’s the additional 3+ hrs I had originally? On top of that, it’s generally recommended not to fully drain the battery every time, so that means even less hrs. Should I fully drain it this time, to recalibrate the meter? I want my 3 hrs back!
Final update…
30 min- 42%
30 min- 35%
30 min- 28%
30 min- 28%
30 min- 7% Yes, that’s correct… down 21% in 30 minutes!!
30 min- 7%
15 min- Unit shut off.
TOTAL TIME: 13 hrs, 45 min.
That’s 3 hrs less than what I previously had!!! I have once again proven what I knew all along, & I’m not pleased. No one can convince me that the battery meter has no effect on the overall playtime. Sansafix, please report these results to the right people, so this issue can be fixed once & for all. I want my 3 hrs back!!!
Message Edited by Sasafrass452 on 06-15-2008 11:27 AM
What does “Ch. Mode off/on” mean?
What the meaning of “Ch. Mode off/on”?
Wow, that’s some gnarly font size there. Ch. Mode is “Chapter Mode”, used with Audible .aa audio books only- the books can display in standard “parts” or in individual chapter breaks.
Using the audiobook folder with the new firmware, the speed function does work with standard files.
Bob :smileyvery-happy:
On the one hand, I’m envious of Sasafrass for even getting the 13.75 hours! I get less than that with the old firmware.
On the other hand, I can empathize with her, because why should upgrading firmware (which is supposed to fix a few things) downgrade performance?
On the one hand, I love SanDisk for beiong so reponsive to customers and supporting an existing product so well…and on the other, it is very disheartening that they can never seem to get it right…
@miikerman wrote:
@sasafrass452 wrote:
That’s 3 hrs less than what I previously had!!! I have once again proven what I knew all along, & I’m not pleased. No one can convince me that the battery meter has no effect on the overall playtime. Sansafix, please report these results to the right people, so this issue can be fixed once & for all. I want my 3 hrs back!!!
I can hear and understand your anguish, Sasafrass. But I, for one, rarely play my Clip for more than 13-3/4 hours while out and about in a day, and so am not too concerned that I will run out of power before I can recharge …
Seriously, though, it might help SanDisk to know if your comparison was with playing the exact same file(s), with the same EQ, volume output, display settings, shuffle on/off, etc. As each of these factors can affect battery consumption, that could be affecting matters. Even area/room temperature can affect the battery (think of a 68 F. degree room and a 90 F. degree room)–seriously. As can file format (mp3 vs. ogg vs. wma), dramatically.
If you have the time and energy and interest and want to be scientific about it, you could roll back to the .20 firmware and repeat your experiment, keeping all other variables identical. It would be interesting to hear the results (as it has been interesting to hear your results to date), if you do it. No pun intended.
I’m not convinced by Sasafrass452’s data. I’m sure Sansa ran battery tests before they released this version, plus I’m confused by how the sasafrass test was run… why did it take over three weeks for Sasfrass to provide this last data point? Is this data from over a three plus week period of time?
I appreciate users pointing out the problems with the player and new issues from new firmware but something like this needs a very scientific experiment with the same files, same time frame etc. with both versions of the firmware. At least to convince me 
True, some settings can effect the playtime between charges, but I haven’t changed anything. The files are all mp3s, 128kbps. I only listened to the Clip for 30 min at a time, without using the display. I doubt the EQ would effect it that much! We had some quite humid weather last week, but again, using the Clip for only 30 minutes at a time wouldn’t make that much of a difference. The bottom line is, I lost 3 hrs of use & that’s not acceptable.
@miikerman wrote:
I can hear and understand your anguish, Sasafrass. But I, for one, rarely play my Clip for more than 13-3/4 hours while out and about in a day, and so am not too concerned that I will run out of power before I can recharge …
Seriously, though, it might help SanDisk to know if your comparison was with playing the exact same file(s), with the same EQ, volume output, display settings, shuffle on/off, etc. As each of these factors can affect battery consumption, that could be affecting matters. Even area/room temperature can affect the battery (think of a 68 F. degree room and a 90 F. degree room)–seriously. As can file format (mp3 vs. ogg vs. wma), dramatically.
If you have the time and energy and interest and want to be scientific about it, you could roll back to the .20 firmware and repeat your experiment, keeping all other variables identical. It would be interesting to hear the results (as it has been interesting to hear your results to date), if you do it. No pun intended.
How are my results not convincing? It’s all there, in black & white. I only listened for 30 minutes at a time, which is why it took a couple of weeks to collect the data. It still would’ve been the same, even if I ran the Clip all day…
@rdow wrote:
I’m not convinced by Sasafrass452’s data. I’m sure Sansa ran battery tests before they released this version, plus I’m confused by how the sasafrass test was run… why did it take over three weeks for Sasfrass to provide this last data point? Is this data from over a three plus week period of time?
I appreciate users pointing out the problems with the player and new issues from new firmware but something like this needs a very scientific experiment with the same files, same time frame etc. with both versions of the firmware. At least to convince me
Sasafrass452 wrote: I only listened for 30 minutes at a time, which is why it took a couple of weeks to collect the data. It still would’ve been the same, even if I ran the Clip all day…
No it would not - there’s the self discharge as well… Even in a perfectly healthy unit you will get less total playing time if you stretch it out over several weeks rather than in a single day or two. It may or may not be enough to explain the 3 hrs difference.
As another poster suggested - re-install .20 firmware and _try_ to do the test the EXACT same way once more if you’re not positive that all conditions were identical… 
Edit: Or time the .29 total, but in the span of only a few days…
Message Edited by SajmonDK on 06-15-2008 11:24 PM
I’d love to hear if anyone else has seen significant changes in battery life to back up Sasafrass’s data.
If I’m reading Sasafrass’s posts correctly about the unit’s usage, if the firmware did effect battery life, the unit in question will have to be charged once ever 3 weeks instead of once a month…
Well, each of us has our own expectations about our players. And the great thing about the firmware updates is that we can decide if we’d rather move back to the older firmware.
I would suggest that Sassafrass downgrade her player and retest to compare the results. We did extensive testing in QA and the battery life is unchanged on average.
Unfortunately, that would mean I won’t be able to see the exact percentage of battery power left. I use Linux, & that information isn’t available when the Clip is connected to my computer. So, downgrading would be useless in my case.
However, I have noticed that the EQ was reset to “normal” after upgrading the firmware. I turned it off, & I’m testing again to see if there’s any difference. I’m guessing that the overall playtime will only be minutes longer… I’ll post the results when I have them.
@sansafix wrote:
I would suggest that Sassafrass downgrade her player and retest to compare the results. We did extensive testing in QA and the battery life is unchanged on average.
You’d still be able to see how much play time you’re getting out of it though, with the old firmware vs. the new. (and that’s the important thing).
Can someone tell me how they are seeing actual digital percentages of battery life remaining? All I see is the battery graphic.
Thanks!
