Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request]: DialPad Zenbook Pro UX6404 #223

Open
zeroz41 opened this issue Nov 27, 2024 · 17 comments
Open

[Feature request]: DialPad Zenbook Pro UX6404 #223

zeroz41 opened this issue Nov 27, 2024 · 17 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@zeroz41
Copy link

zeroz41 commented Nov 27, 2024

Describe the bug

No backlight display lighting up numbers for Asus Dialpad.
No errors noticed in logs so far, installation passed. Rebooted machine.
Sorry didn't find an exact previous issue match and thought this could be appropriate.

What works:

  • Enabling numpad by long press top right of pad
  • Calculator Gesture opens my default Calc App
  • Pressing parts of the touchpad does seem to correspond with keys that "Should" be appears with backlight. (was able to 'type' into KCalc Application)
  • CIRCLE LED indicating dialpad is enabled DOES light up(on top left of pad) when numberpad is enabled.

What doesn't work:
No numberpad shows up when enabled. No light at all besides previously mentioned circle enablement LED.

btw same behavior whether or not external keyboard plugged it. Also no difference if enableing/disabling manually without systemd service.

Expected behavior

  1. Reboot machine
  2. Sysd user service active and no errors
  3. I enable the numberpad by press holding top right of touchpad.
  4. An enablement circle appears on top left of touchpad.
  5. An inluminated set of numbers appears on my Asus laptops touch pad.
  6. I can visually identify the numbers to type them into something.

Relevant log output

no error.log exists or is populated in /var/log/asus-numberpad-driver/

bash install log:

cat /var/log/asus-numberpad-driver/install-27-11-2024-14-33-48.log 
warning: ibus-1.5.31-1 is up to date -- skipping
warning: libevdev-1.13.3-1 is up to date -- skipping
warning: curl-8.11.0-3 is up to date -- skipping
warning: xorg-xinput-1.6.4-2 is up to date -- skipping
warning: i2c-tools-4.4-1 is up to date -- skipping
warning: python-3.12.7-1 is up to date -- skipping
warning: python-virtualenv-20.27.1-2 is up to date -- skipping
warning: libxml2-2.13.4-1 is up to date -- skipping
warning: libxkbcommon-1.7.0-2 is up to date -- skipping
warning: gcc-14.2.1+r134+gab884fffe3fc-1 is up to date -- skipping
 there is nothing to do

groupadd: group 'input' already exists
groupadd: group 'i2c' already exists
groupadd: group 'uinput' already exists
Added groups input, i2c, uinput, numberpad to current user
uinput module loaded
i2c-dev module loaded
uinput module added to auto loaded modules
Udev rules reloaded and triggered

Testing interface i2c-4: failed
Testing interface i2c-5: success (adr 0x15)
The detection was successful. Touchpad with NumberPad found: i2c-5

In system remains config file from previous installation. Do you want replace that config with default config? [y/N]
created virtual environment CPython3.12.7.final.0-64 in 183ms
  creator CPython3Posix(dest=/usr/share/asus-numberpad-driver/.env, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, app_data_dir=/home/tj/.local/share/virtualenv)
    added seed packages: cffi==1.17.1, libevdev==0.11, numpy==2.1.3, pip==24.3.1, pyasyncore==1.0.4, pycparser==2.22, pyinotify==0.9.6, python_xlib==0.33, pywayland==0.4.18, setuptools==75.6.0, six==1.16.0, smbus2==0.5.0, systemd_python==235, xkbcommon==1.0.1
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
Requirement already satisfied: pip in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (24.3.1)
Requirement already satisfied: setuptools in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (75.6.0)
Requirement already satisfied: libevdev in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 1)) (0.11)
Requirement already satisfied: numpy in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 2)) (2.1.3)
Requirement already satisfied: pyinotify in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 3)) (0.9.6)
Requirement already satisfied: python-xlib in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 4)) (0.33)
Requirement already satisfied: smbus2 in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 5)) (0.5.0)
Requirement already satisfied: pyasyncore in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 6)) (1.0.4)
Requirement already satisfied: pywayland in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 7)) (0.4.18)
Requirement already satisfied: xkbcommon<1.1 in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 8)) (1.0.1)
Requirement already satisfied: systemd-python in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from -r requirements.txt (line 9)) (235)
Requirement already satisfied: six>=1.10.0 in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from python-xlib->-r requirements.txt (line 4)) (1.16.0)
Requirement already satisfied: cffi>=1.12.0 in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from pywayland->-r requirements.txt (line 7)) (1.17.1)
Requirement already satisfied: pycparser in /usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages (from cffi>=1.12.0->pywayland->-r requirements.txt (line 7)) (2.22)


NumberPad layout

The automatically recommended NumberPad layout for this laptop (Zenbook UX6404VI_UX6404VI) is b7402. Do you want to use the b7402 layout? (The photo of the recommended NumberPad layout can be found here https://github.com/asus-linux-drivers/asus-numberpad-driver#b7402) [y/N]
Selected key layout: b7402

Systemctl service

Do you want install systemctl service? [y/N]
LAYOUT_NAME: b7402
CONFIG_FILE_DIR_PATH: /usr/share/asus-numberpad-driver

env var DISPLAY: :1
env var WAYLAND_DISPLAY: wayland-0
env var AUTHORITY: /run/user/1000/xauth_oNylca
env var XDG_RUNTIME_DIR: /run/user/1000
env var DBUS_SESSION_BUS_ADDRESS: unix:path=/run/user/1000/bus
env var XDG_SESSION_TYPE: wayland

ERROR LOG FILE: /var/log/asus-numberpad-driver/error.log

Unfortunatelly you will not be able use feature: Disabling Touchpad (e.g. Fn+special key) disables NumberPad aswell, at this moment is supported only X11
Asus numberpad driver service placed
Systemctl daemon reloaded
Asus numberpad driver service enabled
Asus numberpad driver service started

External keyboard

This is a predefined rule for changing the configuration when an external keyboard is connected/disconnected.

The application of this rule results in the following changes if an external keyboard is connected:

 - Numlock key does not activate NumberPad (config value is set to sys_numlock_enables_numpad=0)
 - Numberpad disactivation does not disable Numlock (config value is set to numpad_disables_sys_numlock=0)

In summary when an external keyboard is connected then NumberPad activation is not linked to Numlock state and vice versa.

Do you want install the rule for external keyboard? [y/N]
Rule 90-numberpad-external-keyboard.rules applied
Udev rules reloaded and triggered

Calculator app

Do you want try to install toggling script for XF86Calculator key? [y/N]
No such schema “org.gnome.settings-daemon.plugins.media-keys”
Not detected any supported calculator (gnome-calculator && io.elementary.calculator)

Power supply saver

By default is idle functionality disabled and may be manually enabled in config file later. Or by installing this rule can be enabled by every detected change of power supply mode to battery mode.

Idle mode is configured to be enabled after 10s of inactivity and to decrease 30% of brightness.

Do you want install the rule for idle functionality? [y/N]
Rule 80-numberpad-power-supply applied
Udev rules reloaded and triggered

Installation finished succesfully

Reboot is required. Do you want reboot now? [y/N]

----------------------------------

journalctl -f --user-unit [email protected]
Nov 27 14:48:26 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
Nov 27 14:48:29 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Touched top_right_icon area (numlock) in time: 1732736909.6998165
Nov 27 14:48:29 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Un-touched top_right_icon area (representing numlock key) in time: 1732736909.857179
Nov 27 14:48:29 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Touched top_right_icon area (numlock) in time: 1732736909.9816911
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Slide from top_right_icon exceeded the activation threshold for x and y.
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Activation radius 1200.00 (top left corner is 0)
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: System numlock activated
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Numpad activated
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Setting up for config file key: "enabled" with value: "True"
Nov 27 14:48:32 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
Nov 27 14:52:08 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Touched top_right_icon area (numlock) in time: 1732737128.5149653
Nov 27 14:52:09 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Un-touched top_right_icon area (representing numlock key) in time: 1732737129.4895928
Nov 27 14:52:13 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Touched top_left_icon area in time: 1732737133.6677315
7Nov 27 14:52:14 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:14 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_7:8
Nov 27 14:52:14 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:14 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_7:8
45Nov 27 14:52:15 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:15 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_4:5
Nov 27 14:52:15 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:15 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_4:5
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
5Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
58Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
4Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_5:6
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_8:9
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:16 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_8:9
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_4:5
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_4:5
1Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Pressed numpad key
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_1:2
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: Unpressed numpad key
Nov 27 14:52:17 lappy /usr/share/asus-numberpad-driver/numberpad.py[1569]: KEY_1:2
^C
-----------------------------------
sudo i2cdetect -l
i2c-0   i2c             NVIDIA i2c adapter 1 at 1:00.0          I2C adapter
i2c-1   i2c             NVIDIA i2c adapter 3 at 1:00.0          I2C adapter
i2c-2   i2c             NVIDIA i2c adapter 5 at 1:00.0          I2C adapter
i2c-3   i2c             NVIDIA i2c adapter 6 at 1:00.0          I2C adapter
i2c-4   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-5   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-6   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-7   smbus           SMBus I801 adapter at efa0              SMBus adapter
i2c-8   i2c             i915 gmbus dpa                          I2C adapter
i2c-9   i2c             i915 gmbus dpb                          I2C adapter
i2c-10  i2c             i915 gmbus dpc                          I2C adapter
i2c-11  i2c             i915 gmbus tc1                          I2C adapter
i2c-12  i2c             i915 gmbus tc2                          I2C adapter
i2c-13  i2c             i915 gmbus tc3                          I2C adapter
i2c-14  i2c             i915 gmbus tc4                          I2C adapter
i2c-15  i2c             i915 gmbus tc5                          I2C adapter
i2c-16  i2c             i915 gmbus tc6                          I2C adapter
i2c-17  i2c             AUX A/DDI A/PHY A                       I2C adapter
i2c-18  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-19  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter

------------------------
bash install_device_check.sh
Testing interface i2c-4: failed
Testing interface i2c-5: success (adr 0x15)
The detection was successful. Touchpad with NumberPad found: i2c-5

Desktop

  • Program version: Release 6.4.0
  • Distro: EndeavorOS
  • Kernel: 6.11.6-arch1-1
@zeroz41 zeroz41 added the bug Something isn't working label Nov 27, 2024
@zeroz41
Copy link
Author

zeroz41 commented Nov 27, 2024

potentially worth mentioning too, i installed on KDE wayland. If switching to X11 service fails. But i'm not worried about that for now, and is not the issue ;)

@ldrahnik
Copy link
Member

ldrahnik commented Nov 27, 2024

@zeroz41 Hm. I would try reboot after installation + switch to Windows in case you have dual boot whether it works there / enable, disable there and back.

And try manually send activation i2c commands to each i2c with 0x15 address. Maybe first one found was not NumberPad.

Also, post here dsdt table please:

$ sudo apt-get install iasl
$ cd <work-dir>
$ sudo cp /sys/firmware/acpi/tables/DSDT DSDT
$ sudo iasl -d DSDT
$ sudo gedit DSDT.dsl

@zeroz41
Copy link
Author

zeroz41 commented Nov 27, 2024

Hello thanks for response. With the driver active:
i2ctransfer -f -y 5 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 $<0x01> 0xad turns on the "circle" led as expected and 0x00 turns it off.
i2clist:
i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-6 i2c Synopsys DesignWare I2C adapter I2C adapter

Tried messing with 4 and 6 but they seemed to not be active not accept read write.
heres full list.
[tj@lappy asus-numberpad-driver-6.4.0]$ i2cdetect -l
i2c-0 i2c NVIDIA i2c adapter 1 at 1:00.0 I2C adapter
i2c-1 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
i2c-2 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
i2c-3 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter
i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-6 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-7 smbus SMBus I801 adapter at efa0 SMBus adapter
i2c-8 i2c i915 gmbus dpa I2C adapter
i2c-9 i2c i915 gmbus dpb I2C adapter
i2c-10 i2c i915 gmbus dpc I2C adapter
i2c-11 i2c i915 gmbus tc1 I2C adapter
i2c-12 i2c i915 gmbus tc2 I2C adapter
i2c-13 i2c i915 gmbus tc3 I2C adapter
i2c-14 i2c i915 gmbus tc4 I2C adapter
i2c-15 i2c i915 gmbus tc5 I2C adapter
i2c-16 i2c i915 gmbus tc6 I2C adapter
i2c-17 i2c AUX A/DDI A/PHY A I2C adapter
i2c-18 i2c AUX USBC1/DDI TC1/PHY TC1 I2C adapter
i2c-19 i2c AUX USBC2/DDI TC2/PHY TC2 I2C adapter

I tried i2c 0x15 for 456, where 5 is the only one that accepted the command.
maybe there is a second activation i need to find on device 5? I'm not sure.

Here's dsdt.dsl. its quite large.

DSDT.dsl.txt

@ldrahnik
Copy link
Member

ldrahnik commented Nov 27, 2024

@zeroz41 Second activation is 60,61 (more in Readme) but it is implemented in the driver.

@ldrahnik
Copy link
Member

ldrahnik commented Nov 27, 2024

@zeroz41 What is the output of $ cat /proc/bus/input/devices. Should be there probably one device for Dialpad and second one for NumberPad.

@ldrahnik
Copy link
Member

potentially worth mentioning too, i installed on KDE wayland. If switching to X11 service fails. But i'm not worried about that for now, and is not the issue ;)

@zeroz41 Unfortunatelly you have to reinstall driver each switch in case you use systemd service.

@ldrahnik
Copy link
Member

@zeroz41 Ah, not NumberPad, dialpad doesn't work. Yeah, it will be necessary to listen communication on Windows. Do you have Windows? I am open to instruct you how.

@zeroz41
Copy link
Author

zeroz41 commented Nov 27, 2024

@ldrahnik roger on reinstall for swithing x11, no big deal. Also i do not have a windows partition.
Here's the devices cat. :)
cat_devices.txt

@ldrahnik
Copy link
Member

@zeroz41 On Linux try click on Dialpad while you run these commands: sudo evtest or sudo libinput debug-events

@zeroz41
Copy link
Author

zeroz41 commented Nov 28, 2024

sure thing. Gere is some output from libinput debug-events.
Can see the mapped dialpad presses on the left of some event12s

sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event23 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event18 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event0 DEVICE_ADDED Lid Switch seat0 default group3 cap:S
-event1 DEVICE_ADDED Power Button seat0 default group4 cap:k
-event22 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k
-event25 DEVICE_ADDED BY Tech Gaming Keyboard System Control seat0 default group5 cap:k
-event26 DEVICE_ADDED BY Tech Gaming Keyboard Consumer Control seat0 default group5 cap:kp scroll-nat
-event27 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k
-event28 DEVICE_ADDED BY Tech Gaming Keyboard Mouse seat0 default group5 cap:p left scroll-nat scroll-button
-event15 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse seat0 default group6 cap:p left scroll-nat scroll-button
-event16 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse Keyboard seat0 default group6 cap:kp scroll-nat
-event19 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse Keyboard seat0 default group6 cap:k
-event3 DEVICE_ADDED ELAN9008:00 04F3:4116 seat0 default group7 cap:t size 300x188mm ntouches 10 calib
-event6 DEVICE_ADDED ELAN9008:00 04F3:4116 Stylus seat0 default group7 cap:T size 310x194mm left calib
-event11 DEVICE_ADDED ASUE1A03:00 04F3:32A0 Mouse seat0 default group8 cap:p left scroll-nat scroll-button
-event12 DEVICE_ADDED ASUE1A03:00 04F3:32A0 Touchpad seat0 default group8 cap:pg size 129x80mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on dwtp-on
-event14 DEVICE_ADDED Asus WMI hotkeys seat0 default group9 cap:k
-event10 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group10 cap:k
-event257 DEVICE_ADDED ASUE1A03:00 04F3:32A0 NumberPad seat0 default group11 cap:kp left scroll-nat
-event12 POINTER_MOTION +0.038s -0.29/ 0.00 ( -2.00/ +0.00)
event12 GESTURE_HOLD_BEGIN +0.040s 1
event12 GESTURE_HOLD_END +0.051s 1
-event257 KEYBOARD_KEY +0.055s *** (-1) pressed
event257 KEYBOARD_KEY +0.055s *** (-1) released
2-event12 POINTER_MOTION +1.189s 0.00/ -0.46 ( +0.00/ -2.00)
event12 POINTER_MOTION +1.196s 0.00/ -0.28 ( +0.00/ -1.00)
event12 POINTER_MOTION +1.203s 0.32/ -0.32 ( +1.00/ -1.00)
event12 POINTER_MOTION +1.210s -0.32/ 0.00 ( -1.00/ +0.00)
event12 GESTURE_HOLD_BEGIN +1.214s 1
event12 GESTURE_HOLD_END +1.229s 1
-event257 KEYBOARD_KEY +1.232s *** (-1) pressed
event257 KEYBOARD_KEY +1.233s *** (-1) released
--event12 POINTER_MOTION +4.798s 0.28/ -0.28 ( +1.00/ -1.00)
event12 POINTER_MOTION +4.805s 0.32/ -0.32 ( +1.00/ -1.00)
event12 POINTER_MOTION +4.819s 0.28/ 0.00 ( +1.00/ +0.00)
event12 POINTER_MOTION +4.827s 0.24/ 0.00 ( +1.00/ +0.00)
event12 GESTURE_HOLD_BEGIN +4.828s 1
event12 GESTURE_HOLD_END +4.840s 1
-event257 KEYBOARD_KEY +4.843s *** (-1) pressed
event257 KEYBOARD_KEY +4.844s *** (-1) released
/-event12 POINTER_MOTION +6.451s 0.00/ -0.62 ( +0.00/ -2.00)
event12 POINTER_MOTION +6.458s 0.00/ -0.68 ( +0.00/ -2.00)
event12 POINTER_MOTION +6.465s -0.34/ -0.34 ( -1.00/ -1.00)
event12 POINTER_MOTION +6.472s -0.34/ -0.34 ( -1.00/ -1.00)
event12 POINTER_MOTION +6.479s -0.34/ -0.34 ( -1.00/ -1.00)
event12 GESTURE_HOLD_BEGIN +6.481s 1
event12 POINTER_MOTION +6.486s -0.68/ -0.34 ( -2.00/ -1.00)
event12 GESTURE_HOLD_END +6.500s 1
-event257 KEYBOARD_KEY +6.503s *** (-1) pressed
event257 KEYBOARD_KEY +6.504s *** (-1) released
9-event12 POINTER_MOTION +8.181s 2.04/ -0.68 ( +6.00/ -2.00)
event12 POINTER_MOTION +8.188s 1.70/ -0.68 ( +5.00/ -2.00)
event12 POINTER_MOTION +8.195s 1.70/ -1.36 ( +5.00/ -4.00)
-event257 KEYBOARD_KEY +8.208s *** (-1) pressed
event257 KEYBOARD_KEY +8.208s *** (-1) released
3-event12 POINTER_MOTION +9.448s 0.68/ -1.36 ( +2.00/ -4.00)
-event257 KEYBOARD_KEY +9.463s *** (-1) pressed
event257 KEYBOARD_KEY +9.463s *** (-1) released
8-event12 POINTER_MOTION +10.529s 0.68/ -1.70 ( +2.00/ -5.00)
event12 POINTER_MOTION +10.537s 1.02/ -2.38 ( +3.00/ -7.00)
-event257 KEYBOARD_KEY +10.551s *** (-1) pressed
event257 KEYBOARD_KEY +10.551s *** (-1) released
6-event12 POINTER_MOTION +17.688s 0.00/ 0.31 ( +0.00/ +1.00)
event12 POINTER_MOTION +17.695s 0.00/ 0.93 ( +0.00/ +3.00)
event12 GESTURE_HOLD_BEGIN +17.704s 1
event12 GESTURE_HOLD_END +17.715s 1
-event257 KEYBOARD_KEY +17.716s *** (-1) pressed
event257 KEYBOARD_KEY +17.717s *** (-1) released
9-event12 POINTER_MOTION +18.494s -0.67/ -0.33 ( -2.00/ -1.00)
event12 POINTER_MOTION +18.501s -0.67/ -0.33 ( -2.00/ -1.00)
event12 POINTER_MOTION +18.509s -0.68/ -0.34 ( -2.00/ -1.00)
event12 POINTER_MOTION +18.516s -1.02/ 0.00 ( -3.00/ +0.00)
event12 GESTURE_HOLD_BEGIN +18.520s 1

@ldrahnik
Copy link
Member

@zeroz41 So these events are send from Touchpad device but are associated to DialPad? Try sudo evemu-record /dev/input/event<xyz touchpad device event id> and try describe what you are doing on DialPad / simple should be for example figure out scan code for middle button inside Dialpad in case it is button and can be pressed.

@zeroz41
Copy link
Author

zeroz41 commented Nov 28, 2024

@ldrahnik It seems I was misled and mistaken about the model I own and it only features ASUS dialpad. I wanted to scour the internet and youtube videos to confirm. I thought it featured both numberpad and dialpad when purchased.
My apologies for the time sunk but regardless thanks for the support.
We did at least learn that the same numpad activations also enable disable dialpad led, and gesture support works the same.
So non issue, we can close.

@ldrahnik
Copy link
Member

ldrahnik commented Nov 28, 2024

@zeroz41 This NumberPad driver adds NumberPad functionality with no hardware support except backlight leds. So Dialpad works out of the box? I am open to create new repository fór Dialpad driver if it does make sense.

@zeroz41
Copy link
Author

zeroz41 commented Nov 28, 2024

I will check functionality of dialpad without your driver installed soon.
. MY uncertainty from watching youtube videos was still is if my model/other dialpads even have the full backlight led or just the led that lights up the circle shown here. I haven't confirmed 100%
image

To be honest if you were to create a dialpad driver it looks like much of your numberpad code pretty much just works the same for the gestures and activation. Everything functioned for numpad as expected expect the numberpad actually being visible lol.

From what i've looked at the dialpad basically acts as a rotary knob upon activation around the circle, which the gestures being clockwise or counter clockwise around the circle to use. While much more advanced on windows, i'd imagine some base functionality of hooking into volume controls or brightness.

Found this btw. https://github.com/fredaime/openwheel
But appears to be related to physical Asus Dials, which differ from dialpads.

@ldrahnik
Copy link
Member

ldrahnik commented Dec 1, 2024

@zeroz41 Ok, exist two variants DialPad and Asus Dials and you have DialPad thwt layes on touchpad. So basically associate shortcuts for currently opened app (somehow) with default shortcuts when is not opened any app would be ok? Of course only when is DialPad activated via top right corner. What about possivility to divide circle by half or to quaters? For configirable buttons in config? Top, left, bottkm, right virtual button I mean spot with specific default functiobality and specific functiobality for each app. Maybe for someone better option then knob? Have to this variant konfogurable for each state (default or specific app state). How it looks like when Is light up? Does work entire Touchpad?Is there defined grid like NumberPad has? Is not because intended usage is knob? Because I saw buttons in some official video in some Adobe produkt. So dividing by other number than backlighted grid has would be confusing?

@ldrahnik ldrahnik added question Further information is requested and removed bug Something isn't working labels Dec 1, 2024
@ldrahnik ldrahnik changed the title [Bug]: Another backlight not turning on. Zenbook pro ux6404. Numpad/dialpad won't display. [Feature request]: DialPad Zenbook Pro UX6404 Dec 1, 2024
@ldrahnik ldrahnik added the enhancement New feature or request label Dec 1, 2024
@ldrahnik
Copy link
Member

ldrahnik commented Dec 1, 2024

@zeroz41 I have created repository https://github.com/asus-linux-drivers/asus-dialpad-driver but I will not start until the idea is clear.

@zeroz41
Copy link
Author

zeroz41 commented Dec 1, 2024

Nice! @ldrahnik . I wouldn't want to answer incorrectly as I've not experienced actual usage of asus dialpad on Windows. So makes sense not to start anything now until things are more clear!

And yes seems there is a more physical ASUS DIAL and a touchpad based one ASUS DIALPAD.
Some other questions is "for dialPAD" is is the actual diapad always in the same relative coordinate accross models? If so then your idea of relative touchpad dimension division could be practicle. Or defined grid as mentioned.
Or is there some special detection by hardware when fingers are placed 'near the dial' vs not near dial, while dialpad is "active".
From what i've seen the gesture activation to turn on for DIALPAD appear to be same as ASUS numberpad.

If i get a windows iso and some time I'd be willing to test some things down the line. Currently have limited capped bandwidth related to where i am.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants