@BuZz : I saw this menu, but it provides me only with the choices "bookmark" and "share". In fact the first post is not editable, but other ones are editable (I just edited this one)

@snock said in Retropie for Odroid-Go Advance?: I was referring to the script (retropie) to install cores/ports/app as I can do with retropie in my rpi. That is not ported or tested with the hardware/system that's supporting the Odroid GO Advance. It's not supported right now and I don't think it will be supported in the near future.

@fluffypillow thanks again for putting this together. For better or worse it has inspired me to start on a Pi4 build and hopefully learn a bit more about this stuff. And to the rest of the team keep on doing the amazing stuff that you do.

^_^ Thanks anyway pal. Glad you're still alive! I knew you had done some work with the XU4 and the N64 case. That's why I was hoping you might be able help. It's cool though.

In this case, I don't know why it's not working. It's possible that I've added something else besides the step I enumerated in my previous post, but I don't think so.

One hour ago I removed and then reinstalled from source and the same :(

@mitu Is solved now if I changed the theme and worked everything. I just have in some psx games issues with te control but is minimal. Thank you for all. Now is time to play after the hard work of configuration almost 3 weeks wow!

Ok I will try but also check one photo and it says also, besides that, Audio Manager error ALSA, something like that, SDL audio problems. With that fbset can be fixed also?

Ok thank you it works.

I installed everything as it says here with the latest version: https://retropie.org.uk/docs/Odroid-XU3-XU4/ I deleted from the retropie setup directory: Now I see: https://ibb.co/F4ksdhn But same error emulationstation. or line for same error. When I installed the new retropie it took almost 3 hours it was a lot of time but did nothing. Same SDL error :(

Thank you @mitu for all help. I almost finish my image from other posts you helped me to solve. In the case of the game pads I write a solution worked for me, just in case someone is lost and can be useful. This is the solution: Finally I could make work two 8bitdo SN30 Pro 2 game pads. I used the firmware V1.2 and worked pretty with this same technique. However, I wanted to try with the latest V1.3 firmware to see what happens and I could make work. Fighting with the retro arena setup and also retropie setup both versions in the bluetooth script, it just worked for me the first time and after the first time is impossible, at least for me, to pair again by the horrible error Already exists bluez.org. Something is stored in the cache or somewhere after the first pairing but I could not find information in any place. Most of posts run from a real solution and they mention “my solution was begin with a fresh image and problem solved”. I made that but if you have a mistake, like in my case, is an endless loop over and over again and no solution. Then this is what I did: First I made a copy, to have safe the original file “/etc/dbus-1/system.d/bluetooth.conf”. Then I replaced that file with this: https://pastebin.com/LufCYWy9 Then I made this procedure to pair: 1.-sudo service bluetooth restart 2.-agent on 3-power on 4.-scan on 5.-scan off 6.-pair “mac address of the gamepad” 7.-connect “mac address of the gamepad” At this is step it will pair although and is possible it can says cannot connect. No matter this is not a thing to be afraid. If it doesn’t connect or says fail to connect in specific: Turn OFF if it is ON the game pad. Turn ON again normally the game pad and type again step 7 (connect with the mac address command). It can says a couple (2 or 3) times is not possible connect but no matter it will do. Simply is turn OFF the game pad and ON again and give the “connect” command again. Once say successfully connected is give this command: 8.-trust “mac address of the gamepad” 9.-Return the original file “/etc/dbus-1/system.d/bluetooth.conf”, deleting the one of pastebin above described. Just in case. I used the pastebin temporary just to pair, after pair there is no sense to keep it. If in the step 6 of pairing says already exists bluez.org or simply never connected in step 7 then is type first to see the devices paired: devices After that is check if i there the game pad. If it’s there then is give now: remove “mac address of the gamepad” One is successfully removed is back to step 5. Once is paired, and connected, because It will pair for sure, also will be detected ALL the buttons by emulation station. I have two gamepads and both were detected including after reboot and latest firmware. I tested this like 10 times to be sure, including making tests downgrading and upgrading firmware in the game pads and always worked at the end. I write this just in case someone has a problem as me and want time and loss time beginning from fresh image and is wanted to save time.

you need to reinstall settingsmenu from setup on cli, although you can just wait for later today when 3.0 comes out.

There are some good instructional vids out there. Unfortunately some of the most popular ones are not always too accurate. Need someone who is clued up to make more.. eh @herb_fargus ;-)

They do have a discord, you could try there. http://odroidarena.com/ link should be on the right hand side of the page.

odroid go isnt running retropie i dont even think its running Emulation station from what i understand its running a custom launcher made to look like ES

Is lowering the resolution an option to you? And using overlays and shader can also have an impact.

@barbudreadmon said in Odroid XU4 MAME Performance?: @loggahead said in Odroid XU4 MAME Performance?: I just have to update the lr-fbalpha package right? If you mean from binary, probably not. As said above you'll probably have to update from sources. This worked! Thanks so much again!