OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V  < 1 2  
Reply to this topicStart new topic
> Help Blanker, how does it work? and whats does it do?
karlto
post Apr 12 2006, 12:31 PM
Post #16





Group: Members
Posts: 343
Joined: 3-October 05
From: NZ
Member No.: 8,243



QUOTE(10BaseT @ Apr 12 2006, 07:37 PM)
What I meant by * * * is u can put any value there... I don't think a xset dpms takes * as a valid argument

but yeah, seems to be working fine smile.gif
*

I was actually referring to a wildcard too (I'm not very articulate sometimes) - from what the man page says, 'xset +dpms' and 'xset -dpms' should be taken care of automatically depending on what values you use. I see from my own tests also that pdaXrom does not always do this, and it needs to. The environment the blanker was originally written for maybe supported this better so explicit commands were not required?

Another caveat is that any power events (suspend, battery/AC change) will reset all these settings.

Perhaps a good project would be to integrate the blanker functionality into the lightnpower.py script as a third mode, indicated by a file flag or something? The battery applet/power management seems to honour these settings consistently...
Go to the top of the page
 
+Quote Post
10BaseT
post Apr 20 2006, 12:53 PM
Post #17





Group: Members
Posts: 13
Joined: 24-March 06
From: USA, CA(Santa Cruz)
Member No.: 9,437



QUOTE(karlto @ Apr 12 2006, 12:31 PM)
QUOTE(10BaseT @ Apr 12 2006, 07:37 PM)
What I meant by * * * is u can put any value there... I don't think a xset dpms takes * as a valid argument

but yeah, seems to be working fine smile.gif
*

I was actually referring to a wildcard too (I'm not very articulate sometimes) - from what the man page says, 'xset +dpms' and 'xset -dpms' should be taken care of automatically depending on what values you use. I see from my own tests also that pdaXrom does not always do this, and it needs to. The environment the blanker was originally written for maybe supported this better so explicit commands were not required?

Another caveat is that any power events (suspend, battery/AC change) will reset all these settings.

Perhaps a good project would be to integrate the blanker functionality into the lightnpower.py script as a third mode, indicated by a file flag or something? The battery applet/power management seems to honour these settings consistently...
*



Yeah thats about what I figured too... I haven't submited a bug report yet tongue.gif because my work around is working fine other then I do have to be careful of (suspend, battery/AC change). I'm debating wheather I want to try rewriting the blanker and the lightnpower.py script into one program or script because there are other times when supending is bad like rewiting files to the Zaurus via USB...
Go to the top of the page
 
+Quote Post
karlto
post Apr 20 2006, 04:04 PM
Post #18





Group: Members
Posts: 343
Joined: 3-October 05
From: NZ
Member No.: 8,243



QUOTE(10BaseT @ Apr 21 2006, 09:53 AM)
Yeah thats about what I figured too... I haven't submited a bug report yet  tongue.gif  because my work around is working fine other then I do have to be careful of (suspend, battery/AC change). I'm debating wheather I want to try rewriting the blanker and the lightnpower.py script into one program or script because there are other times when supending is bad like rewiting files to the Zaurus via USB...
*

After claiming here that everything worked fine for me I discovered it didn't... so I came up with a workaround also. The problem is that the blanker is compiled, so I gave away the idea of using that. The lightnpower.py script however is actually very reliable, and the settings here are honoured throughout (settings in ~/Choices/lightnpower.cfg). So, I made a second file with some always-on settings, and:

CODE
#!/bin/sh

case "$1" in

       on)
         if [ -f ~/Choices/lightnpower.cfg.blanker ]; then
                 mv ~/Choices/lightnpower.cfg ~/Choices/lightnpower.cfg.normal
                 mv ~/Choices/lightnpower.cfg.blanker ~/Choices/lightnpower.cfg
                 /usr/bin/lightnpower.py --loadandquit
         fi
        ;;

       off)
         if [ -f ~/Choices/lightnpower.cfg.normal ]; then
                 mv ~/Choices/lightnpower.cfg ~/Choices/lightnpower.cfg.blanker
                 mv ~/Choices/lightnpower.cfg.normal ~/Choices/lightnpower.cfg
                 /usr/bin/lightnpower.py --loadandquit
         fi
        ;;

       *)
         echo "Usage: $0 (on|off)"
         exit 1
        ;;

esac

exit 0

This script just copies the different settings file in, runs the lightnpower.py script to update settings, and they are used until swapped back. Instead of 'on' and 'off', it would be reasonably trivial to have any number of modes/files...

And you don't have to be careful about taking on or off AC power or suspending at all.
Go to the top of the page
 
+Quote Post

2 Pages V  < 1 2
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 23rd March 2019 - 09:28 PM