Changing Android DPI to 480/640 causes the TV Row to be Unbrowsable

[mo123]

Changing the Android DPI to 480/640 on GoogleTV 12 with a 3840x2160 resolution causes the TV Row to be unbrowsable then you can only press right 3-4 times then it jumps back to the first banner icon.

[mo123]

@spocky Hope you can fix this bug so the launcher can be used on all DPI's and 4K resolution. wm density 640 wm size 3840x2160

[spocky]

I can't manage to make GoogleTv work as expected : when I execute these commands to switch to 4k, the home screen tells me that "1920x1080 screen resolution is not compatible with GoogleTv". And everything on the UI is really big. looking at wm size, it doesn't seem to change: Physical size: 3840x2160 Override size: 1920x1080

Edit : got it working with 4k on my shield by using wm size 3839x2160 (which doesn't work on my CCwGTv) and then applying 640 density. With this configuration, Projectivy works as exepected.

[mo123]

I can't manage to make GoogleTv work as expected : when I execute these commands to switch to 4k, the home screen tells me that "1920x1080 screen resolution is not compatible with GoogleTv". And everything on the UI is really big. looking at wm size, it doesn't seem to change: Physical size: 3840x2160 Override size: 1920x1080

Edit : got it working with 4k on my shield by using wm size 3839x2160 (which doesn't work on my CCwGTv) and then applying 640 density. With this configuration, Projectivy works as exepected.

Hi

It works correctly but only for a few hours or days and if you have multiple apps in the tv row then you can only browse to the 3rd/4th icon then it jumps back to the 1st icon.

It seems to happen when you install additional apps or open apps and go back to the launcher homescreen. Also only happens when Edit Category - TV Apps - Sliding Rows Disabled With the default settings - Sliding Rows enabled, it doesn't happen

[spocky]

Ok, I've set it up as you described. For now it works fine. I'll update this comment if I can reproduce your issue. Edit : It's been 5 days I'm using 4k on my Shield (still can't seem to make it work on my CCwGTv), with no issue so far (except it"s a bit less fluid). Either it's device specific (but then I will need more details to reproduce it), or it's fixed in the upcoming build due to all the changes I've made. Let's hope for the latter.

[mo123]

Another user reported the same problem while using a touch mouse remote. I use a G30 airmouse. Perhaps remotes that come with the Shield, Chromecast 4K are keyboard mode only with no mouse mode and they don't cause problems and the problem only lies with airmouse remotes that have mouse mode activated and cause extra input commands to be sent to the launcher.

[spocky]

Yes, as I wrote here, the only time I saw this behavior was not related to the device resolution but to mouse-like movements.

To give you more details, Android Tv components (called "leanback") do not work well (or at all) with mouse or touchscreens. To improve compatibility, I've developped workarounds upon the stock implementation (for now only on horizontal scrolling). These are not perfect (and don't manage "grid" categories correctly) but allow minimal touchscreen usage (which also helps me debugging from my smartphone). This will improve in the future but as this involves hacking into the stock components to patch their behavior, it takes a lot of time for an improvement targeting a small number of users (leading it to not be top priority).

[spocky]

A changed had been made in the upcoming 4.52 to not auto select the first card or the category when it's interacted with touchscreen/air mouse and is not a "sliding row" (or a grid, but that was already the case before). This should fix the behavior discussed here. Don't hesitate to reopen if it's not.