|
To all the folks who are experiencing stuff like skipping, high-pitched whine, no stereo, inconsistent music speed/pitch, etc - I have found it is essential to examine and adjust one or more registry settings (this seems to be true for most/all WM devices, depending on what the creator of the ROM put in there). Search ppcgeeks or xda-developers for some of the following strings and see what has worked for people:
UseJointStereo
BitPool
MinSupportedBitPool
MaxSuppportedBitPool
AudioGateway\Capability
Bta2dpsnd\Priority256
There seem to be some pretty standard recommendations out there for all of these except the BitPool ones. Getting your BitPool settings right can be tricky in my experience as it seems to be influenced by a number of factors. One of the most important factors is what BitPool setting your headset likes best (not standard across headsets), and there seem to be others as well (like which media player, type of encoder and what bitrate of your music files, etc). Something that has worked well for me - instead of using a single BitPool value (which may not be right for your headset), don't use that reg value at all (delete BitPool if it is there), and instead, start by using the MinSupportedBitPool and MaxSupportedBitPool values to create a range (your WM device and headset will negotiate a mutually agreeable BitPool to use within this range). Then adjust as follows: increase the Min value to increase quality/reduce high-pitched whine, and decrease the Max value to reduce skipping and inconsistent music pitch. Min of 30 and Max of 58 should be reasonable values to start with.
Of course, if you have replaced your MS Bluetooth stack with one of the hacked Widcomm ones, all bets are off (I haven't tried the Widcomm and dont know what reg entries it might be sensitive to). And as always, YMMV...
|