"FATAL: kernel too old" is probably an issue for S2. Do you know where the message is coming from, glibc? glibc is provided in Flatpak by its own platform, that's gonna be hard to patch.
Regarding general progress with Flatpak and Angelfish.
KDE platform added new type of extension - input plugins - which allowed me to distribute Maliit plugin as an extension in Flatpak. This depricates a hack used to package Flatpak extension in RPM and users will have to install Maliit using org.kde.PlatformInputContexts.MaliitSailfishOS :
Right now 5.12 still has to be built, there were some Flathub internal issues with that runtime. As soon as its done, I'll let you know.
Note that after installing extension, you should remove flatpak-maliit-plugin-qt package in SFOS. Next version of Flatpak Runner will not use it.
Next, I managed to improve HW acceleration in WebEngine. I found the set of environment variables that, while not fully using HW acceleration, seem to make Angelfish reasonably fast. Flatpak packaging scripts have been developed further to improve playback of videos. Right now, it looks like all the sites I have visited are playing as they should. My issues with the acceleration are reported as a bug in https://bugreports.qt.io/browse/QTBUG-82423 and there is a hope it will be resolved at some time.
All this will become available with the next release of Flatpak Runner (waiting for KDE platform rebuild) and Angelfish (maybe will have to ask for it the lead developer). Assuming that the next SFOS will have updated libhybris, it all comes right on time.
"FATAL: kernel too old" is probably an issue for S2. Do you know where the message is coming from, glibc? glibc is provided in Flatpak by its own platform, that's gonna be hard to patch.
I don't know how can I check this message is coming from where. If you an idea on how to check,I appreciate if you let me know.
Regarding that post, I did respond on that already.
After reading your post about the general progress of Fltapak where you mentioned you might need to contact the main developer of Flatpak. Is it worth to as them to try to apply the glibc patch that elros provided? If they can apply that, this can make Flatpak available for the wider audience like my S2 with that old kernel.
Can you please check if xdg-dbus-proxy is installed? Maybe I am missing some dependency...
I just have checked my Nexus 5 and can confirm yes, xd-dbus-proxy is installed.
What I spotted on my Nexus 5 was the version of libhybris. It is 0.0.5.33+master.... while in the install instruction you said Flatpak is required libhybris >= 0.0.5.34
How can I get the newer libhybris?
I am happy to build a new sailfish image if I know what to change in there to get the newer libhybris.
I just have checked my Nexus 5 and can confirm yes, xd-dbus-proxy is installed.
Souldn't we install the flatpak-libs package?
No, flatpak-libs is not needed on device. Have you rebooted after installation? Other than that, I am out of ideas on why that xdg- missing error is issued
I don't know how can I check this message is coming from where. If you an idea on how to check,I appreciate if you let me know.
Regarding that post, I did respond on that already.
After reading your post about the general progress of Fltapak where you mentioned you might need to contact the main developer of Flatpak. Is it worth to as them to try to apply the glibc patch that elros provided? If they can apply that, this can make Flatpak available for the wider audience like my S2 with that old kernel.
The best I can come up is to grep inside flatpak platform. As in
flatpak run --command=sh org.kde.mobile.angelfish
then in the opened shell, try to grep files in /usr
As for patch, I don't know who to ask. I am mainly in contact with some KDE developers. That type of question should probably belong to freedesktop-sdk IRC/Matrix channel or their issue tracker in gitlab. But try to see first which file has the error message and proceed from there.
)