@mitu said in Speeding up retropie boot up on a Pi zero and turning off BT & WiFi..:

@MachLid One thing you can do to speed up the boot is to disable file shares (Samba services). From what I've noticed, this is one of the services that takes up a lot of time (proportional to the total boot time) to start up.
I've looked up in the RetroPie-Setup script and you only have the options to remove Samba completely (not disable it), so you'd have to use the command line to disable the services manually.

sudo systemctl disable smbd sudo systemctl disable nmbd

More ideas and help!! thank you very much, and I'm also going to try this as well.
I have no problem killing anything unnecessary on it in order to speed up booting into the game selection menu.
What I'm hoping to do with this Pi Zero is simply and only use it for mostly Atari 2600 stuff and maybe some popular arcade games from pre 1990's or earlier (if it'll handle it).
I grew up with a Atari 2600 and lots of this stuff thru out the 1980s,, and thought it'd be neat to have something very little and compact (and even battery powered) and be able to quickly power on, and play some of the true classics. Not sure what I'm doing yet for a compact and portable housing or anything like that yet,, I just wanted to square away the working parts first.

Thanks again.

@mitu Oooops, sorry about that. Will do!
Thanks

@rodrigoleao said in [SOLVED] 8bitdo and dualschock 3 at same time:

Is it happen with your setup too? I'm using the default bluetooth of raspberry pi 3.

Yes it happens a bit for me too sometimes. I have both, a Raspberry PI 3B and 3B+, and as @mitu says the bluetooth of the plus is way better (but not perfect) than the normal one.

Also make sure that the battery of the 8bitdo controller is charged, I found out that when it's about to get flat, it has a lot of latency/delays in response.

Good you sorted out your problem!

Excellent, thanks for the quick reply. I won't be able to do it tonight, but will get onto it tomorrow.

Cheers

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

No worries. I just wanted to help the community out!

Anyone! I’m really desperate to fix this.

@retroresolution

Hi RR, I had the exact same problem and it was driving me insane... thanks for figuring this out and sharing your solution!

Does anyone know if there is there any resolution to getting ALL of the buttons on this controller to work in ES? I'm disappointed that all of the buttons cannot be used. Originally I was attempting the macOS pairing and nothing would work (I read somewhere this is the best setting for retroarch. Cannot cite my current source because I forgot).

After two weeks of trial and error, I'm happier after reading this thread that I can use the Windows setting, but I often use the trigger buttons for load and save states (the shoulders are for ff and rewind). So full functionality is reduced for me.

@mitu It works just fine within EmulationStation, but once I start RetroArch everything freezes until I connect the USB controller.

Got it thanks again for all the help. I guess this brand is more commonly referred to as a shenwen controller and that's what the pi recognized it as.
After installing the PS3 drivers, I used this guide to help:
https://raspberrypi.stackexchange.com/questions/54522/retropie-ps3-controller-over-bluetooth/54630

I appreciate the help as I'm now able to play from the comfort of my couch, as opposed to a folding chair I had set up in front of the TV.

@WDW plug in a working controller and press start then exit emulationstation(takes you to command line).
type: sudo /home/pi/RetroPie-Setup/retropie_setup.sh (setup menu)
then go to config, then find bluetooth. (while youre here check 8bitdo hack is off). Next forget devices and reconnect one gamepad.
If it stays connected then:
run: jstest /dev/input/js0 (checks input of first controller device- press buttons)
If the previous works then you might have a problem with emulationstation or something thus i dont know how to fix.

If not then try the following:

sudo hciconfig hci0 reset

(resets bluetooth adapter)

sudo invoke-rc.d bluetooth restart

(then restart it)

sudo bluetoothctl

(open bluetooth commandline)

scan on

( start scanning)

output looks like this:

[CHG] Controller xx:xx:xx:xx:xx:xx Discovering: yes [NEW] Device xx:xx:xx:xx:xx:xx LAPTOP-4BNKAVN8 [NEW] Device E4:17:D8:A2:0C:72 8BitDo N30 Pro 2 [bluetooth]# pair E4:17:D8:A2:0C:72

(pair your mac address)
will output like this

Attempting to pair with E4:17:D8:A2:0C:72 [CHG] Device E4:17:D8:A2:0C:72 Connected: yes [CHG] Device E4:17:D8:A2:0C:72 Modalias: usb:v2DC8p2865d0100 [CHG] Device E4:17:D8:A2:0C:72 UUIDs: 00001124-0000-1000-8000-00805f9b34fb [CHG] Device E4:17:D8:A2:0C:72 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device E4:17:D8:A2:0C:72 ServicesResolved: yes [CHG] Device E4:17:D8:A2:0C:72 Paired: yes Pairing successful

(then trust it)

trust E4:17:D8:A2:0C:72

(then connect it)

connect xx:xx:xx:xx:xx

NOTE- change the address to yours.

...

@MosaicDragon The ps3driver - if installed - will disable the native OS Bluetooth stack, so you'll not be able to pair additional (non-PS3) controllers. This is the behavior you're seeing. I advise you to remove the ps3driver and install the sibling customhidsonly driver and try to pair any Bluetooth controllers you have (including the PS3 controller).

That's great to hear, since I didn't have any ideas left anymore myself.

Yeah, bluetooth pairing is one of the most annoying things about wireless controllers in computer tech that I know.

Thanks for posting your solution, albeit not exact instructions. :)

@PaddyPat You might want to disable the ps3 controller driver and use the customhidsonly driver instead (you'll have to re-configure the controllers again after switching drivers).
Traditionally, Blueooth problems can be alleviated by disabling the Wifi or using a dedicated USB Bluetooth dongle - but for the 3B+ that may no longer be necessary since the wireless chips is better.

So i followed the instruction to remove BT completly in the link above, moved mu stuff to another room and suddely both controllers connect and are recognised in ES :)

@MalachiConstant You'll need to use SSH and use WinScp to browse the whole filesystem on the PI, the file shares will not show you the log file. Maybe you already have it enabled, but I'm mentioning just in case.
The log file is /dev/shm/runcommand.log and it's produced after you run a ROM. Try enabling vebose logging when starting the ROM via Runcommand launch menu.