Is there a reason why Amazon Store and Amazon FireExo releases are named identical since two releases? Before there was a FireExo tag in the name of the download. Looking at the list of downloads, it seems that both Amazon releases share the same download name now. Is this correct?
Will be watching to see the response on this. I feel like playback hasn’t been as smooth with 9.2 compared to 9.1, also issues with the app crashing. If this is actually the wrong version due to a mistake in the release post that could be related. I’ve been side loading due to long delays on Amazon’s app store approval.
For a while now we have merged the two ExoPlayer variants into a single variant (since last year), as this hasn’t caused any issues on non-FireTV devices we have committed to the merge and have reduced our APK’s to follow. Previously, Amazon AppStore APK’s would use the Google variant of ExoPlayer, and the Fire OS APK would use an Amazon variant, now they have been merged we can use a single APK for Amazon AppStore and Fire OS.
To be more technical; Amazon adds a bunch of modifications to ExoPlayer that are specifically for FireTV devices, each code change they make only runs on an Amazon device (through lots of if’s and model checks), we now bundle all of these modifications into Google ExoPlayer.
What playback issues have you been experiencing with v9.2? Oddly there has been no playback changes to the app in v9.2 - the playback work that has taken place was all for Movies & TV via Plex or features that haven’t yet been merged into the code base (such as full ASS subtitles support).
Stuttering on some playback (panning shots) and the app freezing up and crashing at times, too. This is HVEC content with ASS subs, but the device is being fed a transcoded stream anyway from my server, so I would expect playback to be the same as with most other content.
If I keep seeing this I’ll see if I can get some logs or something when it hangs/crashes and make a new thread.
Please do, ping me on the thread and I will take a look!
