• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Dang. I'm sure the optimistic can run it. I use FPse and frogger works well. Strange, no n64oid.

I thought it was strange too. I can run most games on FPse at 25-35 frames per second. From what Ive read, the person who made PSX4Droid also made N64oid and the guy has a tendacy of half-assing his apps :( I would love to see the FPse guys make a competing N64 emulator.:D
 
  • Like
Reactions: VioletLinked
Upvote 0
I could not get Nesoid to work but I did get TigerNES to work. :)


Nesoid and all other emulators except the n64oid and all tiger emulators work for LG optimus s. All of the __oid ones work other than n64oid. Psx4droid works fine as well as FPse. Why no n64oid? I don't know. If anyone can get it working or installed, PLEASE tell me.
 
Upvote 0
Try this if your phone is rooted, use Root Explorer or a similar app to copy the n64oid apk to the /system/app/ folder, then change the permissions to rw-r--r-- (make sure you are mounted as r/w, you can do this by touching the Mount R/W button on the upper right). Then go back to your SD card and rename the original apk to com.androidemu.n64-1.apk, then move that to the /data/app/ and change the permissions once again to rw-r--r--, then reboot your phone, congrats, you installed it, but when I select a rom to play, I get a force close unfortunately, I'm using the LG Vortex, but I think the Optimus S and the Vortex are just about the same phone. See if N64oid will work after you did this.
 
  • Like
Reactions: VioletLinked
Upvote 0
It Still won't work.
I think I know what it is however.

The N64oid System requirements

- Android 2.0 or above
- ARMv7 compatible CPU
- OpenGL-ES 2.0

Here is what LG Optimus S has:

- Android 2.2
- ARMv6 compatible CPU (He have no ARMv7)
- OpenGL-ES 2.0 (I think so)

I got the source code. If someone can recompile it or something and make it work, I'll worship you forever.

Here is Source:

http://sourceforge.net/projects/n64oid/
 
Upvote 0
For anyone who is on an older pre-ARM7a device, here are the core and video plug-ins compiled for ARM5 and later (can't guarantee they will work, since I don't have an ARM5 device to test them on myself):

libmupen64plus-core-ARM5 (the sourcecode)
libgles2n64-ARM5 (sourcecode included in previous link)

Unfortunately, since half of N64oid is closed-source, I couldn't put together a complete APK package. To use this new library, first you must install N64oid (tested on version 2.0.3, no idea if it works on other versions). You must also have your device rooted, and you will need a terminal app (the free "Terminal Emulator" from the Android Market works fine). Download the above files (the Android browser app may stick a ".txt" extension on the end of them for some reason, don't worry about it). Then open your terminal and get root access. Navigate to your app install folder. For my DroidX, this is /data/data, but it may be different for other devices. You'll have to look around if its not there. Enter the n64oid library directory, backup the current core and video libraries, and copy the downloaded files (on my DroidX they are in /mnt/sdcard/download, but it may be different on other devices). Rename them libmupen64plus-core.so and libgles2n64.so. Then change their permissions to make them executable:
Code:
su
cd /data/data
cd com.androidemu.n64/lib
mv libmupen64plus-core.so libmupen64plus-core-BACKUP.so
mv libgles3n64.so libgles2n64-BACKUP.so
cp /mnt/sdcard/download/libmupen64plus-core-ARM5.txt ./libmupen64plus-core.so
chmod 755 libmupen64plus-core.so
cp /mnt/sdcard/download/libgles2n64-ARM5.txt ./libgles2n64.so
chmod 755 libgles2n64.so
exit
exit
Obviously, if these libraries break N64oid, you can delete them and rename the backups you made earlier, like so:
Code:
rm libmupen64plus-core.so
mv libmupen64plus-core-BACKUP.so libmupen64plus-core.so
rm libgles2n64.so
mv libgles2n64-BACKUP.so libgles2n64.so
For folks with ARM7a devices, here is Yongzh's core library (based on the most recent sources he posted a couple days ago) upgraded to the latest version of Ari64's dynarec (will improve overall performance and fix crashes on some ROMs):

libmupen64plus-core-ARM7 (the sourcecode)

Installation of this one is the same as above, except you are only replacing one library instead of two:
Code:
su
cd /data/data
cd com.androidemu.n64/lib
mv libmupen64plus-core.so libmupen64plus-core-BACKUP.so
cp /mnt/sdcard/download/libmupen64plus-core-ARM7.txt ./libmupen64plus-core.so
chmod 755 libmupen64plus-core.so
exit
exit
I personally avoided rooting my phone until only a couple days ago, because doing so voids the warranty and opens a rather sizeable security hole, but in the end I kind of needed to do this to get a working core with the latest dynarec for comparison. That being said, if you are not comfortable with rooting your own device, if you want to help me test my project, or you just don't want to pay the 5 bucks for N64oid, feel free to follow my project, which I intend to place on the market for free once its complete.
 
Upvote 0
For anyone who is on an older pre-ARM7a device, here are the core and video plug-ins compiled for ARM5 and later (can't guarantee they will work, since I don't have an ARM5 device to test them on myself):

libmupen64plus-core-ARM5 (the sourcecode)
libgles2n64-ARM5 (sourcecode included in previous link)

Unfortunately, since half of N64oid is closed-source, I couldn't put together a complete APK package. To use this new library, first you must install N64oid (tested on version 2.0.3, no idea if it works on other versions). You must also have your device rooted, and you will need a terminal app (the free "Terminal Emulator" from the Android Market works fine). Download the above files (the Android browser app may stick a ".txt" extension on the end of them for some reason, don't worry about it). Then open your terminal and get root access. Navigate to your app install folder. For my DroidX, this is /data/data, but it may be different for other devices. You'll have to look around if its not there. Enter the n64oid library directory, backup the current core and video libraries, and copy the downloaded files (on my DroidX they are in /mnt/sdcard/download, but it may be different on other devices). Rename them libmupen64plus-core.so and libgles2n64.so. Then change their permissions to make them executable:
Code:
su
cd /data/data
cd com.androidemu.n64/lib
mv libmupen64plus-core.so libmupen64plus-core-BACKUP.so
mv libgles3n64.so libgles2n64-BACKUP.so
cp /mnt/sdcard/download/libmupen64plus-core-ARM5.txt ./libmupen64plus-core.so
chmod 755 libmupen64plus-core.so
cp /mnt/sdcard/download/libgles2n64-ARM5.txt ./libgles2n64.so
chmod 755 libgles2n64.so
exit
exit
Obviously, if these libraries break N64oid, you can delete them and rename the backups you made earlier, like so:
Code:
rm libmupen64plus-core.so
mv libmupen64plus-core-BACKUP.so libmupen64plus-core.so
rm libgles2n64.so
mv libgles2n64-BACKUP.so libgles2n64.so
For folks with ARM7a devices, here is Yongzh's core library (based on the most recent sources he posted a couple days ago) upgraded to the latest version of Ari64's dynarec (will improve overall performance and fix crashes on some ROMs):

libmupen64plus-core-ARM7 (the sourcecode)

Installation of this one is the same as above, except you are only replacing one library instead of two:
Code:
su
cd /data/data
cd com.androidemu.n64/lib
mv libmupen64plus-core.so libmupen64plus-core-BACKUP.so
cp /mnt/sdcard/download/libmupen64plus-core-ARM7.txt ./libmupen64plus-core.so
chmod 755 libmupen64plus-core.so
exit
exit

I personally avoided rooting my phone until only a couple days ago, because doing so voids the warranty and opens a rather sizeable security hole, but in the end I kind of needed to do this to get a working core with the latest dynarec for comparison. That being said, if you are not comfortable with rooting your own device, if you want to help me test my project, or you just don't want to pay the 5 bucks for N64oid, feel free to follow my project, which I intend to place on the market for free once its complete.


Paul, first let me say, YOU ROCK. You have coded minecraft, emulators, games, websites... I mean holy!

I did finally get my LG Optimus s rooted. I overclocked it to 600 MHz, and aperently thats as high as all the overclocking apps can go... (WHHHHYYY???)

Oh, and I suck at rooting and code and stuff... so Im outta luck. I though n64oid was 100% open...

And yes, I do want to test out Mupen64Plus AE, but will it work on pre ARM 7a devices? I'd love to test it!

Please, send me an apk if possible!
 
Upvote 0
It'll be compiled for compatibility back to ARM5, an optimized version for ARM7A, and a version for x86. That should cover 95% of android devices out there (only limit being the GLES2 requirement for the video plug-in until a GLES1 version (probably of Arachnoid) is developed. That being said, I have no idea how smoothly it will run on 600MHz. The audio would probably be skippy, but probably playable. It'll be interesting to see how it does on some of these devices. Anyway, it is nearly complete, but I'm still struggling with the video plug-in (I'm not much of a GL guru, sadly).
 
  • Like
Reactions: VioletLinked
Upvote 0
It'll be compiled for compatibility back to ARM5, an optimized version for ARM7A, and a version for x86. That should cover 95% of android devices out there (only limit being the GLES2 requirement for the video plug-in until a GLES1 version (probably of Arachnoid) is developed. That being said, I have no idea how smoothly it will run on 600MHz. The audio would probably be skippy, but probably playable. It'll be interesting to see how it does on some of these devices. Anyway, it is nearly complete, but I'm still struggling with the video plug-in (I'm not much of a GL guru, sadly).


Dude, thats awesome! When will it be released?
Can you give a date, and if possible send me a testing prototype?
Paul, You rock man! Good luck with your Future coding! :D
 
Upvote 0
Dude, thats awesome! When will it be released?
Can you give a date, and if possible send me a testing prototype?
For testing, I can't be much more specific on a date than to say "hopefully soon" (a month ago I was positive it would only take a couple days to track down the problem, but I still haven't yet). The final roadblock is that I don't know what's wrong with the video plug-in. No video plug-in is kind of a deal breaker for anyone who doesn't like to "play it by ear" so to speak :D As for a market release, the last component I'll need to code is a front-end (so the user doesn't have to play around in the config files just to control the emulator, or have a wireless joystick for touch-screen only devices). The front-end will be coded in Java, which I'm very comfortable with, so it shouldn't take more than a month or so to finish it once I can actually start working on it.
 
Upvote 0
Once this emu gets up and running on this phone, I'll most likely say "screw android gaming". My biggest issue with android gaming on this phone is the lack of SD support. I can't really enjoy games like I want to because I'm so busy having to shuffle my apps around. :( Before I forget, control mapping should be easy on this phone. A and B can be the search and back buttons. C and the analog can be on the screen and Z,L and R can be mapped to the volume camera and speech buttons
 
Upvote 0
No invitation needed. Just visit my Mupen64Plus AE project page. The latest "official builds" will be posted there.

Progress update: I'm working on fixing the Vec4 optimization, which is the cause of the shader bug on phones without Neon. I hope to get that fixed in the next couple of days - should be the last major bug to fix before starting on a nice user-friendly GUI (I know everyone is tired of playing in the config files, haha)
 
Upvote 0
Thanks but how am I supppose to choose which rom I want to play it only chooses super m ario

Jesus christ. Read the frkin fourm!

Whatever.
Its easy! Switch the Mario.n64 file with a diffrent rom, and change the name to Mario.n64,
In you sd/app-data/paulscode.../roms folder.

So if you wanna play smash bros..

First. Download the rom file online. Then, unzip the file. It should be something like this:

Super_smash.z64 or similar.
Rename that to Mario.n64.
Replace the existing Mario.n64 in your Tom's folder.

Boot up mupen ae, and play!
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones