[QUOTE=rsn8887;26842]Same problem here exactly, tried nightly from 08/13 and downloaded latest mame cores using online updater option. It always show no core after loading the mame cores and then asks about open as archive when trying to load content. This is on nvidia shield portable.[/QUOTE]
Update to lollipop man all will work fine again
@Radius I went back to kitkat and the issue returned so it maybe has to do with android version? updated again to lollipop and all worked fine, weird…
[QUOTE=elconejotres;26899]Update to lollipop man all will work fine again
@Radius I went back to kitkat and the issue returned so it maybe has to do with android version? updated again to lollipop and all worked fine, weird…[/QUOTE]
Thanks for the info, but after reading the thread over on the Nvidia Shield Portable forums about the various updates, I will probably never upgrade Lollipop. In fact I am pretty happy to be running the last firmware version on which the Broglia .emu emulators work without any stuttering. That stuttering problem with newer upgrades has never been fixed AFAIK, unless you root the device and then change the CPU governor settings.
Same here you’re using CriticalComposer custom rom Buckler 2 right? the issue with mame 2014 (2014 not 2015 or MAME which is known broken) is present in any kitkat version even on buckler only for that I went to lollipop, the .emu problem doesn’t bother me at all because I don’t use those emus they have really bad performance and lotsa issues 
RA crash with latest mame cores…
latest RA with mame 2003 doesn’t work…
The back button is not working on the daily I installed yesterday. When I press it the first time I get the message “Virtual (0/0) not configured”. I’ve tried to remap the menu button directly, but its as if RA is intentionally ignoring presses from my back button. I’m using a Samsung Galaxy S5 with an ipega 9023. This is the first daily I’ve used, so cannot say if this is a regression, or a bug specific to my device.
“The response to the Android port has been pretty depressing. Doesn’t help that most of the feedback is totally non-constructive / vitriolic”
???
I am still waiting for a solution to the mame cores problems…
And I am willing to help as much as needed !!!
I installed latest build (first time on new device) an android box (G Box Q)
The current GUI is the touch version (black with small white text)
Tried using remote to navigate and change the UI to lakka style xmb, as my HID controller wasn’t responding even though RA detected it and it works with GTA: SA mobile and with the box just fine.
When i click to change UI it won’t change to other UI interfaces, when i click (acts as touch, coz my TV isn’t touch based) it won’t simply change and scrolling is out of the question.
What to do? The controller in question is the Razer Serval, and it is amazing. Just won’t work with RA or I’m missing something in the menu to change…
You need to change it to xmb and exit retroarch, then open it again.
facepalm Scrolling still isn’t fixed after all this time?!?
I exploited selecting the lowest menu option with extra options and going back once to see more menu items so the input menu was onscreen. I eventually got to every certain menu I needed via this exploit to gain actual control by mapping my input the first time and changing the GUI style. All this with a Logitech K400r keyboard.
Currently,I have really great controls to my own personal likeness,and have played/level grinded Mario&Luigi Superstar Saga on the mGBA core making use of rewind to max my POW stat bonus every level-up.
Change to XMB, in the Onscreen Overlay change Display Overlay = ON and Hide Overlay in Menu = OFF, always launch RA in the landscape position and be happy! 
Edit: and remember to wait 3 ~ 7 seconds to retroarch load the overlay properly
This is more of a GUI thing so I guess it affects all implementations of Retroarch but one thing that always bothered me was when you would cycle through settings values and reach the end, it resets back to the lowest value possible. That works fine but you can’t go the opposite way to get back to the highest value. This sort of becomes a nuisance if you accidentally cycle past the max value allowed for a specific option setting. Take the overlay opacity for example. You could hold right and have it cycle through all values until it reaches 1.00. Going over makes it drop back to 0.00. You can’t press left though to get it back to 1.00 and have to cycle through all the values again until to reach your desired setting. I always hoped one day a nightly would address this
Also, is there a reason why you would select null for menu driver?
i have two request.
1.i can’t load MAME 2014 core in 1.2.2 after update core. how can i load mame 2014 core? 2.PLEASE REPAIR BACK BUTTON IN MENU SCREEN.
Been testing this recently on the Shield TV and noticed the following:
Controller initially pairs on port #0. Everything works fine. If the controller goes to sleep, when you wake it back up, it pairs to the next available port (in my case, generally port #2, I believe, since my keyboard takes port #1). If you put the controller to sleep, and wake it back up again, it will again grab the next port (#3), and so on.
So, if I walk away from it for too long, I end up having to force close the app and relaunch in order to get the controller back on port #0. Not sure if there’s another way around this, currently?
Sorry but I got the same results with the mame cores after installing RA from scratch…
[QUOTE=MarzSyndrome;28705]Could anyone confirm whether Ogg Vorbis audio in the Genesis Plus GX core has been fixed yet?
It’s emitted nothing but white noise in the Android builds for ages and quite recently ekeeke mentioned a possible fix, but it needs to be done at the source level.
https://github.com/libretro/Genesis-Plus-GX/issues/28[/QUOTE]Anyone? If this got sorted it would hopefully mean being able to free up some SD card space again.
Just tested the latest version (10-05) with my archos gampad 2 and mame 2003/2014 are not working,
Arcade (FB Alpha) works, again when I select mame core I got a “No Core” text on the bottom left of the screen…
Other cores like stella, game and watch are working fine !!!
Both devices that are NOT working are NOT rooted…
downloading mame 2014 core…
updated the info files and … the same results RC crashed…
Oct 7th apk crashes on launch. 6th apk works fine.