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

Re: Leopard oddity in naming device types
by Garth Cummings 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.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.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard oddity in naming device types
by Ralf Menssen 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: Bluetooth-dev(a)lists.apple.com User-agent: Thunderbird 1.5.0.10 (Macintosh/20070221) Roman Pixell schrieb: > > On 2 apr 2007, at 18.44, Garth Cummings wrote: > >> Hi Thomas, >> >> On Apr 2, 2007, at 5:32 AM, Thomas Tempelmann wrote: >> >>> Playing with 9A377a, >> >> Which is under NDA and not appropriate to discuss on public mailing >> lists. Sorry. >> >> --gc > > > the thought has crossed my mind before, but are we not all under NDA? > i thought this list was for ADC members only. > Just google: "Roman Pixell" Bluetooth and look what happens... -- ======================================= Ralf Menssen _______________________________________________ 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 Mihnea Galca 03 Apr '07

03 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 Marco, Thank you for the response. I will not be able to attend WWDC. Can I get in touch (by mail) with the Mac OS SCO expert ? 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 > Hello Mihnea, > > For each channel (RFCOMM or L2CAP) there can be only one client, so > in general if the SCO driver is using the channel you can not use the > same channel. > So if you want to use the default SCO driver you can not read the > button pressed. If you want to manage your own SCO connection there > is an API in IOBluetoothUserLib.h > called IOBluetoothAddSCOAudioDevice and > IOBluetoothRemoveSCOAudioDevice, in this case the audio is handled > for you but you need to handle the RFCOMM > channel (so volume and button clicks) more info at http:// > developer.apple.com/documentation/DeviceDrivers/Reference/IOBluetooth/ > IOBluetoothUserLib/CompositePage.html#//apple_ref/c/func/ > IOBluetoothAddSCOAudioDevice > You need to know in deep how the MacOS X audio system works to use > that API. > > I am not the SCO expert, but he will be at WWDC if you have some > specific questions. > > > On Mar 27, 2007, at 4:47 AM, Mihnea Galca wrote: > >> Everything in this message is related to latest Mac OS. >> >> 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 ? >> >> 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/mpontil% >> 40apple.com >> >> This email sent to mpontil(a)apple.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.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: More details on OBEX FTP trouble - solved
by Thomas Tempelmann 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Thread-index: Acd10GO4omqjwuHDEduc5gARJHK4jA== Thread-topic: More details on OBEX FTP trouble - solved User-agent: Microsoft-Entourage/11.3.3.061214 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"? 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". 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.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard oddity in naming device types
by Roman Pixell 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com On 2 apr 2007, at 18.44, Garth Cummings wrote: Hi Thomas, On Apr 2, 2007, at 5:32 AM, Thomas Tempelmann wrote: the thought has crossed my mind before, but are we not all under NDA? i thought this list was for ADC members only. / ® _______________________________________________ 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.… Playing with 9A377a, Which is under NDA and not appropriate to discuss on public mailing lists. Sorry. --gc This email sent to site_archiver(a)lists.apple.com

1 0

Re: rfcomm mtu
by Daniel Birns 03 Apr '07

03 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:in-reply-to:mime-version:content-type:references; b=HO2qzmZF3sl5NLpCWBaEtb56pJS1YrSl+djFIT/oJUo+689jKaDoTSVKQZDk6njVlIPWAO30eZ8F3CI9px1hz3kh/XkmY/T6YM5IaBgZvmpkYLTmOWrbyNfKhJ37hULfiPIKr8q+4k4eYBueBuzq7rVfQuWPVXYes+Imu1goCyk= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Fm8pVjgtgl4KTuGVcV9x0/YXlnOisxwTnkSSKNHY5LvXmr7xicaaghQLSaBxsKNM+LLom1VWUUZzJ89PqjmO8W7rmfVe1Y8n8H4qo3v5+hiKdU47Yg8Pm9+QkBXUvUdVFygJOhYhHv2teDm3ZPVI269OTwhqGUYrE6AjY8Tai/0= _______________________________________________ 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 mtu
by Marco Pontil 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com .. Marco On Apr 2, 2007, at 4:50 PM, Daniel Birns wrote: Fellow Bluetoothers, Thanks. _______________________________________________ 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.… The RFCOMM Mtu defaults to 1500-something bytes, if you get 128 it is probably because the device you are talking to is requiring a smaller MTU. I'm using Carbon and RFCOMM, and the GetMTU() call is telling me that my mtu is 128 bytes, and in fact the WriteAsync() call fails when I write more than that, and succeeds when I write less, as advertised. This seems like a very small MTU. Is there some way to make it bigger? --Daniel _______________________________________________ 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/mpontil% 40apple.com This email sent to mpontil(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: rfcomm mtu
by Joseph Kelly 03 Apr '07

03 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Joseph K. On Apr 2, 2007, at 4:50 PM, Daniel Birns wrote: Fellow Bluetoothers, Thanks. --Daniel _______________________________________________ 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/joeman%40mac.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.… I'm not sure where the MTU gets set -- whether it's in the spec or is determined by the particular interface, etc? Either way, my code breaks up its outgoing packets into MTU sized chunks and I've had no problem at all with writing to my device on many different Macs with many different bluetooth interfaces. I'm using Carbon and RFCOMM, and the GetMTU() call is telling me that my mtu is 128 bytes, and in fact the WriteAsync() call fails when I write more than that, and succeeds when I write less, as advertised. This seems like a very small MTU. Is there some way to make it bigger? This email sent to joeman(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

rfcomm mtu
by Daniel Birns 02 Apr '07

02 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=o2kmDBEd7bYRuHgDY8+/eE5o2x8R9lrPxgSbFG/QYF6b49Gs69F+jWn7xhKcNHS3v1EyxVMMqjUW09iwSDJH6bV9mJ2uw+9gq/9rul9Cj2Jd5TK8dGFkJ6MAFUX1koAdngG0wsZaeNxNTTGQhTXy/OLOH0nudLUbb604E9dW04w= 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=AO86RTvoynPwVwVp5CzPwB9WMtFqMeGGDBjJzeBx/9nym+wLv+KaybA8syBnWtfcJMHe8+DU0nvJQZbPnVMz4Qb0dTGjCESJggd0vPKKfV4IObLHuyB43oew4xozsjXYUtmR6sww4XjXaH0R6+JMUM4uDzGv3ULGZkDis1Z+TaQ= _______________________________________________ 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: What is "Bluetooth Audio Gateway"?
by Marco Pontil 02 Apr '07

02 Apr '07

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com ... Marco On Apr 2, 2007, at 11:30 AM, Thomas Tempelmann wrote: On 2.4.2007 18:21 Uhr, "Marco Pontil" <mpontil(a)apple.com> wrote: You must have setup an headset on that mac, that service is published once you setup a headset to allow the headset to connect back. 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.… Sorry, misunderstand: I meant a Bluetooth headset (like this: http:// www.thetravelinsider.info/roadwarriorcontent/images/btheadset.jpg ). To make things clearer: there are 2 services involed with BT headsets: 1] on the headset ( http://www.thetravelinsider.info/ roadwarriorcontent/images/btheadset.jpg ) the "Headset" service 2] on the phone (or the mac) the Audio Gateway. In this way either side can connect to the other (the headset looks for the audio gateway, and the audio gateway looks for a headset). Other macs and the nokia phone do not see the service because they are them-self audio gateways. (audio gateways do not look for audio gateways). Indeed. I have a USB headset connected. So, this feature is provided by Apple then? Kind of a easter egg, it appears :) Yet, if that's the case, why can neither my Nokia N80 nor my other Macs use that service? BTW, has that feature been introduced in 10.4.4 perhaps? (I wonder if that's the thing that Zach Rosen's BPE2 builds upon) _______________________________________________ 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/mpontil% 40apple.com This email sent to mpontil(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0