Can you please be a little more specific, like what happens when it crashes, what are the version numbers of the involved software, like just a description of what you’re seeing? If you want a solution to a problem, you have to describe what’s going on a little…
1 Like
tablo uses the roku video player. And if you blow up the video play the tablo app will exit. If you use a roku and release 12.5.5 and you get the spinning wheel of the video player and the words loading, if you hit the return button the video player exits the app.
One of my local stations moved RF’s and the engineers have been playing with the signal. When the S//N fluctuates it blows the video player and the app exits. It also blows the hdhomerun app.
I’ve given this release information to support a couple of times already.
Roku - model 3810x software version 12.5.0 build 4178-50
Tablo - firmware version 2.2.48
You start live TV and for varying periods of time the app crashes and goes back to the Roku home screen.
How about updates on getting live TV fixed @TabloSupport ?
Live TV, both over the air or from the online channels on the app crashes after a few minutes and goes back to the Roku home screen. Looks like a software issue to me. Update coming or do I send it back???
@TabloSupport - This support forum has many people posting the same app crash info. Can you provide weekly updates on your progress, here in the forum? It would be nice to know if you are making progress.
I can offer my services as a Beta tester, if needed. I have been an Server Admin (IT guy) for over 40 years, with a background in application and server diagnostics experience. I want you to be successful for all of us. 
3 Likes
Sorry, when I read your posting I was thinking about Tablo having to reproduce the problem to see and fix it. I didn’t know that you had reported the details elsewhere previously. I haven’t seen this problem, my Tablo has worked well with Roku (and Chromecast 4K and Fire Stick 4K MAX). Actually, better than the Legacy Tablo that I’ve used for several years, that was getting a little flaky lately.
Thanks for reporting this and giving the details about how you encounter it, that’s how it’ll get fixed.
@MrDoh, are you a customer or TabloSupport?
Customer who spent a career in software :-).
2 Likes
Same here, @MrDoh
Until the Tablo software team corrects the “shutdown to Roku Homepage” problem on the Roku Tablo App, others Users have suggested the following work around - just delay the Live TV feed for about 30 seconds. I have been doing that for a few days now and has worked so far - no more crashes!
Thank you for that tip. I’ll try to use that for the time being @gatorgogo
Me too!
Yup we all got suckered in buying this crap!!!
Unfortunately, I had 2 “shutdown to Roku homepage” events tonight even though I was using the “delay the Live TV feed for 30 seconds trick”. But even though this work around is not perfect, I still think it reduces the frequency of these crashes so should help until the Tablo software team figures this out.
How much time went by when the crash occurred? I have a theory that whatever clock it is using to push out the video is outrunning the buffer. I noticed this a couple of time when I went back 30 seconds. After an hour or two if I paused the program the time didn’t show I that I could fast forward 30 seconds.
1 Like
One crash froze the Video and it took about 20 seconds to return to the Roku Homepage. The second crash was just an immediate return to the Roku homepage. I’m not sure this info helps or not. Do you think trying a delay longer than 30 seconds would help at all?
I need to clarify the question. The channel was selected by you. Then the 30 second technique was used. How long were you able to view the channel until the app crashed? It could be a 30 second rewind won’t cause a crash until 2 hours later. Maybe a 60 second rewind may take 4 hours until the app crashes. I still think whatever clocking is being used is outrunning the buffer.
Hardware and software
This morning Sunday, I read multiple replies from people having issues last night. I also had similar outages/crashes during the playoff football game of the 49ers and Packers. The thought I had was maybe the Tablo servers are overrun by the volume of users at the same time on the same channels. But without input from @TabloSupport, we are all guessing.
I don’t know exactly the time from setting the 30 second delay to the time of the first crash - I would guess 2 hours? The second crash happened within about 1/2 hour after restarting the Tablo App and setting the 30 second delay. I also had a 3rd crash too - that was about 1 hour later.
The crashes happened during the Packer/49ers game (interesting that Buzz56 also had crashes on the same game - coincidence?)