Content DPI is wrongly calculated after 2.1.3.7 update MER#1855
Closed this issue · 9 comments
On Motorola Moto G2 everything is too small and on Motorola Moto X Play everything is too big. Moto G2 has 5" HD display and X Play has 5.5" FullHD display. More details in [https://bugs.merproject.org/show_bug.cgi?id=1855](mer bug)
Does Silica reports correct Theme.pixel ratio?
Could you try to hack a bit some qml file that import Silica by adding (import Sailfish.Silica 1.0):
Component.onCompleted: console.log("================= Theme.pixelRatio:", Theme.pixelRatio)
Or editing the existing attach Component.onCompleted signal handler.
@rainemak i can try i know how to make app so that's not problem. I'll post results later today.
@rainemak Good catch pixelRatio is wrong
[D] onCompleted:41 - ================= Theme.pixelRatio: 0.949999988079071
while i set in droid-configs-device pixel ratio to 1.0. But i don't think its much difference. On Moto X Play Theme.pixelRatio is 1.5 and it's correct and content is still too big
ah sorry it's reported correctly on both. I just had it set to 9.5 and didn't noticed :)
@rainemak what about this? 1396416#diff-0e59a9dc6f6283976430d17c8f4c41a9L404
Confirmed same problem on Nexus 7 2013 everything is too big. 7" FHD. I think more examples thats not working are not needed. No offence just wondering how you gus tested it.
By any chance could check this one again. Is this still valid?
oh my such old issue. This was fixed ages ago.
@Michal-Szczepaniak that's what I thought but I don't have Moto devices.
@rainemak so i'm confirming then that it's fixed :P