Do I correctly understand that you've backported RFCOMM to Android 1.5? What was involved? If there were patches needed, please share!
(I'm presently using a Dell Mini running a bit of code using python- bluez as a datalogger, but keeping it charged, remembering to take it out of the bag to turn off, etc. is being a hassle; pushing that task to my ADP1 would mean that my current set of habits would work). On Jun 26, 2:24 am, Santi <[email protected]> wrote: > Hi, > i was working with last cupcake release las week and i recompiled it to > use RFCOMM API in my dev phone. i can say that status is yet unestable, > something sockets don't free resources on destroy method is invocated > and application crashes when it tried reopen it. You can see a demo > inhttp://openhealth.morfeo-project.org/ > I remember you that the API is in development process yet and i can see > that it goes to the rigth way, i hope that we can see it in android > official branche in next months :) > > Long escribió: > > > Hi, > > What is the latest status of the RFCOMM support in android? > > I'd like to write an application using RFCOMM to communicate with > > PC. I don't want to > > rebuild a custom image. I just want my application can run on a HTC > > Magic. Is that doable now? > > > I heard of there is an application bluex can transfer files with > > obex. Obex is based on RFCOMM. > > So that indicates the rfcomm should be OK. > > > But i am confused because lots of post on the list say RFCOMM is > > not ready yet. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
