iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The best starting point for LostOdysseyRecomp on Android is Vulkan with the driver recommended for your device: Turnip on Qualcomm phones and tablets where it is offered, or PanVK on supported Mali hardware. Begin with conservative render resolution and frame-rate targets, finish shader compilation, and increase one setting at a time. For controls, a USB-C or Bluetooth gamepad is the most reliable option; the port hides touch controls automatically when a controller is connected. If you play on the touchscreen, use the CTRL menu to resize, reposition, recolor, or hide each control.
There is no single universal “best” preset. LostOdysseyRecomp is an experimental native port, and sustained performance depends on the phone or tablet, GPU driver, display ratio, thermals, and game scene. The workflow below gives you a stable baseline, then shows how to tune image quality and controls without losing responsiveness.
Check that your Android device can run the port
LostOdysseyRecomp’s Android build requires a 64-bit device running Android 8.0 or newer with Vulkan support. Those are minimum platform requirements, not a promise of a particular frame rate or resolution. A device can meet the operating-system requirement and still need a different GPU driver or lower graphics settings.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Operating system: Android 8.0 (API level 26) or later.
- Architecture: 64-bit Android.
- Graphics API: Vulkan-capable GPU and driver.
- Storage and network: Leave enough free space for the game files and shader pack, and use a dependable connection for the first shader download.
The project describes the port as experimental. Treat driver changes, shader packs, and performance as device-specific rather than assuming that a setting that works on one Snapdragon or Mali model will work on another.
#1 Best Overall
- WIDE SCREEN COMPATIBILITY — PHONE TO TABLET: X5 Lite is a versatile phone controller that stretches up to 213mm to fit iPhone 15/16, most Android phones, iPad mini 6/7, and compatible Android tablets. Secure Type-C connection keeps gameplay stable and responsive.
- MOBILE, CLOUD & REMOTE GAMING: Play supported mobile games like Zenless Zone Zero, or stream console and PC games through Xbox Game Pass, Steam Link, Moonlight, and remote play. Enjoy physical controls wherever you play.
- HALL EFFECT STICKS — PRECISE CONTROL: GameSir Hall Effect sensing sticks deliver smooth 360° control for accurate aiming, movement, and camera adjustments. Built for fast-paced mobile games and streamed console or PC titles.
- LIGHTWEIGHT & ERGONOMIC — 135.4G: At just 135.4g, X5 Lite stays lightweight during extended gaming. Ergonomic, laser-engraved textured grips provide a secure, comfortable hold at home or on the go.
- CUSHIONED MEMBRANE CONTROLS — COMFORTABLE & QUIETER: Cushioned membrane buttons and triggers provide comfortable feedback for repeated inputs while keeping operation quieter. Ideal for extended sessions or gaming in shared spaces.
Use this graphics setup order
Changing settings in the right order avoids chasing stutter that is actually caused by missing shaders or an incompatible driver. Complete each stage before moving to the next.
1. Launch with Vulkan and complete the shader download
Start the Android build and select Vulkan when the renderer is offered. Allow the initial shader-pack download to finish before judging performance. The Android guide warns that skipping the download causes shaders to compile on the device; that process can take minutes and can look like a frozen or very slow start.
- Open the port and choose the Vulkan renderer if prompted.
- When the shader download appears, keep the app open until it completes.
- Restart the game if the guide requests it, then test an actual save area rather than only the title screen.
After a game update, check the shader status again. Recent release notes explain that shader packs can change between releases and may need to be downloaded again. A post-update return to stutter or long pauses can therefore be a shader-cache issue rather than a failing GPU.
2. Select the driver recommended for your GPU
Android first-run setup can open a GPU-driver page. Use the recommendation shown for your exact device model instead of selecting a driver solely because it is newer.
| Android GPU family | Driver to try first | What to expect |
|---|---|---|
| Qualcomm Snapdragon/Adreno | Turnip, when the driver page offers it for the device | The port’s Android guidance identifies Turnip as the relevant option on Qualcomm hardware. Availability and compatibility vary by model. |
| Supported Mali hardware | PanVK, when recommended for the device | PanVK is intended for supported Mali configurations; not every Mali device is supported. |
| Any device without a compatible recommendation | Use the driver path shown by the app | Do not force an unlisted package. If a driver cannot run the game, the app returns to the driver page and reports why. |
Open the driver selector from the documented CTRL pages if you need to revisit it after first launch. On Qualcomm, try the recommended Turnip package first; on supported Mali hardware, try the recommended PanVK package first. Keep a note of the original driver so you can revert if a change causes crashes, missing textures, or a launch loop.
3. Establish a conservative baseline
Set render resolution and frame rate to levels your device can sustain continuously. The project does not publish one universal “best” value or an authoritative FPS table, so start low enough to avoid thermal throttling and raise quality gradually.
Rank #2
- Compatible with Windows and Android.
- 1000Hz Polling Rate (for 2.4G and wired connection)
- Hall Effect joysticks and Hall triggers. Wear-resistant metal joystick rings.
- Extra R4/L4 bumpers. Custom button mapping without using software. Turbo function.
- Refined bumpers and D-pad. Light but tactile.
- Choose a moderate render resolution and a frame-rate target your device can hold in ordinary play.
- Load a busy room and a conversation scene, not just an empty corridor.
- Play for several minutes so heat-related throttling can appear.
- Increase only one variable—resolution or frame rate—by one step.
- Repeat the same scenes and keep the higher setting only if frame pacing remains consistent.
Recent Android/Vulkan release notes mention higher frame rates, cheaper final upscaling, and Turnip visibility-check improvements. Those changes can make a newer build faster than an older one on the same device, but they do not establish a guaranteed target for every phone. Re-test after updates instead of copying a preset from another model.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall4. Pick an aspect ratio deliberately
The Graphics menu documents four choices: Auto, 16:9, 21:9, and 4:3.
| Aspect-ratio choice | Use it when | Trade-off |
|---|---|---|
| Auto | You want the port to adapt to the current display. | Framing can vary with the device’s native shape. |
| 16:9 | Your display is 16:9 or you want a conventional widescreen frame. | Wider or taller screens may show black bars. |
| 21:9 | You use an ultrawide phone and want that fixed composition. | Other displays can add black bars. |
| 4:3 | You prefer the original-style squarer framing or need predictable geometry. | Widescreen displays will normally show black bars. |
Fixed ratios intentionally add black bars when they do not match the display. Choose the ratio for predictable framing rather than treating the bars as a rendering fault.
5. Enable HDR only after the base image is stable
HDR is available under Graphics, along with a brightness/gamma control. Leave HDR off while you are solving launch, driver, shader, or frame-pacing problems. Once Vulkan, the driver, shaders, and baseline resolution are stable, enable HDR and adjust brightness or gamma for your display.
- If colors, brightness, or the image become incorrect after enabling HDR, disable it and confirm the normal SDR path first.
- HDR quality depends on the display and driver path; the project does not publish a universal HDR calibration value.
- Do not use HDR as a fix for a dark image caused by an unsuitable gamma setting.
Recommended graphics profiles by goal
Use the following profiles as starting logic, not as device-independent presets. Each profile keeps the driver and shader requirements above intact.
Recommended Free Tools
| Goal | Settings approach | What to monitor |
|---|---|---|
| Most stable play | Vulkan, recommended device driver, conservative resolution and frame rate, Auto aspect ratio, HDR off initially. | Frame pacing in busy rooms, long sessions, and conversations. |
| Sharper image | Keep the stable frame-rate target and raise render resolution one step at a time. | Heat, sustained performance, and whether later scenes remain smooth. |
| Higher frame rate | Keep resolution moderate and raise the frame-rate target one step at a time. | Whether the device can maintain the target after it warms up. |
| Ultrawide framing | Select 21:9 on a matching display; otherwise use Auto or the ratio that avoids unwanted bars. | Composition and black bars, not just the number of pixels. |
| HDR display | Stabilize SDR first, then enable HDR and tune brightness/gamma. | Color correctness and driver stability. |
These choices involve real trade-offs: sharper rendering costs GPU time, higher frame-rate targets cost sustained power, and HDR adds another display-and-driver dependency. No published benchmark establishes a universal winner for average FPS, battery drain, or latency.
Rank #3
- Bluetooth Controller for iPhone & Android: Mocagen mobile gaming controller Compatible with all iPhone models (including 18/17 series) and Android devices. Pairing steps: 1. Turn on Bluetooth on your phone and go to the pairing screen. 2. Press and hold the Home button for 3 sec until LED4 flashes. 3. Find "XBOX Wireless Controller" on your phone and tap to pair. Quick reconnect: After first pairing, simply press the Home button once (with Bluetooth on) to reconnect
- Play Most Controller-Compatible Games: This iPhone game controller supports cloud gaming (e.g., Xb*x Game Pass, GeForce NOW), Xbox Remote Play, emulator games, and native mobile games (e.g., Apple Arcade). Enjoy effortless control and play Fortnite, Call of Duty, Roblox, Genshin Impact, and many more anytime, anywhere. Note: Controller only works with games that support controller input, and does not support PS Remote Play
- 5M-Cycle Lifespan & Zero Drift: MC1 mobile gaming controller features a Hall-effect joystick with a 5M cycle lifespan, 2.5x longer than standard carbon-film sticks. Its innovative electromagnetic induction technology ensures drift-free operation, enabling precise character control in intense games and significantly extending this phone game controller durability
- Ergonomic Grip Design: The handle is ergonomically shaped with a l*ser-engraved texture for anti-slip and enhanced grip, effectively reducing fatigue during long gaming sessions. The scientifically designed joystick and button layout ensures smooth operation. Whether for personal use or as a gift, it delivers a more comfortable and healthier gaming experience
- 7-Color RGB Light Ring & 600mAh Battery: The mobile game controller features a 7-color adjustable light ring on the joystick(ABXY button lights can be turned off, but their colors are not adjustable). The lighting is vibrant yet eye-friendly. The built-in 600mAh battery provides up to 6 hours of battery life in brightness mode — enough for a full day of gaming
Connect and map a physical controller
A USB or Bluetooth controller hides the touch controls automatically. That makes a physical pad the simplest way to get an unobstructed view while retaining the port’s remapping options.
Bluetooth setup
- Put the gamepad into its pairing mode.
- Open Android’s Bluetooth settings and pair the controller.
- Launch LostOdysseyRecomp after Android reports the controller as connected, or reconnect it before returning to the game.
- Open Settings → Gameplay → Controls.
- Test every mapped input before starting a long session.
USB-C setup
- Connect a compatible wired controller to the phone or tablet’s USB-C port.
- If the device asks for USB permissions, allow the controller connection.
- Open Settings → Gameplay → Controls and verify the mapping.
- Disconnect and reconnect once if Android does not expose the pad to the game; then check the Controls page again.
The official controls page supports changing controller buttons and keyboard keys. It also includes button prompts and vibration strength, so you can match the on-screen labels to the physical layout of your pad.
Verify the complete button set
Do not test only movement and the confirm button. Check the complete set listed by the port:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- A, B, X, and Y (or the equivalent face buttons on your controller).
- D-pad directions.
- Left and right shoulder buttons.
- Left and right triggers.
- Start and Back.
- Any keyboard-equivalent actions you have reassigned.
Use a menu, a controllable character, and a scene that exercises shoulder or trigger inputs. If a face-button prompt does not match your controller’s lettering, remap the button in Controls rather than relying on muscle memory.
Set prompts and vibration
Choose the button-prompt style that matches the labels you see on the controller. Set vibration strength to your preference; lower or disable it if noise, comfort, or power use matters. The documentation specifies the setting but does not provide battery-drain or latency measurements, so treat those effects as device- and controller-dependent.
Configure the touchscreen when you do not have a gamepad
Open the CTRL menu to edit touch controls. The Android guide documents controls for size, opacity, position, and visibility, allowing you to build a layout around your hands and screen ratio.
Rank #4
- MODERNIZED DESIGN — Experience the modernized design of the XBOX Wireless Controller with sculpted surfaces and updated geometry that enhances comfort and control during long gaming sessions.
- PRECISION PERFORMANCE — Stay on target with a hybrid D-pad and textured grips on triggers, bumpers, and back case for improved accuracy and handling.
- SHARE BUTTON: Seamlessly capture and share content such as screenshots, recordings, and more with the new Share button.
- VERSATILE CONNECTIVITY — Connect via USB-C for plug-and-play on console and PC, or quickly pair and switch between supported devices with XBOX Wireless and Bluetooth support.
- BUILT-IN AUDIO SUPPORT — Plug in compatible headsets using the 3.5mm audio jack for direct voice chat and immersive in-game sound.
Resize and reposition controls
- Open CTRL from the Android interface.
- Increase a button’s size if your taps miss during movement or combat; decrease it if controls overlap the game image.
- Drag controls to a comfortable thumb position, leaving room for camera or menu gestures.
- Adjust opacity so controls remain findable without obscuring dialogue or exploration.
- Save the layout, then test it in a normal gameplay scene rather than only in the editor.
Hide controls selectively or completely
CTRL lets you hide touch elements when you use another input method. A connected USB or Bluetooth controller hides the touch controls automatically, but you can still use CTRL when you need to edit the layout or restore visibility.
If the controls disappear and you need to reach CTRL again, use the documented system-bar and Android-Back behavior to reveal the Android interface, then reopen CTRL. The exact gesture can differ by Android navigation mode, so test it before beginning a session.
Diagnose common Android problems
The game returns to the driver page
This indicates that the selected driver cannot run the game on that device. Return to the recommended driver shown for the model, or restore the previous driver package. Do not keep forcing an incompatible Turnip or PanVK build.
The first launch appears frozen
Check whether shader downloading was skipped. The port can compile shaders on-device instead, and the guide says that compilation takes minutes. Let it finish once, then restart and allow the shader-pack download on the next setup.
Performance degrades after an update
Look for a shader-pack prompt. Release notes state that shader packs can change after updates and may need to be downloaded again. Rebuild the shader cache before lowering every graphics setting.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frame rate is acceptable briefly, then falls
Heat-related throttling is a likely explanation when a setting works cold but not during a longer session. Return to the conservative baseline, lower either resolution or the frame-rate target, and retest the same busy scenes after the device warms up.
Best Value
- Compatible with Android devices and fits mobile devices ranging from 100mm to 170mm in length.
- Hall Effect Joysticks and Triggers
- Refined bumpers and D-pad. Light and tactile.
- 2 Pro back paddle buttons
- Profile button. Wear-resistant metal joystick rings. Turbo function.
Textures or visibility look wrong on Qualcomm
Confirm that the recommended Turnip driver is selected for your model and that the port is current. Turnip visibility-check improvements are specifically mentioned in recent release notes, so an update can change results. If the recommended driver still fails, switch back to the last known-good driver and report the model and driver version to the project rather than guessing at unrelated settings.
Touch controls cover the image
Open CTRL and lower opacity, reduce size, move the controls toward the bezels, or hide elements you do not use. If a physical controller is connected, Android should hide the touch overlay automatically.
A controller connects but a button is wrong
Go to Settings → Gameplay → Controls, remap the affected input, and test A/B/X/Y, the D-pad, shoulders, triggers, Start, and Back. Check the selected button prompts as well; a prompt mismatch can look like a mapping error even when the input is working.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow to choose between graphics and control options
When comparing two setups, judge them on the factors that affect your own sessions rather than on a single peak frame-rate number.
| Decision | Compare | Practical question |
|---|---|---|
| Graphics profile | Sustained frame rate, image sharpness, shader-compilation behavior, heat and battery impact, and driver requirement. | Does it remain smooth in busy rooms and conversations after the device heats up? |
| Bluetooth versus USB controller | Mapping reliability, latency, ergonomics, vibration, portability, and automatic touch hiding. | Does the pad stay connected and expose every button you need? |
| Touch versus physical controls | Thumb reach, overlay visibility, remapping effort, and screen space. | Can you operate menus and movement without accidental taps? |
| Fixed versus Auto aspect ratio | Predictable composition versus use of the full display. | Are black bars preferable to a changing or stretched frame? |
The official documentation does not publish a universal controller-latency ranking, battery test, or average-FPS benchmark. Any claim that one retail controller or one Android model is always fastest would go beyond the available evidence.
A repeatable tuning checklist
- Confirm 64-bit Android 8.0 or newer and Vulkan support.
- Launch with Vulkan and complete the shader download.
- Select the driver recommended for the exact device: Turnip for qualifying Qualcomm hardware or PanVK for supported Mali hardware.
- Start with conservative render resolution and frame-rate settings.
- Choose Auto, 16:9, 21:9, or 4:3 according to the display and your tolerance for black bars.
- Test a busy room and a conversation after the device has warmed up.
- Raise one graphics setting by one step, then repeat the test.
- Enable HDR only after SDR rendering and the driver path are stable.
- For a pad, pair Bluetooth or connect USB-C, then verify every input in Settings → Gameplay → Controls.
- For touch, open CTRL and set size, opacity, position, and visibility.
- After every port update, check whether shaders need to be downloaded again.
Bottom line
For most Android players, the dependable starting configuration is Vulkan, the model-specific recommended driver, completed shaders, conservative resolution and frame-rate targets, and Auto aspect ratio. Add sharpness or frame rate one step at a time, and postpone HDR until the image is stable. Use a USB-C or Bluetooth controller when possible—the port hides touch controls automatically—and use Settings → Gameplay → Controls to verify and remap every button. CTRL provides a practical fallback for a fully customized touchscreen layout.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
