It makes sense, though right? I mean, all it's doing is serial port emulation...
I'm not sure how it works in code, so that could be completely off, but I had thought RFCOMM was serial port emulation, so it makes sense that if you're reading data from the serial port you end up messing with the port. I guess my question, if someone already has /dev/ttys* you don't get an error in trying to open it in your code. http://www.slideshare.net/erinyueh/android-bluetooth-introduction <http://www.slideshare.net/erinyueh/android-bluetooth-introduction>Anyway, yeah, you probably want to avoid messing with serial stuff when you're doing Bluetooth stuff. What use did you have for the using that, anyway? (Just curious.) Kris On Thu, Mar 31, 2011 at 11:02 AM, John <[email protected]> wrote: > I don't need help porting Android to different hardware. I am using > JNI to read the serial ports, and the sdk to open a bluetooth > connection. > This is a device that is already running Android. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" 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-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
