I have a Roku TV and have the Fox News channel installed. The issue is Fox News Live stream is delayed by 1 hour (for example...when it’s 10am EST the live stream is showing the stream from exactly 1 hour prior). I confirmed that the TV is set to the right time zone and is displaying the correct time in the home screen. I have compared this to the Fox News app on FireTV and iOS devices and the live stream on both do not have this problem, seems to be only on the Roku platform.. Is there any fix for this?
I have a lag problem on my model #43S405, but not on my model #32S305, when each TV is streaming the same show. Both TV’s have an “excellent” wireless connection. Thus, the problem appears to be on my end, rather than the channel provider’s end. Anything I can do to to reduce or eliminate the 20 second lag on the 43” tv?
I actually was able to find the problem and resolve it and hadn't seen the issue come back since. What I found was actually on my end. In my network environment I have pi-hole (network ad-blocking) setup, and what was happening was that when I launched the Fox News app I had noticed that it was playing content from exactly 1 hour prior. As a test what I did was disable pi-hole and launched the Fox News app and it worked perfectly. So in digging deeper into it I watched the logs live in pi-hole and when launching the app and then added to the whitelist. What I also noticed was that the ads on the Roku home screen on the right side were blocked (before I had made the changes) Once I had disabled pi-hole (and ultimately added the ads platforms to the whitelist) all in the world was happy. Off the top of my head I don't recall 100% which advertising platform it was, but maybe someone from Roku support can chime in here and advise which platform(s) they use.
I can tell you that this issue was definitely specific to the Roku platform as I currently also have FireTV with the Fox News app and had no issues at all before I had found the issue.
@RokuTannerD Not really sure why this issue was marked a solved when the issue was never really fixed, not an issue with the developer, and is certainly specific to the Roku platform even though it was environmental.