I did, from raspi-config. When logging into SSH it no longer states ‘rfkill currently blocking wifi!’ Is there another specific-to-wifi command I need to set for its locale?
The output from sudo service bluetooth status is now
May 12 20:40:36 raspberrypi bluetoothd[625]: Bluetooth management interface 1.18 initialized
May 12 20:40:36 raspberrypi bluetoothd[625]: Failed to set privacy: Rejected (0x0b)
May 12 20:40:36 raspberrypi bluetoothd[625]: Failed to set device class: Not Powered (0x0f)
Edit: I noticed this topic: Bluetooth issues with 8BitDo SN30pro on Rasp Pi 4 with Retropie - #7 by Richard154847 having a similar issue with Retropie, which lead to someone suggesting this older solution: Raspberry Pi 4 won't pair to bluetooth devices - Raspberry Pi Stack Exchange which delays the startup of the bluetooth service. I’ve tried editing the configuration file to do the same and now the output from sudo service bluetooth status is:
May 13 09:45:47 raspberrypi bluetoothd[718]: Bluetooth management interface 1.18 initialized
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to clear UUIDs: Busy (0x0a)
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to set mode: Busy (0x0a)
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to add UUID: Busy (0x0a)
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to add UUID: Busy (0x0a)
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to add UUID: Busy (0x0a)
May 13 09:45:47 raspberrypi bluetoothd[718]: Failed to set device class: Busy (0x0a)
Bluetooth scanning now appears to start
pi@raspberrypi:~ $ sudo hcitool scan
Scanning ...
however nothing ever appears…
