How to Connect a Bluetooth Controller to Android (2026)

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Pairing a Bluetooth controller to Android is quick once the controller is in the right input mode, and the mode is where most attempts fail. A pad that shows up in Android's Bluetooth list but does nothing in a game has usually connected in Switch mode instead of an Android or DInput mode, or the game itself only accepts touch. If you are still choosing hardware, the roundup of the best game controllers for phones on Android and iPhone separates the models that actually use Bluetooth on Android from the ones that only mount over USB-C.

The sequence that works: set the controller's mode, hold its pairing button, scan from Android's Bluetooth menu, select the advertised device name, then confirm the steady light before you open a game. Skipping the mode step is what turns a two-minute job into an afternoon of forgetting and re-pairing the same device.

Android only promises that the operating system sees your controller. Whether a game responds is decided by the game. That split between system-level pairing and app-level support explains most of the failure cases further down.

As an Amazon Associate, I earn from qualifying purchases.

What You'll Need

• A controller with an Android-compatible Bluetooth mode, or a USB-C or 2.4 GHz alternative if it has none
• Android 9 or newer, and Android 12 or newer if you plan to use a DualSense or activate a screen mapper
• A charged controller, since a low battery causes failed pairing and mid-session drops
• The exact model name or number printed on the underside of the controller
• A data-capable USB-C cable for firmware updates or for testing the pad wired
• An OTG adapter or hub if you want to try a 2.4 GHz receiver on a phone

Before You Start: Three Decisions, Not One

Three separate things decide whether a controller works on Android, and they are independent of each other.

The first is transport. Bluetooth, a USB-C cable and a 2.4 GHz receiver are three different physical paths, and a controller that supports one does not automatically support the others. The second is input mode. Some pads expose an Android or DInput profile, an XInput profile, a Switch profile and a keyboard profile, and the one you select changes both the identity Android sees and the button order a game receives. The third is game support, which lives entirely inside the app and has nothing to do with how cleanly the pairing went.

Android has supported game controllers since API level 9, and apps receive controller input as KeyEvent and MotionEvent data rather than through a console-style driver. Multiple controllers get distinct input-device IDs on the Android side, which matters later if you want local multiplayer. Most troubleshooting collapses these three layers into one, which is why "paired but not working" has so many different causes.

Step 1: Set the Controller's Android Input Mode

This is the step people skip, and it is the one that decides everything after it. Mode is set differently depending on the pad: a rear slider on most 8BitDo models, a button combination before power-on on the GameSir Nova Lite and the Nintendo Switch Pro Controller, and nothing at all on Xbox and PlayStation pads, which have no mode selector.

Turn the controller fully off before changing mode. Android can store each mode as a separate device identity, so if the buttons or sticks behave strangely after a mode change, forget the device in Bluetooth settings and pair it again from scratch.

Step 2: Put the Controller in Pairing Mode

Exact buttons and light behaviour differ by model. The signal to watch is a rapidly flashing light, which means discovery is active, and a steady light, which means the bond is established. Match your controller to the row below rather than guessing.

Two details are easy to miss. On current Xbox firmware, a double-press of the Pair button switches between a remembered Xbox and a remembered Bluetooth host, while a long hold starts a brand-new pairing. On Genshin Impact and similar ports, the device name Android shows is generic, so "Wireless Controller" in your list is the DualSense or DualShock 4, not an error.

Step 3: Pair It From Android's Bluetooth Menu

Once the controller is advertising, open the Bluetooth scan and select the name from the table above. Menu wording differs by manufacturer, and telling someone on One UI to look for "Connected devices" is a reliable way to lose them.

Accept the pairing prompt when Android shows it, then wait for the controller light to stop flashing. If the device appears and then vanishes before you can select it, the pairing window closed. Hold the pairing combo again and select the name in the same attempt.

Which Controllers Pair Most Cleanly on Android

Three configurations account for the fewest support questions, mostly because they remove choices that can be made wrongly.

• Xbox Wireless Controller: no mode selector, one pairing button, and a device name Android recognises consistently. Check the Xbox Wireless Controller on Amazon
• DualSense: the cleanest PlayStation-side pairing on Android 12 and up, with multi-device slots once the firmware is current. Check the DualSense on Amazon
• 8BitDo Pro 2: the D position on the mode slider makes the Android profile an explicit choice instead of a guess. Check the 8BitDo Pro 2 on Amazon

The 8BitDo lineup guide covers the mode sliders across the family, and the GameSir model breakdown covers the wired and wireless branches that get confused with each other.

Two 8BitDo warnings are worth stating plainly. The original 8BitDo Ultimate Bluetooth Controller is officially for Switch, Windows and SteamOS, and its Bluetooth path is specified for Switch rather than Android. Do not merge it with the Ultimate 2, Ultimate 2C or regional variants, because each of those has its own compatibility list. The 8BitDo Micro has no analog sticks, so it suits turn-based games, shortcuts, tablets and accessibility setups rather than stick-driven action games, and older units should be on firmware 1.05 or later, which addressed Bluetooth sleep behaviour and DInput delay.

Step 4: Confirm the Connection Before You Open a Game

A steady light proves the bond, not the input. Test in this order:

• Move each stick through its full range and check that it reports a smooth arc rather than jumping. Small offset at centre is normal and is what deadzone settings exist for.
• Press every face button and shoulder input, and check the button labels Android reports. Reversed A/B or X/Y almost always means the controller is in Switch mode.
• Pull each trigger slowly. A trigger that reads as on or off is digital, which is expected on microswitch trigger modes and on hair-trigger settings.
• Press Home and see what Android does with it. On some TV builds and handhelds it opens a system overlay, which is normal behaviour rather than a fault.
• If the game you want is not installed yet, open a known native title first. Testing against a touch-only game tells you nothing about the pairing.

On Android 17, the controller's Game Controller settings let you swap any two buttons or the left and right sticks, and wired controllers also appear under Settings > System > Game controllers. That swapping is a system-level remap. It does not convert a touch-only game into a native one, so treat it as a fix for a wrong glyph rather than a compatibility fix.

Step 5: Switch the Game Itself to Controller Input

This is where most "it paired but nothing happens" reports end, and it has nothing to do with Bluetooth. Android exposes controller events to apps, and the app decides whether to read them.

Games with native controller handling consume those events directly. The list includes Minecraft, Dead Cells, Stardew Valley, GRID Autosport, Roblox, Fortnite, Call of Duty: Mobile, Diablo Immortal, Brawlhalla, Terraria, Vampire Survivors, Asphalt Legends Unite and TMNT: Shredder's Revenge, alongside most console ports. For a deeper look at how input layers behave on the shooter side, the Call of Duty: Mobile controller guide walks through the in-game support path, and the Fortnite controller picks cover what competitive players assign to rear inputs.

Two cases need a manual toggle rather than a pairing fix. Genshin Impact added native Android controller support in version 5.5 in March 2025, so older advice calling it iOS-only is out of date. Zenless Zone Zero supports controllers but may require you to select its Controller or Input option in the UI. If a game has a Control Type or Input setting, it needs to be on Controller, not Touch.

Native Controller Support vs Touch Mapping

A touch-only game can sometimes be played with a pad through a screen mapper. The mapper injects taps, holds and swipes through an accessibility service, wireless debugging or a helper on a PC, and it produces virtual touch events rather than gamepad API input. Analog sticks become directional swipes. There is no true analog response to gain, and game terms or anti-cheat systems may prohibit mapping outright.

If a game refuses controller input and you want to stay clearly inside the rules, the honest options are touch controls or a different title. Screen mapping is a workaround with a policy risk attached, and it is worth checking the game's terms before installing anything.

Controllers That Never Pair Over Bluetooth on Android

Several models that show up in Android controller searches are not Bluetooth devices at all. They are listed here because pairing steps are pointless for them, and because a shop listing is not a compatibility statement.

If you own one of these and it lights up but does nothing, the GameSir power and detection fixes cover cable, OTG and mode faults in that order. For the telescopic pads that clamp a phone, case thickness, connector alignment and OTG support cause more detection failures than software ever does.

Android Version Differences That Matter

Troubleshooting: Paired but Nothing Happens

For persistent analogue faults rather than pairing faults, the stick drift test and fix guide covers the diagnosis path, and hall effect sticks explains what contactless sensing does and does not solve. Neither sensor type removes the need for a sane in-game deadzone.

Multiple Controllers, Latency and What Bluetooth Cannot Fix

Android assigns each connected controller a distinct input-device ID, so four pads can sit connected at once. That does not make a game four-player: local multiplayer and player assignment are implemented by the app, not by the operating system. Emulators usually expose manual player and device assignment, which is why the retro and emulator controller guide treats emulator mapping as a separate topic from mobile game support.

On latency, no universal millisecond figure applies. A direct USB connection normally avoids radio scheduling and is the most consistent option. A well-implemented 2.4 GHz receiver can also be very consistent. Bluetooth varies with the controller's polling behaviour, the phone's radio, firmware, the game's frame rate, interference and power management, so a controller that feels fine on one handset can feel sluggish on another.

Two practical notes. A 2.4 GHz dongle is not Bluetooth and needs USB host support, so OTG has to be enabled and the adapter has to carry data. And controllers usually reconnect to the last host they bonded with, so if a pad keeps returning to a console or a tablet, turn Bluetooth off on that device or use the controller's remembered-device slots.

Common Mistakes to Avoid

• Pairing in Switch mode and then blaming the game. If A and B are reversed, the mode is wrong, not the pairing.
• Assuming a companion app proves Android gameplay support. Some mobile apps only configure the controller.
• Treating a wireless controller as Bluetooth by default. The Razer Wolverine V2 Pro is wireless through a proprietary dongle and is not an Android gamepad.
• Reading XInput as a transport. XInput is an input convention, not a radio, and plenty of Android dongle setups have no clean XInput path.
• Concluding that a game supports controllers because it works in an emulator. Emulators expose manual mapping that native mobile titles do not.
• Pairing four controllers and expecting four-player. The game has to implement it.
• Skipping the forget-and-re-pair step after a mode change. Android keeps each mode as its own device entry.
• Charging with a cable that carries power only, then wondering why a wired pad is never detected.
• Updating firmware without checking the exact model. Cross-flashing a revision is one of the few ways to turn a working controller into a paperweight, and the controller repair guide documents how often that turns into a hardware problem.
• Assuming low deadzone adds aim assist. It only accepts smaller physical stick movement sooner.

Conclusion

Bluetooth pairing on Android is the easy half. Set the controller's mode, hold the pairing combo, select the advertised name from the right menu path for your phone, and confirm the steady light. The hard half is remembering that Android and the game are two separate approvals, and that a pad living in Switch mode will pair perfectly and behave incorrectly.

Work through the layers in order: transport, mode, pairing, then the game's own input setting. Almost every problem in this guide resolves at the mode step or at the in-game Controller toggle, and neither one is fixed by pairing again.

For a controller that meets you halfway, the Xbox Wireless Controller has no mode selector to misread and one pairing button to hold. If you are still narrowing down hardware, start with the best game controllers for phones, check the Android TV and smart TV options if you split time between a phone and a television, and compare the phone-mount picks against your handset width before buying a telescopic model. Check the Xbox Wireless Controller on Amazon