Bluetooth stops working few seconds after boot

[duffpl]

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

1. Boot the device
2. Enter BT > manual pairing mode
3. Observe that list of found devices becomes empty after short while
4. Disable/Enable BT doesn't change anything

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 expected

2024-07-10 00:31:19,984 agent registered
2024-07-10 00:31:24,996 adapter found
2024-07-10 00:31:25,007 BlueZ 5.72(68:8F:C9:13:CB:28), powered=1
2024-07-10 00:31:25,008 signals set

However after launching bluetoothctl and using show it looks like controller is unpowered

Controller 68:8F:C9:13:CB:28 (public)
	Manufacturer: 0x005d (93)
	Version: 0x07 (7)
	Name: BlueZ 5.72
	Alias: BlueZ 5.72
	Class: 0x00000000 (0)
	Powered: no
[...]

Running power on results in error:

[bluetooth]# Failed to set power on: org.bluez.Error.Failed

Details of any modifications you have made to Knulli.

None

Logs and data

A bit more data from bluetooth-agent.log

2024-07-10 00:54:32,124 agent registered
2024-07-10 00:54:37,136 adapter found
2024-07-10 00:54:37,147 BlueZ 5.72(68:8F:C9:13:CB:28), powered=1
2024-07-10 00:54:37,148 signals set
2024-07-10 00:54:51,127 listing mode enabled
2024-07-10 00:54:51,128 Start discovery (signal)
2024-07-10 00:55:20,136 listing mode enabled
2024-07-10 00:55:58,304 agent registered
2024-07-10 01:09:59,796 agent registered
2024-07-10 01:24:04,847 agent registered
2024-07-10 01:24:09,860 adapter found
2024-07-10 01:24:09,870 BlueZ 5.72(68:8F:C9:13:CB:28), powered=0
2024-07-10 01:24:09,871 powering on adapter (68:8F:C9:13:CB:28)
2024-07-10 01:24:09,884 signals set

[n-a-z]

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.

[Syferus]

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.

[Dorifer]

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.

[xXDeonoXx]

same issue and same symptoms

[Harry989]

I also have the same issue, yet my controller refuses to connect during the period where the bluetooth service is working.

[radmand510]

exact same issue here also on my rg40xxh

[MiroslavGubenko]

Same problems on rg35xxH. A couple of ideas to check: I use a second SD card. Formatting in ext4 using Knulli.

[4a4ik]

Same problem Anbernic_RG32XX_SP, red transparent, should be V2. firefly 2024/12/04 03:10
2 SD cards. If I do it fast I can pair devices after reboot and bluetooth audio works.
Thanks @n-a-z I installed KNULLI only because I want bluetooth audio
There is another issue, I think with the same problem
Bluetooth is not working properly #65