[android-developers] Re: Bluetooth and Serial Port Profile
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 manfred.spell...@gmail.com 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 npe...@google.com 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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
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 npe...@google.com 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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
Nick Pelly wrote: 2009/5/20 moa mich...@jixel.com: What is the process for it becoming available on real devices? If an SDK update is released that supports SPP or RFCOMM. Does that mean applications compiled on that SDK will run on current cupcake devices (like the Magic) without any new firmware on the phone? Or once new BT support is added to the SDK does that mean new firmware on the phone to be compatible? New firmware would be required. For the record: Early access to such a firmware would be *MUCH* appreciated. Our installments often have several months lead time, so being able to show a working prototype long before it being officially available could make a lot of decision makers very happy to go the Android route rather than the more typical Nokia route for the whole installation. Best / Jonas --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
Jonas Petersson wrote: For the record: Early access to such a firmware would be *MUCH* appreciated. Code changes of the sort you are seeking should show up in http://source.android.com. Your bigger challenge is in knowing when the feature is sufficiently done that it is worthwhile testing out. Since you are seeking Bluetooth, and the emulator does not emulate Bluetooth AFAIK, you would be needing the source code anyway in order to create a firmware image for your prototype hardware device. Or, wait until an official shipping Android has those capabilities. For example, if somebody contributed patches now, they could presumably be included in Android 2.0 (or whatever the next major release winds up being called). BTW, discussion about the source code itself is best held in a discussion list pertaining to the source code: http://source.android.com/discuss -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 0.95 Available! --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
What is the process for it becoming available on real devices? If an SDK update is released that supports SPP or RFCOMM. Does that mean applications compiled on that SDK will run on current cupcake devices (like the Magic) without any new firmware on the phone? Or once new BT support is added to the SDK does that mean new firmware on the phone to be compatible? On May 19, 11:14 am, Ahn mhahn0...@gmail.com wrote: Hi Nick, Could you update the current status on your RfcommSocket.java? I really wanna use BT/RFCOMM. BT --Ahn On 5월13일, 오후3시19분, Nick Pelly npe...@google.com 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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
2009/5/20 moa mich...@jixel.com: What is the process for it becoming available on real devices? If an SDK update is released that supports SPP or RFCOMM. Does that mean applications compiled on that SDK will run on current cupcake devices (like the Magic) without any new firmware on the phone? Or once new BT support is added to the SDK does that mean new firmware on the phone to be compatible? New firmware would be required. On May 19, 11:14 am, Ahn mhahn0...@gmail.com wrote: Hi Nick, Could you update the current status on your RfcommSocket.java? I really wanna use BT/RFCOMM. BT --Ahn On 5월13일, 오후3시19분, Nick Pelly npe...@google.com 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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
Hi Nick, Could you update the current status on your RfcommSocket.java? I really wanna use BT/RFCOMM. BT --Ahn On 5월13일, 오후3시19분, Nick Pelly npe...@google.com 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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
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 ho...@helloandroid.com 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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
On May 13, 9:19 am, Nick Pelly npe...@google.com 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. That is very good news. I am trying to work with the current version of RfcommSocket but it fails when calling create() with Operation not permitted. I started the adb shell and started the application as root but I get the same error. Any idea what can I do about this? E/bluetooth_RfcommSocket.cpp( 1094): createNative: Could not create RFCOMM socket: Operation not permitted W/System.err( 1094): java.io.IOException: socket not created W/System.err( 1094):at android.bluetooth.RfcommSocket.create (RfcommSocket.java:168) W/System.err( 1094):at ro.clawoo.rfcommtest.RfcommTest.onCreate (RfcommTest.java:17) W/System.err( 1094):at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java: 1123) W/System.err( 1094):at android.app.ActivityThread.performLaunchActivity(ActivityThread.java: 2231) W/System.err( 1094):at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java: 2284) W/System.err( 1094):at android.app.ActivityThread.access$1800 (ActivityThread.java:112) W/System.err( 1094):at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1692) W/System.err( 1094):at android.os.Handler.dispatchMessage (Handler.java:99) W/System.err( 1094):at android.os.Looper.loop(Looper.java:123) W/System.err( 1094):at android.app.ActivityThread.main (ActivityThread.java:3948) W/System.err( 1094):at java.lang.reflect.Method.invokeNative(Native Method) W/System.err( 1094):at java.lang.reflect.Method.invoke(Method.java: 521) W/System.err( 1094):at com.android.internal.os.ZygoteInit $MethodAndArgsCaller.run(ZygoteInit.java:782) W/System.err( 1094):at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:540) W/System.err( 1094):at dalvik.system.NativeStart.main(Native Method) 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
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 alin.claudiu.ra...@gmail.com wrote: On May 12, 7:00 am, Zach Hobbs ho...@helloandroid.com 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
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. -Zach On May 11, 1:57 pm, Alin Radut alin.claudiu.ra...@gmail.com wrote: On May 3, 10:46 am, Nick Pelly npe...@google.com wrote: Thanks. RfcommSocket is hidden in the 1.5r1 SDK, is there any way I can access it without compiling my own version of the framework? No I see. I built both the system images and the SDK after following the instructions fromhttp://source.android.com/documentation/building-for-dream andhttp://source.android.com/projects/bluetooth-faqbut there is no sign of RfcommSocket in the output files. I am still trying to wrap my head around the way the building process works but to little success so far. I assume the RfcommSocket file is being omitted from the building process but I can't find where. How would I go about building a version of Android and the SDK that would allow me to interact with RFCOMM? 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 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
On Saturday, May 2, 2009, Alin Radut alin.claudiu.ra...@gmail.com wrote: On Apr 22, 3:09 am, Nick Pelly npe...@google.com wrote: RfcommSocket.java is what you want. SPP is just rfcomm. Thanks. RfcommSocket is hidden in the 1.5r1 SDK, is there any way I can access it without compiling my own version of the framework? No Alin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
Thanks. RfcommSocket is hidden in the 1.5r1 SDK, is there any way I can access it without compiling my own version of the framework? No Not even using reflection? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[android-developers] Re: Bluetooth and Serial Port Profile
On Apr 22, 3:09 am, Nick Pelly npe...@google.com wrote: RfcommSocket.java is what you want. SPP is just rfcomm. Thanks. RfcommSocket is hidden in the 1.5r1 SDK, is there any way I can access it without compiling my own version of the framework? Alin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
