Bump....   Has anyone had this problem before?

Thanks in advance for any help you can provide!



On Sep 2, 7:52 am, dfournier74 <[EMAIL PROTECTED]> wrote:
> I believe I am having some issues with the ADB communicating to my
> emulator instance.  It appears that the adb does not reckognize the
> instance of the emulator when running.
>
> My Laptop Configuration:
>
> OS:                   Vista Ultimate edition
> Processor:         Intel(R) Core(TM) 2 CPU    T7200 @ 2.ooGHz
> Memory:            4 GB
> System Type:    32-bit
>
> My steps to start the adb and emulator, plus logging for each...  (I
> have tried to start emulator first and also adb first and still get
> the same results.  For the logs below, I have started the emulator
> first...
>
> 1)  Start Emulator in verbose:
>
> C:\Users\dfournie>emulator -verbose
> emulator: autoconfig: -system F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_bet
> a\tools/lib/images/
> emulator: autoconfig: -datadir C:\Users\dfournie\AppData\Local\Android
> emulator: autoconfig: -kernel F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_bet
> a\tools/lib/images/\kernel-qemu
> emulator: autoconfig: -ramdisk F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_be
> ta\tools/lib/images/\ramdisk.img
> emulator: autoconfig: -image F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_beta
> \tools/lib/images/\system.img
> emulator: autoconfig: -initdata F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_b
> eta\tools/lib/images/\userdata.img
> emulator: autoconfig: -skindir F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_be
> ta\tools/lib/images/\skins
> emulator: autoconfig: -sdcard C:\Users\dfournie\AppData\Local\Android
> \sdcard.img
>
> emulator: autoconfig: -data C:\Users\dfournie\AppData\Local\Android
> \userdata.img
>
> emulator: autoconfig: -data C:\Users\dfournie\AppData\Local\Android
> \userdata-qem
> u.img
> emulator: parsing built-in skin layout file (size=7714)
> emulator: skin network speed: 'full'
> emulator: skin network delay: 'none'
> emulator: argv[00] = "emulator"
> emulator: argv[01] = "-kernel"
> emulator: argv[02] = "F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_beta\tools/
> lib/images/\kernel-qemu"
> emulator: argv[03] = "-initrd"
> emulator: argv[04] = "F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_beta\tools/
> lib/images/\ramdisk.img"
> emulator: argv[05] = "-nand"
> emulator: argv[06] = "system,size=0x4200000,initfile=F:\Shared\appsDev
> \Java\andr
> oid-sdk-windows-0.9_beta\tools/lib/images/\system.img"
> emulator: argv[07] = "-nand"
> emulator: argv[08] = "userdata,size=0x4200000,file=C:\Users\dfournie
> \AppData\Loc
> al\Android\userdata-qemu.img"
> emulator: argv[09] = "-nand"
> emulator: argv[10] = "cache,size=0x4200000"
> emulator: argv[11] = "-serial"
> emulator: argv[12] = "android-kmsg"
> emulator: argv[13] = "-serial"
> emulator: argv[14] = "android-qemud"
> emulator: argv[15] = "-append"
> emulator: argv[16] = "qemu=1 console=ttyS0 android.checkjni=1
> android.qemud=ttyS
> 1 android.ndns=3"
> emulator: mapping 'system' NAND image to C:\Users\dfournie\AppData
> \Local\Temp\\A
> ndroidEmulator\TMPDDDD.tmp
> emulator: mapping 'cache' NAND image to C:\Users\dfournie\AppData\Local
> \Temp\\An
> droidEmulator\TMPDF35.tmp
> emulator: using 'dynticks' alarm timer
> emulator: using 'winaudio' audio input backend
> emulator: using 'winaudio' audio output backend
> emulator: warning: opening audio input failed
>
> emulator: control console listening on port 5554, ADB on port 5555
> emulator: can't connect to ADB server: errno 10061: connection refused
> emulator: ping program: F:\Shared\appsDev\Java\android-sdk-
> windows-0.9_beta\tool
> s\ddms.bat
> emulator: ping command: C:\Windows\system32\cmd.exe /C "F:\Shared
> \appsDev\Java\a
> ndroid-sdk-windows-0.9_beta\tools\ddms.bat" ping emulator 1.5
>
> 2)  Start ADB using Trace set to All:
>
> C:\Users\dfournie>SET ADB_TRACE=all
>
> C:\Users\dfournie>adb start-server
> _adb_connect: host:version
> socket_loopback_client: could not connect to tcp:5037
> * daemon not running. starting it now *
> * daemon started successfully *
>
> 3)  Check to see if ADB reckognizes emulator:
>
> C:\Users\dfournie>adb devices
> adb_query: host:devices
> _adb_connect: host:version
> socket_loopback_client: port 5037 type tcp => fd 100
> writex: 100 0022CB50 4: 30303063  000c
> writex: 100 ok
> writex: 100 0041E311 12: 686f73743a76657273696f6e  host:version
> writex: 100 ok
> readx: 100 0022CAB0 4
>
> At this point the command prompt returns nothing and just sits
> there...  I do not get the "No devices" found or devices listed.
>
> Can someone let me know what else I can do to figure out why this is
> not working?
>
> Thank you,
>
> Derek

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to