All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204589] Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Date: Wed, 24 Jan 2024 16:49:15 +0000	[thread overview]
Message-ID: <bug-204589-62941-7XGwsDL4Nc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204589-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204589

Lee Fleming (LeeFlemingster@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |LeeFlemingster@protonmail.c
                   |                            |om

--- Comment #20 from Lee Fleming (LeeFlemingster@protonmail.com) ---
I have been able to reproduce this problem.

OpenSuse Tumbleweed.
Framework AMD 13-inch laptop.

I've only seen the magic trackpad 2 disconnect under a specific condition.

I have an LG Xboom bluetooth speaker. When the speaker is on, connected to
bluetooth and connected to USB to charge, then when I stop moving the mouse
pointer for 5 seconds the trackpad disconnects.

This only happens when the speaker is connected to the USB A port (front left).
If connected to the USB C port (or physically disconnected entirely) then the
problem goes away.

I have not tried swaping the USB modules on this laptop. Not all the ports are
made equal. The speaker was connected to port 2 in this diagram.
https://knowledgebase.frame.work/en_us/expansion-card-functionality-on-framework-laptop-13-amd-ryzen-7040-series-SkrVx7gAh

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2024-01-24 16:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 10:19 [Bug 204589] New: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes bugzilla-daemon
2022-01-11 17:20 ` [Bug 204589] " bugzilla-daemon
2022-06-15 22:19 ` bugzilla-daemon
2022-06-16 13:04 ` bugzilla-daemon
2023-01-11 21:15 ` bugzilla-daemon
2023-01-11 21:19 ` bugzilla-daemon
2023-01-11 21:23 ` bugzilla-daemon
2023-01-11 22:06 ` bugzilla-daemon
2023-05-22 11:54 ` bugzilla-daemon
2023-06-02 16:37 ` bugzilla-daemon
2023-06-23 14:23 ` bugzilla-daemon
2023-11-02  8:17 ` bugzilla-daemon
2023-12-14 20:54 ` bugzilla-daemon
2023-12-16 23:20 ` bugzilla-daemon
2023-12-17  0:31 ` bugzilla-daemon
2024-01-24 16:49 ` bugzilla-daemon [this message]
2024-01-24 19:41 ` bugzilla-daemon

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-204589-62941-7XGwsDL4Nc@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.