Support and General Use > Theming and Appearance Customization

Does a wps tag exist to switch display off during play ?

<< < (2/3) > >>

Yotto:

--- Quote from: Bluemax on September 28, 2006, 11:15:01 AM ---When I understood it right, you do the if/else query concerning the hold switch and then all images are deleted to blank the display ... that'll maybe a good idea  ::) Can you show it to us when you have found the clue to it ? (I'm a noob to rockbox)

--- End quote ---

The problem is, many images don't disappear when you stop telling them to appear.  You have to actually cover them.  The new album art code, by the way, does NOT have this problem.  I found some time last night and actually whipped up a quick all-text wps that blanks everything upon hitting hold.  It's not ready for general consumption yet, but it's getting there.

Bluemax:
 :)

I would appreciate it when you can share your new knowledge with us  ... when you did it ! I'm really looking forward for this 'feature' to save battery time.

Yotto:
I"m having some issues with it.  I haven't tested enough to be *sure*, but it appears that my very simple all-text WPS that blanks the screen on hold actually uses *more* power (by a lot) than any other WPS I've ever tried.  Anybody else notice a power drain (Like, your iPod uses more power than it gets from the USB cable) when using a lot of code for the hold switch?

Chronon:
Huh.  That's very odd.  I haven't done anything along these lines, but that sounds like a bug to me.

Yotto:
My testing is far from complete, but I msut retract my last statement.  The problem seems now to be that if the battery is sufficiently drained (Under 30-50%, I don't know the exact number right now), then it drains faster than it charges if I'm in Rockbox and listening to music.  If it's higher than  whatever that line is (30-50%) then it charges faster than it drains.

This is all in Senab's build, and I want to stress I'm not *reporting* anything, just talking about it because it's kind of odd. When I know more, I fully intend to do it with whatever the latest build is and then actually make a full report.  The problem is, the testing takes some time (I have to let it charge, let it drain, let it sit a while with the cable plugged in (which causes the reproted % to be wrong) then unplug it to see where it is, etc.  Much more involved than just letting the battery drain.

Anyway, like I said, it's odd :D

Navigation

[0] Message Index

[#] Next page

[*] Previous page