Anyone have an idea what might be wrong?

Monkey Targets Forums/Android/Anyone have an idea what might be wrong?

Gerry Quinn(Posted 2012) [#1]
Last year I was using the Android emulator to run Monkey programs and had no major problems. But I didn't use it for a while and now they don't seem to work at all. When I compile the simplest program (e.g. monkeypuzzle from bananas) I just get a black screen on the emulator and eventually an error message that MonkeyGame is not responding.

I upgraded the Android SDK to Version 19 but it made no difference. My virtual machine is API Level 8 and seems to work fine for everything except Monkey games.

Is there some new thing I have to configure?


AdamRedwoods(Posted 2012) [#2]
which monkey version?


Gerry Quinn(Posted 2012) [#3]
It's happening on both the latest version and V39, so I guess all of them!


benmc(Posted 2012) [#4]
Have you opened ddm and looked for errors?

EDIT: Same happened for me on any 2.2 target, but the app launched fine on an API level 14 emulator. Looking at the project properties file in the Android target, it appears to set the target to android-13, so maybe you have to be using an API level of 13 or above?


Gerry Quinn(Posted 2012) [#5]
Ah, thanks... target was indeed the answer. Changing to an API-13 emulator got it working.

However according to http://developer.android.com/resources/dashboard/platform-versions.html API-13 has a minuscule share of the market. After much tearing of hair I was able to get it working on API-8 by altering ant.properties and build.properties. API-8 has 20% of all machines and only 6% are lower. I don't know why it is not the default target - maybe there is some technical reason...


Gerry Quinn(Posted 2012) [#6]
Aargh... the monkeypuzzle example works but my stuff doesn't, and Monkey docs say "Make sure to install at least "Android 3.2 (API 13) SDK Platform"."

This can't be right, surely? According to the page I linked only 7% of androids are API-13 or higher! Monkey was originally API-7 then went to API-8 which was fine. Now it wants API-13??? What happened to cause such a leap?


benmc(Posted 2012) [#7]
That may just be for the OpenGL requirements.

I've had no problem opening my projects in eclipse, setting the min-sdk to 8 and the target to 14, then building and running on my Android 2.2 device.


AdamRedwoods(Posted 2012) [#8]
I just did an emulator test through AVD manager api8, monkey56b, with a minib3d project and that worked.

my monkey/targets/android/templates/AndroidManifest.xml file is set for minSdk=3, targetSdk =7


Gerry Quinn(Posted 2012) [#9]
Okay, I found it... the problem was with the ANDROID_NATIVE_GL_ENABLED setting. I changed that to "true" and it worked.