I found the setting for alpha nav in the Mac client. Can’t seem to find it in android client. Alphabetical navigation is critical if you have a big collection. It could take many, many minutes to thumb scroll from “a” to"p". I would never see any content from the middle of the alphabet.
OK. I just coaxed the tablet into landscape and fullscreen mode and it’s there. For some reason, Roon doesn’t want to re-draw when the device is rotated. On the tablet, if you start Roon with the device in portrait orientation, there’s no alpha nav element. If you start Roon in landscape (on this particular tablet anyway) it complains about screen resolution and offers “maximized” or “fullscreen”. "Maximized doesn’t appear to do anything but start the app. “Fullscreen”, as it turns out, starts the app a la Kindle, with the notification bar hidden and the alpha nav element is there.
Now. I did that once. Now I can’t get Roon into fullscreen mode , or to run in landscape at all. Even with the tablet locked on landscape, Roon starts in portrait. And with no alpha nav.
The business about Roon refusing to run in landscape mode is mysterious, especially given that it did at twice start start in landscape and offer fullscreen mode, which appeared to work, at least once.
I’m going to try an uninstall/reinstall and see what happens… nothing good. Same behavior.
It appears that Roon looks at the viewport and decides under a certain value that it’s dealing with phone and always orients itself accordingly (except when it doesn’t).
Sooo. That’s OK. Portrait is nice enough. But alpha nav needs to be available. especially on a phone, where you can only see a few thumbnails per screen.
If your screen, after compensation for DPI, runs at what our graphics designers have deemed large enough for the full ui, you are in tablet mode (which is similar to the desktop mode). If your machine doesn’t hit that spec, you run in phone mode.
The resolution, post DPI compensation is around 1024x700.
What most people around here call portrait mode is really phone mode, and waht they call landscape mode is desktop/tablet mode.
The phone mode does not really have browsers… you can get to them, but it’s not easy. The phone UI is meant to be a reduced functionality UI, for quick actions based around mobile usage, and not as a primary Roon experience.
It is on the roadmap to make the phone experience first class, but it involves a lot more than just a UI change.
Today I picked up that tablet to check out the tablet version of the way cool fielded filters in “Focus”. Today, Roon refused to run in any way other than in landscape orientation. The tablet’s homescreen was in portrait when I started Roon. Roon’s splash screen came up on its side, Roon asked about running in fullscreen and I took that option. From then forward, Roon was steadfastly in landscape mode. Which was desired behavior - at least what I desire - and everything functioned perfectly. I couldn’t make Roon go back to portrait orientation any more than I could make it switch to landscape two nights ago. Today the tablet was in autorotate mode. (So in theory, an application should redraw from portrait to landscape and vice versa whenever the tablet was rotated.)
So, based on that and what you just said, I am tentatively concluding that:
In “fullscreen mode” this tablet has j u s t enough resolution to run in tablet mode. That’s great by me, if I can somehow rely on it happening, since I don’t have a bigger tablet laying around. (I have a better one. But it’s even smaller.)
Hi, One thing to note is that Roon does not react to tablets screen rotation whilst running. The screen resources are only checked when Roon starts up and once running that mode (tablet/landscape or phone/portrait) is fixed unstill Roon is shutdown.
OK. Only checking on startup makes sense. Or even simply not doing portrait above a certain screen res. Amazon Video behaves that way. Actually, I don’t think it does portrait ever.
The strange part is Roon starting in portrait regardless of tablet orientation at startup one day, despite restarts of the tablet, locking the tablet in landscape, dropping data and cache and even reinstalling, and then starting in landscape the next, again, regardless of tablet orientation.
That may not be a bug in the normal sense. It might just be the program interacting in an unexpected way with this poor-performing tablet. [slips into prognostication mode] On the other hand, I’d judge it to be a matter of concern because there are probably many users will will dedicate a tablet as a remote control, maybe one each in several rooms. As time goes on and people accumulate tablets, that will become more common. I doubt people will dedicate their best tablets as remote controls. Exactly the opposite is more logical. Thus, instead of seeing better hardware as upgrade-itus drives device sales, Roon needs to be prepared for the hand-me-downs. [/prognostication mode]
So, after several days of behaving nicely in landscape mode (after paradoxically starting into landscape from a vertically oriented device), Roon crashed and upon restart reverted to starting into phone mode regardless.
Remember in grade school when they taught us that computers were wondrous devices that could only do simple things but would do them with absolute repeatability? Ah well…
I looked up the specs for that tablet and its screen is 800x 1280. So actually, it should work fine in tablet mode, resolution-wise. (Well, and the fact that it functions perfectly when it feels like it would also suggest that.)
Would an option is settings that forced the mobile client to one mode or another- phone, tablet, fullscreen or not - be a practicable solution for situations like this? (assuming this isn’t just a bug
My guess is that the DPI is funky on that device. I just did an analysis of a Lenovo Yoga 10" tablet (similar resolution, probably same problem). There are some suggestions on DPI fixing stuff there. You should be able to run at 160 (MEDIUM) and take advantage of your 1280x800. My guess is you are running at 213 (TV) or higher and your “virtual resolution” is much smaller than 1280x800.
I’m not sure I follow. If the native resolution of the device is 800x1280, shouldn’t the device report that and thus Roon would be run at 1:1 device pixels to virtual ones? I thought that the OS would only scale if the app was trying to display something that was too small for native. But Roon wants all the resolution it can get (up to a point), if I’m understanding it right.