RetroArch Android Controller Not Working / No Sound Fix 2026

fix-controller-not-detected-autoconfig-and-reconnect (sortOrder=1, isMostHelpful)

RetroArch relies on "autoconfig" profiles to map controller buttons. Most popular controllers (Xbox, DualSense, DualShock 4, Switch Pro, 8BitDo) are in the bundled profile database. If your controller isn't working:

Step 1 — Force autoconfig to re-run:

1. Disconnect your controller (unpair Bluetooth, or unplug USB).
2. In RetroArch, go to Settings → Input → Auto-Configure Controllers: ON.
3. Reconnect your controller. RetroArch should show a pop-up: "[Controller Name] configured."
4. If no pop-up appears, your controller may not be in the profile database — proceed to manual mapping below.

Step 2 — Manual button mapping (if autoconfig didn't work):

1. Settings → Input → Port 1 Controls.
2. Press each button one at a time to map it. Press the RetroArch button, then press the physical button on your controller.
3. Map all buttons (A/B/X/Y, D-Pad, L/R triggers/bumpers, Start, Select/Share).
4. Save: Manage Remap Files → Save Core Remap File so the mapping persists.

Disable the on-screen touch overlay once your controller is working — it often intercepts touches and causes phantom inputs:

• Settings → On-Screen Display → On-Screen Overlay → Display Overlay: OFF

Bluetooth reconnect tip: if the controller disconnects mid-game and doesn't reconnect automatically, close RetroArch fully, reconnect the controller from Android's Bluetooth settings, then reopen RetroArch.

fix-no-sound-or-audio-crackling (sortOrder=2)

No sound at all:

• Go to Settings → Audio → Audio Enable: ON. It defaults to on, but can be toggled accidentally.
• Check Audio Driver: Settings → Drivers → Audio Driver. Try AAudio (Android 8+ preferred) or OpenSL ES (older devices). Switch between them and restart RetroArch.
• Confirm Android's media volume is up — RetroArch uses the Media audio stream, not the Ringer stream.

Audio crackling / stuttering:

• Settings → Audio → Audio Latency (ms): increase this from the default. Try 128ms → 192ms → 256ms. Higher latency buffers more audio ahead, eliminating crackles at the cost of slight sync delay. Most users find 128–192ms unnoticeable.
• Audio Resampling Quality: lower it to Sinc (Lowest) if crackling persists — this reduces CPU load on the audio thread.
• Threaded Video: try toggling Settings → Video → Threaded Video. On some Android devices, keeping video on the same thread as audio eliminates crackling; on others, threading helps. Test both states.

core-specific-button-layout-problems (sortOrder=3)

Some cores use button layouts that don't match your controller's physical labels — especially SNES cores on Xbox-style controllers (where the B button on a SNES controller is the East face button, opposite to the South face button labeled B on Xbox controllers).

Fix: use a core remap file per system.

1. Load a game with the core.
2. Open the Quick Menu (swipe from the left edge, or press the Menu button on your controller).
3. Go to Controls → Manage Remap Files → Save Core Remap File.
4. Now in Controls, remap individual buttons for this core only. These remaps override the global layout without affecting other cores.

Common core remaps needed:

• SNES cores (Snes9x, bsnes): swap A↔B and X↔Y on Xbox-style controllers to match Nintendo layout expectations.
• Genesis/Mega Drive (Genesis Plus GX): map A→L, B→Y, C→B (or per your preference) for the 3-button layout.
• N64 (Mupen64Plus-Next): Z-trigger often maps oddly; remap to Left Trigger or a shoulder button that feels natural.

video-driver-and-performance-issues (sortOrder=4)

RetroArch crashes on launch or shows a blank screen:

• Go to Settings → Drivers → Video Driver. Try Vulkan → if broken → OpenGL → if broken → GLCore. Each restart after switching drivers applies the change.
• After changing video driver, delete the RetroArch shader cache if you had shaders active: Main Menu → Load Shader Preset → clear any active preset. Shader presets compiled for one driver don't work with another and cause blank screens.

Games run slow despite a capable phone:

• Enable Settings → Frame Throttle → Fast-Forward Rate is NOT the speed issue — check the actual emulation speed: Settings → On-Screen Display → On-Screen Notifications → Display Frame Count: ON. If FPS is the right number (e.g., 60 for SNES) and it still feels slow, the issue is input lag, not emulation speed — lower audio latency and enable Hard GPU Sync in video settings.
• Per-core CPU usage: some cores (e.g., Mupen64Plus-Next for N64) are very demanding. On mid-range devices, use a lighter core alternative — ParaLLEl-N64 vs Mupen64Plus-Next, or Mesen vs bsnes-hd for NES/SNES.