We hear you, and we’re investigating the issue. We hope to include a fix with proper calibration in a future update.