@gtmagnet,
I'm using a Jambox BT speakers by Jawbone, they connect as a set of BT stereo headset as they have a mic as well. (Have upgraded to their latest firmware as well, but as per below this is not an individual device brand problem.)
I'm not sure I can reproduce since it seems to change every day but here are some more info.
History:
- Upgraded to Lion problem started.
- Combined info from this thread and found a reset work around (see earlier post).
- Still problem when MBA woke up from sleep but could be worked around by turning of BT device and then turn it on again.
- Still some irregular problems but did not investigate further since I could get it to work for the most part.
- Installed 10.7.1 update problem reappeared. Again did the reset work around and it started to work again.
- Today with no changes at all I have the problem again and the power cycling on the BT device doesn't help.
So new procedure:
1. Got to BT Preferences, Advanced... Check 'Reject Incoming Audio Requests'
2. Turn BT off on MBA and BT device
3. Turn BT on on MBA and then on BT device
4. From the Menu bar Slecet BT device Use as Audio Device
5. Play video in iTunes (now the MBA is connecting to the BT device) and the audio is coming from the BT device
Back to having a working BT speaker again.
If I now put the MBA to sleep and then wake it up again the BT audio is disconnected and the internal speakers are on (which is correct). Turning on the BT audio again from the Menu bar BT... the audio gets connected and stays connected but the audio is stuttered, power cycling the BT device and again turning on BT audio the audio is ok in the BT device. This is all correct except for the stuttered audio.
Reverse the procedure and Uncheck 'Reject Incoming Audio Requests' and the problem reappears. (I also don't think this is the real problem but just something that helps as a work around. This is since the Jambox is unique in that it connects to the MBA as it is powered up, other headsets that has been reported to have this problem does not do that and the problem for them occurs when an app is making a connection to the active audio device.)
This problem is a moving target which indicates a software bug that is getting some indirect influence. Why would it change behavior from yesterday to today? A datestamp some where?! A memory position some where that has changed?! It is clearly a Mac OS X software problem since so many are reporting it with so many different devices. If this software is written in C++ I would say there is an uninitiated pointer somewhere, I don't know Objective C and how similar bugs are created there but I assume they are still.
When I say problem it means that the BT adiuo device is reported to have an error and is disconnected as per the popup in artfromeast longmeadow post of July 27.
Hope we get a fix to this soon instead of having to work out new work arounds everyday.
If you want more problem identification info maybe there is a way we can direct email or PM contact.
Have a good one and good luck.
--A