Kindly Request for Support for the New USB-C Touchpad

[EachSheep]

Pre-report checks

• Have you checked (use search) Azure DevOps Board and Github issues for known bugs and plans?

Is your feature request related to a problem? Please describe.
We sincerely request support for the newly released touchpad with a USB-C interface, launched on October 28, 2024.

Hello, I am a user of both Windows and macOS. On October 28, 2024, I purchased Apple's newly released touchpad with a USB-C interface.
However, I noticed that this new touchpad does not seem to be supported by the Release 3979 driver. On the same machine, the older version of the touchpad with a Lightning interface is well-supported.

My system is Windows 11 Pro 23H3.

Describe the solution you'd like
Add support for the new touchpad with USB-C interface.

[CaptPickguard]

I too have run into this issue. It appears the official Bootcamp drivers also are unable to properly make use of the new device... unless there is a new release from Apple I am not aware of. Hoping support can be added to this driver!

[Private0xCC]

Whether the author no longer intends to update？

[StephenWatson6]

建议继续用lighting版，不推荐USBC版

[StephenWatson6]

建议继续用lighting版，不推荐USBC版

硬件不变，兼容性倒退，不支持15.0以下macos系统。
不适配该windows驱动，无触摸板设置选项，无手势功能，有线连接时报驱动错误。
拆解评测视频：https://www.bilibili.com/video/BV1snSmYBE5e/

[noahhhi]

The new trackpad seem does not support multi-touch on Windows, including iPad and Mac (unless you upgrade to latest system).

[CaptPickguard]

What I wonder is does a new version of bootcamp support it... I wonder if someone could pull the driver from a newer Mac if so.

…

On Wed, Nov 6, 2024, 12:13 a.m. noahhhi ***@***.***> wrote: The new trackpad seem does not support multi-touch on Windows, including iPad and Mac (unless you upgrade to latest system). — Reply to this email directly, view it on GitHub <#548 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIATVDSJ6AZAPE74D2GLVOTZ7GQNZAVCNFSM6AAAAABQ4CPO2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYG4ZTSNRSGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[FoldableChair]

The new trackpad seem does not support multi-touch on Windows, including iPad and Mac (unless you upgrade to latest system).

well magic utilities is able to get it working so im gonna assume its possible

Edit: has anyone tried contacting the developer directly?

[takahar]

Does someone check the USB Device ID of the USB-C Magic Trackpad?
(ref: https://kb.synology.com/ja-jp/DSM/tutorial/How_do_I_check_the_PID_VID_of_my_USB_device )

In many cases, simply adding the USB Device ID to the driver INF file and reinstalling the driver resolves compatibility issues with the newer model of the device.

[FoldableChair]

Does someone check the USB Device ID of the USB-C Magic Trackpad? (ref: https://kb.synology.com/ja-jp/DSM/tutorial/How_do_I_check_the_PID_VID_of_my_USB_device )

In many cases, simply adding the USB Device ID to the driver INF file and reinstalling the driver resolves compatibility issues with the newer model of the device.

I think i found the device id info for the usbc touchpad (VID_05AC&PID_0324) and i tried replacing it in the driver but i got a hash catalog file error and i have no idea how to fix that (im a complete amateur)

[398noe]

As far as I checked, the hardware ID was shown as follows USB\VID_05AC&PID_0324&REV_0410&MI_00.

However, when I check the source code, in Device.c of the AmtPtpHidFilter project, it works like sending STATUS_NOT_SUPPORTED to TraceEvents if it is not a VID / PID of TRACKPAD_2.

mac-precision-touchpad/src/AmtPtpHidFilter/Device.c

Lines 306 to 317 in 29d2778

	// Check if this device is supported for configuration.
	// So far in this prototype, we support Magic Trackpad 2 in USB (05AC:0265) or Bluetooth mode (004c:0265)
	if (deviceContext->VendorID != HID_VID_APPLE_USB && deviceContext->VendorID != HID_VID_APPLE_BT) {
	TraceEvents(TRACE_LEVEL_ERROR, TRACE_DEVICE, "%!FUNC! Vendor not supported: 0x%x", deviceContext->VendorID);
	status = STATUS_NOT_SUPPORTED;
	goto exit;
	}
	if (deviceContext->ProductID != HID_PID_MAGIC_TRACKPAD_2) {
	TraceEvents(TRACE_LEVEL_ERROR, TRACE_DEVICE, "%!FUNC! Product not supported: 0x%x", deviceContext->ProductID);
	status = STATUS_NOT_SUPPORTED;
	goto exit;
	}

Since other VID / PID definitions were found, it appears that we will have to add definitions to these files and modify the associated code, then re-build entire of solutions.

https://github.com/imbushuo/mac-precision-touchpad/blob/master/src/AmtPtpDeviceUsbUm/include/AppleDefinition.h

This may indicate that simply appending the pid and vid to the inf file will not work. ( I have never developed driver 😢 I hope the new Trackpad will work on Windows as well.)

[mlo0352]

I saw that nobody can make releases because they're unable to sign - would there by any way for us to make changes and attempt to create an unsigned driver? I have never worked with drivers, but I'm more than willing to help modify the code to work.

The MT3 working is very ideal for people, who, like myself, need to have all of their peripherals working on USB-C.

[airtaxi]

I don't have this product but if you follow the instruction of this link, you can install any unsigned drivers.

[mlo0352]

well magic utilities is able to get it working so im gonna assume its possible

Edit: has anyone tried contacting the developer directly?

Also, and maybe I'm doing something wrong here, Magic Utilities doesn't have full features - they're missing three finger swipe-up and swipe-to-side and pinching (although they claim this is because there's no Windows equivalent to the pinch-to-zoom action).

[Gentoli]

I have a diff that adds the new USB device ID (will add the Bluetooth ones when I got to using it). All the precision features seems to be working for me.

Gentoli@2f9b218

On publishing / creating release without EV, I know Virtual-Display-Driver uses a self-signed testing cert. I'm not sure how will that interacts with secure boot.

[Wikiwix]

@Gentoli Nice!
You might want to make a PR at this "fork".
At least for USB it is the most complete solution that is maintained. What is more, they make releases for ease of use and have a way to get around the certificate situation