hello, when i run the command i've:

i2c-3 i2c i915 gmbus dpb I2C adapter i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-6 i2c i915 gmbus dpd I2C adapter i2c-4 i2c i915 gmbus dpc I2C adapter i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-0 smbus SMBus I801 adapter at efa0 SMBus adapter i2c-7 i2c AUX A/port A I2C adapter i2c-5 i2c i915 gmbus misc I2C adapter

I would like to know what to choose and where exactly to change the name in the .py?

And then the command that could work with the new name and number?

I just bought this laptop and I removed windows but everything works except the num pad (touch pad work)

Thank you for your work and your time.

Hi, I have the laptop mentioned in the title. It has the exact same touchpad layout and seems to support a numpad within the touchpad (in Windows). Would it be possible to add support for this laptop in your code? I tested with the existing code on Arch, but I can not get this to work reliably in its current form. Attached the output showing the devices. Thanks.

Hendrik-Jan

Hi!

I've an issue with asus ux393e.

Your script is works correctly on my mashine, but touchpad backlight is not working. Do you have some ideas how to fix it?

Event though the shortcut is under the F8 key, it should activate on Fn+F8, and not on F8. On devices that have the Fn-Lock, if the Lock is active, pressing F8 will not activate the numpad as would be expected.

After install on ASUS ROG STRIX 15 (G532LWS) Ubuntu does not boot to login screen. Can boot only console mode.

/proc/bus/input/devices

I: Bus=0018 Vendor=04f3 Product=315e Version=0100
N: Name="ELAN1405:00 04F3:315E Touchpad"
P: Phys=i2c-ELAN1405:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-3/i2c-ELAN1405:00/0018:04F3:315E.0001/input/input20
U: Uniq=
H: Handlers=mouse2 event17 
B: PROP=1
B: EV=1b
B: KEY=e520 30000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

If necessary, I can provide additional information.

I just installed it on my new UM425UAZ laptop and it mostly works with the only issues being Fn+F8 not enabling the numpad. The top right on the touchpad enables the numpad no issues.

Is their anyway to make the driver load up at start up? I can start the service it manually with "sudo service asus_touchpad_numpad start" But when starting it again the brightness of the touchpad goes back to lv1 instead of where I left it(in my case Lv3)

While the Fn+F8 issue does not bother me, it might be an issue for someone else. Have confirmed the issue mentioned in #52

Is it possible to rebind the "Calculator" key when the numpad is disabled.

When using the numpad in windows, you require a 1second hold of the numpad button to turn the numpad on, this would be nice to have here as well to prevent accidental activation

Thank you.

Hello,

on my UM425IA using m433ia layout, pressing top left corner starts the calculator, whereas pressing the top right corner enters the equals sign, but only when enabling the numpad. Under Windows, one has to hold the top right corner to enable the numpad and swipe out the top left corner to start the calculator, which arguably reduces the chance of accidental activation. Would it be possible to implement similar behaviour for linux?

Hi, i have next laptop

tried all installation options but i have next issue: Numpad not highlighted(it just dark like turned off), but if i press right top corner i can write numbers like numpad is working properly. Can you please direct me where i can find part of code which response for highlight of touch bar? Tried to find by myself but with no result.

new value of mesh for asus ux363ea

xx = [0.232,0.410,0.588,0.768] yy = [0.343,0.553,0.763]

        try:
            # first row
            if y < yy[0] * maxy:
                if x < xx[0] * maxx:
                    value = EV_KEY.KEY_KP7
                elif x < xx[1] * maxx:
                    value = EV_KEY.KEY_KP8
                elif x < xx[2] * maxx:
                    value = EV_KEY.KEY_KP9
                elif x < xx[3] * maxx:
                    value = EV_KEY.KEY_KPSLASH
                else:
                    value = EV_KEY.KEY_BACKSPACE
            # second row
            elif y < yy[1] * maxy:
                if x < xx[0] * maxx:
                    value = EV_KEY.KEY_KP4
                elif x < xx[1] * maxx:
                    value = EV_KEY.KEY_KP5
                elif x < xx[2] * maxx:
                    value = EV_KEY.KEY_KP6
                elif x < xx[3] * maxx:
                    value = EV_KEY.KEY_KPASTERISK
                else:
                    value = EV_KEY.KEY_BACKSPACE
            # third row
            elif y < yy[2] * maxy:
                if x < xx[0] * maxx:
                    value = EV_KEY.KEY_KP1
                elif x < xx[1] * maxx:
                    value = EV_KEY.KEY_KP2
                elif x < xx[2] * maxx:
                    value = EV_KEY.KEY_KP3
                elif x < xx[3] * maxx:
                    value = EV_KEY.KEY_KPMINUS
                else:
                    value = EV_KEY.KEY_5
            # last row
            else :
                if x < xx[0] * maxx:
                    value = EV_KEY.KEY_KP0
                elif x < xx[1] * maxx:
                    value = EV_KEY.KEY_KPDOT
                elif x < xx[2] * maxx:
                    value = EV_KEY.KEY_KPENTER
                elif x < xx[3] * maxx:
                    value = EV_KEY.KEY_KPPLUS
                else:
                    value = EV_KEY.KEY_KPEQUAL

Hi, I don't have the traceback available. But in the code I found something that looked wrong.

In /usr/bin/asus_touchpad_numpad.py there looks to me (and my traceback at computer startup), that x and y could be undefined:

      # During tap #
      if finger == 1:
          finger = 2
          try:
              # first row
              if y < 0.25 * maxy:

if not these have been matched:

        # Get x position #
        if e.matches(EV_ABS.ABS_MT_POSITION_X):
            x = e.value
            continue
        # Get y position #
        if e.matches(EV_ABS.ABS_MT_POSITION_Y):
            y = e.value
            continue

Default values for x and y maybe could help, or an indicator if this has happened.

Also while at it, the try-catch-case this is in looks like it is only used for the last rows, so try could be moved there instead.

The Numpad is working, but the backlight doesn't. I have tried manually enabling it by this command: i2ctransfer -f -y " + device_id + " w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xad with correct "device_id" and it doesn't work.

Also, I have tried @kawaegle script for testing the backlight, and the result is the same with different values.

I think that enabling backlight in the UM425 has another register address, and I need to send some other I2C data. How can I find exactly this I2C sequence?

Hello, I am contacting you because my keyboard is not available. I have the new asus zenbook 14 oled (ux3402z). I would like to know if it is possible to have the keyboard available too? I would like to know if it is possible to get it? Romain

Very minor note,

Line 187 in asus_touchpad.py is written as:

# status 1 = min bright
# status 2 = middle bright
# status 3 = max bright

It should be 0, 1 and 2

I just wanted to report that the numpad on an Asus Zenbook 14 UM425QA is working perfecly with the m433ia.py layout. You may add it to the "tested and working" section in the readme.

A BIG BIG THANK YOU to all contributors for this.

it's annoying so I remove it i guess the original code was great when we touch the brightness button twice without the numlock but on my case (and maybe a lot of user case) the calculator just spawn randomly

Is it possible to change the time needed to press the on/off key? by default the driver switches the keypad on/off as you tap on the calculator logo on the top right side. i would like to press it for 1 second in order to activate it.