yashsingh1/xdaforums huggingface dataset:
[Xperia Play Android Development] bubblegumballoon:
Well there's always psxperia if you really need analog controlls for PS1 games.

I tried ocarina of time and it works with some minor glitches but it needs an overlock torun full speed, I also tried banjo tooie which doesn't work at all in n64oid but is prone to crashing in Mupen. In general Mupen can play more games than n64oid but some games run a bit slower.
[Xperia Play Android Development] antEris:
I have a pretty big library of n64 titles I'll try some out and report back later. Might even start a comparability thread

In the general section.
[Xperia Play Android Development] emann56:
How do I get the buttons to work on the xperia play?
[Xperia Play Android Development] paulscode:
First, install and run the SDL Scancode Finder app. Press the keys you want to map, and write down the Scancodes that are displayed. Then edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. Finally, save the file and start the emulator.
[Xperia Play Android Development] BuckM:
Just to make it a little easier:

Up: 82

Down: 81

Left: 80

Right: 79

Square: 191

Triangle: 198

X: 119

O: 270

Sel: 88

Start: 87

L: 184

R: 185

Menu: 118

Like Paul said just take the values and toss them in here:

/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini
[Xperia Play Android Development] paulscode:
This may or may not be possible under Android (I'm not sure yet, since this is my first real Android project so I don't have as much experience with the API as some developers). The catch here is that in order to launch a sub-class of Activity, you must do it from an Intent (basically tell the OS, "hey I'd like to launch this, please"). However, to create an Intent, the sub-class of Activity must be declared in the AndroidManifest.xml, otherwise it throws an exception at run-time when you try to run the Intent. To get Xperia Play touchpad input, you must extend a sub-class of Activity called NativeActivity, which is only available in Android 2.3 and higher. You can't compile the program with a class in the AndroidManifest unless that class is also declared in the source code. By declaring the class, you add "extends NativeActivity" to your code, thus limiting the app to Android 2.3 and higher (chicken, egg.. no chicken..)

I'm thinking it might be possible to declare a fake class that extends just Activity with stub methods that are in NativeActivity, compiled into a separate JAR that ships with the emulator. Adding the Xperia Play input plug-in would replace this JAR with one that has the same class name, extending NativeActivity instead. This might "trick" the compiler into letting me build the app without limiting the android version by having to extend the class that's missing in lower versions. That, of course, assumes the developers didn't think of this workaround and put something in place to prevent it. That's ultimately what we're talking about here - trying to work around security measures that are in place to prevent someone from writing an app that installs with certain permissions, then quietly "updates" itself after installation to do things you don't want it to do.
[Xperia Play Android Development] eros78:
That would be great!
[Xperia Play Android Development] emann56:
Hmmm still doesnt work:(
[Xperia Play Android Development] bubblegumballoon:
Hmm weird... download the file I will put at the end of this post, I already

configured the controls for you. Just take the file and put it in [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini

Just overwrite the old InputAutoCfg.ini

http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini

(you will probably have to right click and save the link, clicking on it will just open it as a text file)
[Xperia Play Android Development] bubblegumballoon:
Added an FAQ to the OP. Hopefully it should help answer alot of peoples question about how to use the emulator. :)

Alot of it is just copy pasted from paulcode though haha :P
[Xperia Play Android Development] paulscode:
If it still doesn't work using bubblegumbaloon's config, could you post the logcat output? If that does fix the problem and you are curious why yours didn't work, feel free to upload a copy of your config and I'll see if I can spot the typo for you.
[Xperia Play Android Development] emann56:
Works now:D Don't know what happend but now it works :P
[Xperia Play Android Development] AndroHero:
Thats really something you want to stay away from, otherwise you may end up being known as the grandfather of android trojans :D
[Xperia Play Android Development] Logseman:
Question. What is the least powerful phone that you think will run mupen64 fine ?
[Xperia Play Android Development] paulscode:
That question depends on many different factors, such as which games you are trying to run, if you require the audio, if your device has an ARM7 CPU, and if your device is overclocked. Zelda64, for example, requires over 1GHz to run smoothly, while Mario64 reportedly runs at full speed on some of the lowest-end 800MHz ARM7 devices. You take a major hit when you move to pre-ARM7 devices. Mario64 and some other average games are reported to run at a playable speed on ARM6 600MHz devices overclocked to 729MHz with the audio disabled. Other factors can also have a significant impact on performance and stability, including what Android version you are running (upgrades tend to add additional optimizations), which build you are running (cyanogenmod tends to be the least bloated), video drivers (chainfire 3D pro 2.8 Beta Egl Video Drivers reportedly improve performance on some devices), how many background processes you have installed and running, specific overclocking and overvolting settings, and so on.

So there's a complicated answer to a simple question for you :D
[Xperia Play Android Development] DrGit:
I love those! I guess that's why I exist... heh heh.

Welcome to XDA, Paul!

/OT

Let me know where you are with the GUI - as soon as the need to rename ROMs to mario.n64 before playing them is eliminated, I'll be back to full-time testing, debugging, and coding... For now, I'm dabbling with native Debian on my Droid, so I might not be interested in coding for Android much longer.

Long live the real Nintendo Revolution, Project Reality, the Ultra 64!
[Xperia Play Android Development] Logseman:
The question came because perhaps it wouldn't be such a big deal to only support gingerbread devices and forward. Those phones with Froyo tend to either be not powerful enough to play N64 games altogether or they will support CM7 which uses gingerbread anyways.

Lower spec devices tend to have fairly small screens too, which would make harder to play N64 games anyways. Basically I don't see many people playing mupen on an HTC Wildfire, Samsung Galaxy Mini, Sony Ericsson Xperia X10 mini or the like.
[Xperia Play Android Development] paulscode:
Hey, man, I haven't talked to you in a while! Thanks again for sharing the source code from your project - the information I got through comparisons gave me the missing pieces to the puzzle I needed to get the core up and running. This project owes a lot to developers like you. Good luck in your future porting projects!
[Xperia Play Android Development] juxtapose519:
Holy crap, I frigging love this emulator. The new touchpad settings are spot-on. I'm playing Goldeneye with respectable controls

on a handheld

.

Thanks for the XP support!
[Xperia Play Android Development] mehdi.moha:
i've test your aok , that is great , but still have decreasing frame effect . slow motion on gameplay .

but that is awsome that it can detect the touch pad :)
[Xperia Play Android Development] paulscode:
Some things you can try are:

- Ensure the phone's OS is updated

- Reboot your phone before running the app

- Study logcat output to find unnecessary processes, and kill them

- Overclock if your phone is rooted

- Tinker with the overclock settings (other folks here might have some suggestions)
[Xperia Play Android Development] antEris:
Compatibility thread

Hey all,

Just wanted to draw a little attention to the compatibility thread. Please let me know pm / post any games you know work and on what firmware ~clockspeed ect. you've tested at and I'll update it.

Also, if anyone has any games in particular they want to know if work let me know and I'll give those priority in my own testing.:)

And thanks again paulscode, I'm sure I'm not the only one who was starting to worry no one would give the xperia play any dedicated love in an emulator. You rock!:D
[Xperia Play Android Development] bubblegumballoon:
Updated the op with the new project thread link. The old one is archived and can be found here: http://www.paulscode.com/forum/index.php?topic=60.0
[Xperia Play Android Development] mehdi.moha:
ok man :D thanks for your attention to my report !

I'm root and overclock , surely your work is great , but when i using N64 , it work smoothly with default ( 1GH cpu ) .

for example on paper mario (( for me and all of my friend , the paper mario is #1 game on nintendo 64 :D )) when i use n64 , i can play easily , just some blue background on some fights .

but when i used your APK with paper mario , so many black screen and slow motion appeared on screen.

totally , I've said before , your work is really really great and appreciated , n64 still can'y detect the touch pad , but yours , detected completely .

thanks again man:)
[Xperia Play Android Development] paulscode:
The gist of your post is that N64oid runs faster than Mupen64plus AE, correct? There are a couple reasons for this. One is that this is a debug build, which has a little more overhead. The second is that SDL adds an extra layer between the emulator and the hardware (Yongzh completely eliminated SDL in his port). I don't have any short-term plans to remove SDL, but this is opensource, so anyone ambitious could do this. Also, a lighter-weight video plug-in would improve performance, and there are some additional optimizations that can be done, such as removing the trampoline stuff from the dynarec, halving the size of the dynarec target memory, and moving it to the .bss section (at the cost of compatibility with some ROMs), or placing RDRAM at the native memory location if nothing happens to already be there on a specific device.

Anyway, long story short, I expect performance to improve over time, especially if I can get some other developers interested in contributing to the project.
[Xperia Play Android Development] mehdi.moha:
WOW :eek::)

very very complete and nice information , you are really master man :D

i'm sorry about this question , do you think that with this knowledge that you have , or anyone else like you , can release an emulation for NDS , as complete as you made this ?:confused:

i'm sorry again for this junk question . :(
[Xperia Play Android Development] paulscode:
In theory, it would be considerably easier to emulate the NDS than the N64. The system only had two relatively slow processors: an ARM946E-S 67MHz main CPU and an ARM7TDMI 33MHz co-processor. Even if the rule-of-thumb 5X speed to emulate a system were required, most android devices have that easy ((67 MHz + 33 MHz) * 5) = 500MHz. In fact, I doubt an NDS emulator on Android would require even that much speed, because most emulators are having to translate between different CPU architectures (for example NEC to x86). In this case, since Android devices and Nintendo DS both have ARM CPU architectures, the recompiling would probably be pretty efficient. On the other hand, there might be some logistical problems with fitting the two screens and virtual buttons without interfering with the touchscreen functionality ;)

Anyway, I don't currently have any plans to port a NDS emulator to Android. My planned next project after Mupen64Plus AE will be to port NullDC (Sega Dreamcast emulator) to Android.
[Xperia Play Android Development] IE-coRe:
I think the main problem of a ds emulator is that the ds is still a actual console, not old like gameboy and n64 and nintendo still sells more ds games than 3ds games. So they would fight...

abaut the tho screen probllem, the ds has such a low resulution that it would not be a problem to display them side by side... and abaut the controls.... i have a Xperia Play:p:p:p
[Xperia Play Android Development] Cat_On_Droid:
I say the nds is only possible on tablets to play smoothly. Like sony tablet P
[Xperia Play Android Development] mehdi.moha:
thak you sooooooooooooooooooo much ,

i'm really eager to hear your explain about this :D

i personally think that sega dreamcast didn't have any famous games like ps1 , n64 , nds ... we wish some angel start working on psp games ;)

anyway , i'm really waiting for that day , that can play paper mario with touch pad :rolleyes::)

other emulators still can't detect the touch pad ..

you are the #1

thank you again ,
[Xperia Play Android Development] Logseman:
Sega Dreamcaat has a host of games in the peak of all time gaming. Soul Calibur, Skies of Arcadia, Code Veronica, Sonic Adventure...

Nothing that Paul doesn't know, I guess. I'd love to cooperate with that once the time comes.
[Xperia Play Android Development] bubblegumballoon:
Heck it would be worth it just for the sonic adventure games! :)
[Xperia Play Android Development] crono141:
I tell you, I'd almost kill for a NDS emulator. It's the only nintendo handheld that I own that is not emulated in android. I understand the desire for Dreamcast emu, but I personally feel that an NDS emulator would be far more popular.
[Xperia Play Android Development] bubblegumballoon:
There are already 2 NDS emulators, check out my emulator guide: http://xdaforums.com/showthread.php?t=1326087

But be warned they are very very very slow and theres no official way to get them anymore.
[Xperia Play Android Development] crono141:
Which is the problem. There are no complete or functional emulators. And as you said, no official way to get them.
[Xperia Play Android Development] paulscode:
Not looking at the sourcecode, I would speculate that the reason for the slowness is they are using a "pure interpreter" type of strategy, which is doable for something like the original NES, but not nearly acceptable for more sophisticated systems. It would really take an assembly savant like Ari64 to write a dynamic recompiler before emulation on Android would be doable. Compared to the N64 dynarec this would be considerably simpler to write, but still beyond my capabilities ;D
[Xperia Play Android Development] b15love:
What time frame do you think we will be able to start using pluggins and texture packs?
[Xperia Play Android Development] mehdi.moha:
hey master ,

you know , we all know that you have the knowledge to release it :D

N D S :D emolator
[Xperia Play Android Development] paulscode:
You can use plug-ins now (although the only ones built for ARM right now are mine and Yongzh's) The plug-ins can be set by editing the file [sdcard]/app-data/paulscode.android.mupen64plus/mupen64plus.cfg. However, you probably won't have any luck using Yongzh's N64oid plug-ins in Mupen64Plus AE, because he altered the official Mupen64Plus 2.0 API for whatever reason (I'd guess to protect the closed-source components, or out of some necessity related to the removal of SDL or the JNI linkage).

I'm not sure about the texture packs question. That's a special function of the video plug-in, right? If so, then I'll have to port another video plug-in to GLES1/2, (maybe Rice Video?), because gles2n64 does not have this capability. No specific time-lines for that, though (porting a couple of video plug-ins is high on my priority list after finishing the GUI).
[Xperia Play Android Development] captain67:
Nice to see an emu dev on the play forums. The rest are all enigmatic and never chat with us. I've got high expectations of this emulator, after reading all the posts. High performance n64 gaming with the touch sticks would be a dream come true.

Sent from the best phone ever
[Xperia Play Android Development] Cat_On_Droid:
by next year , we should have a fully working Touch pad gaming for PSone games and N64!!

Also@ good idea to join XDA forums Paul! Will defintely spark more interest :)
[Xperia Play Android Development] bubblegumballoon:
Just a little update. In a new test the emulator now has things like fast forward and slow motion. :)
[Xperia Play Android Development] b15love:
yes, it requires the Rice Video pluggin and then a texture pack for which ever game your playing. Heres a link of some texture packs (hi-res, retexture, etc. etc..)

http://www.emutalk.net/forums/110-N64-Textures

The make the games look so purdy
[Xperia Play Android Development] paulscode:
Kris has nearly finished porting Rice Video to GLES2 (a couple of bugs left, but he's done some amazing work). I'm in the process of porting his code to Android (relatively simple, just requires adding JNI linkage to handle the EGL stuff from Java).
[Xperia Play Android Development] AndroHero:
Are you joking? The dreamcast had some of the best and innovative games to date :o
[Xperia Play Android Development] kupo5131:
When you get the DreamCast emu working will you be able to make a VMU emu that will tie in with the save data? That would be absolutely amazing.
[Xperia Play Android Development] Logseman:
Let the poor sod finish the N64 emulator first :D

piano piano si anda lontano.
[Xperia Play Android Development] mehdi.moha:
:confused:the first page (( download link has been changed ))
[Xperia Play Android Development] bubblegumballoon:
Pauls been drastically changing the forums recently and the thread keeps being changed so instead of linking directly to the thread now im just linking to the forums (stops the link from breaking).
[Xperia Play Android Development] captain67:
I second this motion. One person can only do so much, and he isn't getting paid for it.

Also, is it possible to map the right stick to be like the C buttons?

Sent from the best phone ever
[Xperia Play Android Development] bubblegumballoon:
I suppose a mod could move it but ive posted stuff in that section before and its so active threads just get blown off the front page so nobody sees it. :/
[Xperia Play Android Development] paulscode:
The right touchpad has the C buttons mapped to it in the layout I wrote for the test, but you can map any button to anywhere on the touchpad (the layout is completely customizable using the pad.ini file and color mask images)
[Xperia Play Android Development] captain67:
All we need now is a nice gui and some extra speed and it'll be perfect

Sent from the best phone ever
[Xperia Play Android Development] bubblegumballoon:
GUI is being worked on. As for extra speed theres always the option to overclock for now but a decent amount of games already run fine at stock speed.
[Xperia Play Android Development] ermacwins:
I might create thread to get more exposure and maybe some people can help in some shape and form.
[Xperia Play Android Development] juxtapose519:
I've got mine overclocked to 1.7GHz and it runs every game I've thrown at it smooth as pancakes.
[Xperia Play Android Development] captain67:
How long can you play on a single charge with it clocked so high?

Sent from the best phone ever
[Xperia Play Android Development] Dyelon:
Can't wait for GUI
[Xperia Play Android Development] bubblegumballoon:
I will be sure to post here when its done unless paul posts it first haha. :)
[Xperia Play Android Development] silvacrest:
i no the golden rule is not to ask for a ETA so i will just ask in terms of percentages how far are you with the gui? 30%? 40%?

sorry if this is equally annoying as asking for a ETA :)
[Xperia Play Android Development] bubblegumballoon:
Im not the one developing the emulator haha paul lamb is the creator (known as paulscode here) anyway about a week ago he said it would take about 2 weeks to finish the gui assuming theres no major complications, so my best guess is another 1 - 2 weeks. This is just purely speculation so please dont take my guess as a fact. :P
[Xperia Play Android Development] paulscode:
I'd still say thats about right. It's taking a bit longer to get to the testing phase than I anticipated, so there is of course the possibility that I get it working on my phone but it has problems on other phones which take a while to debug. Hopefully not.
[Xperia Play Android Development] bubblegumballoon:
Just a little update, theres been some new tests which allow you to suspend and resume the emulator. This means you can quit the app with the home button and touch on its icon in the status bar to resume or you can press menu and close while in the emulator to close it completely.
[Xperia Play Android Development] IE-coRe:
This alredy is some kind of gui.....xD
[Xperia Play Android Development] bubblegumballoon:
haha yeah kind of, pressing the menu key brings up a few options but thats not the proper UI yet just the in game UI. Choosing menu just crashes the emulator since there is no menu yet but its coming eventually. :)
[Xperia Play Android Development] ermacwins:
Made thread here for more support and attention http://xdaforums.com/showthread.php?t=1349052

Also will there be support for high-res textures?

I got a Galaxy S2 for testing if need be
[Xperia Play Android Development] paulscode:
This is one of items on my list. Once Kris' GLES2Rice video plug-in is debugged and running well, I'll uncomment and debug the high-res code (if he doesn't get to it first).
[Xperia Play Android Development] loyal4ever:
I just test it with Zelda oot, the touchpad works great, controlling Link feels just right. Even better than Mario64, it could be because the game original control design more refined than mario.

ofcourse, there are some texture and sound glitches for now, eventually everything can be fixed and become better with time.

I really want to thank you Paul for your hardwork on this and bubblegumballoon for testing and maintaining this thread.

also not forgetting to thank BuckM for suggesting a perfect values. :)
[Xperia Play Android Development] bubblegumballoon:
That link goes straight back to here? :s
[Xperia Play Android Development] ermacwins:
Thanks thats good to know. I tried it on N64oid with Zelda OOT it works then it just returns to the rom selection. Not sure if its because of Cutsom Rom

oops my bad, was in a hurry. Fixed
[Xperia Play Android Development] bubblegumballoon:
Just a little heads up, Pauls nearly done coding the GUI. It shouldn't be long until to GUI version of the emulator is finished. :)
[Xperia Play Android Development] sonicfreak360:
Makes me want to thank every single post Paul made!
[Xperia Play Android Development] Nhialor:
Paul, on your forum it says

I will NOT be actively maintaining a branch of the app supporting Xperia Play touch-pad input. Therefore, this example will not benefit from updates and bug-fixes in future builds.

Is this still true? If you fully implement controls as you have done, what stops you maintaining them? Surely if they're built in, it shouldn't be too hard to keep them in!?
[Xperia Play Android Development] toxicpaulution:
Well I'm not having any luck with this I did as it said and I am using a play
[Xperia Play Android Development] bubblegumballoon:
Any build with Xperia touch pad support won't work on versions of android lower than 2.3 and it's tedious to create multiple builds all the time especially in the beta testing phase when new build are created very often (I remember in the early stages of the development there was about 10- 20 builds per day being made), that's why there are two separate versions.

Paul said he will post a new build for the Xperia play once the GUI is does so we will have the benefit of both the touch pads and the GUI. There are also instructions on the OP of the Mupen thread on Paul's forum which tell you how to add Xperia play controls to all future build yourself in case he doesn't, it's not too complicated and if you know how to comple code then you can do it pretty easily.
[Xperia Play Android Development] bubblegumballoon:
What are you having trouble with?
[Xperia Play Android Development] toxicpaulution:
I can't get the analog stick mapped correctly :/