@Artemis008 ok. So since you use gamelist.xml's the only issue was it didnt delete from xml. You are all good there. If you uninstall a system in retropie setup, then you hit select while that game is highlighted on the game select screen and edit the game you can just delete it there and it should delete it from the xml

Yes, give it a go from a version with the standard build and add AM from experimental. I'm sure Buzz integrated it better than I would have done, plus I could do the same to help debug if it still doesnt work.

@GtBFilms I buy it. Really cool and fast!

Hello,

Sorry to revive a old topic but I have the same issue, and so I thought I'd add my details in case anyone has more info since last time:

Raspberry PI 3B Retropie 4.3 BLE Keyboard Logitech K830

As OP, the keyboard is discovered and it claim pairing is successful, but it's not usable :(.

I found the post below on stack Exchange that looks promising (suggesting installing latest BlueZ module), but before I attempt the steps myself, I wanted to check if anyone has tried it for retropie.

"Does RPi 3 have BLE (Bluetooth Low Energy/Bluetooth 4.0/Bluetooth Smart)"
https://raspberrypi.stackexchange.com/questions/61758/does-rpi-3-have-ble-bluetooth-low-energy-bluetooth-4-0-bluetooth-smart#answer-61775

Thanks!
Tim

When attempting to compile using Debian I was getting kernel panics and references to null pointers in memory. After trying a different SD Card, Cables, and power sources everything has only began to work once I've bought a new Pi.

I can only assume I've got a faulty unit?

Regardless I'm now able to run RetroPie on the exact same setup (with the Pi swapped out).

Sorry, this was not working....

pi@retropie:~ $ bluez-test-device remove E8:06:88:4D:25:43
-bash: bluez-test-device: command not found

As much as I wish that I had an answer for this, I do not. However, I do have resolution. I started over from the bare image again, and rewrote my scripts from scratch to favor ALSA over PulseAudio - and did not install PulseAudio this time around. Considering the other issues that PulseAudio was giving me, in terms of system stability (or the lack of system stability), I can only imagine that my original issues were also related to that.

On the plus side, I've managed to knock together a decent script that gives me what I was after - volume up/down followed by an indicator tone, volume up/down to exit mute state, and a functional mute toggle through tracking the volume and mute states. More complex than what I was trying originally, which was using pactl to control it all, considering that I am on of the "lucky" ones who cannot get ALSA to unmute.

Hi!

I used this one for my first arcade controller with retropie and it works great (i play only arcade games, but i guess with other systeme, it'll work too)
http://groovygamegear.com/webstore/index.php?main_page=product_info&cPath=76_80&products_id=303
And i think an Arduino Leonardo can emulate keyboard input...

@backstander
Interestingly enough, it seems retroarch.cfg does not exist in my system and that may be what's causing the issue 0_o

I'm gonna try resetting to defaults and see what happens! Thanks!

@charlied43 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first (as agreed when registering)

@mvgilpatrick your chances to get help increases if you open a new thread specific to your issue. Be sure to give as much info about your setup as possible (good advice on how to get help here: https://retropie.org.uk/forum/topic/3/read-this-first ).

Showing ways to reproduce your issue always helps.

That's unfortunate.

Does anyone know any workarounds such as using the device as a controller rather than keyboard? Or mapping the keys to a virtual controller?

If anyone did try to help, don't worry I ditched the mini keyboard and went for a standard USB one. Solved

Sorry, forgot: I am on RetroPie 4.1.8

ok i finally uploaded everything and made a readme on github. Everything works now, when mouse mode is active the keys from your buttons are not registered anymore and you can switch between mouse mode and your normal input method. you specify and remap existing keys of your encoder specifically for use in mouse mode (you tell it if i press this button which is key CTRL for example then send key F5 instead). You can specify 6 keys like this.

i did not find a game yet that did not work with this version, my readme needs work though but it's a rather long readme for something simple to setup