EDIT: Never mind.
It runs. It just takes five minutes to load and make the emulator ready. I’m not used to tools taking that long to work. And the program (Drop game tutorial) is really sluggish and doesn’t respond to keyboard (and images greatly lag sound events). But it is running.
[s]I am attempting to run the most basic Libdgx-android project on Eclipse Juno. As far as I know, the most basic program, using the setup tool, should display the Libgdx.png file. The -desktop and -html both display the .png as expected.
Maybe there is something basic in the way I’ve configured things that is causing problems? Being totally new to this, I wouldn’t be at all surprised.
Here is the error message when running the -android project (after starting the AVD for the Galaxy Nexus–maybe there’s a better emulator to run?) via right clicking and selecting “run as Android project”:
[2013-08-04 22:11:40 - hierarchyviewer]Unable to get view server version from device emulator-5554
[2013-08-04 22:11:40 - hierarchyviewer]Unable to get view server protocol version from device emulator-5554
[2013-08-04 22:11:41 - ViewServerDevice]Unable to debug device: AVD_for_Galaxy_Nexus [emulator-5554]
[2013-08-04 22:11:41 - hierarchyviewer]Unable to get the focused window from device emulator-5554
I just turned off this emulator and tried running the program (right click on project, select “Debug as Android Application”) again. It automatically picks another emulator that I had loaded yesterday and gives the same sort of error messages.
[2013-08-04 22:20:19 - hierarchyviewer]Unable to get view server version from device emulator-5554
[2013-08-04 22:20:19 - hierarchyviewer]Unable to get view server protocol version from device emulator-5554
[2013-08-04 22:20:19 - ViewServerDevice]Unable to debug device: AVD_for_4.0_WVGA_480x800 [emulator-5554]
[2013-08-04 22:20:19 - hierarchyviewer]Unable to get the focused window from device emulator-5554
When loading the generated project into Eclipse, I have to go into the Build configuration, select Android and click Project Build Target: “Android 4.3”, and I leave unclicked “Google APIs”.
This act gets rid of error messages I previously wrote about. I also go into the AndroidManifest.xml and set the targetSdkVersion from 17 to 18 to match the API indicated in the Android SDK Manager in Eclipse.
Tried again–this time more error messages, and I tried launching the Galaxy when asked.
[2013-08-04 22:38:10 - AngryMason-android] ------------------------------
[2013-08-04 22:38:10 - AngryMason-android] Android Launch!
[2013-08-04 22:38:10 - AngryMason-android] adb is running normally.
[2013-08-04 22:38:10 - AngryMason-android] Performing com.adonax.AngryMason.MainActivity activity launch
[2013-08-04 22:38:10 - AngryMason-android] Failed to find an AVD compatible with target 'Google APIs'.
[2013-08-04 22:39:05 - AngryMason-android] Still no compatible AVDs with target 'Google APIs': Aborting launch.
[2013-08-04 22:39:05 - AngryMason-android] Performing com.adonax.AngryMason.MainActivity activity launch
[2013-08-04 22:39:29 - AngryMason-android] Launching a new emulator with Virtual Device 'AVD_for_Galaxy_Nexus'
[2013-08-04 22:39:35 - Emulator] Failed to create Context 0x3005
[2013-08-04 22:39:35 - Emulator] emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
[2013-08-04 22:39:36 - AngryMason-android] New emulator found: emulator-5554
[2013-08-04 22:39:36 - AngryMason-android] Waiting for HOME ('android.process.acore') to be launched...
Then all this disappears and the first errors I posted reappear.
Am quite lost. Is there another AVD that would be a better choice?
Also, as might be expected, I get similar messages when trying to run the “Drop” tutorial that does run in the -desktop version. [/s]