I'm new to Android development, and I'm having trouble with a simple
Hello World app..
It worked yesterday with the emulator, on a virtual device with Android
1.5
When I run the app a day after, it's stuck at the android startup
screen continuously outputting the following:
[2012-02-17 23:40:03 - HelloWorldAndroid] Starting activity
com.mathias.HelloWorldAndroidActivity on device emulator-5554
[2012-02-17 23:40:05 - HelloWorldAndroid] ActivityManager: Can't
dispatch DDM chunk 46454154: no handler defined
[2012-02-17 23:40:05 - HelloWorldAndroid] ActivityManager: Can't
dispatch DDM chunk 4d505251: no handler defined
[2012-02-17 23:40:06 - HelloWorldAndroid] Device not ready. Waiting 3
seconds before next attempt.
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: INTENT is
described with:
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [-a
<ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>]
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [-c
<CATEGORY> [-c <CATEGORY>] ...]
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [-e|--es
<EXTRA_KEY> <EXTRA_STRING_VALUE> ...]
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [--ez
<EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> ...]
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [-e|--ei
<EXTRA_KEY> <EXTRA_INT_VALUE> ...]
[2012-02-17 23:40:06 - HelloWorldAndroid] ActivityManager: [-n
<COMPONENT>] [-f <FLAGS>] [<URI>]
I've searched google and found several people with the same problem, but I was unable to find a solution.
I'm running Eclipse Indigo Service Release 1
Looking forward to more app development, when I get this working :-)
Thanks in advance!
/Mathias
I usually see "Can't dispatch DDM chunk" when there are issues with the SDK installation. Make sure that you do not have two different copies of the Android SDK and are mixing and matching them (e.g., you are using one SDK copy with Eclipse and a different SDK copy from the command line at the same time).
I have read that it is a message that means that your app requirements and AVD are slightly incompatible. For example, if you have Android 3.2 installed for ad purposes, and you test the app on a Android 2.1 emulator, you will get this message.
And one important thing is that, you've to provide minSDKVersion and targetVersion in manifest file.
Related
So everything was working fine, today I opened android studio and try to run the emulator, and it wont start. I will provide the errors in an image bellow.
I tried wiping the emulators data , and disabled the antivirus, I tried new device...
Please help I need it :(
ERRORS OF EMULATOR PICTURE
11:45 AM Gradle sync started
11:45 AM Gradle sync finished in 2 s 250 ms (from cached state)
11:46 AM Executing tasks: [clean, :app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 47 s 998 ms
11:47 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 20 s 141 ms
11:48 AM Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: C:\Users\User.android\emulator-grpc.cer security will be disabled.
11:48 AM Emulator: Started GRPC server at 127.0.0.1:8554
11:48 AM Emulator: C:\Users\User\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
11:48 AM Emulator: deleteSnapshot: for default_boot
11:48 AM Emulator: Process finished with exit code 0
11:49 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:49 AM Gradle build finished in 5 s 906 ms
Possible solutions
Invalidate/Restart Android studio
Open AVD Manager select you emulator and wipe Data from the dropdown
Installing Intel latest Intel HAXM
or delete current emulator and install new one
I want to say, that any possible solution did not work for me, I lost 4 hours working on that. I quit and installed Genymotion , I can tell that it runned smoother than the android emulator.
i followed all the instructions in the tutorials, but from some reason i can't create the emulator....
what eclipsed showed me after trying to run:
[2013-09-06 12:24:30 - The New Boston] ------------------------------
[2013-09-06 12:24:30 - The New Boston] Android Launch!
[2013-09-06 12:24:30 - The New Boston] adb is running normally.
[2013-09-06 12:24:30 - The New Boston] Performing com.TheNewBoston.travis.StartingPoint activity launch
[2013-09-06 12:24:30 - The New Boston] Automatic Target Mode: launching new emulator with compatible AVD 'droidX'
[2013-09-06 12:24:30 - The New Boston] Launching a new emulator with Virtual Device 'droidX'
[2013-09-06 12:24:33 - Emulator] Failed to allocate memory: 8
[2013-09-06 12:24:33 - Emulator]
[2013-09-06 12:24:33 - Emulator] This application has requested the Runtime to terminate it in an unusual way.
[2013-09-06 12:24:33 - Emulator] Please contact the application's support team for more information.
In IDE menu click on windows option. Go in android virtual device manager. If you created any emulator click on that emulator. then edit and in memory options. change RAM size to 256, 512 or 1024. Hope its work.
I just created a sample Hello world through Eclips in Windows. If i debug the application, emulator halts saying waiting for debugger,
Recently i updated to API 16 & 17.
here is the console message:
[2013-02-09 12:56:45 - helloworld] ------------------------------
[2013-02-09 12:56:45 - helloworld] Android Launch!
[2013-02-09 12:56:45 - helloworld] adb is running normally.
[2013-02-09 12:56:45 - helloworld] Performing com.example.helloworld.MainActivity activity launch
[2013-02-09 12:56:45 - helloworld] Automatic Target Mode: launching new emulator with compatible AVD 'FROYO'
[2013-02-09 12:56:45 - helloworld] Launching a new emulator with Virtual Device 'FROYO'
[2013-02-09 12:56:47 - helloworld] New emulator found: emulator-5554
[2013-02-09 12:56:47 - helloworld] Waiting for HOME ('android.process.acore') to be launched...
[2013-02-09 12:58:36 - helloworld] ------------------------------
[2013-02-09 12:58:36 - helloworld] Android Launch!
[2013-02-09 12:58:36 - helloworld] adb is running normally.
[2013-02-09 12:58:36 - helloworld] Performing com.example.helloworld.MainActivity activity launch
[2013-02-09 12:58:37 - helloworld] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'FROYO'
[2013-02-09 12:58:37 - helloworld] Uploading helloworld.apk onto device 'emulator-5554'
[2013-02-09 12:58:39 - helloworld] Installing helloworld.apk...
[2013-02-09 12:58:43 - helloworld] Success!
[2013-02-09 12:58:44 - helloworld] Starting activity com.example.helloworld.MainActivity on device emulator-5554
[2013-02-09 12:58:45 - helloworld] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.helloworld/.MainActivity }
Best solution is to get the fresh copy of ADT from Google and start development, its 399 MB only.
I have installed and set up Eclipse and the plugin ADT in order to work with Android SDK. So far so good. But when I try to launch a VM(virtual Machine) for any android platform that I choose (for example: android 3.2) I just get the skin launched together with a keyboard console and phone buttons, it seems to boot up to a state and then does nothing but displays the android logo on the main vm screen and that's all it does - no more!, no VM functionality!, what's going on? Have I missed out some step? Please help...
Have been waiting sometimes over 10 mins in each case for the emulator to start.
I launched/ran an Android project test sample; 'hello world' from the eclipse environment after installing the ADT plugin for Android These are the error messages I had displayed in the console ddms:
[2012-04-30 14:31:20 - HelloAndroid]
[2012-04-30 14:31:20 - HelloAndroid] Android Launch!
[2012-04-30 14:31:20 - HelloAndroid] adb is running normally.
[2012-04-30 14:31:20
- HelloAndroid] Performing com.example.helloandroid.HelloAndroidActivity activity launch
[2012-04-30 14:31:20 - HelloAndroid] Automatic Target Mode: launching
new emulator with compatible AVD
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:20 -
HelloAndroid] Launching a new emulator with Virtual Device
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:40 -
Emulator] Warning: No DNS servers found
[2012-04-30 14:31:52 -
Emulator] emulator: emulator window was out of view and was recentered
[2012-04-30 14:31:52 - Emulator]
[2012-04-30 14:31:53 - HelloAndroid]
New emulator found: emulator-5554
[2012-04-30 14:31:53 - HelloAndroid]
Waiting for HOME ('android.process.acore') to be launched...
[2012-04-30 14:49:03 - HelloAndroid] HOME is up on device
'emulator-5554' [2012-04-30 14:49:03 - HelloAndroid] Uploading
HelloAndroid.apk onto device 'emulator-5554'
[2012-04-30 14:49:03 -
HelloAndroid] Installing HelloAndroid.apk...
[2012-04-30 14:51:38 -
HelloAndroid] Failed to install HelloAndroid.apk on device
'emulator-5554!
[2012-04-30 14:51:38 - HelloAndroid] (null)
[2012-04-30 14:51:39 - HelloAndroid] Launch canceled!
At no point have I have anything but the Android logo displayed on my emulator. I have tried various platform emulators - none of them are performing!
A second lot of errors I received back on a test run after I checked the user data wiped in the Run configuration menu was: result
: [2012-04-30 17:20:27 - Emulator] Failed to allocate memory: 1455
[2012-04-30 17:20:27 - Emulator]
[2012-04-30 17:20:27 - Emulator] This
application has requested the Runtime to terminate it in an unusual
way.
[2012-04-30 17:20:27 - Emulator] Please contact the application's
support team for more information.
Bench mark results of my computer using Novabench incase anyone wants to check, are:
30/04/2012 17:45:59 Microsoft Windows 7 Starter Intel Atom N550
1.50GHz # 1500 MHz Graphics Card: Intel(R) Graphics Media Accelerator 3150
1014 MB System RAM (Score: 78) - RAM Speed: 1610 MB/s
CPU Tests (Score: 70) - Floating Point Operations/Second: 24110532 -
Integer Operations/Second: 43813828 - MD5 Hashes Generated/Second:
159380
Graphics Tests (Score: 1) - 3D Frames Per Second: 3
Hardware Tests (Score: 6) - Primary Partition Capacity: 87 GB - Drive
Write Speed: 14 MB/s
Do you Run your project or only start an emulator? After starting emulator, click Run button and select "Run as Android project".
I am not sure how long you waited, but starting the emulator the first time (before you have a snapshot) can take quite a long time. Depending on you hardware it can take more than 10 minutes to launch.
I had a similar issue which was solved by creating a new emulator and running it. You can check progress in Devices view through DDMS. Sometimes, this problem may occur when a snapshot enabled emulator hangs because of error, which can be solved by starting the emulator with user data wiped.
Emulator thread automatically cuts off if for some time you have not done any activity on it..
so.. keep running your app to keep emulator on LIVE!
My advice - if you having an android phone.. please usb debug it and Debug your application on your phone... You will feel relieved from the long durations of the emulator........ to run!! :)
I am having trouble getting my app to run in both API level 7 and and 8. The code works fine in both versions when I start the project from the ground up in eclipse and I target the respective API level. However my setup that should run both does this when targeted for 7 and starting in API 8 when starting the emulator.
[2011-05-24 11:47:02 - AndroidHTOnline] ------------------------------
[2011-05-24 11:47:02 - AndroidHTOnline] Android Launch!
[2011-05-24 11:47:02 - AndroidHTOnline] adb is running normally.
[2011-05-24 11:47:02 - AndroidHTOnline] Performing testapp.test.testapp activity launch
[2011-05-24 11:47:02 - AndroidHTOnline] Automatic Target Mode: Preferred AVD 'DROID' is not available. Launching new emulator.
[2011-05-24 11:47:02 - AndroidHTOnline] Launching a new emulator with Virtual Device 'DROID'
[2011-05-24 11:47:03 - AndroidHTOnline] New emulator found: emulator-5554
[2011-05-24 11:47:03 - AndroidHTOnline] Waiting for HOME ('android.process.acore') to be launched...
[2011-05-24 11:47:26 - AndroidHTOnline] HOME is up on device 'emulator-5554'
[2011-05-24 11:47:26 - AndroidHTOnline] Uploading AndroidHTOnline.apk onto device 'emulator-5554'
[2011-05-24 11:47:26 - AndroidHTOnline] Installing AndroidHTOnline.apk...
[2011-05-24 11:47:50 - AndroidHTOnline] Success!
[2011-05-24 11:47:50 - AndroidHTOnline] Starting activity testapp.test.testapp on device emulator-5554
[2011-05-24 11:47:52 - AndroidHTOnline] ActivityManager: [1] Killed am start -n test...
Here is my manifest file. Switching target sdk seemingly has no effect.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="testapp.test"
android:versionCode="1"
android:versionName="1.0">
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="7" android:maxSdkVersion="8" />
<uses-permission android:name="android.permission.INTERNET" />
<application android:icon="#drawable/icon" android:label="#string/app_name" android:debuggable="false" android:enabled="true" android:allowBackup="false" android:allowClearUserData="true" android:testOnly="false">
<activity android:name=".testapp"
android:label="#string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
So why is the activity manager killing the app. Is there a more detailed output I can view to get more details? Is my setup for min, max and target an accurate type of setup I am looking for? I am running Eclipse on Windows. I am C# programmer and am new to Android and Java so any tips would be helpful.
Edit: I have posted the logcat log file here. http://www.strategynerd.com/log.txt I am still looking through it to attempt to find the problem, will post back if I find something.
Update: It appears the error may be occuring somewhere here in the log.
05-24 18:27:08.443: INFO/installd(35): move /data/dalvik-cache/data#app#testapp.test-1.apk#classes.dex -> /data/dalvik-cache/data#app#testapp.test-1.apk#classes.dex
05-24 18:27:08.554: DEBUG/PackageManager(59): New package installed in /data/app/testapp.test-1.apk
05-24 18:27:10.094: INFO/ActivityManager(59): Process com.android.settings (pid 119) has died.
05-24 18:27:12.094: INFO/ActivityManager(59): Force stopping package testapp.test uid=10036
05-24 18:27:12.834: INFO/WindowManager(59): WIN DEATH: Window{450470a0 com.android.launcher/com.android.launcher2.Launcher paused=false}
Is there a more detailed output I can
view to get more details?
Yes, the answer is Logcat. Open that perspective and post the log.
Is my setup for min, max and target an accurate type of setup I am looking for?
Are you sure you need a maximum version? Generally speaking most stuff developed in 7 is going to be forwards compatible. The newer screen sizes are where some run into difficulty, but that is a different issue.
You can also read about the difference between min and target version here.
Android applications are generally forward-compatible with new versions of the Android platform,
you don't need to specify the max version (it is explicitly recommended to not use the maxSdkVersion attribute).
Try to specify only the minSdkVersion attribute and see if it works.
Cheers