LDPlayer switching Android version and 64-bit tutorial
In a word: LDPlayer provides two sets of mainstream kernels, Android 9 and Android 7, and distinguishes 32-bit / 64-bit - select the corresponding kernel when "New Emulator" in the multi-opener, or download the official corresponding version. New games, large 3D game selectionAndroid 9 + 64 bit, select when some old games are not compatible with the new kernelAndroid 7。
Key points of this article
- 1. Which Android versions does LDPlayer support?
- 2. How to switch Android 9 / 7 kernel
- 3. How to choose between 32-bit and 64-bit
- 4. Will data be lost after switching versions?
- 5. Which version to choose between old games and new games?
1.Which Android versions does LDPlayer support?
LDPlayer main supportAndroid 9 (recommended), while retainingAndroid 7The kernel is compatible with old games; and is available in 32-bit and 64-bit versions. Most new versions of games already require 64-bit + newer Android. Old games or specific apps may only work properly under Android 7 / 32-bit. Multiple emulators with different cores can exist on a computer at the same time, and they can be used separately according to game needs.
2.How to switch Android 9 / 7 kernel
There are two ways to cut the kernel: ① OpenMulti-opener, click "New Emulator", select Android 9 or Android 7 kernel when creating, and build an instance of the corresponding version; ② Select the installation package corresponding to the kernel version from the official website download page to install. Instances of Android 9 and Android 7 can coexist on the same computer, and you can open which game you play without affecting each other.
Three.How to choose between 32-bit and 64-bit
Select 64-bit for new games, and fall back to 32-bit for old games/compatibility issues.
The 64-bit kernel can run large-scale 3D new games and use up more memory, and is currently the mainstream recommendation; a few old games and apps only release 32-bit packages, or crash in 64-bit, in which case it is more stable to switch to a 32-bit kernel. When it fails to install, crashes when opening, and prompts "Incompatible with this device", try switching bits/kernel first.
Four.Will data be lost after switching versions?
Switching kernels is usuallyCreate a new instance of a different version, the original instance and the data inside it will not change; if you "change the kernel" of the same instance, it is equivalent to resetting the system, and the installed apps and data will be cleared. Please back up important data first or log in to your account to synchronize it with the cloud. Safe approach: Keep the original instance and create a new kernel instance to migrate the game.
5.Which version to choose between old games and new games?
Choose a mantra:New games / Large 3D / Requires higher version of Android → Android 9 + 64 bit；Old games / nostalgia / can’t install the new kernel → Android 7. If you are not sure, use the default Android 9 + 64-bit first. If a specific game cannot be installed or crashes, then create a new old kernel instance for that game. See crash troubleshootingCrashback is compatible with games。
Source:LDPlayer official website · Android kernel version and bit number description. The specific compatibility is subject to the actual situation of each game.
Version and Compatibility FAQ (8 Article)
How to deal with LDPlayer crash prompt "Insufficient memory"?
Add appropriate memory to LDPlayer, close redundant multiple windows and background programs, and lower the resolution by one level. If the computer's physical memory is small (such as 8G), then don't open more. Opening only one LDPlayer will be much more stable. Memory is a hard upper limit, and optimizing allocation is more effective than forcing more memory.
LDPlayer game updates or resource downloads always fail and cannot be accessed?
This may be a network problem: change the LDPlayer network back to NAT mode, check the accelerator, clear the game cache and try again; it may also be that insufficient disk space leads to incomplete resource downloading. Clear the space and then download the game resources again. Prioritize network and space, and most update failures can be resolved.
LDPlayer is stuck on the game login interface or crashes as soon as I log in?
First arrange the network - replace LDPlayer with NAT and install a stable accelerator; then arrange compatibility - change the Android kernel version, switch the rendering mode, and enable VT. If it is a game that requires Google login, you must first install the Google service framework and log in to your Google account. If the framework is missing, you will still be stuck at login.
What should I do if the LDPlayer game screen is distorted, the textures are messed up, or the model is lost?
This is a typical rendering compatibility issue. Switch between OpenGL, DirectX, and Vulkan in the LDPlayer settings and try one by one, update the graphics card driver, and switch the laptop to a discrete graphics card to run. Most of the screen distortion, texture confusion, and model loss can be repaired. For older graphics cards, OpenGL is preferred for greater stability.
What should I do if the clicks in LDPlayer don’t work and the touch points don’t move?
First confirm that the delay is not caused by lagging - turn on VT for LDPlayer to increase the frame; then check whether the key mapping blocks the click, or does not switch to the correct operating mode. If necessary, restart the simulator and reset the key positions. After these two types of lags and accidental touches are eliminated, clicking usually returns to normal.
Can LDPlayer prompt "The device is not supported/the model is not compatible" to be played?
Some games are restricted by model whitelist. You can change the mobile phone brand and model to mainstream models (such as Xiaomi, Samsung) in the LDPlayer settings and try again, which can often be bypassed; if it still doesn't work, it means that the game is temporarily not compatible with this simulator environment, and you can only wait for adaptation or change the game. Actual testing is required.
Is LDPlayer more likely to crash when playing old games than new ones?
Older games are often only compatible with lower versions of Android. If you use the Android 14 kernel of LDPlayer 14 to run very old games, it may crash due to incompatibility; switching to LDPlayer 5 (Android 7) and other lower version kernels and creating a new emulator before playing will be much more stable. To put it simply: old games are equipped with old cores, and new games are equipped with new cores.
When LDPlayer is opened multiple times, will the crash of one window cause the crash of the others?
Under normal circumstances, the multiple windows of LDPlayer are independent of each other, and a crash will not bring down the other windows together; if they all crash at the same time, it is probably because the entire machine has exhausted its resources, or there is a problem with the VT or graphics card driver. Reduce the number of multiple opens, enable VT, and update the graphics card driver, and stability will improve.
Multi-core, compatible with new and old games
Android 9 + 64-bit plays new games, Android 7 is compatible with old games
⬇ Download LDPlayer for free