Absolute mouse not working on Android #170

New issue

Open

opened 2026-02-20 08:20:54 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 08:20:54 -05:00

Owner

Originally created by @DyonR on GitHub (Mar 22, 2025).

It seems that Absolute mouse does not work on Android.
I've tested it on a device running LineageOS 21 (Android 14) and and older LG V30 device running Android 9.
Relative mouse does work.
App: 0.3.8
System: 0.2.3
USB Device classes enabled: Absolute Mouse only
If I enable Keyboard, the keyboard does work, so it's not an issue related to USB detection.
Also tried different USB identifiers.

I was unable to find an issue related to this, which I found surprising, unless I missed it.

Originally created by @DyonR on GitHub (Mar 22, 2025). It seems that Absolute mouse does not work on Android. I've tested it on a device running LineageOS 21 (Android 14) and and older LG V30 device running Android 9. Relative mouse does work. App: 0.3.8 System: 0.2.3 USB Device classes enabled: Absolute Mouse only If I enable Keyboard, the keyboard does work, so it's not an issue related to USB detection. Also tried different USB identifiers. I was [unable to find an issue related to this](https://github.com/jetkvm/kvm/issues?q=android), which I found surprising, unless I missed it.

deekerman added the

component: usb/hid

component: hid/mouse

labels

2026-02-20 08:20:54 -05:00

deekerman commented

2026-02-20 08:20:55 -05:00

Author

Owner

@rmschooley commented on GitHub (May 26, 2025):

Do you still have this issue using the latest firmware? I am able to use the absolute mouse as well as the relative mouse just fine on my Android (which is a Samsung Galaxy S22+ with Android 15 UI 7). FYI - I am using a bluetooth mouse (Logitech MX Master 3) attached to this phone to do this testing.

@rmschooley commented on GitHub (May 26, 2025): Do you still have this issue using the latest firmware? I am able to use the absolute mouse as well as the relative mouse just fine on my Android (which is a Samsung Galaxy S22+ with Android 15 UI 7). FYI - I am using a bluetooth mouse (Logitech MX Master 3) attached to this phone to do this testing.

deekerman commented

2026-02-20 08:20:55 -05:00

Author

Owner

@DyonR commented on GitHub (May 26, 2025):

@rmschooley Using app 0.4.1 and system 0.2.4, absolute mouse is still not working for me on Android devices.
Keyboard and display are working fine. Relative mouse position does work (but it's inaccure since it's relative)

From your message I understand that you have a Bluetooth mouse connected to the device, and that that works. That 'bypasses' the issue, since JetKVM isn't involved, but that naturally isn't a solution when wanting to control a device from another location.

Issue still persists, tested on:
Google Pixel 9 Pro, Android 15, based on LineageOS 22
Samsung Galaxy S20 FE, Android 13, One UI 5.1
LG V30, Android 9

@DyonR commented on GitHub (May 26, 2025): @rmschooley Using app 0.4.1 and system 0.2.4, absolute mouse is still not working for me on Android devices. Keyboard and display are working fine. Relative mouse position does work (but it's inaccure since it's relative) From your message I understand that you have a Bluetooth mouse connected to the device, and that that works. That 'bypasses' the issue, since JetKVM isn't involved, but that naturally isn't a solution when wanting to control a device from another location. Issue still persists, tested on: Google Pixel 9 Pro, Android 15, based on LineageOS 22 Samsung Galaxy S20 FE, Android 13, One UI 5.1 LG V30, Android 9

deekerman commented

2026-02-20 08:20:55 -05:00

Author

Owner

@johnheusinger commented on GitHub (Jun 7, 2025):

Similar issue here with a Google Pixel 8, also using app 0.4.1 and system 0.2.4.

Enabling absolute mouse mode results in erratic behavior with no ability to control the device, eventually crashing the phone and causing a reboot. When relative mode is enabled, the device does not respond to any movements or clicks.

When a mouse is connected directly to the phone, it works as it should.

@johnheusinger commented on GitHub (Jun 7, 2025): Similar issue here with a Google Pixel 8, also using app 0.4.1 and system 0.2.4. Enabling absolute mouse mode results in erratic behavior with no ability to control the device, eventually crashing the phone and causing a reboot. When relative mode is enabled, the device does not respond to any movements or clicks. When a mouse is connected directly to the phone, it works as it should.

deekerman commented

2026-02-20 08:20:55 -05:00

Author

Owner

@qm3ster commented on GitHub (Nov 3, 2025):

On Samsung Fold1 and Fold6, relative works properly (although the browser doesn't capture my mouse which is annoying but probably unrelated), while absolute produces no interactions with the phones.
This is both on screen mirroring and inside DeX.
I tried my shipped
System: 0.2.4
App: 0.3.9
then updated to
System: 0.2.5
App: 0.4.8
To make sure absolute positioning devices work in general I tried a Wacom tablet, and that does. The phone knows it's a pressure-sensitive drawing/writing thingy tho, uses a circle cursor etc. Completely different hover behavior from mouse.

@qm3ster commented on GitHub (Nov 3, 2025): On Samsung Fold1 and Fold6, relative works properly (although the browser doesn't capture my mouse which is annoying but probably unrelated), while absolute produces no interactions with the phones. This is both on screen mirroring and inside DeX. I tried my shipped System: 0.2.4 App: 0.3.9 then updated to System: 0.2.5 App: 0.4.8 To make sure absolute positioning devices work in general I tried a Wacom tablet, and that does. The phone knows it's a pressure-sensitive drawing/writing thingy tho, uses a circle cursor etc. Completely different hover behavior from mouse.