@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 Lol, this is the way. Thank you so much. Feel so dumb for not thinking to make an issue in GitHub. I appreciate you as always, mitu!

@mitu awesome, thanks! It seems pretty silly to attempt to match EXACT versions, since retropie works with latest version anyways. I guess I'll just make my script compare version numbers and if it is < the system I want to replicate, just use the retropie_packages.sh with install_bin. Building EVERYTHING from source and hacking the source parm seems unnecessarily silly.

@WhiteT982 $1 is passing the 1st parameter (probably your steam game) to the "steam" command.

&2>1 is redirecting stderr to stdout (so you can see if an error occurs while reading stdout).

The hotkey actions are only available for P1, that's by design - it cannot be configured.

What Pi model ? What RetroPie version ?
Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, as much as you can.

@sleve_mcdichael Oh, I see! God I feel an idiot haha .. I'll try that out, but that makes sense.

@windg You can also reset the game (Hotkey + B) in order for the controller type to be re-read, just changing it mid-game doesn't work. Save a game Remap file for the controls so you don't have to repeat the steps each time.

@fdr4prez

If correct, you should have one in your mailbox now.

@sleve_mcdichael said in Shader Activation text in Retroarch.cfg?:

video_shader = "/path/to/shader.glslp"

Edit: if you want them enabled by default, use also:
video_shader_enabled = "true"

THANKS!

@JimmyFromTheBay

I've installed the MESS fork for it (lr-mess-mz1500-cass).

What is the MESS fork ?
Please give a better explanation on how you installed.

With this command you can find the supported extensions :

pi@raspberrypi:~ $ /opt/retropie/emulators/mame/mame -listmedia mz1500 SYSTEM MEDIA NAME (brief) IMAGE FILE EXTENSIONS SUPPORTED ---------------- --------------------------- ------------------------------- mz1500 cassette (cass) .wav .m12 .mzf .mzt

These are the loading instructions for MZ-1500 :
Hit C key
TAB > Tape control > Play

I used cassette files inside mz800_cass.zip from mame-sl.
mucmac.zip worked for me.

@erv93 said in Hi,Pi3B, Can’t set Country from Raspi-config:

Hardware issue ?

Loos like it.

See https://forums.raspberrypi.com/viewtopic.php?t=58151 for potential issues during boot. It details most problems and how to find them based on the led blinking pattern.

@DJ151 Not to worry, you weren't disrespectful.

@jbsapp
Great information.

I was curious and managed to locate a little detail on the fuzz and other arguments.

https://stackoverflow.com/questions/16110515/explanation-of-fuzz-and-flat-in-input-absinfo-struct-in-input-h

You can find that

fuzz: specifies fuzz value that is used to filter noise from the event stream.

Which means that the input system in linux will drop events generated by the device driver if the difference from the last value is lower than the fuzz. This is done in the input layer.

Another user posted:

So it would seem that any changes less than fuzz are should be filtered out / ignored.

Also,
https://python-evdev.readthedocs.io/en/latest/apidoc.html
The Device section talks about the fuzz argument.

If the heating is still present if you exit EmulationStation, then the problem is somewhere else - just exit EmulationStation and leave the system to run for a while.

Is the problem with the theme? Or because I'm using Retropie 4.3?

I don't think the version has any influence, but why use such an old version ? Do you have anything running in the background besides EmulationStation (music scripts, input handling scripts) ?

Did you do any soldering/modifications on the Pi ?

Thanks, both - it turns out it is a quirk of the emulator and doesn't like it if there is an extension on particular types of roms. A .sh solution has worked though! Thanks again.

Just for a test i set a 90-second duration.

on my Pi0W the splashscreen was shown for about 75-seconds.

on my Pi3B the splashscreen was shown for about 80-seconds.

So the timer is working for long durations, but it is just not accurate :)

No worries. I can live with it. As I mentioned, i just need about 30-40 seconds.

thanks again.