Replicant

I agree that this can be confusing, especially if the backlight of the buttons is not on. The menu key in the middle should work and lead back to the main menu. So we could change the instructions to use that until this is implemented.

I think changing the installation instructions a bit might be enough. When I installed v. 6.0 on my S2 and were in the recovery I didn't know which is the back button, but I also didn't know which is the "enter" button. In fact, I thought the back button was the "enter" button and so when I pressed it to make a selection the recovery menu just refreshed.

Maybe the device-specific installation page could just explain where the physical keys are located: the "enter" key on the right-hand side and the back button on the front.

A. S. wrote:

I think changing the installation instructions a bit might be enough. When I installed v. 6.0 on my S2 and were in the recovery I didn't know which is the back button, but I also didn't know which is the "enter" button. In fact, I thought the back button was the "enter" button and so when I pressed it to make a selection the recovery menu just refreshed.

Thanks for the feedback! Did you navigate using the screen by tapping on the menu entries? The buttons at the bottom or the sides of the device shouldn't be needed, except for going back to the main menu, because back buttons on the screen are missing (which this issue is about). Considering #1803, I get the feeling that this also needs to be clear so that users don't start searching for an enter button.

Maybe the device-specific installation page could just explain where the physical keys are located: the "enter" key on the right-hand side and the back button on the front.

The screen should be used for navigation. It only needs to be explained where the button is to get back to the main menu because there is currently no back button on the screen.

Some work was done to use the same wording across the different installation instructions, so that they only differ where there are actual differences between the devices. This makes it a lot easier to maintain them. The clarifications for going back to the main menu should be made in the same way across all devices currently supported by Replicant 6.0.

Wolfgang Wiedmeyer wrote:

Thanks for the feedback! Did you navigate using the screen by tapping on the menu entries? The buttons at the bottom or the sides of the device shouldn't be needed, except for going back to the main menu, because back buttons on the screen are missing (which this issue is about). Considering #1803, I get the feeling that this also needs to be clear so that users don't start searching for an enter button.

I actually used the volume keys to navigate. I can't remember if it was because it was impossible to use the touchscreen or simply because I'm such a newbie when it comes to smart phones and touch screens.

Maybe the device-specific installation page could just explain where the physical keys are located: the "enter" key on the right-hand side and the back button on the front.

The screen should be used for navigation. It only needs to be explained where the button is to get back to the main menu because there is currently no back button on the screen.

Yes, I guess you are right. Maybe there are others out there who need a reminder that the Galaxy devices actually have touch screens :-)

Some work was done to use the same wording across the different installation instructions, so that they only differ where there are actual differences between the devices. This makes it a lot easier to maintain them. The clarifications for going back to the main menu should be made in the same way across all devices currently supported by Replicant 6.0.

That sounds reasonable. Well, then I guess adding the back-menu entry would be sufficient for most people.

With these two commits, the touchkey light should be always on when in recovery. This should make it more clear that the button in the bottom right is for going back.
On devices with no touchkeys, like the Galaxy Tab 2 and Galaxy Nexus, on-screen buttons are used.