I may be doing some Bluetooth Serial Port programming work for a client and I'm just looking for some tips in determining complexity/ workload. The work is similar to reading from a bluetooth GPS (not making the phone a bluetooth GPS), but it is some custom hardware, so not exact.
Here's what (I think) I know so far: I will need to pair devices with a Serial Port Profile. I need to connect using a BluetoothSocket which works on Android 2x -I don't know yet if the Android I will be a server or a client in this scenario. I will open an InputStream (no outputstream needed) and have a thread continually blocking for input I believe "BluetoothChat" is the best example to start with. What I would want to know. - Are there devices/manufacturers who block the bluetooth serial port, trying to block tethering or something like that? (-I've seen posts here that imply that, but I don't see a bunch of comments like "Doesn't work on my @#$$" in Bluetooth GPS Providers in the market). -Are there going to be hardware specific oddities, or can I develop with my Nexus One and just hope it works on everything else? -Is pairing something that will require a lot of education for the users, and would a good app try to initiate this inside their app, or just assume it is already done. -Is Bluetooth programming going to be my worst nightmare, like it sometimes was on Windows Mobile, or smoother than I could ever hope? Thanks Nathan -- 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
