Is there any way to set different scaling for different applications in Phosh? Or, does anyone know of another shell that works better with lower scaling percentages?
Phosh works best at the default 200% scaling, but Firefox works, much, MUCH better at 100% scaling (and even then there is still not quite as much space as I would like). In addition, Squeekboard has huge margins on any scaling amount that is not a multiple of 100. It would be incredibly useful to be able to set 100% scaling for Firefox and other applications that heavily benefit from it, and 200% for everything else.
With Firefox, this appears to not do anything all. All GUI elements are exactly as oversized and crowded as before, and web pages still require scroll bars.
Or, does anyone know of another shell that works better with lower scaling percentages?
Phosh works fine at 100%. Your problem is not the shell but that about all applications (rightfully) have tiny buttons, scrollbars, input-fields, etc. If that doesnât bother you, you can run fine at 100% (scale 1).
With Firefox, this appears to not do anything all. All GUI elements are exactly as oversized and crowded as before, and web pages still require scroll bars.
I want applications that heavily benefit from it to have tiny buttons. My problem is that when doing this the shell has tiny buttons too, and doesnât adapt to it well, with areas like the lock screen ending up with huge amounts of empty space.
I think you are talking past each other. Scaling factor (200%, 175%âŚ100%) from Settings / Display settings is different than scale to fit via the Mobile Settings app (you need to have the app, FF or other, running before using is, as it only shows switches for those).
Right. What I see in that last screencap is âscale to fitâ, as in, it has transformed the layout to fit a vertical mobile screen - it has changed compared to your previous âFF at 200% scalingâ image (look at the keyboard and textbox for instance). All the FF elements are now present. But this isnât what you are looking for. You seem to be looking for them to be smaller and fit even more stuff there - âto fitâ doesnât do that. This is the part that Guido missed, if I understood correctly.
Iâd approach this for a different direction. Iâd like to have the Display scale factor to be actually usable (Iâd prefer to use 150% or 175% with L5) but then A) it would have to be persistent, and B) not effect keyboard/squeekboard and the top menu.
I believe you are confusing it with the 150% scaling image. The 200% scaling image does not have the keyboard or text box open; only the 150% image does. The 200% image does have Tree Style Tabs open while the new one does not though; so I (initially misunderstanding what you were saying) took a new screenshot with Tree Style Tabs open for a slightly better comparison:
Basically, for every mobile-oriented application, and especially the top menu and Squeekboard as you mention, and especially especially the lock screen, I want 200% scaling, but for anything which benefits from a lot of buttons, I want 100%. Firefox works completely correctly at 200% scaling, which is why scaling it down does nothing, but addons do not, websites have scroll bars too often, and the GUI takes up too much space, making it a much less pleasant experience than 100% or 150%.
Edit: Seeing the gsettings command in one of your very helpful links, I wonder if there is some setting I can change, either in GTK or in Firefox itself, that simply disables DPI scaling. That would probably be a quicker, easier fix than trying to figure out a way for the compositor to give a different DPI scale to different applications.
Just from usability perspective, even if the vertical would be scaled and made better (which would be nice), turning the phone and using a landscaped view is sometimes a must. Even if scaled. And even then scaling probably is needed.
Above, it looks like there are two versions of the Compositor screen: one that has a âScale to fitâ option at the top, and one that has a âScale down all applicationsâ option at the bottom.
I recognize the latter one, not the first one. They seem to be the same option, though. Or am I wrong in thinking that?
