Currently, the virtual keyboard input is only enabled when running as weston-desktop-shell. Reported from: https://twitter.com/PakoSStoyanov/status/1391034963030597632

Can't start the Gallery app using the embedder. There are no log messages to help narrow down why that is:

$ ./flutter-client ./gallery/build/linux/x64/release/bundle     

Observed on my x64 system as well as the PinebookPro (rk3399) and PinePhone (Allwinner A64).

Tried with drm client and debug modes as well - still no feedback from the system as to why it doesn't want to start.

Do you have a plan to add a Yocto support for flutter-embedded-linux?

Yocto Layer for the Flutter already exists : https://github.com/jwinarske/meta-flutter

It has support for some of the engines, such as flutter-pi.

There is a mouse cursor that appears even when no mouse is connected, on flutter-pi it only comes up when a mouse is connected however in this case it comes up by default on. This is on a gbm backend

At the moment using the standalone wayland client appears to be made to work only within a Weston environment. My attempts to use the embedder with other Wayland environments such as Plasma Wayland, wlroots based ones like Wayfire result in the following error:

[ERROR][linuxes_window_wayland.cc(627)] Invalid compositor and shell.
Failed to create view controller.

I haven't attempted to run the embedder within Cage or Phosh but I don't expect different results.

From what I can see, this is because the defined shell protocol is specific to Weston's implementation: https://github.com/sony/flutter-embedded-linux/tree/master/src/wayland/protocol

Would using a different shell implementation like xdg allow for more Wayland environments to be supported? Or is the error given by the embedder a result from different check defined somewhere in linuxes_window_wayland.h?

From the Wayland book, I can see the section explaining on how to generate the C headers and glue code. Would experiments with other shell protocols be useful to the project?

My understanding isn't as complete as I would like it to be so I don't know if I'm just using the Wayland client incorrectly in this case.

If we want to display CJK characters using system font, we have to enable fontconfig support. Just add --enable-fontconfig to ./flutter/tools/gn command. Could you please consider enabling this in your CI pipeline when you build the artifacts?

After following the docs, I have been trying to run with Wayland backend, however I get the error which I have been unable to resolve:

./flutter-client --bundle=./sample/build/linux/x64/release/bundle/
embedder.cc (939): 'FlutterEngineInitialize' returned 'kInvalidArguments'. Not running in AOT mode but could not resolve the kernel binary.
[ERROR][flutter_linuxes_engine.cc(221)] Failed to start Flutter engine: error 2
Failed to create view controller.
Failed to create a Flutter window.

Any help would be greatly appreciated! Thanks

Hi, I was wondering if you might be interested in using Ozone to abstract away the back ends for Wayland, DRM, etc.

That would also bring along support for X11, Cast and any future backends as well.

There is no dependency on any other toolkit like GTK or even a dependency on Chromium.

It would bring along support for running headless, using hardware overlays and zero-copy texture uploads for things like low power hardware accelerated video on embedded and desktop platforms.

The documentation implies that libflutter_engine.so has to be installed here:

• https://github.com/sony/flutter-embedded-linux#install-flutter-core-embedder-library and here:
• https://github.com/sony/flutter-embedded-linux/blob/master/BUILDING-ENGINE-EMBEDDER.md#5-install-embedder-library

While this is the preferred method, the libraries can be loaded without placing them in /urs/lib. The following method can be used instead: LD_LIBRARY_PATH=<path_to_engine> ./flutter-client ./sample/build/linux/x64/debug/bundle

This could be useful when:

• Switching quickly between debug / profile / release modes for the Flutter application without replacing libflutter_engine.so

Using PinePhone running ManjaroARM with Plasma Mobile, the DRM backend doesn't work. Device information:

• Allwinner A64
• kernel: Linux plasma-mobile 5.11.4-1-MANJARO-ARM #1 SMP Sun Mar 7 19:22:26 UTC 2021 aarch64 GNU/Linux
• mesa: 20.3.4 (the device is using the Lima driver)

Flutter version:

$ flutter --version
Flutter 2.1.0-11.0.pre.164 • channel unknown • unknown source
Framework • revision ede798e029 (2 days ago) • 2021-03-09 01:34:02 -0500
Engine • revision 2441c476a6
Tools • Dart 2.13.0 (build 2.13.0-116.0.dev)

LLDB trace when running the drm backend:

Process 29798 launched: '/home/kde/flutter-embedded-linux/build/flutter-drm-backend' (aarch64)
[ERROR][native_window_drm.cc(185)] Couldn't get resources
Process 29798 stopped
* thread #1, name = 'flutter-drm-bac', stop reason = signal SIGSEGV: invalid address (fault address: 0x20)
    frame #0: 0x0000aaaaaab2e570 flutter-drm-backend`flutter::NativeWindowDrm::FindConnector(this=0x0000aaaaaac75870, resources=0x0000000000000000) at native_window_drm.cc:215:34
   212 	}
   213 	
   214 	drmModeConnectorPtr NativeWindowDrm::FindConnector(drmModeResPtr resources) {
-> 215 	  for (int i = 0; i < resources->count_connectors; i++) {
    	                                 ^
   216 	    auto connector = drmModeGetConnector(drm_device_, resources->connectors[i]);
   217 	    // pick the first connected connector
   218 	    if (connector->connection == DRM_MODE_CONNECTED) {

I don't have a RPi4 to verify if it is the same issue as the one observed with https://github.com/sony/flutter-embedded-linux/issues/9

I am following steps mentioned in wiki, I tried prebuilt libflutter_engine.so (elinux-arm64-debug, elinux-arm64-release, elinux-x64), but every time, cmake is throwing same issue, I am sharing error here.

[email protected]:build$ sudo cmake -DUSER_PROJECT_PATH=examples/flutter-wayland-client -DCMAKE_BUILD_TYPE=Debug ..
User project: examples/flutter-wayland-client
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ubuntu/flutter-projects/mylxc_flutter/flutter-embedded-linux/build
[email protected]:build$ sudo cmake --build .
[  1%] Linking CXX executable flutter-client
/usr/bin/ld: libflutter_engine.so: error adding symbols: file in wrong format
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [CMakeFiles/flutter-client.dir/build.make:857: flutter-client] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/flutter-client.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Please help me out!

NOTE: I have installed Yocto for cross building Cross Building from x64 to arm64

Thanks in advance

Hello everybody

I would need help installing flutter in a Variscite card equipped with i.MX8M Nano processor.

I started to follow the guide, but it is not clear to me how to proceed and in what order the various steps should be followed.

Then is there a way to compile on a macOS with M1 and then run on this card?

The things that are mostly unclear to me are where it says to refer to the cmake build path, and also where to find the flutter-client it refers to in some places in the guide, but I don't find where this is installed.

Thank you

Hello and thanks again for the package !

I am having trouble to see good performances on my linux device. I am running my flutter app (release mode) on an IMX 8 Nano under Debian 11.

My device has no GPU, 1 CPU with 1 core - 1Go of RAM - 1Go disk space. I run the flutter app under OpenBox in X11.

Animation are very janky and missing a lot of frames (Navigator.push with the default animation), scrolling a ListView above other widgets is also laggy. The CPU is also rising up to 90% while scrolling a ListView.builder. Any Transform.translate animation style is janky.

I would like to run a Wayland compositor but i can't find a good one :

• Weston doesn't run standalone - DRM is not supported and under a Openbox - XFCE it works but the performances are worse.
• GNOME requires 2Go disk space that i have not.

I have seen that you have tested :

May i know which Wayland compositor did you use please ? Do you think my device hardware specifications are enough (without GPU or only 1 core) to run a usual Flutter app ?

Thanks a lot in advance

Note : I have run a basic flutter app with only a ListView.builder inside, the scrolling is rising the CPU up to 90% but the animation is quite smooth on X11 (OpenBox). If i scroll a ListView.builder above a Container that has a Image.asset behind (100x100 with 100Kb), it starts lagging.

From https://github.com/sony/flutter-elinux/issues/124

Because I think that many embedded device have no GPU. I want to know if elinux flutter can run on CPU?

I've worked in quiet a few designs in possible config files to launch the embedder from instead of the just command line parameters. It could help make it a lot clearer to start your application and configurations can be more detailed if we do.

Hi,

I've built the debug wayland recipes using meta-flutter and can run flutter apps in debug mode. Whenever I start a flutter app (by using flutter-client -b /path/to/bundle) I get the following error

flutter: Could not start Dart VM service HTTP server:
SocketException: Failed to create server socket (OS Error: Cannot assign requested address, errno = 99), address = 127.0.0.1, port = 0
#0      _NativeSocket.bind (dart:io-patch/socket_patch.dart:996:7)
<asynchronous suspension>
#1      Server.startup.startServer (dart:vmservice_io/vmservice_server.dart:424:19)
<asynchronous suspension>
#2      Server.startup (dart:vmservice_io/vmservice_server.dart:443:11)
<asynchronous suspension>

and subsequently I am unable to attach the debugger. This also fails when using flutter custom-devices on a host machine to try and debug (same error).

Why would this be, is there a way to see a more verbose log?

Thanks