@qstyler said in Cannot setup 8bitdo bluetooth adapter on Pi 4:

Hi! I'm trying to set up an 8BitDo BlueTooth adapter but it doesn't seem to work for some reason.

First of all, I disabled Bluetooth in the config.txt file by adding dtoverlay=disable-bt

Then I plug my dongle and try to do bluetoothctl, but it hangs forever.

To fix the issue I tried to run the following:

$ sudo systemctl enable bluetooth Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth $ sudo systemctl start bluetooth

This command gives no output...

And this is a status of the bluetooth:

$ sudo systemctl status bluetooth * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) Apr 09 11:24:42 retropie systemd[1]: Condition check resulted in Bluetooth service being skipped.

If I try to get a list of USB devices, I can see my dongle, but without a name (device 004):

$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2dc8:3107 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here's the full dmesg output, maybe this will help.
https://pastecode.io/s/ejohjh6u

I'm using Raspberry Pi 4 Model B Rev 1.2

There are no other USB devices connected to my Raspberry.

And I'm using a default usb-c power adapter that came in a box.

The 8bitdo bluetooth adapter is not actually a bluetooth adapter in the traditional sense. When you plug it in, it is treated as a USB controller, not a bluetooth radio. To connect a controller to the receiver, press the pairing button on the adapter, then press the pairing button on your controller. When both lights are solid, the connection is made. It also means you can only have one controller paired to the adapter at a time, and need multiple adapters if you want to pair multiple controllers. Changing bluetooth settings in the OS will have no effect on the adapter.

@mitu Well that can be arranged as I tested the VLC mode and it still worked right, however there's still no game info displayed.

What could possibly be causing that? Something wrong with the chosen fonts? The font files? The resolution I'm forcing it to display at (resolution mode is meant for a screen installed in an Arcade1Up gen 3 cabinet)? I'm trying to think of anything that might mess with its subtitles and can't come up with anything.

EDIT: FINALLY figured it out. In video screensaver settings, VLC Resolution needs to be set to Max. Doing that finally shows the game info. Gonna guess this has something to do with video mode, but I don't know for certain. Either way, that fixed it.

@mitu said in Getting picture when 2 screens are connected. 7" screen and 27"monitor:

I've tried swapping the cables, and it worked from the first try.

I now have picture on the 7" screen, which is now connected to hdmi1 and when I connect the 27" monitor to hdmi0, I get picture on the monitor. The 7" screen then displays a rainbow color screen and then goes blank.

The 7" screen only displays the launching screen, when I play a game.

I immediately tried an arcade game, the launching screen displayed, but then went back to the main menu.
I've tried other consoles, they all seem to work.

I've tried 2 other arcade games, which seems to work.

Coincidence or not, the game I tried first has a bezel overlay.
Maybe the monitor can't handle that for some reason ?

I will disable the bezel and see if it runs then.

@mitu I just saw the other answer in there, I'll try changing those flags and see what happens, thanks!

Could find the solution on my own.

The correct syntax is J0B4/H0VX
where the "X" is set to be 1(up) 2(right) 4(down) or 8(left) depending on the direction.

@mitu so i just mapped it in ES ( after re-enabling auto save) and then i had to quit ES and i did a system shutdown, performed a reboot and it is WORKING! so far, yes!! i think before, i wasn't exiting ES correctly and it kept remapping the r1 to only the start button as the "y" button. and it was showing up as a keyboard input. I REALLY appreciate your help. thank you!

@mitu Updating from source seems to have fixed it.

@JuanZt

Just stopped by to thank you. I've used your steps and was able to get my PS4 controller (not original) to work.

I've found what I was looking for. It works great ! Here is a list of atomiswave shortnames :

atomiswave_shortnames.jpg

You can copy the drastic.sh version from that repo to your own RetroPie-Setup installation (overwriting $HOME/RetroPie-Setup/scriptmodules/emulators/drastic.sh) and then re-install drastic.
Do note that replacing the scriptmodule with another version will make updating the RetroPie-Setup fail, since you modified the file locally.

I get much faster boot times with my bluetooth (8bitdo) controllers turned off. Since that's an acceptable workaround for me, I haven't dug in to figure out what's wrong. My expected boot time is around 30 seconds on a 4. I'm only running retropie.

This thread may help:
https://www.raspberrypi.org/forums/viewtopic.php?t=182356

It suggest running systemd-analyze blame.

@GreenHawk84 yeah that should work

@sad_muso said in Pi 4 Retropie issues:

Hi,

I've just upgraded to a Pi 4 and performed a fresh install of the latest Pi 4 install file (md5: 9154d998cba5219ddf23de46d8845f6c). I know this is still a beta, but I've experienced a couple of quite big issues. Is it the build or something I'm doing?

WiFi search initially found about 8 of my SSID name (for some reason). I couldn't connect to any, but now it can't find any SSIDs at all Retropie has crashed on a few occasions (with 'Retropie has crashed' message) Can't change resolution from 4k to 1080p because I can't get into the resolution menu - it just stays at the same menu level

Have I somehow got the wrong image or copied it to the SD card incorrectly?

I had similar issues

WiFi - I created the file pre setup so didn't have this, however did notice a lot of repeats in Bluetooth when setting up my sixaxis for PS3.

Didn't get crashing

Raspi-config resolution... I couldn't get into this either although I did get a workaround which helped.

All my snes rom have mgd file extension in each zip. After renaming all these rom to flc in the zip. No more problem...

Is ReDream the one with the GUI?

I used FlyCast and it .... worked.... One of the emulators crashed on me but I don't recall which one. I'll try ReDream again as it did load but seemed a little goofy but that's probably due to my inexperience with it. Took me a few minutes to realize the mouse was working and had to exit using the commands and not through RetroArch. I'll give it another whirl.

Part of the problem is not really having anything off the top of my head that I would specifically play on Dreamcast. Nearly everything over the years that I had has either aged terribly and not worth the trouble or has been updated or remade on better systems.

PSO has been redone and done better, Skies of Arcadia is on GameCube, etc.

Okay, there is some problem with the onboard bluetooth. The documentation already mentions that the case interferes with 2.4 GHz wifi. The same is true for bluetooth, and I added a USB bluetooth adapter to mitigate that.

Just for context, here is a comparison of uncached read performance:

SSD

$ sudo hdparm -tT --direct /dev/sda /dev/sda: Timing O_DIRECT cached reads: 520 MB in 2.00 seconds = 259.69 MB/sec Timing O_DIRECT disk reads: 902 MB in 3.00 seconds = 300.36 MB/sec

SD

$ sudo hdparm -tT --direct /dev/mmcblk0 /dev/mmcblk0: Timing O_DIRECT cached reads: 84 MB in 2.04 seconds = 41.13 MB/sec HDIO_DRIVE_CMD(identify) failed: Invalid argument Timing O_DIRECT disk reads: 124 MB in 3.02 seconds = 41.11 MB/sec

Definitely worth the effort to me. Instructions for making the RPi4 boot from USB can be found here, btw.

@DarkGlobe said in kodi - Retropie 4.6 - Raspberry Pi 4B:

Could this issue be fixed by making customisations to the /etc/emulationstation/es_systems.cfg directly rather than creating a copy or would that put the customisations at risk of being overwritten & lost?

The system file (in /etc) is maintained by the RetroPie-Setup script, so it might get changed by an update, so it shouldn't be used for custom systems.

@yaya said in Pi 4 Black Screen after autostart:

may you should add this information into the FAQ ;-)

That's not a bad idea - we'll have a PI4 specific page 'really soon'. Have fun !