From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 213245] New: Logitech bluetooth mouse V270 doesn't wake up properly on move only on click/roll
Date: Thu, 27 May 2021 20:14:20 +0000 [thread overview]
Message-ID: <bug-213245-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213245
Bug ID: 213245
Summary: Logitech bluetooth mouse V270 doesn't wake up properly
on move only on click/roll
Product: Drivers
Version: 2.5
Kernel Version: 5.12.5
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: przemo@firszt.eu
Regression: No
Logitech bluetooth mouse V270 connects without problems, all buttons work, but
left for a few seconds goes to sleep. Moved comes back to life for a split
second (cursor moves a bit, hcidump shows it goes sniff->active-<sniff). If I
keep clicking or using the roll the mosue works. Olso works when I keep moving
it. hcidump:
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 256 mode 0x02 interval 80
Mode: Sniff <- mouse nit moved
> ACL data: handle 256 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 19]
HIDP: Data: Input report <- mouse moves for a split second
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 256 mode 0x00 interval 0
Mode: Active <- mouse moves for a split second
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 256 mode 0x02 interval 80
Mode: Sniff <- back to sniff mode. cursor stays frozen unless I click or
use roll
Further moving doesn't generate anything in the hcidump log, unless I click or
use roll.
Hardware is intel AX200, firmware loaded properly:
$ dmesg | grep iwlwifi
[ 7.819489] iwlwifi 0000:48:00.0: enabling device (0000 -> 0002)
[ 7.883697] iwlwifi 0000:48:00.0: api flags index 2 larger than supported by
driver
[ 7.883716] iwlwifi 0000:48:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version:
89.3.35.37
[ 7.883962] iwlwifi 0000:48:00.0: loaded firmware version 62.49eeb572.0
cc-a0-62.ucode op_mode iwlmvm
[ 8.102109] iwlwifi 0000:48:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz,
REV=0x340
[ 8.313725] iwlwifi 0000:48:00.0: base HW address: a4:42:3b:f9:38:fa
[ 8.332830] iwlwifi 0000:48:00.0 wlp72s0: renamed from wlan0
The mouse works fine on other systems or on android phone. System info:
fedora:/home/przemo
$ rpm -qi bluez | grep Version
Version : 5.58
fedora:/home/przemo
$ uname -a
Linux fedora 5.12.5-300.fc34.x86_64 #1 SMP Wed May 19 18:03:50 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-27 20:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-213245-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.