Android Xibo Client Local Video Freezes After 60 Seconds

Get Help
1

Android Xibo client RTSP “Local Video” freezes after 60 seconds on a new Android 8.1 unit.
I’m able to interact with the client app so the whole client app in not frozen.
It’s just the feed that freezes on a single frame after 60 seconds.
After noticing the default duration is 60 second if non is specified I suspected the duration is not being honored.
So I did the following with the same frozen result for all but one.

  • Created fresh Layout, set media Local Video RTSP url
  • Set Media duration to 3600 with and without a region loop for the Layout.
  • Set Layout region to not loop with no region media duration.
  • Set Layout region to loop with no region media duration.
    This caused the stream to refresh itself after 60 seconds noticeably interrupting the video

Tested this issue against Xibo client R108 and R103.
Have to say my other Android devices with R108 do not have this issue.
However they are running earlier versions of Android.

Included the exported Layout XML below for review, maybe I’m missing something. :slight_smile:

   <?xml version="1.0"?>
   <layout width="1280" height="720" bgcolor="#000" schemaVersion="3">
   <region id="108" width="1280.0000" height="720.0000" top="0.0000" left="0.0000">
   <options>
   <loop>1</loop>
   <transitionDirection>N</transitionDirection><transitionDuration/><transitionType/>
   </options>
   <media id="157" type="localvideo" render="native" duration="3600" useDuration="1">
   <options>
   <mute>0</mute>
   <scaleType>stretch</scaleType>
   <uri>rtsp%3A%2F%2F10.94.1.18%3A8554%2F</uri>
   </options>
   <raw/></media></region><tags/>
   </layout>
2

Thanks for your report.

We’ve not done any testing on Android 8.1 yet. We’ve been recently working on fixing some issues we’ve seen with Android 7 which may have some impact.

The best thing to do would be to log a case with our service desk, giving full details of the device you’re using.

Likely we’ll need output from logcat which may be something you’re unfamiliar with, but it will involve making some changes to the device and connecting it up to an Android SDK temporarily to get log messages from Android itself.

If it’s something we’re able to work around we will try to do so, however, our experience is that often these things are faults in the device firmware rather than in our code and that means it’s not possible for us to rectify them. We have a list of recommended and tested hardware for that reason so you can purchase devices we know will work well.