Miyoo Mini Plus GBA screen settings for Pokémon

Choose between pixel scaling, image shape and screen coverage. A fullscreen picture is only useful if you can still read and use the game comfortably.

Start with readable dialogue and battle menus, then decide how much of the display you want to fill. The guide below gives you a repeatable comparison and a narrow way to keep or undo your choice.

What the two switches mean

Option	Documented purpose	What to inspect
Integer Scale	Scale the original image in whole-pixel increments	Text, sprite edges and how much screen space remains
Keep Aspect Ratio	Fit with the original proportions; disabling it stretches	Character proportions, circles and menu readability

These are documented controls, not a Pocket Deal Radar recommendation for one universal preset. The title screen may look fine while smaller battle-menu text is uncomfortable.

Open and save the setting

Launch your GBA game, press MENU + SELECT, then press B to move back one menu level.
Open Settings → Video → Scaling. Record the original options before changing one.
Resume and inspect the same scene. Compare with the original setting before making another change.
Use Quick Menu → Overrides → Save Game Overrides if the setting should apply only to this game.

Onion's scaling and override instructions also distinguish content-folder and core overrides. A core can serve multiple systems, so consider the scope before applying a broad change.

A short Pokémon readability comparison

Use the same game build, scene and normal brightness. This is a proposed check you can perform, not a result from our own device.

Dialogue: read several lines without leaning closer or skipping words.
Battle: inspect move names, PP, HP and a longer menu label.
Party or summary: check compact numbers and symbols.
Overworld: compare familiar sprite proportions and circular objects.

Keep the version that makes those tasks comfortable for you. If two settings are equally readable, screen coverage can be a preference rather than something you need to optimize further.

If the change disappears after reopening

Check whether you saved the override for the intended game and whether you reopened the same file with the same core. Record other overrides that might be active before changing global settings.

The Onion FAQ warns against using RetroArch's generic global reset, which can break Onion functionality. For a necessary reset, it names Apps → Tweaks → Advanced → Reset Settings → Reset RetroArch main configuration. Back up configuration first and investigate the narrow override before choosing that broader action.

Choose what you are trying to improve

A larger image, even pixel steps and preserved proportions are different goals. Write down the problem you actually notice: tiny numbers, uneven text edges, a stretched sprite or unwanted empty space. That makes the next setting change purposeful.

Your priority	Compare	Inspect before keeping it
Pixel consistency	Integer scaling on and off	Letters and sprite edges in the same scene
Original shape	Aspect preservation against stretching	Familiar sprites and circular objects
Larger displayed text	Screen coverage among the available options	Move names, HP and longer dialogue

These are comparison goals, not a tested preset. If two results are equally readable, it is reasonable to choose by preference rather than keep adjusting until the image fills every edge.

Run a controlled comparison in four Pokémon scenes

Dialogue: choose the same conversation and read a few complete lines. Record whether you can follow the text at your normal viewing distance.
Battle menu: inspect a long move name, PP and HP. Do not choose a setting from large title-screen lettering alone.
Party summary: compare small numbers and symbols. This can reveal a readability problem that is not obvious in the overworld.
Overworld: compare a familiar sprite or object for shape. Return to the original setting before judging the second version.

Keep game build, core and brightness unchanged. If you change scaling and brightness together, you cannot tell which made the text easier to read. Write one short observation for each scene rather than inventing an overall sharpness score.

Illustrative choice

Suppose a fuller image makes move names easier to read but the stretched character shapes bother you. That is a real tradeoff to record. Try the available aspect-preserving view, compare the same battle menu again, and choose the result you can use comfortably.

Save at the scope you actually intend

Onion distinguishes game, content-folder and core overrides. Its FAQ notes that one core can serve several systems and recommends considering content scope before broad core changes. For an initial Pokémon comparison, a single-game override makes the experiment easier to isolate.

Finish the comparison and record the original and chosen values.
Save the game override through the documented Quick Menu route.
Close normally and reopen the exact game with the same core.
Inspect the battle and dialogue scenes again. Then check another game if you want to confirm that the change stayed narrow.

If a second game looks different too, inspect existing broader overrides before saving more changes. A game-specific override can coexist with other settings; it is not a record of every preference in the installation.

Undo a scaling experiment without a global reset

Use your original values as the rollback reference and save the intended scope again. Onion also describes deleting relevant overrides from its Overrides menu as a way to revert changes. Preserve existing customizations before removing anything you did not create for this comparison.

First distinguish an unwanted game override from a damaged global configuration. The broader Onion reset named above affects more than the display choice. Use it only when the narrow investigation does not address the actual problem.

After rollback, reopen and check the same scenes. If the picture is fixed but Continue has different progress, treat that as a separate save issue and preserve its files.

Frequently asked questions

Does fullscreen always look better?

Screen coverage alone does not decide readability. Compare dialogue, battle numbers and sprite shape in your actual game before keeping the larger view.

Why did my setting disappear after restart?

Confirm that an override was saved and that you reopened the same content with the same core. Inspect existing scopes before changing global configuration.

Should I save a core override for one Pokémon hack?

A game override is the narrower starting point. Core scope deliberately affects other content using that core, potentially across systems.

Can these settings increase fast-forward speed?

This guide investigates the displayed image. No speed improvement or physical-device benchmark is supplied; use the separate speed guide for that question.

Scaling is separate from speed and progress

Use the fast-forward guide for controls and the save checklist for missing Continue. Changing the displayed image does not establish that a cartridge save loaded correctly.

Mini Plus overview · Heart & Soul setup. Documentation checked 6 Oct 2026; no physical-unit screen or comfort test was supplied.

Compare the same dialogue and menu twice

Choose a dialogue box with small text and a menu with a visible border. Record the current scaling option and any game-specific override, then describe what is difficult to read or what edge is missing. Change one option and reopen the same scenes. Include whether the result persists after relaunch so readability and persistence remain separate observations.

For example: a different scale makes the text easier to read but leaves a larger border. That is a personal viewing tradeoff to weigh against filling the screen, not evidence of a faster emulator. If an edge remains clipped, record the exact scene and active options before trying another adjustment. The comparison is most useful when you keep the game, scene and other display options unchanged.

Use the local GBA session notebook to download a plain-text record of your attempt. Blank fields stay unrecorded; the notebook does not diagnose your setup.

Based on the creator's documentation, checked 6 Oct 2026. Not hands-on tested unless a section says 'We played it'.

How we check