If there are usability issues with the user interface on Android, I'm sure Holger wants to know about and fix them.
Definitely yes!
I play on Android. I've noticed that there is an option "Ask on Esc key" and the Esc key is linked with a back button. But in my phone, I have to pull out a navigation bar from the edge of the smartphone (with swiping) and then I can press that button...
Yes, I am aware of this problem, but unfortunately can not offer a solution at this moment.
The problem is the following: There is a "stop" button with asking (as you might have touched it by accident), and there is the Android back button (which is handled like the "Escape key" on a classic keyboard, and can be configured to not ask when pressed). This worked more or less nicely as long as the Android back button was a hardware key on many Android devices, and was not part of the display. However, most current Android devices have a display now that covers the whole device, so the back button is now usually part of the display, too. Even worse, with recent Android versions, the back button is usually hidden and has to be made available by swiping from the lower screen border upwards, which makes accessing the back button less easy as before.
There are several possible solutions to this problem:
For one, it is possible to programmatically use a fullscreen display that always shows the navigation buttons (back button, home button and that third button that once was a context menu button and now is some sort of task switcher). The disadvantages are that the usable display size is permanently smaller (which is not that big of a problem for R'n'D, which usually does not use the full display), and that it is now asymmetrical when used in landscape mode (as the system button area is only on one side of the screen now).
As only the back button is needed from those three system buttons, a solution may be to add an option to prevent asking when you hit the stop button. That way, you could stop -> menu -> start, which at leasts prevents you from answering a "do you really..." request.
Another solution could be to (optionally?) add another on-screen button to restart the level (with asking as usual, but which could also get an option to turn it off).
Regarding the initial proposal by jkkk (to add a third option "restart" in the request window): This looks good on first view, but has a number of disadvantages, especially as such a request cannot be answered in a "yes/no" way using a two-key or two button system (like Escape/Enter, left/right joystick button, ok/back keys on a FireTV remote etc.).
So it seems that at least the Android interface needs some additional tweaking here, to please the impatient user...
But adding a dedicated "restart" key for the non-touch screen versions may also be a good idea...