Firmware 2.19 (what I started on)
Right away in Bluetooth mode things felt really off:
- ZR was also triggering R
- ZL was also triggering L
- Random ghost inputs (R, L, Y, etc.)
- Basically unusable in Bluetooth
- Happened immediately after turning it on
Turning off rumble helped a little, but didn’t fix it. Weirdly, just opening the app would temporarily stop everything.
At that point it didn’t feel like normal “drift” — it felt like the whole input system was bugged.
Downgrading to 2.14
After digging around (firmware isn’t easy to find), I downgraded to 2.14.
That made a huge difference:
- No more double-input issue at startup
- Bluetooth actually usable again
- Overall just felt normal
BUT… it’s not perfect
After playing for a while (like 30–60 minutes+), I started noticing:
- Controller feels a little “off”
- Then eventually I’ll get ghost input (usually the R trigger)
The important part though:
- Power cycling fixes it instantly
- Opening the app fixes it instantly
So it’s not constant—it kind of builds up over time.
The interesting part
Opening the app fixes everything immediately.
That makes me think:
- It’s some kind of calibration/state issue
- Not hardware
- The controller just isn’t maintaining that state properly over time
Also worth noting:
- Handheld mode works perfectly, even after hours
- This seems mostly like a Bluetooth issue
My takeaway
- 2.19 = honestly broken (at least for me in Bluetooth)
- 2.14 = way better, but still not fully stable
So downgrading helps a lot, but I wouldn’t call it a full fix.
Biggest complaint
Firmware management is rough:
- Versions aren’t clearly on the official site
- I only found them through a random Google Drive link
- No way to downgrade in the app
That’s kind of a big deal because:
- Most people will just think their controller is bad
- Not everyone has a Windows PC to mess with firmware
Final thoughts
The controller itself actually feels really good. Hardware-wise I like it a lot.
But right now it feels like:
- Great hardware
- Firmware still needs work
Curious if anyone else is seeing the same thing, especially in Bluetooth mode. What firmware are you on?