Start with a clean baseline
Use raw browser input to separate a physical control/event problem from game/app mapping. Test the exact failing key, button, axis or wheel action rather than a generic connected/not-connected state.
Live evidence
Relevant checks
Battery Runtime CalculatorEstimate runtime from battery watt-hours, average load and conversion efficiency.
→USB Voltage Current to Watts CalculatorCalculate watts from an entered USB or charger voltage/current profile.
→USB-C Cable Power Rating CheckCompare an entered cable wattage rating with the power you want to carry, while keeping protocol/e-marker limits explicit.
→First sequence
Do the high-signal checks before risky changes
- 1
Use the power bank's documented usable output/profile
- 2
Check cable rating
- 3
Compare the same load on another known-good output where available
Decision points
What the result should change
If raw events are correct herePrioritize app/game bindings, profiles, sensitivity or remapping.
If duplicates/drift reproduce hereThe symptom is independent of the affected app; compare connection mode and official calibration.
If the entire device freezes intermittentlyPrioritize receiver/cable/power/interference before a single switch or stick component.
Browser can help check
- Estimate runtime from entered Wh/load
- Calculate entered USB power profiles
Browser cannot prove
- Measure actual cell capacity/health without hardware instrumentation
- Read PD profiles generically
- Certify battery safety
Repair boundary
Know when to stop browser troubleshooting
- Do not flash unofficial firmware to fix an input symptom.
- Browser polling estimates are not kernel-level USB analyzers.
- Cleaning/disassembly methods vary by manufacturer and switch design.
Used-device inspection
What to verify before paying or signing off a repair
- Every key/button and repeated-press behavior
- Stick/axis center, full range and dead zones where applicable
- Wireless receiver/Bluetooth plus wired mode if supported