foxy-boot Installation Failed OnePlus 5T Pixel Experience Android 10

The Magisk installation log is as follows

Copying zip to temp directory
Installing Foxy_Boot-1.4(5).zip
Device is system-as-root Archive: /data/user/0/com.ysdqy2fL.fZFptxw/cache/flash/install.zip inflating: service.sh inflating: install.sh inflating: module.prop

       Foxy Boot

Powered by Magisk (@topjohnwu)

Extracting module files Archive: /data/user/0/com.ysdqy2fL.fZFptxw/cache/flash/install.zip inflating: bootanimation-arm64-v8a
Checking the binary cannot locate "_ZN7android21SurfaceComposerClient17getBuiltInDisplayEi" ! Unable to link the executable! ! Installation failed

Dec 26 '19 11:12 Davixk

I get the same error on a different device should I open a new issue?

Mar 20 '20 17:03 jeanrivera

The issue is known by now I'm sure, as the issue is with 10 in general

Mar 20 '20 19:03 Masamune3210

same problem/ andr 10

Mar 28 '20 17:03 runalsh

same problem Mi9 Android 10 PixelExperence

Apr 04 '20 07:04 Cryolitia

Same on Mi 8 (dipper), LineageOS 17.1 It's not yet compatible with Android 10 I guess.

Apr 07 '20 16:04 OriginCode

Same issue with mi9t pro with pixel experience 10

May 04 '20 04:05 Agape2077

Same. OnePlus 5. crDroid 6.6 Rom (Android 10)

May 27 '20 13:05 nivicentiu

I think I could add a support for Android 10, but more and more I think that it might be pointless. It seems that it's impossible to replace bootanimation completely because it's started much earlier than magisk mods applied. And when they're applied, replacing bootanimation makes it visible for 2-3 seconds or something like this. This problem was introduced in Android 8.

Jun 15 '20 09:06 kitsunyan

Screenshot_20200816-192126 Same here it's issue with android 10 Device: OnePlus. 6 (Enchilada) Version: Android 10

Aug 16 '20 13:08 geekyshubham

Screenshot_20200828-142241_Firefox_Beta Same here on the HTC U Ultra, Android 10 (LOS 17.1)

Aug 28 '20 11:08 slendidev

Same on OnePlus 5 crDroid 6.9 (Android 10, Kernel 4.4.234)

Sep 13 '20 11:09 qbbr

I think I could add a support for Android 10, but more and more I think that it might be pointless. It seems that it's impossible to replace bootanimation completely because it's started much earlier than magisk mods applied. And when they're applied, replacing bootanimation makes it visible for 2-3 seconds or something like this. This problem was introduced in Android 8.

Probably add in the description that android Q makes it "impossible" because of the way it was designed (as you said the magisk modules load after the boot animation is almost done ) , and maybe make it clear that android 7 or less is supported (and it will work properly ) , on android 8 and up it won't.

Maybe add ~rules~ a guide on how to change it manually (not systemless ) or start offering zip that do it automatically .

@kitsunyan

Oct 28 '20 09:10 motorto

same problem Nexus 6P Pixel Experience Plus 10

Dec 05 '20 20:12 reivajpg

Only good way I see is to replicate the behaviour of LiveBoot by patching the boot partition. It doesn't completely violate the idea of a completely system-less approach, as it won't modify the system partition.

Pros:

Working on new versions
Depending on implementation, we can achieve much more, much earlier, much more efficiently.

Cons:

Having to deal with the boot partition, and as such, incomparability with nonstandard formats and verified boot.
No longer being state-less, making way for inconsistencies and breakages.