This is related to later versions of ExoPlayer and that device. Google have been able to reproduce the issue, and are investigating it from their end, as noted in this GitHub Issue
This is related to later versions of ExoPlayer and that device. Google have been able to reproduce the issue, and are investigating it from their end, as noted in this GitHub Issue