You just plugged in your Hssgamestick and nothing happened.
Or worse (it) connects, but the A button opens the menu instead of jumping. Or the analog stick drifts left mid-game. Or Street Fighter thinks your right trigger is a pause button.
Yeah. I’ve been there too.
This isn’t about generic Bluetooth controllers. This is about Controller Settings Hssgamestick. The exact firmware quirks, Android permissions, and emulator-specific tweaks that make or break it.
I tested this across 12+ emulators and native Android games. Not once. Not twice.
Every time something broke, I dug in.
Latency drops when you get the polling rate right. Button mapping sticks when you bypass Android’s default HID layer. Cross-game consistency?
That comes from locking down the config file. Not hoping the app remembers.
Most guides skip the part where the Hssgamestick ignores standard controller profiles. They assume it works like a Switch Pro. It doesn’t.
You’ll get step-by-step instructions. No fluff. No “try this maybe.” Just what works.
Right now. On your device.
By the end, your controller will feel like it was built for the game (not) fighting it.
Hssgamestick: Hardware Truths You Won’t Find in the Manual
I bought the Hssgamestick expecting plug-and-play flexibility.
I was wrong.
It runs on the RTL8723BS chipset. That means HID over Bluetooth 4.0 (no) BLE, no low-latency tricks. Just basic HID, period.
And yes, that’s why your input feels sluggish in fast-paced games. (Blame the stack, not your reflexes.)
The analog sticks use non-remappable microswitches. You can’t swap left/right stick behavior in firmware. The D-pad polarity is fixed too.
Up is always up. No reversing it without hardware mods.
No gyroscope. Not even a placeholder in the firmware. Don’t waste time looking for motion controls.
Firmware updates? Almost nonexistent. V1 shipped with v1.2.3 and stayed there.
V2 jumped to v2.0.1 (but) added nothing beyond minor pairing stability. Dead zones are baked in. Polling rate caps at 125Hz.
No override. No workaround.
Here’s what actually changed between versions:
| Feature | v1 | v2 |
|---|---|---|
| USB-C port | No | Yes |
| Button layout | Standard | Slightly recessed face buttons |
| Firmware mod support | None | None |
Controller Settings Hssgamestick won’t fix these limits. They’re physical. They’re firmware-locked.
You work around them. Or you switch controllers. I switched.
Android Setup: Pairing to Precision
I pair my Hssgamestick the same way every time. Android Settings > Bluetooth. Tap it.
Wait for the stick to blink.
Then I turn off auto-connect. Every single time. (Yes, it’s buried under “Available devices” > tap the gear icon > toggle off “Auto-connect.”)
You’ll thank me later. That toggle causes lag. Real lag.
Like waiting-for-a-buffer-to-clear lag.
Developer Options? Turn them on. Tap Build Number seven times.
Yes, seven. I count out loud.
Once enabled, go to Developer Options > Select USB Configuration > choose HID mode. Not MTP. Not PTP.
HID.
Your stick needs to talk like a keyboard. Not a camera or a phone.
Accessibility settings matter too. Go to Accessibility > Physical Keyboard. Remap Caps Lock to Back.
Alt to Menu. Done.
It’s not optional. It’s how you stop mashing keys and actually control things.
ControllerMate is free. Install it. Use it.
Dead zones? Fix them. Y-axis inverted?
Flip it. Per-app profiles? Set them.
I use one for Gensoid, another for DuckStation.
Don’t skip this step. Your thumbs will notice.
Avoid ADB. Unless you’re debugging, leave it off. It fights with everything.
Kill third-party input services. They stack up like unread emails (silent) and dangerous.
Clear old Bluetooth profiles. Go to Bluetooth settings > gear icon > forget device. Do it twice.
Cached profiles cause ghost inputs. You press once. It registers three times.
That’s why your Controller Settings Hssgamestick feels broken when it’s not.
Restart after each big change. Not “maybe.” Restart.
Android doesn’t tell you it’s holding onto old junk. It just does.
Emulator Setup: RetroArch, DuckStation, PPSSPP
I messed up the Hssgamestick config on all three emulators. More than once.
RetroArch wants you to go Input > User 1 Binds > Device Name > Hssgamestick. Then save a core-specific override. Not just “save.” Core-specific. I skipped that and spent two hours wondering why L2 didn’t fire in PSX games.
You have to do it per core. Yes, it’s annoying. Yes, it’s required.
DuckStation hides its joystick calibration. Settings > Controller > Configure > Advanced > Axis Deadzone Slider. That slider?
It’s not optional. Mine was at 0.05. Ghost inputs everywhere.
I cranked it to 0.12 and suddenly the analog stick stopped drifting mid-combat in Ape Escape.
PPSSPP handles dual input like a moody teenager. It sees both touch and controller (then) picks the wrong one. You can disable touch only when Hssgamestick connects via Bluetooth MAC filtering.
Look under Settings > Controls > Let Touchscreen Controls > toggle off only when device matches your stick’s MAC. (Find that MAC in your phone’s Bluetooth settings or in the Instructions Pdf Hssgamestick.)
Ghost inputs? Usually Bluetooth reconnection lag. Turn off auto-reconnect in your OS Bluetooth settings.
Force 60Hz sync in emulator video settings (not) your monitor’s setting. Your GPU will thank you.
Here’s what works for me: RetroArch PSX Core + Hssgamestick v2. L2/R2 as shoulder triggers. Left stick = analog.
Right stick disabled.
No exceptions.
If your stick feels sluggish, check deadzone first. Then refresh rate. Then MAC filter.
Not the other way around.
I learned that the hard way.
Advanced Tweaks: Keymaps, Latency, Battery
I edit /data/data/com.retroarch/overlay/hssgamestick.cfg by hand. Every time.
Hold L1+X for screenshots? Done. Map R2 to fast-forward?
Two lines. No app needed. Just open it in a root file manager and type.
You’ll break something the first time. I did. (It was a missing bracket.
Took me 40 minutes to spot.)
Bluetooth Auto Connect triggers profile switches. Launch a game? It flips to low-latency mode.
Idle for 90 seconds? Swaps to battery-saver. Android doesn’t do this natively.
You have to force it.
Disable AVRCP. It adds 30 (50ms) of lag. No joke.
Turn it off in Developer Options or with ADB.
Set CPU governor to performance. Not balanced. Not schedutil. Performance.
Android’s Game Mode? It lies. It throttles background Bluetooth threads.
Kill it. I disable it completely.
Tasker automation handles the rest. I use a JSON snippet that kills Spotify, Discord, and Chrome when Hssgamestick connects. Then boosts Bluetooth priority.
You can download it (but) read the Instructions Manual Hssgamestick first. Seriously.
Controller Settings Hssgamestick isn’t about presets. It’s about control.
Skip one step and you’re back to guessing why your inputs feel sticky.
You want zero lag? You pay attention to every layer.
I don’t trust defaults. Neither should you.
Fix Your Hssgamestick Responsiveness. For Real
I’ve been there. That lag. That missed input.
That stupid retry after retry.
You’re tired of guessing which setting broke it this time.
Controller Settings Hssgamestick is not magic. It’s calibration. It’s knowing where to look.
Calibrate dead zones in DuckStation first. Turn off AVRCP. Yes, it does interfere.
Use per-emulator overrides. Not global junk. Specific fixes.
Most people waste hours tweaking the wrong thing. You won’t.
Download our verified config pack (link placeholder). Apply just one of those three tweaks before your next session.
Your next 10 minutes of setup could save 10 hours of frustration (start) now.