I'm trying to understand how the screen lock actually works on the n810. How I'd like it to operate:
1. Slide keyboard closed
2. Slide screen-lock switch.
3. Device says "screen and keyboard locked"
4. Device goes to sleep, and any accidental taps or button presses are ignored.
5. Slide keyboard open
6. Device says "screen and keyboard unlocked"
7. I use device.
8. Slide keyboard closed
9. Goto step 3.

It doesn't seem to work like this in practice. Sometimes it relocks when I close the keyboard, sometimes not. If I even understood the algorithm it uses that would help so I don't forget to have it locked.

If it helps, I'm running with the "lock screen with screensaver" mode disabled. Basically I just want the keyboard sliding open or closed to unlock and lock the screen, unless I use the slider manually for the odd times when I want the keyboard closed for tapping (in the car).

Thanks for any insights.

Should be possible to implement via dbus-scripts... and possibly powerlaunch, but I don't think that's necessary.

If I had an N810, I'd hack a POC up and post it, but I have an N800.

1. Use dbus-monitor to explore for slider open and close messages; I think I heard that they are there.
2. Figure out how to programmatically lock the screen. Again, dbus-monitor; watch what happens when you manually lock and unlock.
3. Write scripts to do B, and set up dbus-scripts to run them when it sees A.

My experience has been that, if you are locked already, opening the keyboard and closing the keyboard will auto-relock. Using the interface/pressing buttons/whatever will break this cycle and you have to relock using the top lock.

Both of these are helpful... I ran a quick dbus-monitor experiment and stuff is generated on opening and closing the keyboard and sliding the lock button so this seems doable once I learn more about dbus.