>>55001324

Doesn't matter, mupen64 is shit even on high end devices.

>>55001377
Yes, I debated which emulator to depict since all of them have their problems. Still, it's one that lets you kick the rendering resolution up and supports savestates so that puts it ahead of the likes of reicast.

>>55001324
CPU is more important for emulation.

>>55001324
CPU, I tried emulating a PS2 using a Sandy Vag Pentium system.

It sucked.

>>55001324
They're both really important for emulation on mobile since the CPUs suck total ass and throttle 24/7 and some of the GPUs on Android have the worst drivers imaginable.

>>55001324
Using emulators on a fucking smartphone must be a horrible experience.

>>55001324
My old HTC desire 500 could run N64 without problems, so any modern phone will do.
Now running a moto x play

>>55005014
Anything made before 2000 is fine. GameCube, Wii, PS2 are impossible on current mobile hardware. Most DS games are kinda on the edge of being playable. Mupen64 runs flawlessly on my phone (Qualcomm Snapdragon 810)

>>55005304
>flawlessly
Why the fuck you lying?

>>55005304
It's not just the performance. It will probably drain your battery like a bitch too. And the controls are horrible. Don't tell me they are not, they absolutely are.

both matter you utter mong, you need a CPU for decent JIT, you also need a good GPU to render the scene.

>>55005304
try using a device worth more than $200, the Tegra K1 can emulate ds, psp, ps1, ps2, gamecube, without much slowdown. Also use RetroArch