RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    DESPERATE HELP NEEDED! HC-06 Bluetooth

    Scheduled Pinned Locked Moved Help and Support
    bluetooth4.4hc-06controller
    24 Posts 6 Posters 2.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Dinsdale
      last edited by

      https://www.amazon.co.uk/gp/aw/d/B009ZIILLI

      Just ordered that. Will try it at the weekend as I’m working away this week. Fingers crossed.

      On the subject, is this just a case of plugging it in and it’ll override the onboard Bluetooth of the 3B+, or will I need to run some commands?

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @Dinsdale
        last edited by

        @Dinsdale Although I don't think this would be any help, you can disable the onboard BT by modifying the /boot/config.txt file and adding dtoverlay=pi3-disable-bt on a line.

        D 1 Reply Last reply Reply Quote 1
        • D
          Dinsdale @mitu
          last edited by

          @mitu Perfect, I’ll try it anyway. Thanks!

          1 Reply Last reply Reply Quote 0
          • D
            Dinsdale
            last edited by

            So I disabled onboard Bluetooth, rebooted, and connected the new dongle. It flashes - but no change.

            Now this is most likely be because this dongle won’t be Plug n Play. How do I install it? There’s no instructions in the package for Linux.

            quicksilverQ S 2 Replies Last reply Reply Quote 0
            • quicksilverQ
              quicksilver @Dinsdale
              last edited by

              @Dinsdale I might have a fix for you! It would probably be best to restore things back to default with all the changes you have probably made. This fix should allow you to sync to the built-in bluetooth. (I recently found this fix while trying to help a friend snyc a bluetooth xbox one controller. The things we do for friends and family!)

              Create a new file using nano...

               sudo nano /etc/modprobe.d/bluetooth.conf
              

              Add a single line to the new file...

              options bluetooth disable_ertm=Y
              

              Exit nano, saving the file in the process

              This fixed my connection issues with the xbox one bluetooth controller

              1 Reply Last reply Reply Quote 1
              • D
                Dinsdale
                last edited by

                Thanks man! Unfortunately it didn’t work.

                1 Reply Last reply Reply Quote 0
                • S
                  steptoe @Dinsdale
                  last edited by

                  @Dinsdale said in DESPERATE HELP NEEDED! HC-06 Bluetooth:

                  So I disabled onboard Bluetooth, rebooted, and connected the new dongle. It flashes - but no change.

                  Now this is most likely be because this dongle won’t be Plug n Play. How do I install it? There’s no instructions in the package for Linux.

                  There isn't, at least not for the PI. Some work with the PI but some don't. They auto-install or are auto -detected

                  1 Reply Last reply Reply Quote 0
                  • D
                    Dinsdale
                    last edited by

                    Yeah, I think this one is Plug and Play. I see it in lsusb and it works when I search for Bluetooth devices, though to be honest, this could still be the onboard bluetooth that I haven't successfully disabled - because when I take the bluetooth dongle out, and search for new Bluetooth devices, it just hangs on "searching" and doesn't give me an error. Does this mean the Bluetooth is disabled?

                    Anyway, here's the error in full when I connect via onboard or the dongle. I have typed this out manually. Hope it gives someone a clue.

                    Traceback (most recent call last):
                    File "/usr/lib/python2.7/dist-packages/dbud/connection.py", line 604, in msg_reply_handler
                    reply_handler(*message.get.args_list(**get_args_opts))
                    File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply dev_connect(dev_path)
                    File "/home/pi/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect dev.Connect()
                    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
                    return self._proxy_method(*args, **keywords)
                    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
                     **keywords)
                    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
                    message, timeout)
                    dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available
                    
                    1 Reply Last reply Reply Quote 0
                    • D
                      Dinsdale
                      last edited by

                      I’ve been trying tonight to make some progress. I Google’d the above error and found a reply from @RadBrad87 in this thread: https://retropie.org.uk/forum/topic/1905/retropie-3-8-bluetooth-configure-issue/40

                      Exact same error... so I tried optimistically to remove the PS3 driver (I didn’t have it installed in the first place) and all associated packages... but still nothing.

                      I also noticed separately that I could enable the serial interface - and when I’ve Google’d the HC-06 a lot of references where made to this and SPP... but no dice. Same issue.

                      What the hell is it?!

                      1 Reply Last reply Reply Quote 0
                      • D
                        Dinsdale
                        last edited by

                        Does anyone know why it connects with RFCOMM and why it isn’t recognised as a controller?

                        1 Reply Last reply Reply Quote -1
                        • D
                          Dinsdale
                          last edited by Dinsdale

                          This is now resolved. The guy who did this further did some investigation and found that he needed to convert this to HID to work on Raspberry Pi and other platforms OOTB. He did this using an RN-42 I believe. Finally... works a charm!

                          So, on the off chance anyone has the same bizarre situation as me, this is what did it!

                          ByteThisB 1 Reply Last reply Reply Quote 0
                          • ByteThisB
                            ByteThis @Dinsdale
                            last edited by

                            @Dinsdale What is RN-42 ?

                            D 1 Reply Last reply Reply Quote 0
                            • D
                              Dinsdale @ByteThis
                              last edited by

                              @ByteThis Diffferent type of Bluetooth module, I believe. Could be wrong...

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post

                              Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                              Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.