The new firmware definitely has battery indication issues. The question is whether it is only indication issue, or the battery runs out faster. I don’t like it at all, so I’m going to return to the previous firmware. Not good at all, guys.
All,
The battery indicator is more accurate. In the past the player would sometimes give only 20 minutes play time while the indicator was at 25%. Now you will find the playtime will keep going on even down to the last 7%.
So even though you may think its dropping fast at the beginning, you wont get suprised at the end. In practice it should drop about 7% per hour.
@sasafrass452 wrote:
My battery is currently at 85%, after 2 1/2 hrs of use. I don’t know if that’s normal, but I’m still keeping track…
___________________________________________________________________________________________________________________________________________
That sounds about right. (As long as it doesn’t shoot down to 25% after 4 hours of use!)
@fullmetal wrote:
The new firmware definitely has battery indication issues. The question is whether it is only indication issue, or the battery runs out faster. I don’t like it at all, so I’m going to return to the previous firmware. Not good at all, guys.
Heh…that’s what I was a afraid of. I think I’m going to wait on doing the update to see what becomes of this. Darn…they never can seem to get it quite right!!
@sansafix wrote:
All,
The battery indicator is more accurate. In the past the player would sometimes give only 20 minutes play time while the indicator was at 25%. Now you will find the playtime will keep going on even down to the last 7%.
So even though you may think its dropping fast at the beginning, you wont get suprised at the end. In practice it should drop about 7% per hour.
I dunno, Sans- someone on here mentioned that their meter was down around 20-30% after only four hours of play. Not good. The question is, is that going to be universal with this new FW version…or was that just an isolated case?
Cllipman , same hardware, same firmware … same problems, as usual
1. The battery voltage at shutdown is unchanged from FW 20 to 29. Only the estimate is made more linear.
2. We measured power consumption during MP3 playback continuous at 17 hours so the consumption is unchanged.
Message Edited by sansafix on 05-23-2008 12:21 PM
Sassafrass is retesting his her result and so far his her data appears normal. So I suggest his her initial warnings were a false alarm.
Message Edited by sansafix on 05-23-2008 02:24 PM
Just to clarify, I’m a female 
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%
@sasafrass452 wrote:
Just to clarify, I’m a female
No wonder I always liked ya! (For some reason, I too assumed you were a guy though…)
@miikerman wrote:
Ya’ll need to go out and play in the sun …
I just came in from the pool! (Didn’t try out my waterproof pouch yet though).
O-K…maybe the pool is a little more fun than obsessing over FW issues… (But Sassafrass’s new test results sound encouraging)
Hi all. I just tried updating to the new firmware and had an issue with content not showing up in the menus. When I went back to an older version, the content showed up again…back to new firmware–no content again.
I also tried formatting and resetting. Nothing worked except going back to earlier firmware versions (I tried 18 & 20–both worked).
Anyone else having this issue?
@kcsunapee wrote:
Hi all. I just tried updating to the new firmware and had an issue with content not showing up in the menus. When I went back to an older version, the content showed up again…back to new firmware–no content again.
I also tried formatting and resetting. Nothing worked except going back to earlier firmware versions (I tried 18 & 20–both worked).
Anyone else having this issue?
When you loaded the content, was it in MTP mode? If so, that content isn’t visible when you’re in MSC mode (like when loading the update). And stuff that’s loaded when in MSC mode isn’t visible when you’re in MTP mode. If that’s not it…then I think there’s a problem.
After getting used to the new firmware’s Podcast and Audiobook features for a while, I am beginning to like them a lot. Especially this one:
- Auto Bookmark: will prompt the user with “Resume?” or “Restart” option when restarted.
Which is great, and accidental short left (or right) click does not jump to the beginning of (or to the beginning of next) track, which is also a good improvement.
Having thanked for these two features, let me be greedy
How about making a short left (or right) click to jump 5 minutes back (or forward)?
Not sure if this has been addressed yet, but I’m having issues with the ID3 tags of ogg files. I ripped a CD to wav and used LameXP ver 2.03 to create some 80kbps ogg files, which uses aoTuV beta5. I added metadata to the files for artist, album, genre, and year. I copied the album over in MSC mode. Only the first track of the CD shows up properly in artist, album, and genre. The rest of the tracks are “unknown” for these three catagories. I verified that all of the tracks have embedded metadata using the program AudioShell to read the “AudioShell Information”. There are no other songs on the player, just this one CD, all in ogg format.
When I put that first track which is showing up properly along with the mp3 version of that same track with the same file name, only a .mp3 extension, they both show up under the artist, album, and genre, so at least that part is working.
Its possible there’s a problem with the files I made but I don’t think so. Anyone else try some ogg files to verify this issue?
batook, see this thread: http://forums.sandisk.com/sansa/board/message?board.id=clip&thread.id=6827
Thanks for your reply Clipman.
It was in auto detect mode. I haven’t changed settings, and installed all versions of firmware and all content using the same auto detect setting.
I tried installing 29 using the firmware updater and manually–same results.
Message Edited by kcsunapee on 05-24-2008 10:31 AM
Message Edited by kcsunapee on 05-24-2008 10:31 AM
Just got a Sansa Clip and I found out about this new firmware, and I am absolutely THRILLED with the new OGG support. Excellent job Sandisk!
Can it be AAC time now please? That would allow me to use my (unprotected) m4a files for my mobile phone and my Clip without having to convert stuff all the time. I know AAC and OGG are pretty much on par, quality-wise, but apparently AAC support seems to be more common in other devices so it would be pretty awesome to include it 
Gapless playback would be a close second on my wishlist 
(And FLAC would be a third, but considering the “low” capacity of these Clips, that may be overkill)
Anyway, excellent job so far!
Thanks for the ‘audiobook’ update, it makes it the player to beat IMHO.
@clipuser wrote:
After getting used to the new firmware’s Podcast and Audiobook features for a while, I am beginning to like them a lot. Especially this one:
- Auto Bookmark: will prompt the user with “Resume?” or “Restart” option when restarted.
Which is great, and accidental short left (or right) click does not jump to the beginning of (or to the beginning of next) track, which is also a good improvement.
Having thanked for these two features, let me be greedy
How about making a short left (or right) click to jump 5 minutes back (or forward)?
I’ve not seen this after updating the FW. I usually pause, then turn off the clip when listening to podcasts. They are in the podcast folder, but when I turn the clip back on, it starts where I left off, but it doesn’t offer to “Resume or Restart”.
Am I doing something wrong?
It works fine the way it is, I usually want to pick up where I left off, but there are times when I’s like to be able to bookmark a certain podcast listen to a different one and come back to the same point in the original podcast. Is it possible to do this?
