Thanks for the info all. With a combination of core remapping and removing some lines I didn't realize 8BitDo stuck into the autoconfig by default, I have removed access to 99% of these menus. Still having some issues closing off Mame's menus, but that will be another thread for another day. Thanks as always!
@digriz Thanks for the tip! You're right, the instructions were slightly vague for the different pairing options. My nephew is super patient so I know it's not really going to bother him. For me, I KNOW it could be better! LOL
@mfraz74 Looks like Debian doesn't package the 8bitdo-tool or it's included in a plugin, but I haven't used fwupd so far, so I can't offer more details. Try using the macOS updater to install the latest (4.20 I think) version of the firmware.
After much searching, I found this link https://github.com/goodtft/LCD-show/issues/278 for an issue with an LCD display I tried to use years ago. Apparently, it updated my /boot/cmdline.txt file to put ttyAMA0 in my console, instead of the default serial0. Swapping it back to console=serial0,115200 and rebooting, and now bluetooth works again!
@jimi007 Ok, so, I was an OG Amiga user. I had a 500, 2000, and a 3000. Amiga was made long before any console has force feedback of any kind. So, why would there be any vibration response in any Amiga game ever?
I guess I am trying to figure out why you are expecting vibration from a system that never had it. It just seems on par with expecting stereo surround sound from an Atari 2600.