Can't dispatch DDM chunk error

[dWooot]

Hello,
I have just recently setup my android environment on eclipse. I am
having the following error when I try to run my helloworld program.
Here is the error:


2009-09-10 19:54:32 - testAndroid4] ActivityManager: DDM dispatch reg
wait timeout
[2009-09-10 19:54:32 - testAndroid4] ActivityManager: Can't dispatch
DDM chunk 52454151: no handler defined
[2009-09-10 19:56:16 - testAndroid4] ActivityManager: Error type 2
[2009-09-10 19:56:16 - testAndroid4] ActivityManager: Error: Unable to
connect to activity manager; is the system running?


Can someone please help me solve this ?

Thank you in advance.

[Tor]

Anyone?

I have just experienced this error too; what does it actually mean
(apart from preventing me from installing the built project)?

[2009-11-04 21:14:32 - MyApp]Android Launch!
[2009-11-04 21:14:32 - MyApp]adb is running normally.
[2009-11-04 21:14:32 - MyApp]Performing net.bogus.android.myapp.MyApp
activity launch
[2009-11-04 21:14:32 - MyApp]Automatic Target Mode: using device
'HT97KL000000'
[2009-11-04 21:14:32 - MyApp]Uploading MyApp.apk onto device
'HT97KL000000'
[2009-11-04 21:14:32 - MyApp]Installing MyApp.apk...
[2009-11-04 21:14:36 - MyApp]Success!
[2009-11-04 21:14:36 - MyApp]Starting activity
net.bogus.android.myapp.MyApp on device
[2009-11-04 21:14:40 - MyApp]ActivityManager: Can't dispatch DDM chunk
46454154: no handler defined
[2009-11-04 21:14:40 - MyApp]ActivityManager: Can't dispatch DDM chunk
4d505251: no handler defined
[2009-11-04 21:14:40 - MyApp]ActivityManager: Starting: Intent { comp=
{net.bogus.android.myapp/net.bogus.android.myapp.MyApp} }

MyApp ended up having no listing in the Applications (Settings -> ..),
and was called "net.bogus.android..." in the application list rather
than "MyApp".

I've not done anything to my Ubuntu 9.04 / Eclipse setup that I know
of. Where should I start to look?

Tor

On 11 Sep, 00:59, dWooot <devarshjo...@gmail.com> wrote:
> Hello,
> I have just recently setup my android environment on eclipse. I am
> having the following error when I try to run my helloworld program.
> Here is the error:
>
> 2009-09-10 19:54:32 - testAndroid4] ActivityManager:DDMdispatchreg
> wait timeout

> [2009-09-10 19:54:32 - testAndroid4] ActivityManager: Can'tdispatchDDMchunk 52454151: no handler defined

[Tor]

Hm, the application failing to install turned out to be due to a bad
file system. However, I'd
still like to know what the dispatch error means as I have never seen
it before (it still occurs).

Tor

[fadden]

On Nov 4, 2:56 pm, Tor <tor.hough...@gmail.com> wrote:
> Hm, the application failing to install turned out to be due to a bad
> file system. However, I'd
> still like to know what the dispatch error means as I have never seen
> it before (it still occurs).

It means DDMS is sending requests to your device that it doesn't
understand.

| Can't dispatch DDM chunk 46454154: no handler defined

If you convert that from hexadecimal to ASCII, it spells out "FEAT".
It's asking the VM what features it supports. In this case, the VM
doesn't know what a FEAT request is, so the request is rejected (and
DDMS makes appropriate assumptions).

| Can't dispatch DDM chunk 4d505251: no handler defined

MPRQ, or Method PRofiling Query. DDMS is checking to see if method
profiling is already in progress. This is also pretty new.

[pzul]

I also encountered this problem and can provide more information and a
work-around.

I type "adb install -r mumble.apk"

I get:
"
* daemon not running. starting it now *
* daemon started successfully *
308 KB/s (20130 bytes in 0.063s)

Can't dispatch DDM chunk 46454154: no handler defined

Can't dispatch DDM chunk 4d505251: no handler defined

pkg: /data/local/tmp/mumble.apk
Success
"

If I use "Debug" from eclipse, I don't see any error. I think the
install fails silently and I am actually debugging the previous
version of my application. (Confusing!)

>
> | Can't dispatchDDMchunk46454154: no handler defined

>
> If you convert that from hexadecimal to ASCII, it spells out "FEAT".
> It's asking the VM what features it supports.  In this case, the VM
> doesn't know what a FEAT request is, so the request is rejected (and
> DDMS makes appropriate assumptions).
>

But the "FEAT" request is the result of typing "adb install -r
mumble.apk" - so it doesn't seem that there should be any unknown
feature requests.

I discovered that "adb install" only fails when I have an eclipse
window (and its DDMS) open.

WORKAROUND:
exit eclipse before using "adb install".

I'm running Ubuntu 9.10.

Anyone else experiencing this?

-Paul

[fadden]

On Jan 13, 10:42 am, pzul <paul.b.wis...@gmail.com> wrote:
> But the "FEAT" request is the result of typing "adb install -r
> mumble.apk" - so it doesn't seem that there should be any unknown
> feature requests.

"adb install" pushes the APK and then essentially invokes "adb shell
pm". If you do "adb shell pm" and watch logcat, you can see log
messages from the VM startup. When it starts it becomes visible to
DDMS, and DDMS issues a few queries to figure out what it is. (If you
watch DDMS, you'll see a "?" appear briefly.)

I'm not aware of any reason why DDMS would interfere with the pm
command. Do you see anything odd in the log file when you do the
above? (You can ignore the android runtime complaints about "thread
attach failed" -- it's a thread race where somebody is trying to
attach a native thread after the VM has already decided to shut down.)

[pzul]

New theory: A colleague mentioned that this can happen when there are
two versions of adb: the one eclipse is using and the one the command
line adb is using.

[pzul]

Hi fadden, here is the output from the commands you asked for... -
Paul

$ adb shell pm

Can't dispatch DDM chunk 46454154: no handler defined
Can't dispatch DDM chunk 4d505251: no handler defined

usage: pm [list|path|install|uninstall]
----snip-----

logcat output:
D/AndroidRuntime( 999):
D/AndroidRuntime( 999): >>>>>>>>>>>>>> AndroidRuntime START
<<<<<<<<<<<<<<
D/AndroidRuntime( 999): CheckJNI is ON
D/AndroidRuntime( 999): --- registering native functions ---
I/jdwp ( 999): received file descriptor 25 from ADB
D/AndroidRuntime( 999): Shutting down VM
D/dalvikvm( 999): DestroyJavaVM waiting for non-daemon threads to
exit
D/dalvikvm( 999): DestroyJavaVM shutting VM down
D/dalvikvm( 999): HeapWorker thread shutting down
D/dalvikvm( 999): HeapWorker thread has shut down
D/jdwp ( 999): JDWP shutting down net...
D/jdwp ( 999): +++ peer disconnected
I/dalvikvm( 999): Debugger has detached; object registry had 1
entries
D/dalvikvm( 999): VM cleaning up
D/dalvikvm( 999): LinearAlloc 0x0 used 600236 of 4194304 (14%)

[patrickAR]

I used to get "Can't dispatch DDM chunk XXXX : no handler defined" and
after updating ADT (eclipse plugin, not the SDK packages) will no
longer happen, apparently there´s you need an updated plugin for newer
packages. To update ADT you must go to eclipse plugin via Help > Soft
Updates > Available Soft and browse https://dl-ssl.google.com/android/eclipse/
for updates.

HTH,
--patrickAR

[GK Gupta]

I too agree with the description "When eclipse/DDMS and another adb
instance is there then this type of error is observed". I have
observed same behaviour. With DDMS running I was getting the above
mentioned error but once I closed DDMS error was gone.

On Jan 21, 2:30 am, patrickAR <patricio.kei...@gmail.com> wrote:
> I used to get "Can't dispatch DDM chunk XXXX : no handler defined" and
> after updating ADT (eclipse plugin, not the SDK packages) will no
> longer happen, apparently there´s you need an updated plugin for newer
> packages. To update ADT you must go to eclipse plugin via Help > Soft

> Updates > Available Soft and browsehttps://dl-ssl.google.com/android/eclipse/
> for updates.
>
> HTH,
> --patrickAR