Recently, after having my sixaxis time out I am not able to reconnect it by pressing the PS button. Earlier (few months back) this was possible..
When doing hciconfig I get bluetooth “UP RUNNING” but no pscan. After a reboot “UP RUNNING PSCAN” and my sixaxis will pair no problem.
After “breaking” I can manually do hciconfig hci0 pscan via ssh and the controller will pair again. But this is obviously more involved than I would like.. I prefer to keep the pi on 24/7 so turning off after every game isnt viable.. Anyone know how to make this work?
Same probem on my setup. After PS3 controller has been connected first time after boot – PSCAN is suddenly disabled.
Once I run “hciconfig hci0 pscan” – it starts to work again (PS3 controller is able to reconnect after being disconnected) until next reboot.
I made a hack to workaround this problem by adding the same command to the end of sixad-sixaxis.cpp main function
system(“hciconfig hci0 pscan”);
I noticed this behavior with recent builds of blueZ. you probably should think about removing qtsixa and use native support of ps3 controller in recent blueZ (i don’t have a tutorial for raspbian, but this tutorial for gentoo probably can help you)
Necessary and Functional
These cookies are placed to make it possible to analyze this website (with Google Analytics) and optimize for the purpose of a.o. the usability.
Cookie names: _ga, _gat, _gid
These cookies are placed to show advertisements (of Google AdSense) and to get these close to your interest.
Cookie names: id, IDE, FLC, DSID, SNID, NID
These cookies are required to show the cookie notification bar, remember your cookie acceptance choice and apply this choice.
Cookie names: privacy_embeds, wpca_consent, woocommerce_cart_hash, woocommerce_items_in_cart, wp_woocommerce_session_, wp-settings-1, wp-settings-time-1