I think I've come up with a pretty good interim solution (until nfc) to the adhoc comm issue, using qr codes and bt spp. It looks like it's going to require lots of fine-tuning for individual devices though, which just sucks.
I've tried a number of different approaches, including bonjour over wifi, which worked surprisingly well, but the dependence on wifi was just a bit too goofy, so the only choice left is bt. making the experience truly seamless for my users has been surprisingly difficult -- this use case is not well thought out at all by Google, particularly how pairing works. I'm hoping for some guidance from someone there on how to make that work well, but I'm not holding my breath. I'm going to post the code for connecting two peers via bt spp comm using qr codes if I can get it to work well enough. If it all comes together it will be a nice stop-gap until nfc is everywhere, which will be a while... On May 27, 3:32 am, Zsolt Vasvari <[email protected]> wrote: > I've never owned a device where Bluetooth "just works" every time. > The closest that one came to has been my Garmin GPS. > > I do hope NFC will make it easier to do adhoc peer-to-peer > communications. > > On May 27, 9:58 am, keyeslabs <[email protected]> wrote: > > > > > > > > > I'm trying to use bluetooth SPP to establish a socket connection > > between two Android devices. There are a few things that are really > > driving me crazy in this effort. > > > First, the Galaxy Tab seems to just be broken when it comes to SPP. I > > can establish the connection just fine, but after a few minutes, and > > most notably whenever the app on the Tab on which the SPP server > > socket was established is killed, the tablet effectively locks up, > > requiring a hard reboot (hold down the power for 7 seconds to > > reboot). I've seen others mentioning the same thing in various > > places, but haven't seen any solutions. Has anyone come up with > > ANYTHING to solve this issue? > > > Second, I've been struggling to find a way to make it easy for users > > to pair devices. I'm developing a full-screen game involving two > > devices, and the pairing request on 2.3 and later seems to happen > > (sometimes) as a notification, which doesn't do much good for a full > > screen game. In some cases it does seem to be displayed as a dialog > > (which is what I want), but it's frequently as a notification. Is > > anyone aware of a reliable way to initiate pairing via DIALOG > > automatically when a socket is opened between two unpaired devices? > > > Finally, has anyone else noticed pairing requests happening twice? > > Dialog shows, user clicks pair, second dialog appears, click pair, > > pairing happens. > > > Thanks for any help! -- 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
