April 2007 - Bluetooth-dev - lists.apple.com

btNotificationDeviceTerminated?
by Daniel Birns 26 Apr '07

26 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=oG890iLWqltr9gOe0FlTxK58X57hUxd/x4s7kpu2XCV3tyvM3NqQa6L55TDHDL6tW895PbtY+F/3TW/mKL42ROwZMzV64DJCyfAKIXmW/WirPQHzVIRSPQPoag2OANsc6at+0llhsaXwcMJdrWoiNiK5rKRVMVlrhQiHCVvMqac= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=q/j8+SHq9EgB5pjvInTuL/kEj5WkUWHyDB6hWanR0no26qSOdssJsyMFQWgFJ1/xvoB3ufTfC70puDklRmQEb3UrkSwhkqGTW428Fw3zq93S+Bim3dnktZFRtlcHYPAW1seCI9ghqRWMeM0UThOqrB31cNDxWAo82yF1Ihoa4Ks= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: RFCOMM + SCO connection
by Harel M. Williams 19 Apr '07

19 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KtIXQWJHc4naHNW3iR1lxacgMVSY8lBL8/qVhu2M1zUTSWw78rOeMJ/u1NkIhD7Cz4LvB5k0pBx1jq7dmXfF9BVTsKGEuLzwLDpedOPs+jKSD0Pvxde6l8fRNUodDB92b7wrZFs2yuss2c6NDDR0uPuBhInkyNWf1KGJbpkkWcs= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=hxEsfa1iIaPkIr51NGtjTVg9EjS/L7KIQdnuis9vGfN5IgMXKRdfjek1ejeNtaEfdmCabGzuLa82ZDKyh2j3vluAcDQhlLuMkqzL9FCCPV7wRVw+NopXKUiy4M/UJ+qBcWgPFpGWN9/VyGAQyugyzAXUPfZTctwE/INY/tua2DA= Hi Mihnea, It is definitely possible, and even necessary to have an RFCOMM connection established in order for the SCO connection to be established. I think what you are missing are the initialization steps that you need to send across RFCOMM as well as advertising the 'Audio Gateway'. You should refer to the Bluetooth Headset Profile Spec to figure that out. First, make sure you are advertising the 'Audio Gateway' profile on your Mac (there is a plist for this service available somewhere in /Developer/Examples/Bluetooth/...). An RFCOMM channel will be assigned to this service, and you will have to make sure to communicate over that specific channel. The headset should automatically communicate with this channel because it is specified in the advertised service. Second, the headset must be paired with the Mac. You can do this through the Bluetooth Setup Assistant. It is nearly impossible to do this programatically because the APIs for HCI aren't public. (On a semi-related note, if you use Parallels to load up your favorite variant of Linux, you can access the HCI layers using BlueZ, so I am guessing that the developers of Parallels were granted access to these "Private" APIs. If I am correct, that doesn't seem very fair. Do Apple Engineers really want us using AppleScript to take care of pairing, for example, programatically?) Third, you must establish the RFCOMM connection. The headset will send a bunch of AT commands over the link and you must respond as indicated in the headset profile. Once you have responded correctly, audio will be sent across the SCO link. The difficult part here is getting a handle on the Audio data from the Audio Device created by IOBluetoothAddSCOAudioDevice. As Marco mentioned earlier on the bluetooth-dev list, you have to do a bunch of CoreAudio gymnastics. But, before you delve into this, just go into Audio System Preferences, and see if the meter on the SCO Audio Device Output is moving as you scream into your Bluetooth headset :) There may be a simpler way to get to the audio, but only certain special people get access to the SCO Bluetooth Classes.... Hopefully that'll get you started. I intend on writing a guide on how to do all of this, step by step, sometime soon. Also, I feel your pain. I have struggled with similar issues, with very few hints from the bluetooth-dev list. Apple Engineers, is there a reason that on this specific issue you have been relatively silent as far back as I can tell according to the archives? It seems to me that everyone who has figured out this problem has used a technical incident and then say they can't help because they are under NDA. I don't get it...and not all of us can (afford to) attend the WDC. -Harel Hello, Is it possible to have a rfcomm connection with a bluetooth headset on top of which to start/stop SCO connection ? Usage scenario: a RFCOMM connection has to be maintained to a bluetooth headset to get button press events, but in the same time, SCO is activated to play/record sounds using the headset. So far, I could make a RFCOMM connection to capture button press events, but I couldn't start SCO in any way. SCO seems connected to a system audio device which connects/disconnects the headset when needed. I couldn't find any method to control SCO from API. How can I solve the problem in the above given scenario ? Do I need to develop my own SCO layer over RFCOMM and create a new audio device driver ? Any pointers to do such a thing ? I've tried IOBluetoothAddSCOAudioDevice, but it's a deprecated function and the only thing it does, is to create the associated audio device, if such a device is not already present. My code is the following: void* keys[1]; keys[0]=[[NSString alloc] initWithCString:"IOAudioControls"]; void* values[1]; id array=[[NSMutableArray alloc] init]; values[0]=array; CFDictionaryRef dictionary=CFDictionaryCreate(NULL,keys,values,1, &kCFTypeDictionaryKeyCallBacks,&kCFTypeDictionaryValueCallBacks); IOReturn res=IOBluetoothAddSCOAudioDevice(m_headset,dictionary); The operation was successful in the case when the audio device didn't exist. In the case when the device existed (created using bluetooth interface in the OS), the function returned a general error. Regards, Mihnea GALCA _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/harelw%40gmail.com This email sent to harelw(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… On 4/19/07, Mihnea Galca <mgalca(a)tremend.ro> wrote: This email sent to site_archiver(a)lists.apple.com

1 0

RFCOMM + SCO connection
by Mihnea Galca 19 Apr '07

19 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Importance: Normal User-agent: SquirrelMail/1.4.7-4.fc4 Hello, Is it possible to have a rfcomm connection with a bluetooth headset on top of which to start/stop SCO connection ? Usage scenario: a RFCOMM connection has to be maintained to a bluetooth headset to get button press events, but in the same time, SCO is activated to play/record sounds using the headset. So far, I could make a RFCOMM connection to capture button press events, but I couldn't start SCO in any way. SCO seems connected to a system audio device which connects/disconnects the headset when needed. I couldn't find any method to control SCO from API. How can I solve the problem in the above given scenario ? Do I need to develop my own SCO layer over RFCOMM and create a new audio device driver ? Any pointers to do such a thing ? I've tried IOBluetoothAddSCOAudioDevice, but it's a deprecated function and the only thing it does, is to create the associated audio device, if such a device is not already present. My code is the following: void* keys[1]; keys[0]=[[NSString alloc] initWithCString:"IOAudioControls"]; void* values[1]; id array=[[NSMutableArray alloc] init]; values[0]=array; CFDictionaryRef dictionary=CFDictionaryCreate(NULL,keys,values,1, &kCFTypeDictionaryKeyCallBacks,&kCFTypeDictionaryValueCallBacks); IOReturn res=IOBluetoothAddSCOAudioDevice(m_headset,dictionary); The operation was successful in the case when the audio device didn't exist. In the case when the device existed (created using bluetooth interface in the OS), the function returned a general error. Regards, Mihnea GALCA _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: problem with IOBluetoothRegisterForFilteredRFCOMMChannelOpenNotifications()
by Daniel Birns 17 Apr '07

17 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PhHA4HaX7oGWIB7GrBsImLSTMoYHRXuZeH8CgZWAKD4rx5+2VoqIZnlzpla9qXPO0rz7im+6VbatC3aoy0ogl+lSGhVYyr9In+cmAHSPTKAx34Q1vOel7LML2rzDEfbVWJ54pKe5nklOSt4F95Wr2w99yaEu94u/UbJ+2x7WZoc= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=EEpfThMJzYAdTy2JW4L3cW/++bW1Oha4VnspJUSe6bzRgxKHqQTZYM5KttQvYfEoBOE74T2/T9eNovuWPcDA15q67hOsOCjQXAKRP5wIBVav1Hmo/P3JKlB2oUNWM0nrzfzgBVC+iJQSwPUzYB6P9W8p7VxogLSKIfs1H6T6IZ8= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

problem with IOBluetoothRegisterForFilteredRFCOMMChannelOpenNotifications()
by Daniel Birns 17 Apr '07

17 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; b=iIDU1KmY+xUKT9HE8f4sEZ3GdMhAWFpU3VGbZsjOb4t5LUkgv1km7/1nzuPEaZTzR15ayKI+IhEQeMBJUKL5ySu3Ywrdy671AXP/wAgZxWCeJkYyYAQHlr4vFM88EmEaqO1cUukil81SfOSleYVXjNdZWk3ZMX4jPfsPmcB762I= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=fX+dxhNqlt/pyt3GmroJwxTP3HznlGSUbLNI9uobtxOnQdEWKpyph1J2WGYdXuF3sI17RJDcd4Z9WkX5BYMMXFn5A5SE8xvZ519+zPFX68ou8IXCRHP8/tR6CIe4yEovw0UCBE5XAFZLsweos1sF4w+mag0Zf5gJb73v6pw9pdE= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Resource Busy
by Ross Barkman 14 Apr '07

14 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Kia ora, Ross _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… Probably more an end-user question than a dev one, but: users of my scripts frequently get a "Resource busy" message in their Internet Connect logs when using Bluetooth. I know the obvious suspects for tying up the serial port service (Address Book, various sync apps), but sometimes it is very difficult to determine which process has made the port busy. Is there any quick method to determine the PID or name of the process that 'owns' the port? This email sent to site_archiver(a)lists.apple.com

1 0

Bluetooth carbon mysteries resolved
by Daniel Birns 09 Apr '07

09 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=mzWaBn5mphHkFnoto+QEXOqbsIHvjptnEC/DbODvd+FTWqozhaNvL3fhA6xUCOAvvaTMdmdC3DqbidkiHpUsA0uhBDG6FWWI3r9+70b+drZ/HtuOYt0Xl+3fHxUpb8XzAvfUu0EUEwsU1wuUDJudAe0bWmm9CsCrtoOvZUf6NeY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=e/T8HnI/xkpUolHqlaywG3dfzaRfBkqKxqLwLBCkWONYcynH1BZxHNRIykE8Yen3vqdvJ7pNlsbsBUGChUbES2J2FIdOoFsLwh51AkBJ+3OLuzOUt2IcyFXgPHhrHtwNXSGRMGtof/7wXiGK+hpkNoQWb0gyjZ7dEiMDAktz4hk= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Results from the SDP binary string issues
by Thomas Tempelmann 05 Apr '07

05 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Thread-index: Acd3jXrwuahEVeOAEdut5wARJHK4jA== Thread-topic: Results from the SDP binary string issues User-agent: Microsoft-Entourage/11.3.3.061214 I have finally been able to analyse the issues I had brought up here a few days ago. I have summarized the results here: http://www.tempel.org/CreatingSDPEntriesWithBinaryDataInOSX My thanks go to the helpful folks from the BT team at Apple, who helped clarifying them. Thomas _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Something wrong with my Bluetooth Service plist
by Daniel Birns 04 Apr '07

04 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; b=Bowlfj49aGfDc0RUhRITttp33LEWunZvFuC9xuNo0Ah4JwSQP6SBcT40rZlyE4d02TvyxgrBDUIyyGBL3sY9uF0hza5+tc3IhB4TeCO+9zM1e/V0TF0HQgn9tHSynnt81XhB6LaSIzjwmWmNBTd1ttZ33m9pjwIfTtW40DmEFZs= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=S/cBsh+nPPnl4hRfVzksZZ47PoqNbg/JOjLdttl7vqdgFlM8oeYSqKO76pBa6X3VzcuO2NRfQ3tT0TESofvnfOT2NtmNB/r+u5UhXO9mopX6Z4tN3YJFteynQT1MDsJVSxkw0qnadJghTvcg6NmD1iCxgOwnUZzhCMKjXSn1AB4= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: More details on OBEX FTP trouble - solved
by Bubba Giles 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com jason On Apr 3, 2007, at 2:13 AM, Thomas Tempelmann wrote: On 3.4.2007 2:09 Uhr, "Bubba Giles" <bubba(a)apple.com> wrote: OBEXSample was not supposed to be an FTP client, which is why it doesn't work that way. It is supposed to be an OPP sample only. Are you sure you're not confusing the sample "OBEXSample" with "OBEXSampleSendVCard"? Really confused, Thomas _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… Actually, now that I reflect on it more, OBEXSample was written to show how to use Apple's OBEX API. Thus, it implements most of the commands in the OBEX spec, not those specifically found in a Bluetooth profile such as OPP or FTP. It was not really meant as a way to show you how to fully implement a proper FTP client, or an OPP client. Not to mention it was written years ago, when OBEX was first implemented on the stack (that is not an excuse just a reality). Besides, the developer samples are provided a starting point, not the end-all be-all of how to do something (which is why there is a gigantic disclaimer at the top). We'll try to fix the erroneous setpath flag. Or why does "OBEXSample" have an implementation and UI for setting a Path? I thought OPP does not provide SETPATH, only FTP does? (i.e. searching for "path" in the OPP 1.1 spec does not find anything) And the implementation of the SETPATH function is still using the wrong flag no matter what. Furthermore, while the GET method provides for receiving the default vCard as doc'd in the OPP spec, it _also_ allows to retrieve arbritrary files, which is a feature of FTP, not OPP, as far as I understand. Please clarify. So my conclusion remains: The sample does not obey the Spec, and should be fixed therefore (as reported in bug #5095147). Or, at least, _document_ its purpose. If it's really meant to show how OPP works, then please write that down there. Refer to the specs, for instance. Or, name it "OPPSample", not "OBEXSample". This email sent to site_archiver(a)lists.apple.com

1 0