Built-in controller not detected automatically after disconnecting external controller

[Ampaex]

Describe the Issue (If applicable)

The console does not respond to built-in controller when it is rebooted while having connected a bluetooth controller.
Seems like the console is not able to recognize that the bluetooth controller is not connected anymore.
Now it is happening to me that I cannot do anything, because the built-in controller is not working and the bluetooth controller is not connecting anymore.

How can the issue be reproduced? (If applicable)

1. Use the bluetooth manager to connect a controller
2. Start playing a game.
3. Shut down the console using the bluetooth controller.
4. Turn on the console and see that you cannot use any console control neither connect the bluetooth controller again.
   (In my case, after rebooting, it returns to where I left it before)

What device are you using?

RG353V transparent black

What version of ArkOS are you on?

Arkos v2.0 (10/25/2024) Update

Anything else you'd like to include that may help to review this issue or feature request?

This happened using retroarch while running rumble_mGBA core.

[christianhaitian]

You shutdown the unit in the middle of gaming? How did you shut the unit down? Describe the steps you took.

[Ampaex]

I think that retroarch controller settings are not updating automatically.

1. When you connect a bluetooth controller it starts acting as player 1, then you can play nice.
2. Afterwards, you have to shutdown the console without disconnecting the controller with just a quick tap in the power button(I have quick mode enabled).
3. Then, booting again results in player 1 being the (missing) bluetooth controller, built-in is disabled, and at least I did not managed to connect the bluetooth controller again(even pressing fn + R3).

[Ampaex]

I had to connect a wired keyboard to recover control over retroarch because it was not responding. In emulation station the built-in was working fine.
The problem it is just you cannot close retroarch at all if you don't have an appropriate configured controller for it.
Maybe a workaround could be adding a button combination at OS level allowing always the built-in controller to exit retroarch no matter the player controller config.

[gabuzom]

I encountered this issue as well. I thought it was maybe because I saved some retroarch configuration including the external controller as port1... but the same happened to me. Some hotkey shortcuts in retroarch still worked from external controller (to quit for instance), but up/down and other basic keys had stopped fundtioning.

It is really crippling.. it's the 2nd time that i wipe retroarch configuration from emulation station and start over again, only to find i am in this stuck situation where no controller (built in or external) can navigate in retroarch :/

[gabuzom]

Doing some very superficial research, it turns out that after saving my retroarch configuration where external controller was port1, and internal controller was port2, the file i find in:

/home/ark/.config/retroarch/retroarch.cfg

contains the following:

input_device_p1 = "0"
...
input_device_p2 = "0"

along with:
input_player1_left = "nul"
input_player1_left_axis = "nul"
input_player1_left_btn = "nul"
etc.

which doesnt sound right and may be part of the problem?

it seems to me that when shuffling around config files something may have gotten wrong. will try to restore a backup config file and see whatup.

[gabuzom]

hmm... i cannot seem to find any backup file where those settings look different... so maybe it's not where the problem comes from, but it def. feels like retroarch.cfg got somehow messed up, or interfered with...