@lordashram and bluemonkey I assume he meant the shader versions, which are still too heavy-duty for mobile GPUs at anything greater than 2x scale (and most phones not even then). The missing frame thing happens when you use a too-slow shader with threaded video enabled.
RetroArch-2013-11-17
Android: Updated: RetroArch, MAME2013
Win64: Updated: RetroArch, MAME2013, TyrQuake
NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions.
Joined to say Mupen (Super Mario 64) is finally working on the 2012 Nexus 7 running KitKat with ART enabled. Not having analog controls for my sixaxis or on screen controls makes it difficult to, you know, play. 
Tried last build, I want to report two things: in TV Mode the MAME 2010 is reported as MAME 2013 (in History, for instance), and the Path config isn’t working in TV Mode. If I set a path, this isn’t saved on exit.
Thanks for the builds 
they’re great.
EDIT: I’m on android
rooted.
tested on stock 4.1.2/4.3/cm11 4.4 kitkat
mupen64 back to retroarch menu,also no core plugin in settings
Tried mupen64 playstore is fine.any problem.
log file attached
I too get the same issue with n64 games not loading.
I’ve looked at your log file twice and unless I missed something then I don’t see anything wrong. Do you change any settings, in Phoenix or in RA (V Mode)?
Something else to try is this: Create the following folder structure: /storage/sdcard1/roms /storage/sdcard1/roms/n64 /storage/sdcard1/rom/system
Move only your n64 & z64 roms to /storage/sdcard1/roms/n64 Using Phoenix (not RA in TV Mode), in settings, paths Tell Phonex to use /storage/sdcard1/roms as your ROM directory then tell Phoenix to Enable custom directory for SYSTEM then point Phonex to /storage/sdcard1/rom/system as your custom directory for SYSTEM This way we can see if you have any type of config files that are causing conflicts by moving just your roms with a clean SYSTEM folder.
done!
still same problem persist!
thx.
Has handy been removed?
@lordashram Would you mind including the instancingviewer-camera core in your android builds for testing purposes? It would be helpful to get some compatibility testing.
If you can get it going, choose any old PNG image as the ‘rom.’ It doesn’t do anything with it, the android frontend just doesn’t support rom-less loading (yet).
RetroArch-2013-11-20
Android: Updated: RetroArch, MAME2010, MAME2013 Added: Instancingviewer-Camera Re-Added: Handy
NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions.
@brujo5 I’m at a loss right now, if I can come up with anything else I will unless any of the devs can come up with any other ideas.
@foleyjo Handy isn’t in the normal build scripts and has to be tweaked a little to compile, but I added it back in my builds again.
@hunterk Lol, I had planned to finally add it in my next build since I saw it seems to be finally working, done. I will test it later as soon as I have time and report my findings.
Thanks lordashram. Wasn’t sure if I had done something wrong because I saw Handy on one build and then couldn’t find it.
I’m still having control issues with these builds. I installed the latest and set back button to bring up the menu. This worked but my device (jxd s5110b) isn’t auto detected. I then deselected the auto detect input and set my own binds but when I loaded a core my control binds are ignored and the back button no longer brings up the menu
I haven’t been able to get any controller binds working on any of the test builds either…