Leagoo Lead3 kitkat not working with link2sd

[mirandam]

...
Therefore, I guess it has to do with something within our own systems, although I have no idea what could it be. Does anybody know how does the apk loading process works? Maybe we can find some hint there.

I have one more question, though. Normally, when Link2sd does work, after you move an app to the sd card and you try to launch it afterwards without any reboot, does it open? Now, for me, it doesn't. That's also the case when I move the apk somewhere else (within the same file system) and link it back to the original location. I wonder if that's a symptom of the same underlying cause (not following the symlinks).

You can look inside the apk file when you rename it to zip as it is in fact a normal zip file. In the case of link2sd you won't find much there as it contains a number of compiled ELF binary files (apart from some xml's used for menus and the likes).

On JB when you link an app in link2sd it moves the apk (+libs and data) and creates the corresponding link in /data/app without the need for a reboot, after leaving link2sd you can simply execute the app and it runs.
On kitkat when you link the app a messages appears saying you need to reboot the device, much like when you convert an app to a system app.

As far as I can remember, I've never seen a version of link2sd which claims to be kitkat compatible, the latest only stating lolipop compatibility. But then again, what is compatibility? Is any software producer capable of claiming 100% compatibility whithout being able to test each and every combination of os/rom ?