You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wording is inconsistent and misleading in Recovery menu. Indeed "FIRST BOOT DISABLE" is by default and means here that it's disabled and that you have to click to enable it. Regarding "FACTORY TESTS ENABLE" it's the contrary: it's here disabled too and you have to click to enable it whereas the wording is the opposite, that's very confusing and we should differentiate the state of an option and the action it performs when clicking it. As an example, I myself misclicked one or two times and triggered the FIRST BOOT sequence by mistake.
Tested on firmwares 2.0.0, 2.0.1, 2.1.0, 2.1.1 beta, 2.2.0 beta.
Steps to reproduce the behavior:
Press Fn+START while booting the device
Once in Recovery menu, use UP or DOWN d-pad to select menu
Notice the the inconsistency between "FACTORY TESTS ENABLE", "FIRST BOOT DISABLE" and "NETWORK ENABLE"
Expected behavior
By default, you should have the different options like this:
ENABLE FACTORY TESTS => DISABLE FACTORY TESTS
ENABLE FIRST BOOT => DISABLE FIRST BOOT
ENABLE NETWORK => DISABLE NETWORK
or
FACTORY TESTS: DISABLED => FACTORY TESTS: ENABLED
FIRST BOOT: DISABLED => FIRST BOOT: ENABLED
NETWORK: DISABLED => NETWORK: ENABLED
Note: I personally prefer the 2nd one, more natural as that's easier to understand the current status of each option.
Screenshots
The text was updated successfully, but these errors were encountered:
DrUm78
changed the title
Inconsistent and misleading wording in Recovery menu
[Recovery] Inconsistent and misleading wording in the menu
Apr 23, 2021
Wording is inconsistent and misleading in Recovery menu. Indeed "FIRST BOOT DISABLE" is by default and means here that it's disabled and that you have to click to enable it. Regarding "FACTORY TESTS ENABLE" it's the contrary: it's here disabled too and you have to click to enable it whereas the wording is the opposite, that's very confusing and we should differentiate the state of an option and the action it performs when clicking it. As an example, I myself misclicked one or two times and triggered the FIRST BOOT sequence by mistake.
Tested on firmwares 2.0.0, 2.0.1, 2.1.0, 2.1.1 beta, 2.2.0 beta.
Steps to reproduce the behavior:
Expected behavior
By default, you should have the different options like this:
ENABLE FACTORY TESTS => DISABLE FACTORY TESTS
ENABLE FIRST BOOT => DISABLE FIRST BOOT
ENABLE NETWORK => DISABLE NETWORK
or
FACTORY TESTS: DISABLED => FACTORY TESTS: ENABLED
FIRST BOOT: DISABLED => FIRST BOOT: ENABLED
NETWORK: DISABLED => NETWORK: ENABLED
Note: I personally prefer the 2nd one, more natural as that's easier to understand the current status of each option.
Screenshots
The text was updated successfully, but these errors were encountered: