Repository navigation
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: device-specificOnly manifests on certain devicesOnly manifests on certain devicese: impellerImpeller rendering backend issues and features requestsImpeller rendering backend issues and features requestse: impeller-naughty-driverDevices & drivers that may be behaving unexpectedly and may need workarounds.Devices & drivers that may be behaving unexpectedly and may need workarounds.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.platform-androidAndroid applications specificallyAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versionteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Description
Steps to reproduce
I have not yet tried to build a minimal app to reproduce the issue.
The App was recently ported from Flutter 3.19 to 3.24, and today I tried the App using Impeller, to see if any issues would occur.
The App was build using the AndroidManifest.xml metadata:
<meta-data
android:name="io.flutter.embedding.android.EnableImpeller"
android:value="true" />And is running in Release mode on a Huawei P40 Pro+ (Android 10).
Expected results
There are no visual glitches during Animations
Actual results
There are visual glitches during animations, like on the bottom bar or in scroll views.
Interestingly the glitches can not be captured using on-device screen recording.
Code sample
Code sample
I have not yet built an example to reproduce the issue.
If this is needed, I will try to make one.
[Paste your code here]Screenshots or Video
Screenshots / Video demonstration
petal_20240820_155018.mp4
Logs
Logs
[Paste your logs here]Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.0, on Arch Linux 6.6.35-2-lts, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2024.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.1)
[✓] Connected device (1 available)
[✓] Network resources
! Doctor found issues in 1 category.Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: device-specificOnly manifests on certain devicesOnly manifests on certain devicese: impellerImpeller rendering backend issues and features requestsImpeller rendering backend issues and features requestse: impeller-naughty-driverDevices & drivers that may be behaving unexpectedly and may need workarounds.Devices & drivers that may be behaving unexpectedly and may need workarounds.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.platform-androidAndroid applications specificallyAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versionteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Activity
jonahwilliams commentedon Aug 20, 2024
We need both example code that reproduces the problem and the model of the android device this reproduces on.
AtjonTV commentedon Aug 20, 2024
Ok, I will try to build an example tomorrow.
The device is a Huawei P40 Pro+ (Model: ELS-N39) running EMUI 12.0 (Android 10).
AtjonTV commentedon Aug 21, 2024
I have built a minimal app to reproduce the issue:
https://github.com/AtjonTV/impeller_test
It is a bit more complex because I rebuild the basic architecture of the production app.
This is now build using a different Host, running on the same device (P40) and this time I confirm it glitches in debug mode too.
New Host
flutter doctor:Details
Here is the log output:
Details
AtjonTV commentedon Aug 21, 2024
I just installed a release build of the sample on another device, and it has very similar glitches. They start out being barely noticeable but start to become more pronounced the more I switch between the nav bar items.
It's a Samsung Galaxy A10 (Model: SM-A105FN/DS) running One UI 3.1 (Android 11).
jonahwilliams commentedon Aug 21, 2024
Log messages indicate the Vulkan driver on the device may not be fully functional. Needs more investigation
AtjonTV commentedon Aug 21, 2024
I will try to get a Log from the Samsung. Sadly, it has issues with USB-Debugging getting reset every few seconds, so I am not sure if I can get them.
AtjonTV commentedon Aug 21, 2024
I am able to get logs from the Samsung, but the Glitches do not appear on it if the app is in debug mode.
Not sure why they are only visible in release mode on the Samsung.
Here is the log, though I think its useless:
Details
Here is a
adb logcatfrom the Samsung with the app in release mode:Details
huycozy commentedon Aug 21, 2024
Hi @AtjonTV, can you check if this device supports Vulkan? Please see https://docs.vulkan.org/guide/latest/checking_for_support.html#_android.
Please also try running app in profile mode on Huawei P40 Pro+ and observe Devtools to see if many janks appear.
AtjonTV commentedon Aug 21, 2024
The Vulkan app is Android 12+ and the Samsung has Android 11.
In the Performance tab I can see some Raster janks, but they don't always show up at the same time as it glitches.
I hope that I am looking in the right spot?
Also, here is an export from the Performance tab:
dart_devtools_2024-08-21_13_16_24.680.json
AtjonTV commentedon Aug 21, 2024
Samsung has a GPU Debugger and its overlay says Vulkan.
33 remaining items
tom-anders commentedon Sep 4, 2024
I'm seeing similar issues with flutter
3.25.0-0.1.preon a Motorola Moto G52 (Android 13).flutter channel masterdid not fix the issue. Interestingly,3.24does not have any issues for meLightningDev1 commentedon Sep 13, 2024
Experiencing the same issue on a Huawei P30 Pro (Android 10) using latest stable Flutter version.
gaaclarke commentedon Sep 26, 2024
Some people that are seeing issues here may be the same issue which was reported in #154778, which has been confirmed to be fixed on
main. It's hard to distinguish one glitch versus another visually.I tried to reproduce this issue with a Pixel 4a (since it reproduced the issue in #154778), but was unable to reproduce it, confirming it is a different problem.
jonahwilliams commentedon Sep 26, 2024
@gaaclarke the problem on the P40 was that the AHB swapchain wasn't working, so I disabled it based on vendor id/api level.
jonahwilliams commentedon Sep 26, 2024
(That was confirmed by me locally, but the p smart z might be different)
bdezso commentedon Oct 10, 2024
Similar glitch with the current master branch on P30 Pro
jonahwilliams commentedon Oct 18, 2024
We've disabled the Android Hardware Buffer (AHB) swapchain on all 29 devices. That may cover some of bugs listed here.
fayax555 commentedon Nov 30, 2024
I experience a similar visual glitch on my Redmi Note 8T (GPU: Adreno 610) with Impeller during animations. The issue is fixed when I disable Adreno 610 from my locally built flutter engine like this flutter-team-archive/engine#56216.
jonahwilliams commentedon Dec 3, 2024
@fayax555 can you file a new bug for that one? We can add Adreno 610 to the list, its a little bit suspicious that I'm allowing older Adreno's than 630 given that we confirmed that one doesn't work at all..
jonahwilliams commentedon Jan 15, 2025
I'm closing this as fixed by disabling SurfaceControl, as I haven't heard back from the original issue filer (and I can reproduce the fixes on my own Huawei devices)
github-actions commentedon Jan 30, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.