Open duffpl opened 2 months ago
Can confirm this is happening on the RG35xx SP as well. Strangely, if I manage to pair anything within those few seconds, bluetooth seems to be working normally.
Same behaviour on the latest Knulli build with a RG35XX H and a SN30 Pro over Bluetooth. If the controller is in pairing mode as the device is turning on with Bluetooth enabled it appears in the device list but even then it will not pair properly and the device list eventually depopulates entirely.
This applies to Xinput mode, if Dinput mode is attempted to be paired with the same steps it will successfully pair without notification but as far as I'm aware this mode does not support rumble.
I have the same issue with my RG35xxH: I tested it with two different Bluetooth Controllers (one 8bitdo and one off-brand PS4 Controller). Both show up in the bluetooth menu when I disable Wifi but are not paired when I select them in the menu. After a few seconds they just vanish from the device list. Both Controllers work fine with other devices (I paired tzhem with myx android phone just to be sure). I even popped my Stock OS SD back into the H: Here both Controller paired normally and were useable.
Knulli build version
40-dev-d8b86623f3 2024/05/30 01:50
Your architecture
RG35XX Plus
Issue description
Bluetooth seems to be deactivating shortly after boot. When device is started BT devices show up in manual pairing screen but list becomes empty and no devices can be paired
Detailed reproduction steps
Details of any attempts to fix this yourself
I've looked into
/var/log/bluetooth-agent.log
and it seems that after booting controller is working as expectedHowever after launching
bluetoothctl
and usingshow
it looks like controller is unpoweredRunning
power on
results in error:Details of any modifications you have made to Knulli.
None
Logs and data
A bit more data from bluetooth-agent.log