LinkBack URL
About LinkBacks
Reply With QuoteIs the contacts support being handled by and implementation of the Phonebook Access Profile (PBAP) or just a proprietary method over OBEX?
Yep, have one for you. We have finished initial testing, and are almost ready to put the release out on the forums. We are waiting on some 3rd party vendors to implement some crucial items for us, and once that is completed we integrate it into the new release, and then it's time to get it out to all of you. Our estimate to have this done will be sometime next week, probably toward the latter end of it, but there are no promises because at this moment it is in the hands of a 3rd party to get these last few details done. Stay tuned though, it's almost there.Originally Posted by Nola111
Is the contacts support being handled by and implementation of the Phonebook Access Profile (PBAP) or just a proprietary method over OBEX?
Wouldn't it have to be PBAP? Otherwise there would have to be software installed on the phone to deal with the proprietary protocol and that would limit the number of compatible phones even further.
In this initial release of Centrafuse with bluetooth, we will only support handsfree and headset profile, to integrate calling features of your bt phone. Phonebook support is not there yet, although it will be in the future. With support for Phoco ending, the new actual phone integration in CF began only 6 weeks ago. Phonebook support will follow, no worries!!
It would be best if it was PBAP, but it has been implemented in OBEX for some time. PBAP is a fairly recent thing in the history of Bluetooth.
Remember, the Bluetooth profiles can be considered just application templates, so it certainly can be done other ways, it just may not interoperate very well, which is why I am asking. Everyone can interpret the spec differently, and possibly use different stack API to get the job done. The good thing about supporting the profiles is that everyone follows the same template (ie. profile API) thus ensuring interoperability.
<expels a massive puff of air as he unloops the noose from his neck and steps down from the chair> . . .there may be hope after all . . .
PDP1170/TRS80/Atari800XL/Amiga500/286/486/P2/P4/C2D still a newb (but an old newb, been doing this a while) working my way up to "Complete Newb"
from fluxmedia site:The new phone utility will include all software necessary to locate and use your usb bluetooth device. No extra drivers will need to be searched for, and although we do not have a list of specific bluetooth dongles that are supported, there are a WIDE range of them that are. The only dongle that I believe will not work are Broadcomm based, which require firmware upload on init from what I remember. If anyone is looking for a recommendation, I am using DLink DBT-120 for most of the testing, and it has been flawless.
waiting for updates on the Bluetooth stack to add support for the Broadcom chip, doing most of our current testing with CSR chips...
installer is built and it's being tested internally more than other releases... it will be a nice release... I here from the stack company on Friday, hoping to get the update then... we then have to test, etc... it will be coming soon... hang on...
I'm&&
..... Does it support broadcom or doesn't it?
Is the new phone software out yet? Or am I supposed to be monitoring another thread? Thx.
PDP1170/TRS80/Atari800XL/Amiga500/286/486/P2/P4/C2D still a newb (but an old newb, been doing this a while) working my way up to "Complete Newb"
Not out yet, and no mention from Flux folks as to the status. Sucks.
oh come on peeps...
it will be released when its done!!
stop the nagging...
Posting Permissions
Bookmarks