Well, welcome to the club! 
Thanks, I might have to take that up with Roku 
philsoft, now yours is crashing and mine stopped with the latest firmware update of 6.2 3672 on a 4200x (even when I re-installed the Preview app. back again).
How weird is that?
I am curious if you have a 4200 or 4200X?
Could the new firmware fix the problem in the 4200x units and cause it on the 4200 units?
How else could this strange behavior change be explained I wonder.
Thanks
Okay, So I noticed the ROKU firmware update also (it must have come along with the AC/DC promo theme update).
And I decided to reload the Preview Channel on my 4200X to see if the F/F bug returns (since I only had it bad when both apps were installed) and to my surprise it no longer crashes.
So itâs been about 5 days now of constant F/Fâing thru commercials using both methods and not one single reboot yet!
That made me happy (figuring ROKU found the issue and corrected it) and I came here to share the good news only to see that with the firmware update now people who never had the issue suddenly had it, unbelievable.
As I asked philsoft in my previous post, maybe it has something to do with different hardware between the 4200 and 4200x models? They seem to use the same firmware versions in these two but maybe they need different firmware? (like other models get).
Just trying to be helpful by updating you guys with my observations.
Thanks everyone and have a great Labor day weekend.
~Doni
PS My Tablo hasnât updated yet to new firmware, just my ROKU has, if that makes a difference in this puzzle.
No sorry, mine is a 4200X
There is no hardware difference between these - the X simply designates it was sold via an online store and R models where sold through brick and mortar (Best Buy, etc.)
That may not be true for all roku models. I have a 4200x (roku 3) and a 4210r roku 2. Both sold on amazon by amazon and shipped by amazon.
Is the model suffix R or X on the actual unit or just the boxâŚThere are reports that even though the box may say R for an Amazon unit, the label on the actual Roku is X.
And regardless, the 4200X and 4200R are exactly the same inside and out, other than the X or R suffix.
Update 9/6 - Roku 3 4200x got Build 3672 and Roku 1s 2710x got Build 3678 sometime in the last couple of days. I just tried to duplicate the reboot scenario without success and so far no rebooting/freezing on either 1 or 3 using classic Tablo app. Crossing fingers.
1 Like
Build 3672 on my 5 Roku 3âs is pretty awful, rebooting several times per hour on typical commercial skipping with fast forwards. Unquestionally worse than prior builds in terms of crashing with FF.
New Tablo firmware now taking much longer to remotely connect, nearly 2 minutes tonight versus approx 20 seconds average in prior release.
1 step forward in some yet to be appreciated added features and 2 steps backward AFAIAC.
One user pleading to please fix whatâs broken or way too slow before tackling the âwish listââŚ
This exact problem happens with the Showtimes Roku channel while fast forwarding and skipping ahead constantly. So itâs definitely not a Tablo-only problem.
2 Likes
Since updating to Tablo 2.2.2, Roku 3 4230R has been absolutely stellar! I canât get it to reboot (so far) after many attempts of recreating the issue (simply FF a few times and then hit play).
However Roku 3 4200X is rebooting as usual, multiple times with typical frequency.
Maybe there is a difference (with respect to tablo) between these two models.
Both running Roku software âversion 6.2 build 3672â (over same wifi network, through the same router, to the same tablo as detailed in my previous post).
Edit: For me, this is only happening when using Roku with Tablo (not with Netflix or Amazon Instant Video)
1 Like
My curiousity and frustration brought me tonight to the local Walmart where I purchased a Roku 3 Model 4230X, the newest model with voice search. Although I already have 6 active Roku 3 4200âs and a spare 4200, I was anxious to see if my rebooting would disappear on this new unit.
With disappointment I report that it certainly crashes less often, but still rebooted within literally 3 minutes of deliberate fast forwards, rewinds, and plays.
It is going back to Walmart tomorrow.
Firmware updated to Build 3672 as soon as it got a network connection.
Larry
I have read most of these and they are all very similar to what I have been dealing with since the day I got all my cord cutting hardware working together this last spring. Roku3, tablo 4 tuner w/2tb HDD. If we watch any show live or recorded and pause or ff then push play the app locks up, the roku locks up and shortly after it reboots. I hoped the preview would fix it and it didnât. I hoped the roku update would fix it, it didnât and then this last update I was hopeful that it would at least get better and it hasnât. I would be willing to do any debugging necessary to help resolve this issue. It happens at least once but usually 4 to 5 times during an hour long show. I have a roku stick too but I donât use that regularly, that is just for use in a bedroom. Please help! Thanks.
2 Likes
Yes, sadly I have to retract my post from 2 days ago.
Though, in my experience, the Roku 3 4230R (newest model with voice search) crashes less often than the Roku 3 4200X, it still crashes more than it should.
I just canât find a rhyme or reason (or pattern) ⌠just FF a few times during a recorded show (especially if you do it fast) and ⌠crash/wait for Roku reboot.
I have just never seen this on iPad or FireTV box with Tablo (or in other content served from other sources on the Rokuâs).
1 Like
I have posted an observation here several times which nobody has confirmed yet I sense the distinct possibility I am not alone, namely:
My crashes seem to be related to a highly variable delay time between pushing remote control buttons and receiving responses from Tablo / Roku.
Sometimes, the responses to button pushes are instantaneous. Other times, they may lag by a seond, possibly longer.
My crashes seem way more frequent when the delay is longer, and seldom happen when the delays are very short.
There are stretches of hours where crashes occur occasionally and there are other times when crashes occur 3-5 times per hour. The lag is noticeably longer when the crash frequency increases.
I have no explanation for why delays are so variable. My prior PVR and 6 set-top boxes had nearly instant responses regardless of network load, time of day, etc. The Tablo and Rokus seem extremely unpredictable in terms of delay / latency / lag. My LAN network traffic is extremely low otherwise.
I raise this comment for only 1 reason, not to bash Tablo or Roku, but merely to see if some WAN, LAN, or other factor such as devices âcalling homeâ may account for why these crashes seem to occur in an inconsistent pattern related to delay time. I can crudely predict if crashes will be occuring often by operating the remote a few times to see if the replies are instant or delayed.
I have an occasional evening where the crashes nearly disappear and most other nights where they occur frequently. Am I the only one seeing this specific behavior? Do we know for sure that Roku and / or Tablo servers do not participate in any fast forward and rewind key replies?
Thanks for any inputs,
Larry
@RetiredEngineer, your hypothesis may have some weight:
I can sometimes anticipate the crash, or even mitigate it, if I allow the Tablo to âcatch upâ to the button clicks, i.e. FF a few times, wait a few seconds before pressing play again. (Though, in fairness, sometimes you click slowly just once and it does it).
It does seem to happen to me more frequently when I am watching recorded material and the Tablo is recording at least one other program at the same time.
I have also experienced the crashes on a friendâs setup who has a wired Roku on a gigabit network with, of course, their own Tablo, etc.
Thanks @Tablotester!
Slow button pushes seem to help a little bit here also, but not enough to prevent unexpected crashes in most cases. Variability in delay time is the biggest mystery to me, and perhaps Tablo recordings in the background may account for some or all of this variability.
Experiments I have done make it pretty clear that the initial set up which occurs when the Roku is used to select the Tablo channel definitely requires an Internet connection. If the Internet connection is lacking, Roku does not/cannot discover the Tablo box. Once the Tablo box has been found and the Tablo database has been retrieved by Roku, it is my impression that the Internet connection is no longer needed. Therefore, individual fast forward and rewind and play commands from the remote control through the Roku to the Tablo can all occur with no âcalling homeâ or other Internet intervention. I have therefore dismissed the possibility that the WAN is contributing to the variability in latency / rebooting problem, and feel pretty confident that it is local.
I have just been curious about whether other users experience the variability I have described, and I have yet to convince myself that there is a cause and effect relationship with reboots. No doubt, there is a strong coincidence I witness of reboots occurring with the slower, delayed high latency periods of time, but not necessarily a cause-and-effect relationship to rebooting.
Thanks very much for your insights and your reply.
Since updating to Tablo 2.2.2, Roku 3 4200x with Build 3672 and removing the Tablo preview channel and reinstalling on my Roku. I have not had any issues after 6 days. I too have had the same issues as everyone here is describing. This is the longest period I have gone without issues. FYI I have all of mine Ethernet wired, not that seems to make much difference with the issues everyone is having.
1 Like
I have two Rokus with tablos and have the same rebooting issue. Glad to see a number of people not giving up on complaining about this issue. Tablo needs to own this issue and make reliability the top priority (glad to see the CEO is onboard). This type of race condition issue is difficult to isolate but generally if the issue can be reproduced reliably, it can be resolved.
My email to Tablo:
I have frequent reboots of the Roku 3 when using the Tablo channel. The reboots always occur when attempting to fast forward (skip over commercials, etc). The reboot frequency is often enough such that I could reproduce the problem with a fair amount of ease. This reboot issue has occurred since purchasing the Tablo unit. I assume this is a known problem. Do you have plans to fix this issue?
Tablo response:
Iâm sorry to hear that youâve been having some issues with the Tablo Roku channel. Unfortunately, weâve narrowed this down to the changes in the most recent Roku firmware update.
The latest Roku firmware appears to be crashing and causing reboots on many other channels including Netflix, SlingTV and Hulu. Weâre hopeful that Roku will correct this soon.
My thoughts:
This is not the response I was hoping for. Tablo needs to own this reboot issue since Roku works fine on other channels. If the problem turns out to be with Roku firmware, then they need to work with Roku to resolve the issue. We should not expect Roku to give high priority to an issue that is mostly a problem for the Tablo device.