webOS Next Release - 1.2.0 #169
Comments
|
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? |
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 |
|
@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. |
Thanks @anthonylavado , will this be for webOS 4 as well? |
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. |
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. |
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. |
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 the basic functionality of this app. As far as I understand this is just a wrapper for the web version.
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. |
My god! Hope you are not serious. 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. |
|
|
|
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 is a very good shout 😅 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 🤔 |
|
|
|
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? |
It means it is available on all devices cc from lg website great work thank you to everyone!
|
|
Now that is good news :-) |
|
It is indeed visible in the store app and I was able to install/login/use on my 2019 webos 4.5 TV. Thank you for everyone who contributed to make this happen! |
|
Once again, thank you to all the Jellyfin community to make this happen! You guys are legends! |
|
Everything is fine here! v3.5. Thank you for everyone's excellent work. |
|
Congratulations on releasing the app for lg tvs 🥳 Now many people can switch 😅😅 Thabks for the hard work devs 🤌🏿🤌🏿🤌🏿🤌🏿 |
|
I just tested it, it works ! Thank you so much for your hard work and time you have spent with LG team. FYI, I had to remove the Jellyfin app installed through Homebrew. It asked again for the credentials, but all the content was still there, fantastic work ! |
|
Finally! Good Job. Let's hope future updates don't take several months to get approved. |
|
I hate to say it but the app isn't available for me in Germany as it seems 🤔 |
I‘m also in germany and could download it with no issues. |
|
Could it be because I still have the developer mode version installed?🤔
EDIT: It was actually because the old version was still installed. Works great now!
|
|
@TheColin21 Yes. To all - I'll be closing down this issue, as we'll be making a formal announcement soon. If you have the developer/homebrew version of the app installed, you'll want to remove that or else the Store version won't install (they have the same package ID). It's still not perfect, but updates will be mostly delivered by updating your Jellyfin server, as the app loads from the web interface there. There are still some tweaks we do need to make to the shipping app, but now that it's in store it becomes much, much easier to clear that hurdle. |
|
@anthonylavado dude you’re a legend. Thank you so much to you and everyone who contributed. Been waiting for this for a long time. |
|
@anthonylavado Many Thanks!!! Great Job... |
|
Great job! Tried my flac music, 1080p tv shows and movies. The only thing not working [out of memory and reboots the app] (although it's asking much I admit) is a direct play of my 4K version of Super Mario Movie, it plays the intro credits and then stops (again, that's a 60GB file so..). I'm not sure if I can edit some settings to reduce the buffer, but I'm open to try things. I still appreciate the work, thanks! |
|
@anthonylavado - my immense thanks for this, it's installed great on my tv and I can finally switch over to Jellyfin from team green. I've been waiting a very long time for this day! Appreciate your work and that of everyone else who has contributed. @martingem - if that's a 4K Blu-ray rip, you may be running into problems with bandwidth (my guess is this is the case as you made it through the credits ok). LG persists in using 100m ethernet adapters on their TVs (to save literal pennies a unit) and 4K BD bandwidth caps out at something like 120m. The way to fix this is to buy one of a very specific set of USB ethernet adapters and plug that into the TV (most don't work but some do, Google is your friend). Works great once you do. If your wifi is good you may be able to validate this is the issue using that, as the wifi bandwidth exceeds that of the ethernet (though reliability is obviously worse). See for example (pretty sure I have the third Cable Matters one on my C8, though it's been a few years): https://www.reddit.com/r/PleX/comments/cg0y03/someone_got_a_usb_gigabit_ethernet_adapter/ |
|
@caeci11ius Thanks for the hints, I'm indeed using a wired connection all the way through (from my MiniPC running jellyfin to my router to the TV). I'll try to see if I can source a compatible adapter, thanks! |
|
You can also try just using WiFi, much higher bandwidth than the bad LG ethernet port. Though if you're running from a mini PC, likely transcoding performance is the issue. Check the 'Playback Info" in the settings while playing the video. In my testing most videos work great, but for full quality Blurays, it kicks into transcoding when it probably shouldn't. I selected AC3 audio and disabled subtitles before pressing play, but it still says "Reason for transcoding: Secondary audio tracks are not supported". Hopefully will be supported in a future update for web. Anyway, great work Anthony, thank you so much for getting this in the LG Store. |
|
This news has made my day. Can also confirm the app is working a charm on my LGTV. Thanks @anthonylavado and team for all your hard work and efforts to get this over the line. Every time I'm chilling on the sofa watching my shows I'm sending my gratitude! |
|
@caeci11ius Just for your curiosity, the Cable Matters (Black one) Ethernet to USB didn't work on my TV (70UK6190PUB). You still fixed my issue: My Beelink S12 Mini has only one Ethernet port and my NAS was connected through NFS through the same router that sends the jellyfin data to the TV. So you can imagine the traffic (in and out that must be too much). So I used the Ethernet adapter to USB as "Input" for my Mini PC for NFS (only ingests from my NAS directly - my TS231P to the Adapter/Mini PC), while my built-in Ethernet is "business as usual" providing Jellyfin (webui and transport). It works flawlessly Direct Streaming HDR10, even though I'm wired. So thank you so much for pointing me somewhat to that solution (having the adapter on hand) :) @TimberAngry unfortunately that route didn't work (tried it) as my wifi module seems to not be working on my 70UK6190PUB. So the solution either had to be wired, or that my mini pc has a Jellyfin player that I could route through HDMI. Fortunately Wired ended up working as stated above. Thanks though, might help others! |
|
thank you :) |
|
Fantastic news here! I was so happy to find Jellyfin in the official content store. I kept forgetting to extend the dev time... A big thank you!!! One note, can this please be added as a GitHub release? https://github.com/jellyfin/jellyfin-webos/releases I checked it first to grab the latest ipk. |
|
Hi there, However I can't find Jellyfin in the content store on my LG HU715QW UST projector... I tried changing the country (I tried with Germany, France and USA) but it did not fix the issue. My projector has WebOS version 6.3.0-5102 (kisscurl-kavir). |
and others
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:
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, 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+
webOS 1, 2/2UF64, 3/3.5, 4/4.5
None known at this time.
The text was updated successfully, but these errors were encountered: