I'm crossing my fingers that the upcoming firmware update mentioned in the newsletter will fix this issue, but who knows.