Thanks for the clarification! And I would have sworn that after my migration to XPx64 the change in Ubuntu was troublesome in the 1st incarnations of 64bit but later it was pretty easy (maybe because all apt* gets where referencing 64bit installs), but still I remember using certain geo-scientific apps (edit: deb packages) that where 32bit (and wheren't updated since ages) only under ubuntu 64bit... but I am really not sure whether I installed a layer similar to WoW64 or simply used in that time something like "linux32 <appname>", but what I am pretty sure in my memories is that in early ubuntu 64bit versions I've stepped back from migration because they where 64bit World only and just a few distros later it was alike (in my memory) to the windows world :/ Well, Memories.... But to add one last statement, after XPx64 (which really wasn't supported/pushed by M$ from start and the users of it learned pretty fast how to use Orca or the Windows SDK AppVerifier to get apps installed) and the early hazzards of 64bit OS', I've never had any trouble of running 32bit Apps on my Desktop PC Systems (on various 64bit OS)... So I am really troubled by the notion of the concept 32bit ain't running under 64bit OS', as my experience is strictly opposed to that :/
Though I may say, my thoughts aren't really helpfull within OP's topic ... Sigh...
@llivingst I ran into a similar issue when I updated a year old build on my pi 4. It would get to emulation station, but went to a blank screen when going into a game. It think it was crashing cause I could not exit back to emulation station or my video feed was gone. I know a lot of kernel changes were made, so maybe you have a custom configuration that interferes with the new kernel. But Step one would be to try switching hdmi ports. I remember that being in the wrong port did that before. If not, you might have to reimage a new build. I changed all my custom configs from overclocks to KMS drivers switched back to and still no go.
Hopefully, someone that was able to connect these will chime in here. I have the same problem, seems like I was able to connect them through bluetoothctl in the OS (got success message and the rumble from the controller), but nothing I can do to connect with RetroPie and have them usable.
@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
I have noticed an issue with the OLED stats display which still noot working when the Pi boots up.
Without an actual display, it's difficult to diagnose. But, since you created a service unit for it, why not look at the error messages logged by the service to see what's the error printed by the script ?
The Pi4 and Pi3 are different hardware and have different USB controllers, hence the difference. That's not why your controller behaves this way.
There must be some difference somehow. I tried 2 different controllers: Xbox One Series X controller and Xbox One S controller ("S" not "Series S"). I tried all 4 usb ports. Everything work fine on my Pi 3 but none of them get turned on when my Pi 4 boot.
I think I will move on, anyway I planned to use the Xbox One wireless dongle and buy batteries + a docking station for refilling the batteries, so this problem shouldn't bother me anymore after that. I'm just leaving as much information as possible in case someone else encounter the same problem in the future.