COMPLETE PICTURE · INTENDED PROPORTIONS · USEFUL PHYSICAL SIZE
A full panel is not always the right picture.
Black borders can be a normal consequence of preserving a game's intended proportions or using a particular scaling method. They are not, by themselves, proof of a defective screen. Stretching can alter shapes; cropping can remove part of the field. Compare the exact release, the complete useful picture and its physical viewing size before choosing a handheld. R36S and R36MAX both list 640×480 displays, with 3.5-inch and 4-inch diagonals respectively. Choose compact R36S value when the actual presentation suits you; compare R36MAX for a wanted larger physical view, not an assumed resolution or performance upgrade.
By iGameConsole Editorial Team · Canonical descriptions and all 24 variants for R36S and R36MAX reviewed October 3, 2026. Numerical examples below are explicitly simplified geometry, not measurements of shipped screens or observed emulator output. No display calibration, brightness, latency, shader-performance or whole-library rendering test was performed.
Buy the picture you want to use
Useful text, visible edges and familiar shapes can matter more than eliminating every empty strip.
Check the selected game presentation rather than judging the device from a staged scene.
The 30-second screen-fit verdict
Complete field and intended shapes matter: compare a supported proportion-preserving presentation of the exact release.
Regular pixel enlargement matters: investigate the actual integer-scaling behavior and the resulting picture size.
You want a larger physical view: compare R36MAX after the game fits. It does not add more listed pixels than R36S.
You want every game to occupy every edge: establish which trade-offs you accept. A different source shape cannot always fill a panel without changing proportions or removing content.
You suspect a fault: record the actual context. This guide does not diagnose every black area as harmless or prescribe hardware repair.
1. Separate source image, intended picture and panel
A game frame's pixel dimensions, intended displayed proportions and the handheld's pixel canvas are related but distinct. Do not assume one number answers all three questions.
Source frame
The software produces a frame or image. Its raw width-to-height pixel count is not automatically the final intended display shape for every historical system and release.
Intended presentation
Original display conventions, pixel shape and game-specific behavior can affect how the image should look. Use relevant release and emulator information rather than forcing one rule across every platform.
Panel canvas
The two reviewed listings specify 640×480. That pixel canvas has a 4:3 ratio. It does not mean every source must be stretched into 4:3.
Active picture
The game may occupy only part of the available canvas. Borders, overlays, scaling and the actual configuration affect what you see.
Physical size
The diagonal describes the display, not a guaranteed diagonal for every rendered game. Compare the active picture as well as the nominal panel.
Do not use a raw resolution as a universal aspect rule
Source-pixel ratio and intended display aspect can differ. Identify the relevant game and supported presentation before treating an arithmetic ratio as the complete answer.
2. Fitting, stretching and cropping make different trade-offs
When source and panel shapes differ, the method of filling the available space matters. Compare the result, not just the setting name.
| Approach | What it tries to do | What to inspect |
|---|---|---|
| Proportion-preserving fit. | Keep the complete intended picture inside the available area. | Border space, active size and correct shapes. |
| Integer enlargement, where supported. | Use whole-number enlargement of the relevant pixel grid. | Picture size, source assumptions and aspect treatment. |
| Non-uniform stretch. | Fill width and height using different enlargement factors. | Changed character, object and text proportions. |
| Cover or crop. | Enlarge enough to fill the area, with some picture potentially outside it. | Lost edges, HUD information and useful field. |
| Custom or mixed configuration. | Apply selected rules, overlays or effects. | The actual release and all relevant views. |
Fit can leave useful empty space
If the complete intended image is wider or taller than the canvas, keeping its proportions can leave strips around it. Empty space is a consequence to evaluate, not automatically wasted screen quality.
Stretch can change familiar shapes
Different horizontal and vertical factors change proportions. Whether you accept that is a preference, but it should be an informed choice.
Crop can change useful information
Look at the actual edges, score, menus and playfield. Do not assume all outer content is disposable.
A menu label is not a verdict
“Full screen” can mean different things in different software. It is not necessarily non-uniform stretching. Inspect the resulting picture rather than condemning or endorsing the words alone.
3. A worked example: a hypothetical 240×160 frame on 640×480
Assume a square-pixel 240×160 source with an intended 3:2 picture. This is a teaching example, not a claim that a particular supplied game or emulator uses these settings.
| Simplified method | Calculated picture | Consequence in the example |
|---|---|---|
| Whole-number 2× enlargement. | 480×320. | If centered, 80 canvas pixels on each side and 80 above and below. |
| Largest proportion-preserving fit. | Theoretically 640×426.7. | Uses the full width with space above and below. |
| Non-uniform stretch to the canvas. | 640×480. | Changes the assumed 3:2 proportions into 4:3. |
| Proportion-preserving cover at 3×. | 720×480 before clipping. | Only 640 of the 720-pixel width is visible. |
The fractional fit height is theoretical geometry, not a report of fractional physical pixels. Actual software must implement its own rasterization, rounding and supported rules.
Why the integer picture can have more border
The next whole-number enlargement is too wide for the canvas. A supported 2× result can therefore be smaller than the largest fractional fit. That is a method trade-off, not evidence of a defective panel.
Why full coverage can remove content
In this cover calculation, the 720-pixel-wide image exceeds the 640-pixel canvas by 80 pixels. Centering would clip 40 display pixels from each side, about 11.1% of the scaled width in total. No actual game cropping was measured.
Why no single method wins every preference
A buyer may prioritize regular pixel enlargement, the largest complete picture or full coverage. Those are different goals. Decide which goal serves your actual game.
4. Integer scaling is not the same as every game's correct aspect
Whole-number enlargement can be useful for a regular source grid, but it should not be treated as a universal correctness certificate.
Identify the grid being enlarged
Source dimensions and relevant aspect treatment matter. A blanket setting can conceal differences between releases or systems.
Inspect intended shapes
If historical presentation uses a different pixel shape or display convention, whole-number enlargement alone may not answer the intended proportions.
Accept the active-size trade-off deliberately
A smaller complete picture can be a sensible choice when you value its appearance. It can also be unsuitable if the resulting text or field is too small for your preference.
Do not promise a supported setting
Availability, naming and scope depend on the actual emulator and firmware. No universal toggle or preset is guaranteed here.
Do not turn a visual preference into a performance claim
A selected scaling method does not independently certify game speed, latency or support for a demanding platform.
5. Filtering and shaders belong to the actual setup
Different rendering options can change appearance. Their usefulness and effects need a selected-device answer, not a universal best-settings list.
Sharper-looking and smoother-looking are preferences
Observe relevant text, edges and motion under the actual settings. Do not describe one filter as correct for every game.
Effects are not original hardware identity
A CRT-style effect can be an aesthetic choice where supported. It does not establish equivalence to a particular original display.
Performance and power need measurement
No fixed shader frame-rate cost, battery percentage or runtime increase is supplied. A general option name is not a controlled benchmark.
Change one relevant variable
Record a working baseline before experimentation. Do not stack unrelated changes and then attribute every result to the panel.
Keep the buying question visible
If a particular rendering function is essential, verify it before purchase. If ordinary presentation fits, optional effects need not become the entire selection process.
6. R36MAX is physically larger, not higher in listed resolution
R36S lists a 3.5-inch diagonal and R36MAX a 4-inch diagonal. Both list 640×480. The physical viewing difference is real as a listing fact; a measured readability result is not supplied.
The proportional size calculation
Under ideal equal-aspect panels and identical framing, 4 divided by 3.5 is approximately 1.143. The same composition would be about 14.3% larger in linear physical dimensions.
Area is a different number
Squaring that ratio gives about 30.6% more area under those assumptions. That does not mean text height becomes 30.6% larger.
The pixel count stays the same in the listings
More physical area is not more listed pixels. It does not independently create extra image detail, a different emulation tier or a supported new platform.
Framing must actually match
If one configuration uses a smaller integer viewport, cropping or another aspect setting, diagonal-only comparisons can be misleading. Compare like for like.
A useful upgrade reason
“I want a larger physical presentation of this correctly framed game” is a clear reason to compare R36MAX. “I want more pixels, no borders and better compatibility” is not established by these two listings.
A larger view can be a valid preference
Keep that reason separate from pixel count and rendering settings.
Ask to compare the same release and framing.
7. A wider picture can use less panel height
To make the geometry tangible, assume ideal square-pixel 4:3 panels whose active diagonals equal the listed sizes. These are calculations, not physical measurements.
| Idealized picture | 3.5-inch panel | 4-inch panel |
|---|---|---|
| Full 4:3 rectangle. | 2.80 inches wide × 2.10 high. | 3.20 inches wide × 2.40 high. |
| 3:2 picture fitted to full width. | 2.80 wide × approximately 1.87 high. | 3.20 wide × approximately 2.13 high. |
| 16:9 picture fitted to full width. | 2.80 wide × approximately 1.58 high. | 3.20 wide × 1.80 high. |
These examples assume ideal geometry, unchanged proportions and full-width fit, with no overlays or other constraints. They do not certify any particular platform, game or shipped-unit dimensions.
Nominal diagonal can overstate the game-specific expectation
A wider fitted image can occupy less height than the full panel. That is why the useful field, not only the display badge, belongs in the buying decision.
A larger panel keeps the relative mismatch
Moving to a larger panel of the same assumed shape enlarges the picture but does not inherently eliminate its border pattern.
Geometry does not establish performance
A widescreen-format illustration is not evidence that either device runs the associated demanding releases well. Keep game fit as a separate gate.
8. Portrait games need a field-and-control decision
A portrait-oriented playfield and a vertically arranged handheld are different facts. The body name does not certify the game's presentation.
Complete field
Check the relevant playfield, score and status information. A larger diagonal does not prove they are all visible.
Rotation
If rotation is essential, confirm the supported software and resulting controls. Do not prescribe a universal menu or assume every game can be comfortably used that way.
Physical handling
Presentation and grip need to work together for the actual task. A rotated image alone is not a complete use demonstration.
No genre-wide certification
One example does not certify every shooter or arcade release. Ask for the title and configuration that matter.
The shoot ’em up buying guide addresses field, action and score requirements.
9. Check text and useful edges, not only a familiar logo
A title image can look impressive while revealing little about ordinary reading or the full gameplay field.
Dialogue and menus
Request relevant text from the exact edition. Different fonts, languages and settings can affect the experience.
HUD and outer information
Inspect relevant score, map, lives or status areas. Cropping may remove useful information depending on the release and configuration.
Familiar shapes
Look for objects or artwork whose intended proportions are understood. Do not use a tilted product photograph as a calibrated aspect measurement.
Motion
A still image does not establish how scrolling, effects or moving text behave. Request a relevant sequence when that matters.
Personal reading preference
A larger physical image may be wanted, but no medical benefit, universal comfort or exact readable-font threshold is certified.
The JRPG screen comparison connects the viewing preference to long-game ownership.
Ask for the actual field
Useful edges, text and the wanted action answer more than a product-scene close-up.
The display and controls remain part of the same task.
10. Compare evidence without changing several variables
A useful screen comparison identifies the exact release, software and presentation. Otherwise you may be comparing settings rather than devices.
| Keep comparable | Why it matters | What to record |
|---|---|---|
| Release and scene. | Different editions or views can show different information. | Original platform, edition and relevant task. |
| Aspect and viewport. | Active size and proportions can differ. | Supported settings and visible result. |
| Filter or effect. | Appearance may change without a panel change. | Relevant options and what was observed. |
| Camera context. | Angle, distance and capture can mislead. | Full screen, orientation and comparison conditions. |
| Information at edges. | Full coverage may conceal clipping. | Relevant field, menus and HUD. |
| Measured claim. | A photograph is not calibration. | Method and limitations, if an actual test exists. |
Match the question to the evidence
For proportions, request the actual presentation. For readability, request useful text and consider personal viewing. For performance, request a separate game-specific record.
Keep calculations labelled
The mathematical examples here explain possible trade-offs. They are not a report of how a delivered emulator is configured.
Keep conclusions narrow
One scene cannot establish every setting, game, brightness condition or session. A credible comparison states what it did and did not check.
The gameplay-evidence guide helps evaluate recordings.
11. Choose R36S or R36MAX for the difference actually listed
Both canonical descriptions and all variants were re-read. The following is a listing-fact comparison, not a new display benchmark.
| Decision fact | R36S | R36MAX |
|---|---|---|
| Listed screen. | 3.5-inch IPS. | 4-inch IPS. |
| Listed pixel canvas. | 640×480. | 640×480. |
| Chipset and memory. | RK3326, 1GB DDR3L listed. | RK3326, 1GB DDR3L listed. |
| Software direction. | Linux-based retro gaming OS, ArkOS community firmware. | Linux-based retro gaming OS, ArkOS community firmware. |
| 64GB base price. | $79.99 | $99.99 |
| 128GB base price. | $89.99 | $109.99 |
| Relevant purchase direction. | Compact classic-game value. | A wanted larger physical view. |
Reviewed USD base selling prices, not checkout quotes or current-stock guarantees. No higher refresh rate, brightness, color accuracy, panel lamination or input latency is certified by this comparison.
Choose R36S when the complete picture fits your preference
A compact presentation can be useful for suitable classics and a dedicated daily routine. Borders alone do not make it poor value.
Compare R36MAX when active physical size matters
The larger listed diagonal is its relevant distinction. Compare the same release and framing rather than assuming automatic text scaling or sharper detail.
Do not upgrade solely to remove borders
These listings share the same pixel ratio. A larger physical screen does not itself resolve a source-to-canvas shape mismatch.
Start with the compact candidate when it serves the actual game
R36S is relevant when the release, field, controls and physical size fit. Confirm the chosen configuration and useful presentation before relying on a generic screen badge.
Review R36S configurations12. Price the viewing preference without inventing a performance tier
At equal reviewed capacities, R36MAX costs $20 more than R36S in USD base pricing. That amount is a comparison of selling prices, not a benchmark result.
When the larger view can justify it
You want the same correctly framed content at a larger physical size and accept the different device format. That is a specific reason to compare.
When the compact candidate can be enough
The actual field and text meet your needs and lower base spending matters more. Do not pay for an unneeded difference because borders look unfamiliar.
When neither answers the requirement
If a particular aspect, rotation workflow, higher resolution or demanding game is essential, identify suitable documented hardware and software. Price alone does not certify it.
A reference price is not a rendering result
Do not turn a comparison amount or promotional claim into proof of better screen behavior.
The storage-versus-screen guide addresses a different budget trade-off.
13. Capacity and finish do not change the panel ratio
Each model's 64GB-to-128GB move adds $10 at the reviewed base prices. Capacity supplies nominal space, not a different display specification.
Space
Choose useful capacity from actual files and available room. More storage does not independently add pixels, fix stretching or establish a supported rendering effect.
Color
R36S lists Purple, Black, White, Red, Yellow, Green and Blue across both capacities. R36MAX lists Black, White, Blue, Gray and Red across both capacities.
Appearance is not a panel tier
Finish does not establish a different aspect, measured brightness or rendering capability. Confirm the actual option if a particular appearance matters.
Content
A capacity or game-count label does not guarantee the exact edition used in a display example. Confirm selected contents and lawful access separately.
Package
Screen protectors, cases and surrounding accessories are not established by a staged image. Review the selected package before assigning value.
The library-count guide and package guide support those separate questions.
14. Keep platform fit ahead of display enthusiasm
A well-framed picture is not a complete compatibility result. The exact release still needs suitable hardware, controls and configuration.
Classic interests
GBA, SNES and PS1 are core directions for the shortlist; R36S also names NES. Individual releases and software remain relevant.
Demanding titles
N64 and PSP results vary by game. R36S describes Dreamcast as limited and PS2 as unsupported; neither candidate is selected here as a full PS2 solution.
Applications and connections
These are Linux-based listings, not Android application devices. Included Wi-Fi and Bluetooth are not established for the intended recommendations.
External display
A USB-C reference does not certify TV output or a complete dock setup. If a larger external view is essential, verify that actual workflow.
Multiplayer
A split-screen mode in a game does not establish a supported second input method or comfortable shared viewing. Check the complete setup.
The favorite-game checklist establishes the purchase-defining release.
Choose a picture you want to return to
A complete, suitable presentation can be worthwhile even when it does not touch every panel edge.
The device should fit your actual game and routine.
15. Firmware differences need supported instructions
ArkOS is community firmware within the Linux-based retro gaming system, not a separate operating system alongside Linux.
Actual builds can differ
Exact firmware can vary by batch and can be updated or re-flashed. Emulator menus, available presentation options and scope can differ.
No universal shortcut
Do not assume one menu path, key combination or preset applies to every delivered setup.
Record the baseline
Note the working game configuration before changing scaling, effects or aspect. Keep a way to identify what changed.
Preserve important data
Use appropriate copies before firmware or storage changes. A visual concern does not justify overwriting valuable progress.
No automatic upgrade promise
A new build or another emulator name is not guaranteed to improve every screen or game. Change for a defined reason with suitable instructions.
16. Gifts and existing owners need a concrete viewing preference
Gift buyer
Ask which edition the recipient remembers and whether they prefer original proportions, a larger view or a compact format.
Do not promise every childhood game fills the screen perfectly.
Reading-first buyer
Request actual dialogue and menu views. Compare active picture size and relevant framing rather than only diagonal.
No universal comfort claim is made.
Existing owner
Identify the current viewing issue and compare the same release and settings before buying another device.
A settings difference is not automatically a hardware upgrade.
Compact daily-use buyer
If suitable complete presentation fits, borders need not undermine the dedicated-handheld role.
Prioritize the experience you will actually use.
These are illustrative purchase patterns, not customer outcomes or display studies.
17. Ask for the complete presentation before purchase
A copyable screen-fit question
“I am considering [model and capacity] for [exact release, platform and edition]. I want [complete field, intended proportions, integer enlargement or a specified viewing preference]. Which supported presentation applies on the selected setup? Please show relevant edges, text and ordinary play, identify the settings, and distinguish observed results from product illustrations or calculations.”
If borders are the concern
Ask what method produces them and whether the complete intended image is visible. Do not request stretch merely because the panel has spare area.
If text is the concern
Ask for the actual text and framing. A logo or a different game is not a useful answer.
If a rendering feature is essential
State it as a purchase condition. No larger capacity or higher price substitutes for evidence of that function.
If the picture may be faulty
Record the device, software, scene and observed behavior. This guide is not a hardware diagnosis or an instruction to ignore abnormal output.
A seven-step screen-fit buying checklist
- Name the exact release. Record original platform, edition, language and important view.
- Identify intended presentation. Separate raw source dimensions from the correct displayed proportions.
- Choose the visual priority. Decide between complete field, regular pixel enlargement, active size and any accepted trade-off.
- Confirm supported settings. Establish the actual emulator, aspect, viewport and relevant effects.
- Request useful evidence. Inspect edges, text, familiar shapes and ordinary motion, not only a title logo.
- Compare physical size and spending. Match framing and choose compact R36S value or a wanted larger R36MAX view.
- Validate and preserve. Record the baseline, test supported changes one at a time and protect important data before meaningful modifications.
Your one-page display decision record
Release: exact platform, edition and relevant task.
Intended picture: supported aspect and any special presentation needs.
Chosen trade-off: complete image, active size, regular scaling or accepted crop/stretch.
Actual setup: firmware, emulator and relevant settings.
Useful information: text, edges, HUD and field that must remain visible.
Evidence: conditions, observed result and untested scope.
Purchase reason: compactness or a wanted larger physical image.
Remaining condition: what still needs confirmation.
18. On arrival, evaluate the result before changing everything
Use the delivered configuration's supported instructions. This is a checking framework, not a universal emulator-settings tutorial.
Identify the unit and release
Match the selected option and record the actual software. Confirm you are comparing the intended edition.
Observe the baseline
Look at relevant field edges, menus and motion before changes. Distinguish game artwork, overlays and presentation space.
Make one supported change
If appropriate, compare a relevant aspect or scaling option while preserving the original setting. Do not re-flash just to chase an unexplained border.
Inspect consequences
Check proportions, clipping and useful active size. More panel coverage is not necessarily a better result.
Check ordinary play separately
A display change does not certify controls, sound, saving or game performance. Verify the wanted activity and normal progress routine.
Record limits and get appropriate help
If output appears abnormal, retain clear context and seek relevant support. Do not open the hardware or overwrite storage based on this article.
19. Recognize the display question you actually have
| Observed concern | Relevant next question | Wrong shortcut |
|---|---|---|
| Empty strips around a complete image. | Is the intended aspect or scaling method producing them? | Assume the panel is defective. |
| Shapes appear altered. | What aspect treatment and horizontal/vertical scaling apply? | Assume more pixels automatically correct them. |
| Important information is missing. | Are cropping, viewport or edition differences involved? | Assume every outer edge is disposable. |
| Text is too small for your preference. | What is the actual active size and framing? | Assume larger capacity enlarges text. |
| A demanded option is unavailable. | Does the actual software support the requirement? | Assume every ArkOS build has identical menus. |
| A game performs poorly. | What hardware and title-specific evidence support it? | Assume a larger panel improves emulation. |
Separate the cause before recommending another device, another setting or a repair. No one shortcut answers every concern.
20. Three illustrative screen-fit purchase decisions
You want compact classic play with complete proportions
Verify the actual release and supported fit. R36S can be a suitable direction when the resulting field and physical size meet your preference.
You want that same complete image physically larger
Compare R36MAX with like-for-like framing. Its larger diagonal is the reason, not an assumed pixel-count or processing upgrade.
You require full coverage, a particular ratio or a specific rendering mode
Establish the actual software and accepted trade-offs. If the essential requirement remains unsupported, choose a documented route rather than assuming either model solves it.
These are hypothetical decisions, not measured buyer results or game-specific rendering certifications.
Keep the complete game in view
The picture you want may matter more than how much empty panel remains around it.
Choose the display and setup that serve the actual release.
The honest fit boundary
Consider this shortlist when…
Your exact classic releases, complete presentation, controls and physical viewing preference fit.
Choose compact R36S value or compare R36MAX for a wanted larger view.
Resolve another requirement first when…
You require higher resolution, a specific aspect or rendering feature, an external display or a demanding title that remains unsupported or unclear.
A nominal diagonal or a familiar scene cannot certify that missing condition.
No calibrated brightness, color accuracy, refresh rate, fixed shader cost, battery gain, universal readability or all-game full-screen result is supplied.
The broader handheld selection guide helps if the device's core role is still undecided.
Frequently asked questions
Are black borders proof of a defective screen?
No. They can result from aspect preservation or scaling. Their actual cause needs context; this guide does not diagnose every black area as normal.
Should every retro game fill the panel?
Not necessarily. Complete proportions, regular scaling and full coverage can conflict when source and panel shapes differ.
Is stretching the same as cropping?
No. Non-uniform stretching changes proportions; cropping can remove part of the picture. Inspect the actual result.
Does a Full Screen menu label always mean distortion?
No. Labels vary by software. Establish the resulting aspect, complete field and supported configuration.
Does integer scaling guarantee every game's correct aspect?
No. The source grid and intended display proportions need separate checks. Availability and aspect treatment depend on actual software.
Is R36MAX higher resolution than R36S?
Not in the reviewed listings. Both specify 640×480; their listed physical diagonals are 4 inches and 3.5 inches respectively.
Does R36MAX eliminate the same game's borders?
Not by size alone. A larger panel of the same assumed shape enlarges the presentation without inherently removing a shape mismatch.
What does the approximately 14.3% size calculation mean?
Under ideal equal-aspect panels and identical framing, 4 divided by 3.5 predicts about 14.3% larger linear physical dimensions. It is geometry, not a measured readability result.
Are the worked examples real emulator measurements?
No. The 240×160 source and ideal-panel calculations are explicitly simplified examples. Actual rasterization and supported settings can differ.
Does 128GB change screen ratio or rendering quality?
No such change is established by capacity alone. Choose space for useful files, not an assumed display upgrade.
What are the reviewed prices?
R36S is $79.99 for 64GB and $89.99 for 128GB. R36MAX is $99.99 for 64GB and $109.99 for 128GB in reviewed USD base pricing.
Will every unit have identical screen settings?
No. The listings use Linux-based retro gaming OS with ArkOS community firmware. Exact firmware can vary by batch and can be updated or re-flashed; emulator options can differ.
Choose useful presentation, not a full-panel promise
Start with the exact release, intended proportions and information you need to see. R36S is a compact candidate when that picture fits; R36MAX is a comparison when a wanted larger physical view matters. Confirm essential rendering requirements before buying. Borders can be a deliberate trade-off, not a reason to invent a performance upgrade.
Review R36S compact configurationsCompare the R36MAX larger view
