That’s great news, although I must admit I’m equally confused as to what has changed that has solved the issue. I would suggest monitoring that device in case the issue turns out to be intermittent, hopefully that won’t be the case though.
If you will have problems again, could you try to clear player cache from CMS instead of removing player ? (Altho it could be same function in work.)