Hi, I find the Galaxy S2 quite problematic with bluetooth as well, often needing to stop & start bluetooth in order to get it to device to connect. I found it is more reliable using the undocumented method you mentioned as well as using the insecure versions of the same method calls and that this seems to work ok on all the devices I have tested with - GS2, Nexus 1, Nexus S, Xperia Arc, LG 2x, HTC Evo 3D & Motorola Xoom.
As far as what the diferences are it is best if you read through the Android source code. Regards On Nov 18, 5:07 am, John <john_ri...@live.com> wrote: > Our app uses a bluetooth connection and has been working fine for > about a year. On a new Samsung G S2 phone we are seeing a problem > connection the socket. The error is 'Service discovery failed'. > > Now we've seen this on HTC phones, and the solution was to include a > call to createRfcommSocket, if the call to > createRfcommSocketToServiceRecord failed. But the same code isn't > working on this Samsung. > > So I am thinking that maybe by forcing the call to createRfcommSocket > we can get this to work. > > However I cannot find any information about what createRfcommSocket is > doing, differently than createRfcommSocketToServiceRecord. Is there > any information on what that call does? > > Are there any other ideas on how to resolve this issue that doesn't > include using an undocumented call? > > Thanks. -- 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
