voodooi2c / voodooi2c Goto Github PK

I use XPS 13 9343 (i7 - 5500) and Sierra 10.12.6
I install and setup complete and event viewer cognized 3 finger swipe but Two finger movement with thumb rejection and Four finger swipe in up, down, left right directions can't cognize

Hello! First of all I'd like to thank you for your good work.
When I inject the kext from the Terminal the trackpad somehow works, but as I move the pointer, it continue moving forever until I touch again the surface. There's something we can do to correct this bug?

Hi, I've been having a very strange problem.

After reading this thread, #70 I was able to finally get VoodooI2C working in my mojave hackintosh system for the internal trackpad (the touchscreen worked out of the box).

However, my internal trackpad only starts working after I force my laptop to sleep and it wakes.

Here's all my debug files including clover DSDT folder
debug_9170.zip

Just updated from 10.13.5 to 10.13.6, after finish my touchpad elan1200 not work any more. Please help

Works after several time restart and rebuild kext cache.

Hey there, it's nice work,
I want to request if high Sierra will be supported in future?
At the moment we're getting kernel panics on the last beta build.

the next request would be, If it could be possible to bring up new elan touchpad working on macOS?

HID\VEN_ELAN&DEV_0651&Col01
HID\ELAN0651&Col01
HID*ELAN0651&Col01

older ones like this are working correctly.
static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN0000", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0605", 0 },
{ "ELAN1000", 0 },
{ }
};

Device: XiaoMi Pro [i7 8550U]

Hello,thanks for your contribution so that many many ppl can use touchpad, its alomost perfect. But there is a problem that always touch the touchpad by mistake when typing and that touch will make the wrong click event.

Some i2c slave devices will have an XDSM method instead of a _DSM method, we should consider both cases.

Hello I am a Voodooi2c user, thanks in advance for having made it easy for me.

My problem is when my double tap touchpad left click does not work, also when I right click using two fingers right click also does not work. Whether that includes the limitations for my touchpad ELAN1200 or I lack in applying the steps that have been extruded by you.

I have applied patch:

OS CHECK (WINDOWS10)
GPIO CONTROLLER ENABLE

Kext :

Voodooi2c.kext (2.0.2)
Voodooi2cHID.kext

Thank You :)

kernel painc when wake up

location at : file : VoodooI2CPCIController.cpp

line 58

IOReturn VoodooI2CPCIController::setPowerState(unsigned long whichState, IOService* whatDevice) {
if (whatDevice != this)
return kIOPMAckImplied;

if (whichState == kIOPMPowerOff) {
    physical_device->awake = false;

    IOLog("%s::%s Going to sleep\n", getName(), physical_device->name);
} else {
    if (!physical_device->awake) {
        configurePCI();
        skylakeLPSSResetHack();  // this line, when the computer wake up kernel panic on 8250U cpu

        physical_device->awake = false;
        IOLog("%s::%s Woke up\n", getName(), physical_device->name);
    }
}
return kIOPMAckImplied;

}

Hello! I just tested this awesome driver!
I can help you to dump something you need by linux or windows or osx, but wacom emr digitizer in my Galaxy Book 12 seem only to work with point pen, and not with rpessure.
Infact the pen is recognized well and work very well.. But no pressure at all!
Can i help to make this dream possible??

(ps also touch dont work in 10.13 in GB12)

I'm not sure if this is the right place to bring this up. I followed this post on how to use VoodooI2C regain control of my laptop's trackpad. My method and results are here. I am not intricately familiar with the os x kernel, i might be able to help with guidance/input.

Once I got my trackpad to work, it became only somewhat responsive: as if the sensitivity was turned almost all the way down. In addition, whenever I stop or lift my finger off the trackpad the cursor continues to move in the original direction. Only excessive clicking seems to stop the cursor. In effect, the trackpad is still unusable for my current configuration.

Can someone point me in the right direction for getting this fixed?

I noticed that the pre-build binary hasn't been updated for quite some time, so I decided to compile myself and maybe get some ideas about the functionalities, however, I'm facing some problem trying to do so.

at first, it complained about unable to find cldoc, solved by running sudo pip install cldoc
(for future reference)

My laptop has I2C HID Touchpad, with ID ELAN1000. I edited Info.plist inside VoodooI2C.kext with that ID, it success to detect (i see in verbose mode when booting). but after that it cause KP

Could it fixed? if can, what should i do?

here what i found in DSDT
`Scope (_SB.PCI0.I2C1)
{
Device (ETPD)
{
Name (SBFB, ResourceTemplate ()
{
I2cSerialBus (0x004C, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "_SB.PCI0.I2C1",
0x00, ResourceConsumer, _Y34,
)
})
Name (SBFI, ResourceTemplate ()
{
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, )
{
0x0000005F,
}
})
CreateWordField (SBFB, _SB.PCI0.I2C1.ETPD._Y34._ADR, BADR) // _ADR: Address
Name (_ADR, One) // _ADR: Address
Method (_HID, 0, NotSerialized) // _HID: Hardware ID
{
If (ELAN)
{
Store (0x15, BADR)
Return ("ELAN1000")
}

            If (FOLT)
            {
                Store (0x15, BADR)
                Return ("FTE1001")
            }

            Return ("ELAN1000")
        }

        Name (_CID, "PNP0C50")  // _CID: Compatible ID
        Name (_UID, One)  // _UID: Unique ID
        Name (_S0W, 0x03)  // _S0W: S0 Device Wake State
        Method (_S3W, 0, NotSerialized)  // _S3W: S3 Device Wake State
        {
            If (LEqual (S0ID, Zero))
            {
                Return (0x03)
            }
            Else
            {
                Return (Zero)
            }
        }

        Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
        {
            If (LEqual (Arg0, ToUUID ("3cdff6f7-4267-4555-ad05-b30a3d8938de") /* HID I2C Device */))
            {
                If (LEqual (Arg2, Zero))
                {
                    If (LEqual (Arg1, One))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                           
                        })
                    }
                    Else
                    {
                        Return (Buffer (One)
                        {
                             0x00                                           
                        })
                    }
                }

                If (LEqual (Arg2, One))
                {
                    Return (One)
                }
            }
            Else
            {
                Return (Buffer (One)
                {
                     0x00                                           
                })
            }
        }

        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (LEqual (TPIF, Zero))
            {
                Return (Zero)
            }

            If (And (DSYN, One))
            {
                Return (Zero)
            }

            Return (0x0F)
        }

        Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
        {
            Return (ConcatenateResTemplate (SBFB, SBFI))
        }
    }
}`

Non-HID I2C devices exist and do not follow the HID standard, or they can appear to respond to HID but be non-functional as HID (e.g. Elan I2C trackpad on some chromebooks).

The best way to check for this is with ACPI. Non-HID devices do not have a compatible ID of PNP0C50.

Relevant source: https://github.com/alexandred/VoodooI2C/blob/master/VoodooI2C/VoodooI2C.cpp#L447

Hello, my problem is the same as issues/44 After I used another driver MacForceOne/VoodooI2C the mouse no longer drifts. The gestures are perfect (five fingers will cause to restart), how can I fix it? Thank you.

Hi! I'm using a Dell XPS9350 with a synaptics I2C touchpad. However it's also routed through PS/2.
How can I help to bring up the normal use of it via I2C? Bothe the 2 I2C controllers are successfully detected with your kext, since they are on i7-6560U Skylake.
Here is some output from Linux, just in case it might help somehow...

[    4.728185] input: DLL0704:01 06CB:76AE Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-8/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input17
[    4.728264] hid-multitouch 0018:06CB:76AE.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0704:01 06CB:76AE] on i2c-DLL0704:01

@alexandred also you may be interessed by this to bring gesture support, hope this might help even if it's a linux-mac reverse-engeneered path.

When scrolling down (fingers going up) you can stop the momentum/inertia with two finger tap
but when you scroll up (fingers going down), you cannot stop it. The only way to stop the inertia is by doing a counter scrolling gesture in the oposite direction.

edit1 also the same thing happens when scrolling hoizontaly. everything is okey when scrolling to right(finger sliding from right to left), but scrolling to left doesnt stop with two finger tap.

Thanks a lot. It works on my notebook: xiaomi air 12.5 6Y30 skylake, but it very slow.

10.13.5

联想小新潮7000使用的也是i2c触摸板，但是是synaptics的，没法驱动，求尽快更新。
Hello @alexandred ,
My computer is Lenovo Xiaoxin Chao 7000, which use an i2c touch pad. But it's Synaptics i2c touchpad and can't be drived by this kexts. Could you please update the git repo soon to fix this problem? Thanks very much!

Hi, I updated my Hackintosh laptop from 10.13 to 10.13.3 yesterday. While everything seemed flawless, I found my I2C touchpad no longer working. Previously, I installed VoodooI2C 1.0.4 to S/L/E and everything worked fine. So I updated VoodooI2C to 2.0.1 ( also tried 2.0.0) and this caused kernel bug and immediate reboot during booting process. This happens so fast that I cannot take a clear picture of the bug screen. It's a long screen with with many driver names and their versions.

The smart zoom disabled and 2F tap don't work well in V2.0.3

Hello,
First of all thanks to your work.
My problem and I now also for others:
Trackpad ELAN 1200 is fully working but CPU running max 3500ghz.
Unfortunately, I have not found aany solution. Attached the problem report.

bug_report_ASUS_Zenbook_UX330UA.zip

I2C devices' probe functions are returning 0 (false) on success.

Affected Lines:
https://github.com/alexandred/VoodooI2C/blob/master/VoodooI2C/VoodooI2CHIDDevice.cpp#L59
https://github.com/alexandred/VoodooI2C/blob/master/VoodooI2C/VoodooCyapaGen3Device.cpp#L646

This appears to be the cause of freezes when loading/unloading the kext several times.

This driver used to be working for OS X 10.11 on ASUS Zenbook UX501VW, whose touchpad hardware is elan1000 on i2c1, recently I installed 10.12.5 on my computer and found that this driver no longer working on my laptop. It keeps reporting error in the log, here is the log.

kernel: (kernel) VoodooI2C::Found I2C device pci8086,a161
kernel: (kernel) VoodooI2C::pci8086,a161::Failed to read ACPI config
kernel: (kernel) VoodooI2C::pci8086,a161:: Loading hardcoded settings for HSW/BDW/SKL
kernel: (kernel) VoodooI2C::pci8086,a161::Unknown Synopsys component type: 0xffffffff
kernel: (kernel) VoodooI2C::pci8086,a161::Failed to initialise I2C Bus
kernel: (kernel) VoodooI2C::stop
kernel: (kernel) VoodooI2C::Found I2C device pci8086,a160
kernel: (kernel) VoodooI2C::pci8086,a160::Failed to read ACPI config
kernel: (kernel) VoodooI2C::pci8086,a160:: Loading hardcoded settings for HSW/BDW/SKL
kernel: (kernel) VoodooI2C::pci8086,a160::Unknown Synopsys component type: 0xffffffff
kernel: (kernel) VoodooI2C::pci8086,a160::Failed to initialise I2C Bus
kernel: (kernel) VoodooI2C::stop
kernel: (kernel) VoodooI2C::Found I2C device pci8086,a160
kernel: (kernel) VoodooI2C::Found I2C device pci8086,a161
kernel: (kernel) VoodooI2C::pci8086,a160::Failed to read ACPI config
kernel: (kernel) VoodooI2C::pci8086,a160:: Loading hardcoded settings for HSW/BDW/SKL
kernel: (kernel) VoodooI2C::pci8086,a160::Unknown Synopsys component type: 0xffffffff
kernel: (kernel) VoodooI2C::pci8086,a160::Failed to initialise I2C Bus
kernel: (kernel) VoodooI2C::stop

This seems to be caused by the incorrect value returned from here readl(_dev, DW_IC_COMP_TYPE); in VoodooI2C.cpp

Any suggestions about this? I wonder if I am the only person who has this issue on osx 10.12.5?

Anonymous UUID: 8D1A334E-D043-B8C6-6366-2541EB74B352

Sat Mar 17 11:02:45 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff800156e339): Kernel trap at 0xffffff7f84050c5c, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000016dc4000, CR4: 0x00000000003627e0
RAX: 0x0000000000000000, RBX: 0xffffff8046c0ae30, RCX: 0xffffff8001e721c0, RDX: 0xffffff803190c6f0
RSP: 0xffffff81f002bd80, RBP: 0xffffff81f002bd90, RSI: 0xffffff8001e18c60, RDI: 0x0000000000000000
R8: 0x000000000000ffff, R9: 0x0000000000000001, R10: 0xffffff805a6d9040, R11: 0x0000000000000003
R12: 0xffffff806090f440, R13: 0xffffff8060a1eaf0, R14: 0xffffff8046c0ae30, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7f84050c5c, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff81f002b830 : 0xffffff800144f606
0xffffff81f002b880 : 0xffffff800157c654
0xffffff81f002b8c0 : 0xffffff800156e149
0xffffff81f002b940 : 0xffffff8001401120
0xffffff81f002b960 : 0xffffff800144f03c
0xffffff81f002ba90 : 0xffffff800144edbc
0xffffff81f002baf0 : 0xffffff800156e339
0xffffff81f002bc70 : 0xffffff8001401120
0xffffff81f002bc90 : 0xffffff7f84050c5c
0xffffff81f002bd90 : 0xffffff7f840519aa
0xffffff81f002bdc0 : 0xffffff7f82123e7f
0xffffff81f002be20 : 0xffffff7f840527bf
0xffffff81f002be40 : 0xffffff8001a6a69d
0xffffff81f002be80 : 0xffffff8001a6a3e1
0xffffff81f002bf00 : 0xffffff8001a69907
0xffffff81f002bf50 : 0xffffff8001a6b516
0xffffff81f002bfa0 : 0xffffff80014004f7
Kernel Extensions in backtrace:
com.apple.iokit.IOHIDFamily(2.0)[56274755-65D2-3435-99D5-63101C02DFDF]@0xffffff7f82112000->0xffffff7f8218cfff
com.alexandred.VoodooI2CHID(1.0)[AC15AC00-AAEC-39C0-BB1A-C23C613F73F3]@0xffffff7f8404e000->0xffffff7f8405dfff
dependency: com.alexandred.VoodooI2C(2.0.1)[ABF613A5-D745-398B-8567-5A8E406D37E2]@0xffffff7f84022000
dependency: com.apple.iokit.IOACPIFamily(1.4)[8794C760-FDD9-3664-ADED-4A9BBEC6E517]@0xffffff7f821a3000
dependency: com.apple.iokit.IOGraphicsFamily(517.22)[2AEA02BF-2A38-3674-A187-E5F610FD65B7]@0xffffff7f82435000
dependency: com.apple.iokit.IOHIDFamily(2.0.0)[56274755-65D2-3435-99D5-63101C02DFDF]@0xffffff7f82112000

BSD process name corresponding to current thread: kernel_task
Boot args: -igfxbeta abm_firstpolldelay=10000 -disablegfxfirmware -igfxdvmtbeta darkwake=8

Mac OS version:
17D102

Kernel version:
Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
Kernel UUID: 18D901F1-4A03-3FF1-AE34-C26B2732F13C
Kernel slide: 0x0000000001000000
Kernel text base: 0xffffff8001200000
__HIB text base: 0xffffff8001100000
System model name: MacBookPro14,3 (Mac-551B86E5744E2388)

System uptime in nanoseconds: 7359180928465
last loaded kext at 3053740366427: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f8405e000, size 32768)
last unloaded kext at 3438999018544: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f8405e000, size 32768)
loaded kexts:
(none)

EOF

Hello，
My device: Lenovo Mixx510 [i5 7200u]
Both touch screen and touch pens can be used，but It still has some bug：
1、Removing the magnetic keyboard can cause the crash and restart automatically
2、Volume and brightness shortcut key failure
3、Keyboard touch panel failure
4、Shutdown kernel panic

Diar Alexander.

Kexts won't work after 10.13.6 update.

Have you a plan to fix it for 10.14 also?

lenovo ideapad 720s
The driving work is perfect, the computer can recognize the touch pad and multi-finger operation, but fails after a period of time

machine model: Lenovo Yoga 910-13IKB
CPU model: 2,9 GHz Intel Core i7 Kaby Lake
OS version: 10.13.5
The version of VoodooI2C: 2.0.2. The following kexts from 2.0.2 version archive are installed into /EFI/CLOVER/kexts/Other:
VoodooI2C.kext
VoodooI2CHID.kext
Patches applied:
[Windows] Windows 10 Patch
[GPIO] GPIO Controller Enable [SKL+] (tried without this patch with same result)

I see both trackpad and touch screen (as TPD0 and TPL1) in IORegistry. The APIC pins are 0x1f and 0x33. Both devices have property "compatible" set to <"PNP0C50">. So technically everything should work, but trackpad is not recognized in Trackpad section of System Control and there is no cursor reaction on trackpad gestures and button clicks. Nither happens with touch screen.

Attached are my patched DSDT, original DSDT and IORegistry output.
Cepxuo.zip

please

I can't get into the chat room for some reason?

Not working keyboard during installation macos
Elan pointing device
Please tell me method

finger touch jump unexpectedly
loss touch after 3 finger touch
ghost touch
2 finger scroll, zoom buggy on any browser
tablet Cube Mix Plus

Hello

I clone the repo and built all the kexts in Xcode 9.2, but they won't load because of an invalid signature:

Invalid signature -67050 for kext <OSKext 0x7fbee6d088b0 [0x7fff9608e5b0]> { URL = "file:///Library/Extensions/VoodooI2C.kext/", ID = "com.alexandred.VoodooI2C" }

How can I make it load? I have already disabled SIP. Should I use kext dev mode?

Can I sign it myself?

KP with Keepsyms

*** Panic Report ***
panic(cpu 1 caller 0xffffff8008bfe39d): Kernel trap at 0xffffff80090bc8f9, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001ea20000, CR4: 0x00000000003627e0
RAX: 0xffffff802f1d7480, RBX: 0x0000000000000000, RCX: 0x0000000000000017, RDX: 0xffffff80300a2b00
RSP: 0xffffff9126ed3e40, RBP: 0xffffff9126ed3e60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8:  0xffffff8030115c60, R9:  0xffffff91270da000, R10: 0x0000000000800000, R11: 0xffffff811cdc5058
R12: 0x0000000000800000, R13: 0x0000000000000000, R14: 0xffffff802f1d7500, R15: 0x0000000000000017
RFL: 0x0000000000010202, RIP: 0xffffff80090bc8f9, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1

Backtrace (CPU 1), Frame : Return Address
0xffffff9126ed3ad0 : 0xffffff8008ae953c mach_kernel : _panic + 0xec
0xffffff9126ed3b50 : 0xffffff8008bfe39d mach_kernel : _kernel_trap + 0x92d
0xffffff9126ed3d30 : 0xffffff8008a9a593 mach_kernel : _return_from_trap + 0xe3
0xffffff9126ed3d50 : 0xffffff80090bc8f9 mach_kernel : __ZN22IOInterruptEventSource23normalInterruptOccurredEPvP9IOServicei + 0x59
0xffffff9126ed3e60 : 0xffffff7f8975f05d org.coolstar.VoodooGPIO : __ZN10VoodooGPIO32intel_gpio_community_irq_handlerEP15intel_community + 0x9b
0xffffff9126ed3eb0 : 0xffffff7f8975ec58 org.coolstar.VoodooGPIO : __ZN10VoodooGPIO17InterruptOccurredEP8OSObjectP22IOInterruptEventSourcei + 0x2e
0xffffff9126ed3ee0 : 0xffffff80090bc46f mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x11f
0xffffff9126ed3f30 : 0xffffff80090bacd1 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1b1
0xffffff9126ed3f80 : 0xffffff80090ba2b6 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x16
0xffffff9126ed3fb0 : 0xffffff8008a978f7 mach_kernel : _call_continuation + 0x17
      Kernel Extensions in backtrace:
         org.coolstar.VoodooGPIO(1.1)[125807B8-4E2E-341B-AE46-F06983D562A3]@0xffffff7f8975d000->0xffffff7f8976afff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f8974d000

BSD process name corresponding to current thread: kernel_task
Boot args: darkwake=0 kext-dev-mode=1 keepsyms=1 

Mac OS version:
16G29

Kernel version:
Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64
Kernel UUID: D3314D98-5D40-3CD8-98A4-F1DD46C20E03
Kernel slide:     0x0000000008800000
Kernel text base: 0xffffff8008a00000
__HIB  text base: 0xffffff8008900000
System model name: MacBookPro13,1 (Mac-473D31EABEB93F9B)

It can ’ works on tLenovo miix 5 plus ,
But I had known it's Hardware ID
Can you tell me how to edit the DSDT to make my screen touching work?
THX

The trackpad for the ZenBook works for version 1.0.4 but very glitchy and to the point of unusable. However the new kexts don’t even work, as the trackpad doesn’t work.

2F tap opens the right-click menu (context menu). However, moving causes the menu to disappear. This behaviour is unexpected because on a normal Mac, the menu does not close. Using a 2F button press has the normal behaviour.

Similary, 1F "auto releases". Attempting open the Apple dropdown (top-left Apple icon) causes the dropdown to close right away.

I narrowed the issue down to: https://github.com/alexandred/VoodooI2C/blob/master/VoodooI2C/csgesture.cpp#L352

Looks clearing the buttonmask = 0; causes the unintended behaviour, but I'm not sure what exactly.

@coolstar your thoughts as to why this is happening?

Please add support for elan0611 for prefpane and gestures. Thanks

Do you guys have any plans on adding support for the Elan1200? I think it's bot too different from the other ones. There is basic support for the Elan 1200 in the MacForOnce repo, but that doesn't include the features from the other Elan trackpads.

Many people would like to have support for the Elan 1200, since it is very popular in Asus Laptops (100 and 200 series).

Thanks

First off: Thank you very much for your work. With latest releases the touchpad of my Dell XPS 13 works just perfect.

However I'm experiencing hidd to cause relatively high CPU usage with VoodooI2C 2.1 and 2.1.1 when the mouse cursor is being moved. With VoodooI2C 2.03 hidd CPU usage was around 5% for me. With latest releases it went up to 20%. Due to the CPU clock rate being raised, battery drain is caused.

Currently VoodooI2C only has support for gestures up to 3 fingers, although the kext can theoretically support up to 15 fingers. To match functionality with macOS, the project should add support up to 5 fingers.

Secondly, only simple swipes are detected and support for more "advanced" features such as pinch and squeeze/splay can be added.

Lastly, the action for each swipe is hard coded into the kext and it would be nice to have customisability. We should consider following what VoodooPS2 has or implement something better.

System reboot whenever both pen down and touch at the same time

Hello. Thanks for all of your work! One issue that is bothersome...enabling dragging with drag lock in Accessability is selectable, but the behavior does not work. Any way to enable this? Thanks

2 finger click/drag only works the first time, could a deadzone for the buttons be added?
and 2 finger right click is intermittent when tapping, it works ok when two finger click is used

I am using a ASUS ZenBook UX330UAR [8th Generation i5] (I don't know what trackpad is used) but when I use version 1.0.4 of the kext, it works BUT it is close to unusable since if you drag it will go on infinitely, and clicking is very glitchy. However starting with 2.0.0 it just doesn't work at all. Hoping to find a fix for this, or is there a possible DSDT patch for this? Thanks!

Hello Alexandre,
I own an DV11P (7140) with Core M processor. I read that you got the touchscreen working for your DV11P. Is multitouch working? Can you post a short guide for it?

Thanks a lot for your great work!

Paddy