-
Notifications
You must be signed in to change notification settings - Fork 27.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device using Qualcomm Adreno 308 (supports OpenGL ES 3.0) crashes with current OpenGL ES 3.1 #36130
Comments
Update: rolling back to Flutter stable channel solved the issue, app runs with no issues:
|
My understanding is that you can't force OpenGL ES 3.0 from the gradle file (or any file under your control). Skia should be checking your supported OpenGL ES level by communicating with the GPU driver and generate the shader for that version dynamically at runtime. The crash here could either be a GPU driver bug, or a Skia bug. CC @bsalomon from Skia. Maybe Skia team need a Samsung J6+ and your app to reproduce the issue. Hence for @vortal: can you please attach a minimal Flutter app that reproduces this crash? Alternatively, can you check if flutter_gallery app crashes on J6+? |
My apologies but I have already returned the device to the client, who I borrowed from, hence I won't be able to supply a "crashable" version again nor verify flutter_gallery. Sorry. But the setup at the time was Flutter dev channel v1.8.0 + Gradle 5.1.1/3.4.1 + Dart 2.4.0 with Android Studio 3.4.1 on an i7 Windows box. Either through debug mode with device attached, or running a release version, the crash has been verified at that very point above. |
I'm getting the same kind of error when running a Flutter app on my Summit 2 smartwatch. Funny thing is this app was running fine until the underlying Android operating system was updated - now it's giving me a black screen, and the following output:
Here's my
|
@vortal @markmclaren2 : can you please try uninstall and reinstall the app to see if the crash goes away? We suspect that the OS upgrade may have downgraded the OpenGL version which causes some trouble in our cache. Deleting the app will evict the cache and fix the problem if that's the case. |
Same problem I'm afraid, even after I removed the app from the device, and performed a |
Ok, I'm going to get a Samsung J6+ to do some local testing (hopefully it suffices without needing a much more expensive Summit 2). @markmclaren2 : can you please provide a minimal Flutter app (hopefully just one main.dart with fewer than 200 lines of code) that reproduces that crash? |
I am facing the same problem. Downgrading to the last stable release solved the problem. |
@liyuqian just the standard app produced by |
Same problem on J4+ |
@liyuqian Do you have any update? We have multiple customers calling in regarding their unsupported phone. We also can not downgrade to stable currently due to other important bug fixes in dev. :-( Anything you need from the community to get it one? |
I can reproduce the issue. But I haven't figured out why the issue happened. Will keep debugging further tomorrow. |
On Samsung J6+, I've identified that
Hence this seems to be a driver bug that claims that it supports GLSL ES 3.10 but actually it doesn't. Will discuss with Skia team to see how to work around this bug. CC @egdaniel |
@liyuqian Did you get any response from the Skia team? We are daily receiving calls regarding this issue. |
The fix is coming: https://skia-review.googlesource.com/c/skia/+/237898 |
The fix relanded in https://skia-review.googlesource.com/c/skia/+/238057 |
Some Adreno 308 devices have a driver bug where the GLSL version is higher than the GL version, and attempting to use shaders with that version triggers an error. Change-Id: I5c8996e9771983e547ec75e57b04e2584507727f Bug: flutter/flutter#36130 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237898 Reviewed-by: Brian Salomon <bsalomon@google.com> Commit-Queue: Brian Osman <brianosman@google.com>
This reverts commit 63655b5. Reason for revert: Seems to be happening on more devices than is expected. Original change's description: > Pin the GLSL version to be no larger than the GL version > > Some Adreno 308 devices have a driver bug where the GLSL version is > higher than the GL version, and attempting to use shaders with that > version triggers an error. > > Change-Id: I5c8996e9771983e547ec75e57b04e2584507727f > Bug: flutter/flutter#36130 > Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237898 > Reviewed-by: Brian Salomon <bsalomon@google.com> > Commit-Queue: Brian Osman <brianosman@google.com> TBR=bsalomon@google.com,brianosman@google.com Change-Id: I4df2a01ae5228aa4edb56b35aa7f28807886282a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: flutter/flutter#36130 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237903 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Brian Osman <brianosman@google.com>
Hi when will this be available in the dev channel please? This issue is impacting ~2% of our android users so including ASAP would be much appreciated. |
This fix will be included in the dev channel as soon as 471c805 is included in the dev channel. Our current dev channel v1.9.7 includes commits up to 08/28 while that commit is on 08/30. We're rolling commits into dev channel as fast as we can. Usually a commit will be in the dev channel within a week or so. Hence I'd expect that fix to be in the dev channel either this week or the next week. |
Hi, yesterday I added internal testers with J6+ and J4+ in beta channel 1.10.7 and the black screen still appears. The bad comments on the store keep growing. |
@huergomartin : #37155 seems to be a different issue. let's try to move the discussion there and find a solution. |
I have samsung J6+ still having black screen . flutter 1.9.1+hotfix4 |
I have the same problem with Samsung J6+ and flutter 1.9.1+hotfix6 |
Hello same problem with j6 and j4, Channel stable, v1.9.1 + hotfix.6. |
Maybe is not the best solution, but you can solve temporarily switching to 1.7.8 hotfix 4 |
If the Flutter team still didn't solve this issue then It seems they are working on react native rather than flutter, It is really disappointing waiting since 9/10/2019. |
Bro come on 1.7.8+hotfix.4 |
@andersonmendesdev I'm using the latest in Beta branch and this issue is not happening anymore. |
So unfortunately I can not downgrade there are several corrections that in this version do not exist, such as overflow in dropdownbutton with large text and overflow in row text and among other various corrections. I believe it is best to go to the beta channel less risk I believe. |
@andersonmendesdev we're currently using Channel beta, v1.10.7 and we did not experience more issues than with previous versions on the stable channel. I would really give it a try. |
@sergicastellsague Great we are already preparing a test version using the beta channel. |
@andersonmendesdev @sergicastellsague We had some issues with iOS using v1.10.7, v 1.10.15 seems ok for both iOS and Android. |
Topic in stackoverflow Success on my J4+ device! |
There is still an error if your application uses the firebase_messaging library |
Buenos Días, tengo el mismo problema con mi dispositivo j4+ ¿ya encontraron una solución? |
@santiagorr207 no seu projeto execute |
saben si en la versión 1.12.13+hotfix.2, este error esta solucionado ? |
não sei qual outro hotfix esta funcionando, a cima do 1.7.8+hotfix.4 |
@santiagorr207 It was fixed quite a while ago, indeed 1.12 also has the fix. |
Muchas gracias ¿me puedes pasar el codigo para actualizar? |
To update @santiagorr207 it's quite simple. First of all you've to switch flutter to use the beta instead of stable: |
me sale lo siguiente "bash: /d/Programas/src/flutter/bin/flutter: No such file or directory |
@santiagorr207 this is because you did not set up the environment variables properly. You either do it now: Or just replace "flutter" by the absolute path of the flutter binary file. |
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 |
I have my app running on Android 7 to 9, except on a Samsung J6+ which has a Qualcomm Adreno 308, supporting OpenGL 3.0.
AndroidManifest.xml already contains:
Gradle:
App Gradle:
What am I getting wrong? Is there any way to have the app forcibly compiled with OpenGL ES 3.0 ?
Steps to Reproduce
Run on a real J6+ device.
Logs
The text was updated successfully, but these errors were encountered: