speaking of architectures... how does flatpak detects default target architecture?

my tablet kernel arch is x86_64, so i installed org.kde.mobile.angelfish/x86_64 and it works just fine, but navigation bar is blank.

angelfish log from tablet: https://gist.github.com/CODeRUS/f8dc...8897f4c54a1c85

then!

i opened xa2 which have aarch64 kernel, so i removed arm angelfish, and tried to install aarch64 one, but its not available
then i installed org.telegram.desktop/aarch64 but it's failing to start with syscall error: https://gist.github.com/CODeRUS/49bf...3f121229f3c02b

Regarding Website layouts my guess is the user-agent setting in anglefish to request mobile site layouts needs to be tinkered with?

The topic is mentioned in the preliminary roadmap:
https://github.com/KDE/plasma-angelfish

Do we have mobile layout for TMO? As for mobile layout setting, that should work for Angelfish already. At least works on other sites...

Did not realize you talked about TMO only.
No, no mobile view. Only this quasi responsive menu wrap if the page gets to small.

@coderus, lovely headache before going to sleep!

I don't know how it does it. I have though that to run AARCH64, I will have to have flatpak binaries compiled in the same arch. And then you could maybe go down (64bit -> 32bit). Which you absolutely tanked with i386 example (tablet flatpak exec in 32 bit, runs 64 bit packages).

Maybe in ARM its trickier. I get the same syscall failure when running

flatpak run --command=sh org.kde.Platform/aarch64

on XZ2. We could try to look into it further by finding where it fails specifically (seems like in https://github.com/flatpak/flatpak/b.../flatpak-run.c). Let's see if I can check it out tomorrow...

But even if we make it run, we will get into trouble with libhybris as its 32 bit and cannot provide GL drivers for 64 bit AARCH64. Or do I miss something?

this is to be discussed with adaptation devs

tested some kde apps. usable ones:
org.kde.kolourpaint
org.kde.kreversi
org.kde.minuet
org.kde.ksudoku
org.kde.ksquares
org.kde.khangman
org.kde.kmines
org.kde.gcompris

Thanks, this helped.

coderus, I have made a devel version for flatpak which would not fail at https://github.com/flatpak/flatpak/b...ak-run.c#L2753 and then we get AARCH64 applications running as well.

Failing syscall is SCMP_SYS(migrate_pages)

tested on Pure Maps as its available on aarch64. Its slow, no hardware acceleration, that I have to ask about in the porters channel. Had to run directly, without flatpak-runner. The latter messed up something, will have to look into it later.

Angelfish does not have aach64 since its an issue with their infrastructure used for KDE flatpaks.

But all in all, aarch64 maybe available and usable if we get hybris working on it. Will have to file bug regarding migrate_pages though.

I've tested Kodi in Jolla Tablet and it works, but videos are played slow.