Mine is ok with 240.
Edit: I remember seeing the exact same DPI problem when using the flatpak builds back then.
Thatās also what Iām using. 240 is a good compromise for text legibility and rendering within the space. Testing with Simon Tathamās puzzles 
EDIT: @rinigus I just noticed while going through the puzzles that drag and drop doesnāt work in the web assembly examples, but that is not a feature request. Just noticed testing: Map, from Simon Tatham's Portable Puzzle Collection
KDE Frameworks have been bumped to 5.105.0. We have now set of scripts that will allow us to update KDE Frameworks and Qt 5.15 releases relatively easily - this should make it possible to keep it all up to date at OBS.
Qt Runner has also been updated to close applications in a more gentle way. As a result, it allows applications to save changes in settings and such when needed.
15 Likes
Just noticed that ktrip and kpublictransport have been added to the github repo. I was about to try those.
Maybe some announcements before the repos go live? Or a quick heads up on IRC?
@rinigus, some libs thatād be nice. For building the KDE games 
KF5KDEGames
KF5NotifyConfig
KF5Crash
KF5XmlGui
KF5NewStuff
KF5DocTools
EDIT: hold those are from an older build. Should I be looking at the latest fedora or suse builds?
EDIT2: Tree - rpms/katomic - src.fedoraproject.org looks like fedora naming.
Good list of libs. Feel free to package them and submit to chum github repo . I suggest to look into one of the packaged KF5 libs and use the same style. We usually take Fedora packages as a start and then edit them to take into account differences in dependencies (have to add opt- and resolve all pkgconfig/cmake requires).
We will just have to make sure that all libs end up mentioned in lists at GitHub - sailfishos-chum/qt5: Qt5 meta package for Sailfish OS: documetation, issues, and scripts - that way we can keep them updated.
Re heads up: sure. As soon as more devs will be doing it
1 Like
On the one hand, thatās really cool, what is done here! It certainly opens up so many possibilities.
On the other hand, I have a big fear that this will kill Silica apps.
Will you continue to care for apps like Fahrplan? Thatās one of my most used apps and the look and feel is head and shoulders above apps like ktrip.
Of course itās your decision, but I also wanted to show my appreciation for your efforts
1 Like
No worries, Fahrplan is not going away anytime soon. Itās not been getting enough love recently.
If, on the other hand, as is now the case, the kde publictransport libs, and consequently the providers, are available, it will offer us an alternative. Fahrplan is still often using very old public facing apis based on Hafas and EFA many of which are dinosaurs. Itās amazing that the binary Hafas interface used for the Deutsch Bahn is still in use as it has nothing to do with the apis that DB offers today.
As for Silica, Iāll certainly continue to use it where I can. But some things I cannot do because of the age and bugs in our QT. Iām hoping this initiative puts a bit of pressure on Jolla to examine what they can do. Sometimes I just package something that I want to use in a Webview hoping to find the time later to build a native thingy.
3 Likes
I have to admit that my understanding of the whole matter is limited, but that is the hope that I, as a layman, also associate with it.
But Iām taking the thread off topic, so Iāll stop at this point.
Thank you and @piggz and @rinigus for the very different but great contributions to the platform!
Port Xperia 5, SO 4.5.0.19. When I start Angelfish I get a picture:
How to fix?
(Xperia XZ2 4.5.0.19 Angelfish working.)
Looks like Angelfish is crashing. Try to run in command line with qt-runner (se desktop file for cmd). Probably some chromium acceleration leads to crash. See chrome://gpu on your device in android chromium and try to replicate with webengine env vars.
[defaultuser@Xperia5-DualSIM ~]$ angelfish
library ālibGLESv2_adreno.soā not found
library āeglSubDriverAndroid.soā not found
angelfish: symbol lookup error: /opt/qt5/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so: undefined symbol: eglCreatePlatformWindowSurface
Thatās something unexpected. I have the same message at start, but egl lib loads. Ask porter for a help. Itās @Thaodan port, right?
Calligra suite would be useful with kio i guess
Radical idea: try a build of all of this against 3.4.x/armv7, to potentially breathe new life into J1 devices? 
4 Likes
its only a few clicks in obs
1 Like
we have a script for it, but it will enable also i486 and aarch64. as for clicks, it is quite a few with the number of libs that were packagedā¦
I get the same when I use the 4.5.x-built packages on my 4.4 device. Not that Iād expect it to work, but sometimes it does.
Got a feedback from eugenio_g7 at SFOS porters channel: you maybe missing this PR in your device (old hybris?): hybris: egl: Provide eglCreatePlatformWindowSurface. by MagneFire Ā· Pull Request #516 Ā· libhybris/libhybris Ā· GitHub
PS: which should also indicate that adding older SFOS releases wouldnāt work very well for Qt 5.15
2 Likes