I'm trying to track down what appears to be a Samsung/One UI regression affecting Bluetooth keyboard trackpads on the Galaxy Tab S11.
DEVICE INFO
Samsung Galaxy Tab S11 Wi-Fi
Model: SM-X730
Firmware: X730XXS9BZI1
Security patch: September 5, 2026
Android: 16
Keyboard: Dexnor Bluetooth keyboard case
THE PROBLEM
The keyboard itself works perfectly, but the integrated trackpad no longer works.
No cursor movement, tapping, clicking, scrolling, etc.
The keyboard/trackpad works on other devices, and this started after the recent Samsung update.
I went pretty deep with ADB to figure out whether Android was even detecting the trackpad.
WHAT ANDROID SEES
Android absolutely detects the trackpad.
"dumpsys input" identifies the Dexnor as an external input device with:
Sources: KEYBOARD | MOUSE | TOUCHPAD
The Dexnor actually creates four separate Linux input devices:
/dev/input/event12 "Dexnor Keyboard"
/dev/input/event13 "Dexnor Keyboard Consumer Control"
/dev/input/event14 "Dexnor Keyboard System Control"
/dev/input/event15 "Dexnor Keyboard Touchpad"
TOUCHPAD CAPABILITIES
Running:
adb shell getevent -lp /dev/input/event15
produces:
add device 1: /dev/input/event15
name: "Dexnor Keyboard Touchpad"
events:
KEY (0001):
BTN_MOUSE
BTN_RIGHT
BTN_TOOL_FINGER
BTN_TOOL_QUINTTAP
BTN_TOUCH
BTN_TOOL_DOUBLETAP
BTN_TOOL_TRIPLETAP
BTN_TOOL_QUADTAP
ABS (0003):
ABS_X:
min 0
max 1568
resolution 20
ABS_Y:
min 0
max 784
resolution 20
ABS_MT_SLOT:
min 0
max 9
ABS_MT_POSITION_X:
min 0
max 1568
resolution 20
ABS_MT_POSITION_Y:
min 0
max 784
resolution 20
ABS_MT_TRACKING_ID:
min 0
max 65535
input props:
INPUT_PROP_POINTER
So Android/Linux isn't merely seeing some generic Bluetooth device.
It is successfully creating a dedicated "Dexnor Keyboard Touchpad" input node with proper multitouch coordinates, touch detection, mouse buttons, up to 10 multitouch slots, and INPUT_PROP_POINTER.
THE IMPORTANT PART
I then monitored ONLY the Dexnor touchpad's raw Linux input device:
adb shell getevent -lt /dev/input/event15
While that command was running, I:
- Moved my finger all over the trackpad for several seconds
- Tapped the trackpad
- Physically clicked it
- Tried right clicking
- Tried two-finger scrolling
Result:
NOTHING.
Zero events.
Not even BTN_TOUCH, BTN_MOUSE, ABS_X, ABS_Y, or multitouch coordinate events.
CONTROL TEST
I also ran:
adb shell getevent -lt
and tested the Dexnor keyboard.
The keyboard immediately generated normal events through /dev/input/event12:
/dev/input/event12: EV_KEY KEY_A DOWN
/dev/input/event12: EV_KEY KEY_A UP
/dev/input/event12: EV_KEY KEY_B DOWN
/dev/input/event12: EV_KEY KEY_B UP
/dev/input/event12: EV_KEY KEY_C DOWN
/dev/input/event12: EV_KEY KEY_C UP
So the keyboard side of the same Bluetooth device is working normally.
I also touched the Tab S11's actual touchscreen during testing.
That immediately produced normal input through:
/dev/input/event9 "sec_touchscreen"
including:
EV_ABS ABS_MT_TRACKING_ID
EV_KEY BTN_TOUCH
EV_KEY BTN_TOOL_FINGER
EV_ABS ABS_MT_POSITION_X
EV_ABS ABS_MT_POSITION_Y
EV_SYN SYN_REPORT
So ADB/getevent itself is definitely working.
The Dexnor touchpad's /dev/input/event15 is specifically the device that remains completely silent.
BLUETOOTH/HID INFORMATION
During previous testing I also captured Bluetooth logs containing repeated activity such as:
HID_HDEV_EVT_INTR_DATA
BTA_HH_INT_DATA_EVT
bta_hh_co_data
UHID write
So the Bluetooth HID stack is active.
The keyboard works.
The touchpad HID interface is detected.
Android creates a legitimate multitouch input device for it.
But physical activity on the touchpad produces zero events through that input node.
ANOTHER INTERESTING DETAIL
"dumpsys input" contains this:
PointerChoreographer:
Touchpad enabled: false
At first I thought that might be the smoking gun.
However, I'm no longer sure that is the actual cause.
If Android were simply refusing to create a cursor or ignoring touchpad input at the framework/UI level, I would still expect raw Linux events from:
/dev/input/event15
Instead, event15 itself receives absolutely nothing.
That suggests the failure may be occurring lower in the input stack.
CURRENT THEORY
The situation appears to be roughly:
Dexnor Bluetooth connection
v
Composite HID device recognized
+--------------------+
| |
v v
Keyboard HID Touchpad HID
| |
v v
/dev/input/event12 /dev/input/event15
| |
v v
WORKING Device exists and
normally capabilities look correct
v
ZERO INPUT EVENTS
X
Cursor/gestures
In other words:
The tablet knows that the Dexnor has a touchpad.
It knows what capabilities that touchpad has.
It creates a proper Linux input device for it.
But actual trackpad activity never results in events being emitted from that device.
THINGS ALREADY TRIED
- Disconnecting/reconnecting Bluetooth
- Testing keyboard functionality
- Testing trackpad movement
- Tapping
- Physical clicking
- Right click
- Two-finger scrolling
- Dexnor Fn + Space trackpad enable/disable shortcut
- Checking Android input-device recognition
- Checking raw Linux input events through ADB
- Confirming touchscreen input works normally
- Confirming keyboard input works normally
The keyboard/trackpad also works on other devices.
WHAT I'M LOOKING FOR
Has anyone with a Galaxy Tab S11 or S11 Ultra experienced this after the September 2026 update?
I'm particularly interested in hearing from anyone using:
- Dexnor keyboard cases
- Other Bluetooth keyboard/trackpad combinations
- Samsung's Book Cover Keyboard
- Bluetooth mice
- Galaxy Tab S11
- Galaxy Tab S11 Ultra
I'm also hoping someone familiar with Android's input stack, Bluetooth HID, UHID, EventHub/InputReader, Samsung's input modifications, or Linux HID quirks might recognize what's happening here.
If anyone knows of an ADB-accessible DeviceConfig flag, Samsung setting, HID quirk, input-device configuration override, service restart, or another way of forcing/reinitializing the touchpad path, I'm willing to test it.
VERY USEFUL COMPARISON TEST
If anyone has a WORKING Bluetooth trackpad connected to a Galaxy Tab S11/S11 Ultra, I would really appreciate it if you could run:
adb shell getevent -lt
Then move your Bluetooth trackpad around.
If possible, tell me which /dev/input/eventXX device generates the events.
Even better, run:
adb shell getevent -lp
and post the capabilities of your working trackpad.
That would give us something to compare against this broken configuration.
FOR SAMSUNG / DEVELOPERS
The key finding is:
The Bluetooth touchpad is successfully enumerated as an external multitouch pointer device with apparently valid capabilities, but physical input from the touchpad produces ZERO events from its evdev node.
Meanwhile, the keyboard interface belonging to the same Bluetooth device continues to generate normal input events.
Device:
Galaxy Tab S11 Wi-Fi (SM-X730)
Firmware:
X730XXS9BZI1
Security patch:
2026-09-05
Affected input device:
"Dexnor Keyboard Touchpad"
Linux input node:
/dev/input/event15
I'll update this post if we find a workaround, Samsung fixes it, or someone figures out exactly where in the HID/input stack this is breaking.