Will there be any support to create insecure rfcomm?
What device(s) are you experiencing the problem on?
What firmware version are you running on the device?
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Original issue reported on code.google.com by bkt...@gmail.com on 22 Oct 2012 at 5:57
Original issue reported on code.google.com by
bkt...@gmail.comon 22 Oct 2012 at 5:57