-
-
Notifications
You must be signed in to change notification settings - Fork 172
[flutter-pi] Could not find a suitable DRM encoder. #96
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
Comments
I just pushed some stuff to the develop branch that should fix this. Can you try that out and see if it fixes it? |
Still error :( |
I think you messed something up here. flutter-pi has no commit Just to be on the safe side, could you please delete the whole flutter-pi folder and then check it out again using Also, can you send me the complete output of the |
Here is output from Regarding
|
Okay, thanks Can you try two more things?
|
I've run those commands and here is the output:
|
kmscube with
|
Sorry, I thought I replied to this thread already. I couldn't reproduce the problem in my testing, even when I used a HDMI monitor and changed my
Yeah, it's always one of the cards in Can you try this for me?
|
Make sure your engine binaries and flutter SDK are up to date.
No, that's not possible. Did you reboot between the |
DRM bug related to this issue is fixed probably by executing commands |
Hello,
First of all, thanks a lot for your job!
I would be very grateful if you could help me with the DRM encoder problem when running flutter_gallery.
I've done all the steps regarding installation flutter-pi, but when I try to run flutter_galary on my
Raspberry Pi 4, flutter-pi throws below error:
pi@raspberrypi:~/Projects/flutter_gallery/build/flutter_assets $ /home/pi/flutter-pi/out/flutter-pi .
[flutter-pi] WARNING: display didn't provide valid physical dimensions. The device-pixel ratio will default to 1.0, which may not be the fitting device-pixel ratio for your display.
[flutter-pi] Could not find a suitable DRM encoder.
The text was updated successfully, but these errors were encountered: