September 2009 - Bluetooth-dev

Re: How to release or disable SCO audio connection
by Peter Sichel 30 Sep '09

30 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com On Sep 28, 2009, at 9:30 PM, Peter Sichel wrote: - Peter _______________________________________________ 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 found IOBluetoothRemoveSCOAudioDevice(), but this function has been deprecated and is no longer available as of 10.6 . The lack of documentation is perhaps more serious than I thought. I found two previous postings in which people have asked about a replacement for IOBluetoothRemoveSCOAudioDevice(), but there was no response. This email sent to site_archiver(a)lists.apple.com

1 0

How to release or disable SCO audio connection
by Peter Sichel 29 Sep '09

29 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com I'm trying to figure out how to disable this audio connection. Can anyone point me in the right direction? Thanks, - Peter _______________________________________________ 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.… My application (Phone Amego) connects with a Bluetooth phone using the Handsfree Profile for the purpose of CallerID and dialing. I've noticed some phones establish an audio connection with the Mac by default such that the speaker and microphone on the phone itself is disabled. P.S. I've spent a little time searching, but so far am finding dead ends. - The Official Handsfree Profile spec does a nice hand wave by saying some external or user initiated event causes the audio connection to release. - The Headset Profile spec shows a picture of sending "AT+CKPD" to establish an SCO connection or release it, but there are no other details. - Other documents hint at advertising an audio gateway profile and accepting an SCO connection. I found IOBluetoothRemoveSCOAudioDevice (), but this function has been deprecated and is no longer available as of 10.6 . This email sent to site_archiver(a)lists.apple.com

1 0

Panic in Bluetooth stack on 10.6.1 ?
by Peter Sichel 24 Sep '09

24 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com - Peter Sichel Sustainable Softworks Interval Since Last Panic Report: 85739 sec Panics Since Last Report: 1 Anonymous UUID: B64A9BB5-DA2E-44B3-B1C0-4384330FD83A BSD process name corresponding to current thread: PhoneAmego Mac OS version: 10B504 I received a curious report today I'd love some help to make sense of. It's my application Phone Amego that's using Bluetooth, but causing a kernel panic from user land is quite an accomplishment. I'm familiar with debugging my own NKEs, but I'm less sure about debugging one of Apple's since I have no access to the underlying sources, or a debug version of the kext itself. Any ideas? Tue Sep 22 20:15:48 2009 panic(cpu 0 caller 0xffffff80002cbf74): Kernel trap at 0xffffff7f80c9957a, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff800cb680b0, CR3: 0x000000005f1ea000, CR4: 0x0000000000000660 RAX: 0x00000000000000fe, RBX: 0xffffff800ca50e00, RCX: 0x00000000a11f0000, RDX: 0x00000000e00002bc RSP: 0xffffff8083af29a0, RBP: 0xffffff8083af29c0, RSI: 0x00000000000000fe, RDI: 0xffffff800cb67800 R8: 0x0000000000000008, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0xffffff80004fc3b6 R12: 0xffffff800cb67800, R13: 0x00000000000000fe, R14: 0x00000000000000fe, R15: 0xffffff8083af2ac8 RFL: 0x0000000000010246, RIP: 0xffffff7f80c9957a, CS: 0x0000000000000008, SS: 0x0000000000000000 Error code: 0x0000000000000002 Backtrace (CPU 0), Frame : Return Address 0xffffff8083af2640 : 0xffffff8000204ae6 0xffffff8083af2740 : 0xffffff80002cbf74 0xffffff8083af2890 : 0xffffff80002ddd4a 0xffffff8083af28a0 : 0xffffff7f80c9957a 0xffffff8083af29c0 : 0xffffff7f80c99fa5 0xffffff8083af2a10 : 0xffffff80005313ec 0xffffff8083af2a80 : 0xffffff7f80c991b5 0xffffff8083af2ab0 : 0xffffff7f80c9ac2c 0xffffff8083af2af0 : 0xffffff800054850b 0xffffff8083af2b70 : 0xffffff80005487ea 0xffffff8083af2be0 : 0xffffff8000548f69 0xffffff8083af2d30 : 0xffffff80002b5f61 0xffffff8083af3dd0 : 0xffffff8000205306 0xffffff8083af3e00 : 0xffffff8000202961 0xffffff8083af3e60 : 0xffffff8000270ee2 0xffffff8083af3ed0 : 0xffffff80002be9f2 0xffffff8083af3fa0 : 0xffffff80002de326 Kernel Extensions in backtrace (with dependencies): com.apple.iokit.IOBluetoothFamily(2.2.1f7) @0xffffff7f80c73000->0xffffff7f80cb2fff Kernel version: Darwin Kernel Version 10.0.0: Fri Jul 31 22:46:25 PDT 2009; root:xnu-1456.1.25~1/RELEASE_X86_64 System model name: MacBookPro5,2 (Mac-F2268EC8) System uptime in nanoseconds: 15391438688021 unloaded kexts: com.apple.iokit.IOFireWireSBP2 4.0.5 (addr 0xffffff7f81549000, size 0x73728) - last unloaded 6666770535240 loaded kexts: com.rogueamoeba.hermes 2.0 com.AmbrosiaSW.AudioSupport 3 com.apple.filesystems.afpfs 9.5 com.apple.nke.asp_tcp 5.0 com.apple.driver.AppleHWSensor 1.9.2d0 com.apple.filesystems.autofs 2.1.0 com.apple.driver.AGPM 100.8.15 com.apple.driver.AppleMikeyHIDDriver 1.1.7 com.apple.driver.AppleHDA 1.7.4a1 com.apple.driver.AppleMikeyDriver 1.7.4a1 com.apple.driver.AppleIRController 161 com.apple.driver.SMCMotionSensor 3.0.0d4 com.apple.driver.AppleUpstreamUserClient 3.0.5 com.apple.driver.NVSMU 1.1.7 com.apple.driver.AppleLPC 1.4.6 com.apple.Dont_Steal_Mac_OS_X 7.0.0 com.apple.driver.AudioIPCDriver 1.1.0 com.apple.driver.AppleIntelPenrynProfile 17 com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a20 com.apple.kext.AppleSMCLMU 1.4.5d1 com.apple.GeForce 6.0.2 com.apple.driver.AppleGraphicsControl 2.8.16 com.apple.driver.AppleUSBTCButtons 1.8.0b4 com.apple.driver.AppleUSBTCKeyboard 1.8.0b4 com.apple.iokit.SCSITaskUserClient 2.5.1 com.apple.BootCache 31 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1 com.apple.driver.AppleEFINVRAM 1.3.0 com.apple.driver.AppleSmartBatteryManager 160.0.0 com.apple.driver.AppleFWOHCI 4.3.4 com.apple.driver.AirPortBrcm43xx 410.91.20 com.apple.driver.AppleUSBHub 3.7.8 com.apple.driver.AppleUSBOHCI 3.7.5 com.apple.iokit.IOAHCIBlockStorage 1.5.0 com.apple.driver.AppleHPET 1.4 com.apple.driver.AppleAHCIPort 2.0.0 com.apple.driver.AppleUSBEHCI 3.7.5 com.apple.driver.AppleRTC 1.3 com.apple.nvenet 1.0.58 com.apple.driver.AppleACPIButtons 1.3 com.apple.driver.AppleSMBIOS 1.4 com.apple.driver.AppleACPIEC 1.3 com.apple.driver.AppleAPIC 1.4 com.apple.security.sandbox 0 com.apple.security.quarantine 0 com.apple.nke.applicationfirewall 2.0.11 com.apple.driver.AppleIntelCPUPowerManagementClient 90.0.0 com.apple.driver.AppleIntelCPUPowerManagement 90.0.0 com.apple.driver.AppleBluetoothHIDMouse 1.3.0f1 - last loaded 362668746641 com.apple.driver.AppleHIDMouse 1.3.0f1 com.apple.driver.IOBluetoothHIDDriver 2.2.1f7 com.apple.driver.AppleProfileReadCounterAction 17 com.apple.driver.AppleProfileTimestampAction 10 com.apple.driver.AppleProfileThreadInfoAction 14 com.apple.driver.AppleProfileRegisterStateAction 10 com.apple.driver.AppleProfileKEventAction 10 com.apple.driver.AppleProfileCallstackAction 20 com.apple.driver.DspFuncLib 1.7.4a1 com.apple.driver.AppleSMBusController 1.0.2d0 com.apple.iokit.IOFireWireIP 2.0.3 com.apple.iokit.IOSurface 73.0 com.apple.iokit.IOBluetoothSerialManager 2.2.1f7 com.apple.iokit.IOSerialFamily 10.0.2 com.apple.iokit.IOAudioFamily 1.7.0fc16 com.apple.kext.OSvKernDSPLib 1.3 com.apple.driver.AppleHDAController 1.7.4a1 com.apple.iokit.IOHDAFamily 1.7.4a1 com.apple.iokit.AppleProfileFamily 40 com.apple.driver.IOPlatformPluginFamily 3.4.0a20 com.apple.driver.AppleSMBusPCI 1.0.2d0 com.apple.driver.AppleSMC 3.0.1d2 com.apple.nvidia.nv50hal 6.0.2 com.apple.NVDAResman 6.0.2 com.apple.iokit.IONDRVSupport 2.0 com.apple.iokit.IOGraphicsFamily 2.0 com.apple.driver.AppleUSBMultitouch 200.20 com.apple.iokit.IOUSBHIDDriver 3.7.5 com.apple.driver.AppleUSBBluetoothHCIController 2.2.1f7 com.apple.iokit.IOBluetoothFamily 2.2.1f7 com.apple.driver.AppleUSBMergeNub 3.7.5 com.apple.driver.AppleUSBComposite 3.7.5 com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.5.1 com.apple.iokit.IOBDStorageFamily 1.6 com.apple.iokit.IODVDStorageFamily 1.6 com.apple.iokit.IOCDStorageFamily 1.6 com.apple.driver.XsanFilter 402.1 com.apple.iokit.IOAHCISerialATAPI 1.2.0 com.apple.iokit.IOSCSIArchitectureModelFamily 2.5.1 com.apple.iokit.IOFireWireFamily 4.1.7 com.apple.iokit.IO80211Family 300.20 com.apple.iokit.IOUSBUserClient 3.7.5 com.apple.driver.AppleEFIRuntime 1.3.0 com.apple.iokit.IOAHCIFamily 2.0.0 com.apple.iokit.IOUSBFamily 3.7.8 com.apple.iokit.IONetworkingFamily 1.8 com.apple.iokit.IOHIDFamily 1.6.0 com.apple.iokit.IOSMBusFamily 1.1 com.apple.kext.AppleMatch 1.0.0d1 com.apple.security.TMSafetyNet 6 com.apple.driver.DiskImages 281 com.apple.iokit.IOStorageFamily 1.6 com.apple.driver.AppleACPIPlatform 1.3 com.apple.iokit.IOPCIFamily 2.6 com.apple.iokit.IOACPIFamily 1.3.0 Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.42f4 Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB Memory Module: global_name AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.91.19) Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports Network Service: AirPort, AirPort, en1 Serial ATA Device: ST9500420ASG, 465.76 GB Serial ATA Device: MATSHITADVD-R UJ-868 USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000 USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0x04600000 USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000 USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8217, 0x06110000 _______________________________________________ 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: IOBluetoothRFCOMMChannel and memory management
by Peter Sichel 24 Sep '09

24 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com On Sep 24, 2009, at 6:21 AM, Hugh Cole-Baker wrote: - Peter _______________________________________________ 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 am writing an application that communicates using an RFCOMM channel to a mobile phone. I use the openRFCOMMChannelAsync:withChannelID:delegate: method of IOBluetooth device to open the channel. The docs for this method state "The RFCOMM channel object is already retained when this function returns success; the channel must be released when the caller is done with it" so I don't retain the object from my code while using it. Apple's sample code (RFCOMM_Open_SPP_Example) does retain the rfcomm channel object upon a successful return from - [openRFCOMMChannelAsync:withChannelID:delegate], so I suspect the documentation is outdated. This email sent to site_archiver(a)lists.apple.com

1 0

IOBluetoothRFCOMMChannel and memory management
by Hugh Cole-Baker 24 Sep '09

24 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Thanks, Hugh -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ 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 am writing an application that communicates using an RFCOMM channel to a mobile phone. I use the openRFCOMMChannelAsync:withChannelID:delegate: method of IOBluetooth device to open the channel. The docs for this method state "The RFCOMM channel object is already retained when this function returns success; the channel must be released when the caller is done with it" so I don't retain the object from my code while using it. After using it I set the channel delegate to nil, close the channel and release the IOBluetoothRFCOMMChannel object, but this causes the app to crash later when a message is sent to the already-deallocated channel object: 2009-09-24 11:16:30.817 bluetooth[9845:a0f] *** - [IOBluetoothRFCOMMChannel retain]: message sent to deallocated instance 0x163f7e40 (gdb) bt #0 0x90510d27 in ___forwarding___ () #1 0x90510bf2 in __forwarding_prep_0___ () #2 0x9256ddc9 in objc_getProperty () #3 0x930181c4 in -[NotificationInfo object] () #4 0x93018a38 in btNotificationRFCOMMChannelTerminated () #5 0x93a26d40 in IODispatchCalloutFromCFMessage () #6 0x904d8df2 in __CFMachPortPerform () #7 0x904d8b8e in __CFRunLoopDoSource1 () #8 0x904d49e9 in __CFRunLoopRun () #9 0x904d2d34 in CFRunLoopRunSpecific () #10 0x904d2b61 in CFRunLoopRunInMode () #11 0x960e2fec in RunCurrentEventLoopInMode () #12 0x960e2da3 in ReceiveNextEventCommon () #13 0x960e2c28 in BlockUntilNextEventMatchingListInMode () #14 0x95714c95 in _DPSNextEvent () #15 0x9571450a in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #16 0x956d669b in -[NSApplication run] () #17 0x956ce735 in NSApplicationMain () #18 0x000023b1 in ?? () More worryingly, if the user closes the baseband connection (e.g. by using the Bluetooth menu item's "Disconnect" option) the IOBluetoothRFCOMMChannel object will be deallocated without my app knowing about it. It looks like it is actually necessary to retain the object I get from openRFCOMMChannelAsync:withChannelID:delegate: while it is being used, somewhat contrary to what the documentation says. Can anyone clarify if this is the right thing to do in this case? This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to unregister a device delegate
by Craig Dooley 16 Sep '09

16 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com [_rfcommChannel setDelegate:nil]; On Sep 16, 2009, at 8:12 AM, Peter Sichel wrote: More specifically, if you open a channel to a device using: The caller becomes the delegate per the last parameter. When you later close the device using: [_rfcommChannel closeChannel] and [_bluetoothDevice closeConnection] Is there a better way? - Peter _______________________________________________ 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/cdooley%40apple.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 using Apple's RFComm sample code and have noticed that in Snow Leopard closing a Bluetooth device has become asynchronous. ioResult = [device openRFCOMMChannelAsync:&_rfcommChannel withChannelID:rfcommChannelID delegate:self]; If you then release the caller, your program will crash when the device object tries to call the previously registered delegate some arbitrary time later. There has to be some way to unregister a device delegate so you can be sure the device object will not attempt to call you after your delegate object has gone away. The existing sample code and framework headers fail to document this so I'm trying to figure out how to unregister my delegate. An ugly work around is to never release a delegate until your program quits. This email sent to cdooley(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

How to unregister a device delegate
by Peter Sichel 16 Sep '09

16 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com More specifically, if you open a channel to a device using: The caller becomes the delegate per the last parameter. When you later close the device using: [_rfcommChannel closeChannel] and [_bluetoothDevice closeConnection] Is there a better way? - Peter _______________________________________________ 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 using Apple's RFComm sample code and have noticed that in Snow Leopard closing a Bluetooth device has become asynchronous. ioResult = [device openRFCOMMChannelAsync:&_rfcommChannel withChannelID:rfcommChannelID delegate:self]; If you then release the caller, your program will crash when the device object tries to call the previously registered delegate some arbitrary time later. There has to be some way to unregister a device delegate so you can be sure the device object will not attempt to call you after your delegate object has gone away. The existing sample code and framework headers fail to document this so I'm trying to figure out how to unregister my delegate. An ugly work around is to never release a delegate until your program quits. This email sent to site_archiver(a)lists.apple.com

1 0

Re: passcode timeout?
by Joseph Kelly 14 Sep '09

14 Sep '09

site_archiver(a)lists.apple.com Delivered-To: Bluetooth-dev(a)lists.apple.com That sounds like an Apple bug, which you should report. Joe K. On Apr 22, 2009, at 8:05 PM, Ken Aspeslagh wrote: Hi: Thanks, Ken _______________________________________________ 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.… When I open a connection to an unpaired bluetooth device with authentication, OS X automatically puts up the PIN code dialog box. But if the user waits more than 30 seconds before entering a passcode, the connection attempt times out and returns with kBluetoothHCIErrorHostTimeout. My problem is that the now non- functional dialog box stays on the screen. If I try again to connect I get a second dialog box. I'm not sure how to handle this situation gracefully. Any tips? Is there a way to keep the passcode request from timing out? Or at least a way to get rid of the PIN code dialog box after the connection attempt fails? ------------------------------------- "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair." - Douglas Adams This email sent to joeman(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Migrate BT projects to iPhone
by David Boydston 14 Sep '09

14 Sep '09

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

Migrate BT projects to iPhone
by C.S. Peng 14 Sep '09

14 Sep '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.23 (Windows/20090812) _______________________________________________ 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