i have some question which are as follows
so when the serial port server profile  will be ported ??
can we customize bluecove api & use it on android ??

On Sep 11, 2:59 pm, Stefano Sanna <[email protected]> wrote:
> On Fri, Sep 11, 2009 at 6:57 AM, windstorm <[email protected]> wrote:
>
> > Hi Stefano, thanks for your great effort!
>
> Thank you.
>
> > Right now I am trying to use your library on a ongoing student
> > project, and here is some basic questions about it
>
> > 1 The discoverable attribute on Android will be automatically turned
> > off in 120 seconds, is there any api or way to avoid this? What I
> > really want is to connect my phone by my device, then send data from
> > the device to phone, not from my phone to my device, so I would prefer
> > to let the phone to be always discoverable.
>
> I'll check and let you know.
>
> > 2 I don't know if it's rude but, based on what you did the
> > implementation? I checked the source code and saw "import
> > android.bluetooth.**", but I didn't see this package in android.jar
> > under my sdk. Then how did you do it?
>
> Using Java reflection, I've found that the BluetoothDevice class
> exposes the following method:
>
> public boolean 
> getRemoteServiceChannel(java.lang.String,short,android.bluetooth.IBluetoothDeviceCallback)
>
> to get asynchronously the RFCOMM assigned to a certain service. To get
> the response, I had to find the definition of
> IBluetoothDeviceCallback. Therefore, I had a look to the Android's
> source code to (hopefully!) find what I needed; finally I used the
> AIDL definition of BluetoothDeviceCallback to generate the
> IBluetoothDeviceCallback in my library source tree.
>
> Much more critical was to find the reference to BluetoothSocket; in
> fact, it was org.bluez.RfcommSocket on early SDK release and
> android.bluetooth.BluetoothSocket on latest source repository. None of
> them was available using reflection. Finally, checking some possible
> name, I've found the current firmware use old class name with new
> package name (that is: android.bluetooth.RfcommSocket).
>
> > 3 Did you ever notice and consider merge all the function provided
> > here:
>
> >http://groups.google.com/group/android-platform/browse_thread/thread/...
>
> > Or you have noticed this?
>
> I didn't read this post, thank you for hint. Since I was not aware of
> that discussion, I've written my (simple) API from scratch, trying to
> keep them very simple. Do you think it would be better to align the
> library to that proposals? Is that the direction that will be taken by
> Google?
>
> > BTW: one question to all, I saw this sdk from sybase:
>
> >http://www.sybase.com/detail?id=1064424
>
> > Anyone tried it before?
>
> Do you know if there is any trial/demo of it?
>
> Regards,
> Stefano.
>
> --
> Stefano Sanna
> [email protected] (Skype: gerdavax)
>
> Personal blog:http://www.gerdavax.it
> Linkedin profile:http://www.linkedin.com/in/gerdavax
> QuadraSpace Project:http://www.quadraspace.org

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to