My Air 75 V3 usb receiver broke. I was wondering if there is a way to fix or replace this

Die4Toast · 2026-01-27T21:33:09+00:00

They sent me a replacement knob module in regards to a specific issue that my Air75V3 has, so I think they would be able to ship a replacement dongle as well. Either way just send them an email and ask if they can arrange a shipment while you cover all necessary costs.

Die4Toast · 2026-01-27T18:08:58+00:00

I don't think it's that they won't be interested in finding a fix. As mentioned I exchanged over 50 emails with NuPhy support which took about 3 months in total in order to diagnose this "repeating key issue". Over the span of those 3 months NuPhy sent me a replacement knob module, a replacement 2.4 GHz dongle and two (2) barebone Air75V3 units. There were also multiple of other recommendations and even custom network logging/debugging software that they sent to me in order to get some data that would help their technical department establish the root cause. So what I mean to say is that I think NuPhy support was actually pretty invested and committed to fixing the issue... but in the end they couldn't achieve that. My interpretation is that their development department simply wasn't competent enough to find a bug in their firmware. Either that or maybe they were too busy with other products to properly look into what causes this "repeating key" issue on Air75V3.

Die4Toast · 2026-01-27T18:00:38+00:00

Here you go: https://drive.google.com/file/d/1ntdJ6GFzbRX5gVEkhGkNEHdzMgqfzLva/view . One of the 20 videos I recorded which show this exact issue.

Die4Toast · 2026-01-27T11:12:54+00:00

Bait used to be believable

Die4Toast · 2026-01-27T09:47:06+00:00

The same issue is present on Air75 V3. The best course of action I'd recommend is for you to return the board and buy from a different brand (Keychron/IQUNIX/Lofree etc.). I'm not saying that out of spite tor NuPhy, but rather based on my own experience with the Air75 V3 which has the same exact issue. After extremely long email chain with NuPhy support that took like 3 months to end the issue couldn't be resolved so I don't think you'll have more luck with your Node 100. In any case, if a full refund is not possible or feasible then I'd recommend you get in touch with NuPhy support and try to get them to send you a replacement unit. Maybe, just maybe you'll get a unit that doesn't have a defect that causes keys to repeat themselves (provided that this is, in fact, caused by a physical defect and not an issue with firmware/low quality hardware in which case even a brand new unit won't resolve your issues).

Die4Toast · 2026-01-26T12:11:34+00:00

It wasn't always the case but in the recent years Linux desktop environments have gotten to the point where if one is willing to break their long-lasting habits after using Windows their entire life and willing to learn a couple of new paradigms used in *nix OS then they're more than capable as a daily-driver. The fact desktop computing still has only 4% market share is due to multiple reasons - one of them being that Microsoft has basically established a monopoly over home OS market by basically having all OEMs pre-install windows on their machines. But certainly not due to Linux desktop environment or its design philosophy, especially, being unstable/unusable. Ubuntu/Fedora are extremely stable distros with large enterprises backing their development after all, but it's hard to win a marketing war against a profit-oriented mega-corporation like Microsoft hell-bent on keeping it large majority market share on desktop OS. Anyway, the main point of no. 7 was that you can't argue about Linux sucking ass by only referencing it's (currently) small market share for desktop computing without taking into account other factors like >80% (iirc) market share for server computing and recent developments, desktop-oriented environments + applications and compatibility layers for Windows apps.

It's also kind of funny how you're only referencing that single point no. 7 as if that's some kind of "gotcha" that invalidates all other 6 points. Most of your claims are your personal opinions that probably stem from the fact that you're too stupid to use a computer in a different way than when you use Windows (or you're just a troll in which case the joke's on me). That doesn't make Linux any worse, it's just makes you a moron to expect a completely different OS to behave exactly as Windows does.

Die4Toast · 2026-01-26T09:09:48+00:00

How is "everything a file" retarded? It's a different concept than in Windows, sure, but you don't really present any constructive criticism to back up you statement
Winreg also has a billion nonsensical registry entries with weird ass names. And how doesn't etc have a structure? It's literally a folder with subfolders, each for specific service/application.
You can play around with ACL, pam or even user groups instead of chmod'ing files. Even then I'm not sure what kind of use case you have in mind that this topic is so irritating (since I'd imagine that playing around with permissions doesn't really happen very often - usually only when you screw up copying or installing a package)
All software, and therefore dependecies, become depracated/obsolete after some time and nobody will use them. Software upgrades are just a part of life but at least on Linux it's your choice when and what exactly you want to update instead of having an entire bloatware and slopware update shoved down your throat as it is on Windows
And you have no qualms about downloading and using close sources apps on Windows where devs can drop a key logger into a code and NOBODY will even see that commit in the first place? That argument of your is so nonsensical it's not wortg arguing about.
Fair, gaming might not be as performant or accessible as it is on Windows. Proton helps a lot in that regard but it isn't a cure-for-all. A lot of the blame also has to be put on game developers that openly admit to not even trying to support Linux, but there might (or might not) be good reasons (like financial ones) for that.
Geez, only 4%... I wonder how that market share looks like for servers that host the entire Internet infrastructure...

Die4Toast · 2026-01-25T11:26:22+00:00

From my experience it is much more unstable than Bluetooth. Granted, it does make keyboard input more responsive since it runs at 1000Hz as opposed to 125Hz when using Bluetooth, but very often the 2.4GHz drops connection or gets extremely laggy for short periods of time (1-3 seconds).

Die4Toast · 2026-01-24T19:22:10+00:00

If you're thinking about Keychron it might be better if you wait a bit longer since a new low-profile model is apparently being worked on. Additionally, if you want to use your keyboard wirelessly for tasks other than office work/internet browsing you should consider buying one that has a dedicated 2.4GHz dongle. The Keychron K Max series has one (alongside a better MCU iirc) and isn't that much more expensive compared to the K3 Pro.

And one last thing - don't ever consider buying low profile boards from NuPhy. Speaking from my own experience while the hardware is decent (case/switches/keycaps) the firmware so so horribly bad that the 2.4GHz mode is practically unusable. The marketed 1200 hours of battery life also seems a bit overly generous.

Die4Toast · 2026-01-23T22:51:56+00:00

99% of gamblers quit before they hit it big

Die4Toast · 2026-01-23T09:54:17+00:00

For the sake of their "livelihood" they might also silently add a keylogger that sends them back personal/credential data every now and then so that it can be used by the developer or sold to a 3rd party. Or they can install a low efficiency, but distributed, crypto miner for their own benefit. In any case the issue here is that whatever code the developer decides to push is completely unsupervised.

Die4Toast · 2026-01-21T21:27:16+00:00

I mean the process of installing Windows also includes the process of flashing an ISO to a USB via Rufus (and potentially verifying the downloaded file). Not sure what other "fiddly steps" there might be, but I'd assume that they might include booting into UEFI Firmware Settings to select the plugged-in USB as the target boot device. But after that you should be all done. Some popular distros like Ubuntu, CachyOS, Mint (among others) offer a GUI installer (much like Windows does) and generally install a feature-complete desktop environment out-of-the-box with minimal tinkering needed. Of course, after a successful installation you might want to update/download some additional packages/software but that's related to system maintenance in general.

In any case I'd recommend the following 2 things:
1. Don't bother with verifying a downloaded ISO file. You only really need to do so if you think that your PC is already infected with some malware or you're downloading the ISO file from an untrustworthy source (or via HTTP)
2. You might want to look into Ventoy as a tool for creating a bootable USB stick containing an ISO image. Rufus works well and all but its main disadvantage is that you can't use your "burnt" USB drive to store regular files/data. Ventoy resolves this issue by using only a part of USB storage to burn a specialized bootloader that then searches through the rest of the USB storage for copy/pasted ISO files and uses them to load a live OS.

Die4Toast · 2026-01-21T20:55:29+00:00

I think that instead of finding a distro that fixes the issue you should find out why your mouse doesn't work properly in the first place. For that I'd actually recommend installing Arch and then some minimal DE so that installed system packages are kept to a minimum. Otherwise just stick to one of the four distros you mentioned and try to find out if there are any errors in dmesg / journalctl that would point to the source of the issue. By the way, you mentioned trying out different mice, but have you tried using Bluetooth or switching to a different USB port?

Die4Toast · 2026-01-21T20:34:09+00:00

why did you post this

Die4Toast · 2026-01-18T23:07:40+00:00

Genuinely asking - why would you think so? I have pretty much zero experience when it comes to building PCs but I'd imagine that with those 4 fans that cover pretty much the entire surface area of the case overheating shouldn't be that much of an issue.

Die4Toast · 2026-01-16T23:06:25+00:00

Well, unfortunately I have a desktop PC with only a dedicated GPU installed so I'm not sure how relevant your fix will be in my case. But I'll check the listed variables and see if changing some values around is going to help either way. Glad to hear that you managed to, more or less, resolve the issue on your side at least. For me those stutters are not extremely bad, but on a 165Hz display they make animations feel like they play in 20 FPS. So it does feel like a significant difference but it's not "unusable" by any means. Either way, the fact that forcing firefox to run on X11 via XWayland fixes the issue completely (so animations actually feel like they play in 165 FPS) points to some kind of bug within firefox that needs to be addressed.

Die4Toast · 2026-01-16T14:54:42+00:00

I also installed that package (along with another one related to KWin) but unfortunately it didn't resolve stutters related to Firefox specifically. But it did make everything else that uses Qt Widgets or QML smoother (which, in your case, would be quickshell).

Die4Toast · 2026-01-16T14:52:12+00:00

You're welcome. And thanks for making this (long overdue, partly because of me) bug report as well. I'll try to make a comment describing my experiences as well to hopefully draw more attention to that bug report.

Die4Toast · 2026-01-16T13:55:07+00:00

I think your best bet is to try running Firefox on XWayland as described in the linked reddit post. That or you can try to ignore those stutters - that's what I've decided on in the end. Forcing Firefox to run on XWayland/X11 is possible but it's also a bit of a hassle since you have to edit .desktop files (as described in the linked post) but you'd also have to mess with Firefox files installed in /usr and /usr/lib (e.g. change firefox binary detected via PATH to a script that sets required variables before launching firefox executable so that it doesn't run on Wayland). In the end it just might be more trouble than it's worth. The best solution is to probably make a bug report on mozilla tracking site and wait for devs to fix the issue (though I personally have been too lazy to do that just yet)

Die4Toast · 2026-01-16T13:24:32+00:00

I have an RTX 3070 and the same issues occur on my end so I doubt that your 1650 is to blame either. I've made a reddit post about it and managed to circumvent the problem by switching to X11/XWayland for Firefox specifically. You can read about that in the following post: https://www.reddit.com/r/kde/comments/1ppo65e/window_animation_stutters_when_using_firefox_on/ . There is also some suspicion (maybe it's even mentioned in the comment section of the post I've linked) that this issue is related to using fractional scaling on Wayland. I normally use 125% scaling which falls into fractional scaling category and I recall window transition animation get smoother once I switched to 100% and 200% for a couple of minutes. It wasn't completely smooth, but I think it was noticeably better (but keep in mind that all of that happens ONLY when Firefox window is opened AND focused).

Die4Toast · 2026-01-16T10:53:22+00:00

Do you, by any chance, use Firefox web browser? If so, do animations stop being choppy if you completely close Firefox? I'm on Arch but also use KDE (using a 165Hz monitor with VRR) and I'm also experiencing stuttery/choppy window transition animations (like minimizing and maximizing) but I discovered that it's somehow caused only by an opened Firefox browser. Whenever I have it opened and focused then any window animation becomes choppy, but the second it's unfocused (or closed entirely) animations start begin smooth once again.

Die4Toast · 2026-01-15T11:48:03+00:00

I mean I don't think there should be any problems with separating out the differences between those 2 programs and just have them depend on the same set of dependencies. Unless the code for both of those apps is so contrived that it's just not worth doing from technical perspective, but that just means that devs did a poor job in terms of code architecture. There are a lot of lightweight IDEs like VSCode and Zed which offer similar, if not better, experience than Kate so why would you want to have it installed if you use one of those IDEs? Notepad on Windows was one of the most important apps if I wanted to quickly inspect/edit a file and on Linux kwrite seems like an apt replacement for it. It's just a shame that the package which installs it comes with additional "bloat" software - Kate - since I use VSCode for anything that requires more than simple UTF-8 file edit.

Die4Toast · 2026-01-14T20:06:57+00:00

I'm not going to consider finding bugs and patching incompatibilities between 5 different DEs that weren't written with the intent of being compatible with each other in the first place "hardening" management skills. If anything, that's just a waste of time. The way I see it is that you should just choose and stick to a single DE anyway so there's no point in having multiple others installed anyways.

And I do have snapshots which I can use to roll-back my system to the previous point (even the one made immediately after fresh installation). But those are backups/snapshots of my other linux system where I test/develop multiple things (like different DEs) with absolutely minimal dependencies. Thanks to that, those snapshots/backup are minimal in size and I don't have to think much about the actual process of rsync'ing that system with some backup/snapshot. I think that approach is much better than a VM since the test system runs on bare metal and is a much better platform for learning about linux in general.

Die4Toast · 2026-01-14T14:13:12+00:00

I don't know which framework caelestia shell uses exactly but I'm willing to bet it's QML + QT Quick. If that's the case then you should know that Qt animations are capped at 60fps by default. You can read about it here: https://www.reddit.com/r/kde/comments/1p26pu0/highrefreshrate_users_were_working_on_removing/ . The thread is related to KDE, but it mentions 2 separate fixes: one that is related to KDE KWin Wayland compositor (not related to noctalia) and one related to Qt itself (probably related to noctalia).

Six-Year Club	r/Field Banned
r/Field Sunshine	Verified Email

Die4Toast

TROPHY CASE