(Sorry for my poor English)
简体中文 || English
A Gearlock package for install libhoudini translation on x86_64 Android11,extracted from Windows Subsystem for Android™️ (WSA).
Only supports x86_64 Android11.
- Computer:Lenovo Legion Y7000 2020 (82AV)
- CPU:Intel core i5-10200H
- GPU:
- Integrated Graphics:Intel(R) UHD Graphics 630
- Discrete Graphics:Nvidia GeForce GTX 1650
- RAM:16GB DDR4 (8GB+8GB)
- OS: AOSP11-stock
- Install Gearlock on Android x86 .
- Download and install this package
- Go to Settings and turn on the arm compatibility switch,reboot.
- Enjoy!
You can use this batch file to extract libhoudini files by yourselves.
Show all
- Arm_32(armeabi,armeabi-v7a)
- /system/bin/houdini
- /system/bin/arm/linker
- /system/lib/libhoudini.so
- /system/lib/arm/*
- Arm_64(arm64-v8a)
- /system/bin/houdini64
- /system/bin/arm64/linker64
- /system/lib64/libhoudini.so
- /system/lib64/arm64/*
git clone https://github.com/AXIM0S/gearlock-dev-kit; cd ./gearlock-dev-kit
./configure; rm -rf ./workdir
- choose "3) Custom Core Package"
git clone https://github.com/natsumerinchan/libhoudini-package.git workdir
rm -rf ./workdir/*.md ./workdir/LICENSE ./workdir/.git ./workdir/.gitignore
./build
- choose "1) I configured it manually"
pm install --abi %ARCH% %APK_PATH%
ARCH:
- armeabi
- armeabi-v7a
- arm64-v8a
- x86
- x86_64
1.Blue Archive (Can open the title page, but it crashes on loading.)
-
Due to app's data is not recognized it will make the game crash on loading. To fix this, there're 2 solutions :
These method are for people who can be able to compile custom Android-x86 images
-
Make a script that set data permission to 777 whenever an app is being opened (PrimeOS method - NOT RECOMMEND)
- Cherry-pick these two commits : https://github.com/supremegamers/device_generic_common/commit/2d47891376c96011b2ee3c1ccef61cb48e15aed6 https://github.com/supremegamers/android_frameworks_base/commit/24a08bf800b2e461356a9d67d04572bb10b0e819
Result : Tested by SGNight using ProjectSakura-x86
-
Use bind mounting file-systems (RECOMMEND)
The proper way is to use file-systems such as
sdcardfs
oresdfs
so that it can bind mount both apps data or obb correctly. This method is still being used by Android devices today.-
Find a kernel that include the file-systems :
** For
sdcardfs
, check out maurossi or youling257 repo : (recommend to setCONFIG_SDCARD_FS
to =y instead of =m)** For
esdfs
, check out HMTheBoy154 (umbral branch) or youling257 (5.18 branch and above).esdfs
andpkglist
are pulled from ChromiumOS's third_party kernel repo. -
Go to device/generic/common and revert this commit
(These next step are required for people who want to use esdfs instead, which HMTheBoy154 recommend)
- Still in device/generic/common, open device.mk and add these line
PRODUCT_SYSTEM_DEFAULT_PROPERTIES += \ ro.sys.sdcardfs=false \ persist.sys.sdcardfs=force_off
- Go to system/vold, cherry-pick this commit
Result : Tested by HMTheBoy154 using BlissOS 15.6 (Android 12L)
-