Getting It Running
Download the latest unstable build of Dolphin from their official site. The stable branch is fine for casual use, but the unstable version has better hardware acceleration and fixes that tend to matter on mobile chips. Install it on your phone, point it at a folder where you've dumped your GameCube and Wii ISO files, and try launching something. Mario Galaxy should work on most modern phones. Some games won't. That's the reality. The process is straightforward once you have the emulator set up. Load a disc image, configure your controls, and go. The default input settings are garbage on touchscreens though, so spend ten minutes remapping. Tap into the control layout editor and assign the analog stick to the left half of the screen, face buttons to the right. Everything else can stay near default. It takes about five minutes to get comfortable, maybe twenty if you're picky about response time. I ran into a specific issue with The Wind Waker HD. The game would freeze solid about forty seconds into the opening sequence every single time on my Pixel 7. Not a crash to desktop, just a complete hang. No error message, no log entry that made sense. The fix was going into the emulator's GPU settings, turning off the "Skip EFB Access From CPU" option, and setting the internal resolution to 1x instead of 2x. That dropped performance slightly but made the game playable. I found this after trying half a dozen forum suggestions that did absolutely nothing.
Here's the thing about Wii Classics specifically. Those aren't a separate emulation layer. Dolphin handles them the same way it handles any Wii disc. The classification exists because Nintendo re-released a bunch of GameCube games as cheaper titles on the Wii eShop, but the code running inside the emulator doesn't care about that distinction. You point Dolphin at a Super Mario Sunshine ISO labeled as a Wii Classic and it runs exactly the same as if it were a disc image ripped from a GameCube. The only difference might be region locks or minor anti-piracy checks that sometimes trip over when you've got a homebrew menu involved, and even then it's rare.
Hardware Requirements
GameCube and Wii emulation on ARM is not forgiving. Your phone needs a Snapdragon 8 Gen 1 or better, or an equivalent MediaTek Dimensity chipset, to run most titles at full speed. The M-series chips in iPads handle this easier, which is why people compare the two platforms constantly. On Adreno 740 or Dimensity 9200 hardware, you're looking at solid performance for simpler games. More demanding titles like Skyward Sword or Metroid Prime 3 will still struggle regardless of what chip you have. Thermal throttling is the real bottleneck. Nobody talks about this enough. A phone will run a game at full speed for about twelve minutes before the SoC temperature triggers a throttle, then performance drops by thirty to forty percent until it cools down, then it spikes back up again. This cycles repeatedly. Using a phone cooling clip or sitting in an air-conditioned room helps more than any setting tweak in the emulator itself. I've seen people chase GPU hacks for hours when the actual solution was keeping the device below thirty degrees Celsius.
Get the Full Details
Controller Setup
Touch controls work okay for short sessions but your thumbs will sweat and slip during longer play. An external Bluetooth controller makes a real difference. Xbox controllers and PlayStation DualSense both pair without issues. The major third-party alternatives from 8BitDo and PowerA also work fine. Input lag on Bluetooth can be noticeable on older phones though. If you're using a device from before 2021, a USB-C wired controller gives you noticeably lower latency. The difference matters for anything rhythm-based like Super Smash Bros. Brawl. Save states are worth using but they aren't reliable across version updates. If you update Dolphin from one unstable build to another, your save states from the previous version will likely be incompatible. Always export your save data through the in-game save system before updating. The emulator's own save state folder lives at /sdcard/Android/data/org.dolphinemu.dolphinemu/files/Saves and you should back that up manually every few weeks.
Performance Tweaks That Actually Matter
Most online guides recommend aggressive settings that make games worse. Here are the ones I've actually found useful. Under Configuration, set the backend to Vulkan. OpenGL works but Vulkan generally gives better frame pacing on Android. Enable dual-core mode if your game supports it, which most GameCube titles do. Turn off synchronization features like Sync GPU Main Thread unless you're dealing with a specific graphical glitch, because disabling it usually improves performance. Set the aspect ratio to Stretch or 16:9 instead of 4:3 for most games, since the native resolution is often too narrow on modern screens. The "Fast Disk Speed" option is worth enabling for almost everything. It bypasses the simulated disk access times that the original hardware used, which cuts load times dramatically. Games that would take two minutes to load on emulated hardware will load in roughly ten to fifteen seconds. A few games break with this setting though. Sonic Unleashed has a known issue where the demo mode corrupts with fast disk speed enabled. If you care about that content, turn it off just for that title.
What Doesn't Work
Don't expect everything to run. The GameCube and Wii library is roughly four thousand titles. Of those, Dolphin's compatibility list shows about three thousand as playable, but "playable" means different things. Some games have graphical artifacts that make them unrecognizable. Others have audio stuttering that ruins the experience. A small number simply don't boot at all. Fire Emblem: Path of Radiance and the Japanese-exclusive GameCube version of Soulcalibur II are examples of games with persistent issues that have existed for years without a fix. Wii Sports requires the motion controls and the Nunchuk attachment. You can map those to a Bluetooth controller but the calibration is finicky and it doesn't feel natural. If you want to play Wii Sports properly, you're better off finding an actual Wii console with a sensor bar. The emulation isn't worth the frustration for that particular title. Online multiplayer through Wiimmfi works for some games but not all. Super Smash Bros. Brawl and Mario Kart Double Dash have working netplay. Most other online-enabled Wii games don't connect reliably through the emulator's modified netplay implementation. The community patches handle the protocol translation but the connection stability varies widely depending on the game's original networking code.
Getting Your Disc Images
You need to dump your own game discs. Downloading ROMs from the internet is common but it's copyright infringement and the files you find are often repacked with questionable compression that can corrupt the game. A GCUIEE or DumpTool plus a standard USB GameCube drive costs about thirty dollars and lets you create clean ISO files from your own copies. The process takes roughly twenty minutes per disc. Wii classics on physical media are harder to find since they were primarily distributed digitally, but the GameCube originals are straightforward to dump. Store your ISOs on internal storage, not an SD card. Access speeds on most microSD cards are slow enough to cause texture loading stalls and audio pops during gameplay. Internal UFS storage is significantly faster and eliminates that category of performance problem entirely. I lost about a week troubleshooting random texture pop-in before realizing the issue was the SD card read speed, not any emulator setting.
