Bluetooth mouse does not connect after reboot

[Maksim Yevmenkin]

On Fri, Jan 21, 2011 at 5:36 AM, David Demelier
<demelier.david at gmail.com> wrote:
> On 21/01/2011 09:08, David Demelier wrote:
>>
>> On 20/01/2011 23:43, Maksim Yevmenkin wrote:
>>>
>>> On Thu, Jan 20, 2011 at 12:43 PM, Oliver
>>> Fromme<olli at lurza.secnetix.de> wrote:
>>>>
>>>> David Demelier wrote:
>>>> > It has two logical button at the both sides. It does "backward" or
>>>> > "forward" in firefox or the same in nautilus. My logitech mouse has
>>>> the
>>>> > same feature on the wheel. if I press the mouse wheel to the side it
>>>> > does 2 more click so the wheel has not only one middle click but
>>>> three.
>>>> > The middle click and "back" "next"
>>>> >
>>>> > 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.
>>>
>>> i'd like to know how those "non-working" events are reported at hid
>>> level. David, could you please use hcidump and obtain traces for those
>>> "non-working" events?
>>>
>>
>> Thanks for your interest :-). There is the output when I press a middle
>> click :
>>
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>
>> And there is when I press back and next :
>>
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>  > ACL data: handle 0x000b flags 0x02 dlen 12
>> L2CAP(d): cid 0x41 len 8 [psm 0]
>>
>> It seems to be detected! Now just need to make it works.
>>
>>>> By the way, I don't think this is bluetooth related at all.
>>>> Maybe you should open a new thread on the x11 list.
>>>
>>> it may or may not be bthidd related :) if bthidd can decode and put
>>> those events into kernel then there is no reason for it to not do that
>>> :)
>>>
>>> thanks,
>>> max
>>
>> Cheers,
>>
>
> With the -R hcidump flag I got this :
>
> for wheel up:
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 01 00
>
> for wheel down:
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 FF 00
>
> for wheel logical button to left:
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 00 FF
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 00 00
>
> and for wheel logical button to right:
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 00 01
>> 02 0C 20 0C 00 08 00 43 00 A1 02 00 00 00 00 00 00
>
> It seems they are well detected as logical button since they sends "pressed"
> and "released" events. So now it's to find out why they are not detected by
> xev.

great! thanks! i was about to ask you for binary dump :) because i was
really interested in those 8 bytes of payload that were not shown in
the first dump :) i think now i should be able to decode those.

thanks,
max