[Bug]: Font and UI Resolution on mobile low
Guidelines
- [X] I have encountered this bug in the latest release of FreeTube.
- [X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Describe the bug
Environment: freetube flatpak, 0.17.0-1pureos1, mobile portrait, 720x1440, Librem 5 phone using Gnome GTK base.

Observe Subscriptions font is fuzzy.
Expected Behavior
Font and UI rendered maybe more based on GTK presets or libadwaita.
Issue Labels
visual bug
FreeTube Version
0.16.0 beta
Operating System Version
PureOS
Installation Method (If applicable)
Flathub
Last Known Working FreeTube Version (If Any)
No response
Primary API used
No response
Additional Information
No response
Nightly Build
- [X] I have encountered this bug in the latest nightly build.
I can confirm that my PinePhone Pro running Arch Linux with Plasma Mobile is also affected by this issue. It seems to me that this is a problem related to the 200% system-wide UI scale used by default in Plasma Mobile (and probably PureOS).
Setting the system UI scale to 100% and setting the FreeTube UI scale to 200% causes FreeTube to display properly scaled content at full resolution.
As pointed out in electron/electron#6571, it may be possible to force a 100% scale by placing the following lines in the main process:
app.commandLine.appendSwitch('high-dpi-support', 1)
app.commandLine.appendSwitch('force-device-scale-factor', 1)
AFAIK is not a FreeTube bug, it's due to xwayland being used and xwayland making things fuzzy at 2x. This should be solvable by setting flags for chromium/electron, maybe this AUR buld can help with figuring out a flatpak implementation for avoiding xwayland: https://aur.archlinux.org/packages/freetube-wayland
Yeah I recently got a new laptop and discovered that blurry apps are just a normal thing on xwayland. Turns out that Plasma desktop 5.26 is going to fix this by adding an "allow apps to scale themselves" option in display settings, so we'll see if that makes it onto plasma mobile.
Do you guys think that this can be closed?
While it still might be worth implementing a workaround it seems like the root problem with this is not freetube, so yeah probably.