Messages

Some bugs I found in the latest Android build:
- The app still segfaults on exit (i.e. pressing back key)
- Backgrounding the app is buggy: If the app gets killed by the system, everything is fine; if it's still running, the screen shows but it doesn't respond after re-opening
- Pressing "x" on the hardware keyboard exits the app
- Portrait orientation is somehow hardwired, if you want to make a landscape app, you have to (1) select landscape mode in the manifest file to get the right d-pad directions and (2) select a portrait (!) screen resolution in GLB

Does GLB_ON_QUIT already work on Android?

Motorola Milestone (Droid) - DRAWRECT colors working

Thanks for getting the keyboard working! However, there are still some minor flaws:
- Space isn't detected yet
- Pressing X exits the app
- For landscape apps the D-Pad directions are rotated by 90° by default because portrait orientation is hard-coded into the manifest. You have to change it manually, but it would be nice if it's set automatically depending on project settings.
- Sliding the keyboard out exits the app. To prevent this, you need to add android:configChanges="keyboardHidden|orientation" to the <activity> tag in the manifest file. This should also be included in the template project.

Concerning the crash/segfault on closing - here is the debug log from a device (Motorola Milestone, Android 2.2.1/Cyanogen 6.1):

Code (glbasic) Select Expand

I/SDL     ( 4497): [STUB] GL_UnloadLibrary
D/dalvikvm( 4497): threadid=9: thread exiting, not yet detached (count=0)
D/dalvikvm( 4497): threadid=9: thread exiting, not yet detached (count=1)
E/dalvikvm( 4497): threadid=9: native thread exited without detaching
E/dalvikvm( 4497): VM aborting
I/DEBUG   ( 4448): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 4448): Build fingerprint: 'MOTO_RTEU/umts_sholes/umts_sholes/sholes:2.2.1/SHOLS_U2_05.26.3/296482885:user/release-keys'
I/DEBUG   ( 4448): pid: 4497, tid: 4505  >>> com.yourcompany.test <<<
I/DEBUG   ( 4448): signal 11 (SIGSEGV), fault addr deadd00d

For further explanation I'll just quote quote from here:

FWIW, fault address "deadd00d" indicates a deliberate VM abort. Before aborting the VM writes an explanation to the log file; you should see it up above what you pasted here.

So there's a thread exiting without being detached from the VM, therefore the VM exits too. This seems to happen right after GL_UnloadLibrary is called, so that's the place where to look for it.

Another thing is that I found many exit()s in the code. You really should avoid using that since Android is designed to care of exiting applications itself. You should just close your activity instead (Activity.finish() from Java; read this if you want to call it from a different thread).

"optical scroll" is just a different kind of D-Pad. Some of the HTC Desire phones have these: