Green flashing when playing from phone

I have to agree with the Samsung rep there. Yes, the Tablo app broke after the update from Samsung, and it was the Samsung update since it is common to all carriers.
However, the Tablo app seems to be the only one affected, this usually means that they coded their app leveraging some bug on the OS or a library (by accident or by design), and the bug was corrected with the update. Or they were using some bit if code (again from the OS or library) that was deprecated and subsequently altered or removed by the update.

One way or another I think it is Tabloā€™s responsibility to identify the problem, find the root cause within the code and fix itā€¦ or, if truly it is a problem affecting their app due to a bug introduced by a manufacturer update, then Tablo is still the one responsible for reaching out to that manufacturer and work with them to correct the problem or, if the manufacturer ignores them (since they have such a small customer base compared to, say, Netflix), then find a software work around that addresses the problem.

I know you donā€™t care who fixes the problem. But think about it: can Samsung, admittedly as huge as they are, troubleshoot every problem that arises with every app that runs on their phones. Especially in such an open ecosystem as Android. If you want more manufacturer control over the apps that run on their phones then you need an iPhone (I hate myself for saying that).

David says they are concentrating on the Tablo firmware update and they will post when they have something

@TabloSupport, @TabloTV: any update on this? Would be great to hear from you instead of all this deafening silence.
This is still most definitely a problem.

1 Like

I got my Tablo firmware update today, so hopefully soon. Samsung suggested that maybe they arenā€™t using the latest model for S7 / S7E to develop with.

Others need to post in various Cord Cutter forums and Samsung forums. I waited until it was two months before posting anywhere but here, but now warning people of the problem and work around needed. Would be awesome if Tablo got a Galaxy S7 to test with.

Iā€™d like to hear it straight from the horseā€™s mouth. Their lack of participation on this thread is starting to look like they are ignoring the issue.

Besides, without feedback from @TabloSupport (or any kind of communication on this matter) the only conclusion that can be drawn is that there is not going to be a solution ā€˜soonā€™.
To say the least this is more than a bit disappointing.

Iā€™ve talked to David some and have faith that it will be fixed. The last was waiting for 2.2.10 but now thatā€™s done, if not soon I too will begin to have doubts. Will my birthday or the fix come first? I think my birthday, which is June 30.

Thatā€™s great, but I donā€™t know who David is. If he is a Tablo representative maybe he can speak for himself here and provide everyone with an update in his capacity as an authorized company representative instead of letting customers relay messages or otherwise speculate on when the fix may be coming.
I am sorry, it is nothing personal against you. Far from it. Iā€™m fed up with this issue, not being able to watch my Tabloā€™s content remotely on my phone. But what Iā€™ve truly lost my patience with is the lack of @TabloSupport or @TabloTV participation. That just tells me there is no fix coming. If there is one coming, even if it is months out, let THEM say so. At least that way we know its on their queue somewhere.

David answers the Tablo phone the majority of the time I call.

You CAN watch Tablo on your phone if you do the work around I posted. Add developer options. Check Disable hardware overlays. You need to check disable hardware overlays each time the phone is turned on or rebooted otherwise the flashing green returns.

Maybe by me posting the work around has slowed Tablo down at finding a fix. I thought it would point them to a solution. It is posted back on APRIL 16.

Thanks, but Iā€™m not interested in the work around.
I am interested in a fix and, more importantly (at this point in time at least), to hear from @TabloSupport.

Iā€™m calling today to let them know they can close a ticket for guide data on 20.2. It finally showed up yesterday on Tablo. Iā€™ll ask him to please post in the flashing green thread. People want to see a recent post by ANYONE at Tablo.

David says they will post this week. Weā€™ll see.

Hi all,

Quick update:

Weā€™ve made several attempts to secure a loaner device locally and unfortunately have not been successful. We are continuing to work to source a device as well as troubleshoot this without the specific hardware in order to narrow down and reproduce this issue.

Unfortunately since we havenā€™t yet been able to isolate the cause, we donā€™t have an ETA on a fix for this yet. That being said, now that weā€™ve got more time and resources to look at this issue, we hope to have it solved soon.

2 Likes

The silence has been broken! Letā€™s hope itā€™s not another two months before another post ,:laughing:

@TabloSupport any chance of Samsung loaning you one for 6 months or so, or sell you one at a reduced price? The problem occurs even when on Wi-Fi.

Anyone want to come to Austin, TX? You can test with mine. If you think itā€™s fixed Iā€™ll try the new app and let you now the results.

Thank you for the update. Please continue to provide status updates on a more or less regular basis so S7 users know that this has not fallen off your radar.

This is not the first time an application has encountered this issue. I donā€™t know how much documentation your Android developers have access to, but there are prior cases where this has happened.

Also, I donā€™t know how constrained your company is resource wise. But you could simply go out and buy an S7. It is not like you are spending resources on a device from an obscure company with only one customerā€¦ it is Samsungā€™s flagship phone, so it is likely that more and more of your customers would upgrade to it as time goes by.
Maybe Tablo doesnā€™t have resources and is too small for Samsung to send a sample phone for development. Just thought I mention it.

We purchase as wide of a cross-section of devices as possible, but unfortunately it isnā€™t entirely feasible to have every single Android device in house.

We have a few more rocks to turn over and are hopeful we can get one on loan.

Apparently thereā€™s enough difference between S6 and S7 to cause the problem on S7 and not the S6. Guess that means time found you to add a new phone.

I thought the Android SDK included software simulations for the phones. Maybe just need to update the Android SDK. I think thatā€™s what Samsung was hinting at.

@TabloSupport see http://developer.samsung.com/home.do

Edit: Test now link goes to
http://developer.samsung.com/remotetestlab/rtlDeviceList.action

Where there are all Samsung phones including our S7 and S7 Edge!

Looks like you need a Google specialist :laughing:

@beastman - The issue doesnā€™t appear in emulators. Since the problem is only occurring on the galaxy S7 family of phones, the problemā€™s almost certainly an issue with the Samsung firmware/hardware video decoders. There may be a work-around, but thereā€™s no way to find it for sure until we have a device.

It might be possible to download an S7 firmware image, and trick an emulator into using that instead, but thereā€™s no guarantee that it would produce the same behavior as a real device (since the hardware itself is likely the issue).

I thought with the second link in the last reply that Samsung had the firmware there.

It really canā€™t work using the testing site because of the dreaded pairing with Tabo. If there were a username / password option, which has been requested numerous times, then you could have.

Guess you need a physical S7.

Weā€™ve managed to test on a physical S7. Apparently, the International and US versions of the phones ship with different processors. We tested with the International version (since thatā€™s all thatā€™s available here) and it unfortunately did not exhibit the same issue. Weā€™re looking into next steps now.

1 Like