Issues After Updating to 2.2.6

Yes that way of factory resetting has worked for some.

No harm in trying it now.

Interesting. Thanks for sharing. Though I think 2.2.6 is better than 2.2.2. I have no problems except for an occasional Loading message on my Roku, but I get that on WatchESPN and Amazon Prime as well.

I just wish I could use 2.2.6. Itā€™s going on a week that my Tablo is sitting, just generating heat, and unable to connect to it. I could do a factory reset, and get it working again, but I hoped their engineers would be able to figure something out by looking at why itā€™s not working.

Iā€™m a software developer, and handle putting out new releases as one of my duties. If any release I put out causes this serious an issue, where it renders several users stuck unable to use their hardware, this would be number one, critical high priority to back out the changes and put out a stable fix for everyone to keep this from happening from anyone. It wouldnā€™t take weeks, we would get something done in hours - at least revert back to the previous release until we figured out what was wrong.

I went with Tablo because like another user said, I like the design and backbone of their DVR. The system was slow at first, and had playback issues towards the start of the year. I couldnā€™t even watch live TV because it would get so far behind. They fixed that, and it was stable for a while, and my hope was they would make the FF, playback faster, and maybe very fast 2 channel flipping with near instant playback. In a year, it hasnā€™t happened, and it seems to be taking steps backwards. Especially since my player is dead right now waiting on a firmware fix, or until I factory reset and lose my recordings.

Iā€™ve upgrraded to Roku 4, in hopes it would be fast enough to stop the LPW error. It didnā€™t. I still believe it is a synch/frame fetch issue, and not performance related. Sometimes I FF to a frame, and it wonā€™t play at all, but if I go back 1 frame, that frame is present and plays instantly. As if they FF to the previous frame, and never actually get to the frame I played because they keep refetching the previous ones.

Anyways, hoping they get this resolved soon, really would like near instant playbacks, fast grid guide with a week of data, flipping channels, and maybe picture in picture (it is a 4 tuner box) with instant flip between channels. Itā€™s been long enough, this technology is in every DVR system out there for the past 10 years.

Iā€™m right there with you on that issue. I thought the improved hardware might compensate for inefficient coding - but there is something more fundamentally wrong going on. If anything, Roku 4 is working more poorly than Roku 3 in my system!
A couple months back, we had near instantaneous resume from FFW and quick loading of the Guide and Recordings page - now it takes nearly 30 seconds on the Preview app to load recordings on a clean, newly re-formatted drive - and minutes to do the same on the officially supported Roku app - its a complete joke.

I tried the factory reset mentioned a few posts ago, and it seems to have improved things considerably. I was loathe to try it for fear that Iā€™d lose even the limited functionality that I had, but finally I got tired of watching football on my laptop and took the plunge. Now both Roku apps seem to be working, for the most partā€¦though they still dump me back to the Roku home screen periodically. So itā€™s not completely stable, but much improved after the factory reset.

1 Like

Does that mean your Tablo is now running 2.2.2?

No, itā€™s running 2.2.6. The factory reset did not restore the earlier firmware version. I forgot to mention that I still canā€™t access my recordings, it still says ā€œNo Recordingsā€ in both Roku apps (the recordings are viewable on my Windows laptop). But Live TV seems to be working OK after the reset.

xxxx cccc xx cc

I know, itā€™s weird. I followed the factory reset procedure, saw the fast blinking light, etc. I had to go through the whole setup process again, do the channel scan, etc. But the recordings are still there, and viewable, when I access the Tablo from my laptop.

I didnā€™t do any reset at all, but I did have to unplug the power and plug it back in a couple days ago. Donā€™t believe this would have caused it, but sometime after this I opened my browser to tablo and it said I needed to update to 2.2.6. Having already done this shortly after this release came out, it was a little perplexing that it wanted to do it again. Tried a few things first, but ROKU would not work, told me to update in fact. Could not read my recordings, just keep trying to. So I went back to the browser to tablo and let it do the update. After that, everything was working really good. Really strange.

Hereā€™s my post on this for anyone interested.

-Rodger

xxxx cccc xx cc

I CAN play them. On the laptop, they work completely normally. But the Roku apps say No Recordings. Iā€™m not inclined to format the HDD for fear of screwing something else up. My main priority was to get live TV up and running in order to watch sports, and now that thatā€™s working, Iā€™m not changing anything else. Iā€™m also not making any sudden movements, am being careful about my tone of voice, and am doing an ancient aboriginal Tablo Blessing Dance from time to time. :wink:

I do need the recordings to work properly as well, but I have a support ticket open and I guess Iā€™ll wait on guidance from support for what to do next.

2 Likes

I have dissimilar and disagreeing lists of recordings between my Rokus and my iOS devices, with many playable recordings on iOS totally missing from Rokus. In addition, selecting different views on Roku shows fewer or more recordings, with sorting by Most Recent view truncating the lis to the fewestt, thereby missing the most. None of the Roku views show all of the sctual recirdings which iOS shows and plays.

This has been a problem since I git the Tablo a year ago, and I posted about it once or twice a while back.

So much of what people are saying here sounds like CPU/GPU overload and perhaps memory leaks. It is so easy to build in memory leaks because of faulted logic in design and CPU/GPU cycles can go crazy over endless looping through bad code. Tablo needs to find someone that is an expert in software analysis. Until they do, it will be hit and miss Iā€™m afraid.

-Rodger

I know that I have seen this reported elsewhere, but I wanted to add my experience. I have a dual tuner Tablo, hardwired to network, and two Fire TV boxes one of which is hardwired and the other on WiFi.

  1. I get the occasional playback error on both of my AFTV systems; I canā€™t exclusively blame Tablo for this as I am way out in the boonies and subject to reception issues. I donā€™t think it is reception though, since I have an amplified DB-8 that picks up a station 120 miles away.

  2. After watching or deleting a recording, I revert to a blank screen. There are no recordings listed, only a small triangle with the number of unwatched shows remaining for the show I just watched or deleted. Navigating back to the menu (where you can select live TV or recordings) and then back to recordings will repopulate the display.

Hey everyoneā€¦

I can appreciate the frustration but name calling and ranting wonā€™t get anyone any closer to a solution on any issue.

Letā€™s keep the tone civil and helpful.

Iā€™m not anyoneā€™s mother so I have no interest or desire to put anyone in time out. I also have no interest or desire to act as a referee between grown people slinging insults.

Please review the rules here: Welcome Everyone!

Please follow them.

3 Likes

I cracked up reading ā€œnot making any sudden movements.ā€
Brings me back to when I was a UNIX admin, and was careful not to give the system console a stern look for fear it would trigger a kernel panic. LOL
Thanks for that.

2 Likes

I also was having strange issues after the firmware update.
There were duplicate programs and recordings even when ā€œDo Not Record Duplicatesā€ was selected.
Trying to find a solution I inadvertantly did a FACTORY RESET!!! OUCH! However this might have been a blessing in disguise as it now seems that things are working as expected.

This points to something that has been mentioned regarding a corruption in the database after the firmware upgrade. It looks like I am still on the 2.2.6 version and things are looking alright up to this point.

Best,
Simeon

1 Like

Using Chrome Browser.
Since firmware update recordings longer that 2 and 1/2 hours get stuck in loop and never finish.
I do not use Roku. For me the only solution is using the browser. Now that is broken.
Also had to reboot device 2 times since update. Drive has plenty of room which was an issue with older versions.

We are aware of this issue and are working on it. Sorry to hear youā€™re experiencing this :pensive: