PDA

View Full Version : A2DP Bluetooth settings clearing


nihil0
16th December 2007, 01:27 PM
I red so many threads and mails to "how to use A2DP on WM6 Trinity" and "which registry setting are working". But I am confused. Because alll the people say something others. Maybe is that depending on the bluetooth headset or maybe on the WM6 ROM. I do not know. But maybe a thread to clarify the actual knowledge on that would be good.

So I try to beginn that.

If you have a working setting please post here and I try to summarise that in this first posting.

Thank you in advance!


Not really working actual settings (P3600 and UDK 6.1 R1):

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd]
"Flags"=dword:00010002
"Index"=dword:00000008
"Order"=dword:00000008
"Prefix"="WAV"
"Dll"="bta2dp.dll"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"Priority256"=dword:00000095
"Order"=dword:00000000
"Index"=dword:00000001
"Dll"="wavedev.dll"
"Prefix"="WAV"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"ConnectHFOnCall"=dword:00000001
"BTAGExtModule"="BTAGExt.dll"
"Capability"=dword:00000025
"SupportCLI"=dword:00000000
"BTAGPBModule"="\\Windows\\BthAGPhonebook.dll"
"NoRoleSwitch"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2 DP\Settings]
"UseJointStereo"=dword:00000000
"MaxSupportedBitPool"=dword:0000001E
"BitPool"=dword:0000001E



Suggestions for settings on P3600:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd]
--> remove any Priority256 value
--> Add "Priority256" entry, Dword: 3C (dec: 60)

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
--> change "Priority256" entry, Dword: 95 (dec: 149)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
--> change "Capability" entry, Dword: 25 (dec: 37)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2 DP\Settings]
--> change "UseJointStereo" entry, Dword: 0
--> change "BitPool" entry, Dword: 3A (dec: 58)
--> change "MaxSupportedBitPool" entry, Dword: 50 (dec: 80)
--> Add "SampleRate" entry, Dword: AC44 (dec: 44100)

joefso
19th December 2007, 03:20 PM
up up! I have a Logitect a2dp bluetooth set. I'm using Sleuth255 suggested a2dp registery values, which help a bit.... :



12/03/06
There may be registry settings, previously done in an attempt to work around the skipping problem, that are now hindering rather than helping. Changing quality and other A2DP settings with the Hermes registry Tweaker may actually contribute to this. If you are still skipping with a known good ROM/headset combination, please check your registry settings against these and report on your findings!

(all DWORD values are decimal)

/HKLM/Drivers/BuiltIn/BtA2dpSnd
remove any Priority256 value
HKLM/Drivers/BuiltIn/WaveDev,
Priority256=149
/HKLM/Software/Microsoft/Bluetooth/AudioGateway
Capability=37
/HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
UseJointStereo=0
BitPool=58
MaxSupportedBitPool=80
Remove all other values from this key including SampleRate