@mitu I dont think so

@mitu pi@retropie:~ $ uname -r 4.19.50+

@Chuck_B lol. There is a tad bit of slowdown, but nothing detrimental.

@gtoal I don't see how this applies to the topic at hand - the poster specifically said it's a non-W(ifi) model and they don't try to use wireless at all.

@ignatius It's possible to expand those four buttons to ten inputs using an outside mapping solution like xboxdrv, but in practice playing any action-heavy game would be very difficult. Certain strategy games and RPGs that need the extra buttons might play well enough though.

I tried buying one and it kept saying my cart was empty when I would click the add button. I'll just have to wait for the next batch. Amazon needs a better system here.

@mitu Sorry about that. I wasn't sure how to post the log file. So I ended putting some soldering some pins on it and putting it in a freeplay zero. I wiped the sd card and added the freeplay modded retropie (That was before I saw your post asking for the log file...). Weirdly enough a somewhat similar issue occurred again. The buttons stop responding and the pie pops up errors. Since I wiped the previous log and I can't access get my keyboard to work on the gba I don't think I can provide much to you. I talked to Ed from Freeplay and he suggested some things to try out. If it doesn't work I'm going to just try out a new raspberry pi and see if that's the problem. Thanks for taking the time to try and help me troubleshoot.

Today, I have some great news :) The emulator is now fully functional. The only thing you need to do is to update git repository line in RetroPie-Setup/scriptmodules/emulators/pcsx-rearmed.sh from gitPullOrClone "$md_build" https://github.com/notaz/pcsx_rearmed.git to gitPullOrClone "$md_build" https://github.com/timemaster5/pcsx_rearmed.git saio and then run update pcsx-rearmed from source in retropie-setup script Then you will be able to run this emulator without performance issues but only with USB keyboard. I am now struggling with key bindings, I am not able to bind UP/DOWN/LEFT/RIGHT buttons of GBZ SAIO.. probably because they are not buttons but hat... I don't know now. Another issue is with the mouse cursor being visible in some games, but this could be hopefully easily fixable. And for the record, the main problem has been caused by one commit to libpicofe adds SDL_DOUBLEBUF flag.

Is that the solution for me?

@lonelik said in Can you naviguate in retropie shell menus with a joystick ?: Maybe the keyboard is my js0... You can check which device is mapped to js0 with this command in Retropies text console that you land in after pressing F4 in Emulation Station: jstest /dev/input/js0 Ctrl + c aborts jstest. Alternatively, this should list all input devices of the system: (I say "should", because I am not at home at the moment and can't test the command on my own Retropie. It works on my Laptop's Kubuntu Linux, though.) less /proc/bus/input/devices You can browse the list with your cursor keys or PgUp/PgDown. Exit the browser with Ctrl + c. You get back to Emulation Station with the command exit.

@obsidianspider ok i found the issue!!!!! i had copy/pasted the config line within /etc/udev/rules.d/10-retrogame.rules (i create this manually rather than using the adafruit install script) was checking the config file and noticed that the config contents looked odd SUBSYSTEM=="input", ATTRS{name}=="retrogame", ENV{ID_INPUT_KEYBOARD}="1" at first glance it looked fine, but when i typed another double quote next to the exsisting ones, it looked slightly different!! so i re-typed all the quotes, and everything is fine and dandy again!!! :)

While I am by far no expert with Bluetooth, I think you need to set the hciconfig class. man hciconfig states this for class: class [class] With no class, prints class of device. Otherwise, sets class of device to class. class is a 24-bit hex number describing the class of device, as specified in section 1.2 of the Bluetooth Assigned Numers document. You can find this at hciconfig (1) - Linux Man Pages I found a list of classes at BlueTooth's Baseband page. In Table 9: The Peripheral Major Class keyboard/pointing device field it uses this bit config 5 4 3 2 Minor Device Class bit no. of CoD 0 0 0 1 Joystick 0 0 1 0 Gamepad And Minor Device Class field - Toy Major Class has this: 7 6 5 4 3 2 Minor Device Class bit no. of CoD 0 0 0 1 0 0 Controller 0 0 0 1 0 1 Game If this helps, here is how I get BlueTooth information from a connected device: pi@lucaspi:~ $ hcitool con Connections: > ACL **00:26:43:66:A8:74** handle 11 state 1 lm SLAVE pi@lucaspi:~ $ hcitool info **00:26:43:66:A8:74** Requesting information ... BD Address: 00:26:43:66:A8:74 OUI Company: Alps Electric Co., Ltd (00-26-43) Device Name: PLAYSTATION(R)3 Controller LMP Version: 2.0 (0x3) LMP Subversion: 0x131f Manufacturer: Cambridge Silicon Radio (10) Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80 <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <paging scheme> <broadcast encrypt> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <AFH cap. slave> <AFH cap. master> <AFH class. master> <extended features> Try connecting your pi 0 to your other pi/debian system and see what info is different. Lastly, maybe check out Bluetooth CoD: Bluetooth Class of Device/Class of Service Explained for information on CoD info. I will be reading this as well for one of my projects, so I might be able to provide more info.

never mind.... i'm dumb.... i choosed a wrong romset from my archive... doh! Vectrex works... :)

@obsidianspider I suppose a smooth, injection molded part would not bind up the same, right? I wonder if there is a workaround for smoothing out this area such as a coating of epoxy or bondo that could be sanded nice and smooth without enlarging. Tedious and tiny, I know. Another thought would be to try a set of buttons you don’t care about and remove the orientation tabs. Maybe it’s the angled spots where the tabs are that bind up.