Thanks for checking out the issue.
>> Note: The focus cannot be changed using touch/clicks!
Regarding how "the focus cannot be changed using touch/clicks!" maybe I'm using the wrong terms? When I touch an EditText box, it is highlighted and then, if I start typing things, the keys I type are routed there. I see that as the EditText box having gained focus as a result of a touch. Maybe there's another way to say that(?) but...by the way, why shouldn't touch or clicks change focus?
>> Strange is that the EditText receives the focus after clicking the CheckBox. As I said, touch usually doesn't
>> change the focus, but perhaps if there was no focus before the focus jumps to the uppermost view?
I had a requestFocus() call made from the button and so, when the screen first shows, that button is highlighted (as expected) and responds to the center key on the directional keypad. So there is an initial focus on the button. When the user clicks on the checkbox, my interpretation is that it puts the focus on the checkbox. If it doesn't, then the checkbox shouldn't be highlighted. If it does, then it should be. Either way, having the focus jump to an element above it seems strange.
>> Is it always the EditText or the uppermost View the focus jumps to ?
It seems to always jump to the first EditText box - even if there are elements above it (like radio buttons). In fact, if an EditText box 1 is declared in the XML file before an EditText box 2 but has a layout_below="EditText2" attribute to place it below EditText box 2 on the screen, it shows up above it anyway(!) and then the focus jumps to it (EditText box 1). I'm not sure if that is a related issue (the google docs does mention that things tend to show up in the order they are declared in the XML file but I just thought the layout_below attribute would do something...) or if I am just fiddling around with the attributes too much...
I'll post this to google.