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

    PI 3 + PS3 Bluetooth controller freeze fix. UPDATED

    Scheduled Pinned Locked Moved Help and Support
    43 Posts 16 Posters 27.9k 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.
    • J
      jmebd @glennlake
      last edited by jmebd

      @glennlake Fantastic! Thank you....I'll give that a shot when I get home from work afterwhile. I checked the date/time and it was incorrect so I went ahead and put the date/time module last night but I'd like for it to not be on there. I keep mine plugged in to ethernet just for kodi stuff so this will help greatly!

      Thanks everyone for their patience and help. I'm sure LOTS will benefit from just this one thread itself.

      p.s. I got my PS3 controller transferred back to onboard bluetooth after the update last night but didn't get a lot of time to play with it but in the 30 minutes I did....worked fine. Anyone else experiences thus far?

      1 Reply Last reply Reply Quote 0
      • J
        Jona1975
        last edited by

        Trying now.. 30 good minutes without any freeze, that's a record! :) Will let the pi on for a while running a Mame game....

        1 Reply Last reply Reply Quote 0
        • J
          Jona1975
          last edited by

          After some hours still running fine, and no new problem has appeared. :)

          1 Reply Last reply Reply Quote 0
          • O
            opensourcefan
            last edited by

            pi3, 3.7, updated to kernel 4.4, ps3 wireless

            I've been using the shutdown system through the menu to turn off the system. I have to unplug it and can't leave it on for the time being.

            I performed the update as per the first post including the certificate command (curl error).

            Immediately after this update, when I use the shutdown command and unplug the pi, it won't boot upon re-plugging it in. It either crashes and stays black or I get a bunch of timeout messages on the screen. If I unplug without using the shutdown command it boots up just fine. If I unplug during the crash and re-plug it boots fine.

            What log info can I provide to help with this and does this need it's own thread even though I believe it's related to the kernel 4.4 update.

            RPI3, v 3.7 from SD Image, Last update, Bluetooth v1.0, Child-Friendly ES, 3 amp Power Supply, Case w/fan.

            1 Reply Last reply Reply Quote 1
            • T
              thorgim
              last edited by thorgim

              After I do the "sudo rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155" and it's doing the update thing, then after a bit, I get several errors, like:
              "gzip: stdin not in gzip format"
              "tar: Child returned status 1"
              "tar: error is not recoverable: exiting now"

              I'm doing this on my raspberry pi 3, Retropie 3.7.

              Any idea how to solve this?

              1 Reply Last reply Reply Quote 0
              • RascasR
                Rascas
                last edited by Rascas

                @opensourcefan I dont't know, I cannot reproduce it. Check /var/log/syslog.

                @thorgim reboot and try again.

                1 Reply Last reply Reply Quote 0
                • T
                  thorgim
                  last edited by

                  @Rascas It did the same thing again, but after I did a "sudo rpi-update", then it update the firmware to 4.4.9-v7, and it backup the 4.1.19-v7 with no errors at all. Seems it work better than the other option.

                  RascasR 1 Reply Last reply Reply Quote 0
                  • RascasR
                    Rascas @thorgim
                    last edited by Rascas

                    @thorgim rpi-update without the hash updates to the latest kernel version available, with the hash updates to the specific commit. Since that specific commit is already verified to work for many people, and later ones not, that was the reason to pick that specific commit.

                    EDIT: That is no longer needed. Kernel 4.4 is on Raspbian repo now, just update as normal:

                    sudo apt-get update && sudo apt-get dist-upgrade
                    
                    T 1 Reply Last reply Reply Quote 1
                    • T
                      thorgim @Rascas
                      last edited by

                      @Rascas Thanks

                      1 Reply Last reply Reply Quote 0
                      • RionR
                        Rion
                        last edited by

                        @Rascas Thank you!

                        FBNeo rom filtering
                        Mame2003 Arcade Bezels
                        Fba Arcade Bezels
                        Fba NeoGeo Bezels

                        1 Reply Last reply Reply Quote 0
                        • L
                          Lagorth
                          last edited by

                          pi3, 3.7, updated to kernel 4.4, ps3 wireless

                          I got my pi last month and was running retropie with the old kernel before and got everything running except for the random freezing problem. So I updated the kernel to 4.4 yesterday. Now it seems impossible for me to pair my ps3 wireless with my pi. Maybe I missed some important settings?

                          That's what I did:

                          'sudo apt-get install rpi-update'
                          'sudo rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155'
                          'sudo update-ca-certificates --fresh'

                          I also tried to use:

                          'sudo apt-get update && sudo apt-get dist-upgrade'

                          Still the controller is working with usb, only. Any suggestions what else I could try to get my bluetooth working again? (I'm quite new to all of this so it is hard to tell what's going wrong for me)

                          1 Reply Last reply Reply Quote 0
                          • O
                            opensourcefan
                            last edited by

                            I think this is a bug with the update itself. It may be killing the Bluetooth. Take a look at this thread https://retropie.org.uk/forum/topic/905/lost-ps3-bluetooth-after-updating-raspbian/9

                            RPI3, v 3.7 from SD Image, Last update, Bluetooth v1.0, Child-Friendly ES, 3 amp Power Supply, Case w/fan.

                            1 Reply Last reply Reply Quote 0
                            • E
                              eightbit
                              last edited by

                              I foresaw there being a BT issue in retropie when I saw the release notes for Raspian on Distrowatch yesterday from Simon Long:

                              "We've just released a new version of our Raspbian image with some (hopefully) useful features. When the Pi 3 launched back in February, we'd not had time to do much in terms of getting access to the new on-board Bluetooth hardware. There was a working software stack, but the UI was non-existent. I'd hoped to be able to use one of the existing Linux Bluetooth UIs, but on trying them all, none were really what I was looking for in terms of usability and integration with the look and feel of the desktop. I really didn't want to write one from scratch, but that ended up being what I did, which meant a fun few weeks trying to make head or tail of the mysteries of BlueZ and D-Bus. After a few false starts, I finally got something I felt was usable, and so there is now a Bluetooth plugin for the LXPanel taskbar."

                              So, the new bluetooth module does fix BT in LXDE...but apparently breaks in in Retropie. The short term solution is to downgrade it as stated in the previous post (although I have yet to confirm that...but I see no reason why it would not work) but again it is a short term solution. The solution is not to suppress the update but to fix the compatibility issue in Retropie. Hopefully we'll see a v3.8 with compatibility with the new BT module fixed so that we can enjoy the best of all worlds.

                              1 Reply Last reply Reply Quote 0
                              • E
                                eightbit
                                last edited by eightbit

                                After a dist-upgrade, do:

                                wget http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb

                                and

                                sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb

                                Reboot afterward. If hciconfig give you an output the bluetooth is working again.

                                This will downgrade the bluetooth module and allow the PS3 controller (and other BT devices) to work again. Best part is now that the kernel has been updated the freezing no longer exists. I have been using the PS3 controller all night without a freeze.

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

                                  what way can I check what version of the bluetooth module is installed from the commandline and also how to check if the bluetooth module is seeing the controller at commandline level?

                                  E 1 Reply Last reply Reply Quote 0
                                  • E
                                    eightbit @Wolfman100
                                    last edited by

                                    @Wolfman100

                                    If you download the pi-bluetooth_0.1.0_armhf.deb and do a sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb, you will get a warning that you are downgrading the file. You will then know you are running the newer version that is not working. You can allow the downgrade.

                                    I believe you can do an hcitool dev to show all on devices if I remember correctly. Don't quote me on that though...

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

                                      @eightbit Thanks for that info.I will have a look at that this evening.I am running RetroPie installed in OSMC and am wondering whether this is causing some kind of Bluetooth conflict between 'bluetoothctl' and 'sixpair'.

                                      I have a bluetooth keyboard which works flawlessly with this setup and also works within RetroPie.This leads me to believe that because this Bluetooth keyboard is working in RetroPie that RetroPie is using Bluetoothctl which OSMC is using rather than enabling SIxpair?

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

                                        I have tried the downgrade but encountered the following error:

                                        root@osmc://# sudo apt-get install rpi-update
                                        Reading package lists... Done
                                        Building dependency tree
                                        Reading state information... Done
                                        E: Unable to locate package rpi-update
                                        root@osmc://# wget http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
                                        --2016-05-16 12:04:03-- http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
                                        Resolving archive.raspberrypi.org (archive.raspberrypi.org)... 93.93.135.188, 93.93.128.133, 93.93.130.236, ...
                                        Connecting to archive.raspberrypi.org (archive.raspberrypi.org)|93.93.135.188|:80... connected.
                                        HTTP request sent, awaiting response... 200 OK
                                        Length: 3182 (3.1K) [application/x-debian-package]
                                        Saving to: ‘pi-bluetooth_0.1.0_armhf.deb’

                                        pi-bluetooth_0.1.0_ 100%[=====================>] 3.11K --.-KB/s in 0.001s

                                        2016-05-16 12:04:03 (2.75 MB/s) - ‘pi-bluetooth_0.1.0_armhf.deb’ saved [3182/3182]

                                        root@osmc://# sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
                                        Selecting previously unselected package pi-bluetooth.
                                        (Reading database ... 51347 files and directories currently installed.)
                                        Preparing to unpack pi-bluetooth_0.1.0_armhf.deb ...
                                        Unpacking pi-bluetooth (0.1.0) ...
                                        dpkg: dependency problems prevent configuration of pi-bluetooth:
                                        pi-bluetooth depends on bluez-firmware; however:
                                        Package bluez-firmware is not installed.

                                        dpkg: error processing package pi-bluetooth (--install):
                                        dependency problems - leaving unconfigured
                                        Errors were encountered while processing:
                                        pi-bluetooth
                                        root@osmc://#

                                        It says package bluez-firmware is not installed.It must be though otherwise I wouldn't be able to use my bluetooth keyboard right?!Could this be that I am doing it as a root user under OSMC?

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          smoothmalik
                                          last edited by

                                          ive literary tried every step in this thread and now my controller when i press to connect to BT connects and then the system freezes up right after ...Is there a legit clean way to get this thing working without a million different steps?

                                          RascasR 1 Reply Last reply Reply Quote 0
                                          • RascasR
                                            Rascas @smoothmalik
                                            last edited by Rascas

                                            @smoothmalik if you read the first post, you only need one step and it is to update and upgrade. It works for me so I cannot see why it wont work for others. I had already installed the package raspberrypi-sys-mods so check if you have that installed also.

                                            S 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.