biscate

No. Does your USB configuration is correctly set? If your trackpad works previously and loses after sleep, it may be a USB configuration issue.

My ALPS V8 works pretty well with this kext version on Catalina. Note: I'm using Karabiner Elements for keyboard specific configurations. VoodooPS2Controller-R6B10fixed.kext.zip

Karabiner version 12.2.0 fixed the CAPS led issue.

From 10.14.1, it seems there is no unresponsive cursor issue anymore. The Caps-Lock stay iluminated issue still occurs in my machine.

Thank you, but that kext does not work on my laptop/ALPS V8 device, like happens with previous Bronxteck's compilation (Sierra/High Sierra). There is no cursor movement, exactly as the previous one. There is click and right-click (Option-click). The keyboard works, but the Caps-Lock light keeps on, whatever the mode used.

I suppose yes. I've downloaded the kext from this forum first page. Tried to recompile the original project (link above) on Xcode 10 Mojave, but got errors, and I don't have skills to manage then. error: Build input file cannot be found: '/Volumes/Macintosh HD 2/OS-X-ALPS-DRIVER-Release-6-WIP/VoodooPS2Mouse/VoodooPS2Mouse-Info.plist' macOS Deployment Target: 10.12 Project Format: Xcode 10.0-compatible

Hi guys, I've been experienced an issue with VoodooPS2Controller-R6B10fixed.kext on Mojave. The cursor movement stops after sleep and/or screen saver. Tried other releases from here, but no one else works on my machine. This kext works well on High Sierra. Thanks.

That is a good news, dsarch! I wish you a good job. Ive been following the work from Dr. Hurt, Jake Lo, Rehabman, and others a long time. Got my ALPS V8 working (with V6 Beta10 Fixed) only after update to High Sierra (not sure if it was because macOS itself or any of Clover, DSDT, etc. configurations implemented on each new OS version), but now it works quite well and I am very happy. Still, it's very good having more people working on drivers or patches used by so many people.

You can use Ctrl+Tap to get right-clicks, as a workaround. Do you have two-fingers scrollling? I have ALPS V8 but no scrolling at all.

Asked something like that before. Anybody?

Oh please, the actual driver versions work quite well for a lot of people with V8 hardware, including me. I don't have the skills for that, but guess it's only mixing parts from two existing drivers.

Nothing else?

It didn't work. There is no movement, no tapping with this (Bronxteck) version.

will try it tomorrow, machine is at work.

Hi guys. I've tried some releases/betas but can't have both 1 finger tapping and 2 fingers scrolling (plus CapsLock fix and Wake after sleep). Is there a version supposed to manage all that? Release 5 gives me tapping but NO scrolling. Release 6 RC2 gives me scrolling but NO tapping. My hardware is ALPS V8. Thanks.

In my ALPS AUI1714 (V8) there is no noticeable change since last test: - no "soft" left-click (taping). For now, left-click is possible only by pushing down the flatbed. - second and third fingers act as "soft" right-click - scroll works on Safari although no inertia - no Pref. Pane (No trackpad found)

Awesome!

No, please, keep it! I copied all the messages related to the trackpad from the dmesg output, while using 1, 2, 3 fingers, taping (clicking) the flatbed. Don't know if that is what you're looking for.

Still no trackpad movement, but now there are interesting error messages and fingers use registries: org.rehabman.voodoo.driver.PS2Trackpad already has a class by that name. Kext com.apple.driver.AppleUSBMultitouch start failed (result 0xdc00400a). Kext com.apple.driver.AppleUSBMultitouch failed to load (0xdc008017). Failed to load kext com.apple.driver.AppleUSBMultitouch (error 0xdc008017). VoodooPS2TouchPad loaded... VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3): 0x00 VoodooPS2TouchPad loaded... ALPS: Found a V8 touchpad with ID: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 ALPS: TouchPad driver started... ALPS ENTER DECODE: pkt_id=2 ALPS EXIT DECODE: Fingers=2, x1=7936, y1=240, z=48 ALPS: Process V8: Fingers=2, x1=7936, y1=240, z=48, buttons=0 ALPS ENTER DECODE: pkt_id=2 ALPS EXIT DECODE: Fingers=2, x1=7936, y1=240, z=48 ALPS: Process V8: Fingers=2, x1=7936, y1=240, z=48, buttons=0

Ooops! My trackpad click can respond for touching or pushing down the flatbed corner (similarly to Piranha's trackpad explanation). I mean only touching the flatbed in this case. Apparently, there is no change on messages using 2, 3, 4 fingers, as described on the following dmesg output: ALPS: Found a V8 touchpad with ID: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 output:0 feature:0Element value capacity 320Report count: 1Report ID: 0 input:72 output:0 feature:0ALPS: Found a V8 touchpad with ID: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 ALPS: TouchPad driver started... ALPS: Process V8: Fingers=0, x1=984, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=928, y1=3, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=984, y1=4, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=8120, y1=14, z=0, buttons=1 ALPS: Process V8: Fingers=0, x1=8096, y1=13, z=0, buttons=1 ALPS: Process V8: Fingers=0, x1=1000, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=952, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=992, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1008, y1=2, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=976, y1=11, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=976, y1=9, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1000, y1=5, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=984, y1=11, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1000, y1=9, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=8, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=8, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1008, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1008, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1000, y1=0, z=0, buttons=0 ALPS: Process V8: Fingers=0, x1=1016, y1=0, z=0, buttons=0

Tested in my HP Presario 14-v065br (ALPS V8). Still no trackpad movement, but soft-clicking the Apple logo recorded some trackpad activity on log, as follows. dmesg says (among many other activities and sandbox violation process): ALPS: Process V8: Fingers=0, x1=8160, y1=12, z=0, buttons=1

Tested in my HP Presario 14-v065br (ALPS V8). Still no trackpad movement dmesg says: ALPS: Found a V8 touchpad with ID: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 ALPS: TouchPad driver started... Tried to get some information from Console, on trackpad use, but couldn't find it.

Didn't work for my device (no trackpad movement). System Prefs says "No trackpad found" Boot Log: ALPS: Found a V8 touchpad with ID: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 ALPS: Touchpad driver started

Sorry for that annoying mistake again. Wi'll be waiting for that. Thank you.

Found: ALPS: Touchpad id didn't match V1-V5: E7=0x73 0x03 0x14, EC=0x73 0x02 0x36 and VoodooPS2TouchPad messages: VoodooPS2TouchPad Version 2.8.15 loaded... VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3): 0x00 VoodooPS2TouchPad Version 2.8.15 loaded...