On Fri, Apr 30, 2010 at 12:41 AM, ari <das.ar...@gmail.com> wrote: > Hi Coolio, > Your input helped a lot.I had the similar kind of > issue.I have an application which has to be run from the android > shell.The requests from the application will go to my library and it > sends it to the /dev/ttyS0.I have a portlistener in the host windows > machine which will listen to the port given as emulator option . the > command is > > emulator.exe -avd androidavd -verbose -qemu -serial COM9 > > But after that there was coming to the portlistener. Then I changed by > library port options to /dev/ttyS1, but that also didnt work.After > that I changed /dev/ttyS2 than i was able to see something coming into > the portlistener. > > I want to ask coolio that how did u come to know that it will be /dev/ > ttys2?? > > Because the Android emulator already uses /dev/ttyS0 and /dev/ttyS1 in the guest system for its own usage (/dev/ttyS0 is to get kernel messages, like thoses displayed with -show-kernel, and /dev/ttyS1 is to implement the "qemud" multiplexing daemon, an internal implementation detail you should not care about).
So when you do -qemu -serial COM9, it really means "allocate the next available emulated serial port device and connect it to the host COM9", hence the /dev/ttyS2 > Please let me know a about your findings. > > On Jan 23 2009, 5:20 am, coolio <justinca...@gmail.com> wrote: > > Thanks, > > > > What is the default configuration for /dev/ttyS2 and what is the > > command to change the configuration? > > > > Justin > > > > On Jan 22, 1:51 pm, David Turner <di...@android.com> wrote: > > > > > if you're using the -qemu -serial <device> option when starting the > > > emulator, it will probably be mapped to /dev/ttyS2 or ttyS3 within the > > > emulator. > > > > > that's because the emulator uses a couple of serial ports for its own > needs: > > > one is to get kernel messages, and the other for the "qemud" > multiplexing > > > daemon which manages a communication channel between the emulator > program > > > and various Android sub-systems (e.g. the GSM stack, the GPS support, > > > etc...) > > > > > you can use emulator -verbose to see which -serial <dev> are inserted > before > > > yours when starting the emulator, if that can help > > > > > On Thu, Jan 22, 2009 at 11:52 AM, coolio <justinca...@gmail.com> > wrote: > > > > > > Hi, > > > > > > I run SDK's emulator and opened /dev/ttyS0, when I write to that > > > > device , it didn't show up in host's serial port. Does anybody konw > > > > what /dev/ttyS0 in emulator is mapped to? Is there any possibility > > > > that I can map emulator's /dev/ttyS0 to /dev/ttyS0 of the linux host > > > > that is running emulator. If I add a serial port on linux host, can I > > > > add/map the serial port to emulator? > > > > > > Thanks- Hide quoted text - > > > > > - Show quoted text - > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
