Agree @RobSewards - this is a difficult one to size, as we don't know it's happening in the client. The only possible indication we have is how long the session runs for - our assumption is that people won't leave the stream running in this bad state for long periods. So where our logs show users playing the video for 90+ minutes, we assume it's working for them - and thus this issue appears to only be affecting a subset of devices.
We've already had confirmation from Samsung that they don't see any issues with our content on any of the devices in their lab, so their current line of investigation is to get as much information from @Rob221 's device/experience as possible.
