Very happy I checked this page today, new apk seems to work. Thank you!
1 Like
Iād say thanks but Google was not delaying a fix, it was you Plex, and you passing the buck, and you havenāt even offered refunds for over 6 months of a common, critical issue consistently crashing devices.
You couldāve actually tested the release.
You couldāve temporarily rolled back changes to the last functional release.
You couldāve delved into why killing the app and restarting it was able to sidestep a crash, which highly suggests it was in your power to create a temporary fix.
Cut the excuses, the spin, apologise, offer refunds, and stop letting critical issues like this linger for 6-12 months or even longer.
4 Likes
Know Iāve, as a matter of sheer frustration here, shared these same sentiments via every channel I could. Ultimately an organization is defined by its RESPONSE to a challenge and Iām sorry but the review here does not reflect favorably on Plex. Iāve asked previously for you to step up here. Remember that many of the same folks yelling at you now supported you then.
1 Like
To be fair, I donāt think the Plex team would have ever figured this one out - it needed the expertise of the Google TV team and SOC vendor:
Also, the issue isnāt even fixed (the root cause, I mean). Plex has introduced a quick workaround to stop the issue from occurring (disabling ātunnel modeā) while Google TV will hopefully continue to resolve the issue at the lower level.
So the Plex team acted pretty quickly to get that test version out with the workaround!
Unfortunately it just took a really long time to narrow the issue downā¦
Iām not aiming to be unfair here but the simple fact is that bugs will be introduced via software revisions. In this case, as many have highlighted, there was a version where it went bad. The user base highlighted that and Plex refused responsibility for the bug AND to look at or implement reversions that might resolve it. The SOC may be a root cause but to suggest that Plex is blameless here (the issue here noted by Google and the SOC vendor as a non-typical approach) is not reasonable. A reversion (even if a limited one) WAS the fix here.
2 Likes
I just want to take a moment to recommend anybody trying this preview apk, that they should force stop the app and clear cache.
I had to do this for all three of mine to get this to work properly.
1 Like
After updating to the beta, my subtitles would not work and the video was play at 2x speed after trying to enable the subtitles. I had to clear the data, not just the cache to resolve. But now everything seems to be working.
@sixones Thank you for getting the workaround beta out quickly after the cause was identified by Google TV and SOC Team. Hopefully they resolve the lower level issue soon.
Please forgive my noob question. I should be better than this. But can someone help me change my Channel to the Beta Channel from the Play Store on the Chromecast with Google TV. Then I should get the new version next week and still get auto updates from the Play Store.
1 Like
@hedbert, there are several ways to sideload an APK. The method I used is described below:
Those steps are for an android phone. You would start off by downloading the below APK to your phone:
https://artifacts.plex.tv/android-experimental/8.26.0.28805-ec518bea/PlexForAndroid-8.26.0.28805-ec518bea-Armv7aGooglePlayStdExo.apk
Hope that helps.
2 Likes
I had my first āfaultā with the new beta version last night. When one HEVC episode finished, the next started and played normally, except there was no sound and trying to turn on a subtitle kept resulting in an error. I just had to go back to the episode list (which didnāt show I had started the next episode) and play it from there, then it worked properly.
So, there was no crash or stretching, etc, and itās only happened once, but there may still be some small bug in there somewhere.
The APK link doesnāt work for me. Anyone else have a link?
1 Like
404 file not found.
1 Like
The fix has been deployed to beta which can be downloaded from; Release Announcements - Android TV beta - #481 by sixones
Alternatively, if you have an Android mobile thatās signed into the same Google account that you use on your Chromecast device you can join the beta via the Play store, after a few hours the update should be available.
2 Likes
Does this beta fix the problem for all affected devices, or just specifically the Chromecast Google TV? This stretching problem is still happening on 8.26.0.28833 release on the Walmart Android TV device that uses a similar chip to the Google TV. I recapped this a while back here in this thread, but also in a separate request along with some other problems with the device:
I think it was a fix proposed by the SoC manufacturer who as far as I know is the same manufacturer of the SoC in the onn. Android box. So it should fix it. Sign up for the beta branch on the Play Store and let us know if it alleviates it for you.
The 8.26.0.28833 release I noted above is the beta, right? Iām enrolled for the beta inside the Play Store.
Maybe they arenāt the same then. I think the beta was 8.26.0.28805
The latest beta also includes the fix, however the fix is only for the Chromecast with Google TV device.
If you can fetch the logs from the device I can make a build that includes the same fix for your device, if it solves the problem we can get that into beta. Steps for fetching the logs are available here; https://support.plex.tv/articles/201573117-android-android-tv-fire-tv-logs/
im sorry but being a new user of the google TV, what im supposed to do to not have the Google TV reboot ? update plex directlt on google TV ? update plex on my computer ? im confused
The issue was with the Chromecast w/ Google TV itself. To fix this you need to go to the Play Store, opt into the beta and install the beta app on your Chromecast. Or you can wait for the official release which should be on its way pretty quickly. It may have even been released already.
