[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
I am using SDK 1.5 Ubuntu 9.04 I tried disabling ipv6 on localhost by using sysctl (sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1 and also tried sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1). But to no use. Can someone please clarify, what I might be missing? Regards Sam On Jul 9, 8:44 pm, babo babo.onl...@gmail.com wrote: On OSX 10.5 use this command to disable IPv6 for loopback interface: sudo ip6 -d lo0 /Attila --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
I am using SDK 1.5 Ubuntu 9.04 I tried disabling ipv6 on localhost by using sysctl (sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1 and also tried sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1). But to no use. Can someone please clarify, what I might be missing? Regards Sam On Jul 9, 8:44 pm, babo babo.onl...@gmail.com wrote: On OSX 10.5 use this command to disable IPv6 for loopback interface: sudo ip6 -d lo0 /Attila --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
On OSX 10.5 use this command to disable IPv6 for loopback interface: sudo ip6 -d lo0 /Attila --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
hi I have tried by disabling IPv6 from network connection but still it don't work and show me error: could not connect to client socket to 1:5556: unknown error On May 25, 3:18 am, David Turner di...@android.com wrote: On Sun, May 24, 2009 at 6:17 PM, Steve steveoliv...@gmail.com wrote: Not working for me either, running a Mac with SDK 1.5. I wonder if the new AVD's have somehow broken the port numbers, and since you have to run each emulator against a separate AVD, now the 2 emulators can't see each other. Argh! No, the issue is related to IPv6 and a bug in the emulator's name resolution code. A fix will be available in the next release. In the meantime, you could try disabling IPv6 on your localhost interface and see if it helps. (Yes, I know it's gruesome, sorry). On May 13, 1:59 pm, Laurie mamla...@gmail.com wrote: Same for me. With the 1.5 SDK toolkit, I cannot send or receiveSMS/ Calls using TWO EMULATOR INSTANCES on the same development machine. **Simulating incoming calls andSMSmessages using the emulator console via telnet works fine. Using DDMS in Eclipse works fine. I am using Windows Vista, using distinct AVDs, both the Dialer/ Messaging applications and port numbers (eg. 5554 and 5556). I have tried both launching both emulator instances through Eclipse, as well as one with Eclipse and one from the command line. Neither method works. These features worked fine in Android 1.1. I hope we get an answer to this query soon. -LED --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
On Sun, May 24, 2009 at 6:17 PM, Steve steveoliv...@gmail.com wrote: Not working for me either, running a Mac with SDK 1.5. I wonder if the new AVD's have somehow broken the port numbers, and since you have to run each emulator against a separate AVD, now the 2 emulators can't see each other. Argh! No, the issue is related to IPv6 and a bug in the emulator's name resolution code. A fix will be available in the next release. In the meantime, you could try disabling IPv6 on your localhost interface and see if it helps. (Yes, I know it's gruesome, sorry). On May 13, 1:59 pm, Laurie mamla...@gmail.com wrote: Same for me. With the 1.5 SDK toolkit, I cannot send or receiveSMS/ Calls using TWO EMULATOR INSTANCES on the same development machine. **Simulating incoming calls andSMSmessages using the emulator console via telnet works fine. Using DDMS in Eclipse works fine. I am using Windows Vista, using distinct AVDs, both the Dialer/ Messaging applications and port numbers (eg. 5554 and 5556). I have tried both launching both emulator instances through Eclipse, as well as one with Eclipse and one from the command line. Neither method works. These features worked fine in Android 1.1. I hope we get an answer to this query soon. -LED --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
Not working for me either, running a Mac with SDK 1.5. I wonder if the new AVD's have somehow broken the port numbers, and since you have to run each emulator against a separate AVD, now the 2 emulators can't see each other. Argh! On May 13, 1:59 pm, Laurie mamla...@gmail.com wrote: Same for me. With the 1.5 SDK toolkit, I cannot send or receiveSMS/ Calls using TWO EMULATOR INSTANCES on the same development machine. **Simulating incoming calls andSMSmessages using the emulator console via telnet works fine. Using DDMS in Eclipse works fine. I am using Windows Vista, using distinct AVDs, both the Dialer/ Messaging applications and port numbers (eg. 5554 and 5556). I have tried both launching both emulator instances through Eclipse, as well as one with Eclipse and one from the command line. Neither method works. These features worked fine in Android 1.1. I hope we get an answer to this query soon. -LED --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
Same for me. With the 1.5 SDK toolkit, I cannot send or receive SMS/ Calls using TWO EMULATOR INSTANCES on the same development machine. **Simulating incoming calls and SMS messages using the emulator console via telnet works fine. Using DDMS in Eclipse works fine. I am using Windows Vista, using distinct AVDs, both the Dialer/ Messaging applications and port numbers (eg. 5554 and 5556). I have tried both launching both emulator instances through Eclipse, as well as one with Eclipse and one from the command line. Neither method works. These features worked fine in Android 1.1. I hope we get an answer to this query soon. -LED --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
I couldn't find an open issue for this, so I opened a new one: http://code.google.com/p/android/issues/detail?id=2660 On May 12, 6:33 pm, lilbyrdie kf6...@gmail.com wrote: I also have the same issue where twoemulatorinstances can't call orSMSeach other like they could before (and simulatedSMSor 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 :::1: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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
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 :::1: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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
I am having the same issue on Windows. It used to work before the upgrade to 1.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 one emulator instance 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 to 1.5 I get a could not connect client socket to :::1:5554: Invalid argument error when trying to send anSMSfrom one emulator to another. I've created a separateAVDfor each emulator instance, 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
http://developer.android.com/guide/developing/tools/emulator.html#connecting On Apr 28, 3:16 am, ivantipov ivanti...@gmail.com wrote: Hi, I used to be able to send SMS messages from one emulator instance to another; the reason why I didn't use Eclipse is because the app automatically replies to a certain SMS request, and the other device is used to receive it. That worked fine under SDK 1.1; however, with the upgrade to 1.5 I get a could not connect client socket to :::1:5554: Invalid argument error when trying to send an SMS from one emulator to another. I've created a separate AVD for each emulator instance, 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
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 send SMS messages from one emulator instance to another; the reason why I didn't use Eclipse is because the app automatically replies to a certain SMS request, and the other device is used to receive it. That worked fine under SDK 1.1; however, with the upgrade to 1.5 I get a could not connect client socket to :::1:5554: Invalid argument error when trying to send an SMS from one emulator to another. I've created a separate AVD for each emulator instance, 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 -~--~~~~--~~--~--~---
[android-developers] Re: SDK 1.5: unable to send SMS to another emulator
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 send SMS messages from one emulator instance to another; the reason why I didn't use Eclipse is because the app automatically replies to a certain SMS request, and the other device is used to receive it. That worked fine under SDK 1.1; however, with the upgrade to 1.5 I get a could not connect client socket to :::1:5554: Invalid argument error when trying to send an SMS from one emulator to another. I've created a separate AVD for each emulator instance, 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 -~--~~~~--~~--~--~---
