Choose the hero you want to control, and the handoff you want to repeat.
For classic action games with switchable characters, check the exact release's complete handoff: meet its actual access conditions, use the supported switch, identify the newly active character and perform the next meaningful action. A roster picture, two characters on screen or a familiar button layout does not establish that whole task.
R36S is a compact candidate when a suitable classic and its essential control-and-handoff routine fit. Compare R36MAX when you want a larger physical view after the task fits. Neither capacity nor screen size adds a missing native character-switch feature.
October 8, 2026 reviewed USD bases are S 64GB $79.99 / 128GB $89.99 and MAX 64GB $99.99 / 128GB $109.99. Both list RK3326, 1GB DDR3L and 640×480; S lists 3.5-inch IPS and MAX 4-inch IPS. The difference here is a wanted physical format, not stronger character-switch processing.
Review compact R36S optionsCompare the larger MAX view
The 30-second fixed-hero or switchable-team verdict
A fixed character can provide all the play you want. A switchable team can be attractive when the actual handoff changes the action you enjoy. Choose that preference without assuming one is more advanced, easier or more valuable for everyone.
| What you want | What to establish | Do not substitute |
|---|---|---|
| One hero for a session | The actual selected character and meaningful controls | A required switching system you would not use |
| Change the active character during action | Native conditions, supported input and next action | A selection screen before the event |
| Reconfigure a JRPG party | The actual roster, menu and command workflow | An action-game handoff |
| An assisting companion | Its real role and any available player command | Proof that you can directly control it |
| Two people play together | Exact mode and complete input or connection route | Two characters controlled by one player |
| Continue on another device | Supported transfer of the relevant progress | A native character change |
By iGameConsole Editorial Team. Current S/MAX descriptions and complete fourteen S / ten MAX variant records reviewed October 8, 2026. This is a task-led buying guide, not a newly performed character-switch, timing, access, compatibility or multiplayer test.
1. A fixed hero is a complete preference, not a missing upgrade
One character can be the reason you return to a classic: familiar movement, one action set and a route you enjoy. A larger roster is not automatically a better purchase if choosing or switching characters is not part of that attraction.
Another player may enjoy handing control between characters, comparing their actual actions or using a permitted switch during a route. That is a different playing interest, not a universal skill or complexity ranking.
Describe the repeated task in ordinary words. “I want to move through this stage with this character” and “I want to switch during this stage and use the other character's action” create different evidence requests.
Keep essential requirements separate from curiosities. If ordinary fixed-character play would satisfy you, an unverified optional switch need not become the whole purchase decision. If the handoff is the reason to buy, resolve it before ordering.
2. Identify the edition before borrowing its character system
Record title, original platform, edition, language and relevant mode. A console release, portable adaptation, sequel, revised collection and modern remake can share characters without sharing access or controls.
A remembered roster or demonstration from another version is not enough. Match the feature and instructions to the actual release you intend to use. A familiar name does not certify identical mechanics across the series.
If the action belongs to a compilation or a particular mode, identify that component and how it is reached. No complete title manifest or universal mode list is supplied here.
Separate native feature presence, actual configuration behavior and supplied content. A suitable platform direction does not guarantee a named game is included, and a supplied file does not prove the essential handoff works as wanted.
3. Choosing before play is not switching during play
A selection screen can let you pick a character for the next event without permitting a change inside it. Establish when the choice can actually occur: before a stage, between attempts, through a menu or during ordinary action.
If in-action switching is the attraction, ask for that exact operation. A roster screenshot or two successful separate sessions does not demonstrate a live handoff.
If choosing one character for each attempt is enough, keep that simpler purpose. You do not need to require continuous switching merely because another release offers it.
The point is to choose the experience you want, not to make every character-related feature mandatory. Distinguishing the timing of selection prevents a technically suitable but different game from being presented as an equivalent.
4. A visible companion is not necessarily a controllable alternative
Another character can be part of the story, follow the active hero, assist under the game's rules or belong to a roster. Its appearance alone does not identify who controls it.
Establish whether direct control can actually pass to that character in the intended mode. A command to request assistance can be a different action from taking over movement and attacks.
If a computer-controlled companion is what you enjoy, identify that behavior instead of inventing a switch. If you want direct control, an assist animation does not meet the requirement.
This distinction also separates an automatic event from a switchable-team game. Watching characters act is not proof that the player can hand control between them. Neither image count nor storage capacity supplies the answer.
5. Access conditions are part of the native task
A selected release can restrict which character is available and when a switch is permitted. Identify the condition relevant to your wanted route rather than assuming a button works in every context.
Possible questions include current availability, a mode requirement or a native state that permits the action. These are investigation categories, not a certified rule list for all games.
A refused action may reflect the actual rules rather than a faulty physical button. Separate native eligibility, input mapping and hardware response before changing several settings.
If immediate access to a specific character is indispensable, ask for that state explicitly. A late-game clip or another player's prepared record does not establish the starting experience in your selected package.
6. Follow the handoff through the next meaningful action
A transition animation can show that something changed without proving the wanted character now receives your input. The useful evidence continues into an action that identifies the new active role.
For a selected task, begin with the actual state, perform the switch, inspect the resulting cue and carry out the next meaningful command. Adapt the sequence to the exact release rather than imposing a universal recipe.
Examples of relevant checks are movement, an ordinary action or a route-specific operation where the software provides it. No character ability, special command or success rate is promised here.
A bounded observation can establish this one transition under stated conditions. It does not certify every character, stage, exceptional state or later mode.
| Stage | Useful evidence | Not yet established |
|---|---|---|
| Eligible state | The target character and actual switch conditions | Every character is immediately available. |
| Input | The supported native command and real mapping | A visible stick or menu action supplies it. |
| Transition | The observed change under the selected mode | Every state permits the same action. |
| Recognition | The cue that identifies the active character | Two visible characters mean two active players. |
| Next action | The intended meaningful command reaches the new role | All abilities and contexts are certified. |
| Continue or return | The required next state or supported reverse switch | Unlimited undo or safe interruption anywhere. |
7. Recognizing the active character can matter as much as switching
After the handoff, the useful information may include the character, a selection cue, a status area or another native indication. Inspect what the actual release uses, not an imagined universal highlight.
Two sprites can remain visible while only one receives movement. A changed portrait can refer to something other than active control. Follow the cue together with an actual command to understand its meaning.
If similar artwork or crowded presentation makes the identity unclear for you, ask for an ordinary representative scene. A flattering empty screen may conceal the information needed during the route.
More physical display area can be a wanted preference, but it cannot add an absent cue or redesign the game's interface. No universal readability or visual-access benefit is assigned to a diagonal measurement.
8. The next character's action may have its own input requirement
Do not assume the same physical command has the same useful outcome in every character context. The release's own controls and the actual mapping define the result.
If the attraction is switching and then using a specific operation, keep those two stages connected in the demonstration. A switch followed by unrelated movement may not answer that requirement.
Combined, held and sequential inputs are separate questions. Establish the one the wanted task actually uses rather than advertising every switch as a single easy press.
No universal macro, simplified-command mode, automatic action, timing window or precision score is supplied. A clear scoped operation is more useful than a claim that every character works perfectly.
9. Direction, position and camera remain part of the route
A handoff can occur while the game presents a particular position or view. Follow the relevant context into the next action rather than inspecting only the character portrait.
Identify whether a view change is native presentation or player-controlled. A second physical stick does not create a modern camera system in an original release that lacks one.
If the route needs a direction and another command together, include that combination. A launcher responding to navigation does not establish the meaningful in-game sequence.
Preserve useful picture proportions and field information. Cropping into the most attractive character can remove the context that makes the task understandable. No universal filter, zoom or scaling recipe is prescribed.
10. Switching back, restarting and undo are different operations
Returning control to another available character can be a native action with its own conditions. It does not necessarily reverse the consequences of the last action or restore an earlier game state.
If the return switch is central to a repeated sequence, request it separately. Do not assume that one successful direction proves every reverse transition or exceptional state.
A restart can return to a different point, and an undo feature has another scope where present. Learn actual behavior with low-stakes progress instead of experimenting on a valued attempt.
No free reversal, unlimited retries or loss-proof control sequence is promised. Choose the supported routine you enjoy rather than treating every change of character as an administrative safety feature.
11. A tag, a formation and a party menu are not one system
A fighting release's supported tag, a character handoff in a platform route and a JRPG active-party change can involve different timing, rules and input contexts. Familiar character portraits do not make them equivalent.
Use the party-building guide when menus, equipment and team preparation are the main interest. It follows the information-to-selection workflow rather than certifying action-game handoffs.
Use the fighting-game selection guide for the essential directional and action pattern and actual versus requirements. The broader task remains version-specific.
This page focuses on who receives direct control after a native in-action change and whether the next wanted action fits. It does not supply a cross-genre roster or universal tag-team instruction.
12. Two characters do not establish two-human play
One player can control different characters over time without another person's input. Conversely, a native two-player mode can have a distinct input arrangement that is not reproduced simply by showing two characters.
If two people playing together is essential, identify the exact mode, device, software and complete controller or connection route. Two purchased handhelds do not independently establish linked play.
Passing one device between people is a handling routine. It does not automatically change the native active player, provide separate records or create simultaneous control.
Do not order another unit or accessory solely to add a native character switch. The game's feature and the human input arrangement answer different questions. No wireless or connected setup is certified here.
13. A character preference does not automatically alter progress
The active character, recorded completion, unlocked roster and continuing campaign can be different pieces of game state. Identify which one matters when you stop.
A visible new character does not prove a permanent unlock. A completed attempt does not prove every record was written. Normal saving and later return require their own supported route.
Game saves, emulator states and independent protection are separate. Test meaningful low-stakes progress through the correct exit before relying on valued records or changing firmware.
A personal note can remind you which action you wanted to try next. It is not a native journal or an automatic synchronization feature. Greater capacity does not protect the only active copy or add persistent character selection.
14. Choose by the actual brief, not the widest roster
A familiar single-hero route
You want the same movement and action through a few stages. Verify that exact task and supported stop; do not make a switching system an unnecessary condition.
A handoff followed by a specific action
You want to change the active role and use the new character meaningfully. Demonstrate the eligible state, switch, active cue and next action. Choosing another portrait before play does not answer it.
A menu-built team
You want equipment, formation or command planning. Follow the party menu and return to play rather than substituting an action game's character change.
A shared session
You want another person participating. Resolve the supported human-input route. A successful solo handoff may be enjoyable but does not certify multiplayer.
These are worked decision examples, not surveyed demand, observed success rates or claims that one preference is more profitable.
15. R36S is a compact candidate after the meaningful task fits
R36S lists 3.5-inch IPS at 640×480, Rockchip RK3326, 1GB DDR3L and Linux-based retro gaming OS (ArkOS community firmware). Its current description identifies NES, SNES, GBA and PS1-oriented classics as core directions.
Those facts narrow a hardware candidate; they do not certify a named title's character system. An essential release still needs its actual native feature and meaningful operation established.
Consider S when the exact suitable classic, mapped handoff, useful information and supported progress routine fit the compact dedicated role. Its lower starting price can be a genuine reason after the main requirement is resolved.
N64 and PSP results are title-dependent. S is not an Android direction or a PS2 solution. Do not extend a familiar franchise name into a guarantee for later-platform entries.
16. MAX is a wanted larger view, not a roster upgrade
R36MAX lists 4-inch IPS at 640×480, RK3326 and 1GB DDR3L with Linux-based retro gaming OS (ArkOS community firmware). Its listed resolution, chipset and memory match S's.
Compare MAX when more physical viewing area is wanted for actual active-character cues, action context and relevant status information. It does not add source pixels, unlock characters or alter native eligibility.
No universal comfort, faster switching, better timing or improved input precision is established. The physical preference should follow the scene and task you actually use.
If the essential handoff remains unconfirmed, a larger panel does not solve that evidence gap. If the task fits and the larger view is wanted, that is a real spending reason without an invented performance tier.
| Fact or condition | R36S | R36MAX |
|---|---|---|
| Panel | 3.5-inch IPS, 640×480 | 4-inch IPS, 640×480 |
| Chipset and memory | RK3326, 1GB DDR3L | RK3326, 1GB DDR3L |
| System direction | Linux-based retro gaming OS (ArkOS community firmware) | Linux-based retro gaming OS (ArkOS community firmware) |
| Native character access | Exact release and mode answer needed | Exact release and mode answer needed |
| Switch and next action | Actual meaningful input task needed | Actual meaningful input task needed |
| Human multiplayer or transfer | Complete independent route needed | Complete independent route needed |
17. Spend for nominal room or physical viewing, not more mechanics
Complete reviewed variant records show S 64GB at $79.99 and 128GB at $89.99; MAX 64GB at $99.99 and 128GB at $109.99. Capacity adds $10 within either model in these USD references.
MAX adds $20 at matched capacity. S 128GB and MAX 64GB compare greater nominal room with wanted larger physical viewing. Neither changes the original release's character roster, input interpretation or eligibility conditions.
Usable space depends on the supplied arrangement and files. A game total does not identify an exact edition or certify a switchable-character catalogue. Choose capacity after the actual task fits.
| Configuration | Price | Useful reason | Not established by spending |
|---|---|---|---|
| S 64GB | $79.99 | Lower entry price for suitable compact classic play | Every character or game feature |
| S 128GB | $89.99 | Additional useful nominal room | More active party slots or safer saves |
| MAX 64GB | $99.99 | Wanted larger physical view | Faster native switches or extra pixels |
| MAX 128GB | $109.99 | Larger view plus nominal room | Wireless play or transferred progress |
All fourteen S and ten MAX variant records were reviewed with no unread pages. S lists Purple, Black, White, Red, Yellow, Green and Blue; MAX lists Black, White, Blue, Gray and Red, across both capacities.
Finish is appearance, not a character tier. Confirm the exact current option, supplied finish, package, availability and applicable checkout charges. These dated USD bases are not a destination total or stock guarantee.
18. The delivered configuration determines the supported commands
ArkOS is community firmware within the Linux-based environment, not a separate operating system alongside Linux. Actual builds can vary by batch, update or re-flashing.
The original release's command, emulator mapping and physical input are different layers. Menu navigation, an emulator function and a native switch can each have a different role.
Use the instructions for the actual configuration. No universal key combination, version, emulator preset, turbo setting or calibration recipe is supplied in this guide.
Keep a working baseline, change one meaningful thing at a time and protect appropriate permitted records before software or storage changes. A familiar button label does not certify every character context.
19. A gift should identify the character experience, not just the favorite name
Ask whether the recipient wants one familiar hero, a native switchable action team, menu-based party planning or playing with someone else. Those preferences can require different modes even within related games.
Confirm the exact release, language and important feature, then assign preparation responsibilities. Do not select a larger card as a substitute for establishing the essential interaction.
For younger recipients, an adult should inspect actual content and follow the device's instructions. Character familiarity and shell color are not universal age-suitability evidence.
Confirm essential package items and current applicable delivery arrangements. No case, wall charger, branded card, arrival date, warranty duration or response deadline is inferred from scene imagery.
20. Ask for one complete, low-stakes handoff
The relevant demonstration identifies the edition and mode, shows the actual access condition, performs the switch, makes the active role understandable and carries out the next wanted action. Include the reverse transition if it is essential.
State what was observed and what was not. One low-stakes handoff can be useful evidence without certifying the complete roster, every stage or full campaign.
For persistence, use the actual normal save and proper exit, then verify the relevant returned record separately. Do not alter valued progress merely to test an uncertain menu or shortcut.
A copyable pre-purchase question: “For [title, original platform, edition, language and mode], I want [one fixed character or this native in-action handoff]. Show the actual access condition, mapped switch, active-character cue and next meaningful action on this configuration. Identify any limit or extra input. Verify essential return and progress separately, without treating two characters as proof of human multiplayer.”
No named handoff has been newly played for this page. Product and scene images illustrate presentation rather than this proposed functional check.
Validate the role you ordered
On arrival, match model, finish and selected configuration to your order, inspect actual contents and read the instructions. Identify the confirmed release and native mode before experimenting with unfamiliar commands.
Use a low-stakes route to check the switch, useful active cue and next action. Verify normal supported progress separately if it matters. Record the actual working arrangement before meaningful changes.
If something differs, identify the stage: eligibility, mapping, transition, active-character information, next action or return. A refused switch under the game's rules is a different issue from an input that never reaches the software.
Follow proper charging and shutdown instructions. USB-C is a connector description, not a fast-charge certificate. Do not remove active storage or overwrite the only useful record to investigate a feature.
The honest fit boundary
Consider the classic route when the exact release's real access, handoff, active information and meaningful action fit. Review S for compact dedicated play or MAX for a wanted larger physical view.
Resolve before ordering when an essential character, immediate access, particular command, modern application, specialized input or human multiplayer route remains unconfirmed. Storage and panel size do not establish it.
Keep a currently working setup or choose another documented route when it meets the essential need better. A dedicated handheld should add a role you will enjoy, not a promise that every character system has become interchangeable.
Seven steps to choose for fixed-character or native handoff play
Identify the wanted character task, verify a meaningful switch where required, then choose a suitable physical format and configuration.
-
Define the activity.
Separate fixed-hero play, in-action switching, party menus, assistance and actual human multiplayer.
-
Identify the exact release.
Record title, original platform, edition, language and native mode rather than borrowing another version's feature.
-
Establish access.
Identify the target character's actual availability and the state in which the handoff is permitted.
-
Follow the complete handoff.
Observe supported input, transition, active-character cue and the next meaningful action; add the reverse switch only when essential.
-
Resolve progress and other players.
Check normal retention and any required human-input route separately; a native character change is not multiplayer or device migration.
-
Choose the real hardware benefit.
Compare compact S with wanted larger-view MAX, choose capacity for nominal room and confirm the selected package and checkout.
-
Validate and preserve.
Follow actual instructions, use low-stakes progress, retain the working arrangement and document an essential mismatch before changing valuable data.
This is a proposed buying and validation routine, not a completed character-system test.
Fixed heroes and native character-switch buying FAQ
What should I check before buying for character switching?
Identify the exact release and mode, actual availability, supported switch, active-character cue and next meaningful action. A changing portrait or roster picture is not the complete task.
Is a fixed hero a worse purchase than a larger roster?
Not automatically. One familiar character and a suitable route can provide the whole experience you want. Require switching only when it materially defines your interest.
Does a character-selection screen prove in-action switching?
No. Choosing before an event and changing direct control during it are separate functions. Match the evidence to the exact timing and mode you require.
Do two visible characters prove both are controllable?
No. A companion, story participant, assist or inactive roster member can be visible without direct control. Follow a supported handoff into the next meaningful action.
Is a refused switch automatically a hardware problem?
No. Actual native conditions can restrict the action. Separate eligibility, mapping and input response before changing the configuration.
Does switching back undo the last action?
Not by definition. Returning control, reversing consequences, restarting and restoring progress have different scopes. Verify the exact native behavior with low-stakes material.
Do two characters or two handhelds establish multiplayer?
No. A solo native handoff and a complete human-input or connection arrangement are different requirements. Buying another device does not establish a compatible linked mode.
Is MAX a faster switching or larger-roster upgrade?
No such tier is established. MAX lists 4-inch IPS and S 3.5-inch IPS; both list 640×480, RK3326 and 1GB DDR3L. Compare physical viewing after the native task fits.
Does 128GB add characters, party slots or record protection?
No such feature follows from capacity. Choose greater nominal room for files, not expanded native rules, unlocks, independent backups or synchronization.
Will every unit use the same switch shortcut?
No universal command is promised. The listed system is Linux-based retro gaming OS with ArkOS community firmware; actual builds can vary by batch, update or re-flashing. Use the actual release and configuration's instructions.
Are pictured games supplied or handoff-tested?
No such guarantee follows from the pictures. Source imagery illustrates devices and scenes. Confirm exact content separately; no named handoff or performance result was newly tested for this guide.
What prices and final buying rule does this guide use?
Reviewed October 8, 2026 USD bases are S 64GB $79.99 / 128GB $89.99 and MAX 64GB $99.99 / 128GB $109.99. Confirm live selection and checkout. Choose the character task, verify the handoff and next action, then choose the handheld.
Follow the guide for the remaining requirement
- JRPG party building covers roster, equipment and menu-based team decisions.
- Platformer stage and collectible goals follows access, meaningful completion and retained records where supported.
- Native game replays separates watching a past event from directly controlling a character.
These related questions support the purchase without replacing the central handoff-to-next-action check.
Choose a character routine you will enjoy returning to.
A familiar hero can be enough. A meaningful native handoff can be the attraction. The useful recommendation follows the actual role you want, not the widest roster or largest card.
Review S for suitable compact classic play, or compare MAX for wanted larger physical viewing. Resolve an essential character, access condition or input requirement before ordering rather than expecting hardware price to add it.
Review compact R36S optionsCompare the larger MAX viewConfirm the live selected option, package, availability, applicable charges and current terms. Keep a working route when it meets your requirement better.
Evidence and editorial scope
Current S/MAX descriptions and complete fourteen S / ten MAX variant records reviewed earlier October 8, 2026 provide dated listing facts and prices. Unsupported older review and library totals are not used as character-system evidence.
Relevant actual party-building, fighting-selection and platform-goal bodies were reviewed. Their main responsibilities are menu-based team planning, essential inputs and versus modes, and stage/collectible progress. This page's independent focus is native in-action handoff and the next meaningful action, not an exhaustive portfolio-gap claim.
The five existing source assets were successfully displayed during the preceding same-day preparation in this conversation. Their appearance supports concise ALT and complete-device, desk, hand and control presentation. This does not retrospectively authenticate earlier unsupported image reads. No new generation or cleanup was performed; native HUD and physical markings remain.
No named character system, immediate unlock, complete roster, switch timing, input accuracy, multiplayer, transfer or persistence feature is certified. Examples define useful buying checks rather than newly performed gameplay results.
Final buying rule: choose the character task, verify the handoff and next action, then choose the handheld.
