BetterJoy has a low battery feature, and most people discover it the annoying way: a Windows notification pops up mid-game — sometimes once, sometimes relentlessly, occasionally on a controller that was charged an hour ago. The feature itself is real and useful (it arrived alongside the battery colour indicator described below). The spam and the false alarms have their own documented patterns, mainly in issues #898 and #973. This page separates “your battery really is low” from the two known glitches.
What the notification and the colour change mean
BetterJoy reads the battery level your controller reports and does two things with it: it can raise a low battery notification (the feature was added as a headline item in v6.4b), and it changes the background colour of the controller’s icon in the BetterJoy window as a running battery indicator (present since v6). So the first check is free: glance at the icon colour before reacting to a popup. If the colour says healthy and the popups keep coming anyway, you are not looking at a battery problem — you are looking at one of the glitches below. One caveat: Bluetooth battery reporting from game controllers is coarse, often a handful of rough levels rather than a true percentage, so treat “low” as “charge soon,” not a precise measurement.
Glitch 1: Notification spam that survives the game (#898)
In issue #898, after the user closed their emulator, BetterJoy kept firing low battery notifications continuously — the only thing that stopped them was restarting. If your spam outlives the session that triggered it, do exactly that: close BetterJoy completely (check the system tray, not just the window) and relaunch it; if the notifications persist, reboot. This pattern is a stuck notification state, not new information about your battery arriving every few seconds, and no setting change is needed once it clears.
Glitch 2: A popup on every button press, and input stops reaching the emulator (#973)
Issue #973 is the stranger variant: inside the emulator, every button press raised a low battery notification, and the controller’s input did not reach the game. The workaround that reporter confirmed — on Windows 11, incidentally, which is useful evidence the combination works there — was to change the legacy UseHIDG value in BetterJoyForCemu.exe.config (the toggle for the bundled HIDGuardian hiding layer) and to follow a specific start order: launch BetterJoy and let it settle before starting the emulator. Two cautions before you copy it: write down the original value first, and treat it as a targeted workaround for this exact symptom, not a general tweak — our config file guide documents UseHIDG as a legacy, troubleshooting-only switch for precisely this reason. If your input is being swallowed more generally, the not-detected guide and the gyro/DSU checks cover the neighbouring causes.
Charging while you play
If the battery really is low, you have a clean option with the Pro Controller: play over USB. A USB-C cable carries data and charge at the same time, so a wired session tops the battery up instead of draining it — and as a bonus you remove Bluetooth from the equation entirely. Joy-Cons are less flexible: they do not charge while you are playing with them detached; they charge when attached to the console or a charging grip, so a genuinely flat Joy-Con means a charging break or swapping to the other pair. Community practice for long sessions is simple — start charged, and treat the first honest notification as your cue to plug in rather than a countdown to argue with.
Reducing false triggers
- Fully charge, then test: a controller charged to full that still triggers immediate “low battery” popups is reporting badly or hitting a glitch — that contrast is your diagnostic.
- Restart BetterJoy after emulator sessions rather than leaving it resident for days; the #898 spam state builds across sessions.
- Re-pair if readings stay implausible: remove and re-pair the controller in Windows Bluetooth settings so the battery reporting channel is renegotiated.
- Keep the layers straight: if the popup-per-press pattern matches #973, apply that workaround deliberately (above) instead of stacking random changes.
One more readout worth trusting over any single popup: after a full charge and a fresh pairing, watch the icon colour through a session. A colour that steps down gradually is the feature working as designed; a colour that claims “low” within minutes of a full charge is the reporting glitch again, and the re-pair in the list above is the fix to repeat — not another charge.
The notification feature working correctly is worth having — a controller dying mid-session without warning is worse. Get a clean copy of the program from the download page if your build predates the feature’s fixes, and find related fixes on the troubleshooting hub.
FAQ
Can I turn the low battery notification off?
There is no prominently documented on/off switch for it in the program’s official documentation, and we won’t invent one. The realistic controls are the ones above: keep the battery genuinely charged, restart the program to clear the stuck state (#898), or apply the #973 workaround when the popup-per-press pattern matches.
The popup says low battery but the Switch shows plenty of charge. Who is right?
Probably the Switch. Bluetooth battery reports to Windows are coarse and can go stale, especially across sleep and re-pairing. Charge fully, re-pair, and judge by the icon colour plus a fresh session rather than a single popup.
Is the notification spam a sign of malware or a broken controller?
No — both documented spam patterns (#898 and #973) are BetterJoy-side states with named workarounds, on otherwise healthy controllers. If spam survives a reboot with BetterJoy closed, look elsewhere; with BetterJoy open, you are in the territory this page covers.