Downloaded the SDK.. but...
Monkey Targets Forums/Android/Downloaded the SDK.. but...
| ||
| Right this is kinda buggin the hell outa me now, I have downloaded the sdk opened the sdk manager and got all the stuff it listed. But Monkey still does not show up Android as a target. :( Any tips ? |
| ||
| Have you set the path correctly in config.winnt.txt (if you use Windows)? |
| ||
'--------------------
'HTML player path.
'
'Must be set for HTML5 target support.
'
'for opening .html files...
HTML_PLAYER="${TRANSDIR}\mserver_winnt.exe"
'--------------------
'--------------------
'Ant build tool path
'
'Must be set to a valid dir for ANDROID target support
'
ANT_PATH="C:\apache-ant-1.8.2-bin\apache-ant-1.8.2"
ANT_PATH="${SYSTEMDRIVE}\apache-ant-1.8.2"
ANT_PATH="${SYSTEMDRIVE}\ant"
'--------------------
'--------------------
'MinGW path.
'
'Must be set to a valid dir for STDCPP target support.
'
MINGW_PATH="${SYSTEMDRIVE}\MinGW"
'--------------------
'--------------------
'Java dev kit path
'
'Must be set to a valid dir for ANDROID and FLASH target support
'
JDK_PATH="${PROGRAMFILES}\Java\jdk1.6.0_23"
JDK_PATH="${PROGRAMFILES}\Java\jdk1.6.0_21"
JDK_PATH="${PROGRAMFILES}\Java\jdk1.6.0_19"
'--------------------
'--------------------
'Android SDK and tool paths.
'
'Must be set to a valid for for ANDROID target support
'
'ANDROID_PATH="${SYSTEMDRIVE}\android-sdk-windows"
ANDROID_PATH="C:\Program Files\Android\android-sdk"
'--------------------
'--------------------
'Flex SDK and flash player path.
'
'FLEX_PATH Must be set for FLASH target support.
'Either HTML_PLAYER or FLASH_PLAYER must be set for FLASH target support.
'
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.6"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.5"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.1.0.16076"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.1"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.0.0.14159"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4.0"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk_4"
FLEX_PATH="${SYSTEMDRIVE}\flex_sdk"
'for opening .swf files...monkey will use HTML_PLAYER if this is not set.
'FLASH_PLAYER="${SYSTEMDRIVE}\flex_sdk_4.0\flashplayer_10_sa_debug.exe"
'--------------------
'--------------------
'MSBUILD path.
'
'Must be set for XNA and GLFW target support.
'
'MSBUILD_PATH="${WINDIR}\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"
MSBUILD_PATH="C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"
'--------------------
|
| ||
| Looks good, as long as your sdk is in "Program Files" and not in "Program Files (x86)". ;) Have you restarted the IDE? |
| ||
| Have you installed ant and the JDK as well? Are their paths correct? All three are needed for the Android target. I also have a feeling the Android SDK needed to be in a path with no spaces but could be wrong. |
| ||
| Did you use the 32bit java sdk? 64 bit does not work with Monkey. Maybe this helps? http://wiebo.wordpress.com/2011/05/08/how-to-monkey-and-android-development-setup/ |
| ||
| Noticed the issue, I am using a new version of the java sdk than those listed, just added a new line to add the version I have and I can now compile for droid. just now trying to figure out the emulator and how to get the app to run in it, looks like another nightmare , the WP7 emulator was so much easier than this. |
| ||
| And I got the 32 bit version I am sure. it's telling me it cant find the device or emulator. all this wealth of options in this emulator setup is a bit mind blowing. |
| ||
| Well yes, the device or emulator is a different story. You have to create an emulator first but this shouldn't affect the ability to build for android. |
| ||
Looked at your blog post Wiebo m8 I had done that already, think its the emulator I am having problems with now tho..BUILD SUCCESSFUL Total time: 1 minute 15 seconds * server not running * * daemon not running. starting it now on port 5037 * * daemon started successfully * Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running? Process Complete I had the emulator running, 3.1 or 3.2 with the window up waiting to see my app appear but then after being built successfully it bombs. |
| ||
| It's not a firewall issue is it ? |
| ||
| Does the emulator get as far as loading up the Android home screen before you try to build and run? |
| ||
| Nah it sits on an Android logo and thats it, is it supposed to loada fake home screen ? |
| ||
| Yeah, how long are you leaving it? Might take a minute or two to get there. |
| ||
| OH MY GOD, that was like 5 minutes just the get the home screen up, ok I will be giving Android a wide berth until I can get some hardware to test on because that emulator is a waste of diskspace. thanks for the heads up tho at least I know my app will run on it :) |
| ||
| I have only compiled for the android target so far, xna next ;) |
| ||
| The emulator is super slow to get going, but you can start it up in advance and then it will be ready when you need it. |
| ||
| yeah to be honest I have no clue, there are so many devices to pick from half of them I think are probably tablets and some I dont know given the resolution they seem to run at, so I think I will wait till I get an android phone. Or until some one does a write up explaining which the most popular emulator settings are and how to speed the damn thing up. |
| ||
| I read somewhere possibly here about sucess stories of developers running the x86 version of android on virtualbox and using that to test as it runs pretty much full speeed |
   |