site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com If you'd like to see it in action, there's a beta version available at: http://mirasoftware.com/BPE2/download/?com.mirasoftware.BPE2 Zach Rosen CEO and Developer mirasoftware.com reelintelligence.com On Aug 10, 2006, at 9:43 AM, mat davidson wrote: mat. On Aug 9, 2006, at 11:35 PM, Andrew Cooper wrote: Sincerely, Andrew Cooper _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... I don't want to violate my NDA with Apple, but it pains me to see another developer struggling with the same issue that I banged my head on for over a year. Using the Mac as a headset/handsfree device has been possible since OS X 10.4.4 using the existing audio driver and some unpublished Bluetooth APIs. I am purposely being as vague as possible because the implementation details were given to me through an Apple Developer Technical Support incident under strict confidences. This is as close as you're going to get to driver information, Im the one who wrote it! So, it sounds like you're trying to use the Mac as a headset/ handsfree-device? Im pretty sure we didn't design that driver you're using to support such behavior. That driver only supports Handsfree-Gateway, the role your phone is currently playing. Its meant to send audio to headset and handsfree devices and is really really restrictive about device behavior that is out of spec. The good news is that we hope to change this in Leopard which unfortunately doesn't help you in the short term. Interesting that you're trying to make the Mac behave as a headset/ HF device, there could be some interesting scenarios there. Maybe support for that behavior will show up in Leopard as well. In the meantime, Im not sure there is much you can do. Heres the list of things involved if you absolutely need to move forwards: - Vend the Headset SDP service, which you may already have done - Write an IOAudioFamily driver that matches on the incoming RFCOMM "Service Level" connection from the AudioGateway device (phone) - Your driver would need to catch the incoming SCO connection, capture the data, format it, and route it into the audio system - You may also need an agent application as well to change the System Sound input/output to the newly loaded driver so the audio data can be heard/sent when the device connects. Sounds pretty nasty to me, but not impossible. Ofcouse we're willing to help, but you're looking at quite a load of work there. I have no idea where I should head to try and solve the problems listed in my last email. It seems like the SCO link isn't ever established with the phone. Is there a way to debug what's actually happening in the driver and why the link might be failing? I can find no documentation on the IOBluetooth audio driver. If I could get the link established and data flowing, I believe I could direct the audio data wherever I please, so getting the SCO link working is the final lynchpin in having my app working. Can anyone offer any suggestions at all? Is there a way to contact Apple more directly for documentation on their driver? _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/mddavids% 40apple.com This email sent to mddavids@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/zrosen% 40mirasoftware.com This email sent to zrosen@mirasoftware.com This email sent to site_archiver@lists.apple.com