I also have the same issue where two emulator instances can't call or SMS each other like they could before (and simulated SMS or calls to them do work -- it's as if the problem is just an outbound one?). Has anyone made any progress on this? The documentation implies that it should still work, but maybe the feature has been removed? Does it work for anyone?
Thanks! On May 3, 4:02 pm, lior <liorza...@comcast.net> wrote: > I am having the same issue on Windows. It used to work before the > upgrade to1.5 > > On Apr 28, 6:01 pm, zlu <zhao.lu...@gmail.com> wrote: > > > I'm on Mac OS X. > > > On Apr 28, 4:50 pm, Raphael <r...@android.com> wrote: > > > > What operating system do you have? Linux, Mac or Windows? > > > R/ > > > > On Tue, Apr 28, 2009 at 3:16 AM, ivantipov <ivanti...@gmail.com> wrote: > > > > > Hi, > > > > I used to be able to sendSMSmessages from oneemulatorinstance to > > > > another; the reason why I didn't use Eclipse is because the app > > > > automatically replies to a certainSMSrequest, and the other device > > > > is used to receive it. > > > > > That worked fine under SDK 1.1; however, with the upgrade to1.5I get > > > > a "could not connect client socket to :::::::00001:5554: Invalid > > > > argument" error when trying to send anSMSfrom oneemulatorto > > > > another. I've created a separateAVDfor eachemulatorinstance, both > > > > Google API, and both devices are listed with the adb devices command. > > > > > Can anyone help? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
