Closed asgerhallas closed 5 years ago
Deploy the app to a Huawei Y6 2018 with Android 8.0.0
does this mean on other devices (and emulator) this doesn't reproduce?
No, not necessarily, I just didn't have any other devices to test on. It does not reproduce in the emulator though. I will see if I can get my hands on some other device tomorrow.
@zoechi I am meeting the same problem with xiaomi 4 Android 6.0. By the way, the same problem with the video_player plugin. (Flutter Channel dev, v0.11.3)
same issue in video player , xiaomi 4 Android 6.0
@zoechi I couldn't get access to another device, sorry.
@asgerhallas that's ok, it just wasn't clear to me if you meant to point out if you see this only on the mentioned device or if this is the only device you tried it with. Thanks for the update.
this issue is good in Flutter 0.7.0
@songfei do you mean this issue is not present in Flutter 0.7.0?
I have experienced a similar issue on an LG-G2 (D802) Device (https://www.lg.com/uk/mobile-phones/lg-D802) running Android KitKat 4.4.2 when using the latest video_player and Flutter (Channel master, v0.10.3-pre.146). I'll try to get my hands on a screenshot.
@recastrodiaz , YES, I confirmed it,
Doctor summary (to see all details, run flutter doctor -v): [✓] Flutter (Channel unknown, v0.7.3, on Mac OS X 10.14 18A391, locale zh-Hans-CN) [✓] Android toolchain - develop for Android devices (Android SDK 27.0.3) [✓] iOS toolchain - develop for iOS devices (Xcode 10.1) [✓] Android Studio (version 3.2) [✓] VS Code (version 1.29.0) [✓] Connected devices (2 available)
video_player and Camera is OK, same code in Flutter 0.11.3 is NOT OK.
Thanks @songfei From this comment in https://github.com/flutter/flutter/issues/24402#issuecomment-439237830, it would seem the regression started in v0.10.2 Would you mind checking if v0.10.1 (https://github.com/flutter/flutter/releases/tag/v0.10.1) works as expected? This should help the flutter team confirm where the regression started. Thanks!
Fixed by https://skia.googlesource.com/skia/+/a6dddeaac902114677b21cb39f423db0f5557b10 (as soon as that rolls into Flutter)
@asgerhallas this should be fixed in the latest release (v0.11.10
, available on the dev and beta channels). Can you please run flutter upgrade
and then verify to see if it's fixed for you?
Fixed by https://skia.googlesource.com/skia/+/a6dddeaac902114677b21cb39f423db0f5557b10 (as soon as that rolls into Flutter)
I also met this issue when play video in flutter_gallery sample on Nexus 5 • android-arm • Android 6.0.1 (API 23), unfortunately after upgrade flutter to 0.11.10, the green block is still exist.
Flutter 0.11.11-pre.2 • channel master • https://github.com/flutter/flutter.git Framework • revision a2a1311a1a (5 hours ago) • 2018-11-26 19:43:10 -0800 Engine • revision 84e3b137a1 Tools • Dart 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)
XiaoMi 4 , Android 6.0 green block is still exist.
facing the same issue. 0.11.10
didn't solve it
Ok, second take... can you please try v0.11.11
(on the latest dev
and beta
channels - available via flutter upgrade
)? Thanks!
Ok, v0.11.13
is live on the dev
and beta
channels, with the latest attempt at fixing this.
Ok,
v0.11.13
is live on thedev
andbeta
channels, with the latest attempt at fixing this.
It is OK on my device. The green block not occur any more.
Great! I'm going to close this issue. Feel free to reopen it if you see this happen again
Hãy giúp tôi sửa cái này E/BufferQueueProducer: [] [hwsched]Can not get hwsched service E/BufferQueueProducer: [] [hwsched] Sched_config_cust.xml is not exit or file is invalid! [] [hwsched] LoadFile error, path:(null), error code:3
Hãy giúp tôi sửa cái này E/BufferQueueProducer: [] [hwsched]Can not get hwsched service E/BufferQueueProducer: [] [hwsched] Sched_config_cust.xml is not exit or file is invalid! [] [hwsched] LoadFile error, path:(null), error code:3
same issue
i have problem when i try to build final apk or using --release
parameter
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 -v
and a minimal reproduction of the issue.
Steps to Reproduce
Logs