Thanks - have tracked down the issue and will fix it for the next app update. Unfortunately there's not a workaround for that device in the meantime that I'm aware of.