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

    SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP

    Scheduled Pinned Locked Moved Help and Support
    255 Posts 33 Posters 219.3k 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.
    • luetzelL
      luetzel @Wolfman100
      last edited by luetzel

      @Wolfman100
      Are you sure that you correctly applied ALL patches for bluez? If not, try to download and install my
      patched version from github.
      Did you restart the bluetoohd/ reboot your pi after installation of bluez?

      Does LED1 light up?

      Can you post the output of 'dmesg' when your controller is connected via USB?

      Wolfman100W 1 Reply Last reply Reply Quote 0
      • Wolfman100W
        Wolfman100
        last edited by

        I'm pretty sure that all the patches were applied correctly...will double check

        1 Reply Last reply Reply Quote 0
        • Wolfman100W
          Wolfman100 @luetzel
          last edited by

          @luetzel

          Pastebin of dmesg output:

          http://pastebin.com/Lap42kFi

          and No LED 1 does not light up

          luetzelL 1 Reply Last reply Reply Quote 0
          • luetzelL
            luetzel
            last edited by

            ok, then you can try to check whats going on using 'sudo bluetoohctl'
            It should display all bluetooth devices:

            [NEW] Controller 00:1B:10:00:2A:EC raspi5 [default]
            [NEW] Device 01:B6:AD:7F:63:25 PLAYSTATION(R)3 Controller
            [NEW] Device 01:B6:52:85:63:25 PLAYSTATION(R)3 Controller
            [NEW] Device 20:73:AB:91:DD:6F Bluetooth V3.0 Keyboard

            with info 01:B6:AD:7F:63:25, I see:

            Device 01:B6:AD:7F:63:25
            Name: PLAYSTATION(R)3 Controller
            Alias: PLAYSTATION(R)3 Controller
            Class: 0x000540
            Icon: input-keyboard
            Paired: no
            Trusted: yes
            Blocked: no
            Connected: yes
            LegacyPairing: no
            UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
            Modalias: usb:v054Cp0268d0000

            check if your devices are 'trusted'

            Wolfman100W 1 Reply Last reply Reply Quote 0
            • luetzelL
              luetzel @Wolfman100
              last edited by

              @Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:

              @luetzel

              Pastebin of dmesg output:

              http://pastebin.com/Lap42kFi

              and No LED 1 does not light up

              Hmm, thats exactly the same vendor and product id on your controller. I'm pretty sure that you should be able to pair your controller with the patched bluez.

              Wolfman100W 1 Reply Last reply Reply Quote 0
              • Wolfman100W
                Wolfman100
                last edited by

                I think their was a problem with the patches downloading,have rebuilt bluez and double checked patches:

                root@osmc:/bluez-5.39/patches# ls
                bluez-01_add-obexd-policy.patch bluez-11_sixaxis-fix-PID-navigation-controller.patch
                bluez-02_obexd-use-system-bus.patch bluez-12_sixaxis-add-support-for-setting-SDP-record.patch
                bluez-03_storagedir.patch bluez-13_sixaxis-provide-dualshock-3-SDP-record.patch
                bluez-04_work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch bluez-14_sixaxis-remove-not-needed-checks.patch
                bluez-05-046d-c52b-Logitech-Inc.-Unifying-Receiver.patch bluez-15_sixaxis-fix-multi-line-comments-style.patch
                bluez-06-broadcom-fixes.patch bluez-20-sixaxis-autotrust.patch
                bluez-07-broadcom-dont-set-speed-before-loading.patch bluez-link_against_ncurses.patch
                root@osmc:/bluez-5.39/patches#

                1 Reply Last reply Reply Quote 0
                • Wolfman100W
                  Wolfman100 @luetzel
                  last edited by

                  @luetzel

                  have updated:

                  GNU nano 2.2.6 File: bluetooth.ver

                  {
                  global:
                  btd_;
                  g_dbus_
                  ;
                  info;
                  error;
                  debug;
                  baswap;
                  ba2str;
                  sdp_*;
                  local:
                  *;
                  };

                  luetzelL 1 Reply Last reply Reply Quote 0
                  • luetzelL
                    luetzel @Wolfman100
                    last edited by luetzel

                    @Wolfman100
                    ok, maybe you misunderstood. It is not sufficient to download the patches, you have to apply all of them with:

                    patch -p1 < patches/bluez-01_add-obexd-policy.patch

                    you have to do it for all files you downloaded. Then, do make/ make install again and restart the bluetoothd service.

                    In doubt, clone the patched bluez from my github repo:

                    git clone https://github.com/luetzel/bluez

                    and compile it on your machine.

                    Also check whether the bluez sixaxis plugin was correctly loaded. What does:

                    'sudo service bluetoothd status' say? Thats my output:

                    bluetooth.service - Bluetooth service
                    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
                    Active: active (running) since Mon 2016-05-16 20:47:11 CEST; 17h ago
                    Docs: man:bluetoothd(8)
                    Main PID: 472 (bluetoothd)
                    Status: "Running"
                    CGroup: /system.slice/bluetooth.service
                    └─472 /usr/libexec/bluetooth/bluetoothd

                    May 16 20:47:10 raspi5 bluetoothd[472]: Bluetooth daemon 5.39
                    May 16 20:47:11 raspi5 bluetoothd[472]: Starting SDP server
                    May 16 20:47:11 raspi5 systemd[1]: Started Bluetooth service.
                    May 16 20:47:12 raspi5 bluetoothd[472]: Bluetooth management interface 1.10 initialized
                    May 16 20:47:12 raspi5 bluetoothd[472]: Failed to obtain handles for "Service Changed" characteristic
                    May 17 07:44:01 raspi5 bluetoothd[472]: sixaxis: compatible device connected: PLAYSTATION(R)3 Controller (054C:0268)
                    May 17 09:22:13 raspi5 bluetoothd[472]: sixaxis: compatible device connected: PLAYSTATION(R)3 Controller (054C:0268)
                    May 17 09:22:23 raspi5 bluetoothd[472]: sixaxis: compatible device connected: PLAYSTATION(R)3 Controller (054C:0268)
                    May 17 13:45:07 raspi5 bluetoothd[472]: sixaxis: compatible device connected: PLAYSTATION(R)3 Controller (054C:0268)

                    1 Reply Last reply Reply Quote 1
                    • Wolfman100W
                      Wolfman100 @luetzel
                      last edited by

                      @luetzel said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:

                      sudo bluetoohctl

                      bluetoothctl does not see the controller:

                      root@osmc:/# sudo bluetoothctl
                      [NEW] Controller B8:27:EB:A1:9B:7F osmc [default]
                      [NEW] Device CC:C5:0A:1F:F9:2C Bluetooth 3.0 Macro Keyboard
                      [bluetooth]# scan on
                      Discovery started
                      [CHG] Controller B8:27:EB:A1:9B:7F Discovering: yes
                      [bluetooth]#

                      luetzelL 1 Reply Last reply Reply Quote 0
                      • Wolfman100W
                        Wolfman100
                        last edited by

                        result of 'sudo service bluetoothd status':

                        root@osmc:/# sudo service bluetoothd status
                        ● bluetoothd.service
                        Loaded: not-found (Reason: No such file or directory)
                        Active: inactive (dead)

                        luetzelL 1 Reply Last reply Reply Quote 0
                        • Wolfman100W
                          Wolfman100
                          last edited by

                          @luetzel

                          Apolagies,I was just following the guide as it is laid out,as a relative noob I didn't realise I had to manually apply the patches.

                          luetzelL 1 Reply Last reply Reply Quote 0
                          • luetzelL
                            luetzel @Wolfman100
                            last edited by

                            @Wolfman100
                            Hmm, it should be possible to see PS3 connection attempts even without having the
                            right bluez version.
                            You dongle should see the controller as soon as you press the PS button, given that it is not connected via USB.

                            1 Reply Last reply Reply Quote 1
                            • Wolfman100W
                              Wolfman100
                              last edited by

                              When attempting to apply the patches I get this output:

                              root@osmc:/bluez-5.39# patch -p1 < patches/bluez-01_add-obexd-policy.patch
                              patch: **** Only garbage was found in the patch input.

                              1 Reply Last reply Reply Quote 0
                              • luetzelL
                                luetzel @Wolfman100
                                last edited by

                                @Wolfman100
                                Ah ok, never mind ;-)

                                Wolfman100W 1 Reply Last reply Reply Quote 1
                                • luetzelL
                                  luetzel @Wolfman100
                                  last edited by

                                  @Wolfman100

                                  @Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:

                                  result of 'sudo service bluetoothd status':

                                  root@osmc:/# sudo service bluetoothd status
                                  ● bluetoothd.service
                                  Loaded: not-found (Reason: No such file or directory)
                                  Active: inactive (dead)

                                  Please try it again with:

                                  sudo service bluetooth status

                                  (my mistake, the 'd' at the end was wrong)

                                  1 Reply Last reply Reply Quote 1
                                  • Wolfman100W
                                    Wolfman100
                                    last edited by

                                    The really really weird thing is that somehow the Pi/OSMC is seeing the PS3 controller as I am currently watching the News streaming on OSMC and when I push the PS button on the PS3 controller after about 7 seconds it makes the stream temporarily freeze for a couple of seconds indicating that the pi is seeing it as this is repeatable every time I push the PS button!! V strange!

                                    luetzelL 1 Reply Last reply Reply Quote 0
                                    • Wolfman100W
                                      Wolfman100 @luetzel
                                      last edited by

                                      @luetzel ermmm...I'm confused.Is this what should happen when I apply the patch?

                                      1 Reply Last reply Reply Quote 0
                                      • Wolfman100W
                                        Wolfman100
                                        last edited by

                                        root@osmc:/# sudo service bluetooth status
                                        ● bluetooth.service - Bluetooth service
                                        Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
                                        Drop-In: /etc/systemd/system/bluetooth.service.d
                                        └─local.conf
                                        Active: active (running) since Tue 2016-05-17 00:28:47 BST; 13h ago
                                        Docs: man:bluetoothd(8)
                                        Main PID: 2072 (bluetoothd)
                                        Status: "Running"
                                        CGroup: /system.slice/bluetooth.service
                                        └─2072 /usr/libexec/bluetooth/bluetoothd

                                        May 17 00:28:47 osmc bluetoothd[2072]: Bluetooth daemon 5.38
                                        May 17 00:28:47 osmc bluetoothd[2072]: Starting SDP server
                                        May 17 00:28:48 osmc bluetoothd[2072]: Bluetooth management interface 1.10 initialized
                                        May 17 00:37:56 osmc bluetoothd[2072]: Failed to obtain handles for "Service Changed" characteristic

                                        Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.

                                        luetzelL 1 Reply Last reply Reply Quote 0
                                        • luetzelL
                                          luetzel @Wolfman100
                                          last edited by

                                          @Wolfman100
                                          I think it is related to the connection attempts, it fails to pair and disconnects again. You should
                                          be able to follow this process with 'sudo bluetoothctl'. After a failed connection attempt you should
                                          see a 'disconnected' message for the controller.

                                          1 Reply Last reply Reply Quote 1
                                          • luetzelL
                                            luetzel @Wolfman100
                                            last edited by

                                            @Wolfman100
                                            Bluetooth daemon 5.38

                                            Version should be at 5.39 not 5.38! Did you forget to 'make install' or to reboot your Pi?

                                            Wolfman100W 1 Reply Last reply Reply Quote 1
                                            • 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.