Tornado A2DP (i.e. bluetooth stereo headphones) - HTC Tornado

I thought it would be nice if we cfoudl get some Q&A going about this topic.
I'd like to hear which Tornado ROMs seem to have good working A2DP, which BT stack they use (if you know), what headset/remote you're using.
I'd also like to know if anyone can give use directions for checking what stack our phone is using.
I'd also like to know your opinions on volume, hiss, etc.
If you are satisfied or unsatisfied with your volume, please include your audiogain settings for comparision:
HKLM\SOFTWARE\HTC\AUDIOGAIN
(note: audiogain settings are in hexidecimal)

Here is some info on A2DP reg tweaking, that is supposed to be relevant to the WM6 bt stack.
i.e. from the "final" or "official" released, not a beta.
[ Default Settings are as follows: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 30
MaxSupportedBitPool DWORD 30
SampleRate
UseJointStereo DWORD 1
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 37
[ Aternate Settings: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 51
MaxSupportedBitPool DWORD 60
SampleRate DWORD 48000
UseJointStereo DWORD 0
Cant remember if i changed the one below or it was already at that value.
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 60
-----------------
[ Sleuth255's WM6 optimum settings for bluetooth A2DP: ]
These are applicable to the newer releases of WM6.
Finding #1:
ADD/CHANGE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings :
Name: UseJointStereo
Value (DWORD): 1
What this does is enable Joint-Stereo for the SBC codec, which is important and makes the biggest significant change to improve sound quality. (Note: In earlier versions of WM5 and WM6, Joint-Stereo was broken and resulted in a mono-output. This is not the case anymore with the newer WM6 ROMS.)
Further note: Sleuth255 found that some of his A2DP headsets could not work with JS turned on. In that case, you have to set the value to 0 to disable JS (resulting in poorer quality sound with more "hissing").
Finding #2:
REMOVE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings if they are present:
- BitPool
- MaxSupportedBitPool
These values are used to manually set limits for the BT stack for the A2DP SBC codec. Previously, it was thought that these values should be set between 38 to 86. But if the values are removed, I think that the BT stack automatically chooses the best BitPool values for maximum quality. I've tried removing these values and the sound quality either improved or at least stayed the same.
[ SUMMARY ]
At this point, you should have only one value in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
Your A2DP audio should be very good at this point - almost indistinguishable from a wired headset. However, if you are still unsatisfied with the sound (you may notice some very slight "hissing" or "swishing" sounds on high frequencies of certain songs), you may want to try the optional setting below.
[ OPTIONAL ]
Finding #3:
This is optional, and a matter of preference.
ADD the following value to the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
Name: SampleRate
Value (DWORD): 48000 (decimal)
This forces the A2DP stack to send the audio to the headset at 48000Hz instead of the default 44100Hz. For some reason, I find that the 48Khz value makes the "hissing" sounds less obvious. Your findings may vary, as some people may prefer the slightly more forward sound of the original setting. But if you are game, give this a try - one thing for sure is that it definitely changes the sound quality.
To reverse the change, just remove the SampleRate value.
If you make this 3rd optional change, you should have the following values in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
SampleRate = 48000
[ Note - Quick tip on registry editing ]
Of course, every registry change needs a soft-reset to take effect. And please take the usual proper care when editing the registry or risk damaging your device.
Find that your settings dont "stick" after a reset?
Make sure you reset the phone like this: After making changes to the registry, exit your registry editor. Then push the power button of your phone (putting it into standby, with the screen off). Wait for about 10 seconds (the phone will be saving the data to disk during this time), and only after that push the reset button.
Click to expand...
Click to collapse
I like to quote my sources, but I don't have the links at this moment. I will update them later.

Varied...
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?

kkrull said:
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?
Click to expand...
Click to collapse
Sorry, I was intending to post my personal details soon.
I am using a Sonorix C3
Standards Bluetooth Specification V2.0
RF Frequency Range 2402 ~ 2480 MHz
Profiles Supported A2DP, AVRCP, Headset, Handsfree V1.5
Transmission Power 0.25 ~ 2.5mW (Bluetooth Power Class 2)
Receiver Sensitivity < -80dBm (PER 1 %)
Distance 10m (in open space)
Click to expand...
Click to collapse
I am using EA's Chinese "WM6 5.2.318.18120" ROM:
http://bbs.koxo.cn/thread-14687-1-1.html
Currently my headset (well, the remote dongle, really) supports stereo playback, call display and bt handsfree usage.
Reception seems very clear. Mic pickup is sensitive and noise cancellation seems to be just as sensitive (I was holding the mic in my hand and gesturing madly one day, and realised what I was doing).
My only complain is the volume. I need to muck about in the audiogain settings to increase it.
As for what bt stack I'm using, I have no clue.
If I dump the zip file from this link, http://forum.xda-developers.com/showthread.php?t=263735&highlight=a2dp the bta2dp.dll was last modified on april, 2006. When I look in the windows directory of my phone, it only tells me I flashed it. I guess I have to dump the ROM to find out.
There is also the problem that the WiMP in my ROM can't handle VBR files. I'll be updating to vjgrace's 3.5 ROM shortly.
edit:
No dropouts. Mostly it is a fight to manage system resources on the phone.

any ppl know how yo make when the phone ringtone can ring in bluetooth.
mean we can listen the ring tone from bluetooth.

Related

You have skipping or other problems with your stereo Bluetooth headphones? Read this!

Unfortunately, there are major incompatibility problems with current Pocket PC models and stereo Bluetooth headphones – to the point of being completely useless.
For example, I’m unable to use my – otherwise excellent - Plantronics Pulsar 590A with the built-in A2DP (that is, stereo headphone) support of my Dell Axim x51v and HTC Universal (both having AKU2+ ROM’s; that is, their built-in Microsoft Bluetooth stack already supports A2DP). Some 200-400 milliseconds after starting to play anything (there is no such problem with system sounds – clicks and so on), the headphone just goes quiet, and the sound will only return after 5-10 seconds. To get lost again, of course, if I (re)start playing anything in any media player.
Fortunately, I have no such problems with my WM5-upgraded (2.01) HP iPAQ hx4700, the Dell Axim x51v with the Widcomm hack, the iPAQ 2210, HTC Wizard and Fujitsu-Siemens Pocket Loox 720 (the latter three with various hacks and other, smaller problems; the first two has no real problems, the x51v with the Flow hack).
People with other headphone models have wildly different problems. Most of them is the “skipping” problem – the sound just stops for some hundred milliseconds or some parts of the sound stream is just ignored.
In this article, (in addition to my already-published, Widcomm-only global bitstream speed setting (BTSpeedSwitcher) and FlowControl article) I elaborate on how the two A2DP implementations (Widcomm, Microsoft (MS)) can be fine-tuned to make your headphones work.
1.1 Communication speed
Most skipping or quieting problems are caused by the too high communication speed between the PDA and the headphones. In these cases, you should first decrease this speed to see whether it helps. If you can get rid of the skips without scarifying much sound quality, then, you can actually make your PDA and headphones compatible.
1.2 Modifying the given values
All the values I’ll elaborate on in this article don’t exist in the Registry by default. This is why I’ve also provided registry import files – you’ll only need to click them from inside Resco Registry Editor (File / Import), the, in my opinion, (for the price) best registry editor for the Pocket PC as can also be seen in the Registry Editor Bible.
These reg. import files contain some default values, which you will most likely need / want to modify with the registry editor (to slightly decrease / increase to decrease the communication speed to get rid of the problems or increase it to have better sound quality, respectively). With most devices (in this test, PL720, hx4700 and x51v with both BT stacks), after you modify a sound quality-related value in the Registry, you’ll only need to restart the BT stack to be able to test the modified value. That is, explicitly stop and restart the BT unit. With the Widcomm BT stack, you’ll need to click “Turn Bluetooth OFF” in the context menu of the BT icon and, then, staright go back to Bluetooth Manager and just reconnect the headphone. With the MS BT stack, in Bluetooth Settings, just untick the “Turn on Bluetooth” checkbox and click OK (or, if it has a Communication Manager dialog like PPC Phone Edition devices, stop BT there); then, re-enable BT and reconnect to the headphones by going back to Bluetooth Settings and selecting “Set as Wireless Stereo” in the context menu of the given stereo headphone.
Note that this (a simple BT stack restart is sufficient) is not the case with the HTC Wizard: with it, for the changes to be registered, you’ll need to power the device completely off by long-pressing the Power button and answering Yes to the question about completely powering down the device. After it is shut down, just press the Power button again and it’ll reboot. It's only then will the changes have effect.
2. Microsoft BT stack: BitPool
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\BitPool
(Registry import script available here)
With the Microsoft BT stack, you can set the BitPool value, which has a direct effect on the communication speed between the PDA and the headset. Unlike with the Widcomm BT stack, in here, you can’t directly supply the number of kilobytes the PDA will transfer the sound to the headphones. Here, you’ll need to multiply the value of this registry entry with 6.5 to get the approximate value of the transfer rate.
To fix most skipping problems, you will want to decrease this value (and you will want to increase it to try to enhance the sound quality).
Unfortunately, decreasing it may result in a horrible sound quality decrease. For example, in my tests, I’ve found out that only with the value 24 can I have uninterrupted music transfer between by Dell Axim x51v (with the original MS stack) and my 590A. With any value over that (even 25), there started to be skips.
Increasing it will not necessarily result in a far better sound quality. On my HTC Wizard ((European) MDA Vario by its origins with the KTamas / bepe AKU3.2 RC1 ROM on it), which has a very bad A2DP sound quality by default, increasing this value to even 120 didn’t help – the very bad “typical for non-filtered contents sampled at a low sampling frequency” distortion remained. That is, you can’t raise the sound quality of the Wizard; not even with extra high BitPool values.
I’ve also played a lot with the MinBitPool Registry value (under the same key; see this forum post), without any success (on my Wizard). That is, at least with the current Wizard hack, it’s pretty futile to try to play with MinBitPool, it seems.
The same stands for SampleRate: it has no effect at all, it seems.
More info here (AGAIN, please note that setting SampleRate, MinBitPool and MaxBitPool don’t have any effect, at least not on the Wizard!)
3. Tweakability of the Widcomm BT stack
Unlike with the MS BT stack (which only has one parameter to be tweaked), there are far more locations / parameters this stack can be tweaked at.
Note that here, I don’t elaborate on the two previous hacks to combat the “transmission stops after a few dozen minutes; otherwise, it's pretty OK” problem – please see the already-linked global bitstream speed setting (BTSpeedSwitcher) and FlowControl article if you have the previously-mentioned problem. The hacks described in this article “only” help with constant skipping problems (and transfer quality fine-tuning), which are completely independent of the subject of my previous article.
3.1 LineSpeed
HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\AV\LineSpeed
(Registry import script available here)
This registry value is very similar to the above-introduced MS BT stack-specific BitPool. The difference is that it allows Widcomm users to directly supply the bit transfer speed between the PDA and the headphones – no multiplication is necessary.
The valid values start with 64 (that is, 64 kbit/s), which results in intolerably bad sound quality. 128 is still very bad; it’s with 192 that the sound quality starts to become acceptable. With 256, it’s already pretty hard to distinguish from the sound quality higher values result in – that is, you’ll want to start with the value 256 (and only slightly decrease to see whether it helps get rid of the problems).
I’ve even tested my Pocket PC’s with extremely high (400-600 kbps) values; they haven’t delivered noticeably (or at all) better sound quality than, say, the 320 kbps setting and they rendered the transmission far more unreliable / unstable, if working at all. For example, even at 400 kbps, my iPAQ hx4700 paused and skipped from time to time; at 600 kbps, it only played for some 20 secs and, then, went quiet. The Pocket Loox 720 fared a bit better at even 460 kbps but, again, the sound quality gain (if any) wasn’t worth the trouble and the additional BT communication load.
Speaking of the PL720, I’ve also tested whether a slightly lower, but still very good transmission speed (256 kbps) completely gets rid of the need for the FlowControl hack (again, see my previous article on the latter). While it played music for more than two hours, around the third hour, it stopped playing. Furthermore, it still had slight pauses (albeit I haven’t noticed playback at a higher pitch in the following 8-10 seconds). That is, you won’t want to completely get rid of the FlowControl hack. (I’ve also tested the PL720 with the FlowControl hack disabled and at 460 kbps – as opposed to the pretty stable 256 kbps. It shuts down itself after 3-4 minutes and, therefore, is useless, as I’ve expected.)
3.2 Blocks and SubBand
HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\AV\Blocks
and
HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\AV\SubBands
(Registry import script available here)
These two values can also be used to fine-tune your transmission parameters under the Widcomm BT stack. They are settable between 4 and 16. With higher values that 16, the Pocket PC won’t connect to the headphones; with lower values than 4, nothing will be heard (not even system sounds – clicks and the like). The lower the value, the worse the sound quality.
Of the two, the second, ‘SubBands’ parameter has a much less effect on the sound quality as the first (Blocks). For example, if you leave Blocks at (the best) 16 and set SubBands to 4, the sound quality will degrade only slightly (and, with the SubBands value of 8, it’ll be almost impossible to notice any quality difference). It will be in no way as bad as, say, using 128 kbps LineSpeed and will still be much better than the A2DP sound quality of the HTC Wizard.
If, on the other hand, you set Blocks to be 4 and leave SubBands at (the best) 16, the sound quality will be considerably worse. It’ll be, say, as setting the line speed (see section 3.1) to 96 kbps.
That is, first, start play with the SubBands value. Decrease it to, first, 8 and if it doesn’t help, 4. Then, if the latter doesn’t result in any usable result, start decreasing Blocks. Again, descreasing Blocks will have a very bad effect on the sound quality.
Note that Blocks only seems to have effect on 1.7 Widcomm versions; 1.5 versions (like the PDA2k upgrade usable on the Pocket Loox 720) don’t take this value into account at all. (Haven’t tested it with 1.6 like the HP update usable on WM2003 and some WM2003SE devices.)
(These three hacks were originally discovered by the well-known mikespikel in this thread.)
3.3 Other additional registry values available in desktop Widcomm implementations and some forum posts
I’ve also thoroughly tested the desktop Windows values listed here. They allow for tuning the bits-per-sample ("BitsPerSample"), setting the sampling frequency ("SamplesPerSec"; the case is similar to the “SampleRate” case of the MS BT stack) and setting the number of channels (mono or stereo; "Channels"). None of them seems to have any effect. If you still want to give it a try, the registry import script is available here.

Bluetooth Headset AD2P skipping

Have any of u experience Skipping when listening to audio via BT headset? Mine skip every 3 secs. any solutions?
i have quite the same problem, but mostly it works fine. Sometimes it skips at the end of the songs or even on the beginning, very annoying
Same here, I'm using Sony Ericsson HBH-DS200 headset. Sometimes it skips during playback (I use pocketplayer). Another annoying thing is that it take forever to find nearby bluetooth devices. A friend of mine also has the TC, but when we both turn on bluetooth it takes really long before we can see each other in 'Bluetooth Explorer'. Anyone knows why that is?
Mine is almost not usable.very 3 sec it will skip not sure what is the problem. Very dissapointed.
The same
Hi guys.
I also have problems with my bluetooth headset.. i have exchanged my phone for a new one but the problem consists.
I cant parre my Sennheiser VMX 100 BT headset to my phone, even though is works perfektly with my HTC P3300 and my HTC Touch??
Further more i cant use my other BT headset eighter. I have tryid
Motorola Miniblue H9
Nokia BH-208
Samsung WEP-200 Headset
but everytime i take a call the headset disconnets after 5-15 seconds ??
there is a setting which controls the size of the buffer. by default it's too small, apparently.
search on xda-devs, there is a fix in one of the tweak and tipps threads.
Edit: Just saw you named the technology wrong. It's called A2DP, Advanced Audio Distribution Profile, thats why you might not find any results because AD2P doesnt exist
Vl-Sher said:
On clean install of WM6 the sound was missing 8 seconds out of 10.
After adding
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\Bitpool = 20 (DEC)
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\MaxSupportedBitPool = 20 (DEC)
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\UseJointStereo = 1 (DEC)
there still are some "whistles", but the sound is more or less stable.
Click to expand...
Click to collapse
blacriderv said:
Yeah it works!
I put a DWORD Value in the same directory of BitPool/MaxSupportedBitPool:
- Name: SampleRate
- Value: 40000 ( Decimal )
Reboot and Enjoy
Click to expand...
Click to collapse
To summarize:
Set BitPool registry values to 40 (not 20)
Create "SampleRate", set value to 40000
Source: http://forum.xda-developers.com/showthread.php?p=1935917&highlight=bitpool#post1935917
Nyx2008 said:
Same here, I'm using Sony Ericsson HBH-DS200 headset. Sometimes it skips during playback (I use pocketplayer). Another annoying thing is that it take forever to find nearby bluetooth devices. A friend of mine also has the TC, but when we both turn on bluetooth it takes really long before we can see each other in 'Bluetooth Explorer'. Anyone knows why that is?
Click to expand...
Click to collapse
Hi
I am using the same Sony and pocketplayer. Using stock ROM with the bitpool set at 64 which is default on this machine, the sound is perfect with no skipping as long as I soft reset, initiate bluetooth, start pocketplayer, then press the headphone play button. It automatically connects and plays. If the phone has been used in a call or any other software first-forget it--bad skipping. This used to happen on my trinity too. Same procedure fixed it. Yes, you can reduce the bitpool but the sound will suffer. The skipping does not happen with my itechs which are bluetooth 1.2. I wonder if the Sony is using EDR or something--the sound is much better--can't even tell its bluetooth.
i have a problem with changing the registry values to try to get rid of the skipping when using a2dp wiht my samsung sbh-500
evertime i softreset the device, the settings are default again...
i use 1.64.08.21 radio and bepes 0.67 rom...
anybody an idea why thsi is happening?
greets and thanks, qoka
-----------------------
ah okay, got it, i made a softreset directly...

A2DP Bluetooth Settings

I have been scouring the discussion board looking for tweaks to the A2DP settings. I have a custom rom but don't think anything was done to enhance the bluetooth settings. I think the sound can be much better but can't find current tweaks with the new stack. So i ask you all, if you have made tweaks to your Bluetooth Audio and are pleased with the sound, what tweaks have you made?
Thanks in Advance!
I am using motorla S9's and the top end sound is washy,tinny.
if you use advance comfig it has bluetooth settings you can adjust
are the s9s comfortable for you? i have the s9 hds and they kill my ears
They are not bad. I can get them to be just right.
I know about the configuration tool, but I am not sure where to go with certain settings? i.e. Bitpool, joint stereo etc. Right now i have bitpool at Medium and it's still kinda crappy - on the high end.
lbhocky19 said:
if you use advance comfig it has bluetooth settings you can adjust
are the s9s comfortable for you? i have the s9 hds and they kill my ears
Click to expand...
Click to collapse
With S9 there is a very fine line between barely noticing they are on and utter discomfort, and it all depends on how you wear them.
Unfortunately there isn't a way to describe it, but there is a sweet spot, a position where it seems to be perfect.
Smaniac said:
With S9 there is a very fine line between barely noticing they are on and utter discomfort, and it all depends on how you wear them.
Unfortunately there isn't a way to describe it, but there is a sweet spot, a position where it seems to be perfect.
Click to expand...
Click to collapse
i may have found the way you describe but when you have them in do they just rest in your ear or do you actually have them like in the canal like most noice isolating ones?
ive used the new zune ones and some shure ones that you really push in your ear but these i can only seem to get just barely in and you dont get the great bass unless you kinda push them which isnt practical
Bluetooth Settings
I use the following bluetooth settings-changed thru the advance config 3.3 tool
bitpool very high
Max bitpool 80
Min bitpool 30
sampling 48000
This sounds really good thru by jabra 620s
thanks for the data - I will go with those settings.
in2vnyl said:
I use the following bluetooth settings-changed thru the advance config 3.3 tool
bitpool very high
Max bitpool 80
Min bitpool 30
sampling 48000
This sounds really good thru by jabra 620s
Click to expand...
Click to collapse
what do you use to listen to your music? I try using the HTC player with setting way low than yours and I get tremendous skipping and songs that are "busy", for talk radio they're fine but almost every song skips. my settings are
bitpool=25
max=60
min=15
sampling=44000
no stereo
I had these problems with my apache but I figured that the Touch Pro would be quick enough for this. Could someone please point me in the right direction to not skip. thanks in advance.
with the settings very high does your phone slow down?
it always makes tf3d real laggy and such whenever i play music over stereo with high bluetooth quality
in2vnyl said:
I use the following bluetooth settings-changed thru the advance config 3.3 tool
bitpool very high
Max bitpool 80
Min bitpool 30
sampling 48000
This sounds really good thru by jabra 620s
Click to expand...
Click to collapse
I am going to try out these settings. I just tried switching bitpool to high and no other tweaks and the sound was still pretty bad, I would almost venture to say worse than FM radio. I never had any problems with A2DP quality on my Tilt and I never touched a setting so I'm pretty disappointed. Hopefully this will fix it.
S9 Working good on Fuze
I have mine on low and no skips, not sure if very low sounded better. Maybe it will work for you
To summarize:
What is the configuration that you ultilizam in bluetooth?
The greater BITPOOL higher "quality" and lower performance of Bluetooth (signal power) right?
My device is HTC Diamond and Motorola S9 (A2DP)
What configuration i use?
one question:
Joint stereo - Yes?
PC400 said:
one question:
Joint stereo - Yes?
Click to expand...
Click to collapse
Just try this simple settings, sounds great, no skipping at all.
Joint Stereo -> NO
reason is becos it would not be true/real stereo if we choose YES... right?
I use the following registry setting.
HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
Bitpool - 76
MaxSupportedBitPool - 80
SampleRate - 48000
UseJointStereo - 0
This is what I have ended up with through trial and error, give this a go. However I think assuming joint stereo doesn't give you real stereo is simplistic and incorrect. I have had a bit of a read and it is quite complicated.
I wouldn't worry about it too much, just try both and see what you think sounds better.
All A2DP confused people must read this:
http://forum.xda-developers.com/showthread.php?t=310438
I'm getting a bit frustrated with the bluetooth on my touch pro.
My current settings are
bitpool very high
Max bitpool 80
Min bitpool 30
sampling 48000
No skipping all is fine until I go walkabout and put the phone in my pocket.
Skip skip skipitty skip.
Tried other settings but still no joy.
Help........

Terrible bluetooth audio quality after upgrading to WM6.5 (Touch Pro2 WWE)

Hi all,
Before upgrading my Touch Pro2 WWE to WM6.5 I was perfectly happy with the bluetooth sound quality. Sure, I did tweak it using a registry editor (months ago, I don't recall the exact changes I made), but the sound quality was marvellous. And...: no hickups!
As probably most of you already did, I upgraded my TP2 to WM6.5 about two weeks ago. So far I like WM6.5, I even get the feeling it has a slight better battery usage.
However, there is one big downside to this upgrade operation: I can't get the bluetooth audio quality on my Jabra headset to meet the quality it had on WM6.1. I used a registry editor to tweak the BitPool and UseJointStereo settings, but still I constantly have the feeling I'm listening to 96 kbit/s MP3 files, whilst the files are of >= 192 kbit/s quality... Also, music sometimes just 'hangs' (silence), and continues after a few seconds.
Am I missing something? Are there other parameters I need to tweak? I'd like to know which settings you guys use. Thanks!
Hi all,
I have the similar problem on my Diamond2. But I didn't used bluetooth headset while having WM6.1, so I can't tell was the audio quality good or bad.
I have silence gaps of 0.5-2s all the time listening to music. The gaps length and frequency doesn't seem to depend on the distance or obstacles (reasonable ones) between the phone and headset. They can be one inch one next to another but the gaps will be present.
However, the audio quality seem to be good.
I have TDiamond2(first official WM6.5 ROM from october 2009) + Jabra BT620s. I've tried various registry tweaks found here and in internet but with no result. Maybe I've missed somthing. Any ideas what might cause gaps?
Thanks in advance!
I think I just found a (the) solution! Check out this post at smartphonemag.com:
http://www.smartphonemag.com/cms/blogs/3/1350#more1350
Particularly, look at the LineSpeed DWORD, located in HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\AV
Setting it to 320 and resetting the bluetooth functionality led to a considerably better audio quality. Other settings which I have changed (don't know if they're relevant):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings
BitPool = 58 (DWORD)
SampleRate = 48000 (DWORD)
UseJointStereo = 1 (DWORD)
(all decimal values)
Good luck!

[Q] Help needed with Omnia 7 Bluetooth (A2DP/Car profile)

Hello, I am quite an avid reader on xda and have gained a lot of knowledge from this forum. Unfortunately I have run into a problem I cannot seem to understand.
I have a Samsung Omnia 7 (T-Mobile, flashed a stock omnia 7 rom,unbranded). Whenever I pair it with my Car audio (I have a Suzuki Alto) the audio drops atleast 5 times a second.
Also the mic voice quality is terrible (people on the other end complain of a lot of static & as if i were speaking from a thousand miles away).
I also happen to have a developer unlock on my phone so this gives me easy access to the xaps.
My Samsung Omnia 7 details are :
OS Version : 7.10.7740.16
Firmware Revision Number : 2424.11.9.2
Hardware Revision Number : 3.15.0.4
Radio Software Version : 2424.11.9.1
Radio Hardware Version : 0.0.0.800
Bootloader Version : 5.9.0.6
Chip SOC Version : 0.36.2.0
I read on the forum about using the Advanced Config tool to set the Bitpool to 51 and set Joint Stereo to 1. But whenever I tried doing that a popup would say "Unable to apply changes"
So I navigated to HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP
and I saw ONLY ONE subkey that as Devices that had 4 Subkeys labelled 1,2,3,4 each with a binary value (Address)
I added a key Settings to HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP and I added the following values to it:
Bitpool : 51 Dword
MaxSupportedBitpool : 51 Dword
SampleRate : 48000 (this was added by advanced config later when I was trying it out again)
UseJointStereo : 1
I tried testing these settings with my car bluetooth kit but the results were the same. At first I was baffled when I didn't see the key SETTINGS in the HKLM\SOFTWARE\MICROSOFT\BLUTETOOTH\A2DP path.
Is this normal?
Is there any way to fix the choppy extremely low quality bluetooth audio?
(PS I do not want bluetooth over video, also I have set SupportCLI from 0 to 1)
Hi,
Got the same problem.
BT worked in the really early days of my Omnia but since then, I am unable to listen to music on my Motorola S9 headset (even worst than you ! Drops 10 times a second !). Even the call quality when using a mono BT earpiece, sound is distorded and other side does not understand a thing of what I say !!
Sad to say but I really think Omnia 7 are subject to Bluetooth hardware failure.
Really think there is no way and quiet forgot about using BT on my handset. Shame because I was using my S9 all the time with my previous wm device and it was really working very well.
Anyway, if you figure out what's wrong, please, share with me ;-)
Last thing, did you apply some audio tricks through the Samsung diagnosis app ?
Good luck
Thomas
Sent from my OMNIA7 using Board Express
Hi, thanks for replying, I don't think the omnia 7 is subject to BT hardware failures as i've read about several omnia 7s running okay.
Also I did apply the sound trick using the diagnosis app but it messed up the audio on my phone. 30/30 sounded like the speaker is going to explode. Though the changes used to fall back upon restarting, they would come back if I played a song or if I got a call. So I had to re-flash my rom & reupdate it to mango.
I haven't tried BT on any pre-mango version but I guess its going to be the same.
Anyways lets hope Microsoft comes out with a fix in their tango update in Q2
:fingerscrossed:
Really wonder if BT problem may be linked to the sound trick. May sound weird but as I said, Bluetooth was working flawlessly at the beginning and I'm not 100% sure but it may have stopped working the day I messed with Samsung diag on sound settings.
More than that, I wonder at which OS level these settings are managed (even wondering if a hard reset or ROM flashing can roll back the whole thing to the factory settings)
I hesitated to hard reset in hope it will work again but I do not want to lose everything without being sure problem will be solved (and will never know id I don't do it )
Thomas
Sent from my OMNIA7 using Board Express
In my opinion the settings are rooted in the rom, you cannot program the hardware from the rom but only change the settings (this is what i think) anyhow, my BT settings never worked, not before messing with the audio settings in the diagnosis, not after, also what's weird is that the a2dp settings weren't present in the registry, i had to add bitpool, maxbitpool etc. manually (no change even then)
anyways, lets hope someone knows of a workaround or microsoft regards this issue as 'serious'
thanks
EDIT : @NebZoNe I tried your settings and they didn't work for me thanks for the suggestions anyways
adding a registry entry for bluetooth like bitpool should be made in ..\AD2P\Settings
see http://forum.xda-developers.com/showthread.php?t=1351043
try a registry editor instead of schaps' advanced config...better.
max supported bitpool must be 80 (dword)
if you use 51 for bitpool then you can't use jointstereo (set it to 0), or use 53 then you will be able to set 1 for jointstereo...
once you've connected your car's stereo to your device try to find the second tweak i've written (dots between \ are numbers) to make sure the sound will be streamed in stereo (if you setted bitpool at 51 for sure!)
good luck.
Hello, I used the root tools by cliff74 & advanced config to verify the settings. Anyways, I haven't tried bitpool at 53 & will do.
Question : in your post you have said this :
HKLM\Software\Microsoft\Bluetooth\Device\........\ Services\..........(then u should see u're in stereo sound settings)
enabled : Dword = 1
The dots are the numbers, so how do I know what device is which number?
Thanks!
japmeet said:
Hello, I used the root tools by cliff74 & advanced config to verify the settings. Anyways, I haven't tried bitpool at 53 & will do.
Question : in your post you have said this :
HKLM\Software\Microsoft\Bluetooth\Device\........\ Services\..........(then u should see u're in stereo sound settings)
enabled : Dword = 1
The dots are the numbers, so how do I know what device is which number?
Thanks!
Click to expand...
Click to collapse
Do you use so many BT devices that you can't identify them in that path?? i only use bt headphones so i didn't have that kind of problem sorry...
and i'm agree that what you'll find behind \Device\ is straightly linked with what you use...so you must find the string "stereo sound" for every device you connect...as well as you'll find a string value with your bt device name after first connection....
I must insist on the fact that schaps advanced config is screwing with BT's manual reg.edition...and there's no reg lines for samplerate values, they are setted up straight from bitpool level (51:48000; 53:44100; 76:96000)
unfortunately, having a look to other threads, it seems that samsung devices usually know issues with bluetooth function...
well in HKLM\SOFTWARE\Microsoft\A2DP\Devices I have 4 subkeys that are :1 ,2,3,4 each with 0 subkeys and 1 value that is address (a binary value)
In HKLM\SOFTWARE\Microsoft\Bluetooth\Device I have 1 subkey that is 00137b96be74 that has 1 subkey "Services" which has 2 subkeys :
The first subkey has the following contents :
Status (a subkey that is empty)
channel (value : 0 dword)
enabled (value :1 dword)
name (stereo sound)
sdprecord (binary value)
Similarly the other subkey of \Device\ has the same contents except for channel and name
Channel (1)
name (Hands-Free //I suppose this is my car bt audio but when i sync my phone with the car it shows BT Radio as the car's head unit's name)
Also i have logitech free pulse BT headsets and I have the same problem with that
well, seems that's alright i've got the same layout...
the only thing i can do is sharing my ad2p settings layout...
hope for you it's not a hardware issue...
I do not have the default key (not sure if that would make any difference) but anyway, thank you
japmeet said:
I do not have the default key (not sure if that would make any difference) but anyway, thank you
Click to expand...
Click to collapse
Same situation with my omnia 7 - and i have motorola s9 like you. I tried many settings in registry but all of them have absolutely no effect ((
though I shouldn't be bumping but *help?*
As I already told, sorry but I really think the reason is really simple. BT chip on Omnia 7 is defective, this is a hardware failure and I am quiet sure it can not be software solved.
There are plenty of reports on the web with people having the same problem with Omnia 7 :-(
Sent from my OMNIA7 using Board Express
But my motorola s9 worked fine with NODO.
Can we diagnose somehow that it is hardware issue? I have used following codes in Diagnosis:
*#232331# - BT RF Test Mode
*#232332# - BT Audio
*#232333# - BT Search Test
*#232337# - Bluetooth MAC Address
First one tells me that RF testmode is on, second gives me nothing... Third displays Search Failed!!! message and fourth just same code...
On my omnia
*#232331# - RF Test Mode ON!
*#232332# - Nothing
*#232333# - Search Fail!!!
*#232337# - 0x78471D364188
My bluetooth only works well when I put off the wifi on my Omnia 7
Sent from my OMNIA7 using Board Express
I've tried the codes and I have the same results as you have, sigh.
ikke008 said:
My bluetooth only works well when I put off the wifi on my Omnia 7
Click to expand...
Click to collapse
My bluetooth dont work with wifi.
And without wifi sound is choppy.

Categories

Resources