Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
[deleted comment]
Same problem here (Huawei u8100 with QVGA display). But I cant use DPad to
select start
. Bigger problem for me is that game is not using whole display.
Original comment by Ganim...@gmail.com
on 1 Mar 2011 at 9:42
Yes, also a Huawei u8100 user, and I'll also add that on top of the Play button
being out of sight, the Quit button looks pretty weird: since it had no room
for horizontal displaying, it went vertical (it still works).
No screenshot since my phone isn't rooted.
Original comment by kojir...@gmail.com
on 1 Apr 2011 at 12:38
Same problem but I can access to the play button anyway in blind mode by
highlighting the button above, moving below and press the trackball (I use a
HTC wildfire)
Original comment by jeanraph...@gmail.com
on 12 Apr 2011 at 10:27
Same for me, I have a samsung corby i5500 with 240x320 resolution. I can't see
the play button and the quit button on the right of the screen is misplaced
Original comment by giandome...@gmail.com
on 17 Apr 2011 at 12:12
Hey, i have a Huawei u8120 with QVGA resolution, and i can start the game.
I choose "Extra arguments" , where to can write, and close down the keyboard,
after go down with the d-pad twice, and click.
And the game is starts, and work fine :)
Original comment by szalm...@gmail.com
on 25 Apr 2011 at 8:00
i have a telstra smart touch, and ive got the same problem with the play button
being cut off, and i cant find any way to start the game. Can u help me?
Original comment by williamj...@gmail.com
on 4 Jun 2011 at 11:18
What the anon at comment 7 suggested worked for me. Just go to the "Extra
arguments" option, then close the on-screen keyboard and press down twice, then
confirm.
Original comment by kojir...@gmail.com
on 4 Jun 2011 at 11:25
Can't find a way to click the play button on Samsung Galaxy Mini.
Original comment by mugna...@gmail.com
on 5 Jul 2011 at 6:18
The main screen layout has been redone to support various screen sizes. Please
download PrBoom4Android_1.2.0-beta.apk to fix this issue.
Original comment by clarkd...@gmail.com
on 6 Sep 2011 at 10:28
Original issue reported on code.google.com by
mr.leet....@gmail.com
on 1 Mar 2011 at 10:59