How to Test a Controller on Android (Bluetooth & USB)

You can test a controller properly on an Android phone or tablet without installing anything. The browser reads your controller directly, which means you can check sticks, buttons, triggers, and drift on the same device you're gaming on.

That's genuinely useful, because most controller problems on Android aren't hardware faults at all — they're pairing or app-support issues that a two-minute test will identify immediately.

How to test a controller on Android

Connect the controller, open a browser test page, and press a button to wake it. Android exposes controllers to Chrome through the same Gamepad API that desktop browsers use, so you get live readouts of every stick position and button press without an app.

The steps:

1. Connect the controller by Bluetooth or USB (both covered below).
2. Open Chrome — this matters, since browser support varies and Chrome is the most reliable on Android.
3. Go to a controller test page, such as the button test.
4. Press any button. Browsers don't expose a gamepad until it sends input, so if nothing appears, press something first.
5. Work through each input and watch what registers.

If the test page responds, your controller and its connection are working, and any problem you're having is in a specific game or app rather than the hardware.

Connecting by Bluetooth

Most modern controllers pair with Android over standard Bluetooth. The pairing combination differs per controller:

Xbox controller: hold the small pair button on the top edge near the USB port until the Xbox button flashes rapidly. Note that older Xbox One controllers using Microsoft's proprietary wireless protocol rather than Bluetooth cannot pair with a phone — only Bluetooth-capable models (later Xbox One revisions and all Series X|S pads) will appear.

PS5 DualSense: turn it fully off, then hold the PS button and Create button together until the light bar flashes rapidly.

PS4 DualShock 4: hold Share and the PS button together until the light bar flashes.

Switch Pro Controller: hold the small sync button on the top edge until the player lights scroll.

Then open Android's Settings → Connected devices → Pair new device and select the controller.

One thing that catches people out: a controller can only hold one active Bluetooth connection. If yours is still connected to a console, it will keep trying to reconnect there. Turn the console off or disconnect the controller from it first.

Connecting by USB

USB is more reliable than Bluetooth for testing and gives lower latency for play. You'll need a USB-C cable that carries data, not just power — this is the single most common reason a controller appears not to connect. Many USB-C cables are charge-only, so the controller charges while Android never registers it as an input device.

Depending on your controller and phone, you may need a USB-C to USB-A adapter (an OTG adapter). Most modern phones support this natively.

If the controller connects over USB but not Bluetooth, or vice versa, that tells you something useful: the hardware is fine and the problem is with one specific connection method.

Android controller test: reading your results

Here's what to check and what each result means.

Sticks. Release both sticks completely and rest the phone on a surface. A healthy stick reads at or very near centre. An off-centre or wandering reading means drift. Run a stick drift test for a clearer readout, and note the value — a recorded baseline is what lets you spot degradation later.

Buttons. Press each one and confirm it registers once and releases cleanly. A button showing as pressed while you're not touching it means a stuck button or contaminated contacts. A button registering twice from one press is switch wear.

Triggers. Pull each slowly from released to fully pressed. The value should climb smoothly and return cleanly to zero. A trigger reading non-zero at rest, or not reaching maximum, has a mechanical problem.

D-pad. Test each direction individually, then the diagonals.

Check controller Android: what Android actually exposes

Android's controller support is good but not identical to a console's, and knowing the limits saves you from misdiagnosing.

FeatureWorks on Android?Sticks and buttonsYesAnalog triggersUsuallyD-padYesRumbleSometimesAdaptive triggersNoAdvanced hapticsNoGyroApp-dependent

Rumble support varies by controller, Android version and app. If vibration doesn't work in a browser test, that's often the browser rather than the controller — try a game that supports rumble before concluding the motors are dead.

Adaptive triggers and DualSense haptics don't work on Android. Those are PlayStation-specific features requiring the console's implementation, so their absence isn't a fault.

Gyro depends entirely on the individual app.

Gamepad tester Android: fixing a pad that connects but doesn't respond

This is the most common Android controller complaint, and it's usually not the controller.

Test in the browser first. If a browser test page registers your inputs, the controller and connection are fine, and the problem is app-specific.

The game may not support controllers. Many Android games are touch-only, and no amount of pairing changes that. Check the game's listing or settings for controller support before troubleshooting hardware.

The game may need controller support enabled. Some titles have a toggle buried in their settings.

Try relaunching the game with the controller already connected. Many apps only scan for controllers at startup.

Check for a mapping app conflict. If you have a controller-mapping app installed, it may be intercepting input. Close it and retest.

Some games restrict controllers deliberately. Competitive mobile titles sometimes block or limit controller input to preserve input parity. That's a policy decision, not a bug.

Common problems and fixes

Controller won't pair at all. Confirm it's not still connected to a console. Confirm it's a Bluetooth-capable model — this trips up Xbox One owners specifically. Remove any old pairing from Android's Bluetooth list and pair fresh rather than reconnecting.

Connects then disconnects. Usually battery or interference. Charge the controller fully, move away from Wi-Fi routers and other 2.4GHz devices, and keep a clear line of sight.

Buttons mapped wrongly. Common with Switch controllers on Android, since their layout differs from what most apps assume. A mapping app can correct it, or use an Xbox controller, which most Android games assume by default.

Works in some apps, not others. That's app-level support, not a hardware fault. The browser test confirms it.

Nothing registers even in the browser. Check the cable is data-capable, try the other connection method, and try Chrome specifically.

Why test on Android at all?

Three genuinely useful reasons.

You game on your phone. Cloud gaming and mobile titles are a real use case, and a controller that drifts costs you the same way it does on console.

It's the most convenient tester you own. Your phone is always to hand. Testing a controller takes two minutes and needs no computer.

Test before the return window closes. If you've bought a controller for mobile gaming, confirm every input works in the first week. Budget controllers have wider quality variance, and a dead button is far easier to deal with on day three than on day forty.

The short version

Android reads controllers through the browser's Gamepad API, so you can test sticks, buttons and triggers on your phone without installing anything — connect the controller, open Chrome, load a test page, and press a button to wake it. Pair over Bluetooth using your controller's specific combination, remembering that a pad still connected to a console won't connect to your phone, and that older Xbox One controllers using Microsoft's proprietary wireless can't pair at all. USB is more reliable but needs a data-capable cable. And if the browser test registers your inputs but a game doesn't, the problem is that app's controller support rather than your hardware.