![]() ![]() I haven't tried it on RPiOS-Lite, but I imagine it would be a different experience (no GUI or Pulseaudio). ![]() So to answer your question, yes, Bluetooth on the new RPi4 works (great, actually, since the December update with Pulseaudio, as BT audio was much more limiting with ALSA). I just paired the keyboard from the GUI like I had previously done with the speakers (although with speakers you also have to select it as the audio output device, the keyboard just works). There are other media control keys that didn't work with Audacious, but they did work with VLC (play, pause, skip, etc.), so that seems to be a software specific issue with Audacious. The Windows key opened the RPiOS menu, and other keys like Home, End and Page Up/Down all worked as expected. Tried some of the extra functions on the keyboard, like volume control, and screen scrolling by drawing a circle around the track-pad, and those worked as well. While listening to music in Audacious I launched Chromium browser and clicked on a YouTube video, and that worked as well (I had sound from Audacious and YouTube playing simultaneously from my Bluetooth speakers). I had previously paired my Bluetooth speakers and was playing sound out of those. I just tried pairing my 4B2 running RPiOS Buster with desktop to a Bluetooth keyboard with trackpad and had no trouble at all (the keyboard and trackpad worked as expected). I do have an Bluez error message like "no route to host" I can see the devices, pair them, but then can't connect them. Well, i've spent two days looking for solution on google, and most of the time, it seems that bluetoothctl is the main tool to pair / connect bluetooth device with the RPI.Īlso, i quite sure that i need to connect the device, because even if the PS4 controler and the keyboard are both listed avec "Paired-devices", they both does the same things when not beeing connected to the RPI : not workingĮDIT : Also, using RPI desktop frontend app doesn't help. What makes you think you need to connect to a device with bluetoothctl? Bluetoothctl is almost always the wrong thing to use to make a Bluetooth connection. Device F4:93:9F:C9:27:35 Connected: noįrom your transcript, the Bluetooth on your Pi seems to be operating normally. Bluetooth: RFCOMM socket layer $ sudo bluetoothctl Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: HCI UART protocol Broadcom registered Bluetooth: HCI UART protocol Three-wire (H5) registered Bluetooth: HCI UART protocol H4 registered Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized Manufacturer: Cypress Semiconductor Corporation $ rfkillġ bluetooth hci0 unblocked $ dmesg | grep Blue Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 ![]() TX bytes:7304 acl:9 sco:0 commands:380 errors:0įeatures: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 ![]() Is it an hardware issue and should i send back the RPI4 ?īD Address: B8:27:EB:D6:4D:70 ACL MTU: 1021:8 SCO MTU: 64:1 Here are the logs from the last installation, full RPI os.ĭoes any one can actually connect to bluetooth keyboard or gaming controlers ? i haven't been able to get any of those both connected to the RPI4.Īlso, i've tried on Dietpi, Raspberry Pi OS Lite (with out desktop), and the "full" version with desktop and recommended applications.Įach time the OS was a fresh installation and apt update & upgrade & reboot done before trying to connect to BT. I've just received and brand new RPI4, and i'm trying to get Bluetooth work in order to connect a keyboard and a PS4 controler.īut, for now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |