Bluetooth mouse does not connect after reboot

[Maksim Yevmenkin]

On Fri, Jan 21, 2011 at 12:00 AM, Oliver Fromme <olli at lurza.secnetix.de> wrote:
> Maksim Yevmenkin wrote:
>  > Oliver Fromme wrote:
>  > > David Demelier wrote:
>  > >  > These back/next buttons are not detected by xev. That's my current
>  > >  > trouble :-)
>  > >
>  > > If xev doesn't see them, the next step would be to find out
>  > > if moused sees them.  Run moused with the -f -d options, so
>  > > it will print all events.
>  >
>  > sorry, i'm a bit confused here. moused has nothing to do with
>  > bluetooth mouse. bthidd decodes hid reports (received over bluetooth
>  > link), fills mouse_info structure, and, feeds mouse_info to kernel via
>  > mouse_action ioctl. so, i don't think that moused will be able to trap
>  > that.
>
> Oops ...  I'm sorry.  I thought that bluetooth would feed
> the sysmouse protocol data via moused(8), just like USB.
> I've never used a bluetooth mouse before, which explains
> my mistake.  :-)

no worries :) i just thought that i was missing or/and
misunderstanding something here :)

> But on the other hand, I think it would be very useful if
> bluetooth mice used moused(8), too, so you could use all
> of its features, like dynamic acceleration, physical-to-
> logical button mapping, wheel mapping, and so on.  That
> might even enable David to solve his problem.

well, yes. the thing is that there is no
/dev/bluetooth_mouse_device_node. so moused can't really read from it.
technically, bluetooth mouse and usb mouse should be nearly identical.
the same hid report is delivered over rf link instead of usb link.
possible options here are

1) virtual usb mouse device driver, i.e. /dev/vums that would accept
hid reports from user space, decode them and present them in a format
moused(8) can understand. something similar to vkbd(4), tap(4), tun(4)
etc.

2) moused(8) appears to have support for x10 mouseremote. that is, it
could read mouse events from /var/run/MouseRemote unix socket
(according to the man page). so, bthidd(8) could decode hid reports,
translate them into x10 mouseremote protocol and feed those to
moused(8) via the unix socket. i don't know how flexible/extensible
x10 mouseremote protocol is and if it has support for all fancy
buttons/wheels etc.

thanks,
max