Emulator Issues #4143

ARMv7 Dolphin Support

Added by jad.padriga over 9 years ago.

% Done:


Operating system:
Issue type:
Feature request
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Hey can you make a Dolphin Emulator for Andriod! Please!

Related issues

Blocked by Emulator - Emulator Issues #5314: OpenGL ES 3.0 back-endFixed


#1 Updated by DimitriPilot3 over 9 years ago

  • Status changed from New to Questionable

I highly doubt it'll be able to run most games at acceptable speeds... And who would spend a lot of time on such a port?

#2 Updated by shadowflash over 9 years ago

I think this isn't a right place to request ports. And what is Andriod ? Android ?
Dolphin depends on x86 right now, even more, it requires SSE2 instructions. Also minimum system requirements are far above anything current portable devices can offer.

#3 Updated by Xtreme2damax over 9 years ago

Lol, this has to be the most asinine request I've seen. Dolphin on Android, seriously? Not only would it be slow as molasses, Dolphin also heavily depends on the x86/x86-64 and SSE2 instruction set. I knew when someone mentioned a port of Dolphin to PS3, someone would show up and make an even more ridiculous request. While we're at it, why not Dolphin on the NES, SNES, Game Gear, Gameboy, Sega Genesis, Sega Saturn, Sega Dreamcast, Playstation, Playstation 2, Xbox, PSP, Nintendo DS?

Also this is an issue tracker, to post bugs and issues with the emulator, not for feature requests or to request ports. For that and everything else, there is a forum believe it or not:

#4 Updated by MofoMan2000 over 9 years ago

I wonder if porting to XBox 360 would actually be feasible… It would be more likely than this.

But Android is a good platform, just not one that's cut out for something as intense as this. I'll star the issue because I have an Android and I'd love to see this tried. My hopes aren't sky high though.

Also, not for feature requests? Then it's time to go through the entire issue tracker and mark every single issue marked "Enhancement" invalid.

#5 Updated by Xtreme2damax over 9 years ago

"Also, not for feature requests? Then it's time to go through the entire issue tracker and mark every single issue marked "Enhancement" invalid."

You misunderstand, the enhancements you are referring to isn't exactly the same as random/ridiculous feature requests. The issue tracker isn't a forum and such requests should be posted on the forum. There's a reason it's called an "issue tracker" and not an "issue, feature request tracker, and support forum". If people just start requesting features, stupid/random requests the developers are going to get pissed and tell them to post on the forum and not waste their time.

Not only that, the guy didn't even fill out the template properly, but how could he since there is no issue?

No way Android would be able to handle something like Dolphin, not within the next 5 - 10 years at least, possibly more and that is if the Android platform ever becomes as powerful as current PC hardware in the near future.

Xbox 360 and PS3 may be possible, may is the keyword and so far no more has been heard about the Dolphin PS3 port that was supposedly being worked on.

#6 Updated by MofoMan2000 over 9 years ago

I'm not saying it's not a ridiculous idea and that it'll magically work at playable speeds. I'm just saying it would be kinda neat.

#7 Updated by Xtreme2damax over 9 years ago

Keep in mind that the average user doesn't care about the novelty, they just care about playing games. If this were to ever happen, can you imagine the amount of users complaining about poor speed, telling them there is no way to solve the issue with poor speed due to hardware limitations?

Yes it would be cool, but most users aren't going to care about the coolness factor except for a relatively small amount of users.

It also comes down can the hardware be emulated, will it support emulating the features of the GC/Wii? The PC already supports these features, so it's just a matter of "translating" the code/instructions that the PC can understand and process.

#8 Updated by shadowflash over 9 years ago

"While we're at it, why not Dolphin on the NES, SNES, Game Gear, Gameboy, Sega Genesis, Sega Saturn, Sega Dreamcast, Playstation, Playstation 2, Xbox, PSP, Nintendo DS?"

It's funny but Xbox port is somewhat possible (will require to rewrite a lot of code to remove SSE2 dependence, and ) - i think it will be possible to run something like Gradius ReBirth (the fastest game on dolphin yet, which goes up to 420fps on A64 3800+) at 10-20 fps on 733MHz Celeron Coppermine, which is an XBox CPU. At least i remember early versions of Dolphin running BAM3K at over 9000 fps on AthlonXP 3200+ :D

Anyway, i don't think there's anyone going to waste time porting Dolphin to Android or XBox or microwave oven controller anytime soon.

#9 Updated by Anonymous over 9 years ago

  • Status changed from Questionable to Invalid

this is not a bug. try sending a dev cookies instead.

#10 Updated by nimeshchanchani about 9 years ago

With quad core processors in clear site... I think porting on android is not a bad idea at all!!

#11 Updated by florian98.rg about 9 years ago

There is no mobile phone with 4 Cores...
And there won't be one until 2020

#12 Updated by MofoMan2000 about 9 years ago

Don't forget to port all the code to Java! That'll be Fuuuuuuun!

#13 Updated by nimeshchanchani about 9 years ago

2020? its already there! both Qualcomm and NVDIA and releasing quad core processors for tablets by mid year 2011, Motorola Atrix already uses a dual core!

and you dont always use java for android you can use native development in c++ as well usind the android NDK

#14 Updated by sl1nk3.s about 9 years ago

Even though dual core ARM and even quad core ARM processors are around the corner, porting Dolphin to Android/ARM would require a huge amount of work and would probably be super slow even on the fastest ARM core you could get in a year or two.
What needs to be done is :
- Write an ARM JIT core from scratch. (currently only x86/64 is supported)
- Complete rewrite of the graphics plugin using OpenGL ES2.
- Memory optimizations and GUI.

Also, this is an issue tracker not a forum, and this clearly isn't an issue but a feature request, so please talk about whatever you want on the forums but keep this place clean.

#15 Updated by whatisajimmy over 8 years ago

For what it's worth, now that Win8 is going to see a shift towards ARM processing without x64/x86 emulation, it would be worthwhile to write an ARM JIT core from scratch anyway... Just a thought.

#16 Updated by parlane over 8 years ago


#17 Updated by ascensionsystems over 8 years ago

In regards to what sl1nk3 said, 2 of the 3 items listed as required are not a big deal whatsoever. GLES2 porting from the current GL back end would require virtually no work, unless they've used a lot of legacy GL calls like immediate mode rendering or quads. Everything else would be simply changing calls using ints or doubles to floats. As far as the android GUI that's pretty easy. Since this would be compiled as a native APP you basically just need to pass the GL context to the native code through JNI and as for the menu GUI and stuff you can basically create those types of interfaces interactively with the android dev plugin for eclipse so those two points are minor.

#18 Updated by NeoBrainX over 8 years ago

We ARE using a lot of legacy GL calls though...

#19 Updated by sepp256 over 8 years ago

It would be worthwhile to add GLES2 as a new backend for use in future portable targets. If someone is interested in such an effort then good, but it's not going to pay off immediately until portable targets can handle GC/Wii emulation.

#20 Updated by Zamadatix almost 8 years ago

It can be funny to look online at people saying 1 or 2 years ago that "devices won't be quad core for 10 years" or "you need 5-10 the power for it to be smooth and you wont see that for too long to care about" . Right now I am on a 350 dollar tablet that blasts most of these predictions away less than 2 years after they were made and 6 months from now the 5x faster replacement will be released. Current devices are already on the border of being fast enough to emulate most gamecube games and development takes a lot of time, power is not an issue however lack of developers is a very valid one.

#21 Updated by pkooiman4 over 7 years ago

Can the history of this issue be moved to the forum and removed here?
That being said, the topic is irresistible.
I am absolutely amazed how well the n64 runs on my phone. I realize the hardware is 17 years old. My how time flies.The power of the xbox has been reduced to something like the $30 raspberry pi.

The Gamecube will be 17 in less than 6. In less than 17 years, microprocessors will the same price as paper is today and would probably be able to play wii u games.

#22 Updated by lloyd over 7 years ago

Dolphin on the Ouya would be pretty badass. Just sayin'.

#23 Updated by Sonicadvance1 over 7 years ago

To get reasonable speed, we need Uniform Buffer Objects which is only supported by OpenGL ES 3 hardware. So Ouya getting good speed is out of the question.
GPU hardware required is Adreno 320, Mali-T6xx, and PowerVR6.

#24 Updated by Sonicadvance1 over 7 years ago

  • Status changed from Invalid to Work started
  • Issue type set to Feature request
  • Priority set to Normal
  • Category changed from ppc to gfx
  • Milestone set to Future

This has been started for quite a while now.

#25 Updated by Sonicadvance1 over 7 years ago

  • Milestone changed from Future to 4.0

#26 Updated by Sonicadvance1 over 7 years ago

Done with 692e39d1bbe1

#27 Updated by Sonicadvance1 over 7 years ago

  • Status changed from Work started to Fixed

#28 Updated by diegojp955 almost 7 years ago

wow.. see all those comments...
i think deserves a apology...

Also available in: Atom PDF