[claytonbeaubien]

This saved my life. Everything is working perfect. I can let controllers go idle and recconect. I dont have to run a shell script to get the second controller working. I am using 2 8bitdo SNES30 controllers. RetroPie v3.2.1

followed this first:

https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller

made sure to do STEP 3:

got my two controllers connecting seperately, but not at the same time until i did this:

The following will keep bluetooth on to keep scanning for the controllers.
sudo nano /etc/rc.local
add “sudo hciconfig hci0 up piscan” (without the quotes)
above the line that says “exit 0”
ctrl x
y
enter
sudo reboot

wait till emulation station loads, and connect away

WOOO!

Hope this helps others too

[claytonbeaubien]

good call, i guess i never thought of that cause i havent had to run as sudo before
i have been having better success running scraper as

sudo scraper thumb_only

plus i make sure, when i do it from winSCP that my pi is not in emulation station.

this seems to work for me for now.

[claytonbeaubien]

Scraper V1.0.4
RetroPie V3.2.1

I get the same issue.

Images end up in each different system folder with a gamelist that is almost blank, just says:

<?xml version=”1.0″?>
<gameList />

I took the time to organize all my roms into folders by name. I am doing up a few of these retro pies for friends. The first few i made didnt have this issue. Games were all in folders and scraping worked fine. Now all of a sudden it doesn’t want to work.

Ive tried scraping from different locations. Doing them all at once, doing a folder at a time. Nothing seems to work for me.

maybe master scraper SSELPH can help???

[claytonbeaubien]

i have opened the splash screen menu from the retropie menu in emulationstation and from the setup script, but i still have no Splashscreen folder… ?

[claytonbeaubien]

i spent a few days frustrated, finally got this to work. The main thing i had to do was uninstall sixad (a previous bluetooth service i had installed for my ps3 controller) after that i followed this forum, just over half way down is a post by Grizzlema, he explains everything thouroughly and also attached config files, i used those config files to replace my existing ones and my controllers now work in every emulator… now to play some friggin games

The old story… setting up 2x 8BitDo NES30 Bluetooth

[claytonbeaubien]

I got my controller to finally connect. I had installed Sixad previously to use my ps3 controller and i guess it was interfering.

I uninstalled Sixad:

sudo apt-get –purge remove sixad

the error went away, and i connected.

I dont have full functionality out of the controller yet, sure i have to play with some config files, but its a start, i will edit the post if i get further.

[claytonbeaubien]

I run into the same issue as Alpine (above). I am trying to connect a Snes30 Controller. It identifies my controller in hcitool scan but when i go to the next step i get the error:

pi@retropie ~ $ hcitool scan
Scanning …
01:06:86:6D:60:0F 8Bitdo SNES30 GamePad

pi@retropie ~ $ sudo bluez-simple-agent hci0 01:06:86:6D:60:0F

ERROR:dbus.proxies:Introspect error on :1.2:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File “/usr/bin/bluez-simple-agent”, line 102, in <module>
path = manager.FindAdapter(args[0])
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.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[Author]

Posts