These sound like issues that occasionally occurred on android devices when users would press HOME instead of backing out of the app to properly close the app’s connection to the Tablo server (puck). Pressing BACK until you confirm that you would like to indeed exit the app has never caused me any problems unless their servers were down.
But I cannot speak for the on-the-hour issues I used to experience. I don’t use my Tablos as often as I used to and have not run across this problem in months – perhaps I’m using the devices at different times.
And KimchiGUN, as far as a class action on a $99 unit being worthwhile, why should the law allow a company to sell and profit on a product that is truly faulty and wasn’t fully tested, using us all as said beta testers, when their deceptive advertising make it sound like it works (PERFECTLY) straight out of the box! Sounds like a textbook case of FRAUD to me! A year later and it still doesn’t work as advertised! P.S. If you think my network is at fault, and that I don’t have the ability to correct problems on a simple home network, then you go ahead and tell me what I’m doing wrong. Sorry dude, if you think that you know more than most everyone else in the community, what are yo still doing here? Just saying!
My experience is the same as yours (with an LG tv) and my reaction is also the same. Not perfect, but for the money I paid, $79, and for the money I don’t have to pay for the guide it is a worthwhile purchase that has gotten better over the year of ownership.
I see “random” issues with spinning circles, delayed/lengthy startup, delayed/lengthy access to various app functions, etc. at least a few times a week. Recording OTA stuff is great when it works, sucks the few odd times it doesn’t. That could be said about my entire Tablo user experience. Pick any part of it. But … my wife and I use the thing every day. Maybe we are hard-headed, or at least cheap.
It continues to frustrate me that I can’t seem to get a reliable/stable user experience 99+% of the time. I have great fiber internet and all hard-wired in house Cat6 ethernet. No wifi involved in any part of my TV world. I have a high-end rooftop antenna, digital RF processing, and solid in-house coax distribution. Both my RF meter, as well as my 4 direct coax connected TV tuners, tell me the RF side of my system is solid. The way I see it after nearly a year if fooling with the Tablo ecosystem … it’s the Tablo hardware and software that continues to struggle with performance and reliability.
Your point about “properly” exiting the Tablo app (at least for the Android variants) is spot on. I get issues every time I forget and just hit “Home” or even turn off the TV directly before exiting the Tablo app. My wife and I both know to restart FireTV or either of our 2 Sony Google TVs if there is even any doubt that the Tablo app wasn’t exited “properly”. Even if we are sure it was, restarting the Android ecosystem fixes a large number of “random” Tablo issues.
I also end up restarting the Tablo itself (pull the power) in some rare instances where nothing else seems to work. Again, this can fix some stubborn issues.
I’m sure most users, myself included, hate having to do these steps as part of “routine operations”, but often they straighten out otherwise unexplained Tablo behaviors. I encourage any Tablo users having otherwise unexplainable issues to make these steps part of their routine “troubleshooting”.
Why this can’t be straightened out more in FW or app updates is a mystery to me, but at least I can keep the silly thing working for a much lower cost than cable/satellite/streaming. It is a cheap OTA solution, but it can also be a PITA.
@ classicrockguy “Why this can’t be straightened out more in FW or app updates is a mystery to me, but at least I can keep the silly thing working for a much lower cost than cable/satellite/streaming. It is a cheap OTA solution, but it can also be a PITA.”
+1. Sums up my feelings too. I love it for the simplicity when it’s working. The inconsistency of reliable performance bugs me. OK this morning, bowed up this afternoon. If it is not working right, I leave it be and come back later. Got a snootfull of the power cycle reboot everything and hope for the best.For the price I don’t expect aircheck reliability, however it could be better than what it is. Sometimes have to wonder what they are thinking: the mass market routine average non-techy customer will be totally frustrated by the hiccups. Not an effective way to get good word of mouth or repeat sales.
I’ve had my Tablo 4th gen since Sept 2023. I know I mentioned this before on another thread that I am 99.99% sure I have never manually restarted the thing. I know for sure I’ve never pushed the reset button and cannot remember ever doing a power cycle with it. The only time it gets restarted is for updates or the very rare occasion we have a power failure that that I think will last longer than the UPS can keep it and other devices running. I have a NAS that’s been plugged in (on a different UPS) and running nonstop since 2017. Has never giving me any problems. Again the only time it gets restarted is for updates or a couple of times when I had to do some maintenance on it. On the other hand when I was using Roku Ultras I had to power cycle them usually once a month or every other. They would just become unresponsive at times. And it wasn’t always while using Tablo.
I have no proof but I’ve always thought the constant shut down and restart of electronics causes premature damage to components that will shorten its life and cause instability earlier in its life.
Yeaaa… there’s quite a few people here. I mean a lot of people here. That are way smarter than me! Here’s the thing, their Tablo’s work for the most part.
Not saying my Tablo is perfect. But I sure did spend a solid 3 months getting it right. Once I got it right… it worked!
Not saying Tablo is perfect. But it’s usable. Stop being dramatic… sign up for cable and be done with it!
My Tablo rarely gets rebooted manually. However, since day one I have experienced issues with fw updates (signal or recording splits) and the only way to fix them was another reboot of the puck. I did not test this theory on these last two updates (2.2.53 beta or the public 2.2.54), but every fw version before this has given me immediate issues. Both pucks are working fine and perhaps my extra reboot was unnecessary this time… but I don’t trust their fw update single reboots anymore.
I agree with all the comments, both positive and contrary. It’s ‘working’ for my wife, which is the important thing. She just told me that the thing she dislikes most is that sometimes pressing buttons within the TabloTV app gives the Roku ‘donk’ sound and the command doesn’t complete. She has to wait for a minute, go back if it doesn’t complete, then try again. It’s more of an unnecessary annoyance that the Legacy Tablo didn’t have.
However, the negative comments have some validity. My beef is that all the problem bugs and idiosyncrasies should be documented or worked out of the product. How would anyone know that it’s imperative to appropriately exit the app for best performance? I only do this because I’m 60+ yo and that’s just the way I do things. Most won’t know to do it.
I don’t see any way to view all recordings. Under the Library tab, “All” now shows all recordings that are set up (which is good), and “Recent” shows sone but not all recordings. You can scroll through “All” and find your recordings but that’s not a good way to find them. There needs to be an “All Recordings” button.
I’m getting jealous of all those that this firmware resolved. Kinda bummed that i can’t go back to my previous firmware.
After update to 2.2.54, neither of my 2 Samsung TV are able to use the in-TV app to connect to my Tablo. The screen just says “Connecting to Tablo” with the spinning wheel. Connection is never made.
I am able to connect both of My Roku to my Tablo. My iPhone also. Unfortunately I am getting too familiar with the Roku green screen work around than I would like.
Here hoping this is resolved in next firmware update.
UPDATE: Per the link from wysiwyggin, clearing the cache on my Samsung TV resolved the issue listed above. YAH !!!
I’m sorry to hear that you’re having an issue. Have you tried deleting and reinstalling the app on your two Samsung TVs? Can you reboot the TVs? If so, try an uninstall, reboot, then reinstall. You could always try rebooting your Tablo itself (press the small bottom button once, don’t hold it) or rebooting your wireless router…
At least you’re still able to watch the Tablo on your other devices.
Updated 2.2.54 and have an issue where the app crashes on AppleTV when selecting Library>Coming Soon. Reinstalled app, reboot Tablo/Apple TV, updated Apple TV, etc. Any ideas?
Tablo firmware release 2.2.54 does not seem to work with my Roku operating on firmware update 14.1.4 even when I go to settings>troubleshooting>audio compatibility mode and change to on, or off no difference. The sound does not work on older recorded shows from over the air TV. Is Tablo continuing to work on a solution or do I need to continue to use my firestick HD or continue to make sure one of my older Roku’s never updates beyond its current 13.0.0?
Roku’s update their OS whenever they want.
You can manually trigger an available update, if one is available, but you can’t stop it from updating when it decides the time is right.
However, older Rokus stop receiving OS updates eventually.
I’ve got a Roku Ultra that is still on OS v12 I believe.
