Fork of SageTV MiniClient for Android TV

[nyplayer]

Originally Posted by phelme

Unlike with the FireStick, no keyboard ever comes up, even with clicking on the keyboard icon in the mini client pop-up. Not for me anyway.

Must be a google TV problem. There are so many limitations with the google TV for example picture in picture does not work when using Channels DVR but it works on Firestick and other Android TV Certified devices. I have completely disconnected mine and put it in storage 2 days after I got it.. So no keyboard would not surprise me.

[phelme]

Originally Posted by nyplayer

Must be a google TV problem.

What's weird is I have a Sony TV with Android from 2015 and with that one the keyboard does pop up in the client. Guess I'll have to talk to Google about it.

[jvl711]

Hi All,

User cncb has been hard at work, and added the following features to the client. The update is under review, but should be approved within the next 24 hours. Thank you cncb for your contributions!

For more info on the external link support see the details in the pull request https://github.com/OpenSageTV/sagetv...lient/pull/102

1.8.0 (5/14/2021)
- Support external links to open videos in other apps directly (Netflix/Amazon).
- Allow display of embedded PGS subtitles in ExoPlayer.
- Add option to enable system sleep.

Thanks,
Josh

[cncb]

I have started a new thread on the External Link support: https://forums.sagetv.com/forums/sho...d.php?p=630059

[Zogg]

So I'm on 1.8.0 and I'm seeing the UI freeze on both my Fire 4k stick and on my Android phone, a Sammie S20+.

Specifically, if I go into Videos and start scrolling down, about 8-10 entries down it will just freeze. Same if I use the page down function, do that twice and the UI freezes. Eventually it will time out and return to the server selection screen.

Also, it only happens when I connect to my Docker-based server running on Unraid. If I connect to my Windows HTPC, which has the same folders mapped, then I don't see this problem.

[jvl711]

Originally Posted by Zogg

So I'm on 1.8.0 and I'm seeing the UI freeze on both my Fire 4k stick and on my Android phone, a Sammie S20+.

Specifically, if I go into Videos and start scrolling down, about 8-10 entries down it will just freeze. Same if I use the page down function, do that twice and the UI freezes. Eventually it will time out and return to the server selection screen.

Also, it only happens when I connect to my Docker-based server running on Unraid. If I connect to my Windows HTPC, which has the same folders mapped, then I don't see this problem.

I know this might be a real pain, but can you try and sideload the previous version and see if you can repro. There was not any intentional changes in those areas, so I am thinking this is either an existing issue, or an issue with your Docker Server.

Either way, knowing if it exists in the previous version will help.

Josh

[Zogg]

Originally Posted by jvl711

I know this might be a real pain, but can you try and sideload the previous version and see if you can repro. There was not any intentional changes in those areas, so I am thinking this is either an existing issue, or an issue with your Docker Server.

Either way, knowing if it exists in the previous version will help.

Josh

Sorry, I made it sound like I'm just seeing this on 1.8.0 but I have seen this on at least the previous version on the Fire TV stick. I don't use the app on my phone all that much but while investigating today I tried and reproduced it. Also, I saw the freeze in the Recordings list also, not just Videos.

Any idea how to troubleshoot this?

[cncb]

Originally Posted by Zogg

Also, it only happens when I connect to my Docker-based server running on Unraid. If I connect to my Windows HTPC, which has the same folders mapped, then I don't see this problem.

This sounds like it could be a networking issue on your Unraid.

[Zogg]

Originally Posted by cncb

This sounds like it could be a networking issue on your Unraid.

Could be, although I don't have it heavily loaded, and none of my Windows clients have this issue, even over WiFi. I do have Sage running in a Win 8.1 VM on the Unraid server though, so I will experiment with that and see if I get similar results.

[Zogg]

I tested with my SageTV server running in a VM on the Unraid machine and it worked just fine, so I went back to the Docker and recreated the problem. Looking in the log file, it appears that the hang is during the displaying or loading of thumbnails:

Sat 5/22 15:47:06.790 [AWTThreadWatcher-4c4445564453@38a27b7d] EventThread-4c4445564453 Hang Detected - hang time = 751 UILocker=null

I have attached the tail of the log file. A Java error is also reported later on but I'm not sure if this is just an artifact of the hang.

Could this be related to the thumbnail issue reported in another thread for the HD200 or HD300?

[stuckless]

Originally Posted by Zogg

I tested with my SageTV server running in a VM on the Unraid machine and it worked just fine, so I went back to the Docker and recreated the problem. Looking in the log file, it appears that the hang is during the displaying or loading of thumbnails:

Sat 5/22 15:47:06.790 [AWTThreadWatcher-4c4445564453@38a27b7d] EventThread-4c4445564453 Hang Detected - hang time = 751 UILocker=null

I have attached the tail of the log file. A Java error is also reported later on but I'm not sure if this is just an artifact of the hang.

Could this be related to the thumbnail issue reported in another thread for the HD200 or HD300?

Does this ONLY happen in the Android MiniClient? We ran into a crash/hang some time ago with thumbanils when the thumbnail filename is very long. You thumbnail is 209 characters long and the max filesystem length on Android in 255 characters... I suspect that IF this only happening on Android client, then you are hitting this problem.

[Zogg]

Originally Posted by stuckless

Does this ONLY happen in the Android MiniClient? We ran into a crash/hang some time ago with thumbanils when the thumbnail filename is very long. You thumbnail is 209 characters long and the max filesystem length on Android in 255 characters... I suspect that IF this only happening on Android client, then you are hitting this problem.

That is probably the culprit, because it DOES only happen in the Android MiniClient. Before I saw your post, I had just disabled video thumbnail generation in Sage.properties and successfully tested it.

Unfortunately some videos I, uh, acquire, do have long names and I don't always shorten them. I will have to go back and shorten those and try again with video thumbnails enabled.

[stuckless]

Originally Posted by Zogg

That is probably the culprit, because it DOES only happen in the Android MiniClient. Before I saw your post, I had just disabled video thumbnail generation in Sage.properties and successfully tested it.

Unfortunately some videos I, uh, acquire, do have long names and I don't always shorten them. I will have to go back and shorten those and try again with video thumbnails enabled.

Yeah, unfortunately, this is a long standing miniclient issue, and the fix is not trivial (at least it wasn't trivial for me... for Josh, it might be very trivial )

[ojones]

Hi Josh & Everyone,

I am working to get the Miniclient functional on several nvidia shields and HiSense tv running google's andriod. Right now I am able to start a recorded stream from the client but am unable to ff/rw (jumps back to beginning and gets stuck in a play/restart loop). I am on the 1.8.0 client from the google store and server side I have 9.2.4 with your updated transcoder and parser.

The video stream was recorded via cablecard using OpenDCT. Playback (and skip ff/rw) is fine in the windows client and the windows placeshifter.

Suspected location in server logs follows (help!!!):
Sun 5/30 8:44:54.456 [EventRouter-594d43554845@1903758d] processUserEvent-UserEvent[ff] evtTime=Sun 5/30 7:53:33.119
Sun 5/30 8:44:54.457 [EventRouter-594d43554845@1903758d] VF.submitJob(VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null])
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VF processing job VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null] nPlayin=true
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VF processing on UI Thread VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null]
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VideoFrame.timeSelected(Sun 4/18 9:00:15.664, true) currFile=MediaFile[id=45082255 A[44515060,44498353,"Against the Odds",78808@0418.09:00,60,T] mask=TV host=Workspace-1 encodedBy=DCT-Ceton InfiniTV Ethernet (00-80-8a-76) Tuner 3 on 192.168.45.60:9000 AHCHD format=MPEG2-TS 0:00:05 12959 kbps [#0 Video[H.264 29.97003 fps 1920x1080 16:9 progressive id=100]#1 Audio[AC3 48000 Hz 6 channels 384 kbps idx=1 id=101 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=102 eng]{ScrapedBy=Phoenix, IMDBID=, SeasonFinal=false, CollectionName=, MediaType=TV, EpisodeCount=0, CollectionOverview=, ScrapedDate=1618754414217, MediaProviderDataID=280558, MediaTitle=Against the Odds, SeriesInfoID=10513883, TagLine=, DiscNumber=0, UserRating=70, CollectionID=0, MediaProviderID=tvdb, TrailerUrl=}] \\workspace-1\tv-rec2\AgainsttheOdds-S01E03-TheHeroesofTarawa-44515060-0.ts, Seg0[Sun 4/18 9:00:00.009-Sun 4/18 10:00:00.003]]
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VideoFrame.timeSelected2(Sun 4/18 9:00:15.664, true) currFile=MediaFile[id=45082255 A[44515060,44498353,"Against the Odds",78808@0418.09:00,60,T] mask=TV host=Workspace-1 encodedBy=DCT-Ceton InfiniTV Ethernet (00-80-8a-76) Tuner 3 on 192.168.45.60:9000 AHCHD format=MPEG2-TS 0:00:05 12959 kbps [#0 Video[H.264 29.97003 fps 1920x1080 16:9 progressive id=100]#1 Audio[AC3 48000 Hz 6 channels 384 kbps idx=1 id=101 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=102 eng]{ScrapedBy=Phoenix, IMDBID=, SeasonFinal=false, CollectionName=, MediaType=TV, EpisodeCount=0, CollectionOverview=, ScrapedDate=1618754414217, MediaProviderDataID=280558, MediaTitle=Against the Odds, SeriesInfoID=10513883, TagLine=, DiscNumber=0, UserRating=70, CollectionID=0, MediaProviderID=tvdb, TrailerUrl=}] \\workspace-1\tv-rec2\AgainsttheOdds-S01E03-TheHeroesofTarawa-44515060-0.ts, Seg0[Sun 4/18 9:00:00.009-Sun 4/18 10:00:00.003]] realDur=3597395
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] seeking numpushbuffers=2730 seekTime=15644
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] MPEG2 seek targetPts=1410840 length=6717535532 durationMsec=3597395 parsedPTS=5175630 lastPos=89455861 firstPTS=2880 mux_rate=0 estimBitrate=1556430
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] Mpeg2Reader seeking to pos=24348632 time=0:00:15.644
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] flushPush0()
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] VF processing job null nPlayin=true
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] isRec=false rd=3597395 base=15644 eos=false
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] VF thread is now waiting for 0:59:41.501
Sun 5/30 8:44:54.459 [Pusher@56a7257f] Seek target=15 actual=13 diff=2
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Seeking again to try to get a better position...
Sun 5/30 8:44:54.460 [Pusher@56a7257f] MPEG2 seek targetPts=1410840 length=6717535532 durationMsec=3597395 parsedPTS=1189440 lastPos=24395641 firstPTS=2880 mux_rate=0 estimBitrate=1850397
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Mpeg2Reader seeking to pos=28009180 time=0:00:15.644
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Seek target=15 actual=14 diff=0
Sun 5/30 8:44:54.463 [Pusher@56a7257f] Disabling I-Frame alignment in pusher since it's skipping too much pts=1798797 startWait=1348347
Sun 5/30 8:44:56.089 [EventRouter-594d43554845@1903758d] processUserEvent-UserEvent[ff] evtTime=Sun 5/30 7:53:34.752
Sun 5/30 8:44:56.089 [EventRouter-594d43554845@1903758d] VF.submitJob(VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null])
Sun 5/30 8:44:56.089 [VideoFrame-594d43554845@6ff4a1ea] VF processing job VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null] nPlayin=true
Sun 5/30 8:44:56.089 [VideoFrame-594d43554845@6ff4a1ea] VF processing on UI Thread VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null]

[jvl711]

Originally Posted by ojones

Hi Josh & Everyone,

I am working to get the Miniclient functional on several nvidia shields and HiSense tv running google's andriod. Right now I am able to start a recorded stream from the client but am unable to ff/rw (jumps back to beginning and gets stuck in a play/restart loop). I am on the 1.8.0 client from the google store and server side I have 9.2.4 with your updated transcoder and parser.

The video stream was recorded via cablecard using OpenDCT. Playback (and skip ff/rw) is fine in the windows client and the windows placeshifter.

Suspected location in server logs follows (help!!!):
Sun 5/30 8:44:54.456 [EventRouter-594d43554845@1903758d] processUserEvent-UserEvent[ff] evtTime=Sun 5/30 7:53:33.119
Sun 5/30 8:44:54.457 [EventRouter-594d43554845@1903758d] VF.submitJob(VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null])
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VF processing job VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null] nPlayin=true
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VF processing on UI Thread VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null]
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VideoFrame.timeSelected(Sun 4/18 9:00:15.664, true) currFile=MediaFile[id=45082255 A[44515060,44498353,"Against the Odds",78808@0418.09:00,60,T] mask=TV host=Workspace-1 encodedBy=DCT-Ceton InfiniTV Ethernet (00-80-8a-76) Tuner 3 on 192.168.45.60:9000 AHCHD format=MPEG2-TS 0:00:05 12959 kbps [#0 Video[H.264 29.97003 fps 1920x1080 16:9 progressive id=100]#1 Audio[AC3 48000 Hz 6 channels 384 kbps idx=1 id=101 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=102 eng]{ScrapedBy=Phoenix, IMDBID=, SeasonFinal=false, CollectionName=, MediaType=TV, EpisodeCount=0, CollectionOverview=, ScrapedDate=1618754414217, MediaProviderDataID=280558, MediaTitle=Against the Odds, SeriesInfoID=10513883, TagLine=, DiscNumber=0, UserRating=70, CollectionID=0, MediaProviderID=tvdb, TrailerUrl=}] \\workspace-1\tv-rec2\AgainsttheOdds-S01E03-TheHeroesofTarawa-44515060-0.ts, Seg0[Sun 4/18 9:00:00.009-Sun 4/18 10:00:00.003]]
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] VideoFrame.timeSelected2(Sun 4/18 9:00:15.664, true) currFile=MediaFile[id=45082255 A[44515060,44498353,"Against the Odds",78808@0418.09:00,60,T] mask=TV host=Workspace-1 encodedBy=DCT-Ceton InfiniTV Ethernet (00-80-8a-76) Tuner 3 on 192.168.45.60:9000 AHCHD format=MPEG2-TS 0:00:05 12959 kbps [#0 Video[H.264 29.97003 fps 1920x1080 16:9 progressive id=100]#1 Audio[AC3 48000 Hz 6 channels 384 kbps idx=1 id=101 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=102 eng]{ScrapedBy=Phoenix, IMDBID=, SeasonFinal=false, CollectionName=, MediaType=TV, EpisodeCount=0, CollectionOverview=, ScrapedDate=1618754414217, MediaProviderDataID=280558, MediaTitle=Against the Odds, SeriesInfoID=10513883, TagLine=, DiscNumber=0, UserRating=70, CollectionID=0, MediaProviderID=tvdb, TrailerUrl=}] \\workspace-1\tv-rec2\AgainsttheOdds-S01E03-TheHeroesofTarawa-44515060-0.ts, Seg0[Sun 4/18 9:00:00.009-Sun 4/18 10:00:00.003]] realDur=3597395
Sun 5/30 8:44:54.457 [VideoFrame-594d43554845@6ff4a1ea] seeking numpushbuffers=2730 seekTime=15644
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] MPEG2 seek targetPts=1410840 length=6717535532 durationMsec=3597395 parsedPTS=5175630 lastPos=89455861 firstPTS=2880 mux_rate=0 estimBitrate=1556430
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] Mpeg2Reader seeking to pos=24348632 time=0:00:15.644
Sun 5/30 8:44:54.458 [VideoFrame-594d43554845@6ff4a1ea] flushPush0()
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] VF processing job null nPlayin=true
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] isRec=false rd=3597395 base=15644 eos=false
Sun 5/30 8:44:54.459 [VideoFrame-594d43554845@6ff4a1ea] VF thread is now waiting for 0:59:41.501
Sun 5/30 8:44:54.459 [Pusher@56a7257f] Seek target=15 actual=13 diff=2
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Seeking again to try to get a better position...
Sun 5/30 8:44:54.460 [Pusher@56a7257f] MPEG2 seek targetPts=1410840 length=6717535532 durationMsec=3597395 parsedPTS=1189440 lastPos=24395641 firstPTS=2880 mux_rate=0 estimBitrate=1850397
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Mpeg2Reader seeking to pos=28009180 time=0:00:15.644
Sun 5/30 8:44:54.460 [Pusher@56a7257f] Seek target=15 actual=14 diff=0
Sun 5/30 8:44:54.463 [Pusher@56a7257f] Disabling I-Frame alignment in pusher since it's skipping too much pts=1798797 startWait=1348347
Sun 5/30 8:44:56.089 [EventRouter-594d43554845@1903758d] processUserEvent-UserEvent[ff] evtTime=Sun 5/30 7:53:34.752
Sun 5/30 8:44:56.089 [EventRouter-594d43554845@1903758d] VF.submitJob(VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null])
Sun 5/30 8:44:56.089 [VideoFrame-594d43554845@6ff4a1ea] VF processing job VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null] nPlayin=true
Sun 5/30 8:44:56.089 [VideoFrame-594d43554845@6ff4a1ea] VF processing on UI Thread VFJob[TimeAdjust r=0.0 t=10000 file=null ifn=null]

Hi,

Few suggestions/questions.

Did you try the stream fix in OpenDCT to clean up the streams. This can fix issues like that. You can also attempt to use IJKPlayer instead of ExoPlayer. I still recommed ExoPlayer, but if you are having issues IJKPlayer may help. If you are having the same issue on different devices that would make me think it is the source material.

Hope that helps.

Josh

[ojones]

Thanks Josh!

The video stream is h264 in a mpeg2 container. I've done a bit more testing and IF I switch to fixed transcoding playback works perfectly over LAN in the android client. Without transcoding the pusher errors out server-side on the android client (mixed behavior on placeshifter client). I think I have opendct cleaning the streams:

consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl
consumer.ffmpeg.fix_stream=true

then for each recording device:
sagetv.device.XXXXXXXXX.consumer=opendct.consumer.DynamicConsumerImpl

Is there any reason the seeking pusher would be more sensitive to bad streams with the android client than the full windows client? I plan to fiddle with: miniplayer/seek_diff_for_reseek in sage.properties when I get a shutdown window.

Thanks for all your work on this!

[stuckless]

Originally Posted by ojones

Thanks Josh!

The video stream is h264 in a mpeg2 container. I've done a bit more testing and IF I switch to fixed transcoding playback works perfectly over LAN in the android client. Without transcoding the pusher errors out server-side on the android client (mixed behavior on placeshifter client). I think I have opendct cleaning the streams:

consumer.dynamic.default=opendct.consumer.FFmpegTransSageTVConsumerImpl
consumer.ffmpeg.fix_stream=true

then for each recording device:
sagetv.device.XXXXXXXXX.consumer=opendct.consumer.DynamicConsumerImpl

Is there any reason the seeking pusher would be more sensitive to bad streams with the android client than the full windows client? I plan to fiddle with: miniplayer/seek_diff_for_reseek in sage.properties when I get a shutdown window.

Thanks for all your work on this!

If you are using ExoPlayer, then it will be problematic with 'bad streams'. The ExoPlayer team is a purist team that believes that a player should only play good streams, and if there are any bugs in a stream, then the source should fix that and not the player. Libraries like ffmpeg exist because the real world doesn't work that way, but, ExoPlayer doesn't use ffmpeg, so it can't easily fix streams (or account for bad data in a stream).

[ojones]

Stuckless - As usual you make a lot of sense! I had forgotten about the ExoPlayer grumpiness with bad files. I had assumed OpenDCT would clean that up but maybe its only cleaned up well enough to play not seek. I wonder if ExoPlayer will fully digest the streams provided by SageTVTranscoder once Josh figures out remuxing. Theoretically OpenDCT should already be doing this but I am clearly not an expert!

I will play around with IJKPlayer as well - appreciate everyone's help.

[jvl711]

Originally Posted by ojones

Stuckless - As usual you make a lot of sense! I had forgotten about the ExoPlayer grumpiness with bad files. I had assumed OpenDCT would clean that up but maybe its only cleaned up well enough to play not seek. I wonder if ExoPlayer will fully digest the streams provided by SageTVTranscoder once Josh figures out remuxing. Theoretically OpenDCT should already be doing this but I am clearly not an expert!

I will play around with IJKPlayer as well - appreciate everyone's help.

To add onto stuckless' comments, which I agree with 100%, there is another caveat here. Android miniclient is telling sage that it does not support .ts/.ps for pull, it tells sage that it supports it for push only. This than makes sage uses its own muxer to process the files instead of sending them raw to the Android client. I have played around with these settings to make it send the files raw "pull", and it does not seem to be able to play it.

In short: ExoPlayer seems to love MKV and is ok at .ps/.ts. So I think that if I get around to adding the remux setting to keep audio and video as is, but place in MKV container, Andriod Client will probably have very little issues with the content.

Josh

[stuckless]

Originally Posted by jvl711

To add onto stuckless' comments, which I agree with 100%, there is another caveat here. Android miniclient is telling sage that it does not support .ts/.ps for pull, it tells sage that it supports it for push only. This than makes sage uses its own muxer to process the files instead of sending them raw to the Android client. I have played around with these settings to make it send the files raw "pull", and it does not seem to be able to play it.

In short: ExoPlayer seems to love MKV and is ok at .ps/.ts. So I think that if I get around to adding the remux setting to keep audio and video as is, but place in MKV container, Andriod Client will probably have very little issues with the content.

Josh

Sage should be able to pull a .ts file (I think you can configure this push/pull stream in the config files of the client)... the problem is that ps/ts files are not seekable, so, if you do pull them, you can't seek them (ie, jump forward/back). This why sagetv created the PUSH streams so that the server could manage the seeking and send the new stream to the client. It's also why sagetv seeking is the fastest you'll see in any client.