Closed GoogleCodeExporter closed 8 years ago
I still can't figure out how to fix this, could someone reproduce this, or just
me?
Original comment by EHo...@gmail.com
on 5 Jun 2009 at 2:34
Ehotou,
I couldn't reproduce this. I setup two new 1.5 emulators, sent one text from
emulator 5556 to 5554 without problem. Then on emulater 5554 did Omnidroid ->
Run
Tests -> App COnfig/User Config to load in the default rules and OmniHandler.
Then
on 5556 sent a text to 5554. It sent, and got my original message back.
Try disabling any firewall you might have running.
--
Drew
Original comment by case.and...@gmail.com
on 5 Jun 2009 at 8:54
Hi, I tried to turn firewall down, and still not working. I am working on Mac
OS X,
leopard platform. Anyone else has the same problem?
Original comment by EHo...@gmail.com
on 8 Jun 2009 at 3:34
I am having this issue on a Windows Vista and a Windows 7 computer, but not on a
Windows XP computer.
I don't have any restrictive firewall settings that I know of.
Original comment by londinop
on 8 Jun 2009 at 3:51
The socket formatting reminds me of IPv6. Are you running IPv4 and IPv6 on
these
machines? If so, try disabling IPv6 and just using IPv4 to see if that could
be an
issue.
Original comment by case.and...@gmail.com
on 8 Jun 2009 at 4:01
Hi, I had the same problem. Turning off the IPv6 works. I am using windows
vista.
This link has information on how to turn off IPv6.
http://www.mydigitallife.info/2007/09/09/disable-and-turn-off-ipv6-support-in-vi
sta/
I tried disabling IPv6 with the registry method and it worked.
Original comment by rutvi...@gmail.com
on 8 Jun 2009 at 7:34
Excellent. Yeah, I just read the last post on this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/5c8d0f279
cae1ae6/c7982a81f0375ad7?lnk=gst&q=sms++emulator+1.5#c7982a81f0375ad7
they say:
"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."
This therefore isn't an OmniDroid bug (marking invalid).
Until the next android release with fix, testing will have to be done with IPv6
turned off.
Original comment by case.and...@gmail.com
on 8 Jun 2009 at 7:53
Original issue reported on code.google.com by
EHo...@gmail.com
on 4 Jun 2009 at 1:57