SanDisk Sansa Clip+ With Rockbox Has Battery Life/Drain Issues

[Illustrator76]

Hi,

I used the Rockbox utility to Rockbox my brand new SanDisk Sansa Clip+ and everything worked just fine. The problem that I am having is that I am getting extremely poor battery life and I have no idea why (even though I am fully charging the Clip+ and it is reading well over 15 hours of battery life left). I used my Clip+ 3 times last week for a total of 3 hours, and when I turned the Clip+ on to use it again, the battery was basically dead. The same thing happened the week before as well. I am making sure that I power down the Sansa Clip+ once I am done with it, so that shouldn't be the issue at all.

Is there anything else I am missing or doing wrong? It almost seems as-if the Sansa Clip+ battery is draining rapidly even when I'm not using it.

Any help given on this matter would be great.

Thanks!

[saratoga]

I recently tested the clip players and battery life was hours better than the Sandisk firmware. I would check that the device is powering off and not being left with the music playing.

[Illustrator76]

I recently tested the clip players and battery life was hours better than the Sandisk firmware. I would check that the device is powering off and not being left with the music playing.

I have always been powering the device off with the power button, I get the actual message that says [Powering Off], and then the screen goes blank. When I turn the Clip+ back on, I get the firmware screen that flashes (with all the numbers and other technical stuff), then the Rockbox logo flashes, and then I am taken to my "home screen" with all of the options to change settings, play music, etc...

Does all of that sound right? Is there anything that I am missing? Do I need to recalibrate the battery maybe? If so, is there any way to do that within Rockbox?

Thanks.

[saratoga]

That sounds fine, and there is no way (or need) to calibrate a battery. 

[Illustrator76]

That sounds fine, and there is no way (or need) to calibrate a battery.

Question. If the alarm is set, does the alarm automatically turn the device on? I SWEAR I made sure that my Clip+ was turned off yesterday, but when I checked it today, my Clip+ was on and the battery was severely drained. I am wondering if I somehow turned the alarm on by a mistake and this is what could be causing issues. If that is not the case, then I am baffled, as this is like the 3rd time this exact same thing has happened.

EDIT: I just noticed that it is ridiculously easy to power this Clip+ on. I barely even touch the power button and comes on instantly. If the alarm isn't the issue, I am wondering if my Clip+ being stored in a tight space is somehow causing the power button to get touched and then power the device on.

I am going to a little more testing to see if I can pinpoint exactly what is going on here.

[Scarlett]

 recently have just the same problem as Frannz. Plugged the CF into a card reader, connected my X5L via USB and moved the content of my 30 GB Toshiba drive (MK3006GAL, 50 pin) to a brand new 128 GB 600x CF (KomputerBay). Then I installed the current bootloader (I think it's version 4) on my X5L using RockboxUtility 1.4.0, unplugged the USB, plugged in the AC and booted up the X5L to finally install the bootloader.
I also installed the current Rockbox (3.13) on the CF via RockboxUtility 1.4.0 while still plugged into the card reader.
The CF card then changed its home from the card reader to a CF adapter ("M-ware® ST5051 CF an HDD-Adapter ID7595"). Finally I swapped the Toshiba drive with the CF adapter.


Unlike scam  400-101  dumps and MICROSOFT  dumps training program.

[[Saint]]

I find it extremely difficult to accept this as being "just the same problem".

I'm prepared to accept "vaguely similar" with the information given.

Firstly, its two completely different devices. Secondly, your hardware has been modified, removing any chance for a basis for comparison.

You give a reasonable amount of detail in your post, but you don't actually give any measurements that are relevant to establishing the scale of the issue. Or any measurements at all that confirm the problem actually exists, for that matter. For example, you haven't even listed the runtime of the device, neither before nor after modification, nor how this differs from your expectations or reality.


[Saint]

EDIT: Come to think of it, I'm not sure you replied to the correct post, who is Franzz? I'm not entirely convinced that I didn't just waste my time replying to a context sensitive spam bot...it wouldn't be the first time.