Describe the bug
This may be an issue only for people using Tvheadend as their OTA LiveTv provider (via M3U/IPTV) using the default/standard "pass" profile (pass through mpeg-ts from OTA direct).
I have this issue in the official jellyfin client and your fork. I suspect it's the same issue.
Using the DUNE client LiveTV is, severely broken on my androidtv (fire cube). I get a blank screen when clicking on the livetv client (I assume I should see a guide or something). If I attempt to tune a livetv channel from the top bar/window on the home screen, it may play for a few seconds before it enters the crash loop.
I run the official client, my own client with various fixes (most have PR's into the official master) and DUNE all on the same device.
I also run Emby client on this device, with a Emby backend server that shares this tvheadend instance without any issues.
I have a fix in a draft PR 5422 (and an official issue open) that fixes my problem fully "on my machine" :-). There is also an issue open that goes more in depth. It's in draft because I'm not entirely confident about it yet.... it needs more serious review and investigation.
Just thought you'd like to know about it.....and I'd like to check out your flavor of the client myself :-).
Describe the bug
This may be an issue only for people using Tvheadend as their OTA LiveTv provider (via M3U/IPTV) using the default/standard "pass" profile (pass through mpeg-ts from OTA direct).
I have this issue in the official jellyfin client and your fork. I suspect it's the same issue.
Using the DUNE client LiveTV is, severely broken on my androidtv (fire cube). I get a blank screen when clicking on the livetv client (I assume I should see a guide or something). If I attempt to tune a livetv channel from the top bar/window on the home screen, it may play for a few seconds before it enters the crash loop.
I run the official client, my own client with various fixes (most have PR's into the official master) and DUNE all on the same device.
I also run Emby client on this device, with a Emby backend server that shares this tvheadend instance without any issues.
I have a fix in a draft PR 5422 (and an official issue open) that fixes my problem fully "on my machine" :-). There is also an issue open that goes more in depth. It's in draft because I'm not entirely confident about it yet.... it needs more serious review and investigation.
Just thought you'd like to know about it.....and I'd like to check out your flavor of the client myself :-).