Arch Linux User Repository

@ScoopNewsworthy I've installed the updated package to test. Unfortunately, BLE still isn't working, but I can confirm that the permissions for /dev/hidraw4 have indeed changed:

crw-rw-rw-+ 1 root root 243, 4 Dec 24 20:03 /dev/hidraw4

This suggests the udev rules are working correctly now, so the remaining issue likely lies with the app itself.

Thanks!

@bubble8008

Thanks for digging into that! The linux-after-install.sh confirms BLE is intended to work, I'd imagine - the rules there just have syntax errors (missing commas by the looks of it, missing KERNEL== prefix (not just KERNELS==), missing 0005: bus type).

I've updated the package with corrected BLE rules based on your udevadm output, and added a missing product ID and a catch-all that was in the upstream script ('a293' and '3311' vendor respectively).

The invisible window issue when running sudo hexcore-link --no-sandbox is likely an app-level bug, maybe with their Electron implementation? Not something we can probably fix downstream with just the binary.

Can you test the updated package and confirm if BLE permissions are now correct? (So we can at least confirm the udev side is sorted)

@ScoopNewsworthy I've tested the updated package, and USB detection is working now. Thanks a lot!

Regarding BLE, I recall the Windows version of Hexcore Link having Bluetooth support. I also noticed the following lines in /opt/hexcore-link/linux-after-install.sh, which suggests BLE might be intended for Linux as well:

# ble
KERNELS=="*:000D:F0E0.*" SUBSYSTEMS=="hid" DRIVERS=="hid-generic", MODE="0666", GROUP="plugdev"
KERNELS=="*:07D7:0000.*" SUBSYSTEMS=="hid" DRIVERS=="hid-generic", MODE="0666", GROUP="plugdev"

Here is the output from udevadm info -a -n /dev/hidraw4:

......
  looking at device '/devices/virtual/misc/uhid/0005:000D:F0E0.0009/hidraw/hidraw4':
    KERNEL=="hidraw4"
    SUBSYSTEM=="hidraw"
    DRIVER==""
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"

  looking at parent device '/devices/virtual/misc/uhid/0005:000D:F0E0.0009':
    KERNELS=="0005:000D:F0E0.0009"
    SUBSYSTEMS=="hid"
    DRIVERS=="hid-generic"
    ATTRS{country}=="00"
    ATTRS{power/control}=="auto"
    ATTRS{power/runtime_active_time}=="0"
    ATTRS{power/runtime_status}=="unsupported"
    ATTRS{power/runtime_suspended_time}=="0"
......

I tried running sudo hexcore-link --no-sandbox. The icon appears in the taskbar, but the window doesn't render anything (it remains invisible). This happens on both X11 and Wayland.

It's possible that BLE support is simply not fully implemented on the Linux version yet.

@bubble8008 Can you confirm that Hexcore Link even has BLE support, for configuration? I don't remember ObinsKit having that, and I don't have a Hexcore board to test with.

In the meantime, can you: 1. Test the updated package to confirm USB detection works 2. If you still want to pursue BLE, run udevadm info -a -n /dev/hidraw4 | grep KERNELS when connected via Bluetooth and share the output 3. Try sudo hexcore-link to rule out permissions - if it still fails with sudo, the app likely doesn't support BLE

@ScoopNewsworthy

Adding the following rules enables detection for my Anne Pro 2D via USB:

# Anne Pro 2D
SUBSYSTEM=="usb", ATTRS{idVendor}=="3311", ATTRS{idProduct}=="a298", MODE="0666", TAG+="uaccess", TAG+="udev-acl"
KERNEL=="hidraw*", ATTRS{idVendor}=="3311", ATTRS{idProduct}=="a298", MODE="0666", TAG+="uaccess", TAG+="udev-acl"

However, I tried the following for Bluetooth, and it didn't work:

# ble
KERNELS=="*:000D:F0E0.*" SUBSYSTEMS=="hid" DRIVERS=="hid-generic", MODE="0666", TAG+="uaccess", TAG+="udev-acl"
KERNELS=="*:07D7:0000.*" SUBSYSTEMS=="hid" DRIVERS=="hid-generic", MODE="0666", TAG+="uaccess", TAG+="udev-acl"

Here is the log:

error: [ui] getHexcoreDevicesAndOpen
Error: 23-1-1/dev/hidraw4 for readDeviceType
error: [ui] getHexcoreDevicesAndOpen
Error: 23-1-1/dev/hidraw4 for readDeviceType

USB works fine for me, but it would be great if Bluetooth could also be supported.

Finally, it seems that install=${pkgname}.install is missing from the PKGBUILD.

Thanks for your work!

@bubble8008 Thank you for that. Let me know if your issues are resolved. Install okay on my machine.

Hi,

I noticed that the current package fails to start after installation.

I managed to get the original .tar.gz from Hexcore's customer service (Taobao), and confirmed it has the same hash as the previous commit and the same content with your version. You can download it here: https://drive.google.com/file/d/1BvScsPp7zLDGix7UK3z1fZiOG6xtg-1N/view?usp=sharing

Regarding the startup issue: It seems the Exec line in the .desktop file was incorrectly changed to Exec=hexcore-link %U. Reverting this or fixing the path should solve the problem.

In addition, after manually starting the program, it fails to detect my keyboard unless I run sudo chmod a+rw /dev/hidraw*. Does this mean we need to add uaccess rules similar to obinskit?

Could you please fix the desktop entry (and update the .tar.gz if you want) and check the udev rules?

Thanks for your work!

It would appear that the Hexcore website is down.

Upstream source hexcore.xyz appears to have suffered a critical server misconfiguration or a complete environment reset. As of late December 2025, the server at 120.26.250.197 is no longer serving company content/binaries and is instead displaying a default LNMP (Linux/Nginx/MySQL/PHP) placeholder page. This indicates the web-root has been wiped or the Nginx config has reverted to factory defaults.

I moved to hosting the .tar.gz files that are dependencies of this package, to Google Cloud, to allow this package to continue to build.

The ObinsKit package has an identical hash to last commit, as I had that one cached locally, so this is just as "safe" as the last version of this package. The Hexcore Link budnle required rebuilding the .tar.gz locally, and I have renamed it accordinly, but uses the exact same binaries as the last commit, but feel free to inspect.

Just being transparent about the upstream link changing.

[UPDATE 12/21/2025] The website seems to be coming back up a little at a time. The download links don't work, but it looks like maybe they've undergone a site overhaul and are bringing things back up. Used user install files provided by bubble8008.

Hexcore 官网似乎挂了。到哪里还能下载到软件包呢？ The Hexcore website seems to be down. Where can I download the software package?