Hi, Is there a firmware I can put on my phone that has SPP available for testing yet?
I've got one the the work in progress ION builds from xda-developers on my Magic just now. Is this any help? On May 29, 9:36 pm, Nick Pelly <[email protected]> wrote: > Hi Manny, > > Sounds like your socket was not getting closed properly. > > There is some discussion of a new interface BluetoothSocket.java on > android-platform. An implementation will soon be available in the open > source tree. > > Nick > > On Wed, May 27, 2009 at 5:14 AM, Manny <[email protected]> wrote: > > > Hello, > > > I am looking forward using the Bluetooth API. > > > For now I am sticking with RfcommSocket.java. > > > I have removed the @hide and recompiled the SDK. > > With the new android.jar I can use RfcommSocket now. > > > I use a Developer Phone with the standard 1.5. > > Can I use the standard firmware with RfcommSocket > > or do I need a new image as well ? > > > For now I have some serious problems. > > > create and connectAsync on a channel work only one time, > > every second time I get the Log-Message > > "05-27 12:08:46.183: ERROR/bluetooth_RfcommSocket.cpp(13416): RFCOMM > > async connect error (25): Device or resource busy (16)" > > I use shutdown and destroy to correctly cleaning the socket, but next > > time I start the app I get this message, > > I can only use a new channel then it works one time. In this case I > > get the Log-message > > 05-27 13:15:54.333: INFO/bluetooth_RfcommSocket.cpp(13485): RFCOMM > > async connect is in progress (Operation now in progress) > > > The next problem is that I get this Log-Message when I make a flush on > > the OutputStream. > > 05-27 13:29:44.633: WARN/System.err(13580): java.io.IOException: > > Transport endpoint is not connected > > This message comes independently if the socket is connected or not. > > > What I want to do is connecting the Developer Phone with the Bluetooth > > receiver on my notebook, > > sending data and receiving it on the Notebook on a Com-Port maybe with > > HyperTerminal for Test purpose > > (In real world a different Hardware is used instead). > > Bluetooth on the Notebook uses Com4 and 5 for SPP. > > > The Notebook finds the G1 Dev Phone, but as profile for it only A2DP > > is listed. > > > The G1 Dev Phone finds the Notebook after scanning, Pairing but not > > connected is stated for this. > > > Any idea how I can get this working ? > > For now with unhide RfcommSocket ? or do I have to wait for your > > Bluetooth API ? > > Do I need a new image for this ? > > > Since we have to present our customer a draft version in aboout 2 > > weeks > > there is a little pressure on this for us. > > > So in general can we get that working with the actual possibilities > > of the SDK and the Dev-Phone or do we have to wait, > > on a later version of SDK, with your Bluetooth API, > > or a different Hardware. > > > Hopefully you can help me > > > I am looking forward to any answers > > > Manny > > > On 13 Mai, 08:19, Nick Pelly <[email protected]> wrote: > > > Just a quick heads up. I'm almost complete on reworking RfcommSocket.java > > to > > > improve its interface, fix a number of bugs, and eventually make it a > > public > > > API. I will soon post on android-platform once its ready for more eyes. > > > > Cheers, > > > Nick > > > > On Tue, May 12, 2009 at 11:01 AM, Zach Hobbs <[email protected]> > > wrote: > > > > > Another note: > > > > > You don't really have to flash the image with the @hide gone, that > > > > class will be accessible by any APK. You just need to have it visible > > > > in your development environment. > > > > > -Zach > > > > > On May 12, 1:05 pm, Alin Radut <[email protected]> wrote: > > > > > On May 12, 7:00 am, Zach Hobbs <[email protected]> wrote: > > > > > > > Did you change anything when you built the SDK? If not, then the > > > > > > classes will still not be visible. > > > > > > > Hint: classes or methods with "@hide" in the comment block above > > the > > > > > > code are not visible in the jar built for the SDK. > > > > > > I removed the @hide from RfcommSocket.java and after a lengthy 4 hour > > > > > compile now it shows up in the .jar file. > > > > > > The problem is that after I flashed the device with the img files I > > > > > can't access the Wireless controls screen because it crashes. It > > > > > appears that there is a problem with the bluetooth A2DP service. The > > > > > adb logcat output is available here:http://clawoo.ro/pub/logcat.txt > > > > > and the traces.txt file is available here: > > > >http://clawoo.ro/pub/traces.txt > > > > > > The problem is that I cannot enable the bluetooth service if I cannot > > > > > access that screen so I cannot test if I can interact with RFCOMM as > > I > > > > > need. Do anyone have any idea why the wireless controls screen > > > > > crashes and what can I do about it? > > > > > > Thanks, > > > > > Alin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
