Closed anthonylavado closed 3 months ago
Glad to see this is on the upcoming schedule! I'm really excited to have an official webOS app for my TV as DLNA is pretty unstable for me as the only alternative. I hope the remaining work allows a release before the end of the year 🤞
Is this actively being worked on ATM ?
My reasons for asking is because so many features not working correctly like DTS, DV passthrough etc, I'm currently considering buying a Zidoo - Z9x Pro but seems like such a waste of money when potential everything I need is already built-in on my LG G3.
I'm not requesting a release date just want to know if it's worth waiting for the next release.
Any updates on this?
Unfortunately, there are still some problems with the webOS app. The repository gives the impression that there is currently no active development. Is this the case or can we expect a new release soon?
Unfortunately, there are still some problems with the webOS app. The repository gives the impression that there is currently no active development. Is this the case or can we expect a new release soon?
most dev work and issue fixing work is done on the web repo https://github.com/jellyfin/jellyfin-web as far as I'm aware this repo is mostly just the app/wrapper that runs the web code on the TV
@marlop352 Do you know what the relevant issues in that repo are, if any? Are we just waiting for 10.9?
@dyfrgi no idea
I've tested both webOS 5, 6, 22+ issues and both are behaving as LG describes as their "Expected" behavior.
Thank you @heimdyll.
I've had a hell of a time in life and computing lately (installing the SDKs and emulators for LG and Samsung are both absolutely terrible).
I'm going to build the latest package and submit, even if it's without other improvements. That way we just get to more TVs to start.
I'm going to build the latest package and submit, even if it's without other improvements. That way we just get to more TVs to start.
Thanks @anthonylavado , will this be for webOS 4 as well?
I've tested both webOS 5, 6, 22+ issues and both are behaving as LG describes as their "Expected" behavior.
Thank you but Webos 5+ already has a Jellyfin app and those were not affected. The problem in the original post is that WebOS 4 doesn't have an app at all in the store because it fails the mentioned "issues".
WebOS 4 is on TVs from 2019. Honestly it's unacceptable that a 4 year old top tier TV can't use Jellyfin...
I had to switch to emby (which does have a perfectly working WebOS 4 app) in the meantime until this gets fixed.
WebOS 4 is on TVs from 2019. Honestly it's unacceptable that a 4 year old top tier TV can't use Jellyfin...
I understand your disappointment, which I share, but I'd use some extra kindness since this is the result of voluntary work. I surely hope this can be sorted out.
WebOS 4 is on TVs from 2019. Honestly it's unacceptable that a 4 year old top tier TV can't use Jellyfin...
I understand your disappointment, which I share, but I'd use some extra kindness since this is the result of voluntary work. I surely hope this can be sorted out.
Even if it's volunatry work, which I greatly respect, I think priorities should be made. Before implementing new features that not everyone might need and pushing out new versions, the priority should be to get it running on as many devices as possible. The issues here seem very small so I don't understand why it takes months to fix.
WebOS 4 is on TVs from 2019. Honestly it's unacceptable that a 4 year old top tier TV can't use Jellyfin...
You can use the web browser app in WebOS to access Jellyfin in the meantime, that's what I am using whilst I wait for the release.
The issues here seem very small so I don't understand why it takes months to fix.
Being voluntary work people have to give up their own time to implement these changes, life gets in the way sometimes and we'll, that's just life.
The dev team isn't huge unlike other projects out there, and there could well be more ground breaking bugs elsewhere that need fixing sooner or other dependants that are being worked on. Personally I see this as a "feature request" to support more versions of webOS.
There is also the whole testing and publishing process which I think previously has been weeks, if not months to complete. Not down to fault with the Dev team, but more delays on LGs side of things.
https://jacobtomlinson.dev/posts/2022/dont-be-that-open-source-user-dont-be-me/
Personally I see this as a "feature request" to support more versions of webOS.
Personally I see this as the basic functionality of this app. As far as I understand this is just a wrapper for the web version.
There is also the whole testing and publishing process which I think previously has been weeks, if not months to complete. Not down to fault with the Dev team, but more delays on LGs side of things.
Correct, That's why I asked 3 weeks ago if there is any progress. Which has been ignored. The least the devs can do is give us some information. Otherwise we have to assume the project is abandoned. I'm sorry that's just the reality.
WebOS 4 is on TVs from 2019. Honestly it's unacceptable that a 4 year old top tier TV can't use Jellyfin...
I understand your disappointment, which I share, but I'd use some extra kindness since this is the result of voluntary work. I surely hope this can be sorted out.
Even if it's volunatry work, which I greatly respect, I think priorities should be made. Before implementing new features that not everyone might need and pushing out new versions, the priority should be to get it running on as many devices as possible. The issues here seem very small so I don't understand why it takes months to fix.
My god! Hope you are not serious. I'm also impacted by the "problem" of having a webos 4 TV, but I will never dare to write a thing like you did! The devs can choose to prioritize what they want. Even forget about our TVs 😒 It is an open source project, if this is so important for you, feel free to fork the project and fix it. If you will do, I will be glad to follow you 😊
I'm not a big coder but I've helped to fix problems on other projects I was concerned, for others I've waited or switched to other solutions. So you can do...
If you are @radry able to setup jellyfin server you should also be able to install jellyfin in developer mode. It's not that hard as it might feel, it's not perfect solution but it works.
Requested update to allow latest app build on webOS 1.2+.
Now we wait.
Hoping for a positive result 🤞🤞🤞 Thank you for your efforts supporting older platforms!
First roadblock. I'm not entirely sure what this message means. It says it was in relation to webOS 23.
"Upload SDK File MR Version"
Interesting... Nothing online regarding this message, just looking at the message i would assume mr is referring to master version, so maybe it wants you to upload the sdk used. If it is in relation to webos 23 that looks like the brand new software for 2023 tvs, https://allhomecinema.com/lg-webos-23-everything-you-need-to-know-about-lgs-smart-tv-platform/?id=48714313982, in which case the sdk that was used to build it is outdated, or possibly the method used to export the file for upload. never worked with lg specifically but i will download the webos manager in a bit and have a go at it!
Magic Remote
? :man_shrugging:
Magic remote is a very good shout 😅 Have you guys given this sdk a go?
https://webostv.developer.lge.com/
Looks like it is linked to vs code in some way which if it works as it looks will be very convenient 🧐
Updated table from https://webostv.developer.lge.com/develop/specifications/web-api-and-web-engine
Going to try setup the environment now and see if I can test on webos23 🤔
No, I figured it out. It was because I set the minimum version as 1.2.0 since that's the lowest I know someone has tested on. LG's request was this:
If you register as a version other than 1.0.0, it will be supported as MR version. If the 1.2.0 file is approved, the webOS 1.0. platform prompts users who do not have 1.2.0 firmware to update the firmware You can run the app after the update (installation and execution will not be possible until the update) To avoid this hassle, we recommend you register as 1.0.0.
So "Upload SDK File MR Version" must mean "Check your application's Minimum Release version". Edit: A better interpretation is "Check your uploaded SDK built file's minimum release version".
Also I tested on 23 before submitting, so no worries there.
Back at submission again:
They logged in once for two minutes a few days ago. Just waiting since.
Could you post the 1.2.0 installer/ipk please? I can't install from the LG store anyway, I just install with the ipk.
@gut5 Just follow Building with Docker or WebOS SDK on the master branch code to build the ipk. It seems to be v1.2.0. Then, you can install it following the steps from Testing
I have a 2020 webos 5 (5.40.1 as of today) TV. Based on few earlier updates I thought this app is already certified for 5 and 6 milestone of webos. But today in the store I don't find jellyfin. Is that going to change once this release gets approved by LG?
I have a 2020 webos 5 (5.40.1 as of today) TV.
If that's your software version then that is different from your WebOS version. Not very helpful.
To confirm WebOS version to to Settings - General - About this TV - TV Information.
This page has a webOS TV Version.
My software version is also 5.40.10 but my WebOS version is 4.10.0
This weird version mismatch also confused me when I was first trying to confirm my version.
I have a 2020 webos 5 (5.40.1 as of today) TV.
If that's your software version then that is different from your WebOS version. Not very helpful.
To confirm WebOS version to to Settings - General - About this TV - TV Information.
This page has a webOS TV Version.
My software version is also 5.40.10 but my WebOS version is 4.10.0
This weird version mismatch also confused me when I was first trying to confirm my version.
You are right.. If I go inside that screen it shows "4.10.0-10" as webOS TV version.. Bummer.. As of now I have Jellyfin running in an android TV connected to the TV, have to live with it for bit longer I guess.
I have Jellyfin running on WebOS 4 by manually loading the IPK using the developer SDK. Works perfectly well if you are willing to sit and figure out the LG SDK which is admittedly a bit convoluted. I'm happy enough with it for now until LG approve the current version and put it on their store which will hopefully not be too much longer.
Kind regards,
Ben
(Sent from a mobile device, please excuse my brevity)
From: Adarsha @.> Sent: Saturday, December 30, 2023 7:35:47 PM To: jellyfin/jellyfin-webos @.> Cc: Benchamoneh @.>; Manual @.> Subject: Re: [jellyfin/jellyfin-webos] webOS Next Release - 1.2.0 (Issue #169)
I have a 2020 webos 5 (5.40.1 as of today) TV.
If that's your software version then that is different from your WebOS version. Not very helpful.
To confirm WebOS version to to Settings - General - About this TV - TV Information.
This page has a webOS TV Version.
My software version is also 5.40.10 but my WebOS version is 4.10.0
This weird version mismatch also confused me when I was first trying to confirm my version.
You are right.. If I go inside that screen it shows "4.10.0-10" as webOS TV version.. Bummer.. As of now I have Jellyfin running in an android TV connected to the TV, have to live with it for bit longer I guess.
— Reply to this email directly, view it on GitHubhttps://github.com/jellyfin/jellyfin-webos/issues/169#issuecomment-1872590123, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGNCZOQWN2TXNOYGCSPXFDYMBUJHAVCNFSM6AAAAAA3NI65I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGU4TAMJSGM. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi Is anything known yet about the release date of the official version 1.2.0?
Also I would like to thank you for such a great application, thanks to which I don't have to use Plex. 🥇
Super excited for this release! I hope LG can finish their QA this month with no issues that block their approval.
Have to update the top post still. Here's LG's three notes. I have to login to the demo server again and confirm what was being attempted. As a note, we have a separate demo server that has a "curated" selection of content similar to the public one. This was done to ensure there were no issues with testing. As an example, one time they complained that one of the Blender cartoons had a rating of "N/A". I set it to "G - all audiences" and that cleared things up.
Issue ID | Priority | Issue |
---|---|---|
TVAPPQA-9423_12852 | P2 | Text: "Unknown error occurred. Are you connecting to a Jellyfin server?" appears when the Connect UI Button is selected after entering the URL |
TVAPPQA-9429_12852 | P2 | When a random video content is played, a black screen appears |
TVAPPQA-22280_12852 | P3 | When the Enter UI Button is selected on the login page, it does not work |
The "Unknown" error could be related to a load balancer timeout issue we've been debugging for a bit. We've made some changes, so hopefully that's more stable.
For "random video", Edit: I think I figured this out. The first episode of Pioneer One has like 5 seconds of black before the picture fades in. There's sound during this time, but I doubt they have the audio on for anything in the testing warehouse. I've filtered this out of the testing account, but tossed the Blender movies back in to give them something to watch.
I'll be looking at the demo server logs to see what they attempted to play. Everything should be "direct play" (the most basic H264 with stereo AAC audio in an MP4 container), so it won't be a transcoding issue.
For "Enter UI", I don't think a P3 is a show stopper, but I'll have to give their documents a review.
Sorry for the bump, any updates?
Was stopped for some personal stuff, got detailed information on the issues that LG reported. Have to increment the build number and send off again.
Was stopped for some personal stuff, got detailed information on the issues that LG reported. Have to increment the build number and send off again.
Could you post a binary build please?
@gut5 If you've been building off this repo, you have the exact same content. There have been no changes except for build number. I'll attach one later just in case.
@gut5 If you've been building off this repo, you have the exact same content. There have been no changes except for build number. I'll attach one later just in case.
Thanks. I don't have the build tools set up.
IT WORKS!!!!!!!!!
Is there a way to install it on a tv not rooted? Maybe a lager userbase could help to test the app ;-)
UPDATE,
instead westing @anthonylavado time I will explain to all the others (my way to thank him for his great job) in order to install the ipk file I have followed the instructions I've found on this page https://smartdigihere.com/install-third-party-apps-on-lg-smart-tv/ Once installed webOS Dev Manager and configured my tv I've installed the ipk file provided in the previous post. Configured the app on the TV with the quick connect function and here is the MAGIC! everything seems to work as it should. I had no time to do a deep test of the app, but everything seems working. Once again thank you @anthonylavado and all the rest of the community of this project ! :-)
i installed before that way but if it just istalled on server it detects jellyfin webos 1.2.2 but once you did the tv out an restart then the app is back to the one thats in the store + on the server it says LG Smart TV Jellyfin Web 10.8.13
and on a fresh installed one the intro skipper plugin works but once you did the tv out it won't work anymore tis is on lg cx
edit: if i try it in the browser then intro skipper works again :/
Could someone push this to the Homebrew Repo?
Forgot to update the top post. Will do that now.
So far so good. LG still has the app in QA Processing. I saw that they logged in and were able to playback video. No other news yet. Considering I've asked them to test for release against all possible webOS versions, it may still take some time.
Amazing! Thanks for your diligence and hard work @anthonylavado
Can't wait to see it in the App Store!
I am not sure how to interpret this - does it mean that the app is only approved on webOS 1.0 and webOS 5 - so all us with versions in between will not be able to use it?
I am not sure how to interpret this - does it mean that the app is only approved on webOS 1.0 and webOS 5 - so all us with versions in between will not be able to use it?
It means it is available on all devices cc from lg website great work thank you to everyone!
Last update: 2024-03-18, 14:12 EDT (UTC -4)
Latest News
We did it! The app is now live in the store for all shipping webOS versions.
App is in testing with LG. No issues reported yet. We are entering the fourth week from submission. I've asked for all possible webOS versions, so I imagine it's taking time for them to test.
Next Release, targeting more platforms
Previous text regarding plans
## Background and Plan Hi all, I'm just going to go ahead and call the next version as 1.2.0. At the time we sent in the app for certification on webOS 5, there were two conditional pass errors flagged to us. They were deemed P3 (Priority 3), which on LG's scale means: "Minor: Contain a possibility to lead customer's complaint; less chance of the issue inquiry(s); easy to interpret its context". This means that these two issues _**must**_ be fixed for the next submission. My current plan is this: 1. Fix/Confirm fix for two conditional pass issues 2. Add in any small fixes that are easy to put through (including pending PRs) - may include jf-web 3. Submit to LG for all webOS versions Unlike Amazon, you can have a partial platform failure with LG - if the app passes for webOS 5/6+ (like it is now), but for some reason fails webOS 4 (or lower), then they'll publish the app for the versions they deem working. After that, they'll return a spreadsheet to us with any found defects, and then we can target them. It's important to remember there are two parts to this app. There is the wrapper itself (this repository), which holds some code for the initial login, loading the web interface, and some capability reporting (including some overrides to the web profile builder for codecs). After that, the remainder of the interaction is actually the web interface on your own Jellyfin server. In a way, this provides us a method to make sure your app is "up to date". As you update your own Jellyfin server, it loads the new web interface from it. This means that some of the fixes we implement will have to be on the jellyfin-web repo, and at this point, they may only arrive to the public for Jellyfin 10.9. That said, we'll do what we can if there's anything we could fix from this project itself. We already provide a separate demo server for all vendors we submit to (Amazon, Google, Microsoft, Roku, Apple, LG, Samsung), but depending on the nature of the fixes here, I may set up a bespoke testing environment just for LG preview. This won't be open to the public, but I'll try to keep you informed of what release/commit I'd be using to test against. The content is largely the same as our existing [public demo server](https://demo.jellyfin.org/stable), but LG's account is limited only to the TV Show library (containing two excerpts of Pioneer One). This content was specifically chosen because it's family friendly (yes they care, got rejected for that once), and pre-encoded into direct play formats (.mp4, 720p H264 SDR, stereo AAC audio,webvtt subtitles for ENG). Alright, that's enough history and planning.Current Known Issues
The "Unknown" error could be related to a load balancer timeout issue we've been debugging for a bit. We've made some changes, so hopefully that's more stable.
For "random video", Edit: I think I figured this out. The first episode of Pioneer One has like 5 seconds of black before the picture fades in. There's sound during this time, but I doubt they have the audio on for anything in the testing warehouse. I've filtered this out of the testing account, but tossed the Blender movies back in to give them something to watch.
I'll be looking at the demo server logs to see what they attempted to play. Everything should be "direct play" (the most basic H264 with stereo AAC audio in an MP4 container), so it won't be a transcoding issue.For "Enter UI", I don't think a P3 is a show stopper, but I'll have to give their documents a review.
Previous known issues
### webOS 5, 6, 22+ | LG Issue ID | Issue Description | Relevant Links | Status | |-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------| | 22281 | Error Type: Function_ Keypad error Problem: When left/right UI Button is clicked in the Search page, Background is operating. Opinion: When left/right UI Button is clicked with magic remote control pointer, same phenomenon occurs. Expected: When left/right UI Button is clicked in the Search page, Text Cursor should move. Steps to Reproduce: - Start App > Login > Main page > Enter Search Menu - Press random Text > Click left/right UI Button - Check if app behaves as intended. | N/A | ✅ | | 22280 | Error Type: Function_ Keypad error Problem: When Enter UI Button is clicked in the Login page, it does not operate. Opinion: When Enter UI Button is clicked with magic remote control pointer, same phenomenon occurs. Expected: When Enter UI Button is clicked, Keypad should not appear. Steps to Reproduce: - Start App > Login page - Click input filed > Click Enter UI Button - Check if app behaves as intended. | N/A | ✅ | | | | | | ### webOS 1, 2/2UF64, 3/3.5, 4/4.5 None known at this time.