Hi,

after trying some usb keyboard/mouse combinations I think about going away from this polling solution and think about recompiling the xserver to get mouse support out of the box.

Has anyone tried it yet or knows a good point to start to recompile?

I think the first step would be to locate the maemo xserver sources for OS2008....

Any hints or experiences appreciated...

Regards,
asys3

Hi,
I want to report you my personal experience:

i installed kde and realized that a mouse would be pretty good.
So I read this thread and installed usb mouse 1.1.
I didn't install dbus script.
And everything works good: I have my wireless usb mouse working and internal keyboard works too (I have N810). KDE always shows cursor and now I have cursor even in default Window Manager (even if it works only in some parts of the ui).

Thank you very much for mouse support, even if it's a little bit cpu hungry. I think I'll buy Apple Mighty...

Hello,

Thank you everyone for all the hard work getting the mouse support up and running.

I just received the USB OTG adapter this morning, installed the nice .deb, made the cursor visible, rebooted, plugged in my USB mouse to the adapter, and presto! a mouse cursor. And now with my nifty new bluetooth keyboard, who needs a klunky laptop!

Now, I'm very new at all this, but I tried the VNC server trick to get the mouse working on some of the unresponsive areas (task launcher, some applets) by adding the option "-extension XInputExtension" to the end of the ARGS="...." string in the file /etc/init.d/x-server. http://maemo.org/community/wiki/how_...800_from_a_pc/
Rebooted and the mouse worked EVERYWHERE!

BUT, as I found out earlier, this now toasts my bluetooth keyboard - any attempt to resume the BTKB connection, and my poor little N800 reboots.

If there is any way I can help out...

How did you make the cursor visible? Mine will not show...

I tested the wireless USB mouse on KDE and it works on every app I've tested. There are literally a hundred plus apps so it will take me some time to test each one but I can see the mouse on any part of screen and app and it even works while screen keyboard is on screen. The best part is that I have right click menu ability. Scroll wheel and left and right click works. Wireless USB Mouse with bt keyboard and full office apps and real computer apps makes my N800 the smallest full feature computer out there. Great job JoLouis and Benson. Sweeeet! Dan

Ok, I can finally see the cursor in Maemo browser, but its sporadic. I really hope ths continues to be developed because as has been stated above, with its virtually a pc like experiece with a bluetooth mouse and bluetooth keyboard.

It'll stay sporadic until Nokia decides to change from its no-mouse, no-cursor ways. Official support is not needed, but something has to change..

I managed to successfully connect my MoGo Bluetooth mouse to N800 after some consecutive failures.
I first tryed to find on forums the xterm utility used for send Bluetooth commands (which by the way I didn’t succeed... and my memory don’t helps me), but I found an interesting post about clearing Bluetooth setting necessary on pairing failures. The Idea is to delete /var/lib/bluetooth/[your_bt_mac_id] folder and REBOOT the tablet.
After this step I used the Bluetooth manager, found the device, tried to pair, entered 0000 as code, and pressed a button on mouse.
I got the successfully paired message.
Hope it will work also for you.

Thread Suggestion:
Please continuously update the first post with the latest successful method of using mouse and make cursor visible to be easy for everyone to find best way of doing it. Is really hard to search on all posts to see what works.

I have a question: is possible to make the right click working?
At this moment works like with stylus, keeping left click longer. On rDesktop worked as expected.
Also I'm having problems with left click on xterm, does not works for example on mc, but click with stylus works.

Let's hope Diablo will know to handle mices...

I went this route and did not enjoy the experience. It took a bit of patching to compile due to the changes in the X server from the stock configuration. Once I had it compiled it worked exactly as the existing one did: no mouse support. There were no compiler flags/#defines to turn it on, nothing obviously commented out, even all the drivers for various input devices were still there. It just didn't work. I asked Daniel Stone about it (The Nokia guy who performed the changes) and I got the impression that it was indeed something they disabled so it would always be forced to used tslib; he hangs out on the maemo dev list so feel free to ask him since my memory is a little fuzzy after so many months. Even the diffs for the patches didn't seem to account for the problems. The only thing I can think of is that KDrive (the embedded version of X) can only handle one pointer device at a time. The init file for the X server contains this line:
ARGS="-mouse tslib -nozap -dpi $DISPLAY_DPI -wr -nolisten tcp"

I'm no X-server guru by any stretch but we may end up having to put a code shim between the X server and tslib that accepts input from a pointer-type device as well as tslib and combines the stream of events before passing it to the X server. The rub there is that we'll need to make sure we use the same protocol as tslib or the X server will be very unhappy (I tried to force it to read from a mouse instead of tslib by changing the arguments to the init script and it made the X server crash almost instantly when trying to use the mouse).
The sources for the X server are public and in the repo for the rest of the maemo developer sources/packages. Good luck and let me know if you have further questions.

Larry