public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Butirsky <butirsky@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Lenovo Legion M600 wireless bluetooth mouse connected and paired yet not working
Date: Sat, 19 Feb 2022 01:31:17 +0300	[thread overview]
Message-ID: <1d65ec6e-7494-c148-8b4a-b2dc463fb141@gmail.com> (raw)
In-Reply-To: <CABBYNZJg0qHO4gvLh8O44um68CzRMM4PE3OymRhGfiQ1kDZO1w@mail.gmail.com>

On 2/19/2022 12:38 AM, Luiz Augusto von Dentz wrote:
> Hi Andrey,
>
> On Fri, Feb 18, 2022 at 1:26 PM Andrey Butirsky <butirsky@gmail.com> wrote:
>> Hi Luiz,
>>
>> On 2/19/2022 12:15 AM, Luiz Augusto von Dentz wrote:
>>> Hi Andrey,
>>>
>>> On Fri, Feb 18, 2022 at 3:55 AM Andrey Butirsky <butirsky@gmail.com> wrote:
>>>> Important addition: the mouse does work on Android 8.10.
>>>>
>>>> Does it mean Android has that special HID driver that missed on Linux?
>>>> 8.10 came out long before the mouse even existed..
>>>>
>>>> Do you have explanation?
>>> No, in fact android seems to also be using UHID, does it uses a vendor
>>> app to set it up?
>> No, it just works right away after connecting from Settings.
>>
>> Also, the mouse works on Windows, without additional software. It's
>> detected as "Bluetooth Low Energy GATT compliant HID device" there.
> Did you manage to test with latest git? Note that windows does seem to
> handle composite HoG device:
>
> https://github.com/bluez/bluez/issues/258
Thanks, updated the issue with info. My device is probably composite 
indeed, as these ones:

https://github.com/kyokenn/rogdrv#rogdrv

I tried BlueZ master but userspace only.


> Btw, it could be due to:
>
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=aa699cb762a02ec7409940ddcfe65b788de8270d
>
> There were some systems (afaik 32bits) with a problem with the header
> copy we had.
My system is 64-bit. Do you think it's still worth to try to update 
BlueZ kernel part? If so, what is the procedure?
Didn't find how to build BlueZ out-of-tree kernel modules or something..

  reply	other threads:[~2022-02-18 22:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 19:49 Lenovo Legion M600 wireless bluetooth mouse connected and paired yet not working Andrey Butirsky
2022-02-15 23:22 ` Luiz Augusto von Dentz
2022-02-16 16:03   ` Andrey Butirsky
2022-02-16 20:26     ` Luiz Augusto von Dentz
2022-02-16 20:32       ` Andrey Butirsky
2022-02-16 21:08         ` Luiz Augusto von Dentz
2022-02-16 22:35           ` Andrey Butirsky
2022-02-16 23:10             ` Luiz Augusto von Dentz
2022-02-16 23:55               ` Andrey Butirsky
2022-02-17 13:06               ` Andrey Butirsky
2022-02-18 11:54               ` Andrey Butirsky
2022-02-18 21:15                 ` Luiz Augusto von Dentz
2022-02-18 21:26                   ` Andrey Butirsky
2022-02-18 21:38                     ` Luiz Augusto von Dentz
2022-02-18 22:31                       ` Andrey Butirsky [this message]
2022-02-19 23:18                       ` Andrey Butirsky
2022-02-20  0:06                         ` Andrey Butirsky
2022-03-08 10:30                     ` Bastien Nocera
2022-03-09 10:21                       ` Andrey Butirsky
2022-03-22  5:48                       ` Luiz Augusto von Dentz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1d65ec6e-7494-c148-8b4a-b2dc463fb141@gmail.com \
    --to=butirsky@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox