I'm modifying a board game app to allow play via Bluetooth. I'm testing on a stack of devices from Samsung, Kyocera, Motorola and HTC. Consistently the HTC phone (Sensation) gets into a state where it won't accept connections (BluetoothServerSocket.accept() never returns though the logs show that ACTION_ACL_CONNECTED was received.) I'm new to BT on Android (not on Linux or PalmOS, though), so it could be my mistake, but that it works on the other devices *and* that the SDK BluetoothChat sample app also fails on the Sensation makes me suspect the phone.
There are also a lot of complaints online about HTC's Bluetooth stack.... Assuming I can't get this to work on the Sensation, I'm going to want to find a nice way to tell owners of that phone not to bother downloading. Those of you who have some experience with Android Bluetooth: how do you play nice in a world where some of your users are going to have a really bad experience with your software? Do BT- savvy users know to stay away from certain brands or models? That the problem manifests as accept() never returning means the broken device is the last to know; I can't just put up a message suggesting you uninstall. What I'm doing so far is putting up Toasts "Failed for the <n>th time to connect to device EricsSensation." When you have a table full of devices all pointing the finger at one of their number it's pretty clear, but most users have only one phone. What's the collective wisdom on this? Thanks! --Eric -- 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
