While waiting to here back from Vova it occurred to me to ask if itās possible to go back to Roon 1.1 and see if that makes a differenceā¦ Is this possible?
If you want to reimport, sure. The Roon databases are not forwards compatible, so 1.1 will not do well with 1.2 databases.
Iāve looked at your logs, and the problem is indeed DPI reporting ā itās causing your tablet to be classified as a phone. Iām trying to think of a solution that will fix your issue, while not negatively affecting thousands of phones out there.
On Windows machines with high DPI display you can launch the app with the scalefactor command. I use it on a laptop with a 2560x1440 display to work around the āfullscreenā issue.
Is there something similar in Android that could be used as a workaround?
I stayed with the Lenovo yogaās because I love the built in stand and the huge battery. I got the next model up - much higher specās and a built in projector! Very happy with it!
Ok, I got to the root of thisā¦ and it looks like the others got this right by messing with the DensityDPI setting.
The problem is that Android source code (I checked latest) has a mechanism of detecting phone mode, which is: smallest size * 160 / densitydpi ā if that value is < 600, you are considered a phone, and Roon trusts the OS.
This device, being 10 inches diagonal and 1280x800, should have a DPI of ~150, as per https://www.sven.de/dpi/
The problem is it is reporting a densitydpi of 213 (TV). If they really wanted to stick to the Android steppings, it should be reporting 160 (MEDIUM).
If they did the right thing, Roon would want to run in tablet mode (landscape). But, because of this stupid setting, they are making your 1280x800 tablet feel much more like a 960x600 tablet
NOTE: I also speak to the technology in Android behind all this here:
A hardware team that area and a software team without a clue about product experience. Pretty much par for the course in the world of hardware manufacturers.