Scroll lag in webOS 2 - Githubissues

nerojdn commented 3 years ago

Hi, first of all I would like to thank you for the extraordinary work you are doing.

THANKS!

I don't know if compatibility with WebOS 2 is intended. I have tested with the emulator, and also on my LG UF8519 -2015- (2.0). In both cases, after logging in, it does not finish loading the blocks on the main page (loading icon). The worst thing, however, is that if I enter a library to list the content, it is impossible to scroll down, the delay is several seconds and makes the application unusable. Is it possible that the cause is the use of iframe? It seems that different versions of WebOS work differently depending on what type of container is used ... So I was wondering if you were planning to support WebOS 2. I have tested ScreenPlay with Jellyfin and it handles scrolling perfectly, so I guess the reason for the above problem shouldn't be the lack of power from the TV. I hope you can solve it.

marine1988 commented 3 years ago

Yes I have the problem to my app lag a lot. Any fix?

anthonylavado commented 3 years ago

We would like to support as many versions of TVs/Devices as possible, but it's likely that this is the iframe issue, as mentioned. We're sort of "cheating" compared to something like Screenplay in that we're really just opening a web session to the server, rather than recreating the client locally. I don't know that there's an easy fix without having to write a "complete" app for webOS,

hoangchungk53qx1 commented 3 years ago

how to send key Enter or OK in swift using WebOS SDK, help me

nerojdn commented 2 years ago

Hi @anthonylavado, I'm testing release v1 over my old LG (webos 2.2.3). Server version is 10.7.6:

Navigating through the libraries is still a bit of a pain. The reproduction however is very good. Well, regarding navigation, scrolling and others, I have discovered something as a developer that has caught my attention. Every time an image is displayed, the server is asked. What has caught my attention is that in the logs it always indicates that there is a slow connection, and being in a local network it seems strange to me. My curiosity as a developer has made me go to the call and I have seen that it looks like a normal call with parameters, among which is the ID of the image, combined with others that seem to shape its size and quality. If this call was not resolved by the server delivering an image properly adapted to the indicated size, could it be that the original image was being delivered (that is, quite heavy), indicating to the client that it be the one that adapts it to the size of the container ? I mean, if this were the case, the work would be done by the client, which would be working with many high resolution images at once while the user was browsing through the libraries. In my opinion this would justify the poor performance while scrolling.
On the other hand, the TV browser has a much better performance showing the libraries, maybe it works better adapting the images (sorry, but I don't know how the webos client is implemented).
Finally, I wanted to point out that in this version all the images are blurred and do not finish loading. I've been reading that this is a known issue, but wanted to know if there is a workaround. NOTE: They look fine on the TV browser, so I don't think re-downloading the images from the libraries will work.

As always, thank you very much for the work you are doing. If you need me to try something from the webos client on my TV (webos 2.2.3) I am at your disposal.

nerojdn commented 2 years ago

I correct myself. Blurred images error is related with my TV's memory. If I close all tasks, open jellyfin, close tele task, open tele, close jellyfin and open it again, then it loads all images perfectly.

LG 49uf8517, webos 2, year 2015, 1500 euros.

I'm sorry, but I will not buy LG again.

jellyfin / jellyfin-webos

Scroll lag in webOS 2 #35