I’m on an android version that now has a “launch video player” step, meaning my only way to play video is via a pl link. This worked for a while but now presents a 404 error. What’s up with this @mattb33 ?
Here’s a link…
I’m on an android version that now has a “launch video player” step, meaning my only way to play video is via a pl link. This worked for a while but now presents a 404 error. What’s up with this @mattb33 ?
Here’s a link…
I can’t see the screenshot. But I had some other issues with that Launch video player. I downloaded the vlc media player for android which is free in the play store. Select that after Launch video player and it works perfectly
If this is an older Android version (I have 4.1) then the pl will actually get fired off via yet another browser call. You might want to check your app association defaults through Android to make sure URLs are handled with Chome instead of the older (broken) Android browser.
Ya, browser associations are cleared. Been using MX player for local playback and Chrome browser for Chromecast playback.
404 not found is the Chrome browser error.
MX player is less descriptive and says, unable to play file. Both of these worked right after 2.1.16 when the ‘launch video player’ feature was enforced for “older” android like mine, 4.1.2.
Seems to me to be a web app change that broke this… But if no one else is encountering this… My fustration grows, as my phone is yet another playback device Tablo has taken away. I’m down to just a tablet, a high end computer and a Roku… from 8 devices I could play Tablo on back when it was released 6-9 months ago.
@Thumbs 404 will only be sent to the web app if the recording isn’t actually ‘there’. Does this happen for each one you try to play? Or can you play this same recording on a different device?
@TabloSupport yes this happens for all shows, none have worked through the Tablo “launch video player” button… All shows do work on my windows chrome browser, which plays videos inline.
I went so far as to paste the URL the “launch video player” button loads on my android device, into my windows chrome browser… Where it also reports 404 -not found.
Also, on both the android and windows chrome browser, they both display an episode thumbnail when selected. This usually means the video file exist… And they do.
This is pretty clearly a web app issue with the “launch video player” button. Fix it please and please keep it in your QA routine.
@Thumbs I have the same exact problem, when I launch VLC from Chrome, it gives me a 404 - Not Found. This has never happened before.
No kidding @Barbz … I can’t even recall getting through one episode of a show on Android without cursing at Tablo under my breath.
I am a bit more optimistic that Tablo will get it right. I got one to avoid giving another nickel to satellite or cable any longer.
Just an an fyi. My Chome on phone, Android 4.1 used to work… but now even after clearing out Chrome data/cache and reconnecting, all I ever get is a 404 when I try to play something back. Android 4.1 is really old, so it basically has to launch the player through another browser request (a two step)… but this did used to work for me. I did recently have a security update on my phone, but I can’t say what broke the web app. But now all I get is 404 not found when trying to play anything.
@cjcox We’ve actually been doing quite a bit of testing with Android 4.1 the last few days, and it’s been tricky.
I erased all Chrome data (both data and cache) before attempting and posting here. Waited for sync… and tried, still I get the 404.
@TabloSupport this issue is due to the ‘=’ added to the end of the url sent by the ‘Launch player’ button for android 4.1 and older web users. Fix that please.
@Thumbs, thank you, thank you!
While the extraneous = makes for a bad demo from my phone, at least it can be made to “work”. I have no idea when this broke though. @TabloSupport, are you sure this wasn’t added on your side? If not, then something on the Android side is doing this now and it didn’t used to… at least in prior testing.
@Thumbs @cjcox Interesting! We haven’t made any recent pushes, so it’s possible that something changed on the Android side - but we’ll have to take a closer look to be sure. We’ll clear this up ASAP!