search

casualsnek / waydroid_script

Python Script to add OpenGapps, Magisk, libhoudini translation library and libndk translation library to waydroid !
GNU General Public License v3.0
1.88k stars 170 forks source link

installing libndk, uninstalling libndk, installing houdini, and then uninstalling houdini leaves libndk uninstallable #119

Closed Kodehawa closed 1 year ago

Kodehawa commented 1 year ago

Title. It's a bit of a cursed issue.

I first installed libndk, then wanted libhoudini to test some performance issues on Azur Lane.

Tried it, it worked fine, but used too much CPU, so I did the following:

The result was going back to libhoudini. If I uninstall libhoudini again (NOT ndk!) I'm left with no translation layer again. Trying to install libndk yields the script installing libhoudini for some reason (even though it says it's installing ndk, and honestly it should be doing that).

You can check this with AIDA 64, as AIDA64 says the CPU is a generic ARM CPU using libndk, while with libhoudini it identifies it as the correct CPU name, but has arm64 capabilities.

My guess is that it's leaving some residual files somewhere, but I honestly have no clue why this would even happen.

Thing is, I'm not completely sure of this. I see libndk on /system/lib64 and /system/lib, but no libhoudini. The behavior of the applications is completely different, though?

Kodehawa commented 1 year ago

image uninstalled libhoudini ^

image ^ installed libndk, but still using houdini -- libndk shows a generic ARM CPU instead - or at least it used to the first time I installed it (restarted container manually separately)

Unless somehow it showing a generic ARM CPU was an issue the first time I installed it, but I'm not completely sure.

can also somewhat confirm libhoudini is still being used because Azur Lane is running better than with ndk, but it uses a lot of CPU -- kind of confused honestly, is there a better way to check?

ayasa520 commented 1 year ago

can also somewhat confirm libhoudini is still being used because Azur Lane is running better than with ndk, but it uses a lot of CPU -- kind of confused honestly, is there a better way to check?

grep "ro.dalvik.vm.native.bridge" /var/lib/waydroid/waydroid_base.prop

Kodehawa commented 1 year ago

can also somewhat confirm libhoudini is still being used because Azur Lane is running better than with ndk, but it uses a lot of CPU -- kind of confused honestly, is there a better way to check?

grep "ro.dalvik.vm.native.bridge" /var/lib/waydroid/waydroid_base.prop

Shows libndk, so closing. Now I'm confused by the fact the AIDA64 CPU string used to be different under libndk before I installed libhoudini. Oh well, I'm gonna trust the prop and say I'm tripping instead.