I do not use the included stand, but I use my home-made case with a home-made kick-stand. My camera's battery is dead atm, but I will try to get pictures up later or tomorrow. One thing I have noticed is that if the IR port lines up perfectly with the IR eye on the keyboard, it will act really strange. You have to have the keyboard at an angle to the IR port. In landscape (rotated right) the IR eye on my keyboard is a little to the right of the IR port on the Zaurus. Otherwise, typing will result in wrong letters , backspaces, and other uncontrollable weirdness.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=135065\"][{POST_SNAPBACK}][/a][/div]
Thanks Oak,
It would be interesting to see your setup. My setup is quite a bit simpiler. I have a pen, pencil or post-it pad (what ever is handy) proping up the SL-6000 with the IR window facing toward me (rotated left). The keyboard is just sitting on the desk, with the Z behind (farther way) it.
I have found there there is a no-go distance I want to avoid with the Belkin keyboard. Yesterday I tried running the keyboard about 2" (5cm) away from the Z, and I was getting good clean key presses. If I run the keyboard only an inch (2.5 cm) away, that seems to be the no-go zone, resulting in what you are seeing, odd letters, backspaces, and other weirdness.
In my case, I think this is due to that fact that the Belkin has 2 LED transmitters, one shooting straight out, and the other angled up (to work with the included stand). I think when the keyboard is only 1" (2.5 cm) away, the two signals are interfering with eachother, which results in the weirdness. You may be experiencing the same thing, but by moving the IR windows off axis, you are avoiding the interference.
To prove my theory, I set the keyboard in the no-go zone, and took a business card, and covered the right half of the keyboard IR window while typing. The keyboard worked just fine. Removing the business card, and it was back to weirdness. For you, it may be the left side (of the IR window) since your setup is a little different.
On a slightly different subject, I think there is a bug in the IRK for Qcop macros, and that is why I can't get the backlight to shut off. I have pulled down the source, and I'll have to look into a bit more.
Thanks again for all the help,
Craig...