UPDATE: Changed thread title to accurately capture the issue as it stands today (3/31/25)
This is strange. When watching Seattle 51.1 (CW) channel on my android devices they come in perfect (video and sound match perfectly). However, when I attempt to watch them on any of the four Firecube TVs in my house, the sound is fine, but the video hangs/pauses.
Why would there be a difference between the Tablo android app and the Tablo Firecube app. Is there a possible bug that might cause this?
Each app is a little different, so it is not unusual for it to work properly on one device and not another. In fact, that is a great way to determine if a problem is with a streaming device, or the Tablo itself.
I have no experience with the Fire Cube, but my first thought would be to clear the cache on the Fire Cube. Here is how to clear the cache on a variety of devices:
If that fails, I would reboot everything; the Tablo itself, your streaming device, and the router.
Let us know if this helps.
It probably has to do with how well each device can handle the raw mpeg2 video that Tablo streams to the apps.
I’m running on Fire TV Cube (2nd gen) with none of the problems you’re experiencing. Everything is wired — Tablo and all streamers — plus I’ve got a solid antenna signal. And as suggested by @KGBnut, I regularly clear the cache.
Ok, cleared the cache on the Tablo and performed all recommended reboots (Router, Tablo and Fire cube.
Video still pausing, audio is fine.
The tower for 51.1 (CW) channel is the same tower for 4.1 (KOMO/ABC), and that channel has no issues ever, so I find it hard to believe this is an antenna issue (but I am no expert here)
My setup:
Wired network (Tablo and all Fire Cubes), Ziply router, with bridge mode enabled, to TP-Link Deco XE75 (QTY 3, Ethernet Backhaul)
Tablo 4th Gen/4 Tuner (FW: 2.2.54-2433716)
Tablo Firecube app (v1.6)
Antenna - ClearStream 2MAX / currently indoor (rarely have any signal issues, except when windy due to trees)
I am stumped on what the issue may be, so just putting it out there in hopes I can pick up a few more local channels I can watch and share my experience to help improve the product.
P.s. I can view the channels perfectly on my android phone and Samsung Galaxy Tab A9, so this really feels like a Fire cube app specific issue
This seems interesting. MPEG2 vs MPEG4 Channels?
Ps. I have no idea what those differences are but what they describe certainly seems to reflect my experience here in Seattle.
Have you had this trouble since you set up the Tablo, or did it previously work okay, and this is a new problem. Just curious.
One other thing you could try… Delete the Tablo app from your Fire Cube, and then reinstall it.
A quick check on Wikipedia for KOMO-TV does not show 51.1 as MPEG4. It’s just tagged as being broadcast on behalf of another station.It is 1080i, vs 720p for the main KOMO (ABC.)
Existed as long as I have owned the Tablo. I noticed it from the beginning, but assumed it was a reception issue, and I would deal with it later after I upgrade my Antenna. Now, I am still seeing it months after the Antenna upgrade, so thought I would investigate and ask questions
Thanks for the additional information.
Still cannot figure out why the video pauses/hangs (sound is fine) on KUNS-TV 51.1 (24), but KOMO-TV 4.1 (30) works perfectly in Seattle even though they both use the same tower (same ownership). RabbitEars does indicate that KUNS-TV is running ATSC 3.0, but so does KONG 16.1 (31) which also comes in perfectly and has no issues (both 1080p). I can replicate this video pause/hang on all of the Firecubes in my house and have yet to be able to replicate this on my android tablet or phone (both stream perfectly), which still leads me to believe this is a platform application specific problem.
KUNS-TV - RabbitEars.Info
KOMO-TV - RabbitEars.Info
KONG - RabbitEars.Info
If you have any thoughts/suggestions I would love to hear them. Details on my wired network/config are in the thread (except no more Ziply router 
), but currently this is my only headache I cannot seem to solve, which seems to point at an app issue based on my testing.
Interesting. Just remembered I also have a Firestick 4K. It works perfectly on that too!?!?
Ok, so now I am really confused!
Same manufacturer, different hardware
Same platform application
Wired (Firecube), WiFi (Firestick 4k)
Could it be wired vs WiFi, hardware, or platform settings?
Update: just tested Wired vs WiFi on the Firecube, still see the video pause/hang.
Now down to hardware or platform settings. Any ideas here?
Update #2: messed with all the display settings (in Display & Sounds: Video Resolution, frame rate, HDR) on the Firecube (changed one at a time and cleared cache each time). No luck. Looked at the Samsung TV settings, but nothing interesting to change there at all.
Still perplexed why this one channel is having issues just on Firecube only.
Here is a swag if it’s a gen 1 cube. The gen 1 fire tv cube used the amlogic S905Z which didn’t have mpeg 2 hardware support. It was software decode.
This kinda sounds like what I am currently seeing, but not seeing any comments or resolution
Ok, I came to the conclusion that the issue was related to the Firecube 2nd Gen since the issue only existed with that streaming device and the Tablo app.
Also, I have wanted to move away from Amazon products, so I bought a Roku Ultra to replace our primary Firecube, to test if the issue went away and, if we liked Roku interface. Very impressed!
The big win is that channel 51.1 (CW) in Seattle is now working perfectly, with no video pauses. We can now watch the Seattle Storm’s entire season. Woot!
Looks like Roku is in our future.
