A list of the reported bugs will be added here so the developers can easily see what bugs are currently in the Emulator.When reporting bugs please state your Phone and Version of N64oid you are using.

Bugs on 2.6All phones:Games that are unplayable :Blast Corps - Crashes at opening screenBomberman64 - Black Screen on loadBanjo Tooie - Crashes after Pressing start at the introDonkey Kong 64 - Clipping issues mean you can walk through anything and everything in the game, makes the game unplayable.Paper Mario - works until you get done with the first chapter. Then you get a black screen.Pokemon Puzzle - League doesn't load the opening video.Rogue Squadron - Unplayable - Can get to craft selection but never into the actual maps.Zelda Majoras Mask - In the menu when you try to enter the Bomber's Notebook you end up with a black screen.Super Mario 64 -When entering the water (eg. Jolly Roger Bay level) the water surface texture become pixelate. - Fixed in version 2.6Zelda Ocarina of Time - In the Kokiri forest depending on which angle you're looking at the water, the surface texture happen to move faster than it normaly does. Maybe this is related to the surface texture bug in mario 64, or maybe not!

Xperia Play R800 Verizon Wireless model (Needs to be confirmed)No Multi Touch Support - (Read More Here) Fixed in 2.5

Zelda OOT:In the Kokiri forest depending on which angle you're looking at the water, the surface texture happen to move faster than it normaly does. Maybe this is related to the surface texture bug in mario 64, or maybe not!

EDIT: It's not related to the surface texture bug in mario 64 because this was fix in the 2.6 version and the water surface texture still move faster in the kokiri forest.

Once again depending on the angle you're looking at, you sometimes can see the torch halo through walls. Here's a picture showing the bug:

Zelda MM:In the menu when you try to enter the Bomber's Notebook you end up with a black screen.

Batman Beyond return of the Joker: go back to game listDonald Duck Quack Attack:go back to game listExcitebike64: first images load, then black screen and commands freeze before the real menu

Working but some problems:Bass Hunter 64: keeps on flickering even if there's no frameskip at allStar Wars Shadow of the empire: flickers as soon as frameskip is not 0...and would be perfectly smooth with frameskip set on 3 Playable at a fair speed without any frameskip only on on overclocked dual core

I posted about this problem with smallest control scheme and non working B button in mario karts, it doesnt work during race, works in menu, so someone could check this on his phone but dont be fooled that it works in menu.Just tested it again now, you cant drive backwards, B doesnt work when using small button scheme.

OK just remove this bug, i dont know why but now i need to press "down" on analog joy along with B to drive backwards so looks like B was working afterall, i remember i didnt had to press B or am i dreaming ? I dont know but i could swear i was using only B without any direction to drive backwards.So everything works ok, B button non working was just my dumb mistake.

2blackb wrote:OK just remove this bug, i dont know why but now i need to press "down" on analog joy along with B to drive backwards so looks like B was working afterall, i remember i didnt had to press B or am i dreaming ? I dont know but i could swear i was using only B without any direction to drive backwards.So everything works ok, B button non working was just my dumb mistake.

In zelda oot (v.2.6) In dodongo's cavern boss battle when i press R to use shield after that everything (link, n64 buttons..) disappears and the game becomes unplayable. I had to use cheats to defeat the boss, but this problem still exists..even when i choose different savegame..

Dude wrote:In zelda oot (v.2.6) In dodongo's cavern boss battle when i press R to use shield after that everything (link, n64 buttons..) disappears and the game becomes unplayable. I had to use cheats to defeat the boss, but this problem still exists..even when i choose different savegame..

Strange, on my device, I went through this point without any problem....................... different GPU maybe?

(I've done about 3/4 of the game on my HTC Sensation without even using one of my bluetooth gamepads^^)

Dude wrote:In zelda oot (v.2.6) In dodongo's cavern boss battle when i press R to use shield after that everything (link, n64 buttons..) disappears and the game becomes unplayable. I had to use cheats to defeat the boss, but this problem still exists..even when i choose different savegame..

Strange, on my device, I went through this point without any problem....................... different GPU maybe?

(I've done about 3/4 of the game on my HTC Sensation without even using one of my bluetooth gamepads^^)

Yeah very weird problem because everything works fine before I use my shield! And now this problem is in every savegame. I also tried rebooting my phone(SGS2).. no effectmaybe i have to delete savegames and re-install the app...

Pokemon Stadium 2 is playable, only until I click on either Marill or Slowbro in the main menu. After that, it slows down a bit, glitches and force-closes shortly after that. When I somehow make it further than that (such as an actual pokemon battle), the pokemon don't show up in the "player vs cpu" screen (not a big issue). When trying to select pokemon to be used in battle, the top half of the screen is black (hiding my pokemon) until i press the "R" button and it displays for a brief moment then goes away. I have to repeatedly press "R" to see my pokemon.Battles work fine, when I'm lucky enough to get to that point. I've tried all frameskip increments, even turning off the sound, but it still force closes at random (once, I got to the second battle of the challenge cup before crash).

Phone Model: Kyocera Echo, Most recent N64oid version (downloaded from site yesterday)It plays Super Mario 64 and LoZ: Ocarina of Time flawlessly.

In paper mario, in various places (often where there is darkness or flickering graphics otherwise), the graphics are very flickering, often they seem to flicker between the foreground and the background. This is very evident later in dry dry ruins, up to the point quite in the end of the level when i take a super block and the game freezes and force closes.

This problem originated in 2.6, where when I went to save a game in the emulator, it wouldn't save. So I dropped down to 2.5 and everything was workiing fine, until today. Now when I go to save my game, on any rom. It doesn't create it. Help would be appreciated.

IshV1982 wrote:This problem originated in 2.6, where when I went to save a game in the emulator, it wouldn't save. So I dropped down to 2.5 and everything was workiing fine, until today. Now when I go to save my game, on any rom. It doesn't create it. Help would be appreciated.

Save state or in game save?What phone?Rooted?If you are rooted, what rom?

HiJust like to say that n64oid is not closing properly after I exit the program (new update 2.6.2)

I open the menu, press 'close' to go back to the rom list, then press the back button - previously this would close the program. Now it exits the program to the home screen but n64oid is still runnin and I have to force close it.

I have had this problem before on a previous version of n64oid, but not for some time.

My phone is an HTC Desire Hd.

(While I'm posting though, thanks for the transparency slider for the control pad - much better!)

hi, first I would like to say thank you for this awesome emulator. The reason why I post this is because I don't know if this bug is phone related or emulator related. See here is my problem, I start the emulator and run OoT all graphics are fine but the sound is kinda off its like ticking? you know like the song is chopped on a thousand mini parts. I love playing mario 64 on the emulator but zelda OoT is my fav n64 game and I would love to be able to hear it without it laggin or being chopped. my device is an HTC Inspire 4G. Any tips on solving this issue is much appreciated.

In paper mario, in various places (often where there is darkness or flickering graphics otherwise), the graphics are very flickering, often they seem to flicker between the foreground and the background. This is very evident later in dry dry ruins, up to the point quite in the end of the level when i take a super block and the game freezes and force closes.

I'm using a non-rooted samsung galaxy s ii

reported by: Mazza

I have the same Problem, when I take the Super Block, the game slows down enormeously and finally force closes...