Cacko Rom 1.22 Is Available!

[ev1l]

dble post.

[ev1l]

Controling LEDs is not a problem, but there is no way to know if lid was closed or open, it's just a trigger, which emmits the same keycode whenever lid is opened or closed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66251\"][{POST_SNAPBACK}][/a][/div]

Can't you poll the current screen resolution? That should give you the orientation.

Where exactly is the option to turn off the screensaver?  I've never been able to kill mine, and yet never been able to get any good screensaver working (it's always just the floating time).  I tried deselecting that applet and all kinds of things.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=72911\"][{POST_SNAPBACK}][/a][/div]

Like I said in the other thread, leave the applet running (you can disable the icon in the options if you don't like that), and set the SS module to none, so it'll launch nothing when it's been idle for a while.

[maslovsky]

Controling LEDs is not a problem, but there is no way to know if lid was closed or open, it's just a trigger, which emmits the same keycode whenever lid is opened or closed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66251\"][{POST_SNAPBACK}][/a][/div]

Can't you poll the current screen resolution? That should give you the orientation.

Yes, I can but it won't help. If you noticed there are two small buttons, so the screen rotates when only one of them is pressed and blanks with both.

[ev1l]

Yes, I can but it won't help. If you noticed there are two small buttons, so the screen rotates when only one of them is pressed and blanks with both.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73081\"][{POST_SNAPBACK}][/a][/div]

edit: got it, you mean the little switches that allow the Z to detect screen position and orientation. Can you detect whether the screen is on? Can you read the buttons directly?

[maslovsky]

Yes, I can but it won't help. If you noticed there are two small buttons, so the screen rotates when only one of them is pressed and blanks with both.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73081\"][{POST_SNAPBACK}][/a][/div]

edit: got it, you mean the little switches that allow the Z to detect screen position and orientation. Can you detect whether the screen is on? Can you read the buttons directly?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73103\"][{POST_SNAPBACK}][/a][/div]

No, like I said the same keycode is generated by Qtopia whenever lid is opened or closed. The current state is definitly kept in somewhere Qtopia, but I can't do the same because it will be unreliable. A very simple example: user closes the lid, then turns Zaurus off, opens the lid and turns Zaurus on.  Since application cannot detect the suspend event, it completely looses track of the lid state...

[Stubear]

If you can grab the qcop message stream somehow (like qcop test does) then you might be able to use that as a way of detecting lid state.

Here is some data captured with qcop test on C760 running Cacko Lite + Japanese.

Lid closed

23:43:36 - Recv - setBacklight(int) int : - 5

Lid opened

23:46:01 - Recv - setBacklight(int) int : - 3

Close Lid then power off

23:54:16 - Recv - setBacklight(int) int : -5
23:54:20 - Recv - suspending()

Open lid then power on

23:56:16 - Recv - setBacklight(int) int : -3
23:56:16 - Recv - resumed()
23:56:16 - Recv - setBacklight(int) int : -3  --- Yes it did give 2 of these

I think that setBacklight to -5 is an indicator that the screen has LCD has gone off rather than than the lid being closed.

I'll test further and report back. (I'll also see if qcop test sheds any light on why the light applet blanks screen when rotated at lowest level. while lowering the level by Fn+3 doesn't)

Stu

[maslovsky]

Unfortnately that doesn't help either. All I see is that brightness levels are being set, pretty much if user was changing brightness level manualy

Yes, looks like I can trap suspend and resume event, but that still doesn't give a reliable way to figure out what's the status of the lid...

[ev1l]

Yes, looks like I can trap suspend and resume event, but that still doesn't give a reliable way to figure out what's the status of the lid...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73170\"][{POST_SNAPBACK}][/a][/div]

But that doesn't really matter. I'd be just as happy with blinky led indicating the Z is on when the LCD is off as with a led indicating the Z is on and the lid is closed. I'd basically just like a visual cue from the led when you can't tell it from the Zaurus itself.
It'd actually be better if that led blinked anytime the Z was on with a keyboard off.

Combining that with throttling to 200mhz when the LCD is off would allow someone to carry the Z on all day. I don't need the Z to suspend when I close the lid, since there's no way to start it again when you open it. But a blinky led and a throttle CPU would allow a user to close it and keep a very fast startup time (just the time for the LCD to turn back on, since throttling back to full speed is pretty much instantaneous).

Ideas, comments, insults?

[DRDR]

Dear experts,

I can still not get a connection with my D-Link DCF-660W w-lan card. Maybe someone can tell me - not a Linux expert - what is going on by looking at the attached dmesg output. It contains lot's of wifi0 errors. :-(

Thanks!

[Cryssli]

Yes, looks like I can trap suspend and resume event, but that still doesn't give a reliable way to figure out what's the status of the lid...

But that doesn't really matter. I'd be just as happy with blinky led indicating the Z is on when the LCD is off as with a led indicating the Z is on and the lid is closed. I'd basically just like a visual cue from the led when you can't tell it from the Zaurus itself.
It'd actually be better if that led blinked anytime the Z was on with a keyboard off.

Combining that with throttling to 200mhz when the LCD is off would allow someone to carry the Z on all day. I don't need the Z to suspend when I close the lid, since there's no way to start it again when you open it. But a blinky led and a throttle CPU would allow a user to close it and keep a very fast startup time (just the time for the LCD to turn back on, since throttling back to full speed is pretty much instantaneous).

Ideas, comments, insults?

Yea! This would be nice!
Just one question aeh... if i close the LCD, the zaurus goes to suspend right? Does it consume more power as if the cpu is throttled when closing the lcd?

I cannot find any battery change applet tovarish mentioned here:
https://www.oesf.org/forums/index.php?showtopic=11767

[ev1l]

Yea! This would be nice!
Just one question aeh... if i close the LCD, the zaurus goes to suspend right? Does it consume more power as if the cpu is throttled when closing the lcd?

No, when you close the lid the LCD's power gets cut off, but that's it.
You can't really get a usable solution out of "suspend on lid close" because there's no hardware to wake the damn thing back up when you open it again. That's why the throttle is an attractive idea: if the Z isn't suspended but just down-clocked, it can still monitor for a state change and go back to normal operation when you open it.

I still don't know whether it's feasable though, Mas hasn't weighted in yet.

[Flandry]

Yea! This would be nice!
Just one question aeh... if i close the LCD, the zaurus goes to suspend right? Does it consume more power as if the cpu is throttled when closing the lcd?

No, when you close the lid the LCD's power gets cut off, but that's it.
You can't really get a usable solution out of "suspend on lid close" because there's no hardware to wake the damn thing back up when you open it again. That's why the throttle is an attractive idea: if the Z isn't suspended but just down-clocked, it can still monitor for a state change and go back to normal operation when you open it.

I still don't know whether it's feasable though, Mas hasn't weighted in yet.

I like that idea a lot, but mightn't it cause stability problems?  When i set Kino to downclock, my Z gets confused eventually.  Maybe that's just kino?

Ev1l, will you please explain how you were able to disable the screen saver?

[craigtyson]

I also use Kino with the lid down in the car.  Suspend would not add to the usability of my Z in my case.  There is a little button on the outside that can be pressed as you close the lid though......... ;-)

[ev1l]

Ev1l, will you please explain how you were able to disable the screen saver?

Set the screen-saver module to (none) in the LSUSSSU applet, and let the tray applet running (you can set the icon to not appear, but the applet must run)

There is a little button on the outside that can be pressed as you close the lid though

I hate that button.

[charlesa]

Hi all -

I just flashed my 860 with 1.22.  I agree with everyone, very nice.  A few observations...

Like others, I had probs getting my DLink 660 WiFi CF card to work.  Apart from the other suggestions in this thread, it turns out that the ESSID field in 1.22 must _not_ contain a name with  a space.  My AirPort ESSID was called "AP 1", but the Z wouldn't take this.  Solution: reconfigure my AirPort with a new ESSID name "AP1" omitting the space in the name.  Voila!

Now I am trying to customize smb.conf.  It seems that /usr is mounted read-only; I can't write it even as SU.  Is this normal?  Why is this?  I flashed the Z with a 28mb root.  Is there something I am overlooking?

# cd /usr/lib.rom/samba/
# ls -l
drwxr-xr-x    1 root     root           37 Apr  7  2004 codepages
-rw-r--r--    1 root     root          905 Apr  7  2004 smb.conf
# chmod g+w smb.conf
smb.conf: Read-only file system
#
# whoami
root
# id
uid=0(root) gid=0(root)
#
# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                28.0M     28.0M         0 100% /
/dev/ram1                44.0k     26.0k     18.0k  59% /dev
/dev/loop0               22.6M     22.6M         0 100% /usr
/dev/mtdblock3           93.0M      3.4M     89.6M   4% /home
none                     10.0M     52.0k      9.9M   1% /dev/shm
/dev/mmcda1             243.9M    177.5M     66.4M  73% /usr/mnt.rom/card
#