Controller support broken, B button is back (exits app)

12-05-2018, 02:48 PM #1

I've tried several different builds of Dolphin (can't remember the specifics, three recent ones and one really old one) and several controllers (Xbox One S, 8bitdo N30 Pro, Moga Pro Power) but I can't get any of them to work with Dolphin. I can bind every single button perfectly except for the right face button, which is B on Xbox, A on Nintendo, Circle on PlayStation. Pressing this button no matter the controller will open the "Press back again to exit" prompt, and not perform any in-game action. Pressing the button again as you can probably guess exits the game. The controller appears to work perfectly fine with other games (I've only tested Sonic The Hedgehog Classic and the Steam Link app, but will test more) so this must be a problem with Dolphin specifically. I've been looking for days and have only found one other person with this issue that went unresolved. Are controllers untested on Dolphin for Android? Is this just an issue with later versions? Do people usually just use touch controls? You tell me.

My device is a Le Pro 3, the 6 GB RAM variant. It's running Lineage OS 15.1 Oreo. I've tried using several different keylayout files, but they didn't work.

**ExtremeDude2** · 12-05-2018, 11:54 PM #2

Check "Options" > "Hotkey Settings" and see if you have anything configured for "Stop".

12-06-2018, 12:16 PM #3

The "options" and "hotkey settings" menus don't seem to exist on Android, and under "controls" there are no emulator settings available, for example "stop", "reset", "disable emulation speed limit".

**ExtremeDude2** · 12-07-2018, 12:00 AM #4

oh, didn't see android (again), how are you connecting them to your phone? Does the same button close other apps?

12-07-2018, 12:21 AM #5

Connecting through Bluetooth, USB OTG doesn't seem to work. Controller works normally in apps with controller support, it's just apps that don't have controller support (and Dolphin) where the right face button works as back.

12-13-2018, 12:22 PM #6

I'm not sure what this forum's rules on bumps are (I checked but didn't see anything) but I felt that a solution deserves a post of it's own.

For years, I've always enabled the "hold back to kill app" feature in the developer settings. I've just always liked the idea of having an escape button if something hangs. But for some reason when this feature is enabled the Gamecube's X button, or Xbox's B button, or PlayStation's Circle button, or whatever button is on the right on the controller you're using will act like a second back button, and cause the aforementioned issue. Disabling this option in the developer settings solved this issue.

Aggro_hamtaro · 09-02-2019, 06:06 AM #7

I have gotten the same problem on my Samsung s10 since the latest update. The B button on my Xbox controller goes back or closes apps.
Unfortunately I can't find any option in the developer settings to disable this.

Scribblette · 09-03-2019, 01:51 PM #8

I'm using the custom build listed in the other thread. Once I've mapped all the controllers on my PS4 controller, pressing circle only behaves as intended in game. Not sure if that's due to a difference in the dolphin version or just due to the fact I mapped out the controls in Dolphin.

Aggro_hamtaro · 09-05-2019, 04:12 AM #9

It seems as if the global button mapping was causing this issue for me. If I map the button in each game it's working fine.

Polaris · 02-23-2021, 09:52 PM **#10**

(12-13-2018, 12:22 PM)krillme Wrote: I'm not sure what this forum's rules on bumps are (I checked but didn't see anything) but I felt that a solution deserves a post of it's own.

For years, I've always enabled the "hold back to kill app" feature in the developer settings. I've just always liked the idea of having an escape button if something hangs. But for some reason when this feature is enabled the Gamecube's X button, or Xbox's B button, or PlayStation's Circle button, or whatever button is on the right on the controller you're using will act like a second back button, and cause the aforementioned issue. Disabling this option in the developer settings solved this issue.

After a rebind, this did it.

I'm sorry for bumping a thread this old, but I've been looking for a solution to this for weeks, thank you very very much for this answer !