Author Topic: Help Blanker  (Read 8958 times)

karlto

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
    • http://
Help Blanker
« Reply #15 on: April 12, 2006, 04:31:53 pm »
Quote
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122796\"][{POST_SNAPBACK}][/a][/div]
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...
SL6000-L, RC12

10BaseT

  • Newbie
  • *
  • Posts: 13
    • View Profile
    • http://
Help Blanker
« Reply #16 on: April 20, 2006, 04:53:50 pm »
Quote
Quote
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122796\"][{POST_SNAPBACK}][/a][/div]
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...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122911\"][{POST_SNAPBACK}][/a][/div]

Yeah thats about what I figured too... I haven't submited a bug report yet    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...
Loadout
(SL-C3100 - Cacko 1.23, SMC(2642w) wireless CF card, SanDisk ultra II 1gb, usb others...)
-- "Ha, he called it a PDA..."

karlto

  • Sr. Member
  • ****
  • Posts: 343
    • View Profile
    • http://
Help Blanker
« Reply #17 on: April 20, 2006, 08:04:59 pm »
Quote
Yeah thats about what I figured too... I haven't submited a bug report yet    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...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123951\"][{POST_SNAPBACK}][/a][/div]
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: [Select]
#!/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.
SL6000-L, RC12