Mchose A7 Ultra [Linux review]

[w6i]

There’s little info about those online, so I’ll share my thoughts.

TL:DR Software:

Mouse has onboard memory, and web based ui.
There is macro support, which I’m assuming is firmware based, but I didn’t test it.

Web UI is accessible on linux using chromium (requires setting write flag on usb device).

Updating dongle/mouse firmware requires running EXE, so I’ve had to update it using VM.

Web UI supports English (pic from VM, but it works on linux as well)

Firmware updater not so much (but it has a single button, and I’m brave)

What is this thing, and why did I buy it instead of well known brand?

Over the years I’ve had multiple razer, roccat, logitech products. Most of them with terrible software, almost all of them broke down before one year mark.

Most mouse designs are a refresh of older ones, and perhaps due to certification with no electrical changes.

Loose comparison with known brand designs:

Mouse wheel:
MCHOSE appears to be using newer sealed TTC encoders, logitech/roccat use older, prone to failure unsealed ones
Switches:
MCHOSE uses Omron optical 70m, LGTM. logitech/roccat use them in newer/pricier models.
Sensor/chip used:
chip is made by Realtek, which adds some familiarity points, all sensors are some ridiculous DPI which I’m going to set to 1200-1400 anyways and forget about it.

How does it feel?

Rigid plastic shell, not glossy but with very little texture. Internals feel rigidly mounted unlike g305 which feel like it contains a weight supported on springs (because it does).
Clicks sound rather hollow, especially side buttons, but everything feels solid.
It’s very light so it sounds light I suppose.
For some reason I expect electronics to be more repairable than average (a mix of seeing the internals and low warranty expectations).
Due to component choice I’d sort of expect the shell to fail at hinge points before switches/encoder does, should that happen the calendar will dictate whether it was a good purchase or not.

[regulareel]

Seems like a crime to write a review of a mouse without a picture of one. Please post one?

I am wondering if the pronounciation in m-chose or mc-hose…

As for repairability, These days I encounter more and more issues with the wheel rather than the mouse clickers especially for non-gaming use. Asus does have good quality mice, if a bit expensive. Then again it also has Armory Crate, which thankfully isnt needed in Linux for the mouse to work well.

[w6i]

I didn’t post one because that’s easy to find online
In the spirit of making questionable choices I went for the most in your face offering

I’ve had enough wheel encoder problems to specifically choose a mouse based on encoder and wheel mount…

Cannot speak about durability yet, ask me again in a year

[Cytomax]

well its been about a month… any update on your thoughts about the product, i appreciate your initial impressions

[w6i]

Scroll wheel lost some tactility/snappiness, it’s still there, just smoother.
It lasts about a month on full charge, charges in less than hour I think?

Overall no complaints so far!

I didn’t check firmware updates since, it works fine and shouldn’t hold sensitive data…

[Draaksward]

Although I see this is the Chinese China, but the sole fact of “web UI” instead of an app, is something I wish other companies will pick up.

[UNinaMe]

Hi there,

I just got this mice but having some issue with connecting it with WebGUI. For some reason the mice stays greyed out on the GUI and I cannot do anything:

I think you mentioned that some kind of WRITE flag needs to be set for the USB device? Can you elaborate on that and perhaps share how you did it?

I am running Arch Linux with KDE Plasma DE. I did update the firmware using windows VM.

Thanks!

[UNinaMe]

For anyone wondering, I followed this:
Open up a terminal and enter lsusb record the relevant vendor and product id for your mouse, my listing comes out as Bus 001 Device 003: ID 3837:100b RealTek MCHOSE A7 V2 Ultra so vendor is 3837 and product is 100b, then

sudo nano /etc/udev/rules.d/mchose-a7-v2.rules

KERNEL==“hidraw*”, ATTRS{idVendor}==“3837”, ATTRS{idProduct}==“100b”, MODE=“0666”, TAG+=“uaccess”

replace the Id’s if they came up different, save with control + o and exit nano. enter the following to the terminal:

sudo udevadm control --reload-rules

sudo udevadm trigger

and you should have access, save this for later if you purchase the mouse.

[pwntr]

Thank you very much, this worked perfectly on my Fedora 43 machine :)!

One thing to note when copy-pasting is to replace the fancy styled double-quotes with regular plaintext ones, like this:

KERNEL=="hidraw*", ATTRS{idVendor}=="3837", ATTRS{idProduct}=="100b", MODE="0666", TAG+="uaccess"

[w6i]

It’s been over a year, and it’s the same as it was one month in.

[lez]

Hey UNinaMe, thank you for this post! I’m having the same issue with my MCHOSE L7 Pro on Nobara Linux 44 / KDE . I did apply the steps you mentioned in your reply, however I still can not access the web driver (grayed out ui like you described it before). I did change the IDs to my device specific output (**lsusb). Im quite new to Linux / Nobara, is there anything I’m missing here?
**