
The common theme in: * https://github.com/flutter/flutter/issues/160854 * https://github.com/flutter/flutter/issues/160804 * https://github.com/flutter/flutter/issues/158091 Is that the Samsung exynos chipset has problems with AHB imports. Unfortunately some of the reported bugs are hard crashes/. While I couldn't reproduce the crash itself, it does indicate to me that attempting to feature detect if AHB imports work is probably too risky (and potentially slow, as we'd have to do a read back). While the Vulkan drivers otherwise work, the deivces in question are not able to reliably import AHBs which prevents platform views from working. This may not fix all issues as there could be different SoC models that also have problems. I considered removing 29 support as well, but there are a large number of APi 29 devices that work fine.
Flutter Engine
Setting up the Engine development environment
See here
gclient
bootstrap
Flutter engine uses gclient
to manage dependencies.
If you've already cloned the flutter repository: