Problem with Mighty Mouse

Problem with Mighty Mouse

[Bastien Nocera]

Heya,

I've tested a Bluetooth Apple Mighty Mouse (AA1197) and though I can
move the cursor without a problem, none of the buttons work. evtest
doesn't see any button events.

Any ideas what I should look at, or which tool I could use to capture
the raw data?

Cheers

Re: Problem with Mighty Mouse

[Benjamin Tissoires]

Hi Bastien,

On Sat, Oct 12, 2013 at 7:48 PM, Bastien Nocera <hadess@hadess.net> wrote:
> Heya,
>
> I've tested a Bluetooth Apple Mighty Mouse (AA1197) and though I can
> move the cursor without a problem, none of the buttons work. evtest
> doesn't see any button events.
>
> Any ideas what I should look at, or which tool I could use to capture
> the raw data?

you can use hid-recorder[1] to retrieve the raw events from hidraw (it
mainly does a hexdump on /dev/hidrawX or you can use the kernel
debugfs interface for some devices which are preventing hidraw to
forward the events).

Ideally, you should give the output of evtest (or evemu) and
hid-recorder at the same time so we can have an idea of the input and
the output of the kernel driver.

Cheers,
Benjamin

[1] http://bentiss.github.io/hid-replay-docs/

>
> Cheers
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Problem with Mighty Mouse

[Bastien Nocera]

On Thu, 2013-10-17 at 15:30 -0400, Benjamin Tissoires wrote:
> Hi Bastien,
> 
> On Sat, Oct 12, 2013 at 7:48 PM, Bastien Nocera <hadess@hadess.net> wrote:
> > Heya,
> >
> > I've tested a Bluetooth Apple Mighty Mouse (AA1197) and though I can
> > move the cursor without a problem, none of the buttons work. evtest
> > doesn't see any button events.
> >
> > Any ideas what I should look at, or which tool I could use to capture
> > the raw data?
> 
> you can use hid-recorder[1] to retrieve the raw events from hidraw (it
> mainly does a hexdump on /dev/hidrawX or you can use the kernel
> debugfs interface for some devices which are preventing hidraw to
> forward the events).
> 
> Ideally, you should give the output of evtest (or evemu) and
> hid-recorder at the same time so we can have an idea of the input and
> the output of the kernel driver.

Colour me confused, it works again. I'll bear those advices in mind if
and when it happens again.

Cheers