>>368894834
I think there was a workaround on their forums or something, I recall hearing about it on their Twitter and that it'll be fixed in a future firmware update. Maybe scroll through their forums or twitter