Device: Mi 11 Ultra
OS Version: Hyper OS 1.05 Star (Issue also present since initial Hyper OS release)
Issue Summary:
When using Face ID to unlock the device, the counter for failed attempts is incremented in such a way that only one attempt is allowed for unlocking the screen using the pattern code. In contrast, fingerprint unlocking allows multiple attempts. Additionally, the lockout time is occasionally set to an excessively long duration (up to 1400 ). A device restart is the only way to reset the counter, but even after restarting, only one attempt is allowed to unlock the screen using the pattern code.
Steps to Reproduce:
1. Lock the device and attempt to unlock using Face ID.
2. After a failed Face ID attempt, attempt to unlock the screen using the pattern code.
3. Observe that only one attempt is allowed before the device is locked out, with a very high lockout time (up to 1400).
4. Restart the device to reset the counter.
Expected Behavior:
- Face Unlock failed attempts should not impact the number of allowed attempts for unlocking via the pattern code.
- After multiple Face ID failures, the system should either allow separate attempts for the pattern code or gradually increase the timeout, rather than drastically locking the user out after one pattern attempt.
Actual Behavior:
- Only one attempt is allowed to unlock the device via the pattern code after a failed Face ID attempt.
- Lockout time is excessively long (up to 1400).
- Restarting the device resets the timer but does not resolve the underlying issue with the attempt counter.
Suggested Fix:
- Separate the attempt counters for Face ID and pattern code unlocks, allowing more than one pattern attempt even after Face ID failures.
- Alternatively, implement a system where Face ID disables after a set number of failures, and then only the pattern code or fingerprint unlock can be used, without drastically increasing the lockout time after just one attempt.
Additional Information:
This issue has been present since the first version of Hyper OS, and neither of the subsequent updates has addressed or resolved the problem.
OS Version: Hyper OS 1.05 Star (Issue also present since initial Hyper OS release)
Issue Summary:
When using Face ID to unlock the device, the counter for failed attempts is incremented in such a way that only one attempt is allowed for unlocking the screen using the pattern code. In contrast, fingerprint unlocking allows multiple attempts. Additionally, the lockout time is occasionally set to an excessively long duration (up to 1400 ). A device restart is the only way to reset the counter, but even after restarting, only one attempt is allowed to unlock the screen using the pattern code.
Steps to Reproduce:
1. Lock the device and attempt to unlock using Face ID.
2. After a failed Face ID attempt, attempt to unlock the screen using the pattern code.
3. Observe that only one attempt is allowed before the device is locked out, with a very high lockout time (up to 1400).
4. Restart the device to reset the counter.
Expected Behavior:
- Face Unlock failed attempts should not impact the number of allowed attempts for unlocking via the pattern code.
- After multiple Face ID failures, the system should either allow separate attempts for the pattern code or gradually increase the timeout, rather than drastically locking the user out after one pattern attempt.
Actual Behavior:
- Only one attempt is allowed to unlock the device via the pattern code after a failed Face ID attempt.
- Lockout time is excessively long (up to 1400).
- Restarting the device resets the timer but does not resolve the underlying issue with the attempt counter.
Suggested Fix:
- Separate the attempt counters for Face ID and pattern code unlocks, allowing more than one pattern attempt even after Face ID failures.
- Alternatively, implement a system where Face ID disables after a set number of failures, and then only the pattern code or fingerprint unlock can be used, without drastically increasing the lockout time after just one attempt.
Additional Information:
This issue has been present since the first version of Hyper OS, and neither of the subsequent updates has addressed or resolved the problem.
