Database Users

Summary: Voicecommand via Bluetooth [STILL UNDONE]

After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht

Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?

Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.

Changed over to Tytn... works perfectly without any hacks

here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.

x7500 - Jabra 8010: voice disruptions/discontinuance reported by people I talk to

Hi guys,
I am wondering about the happiness of the union X7500 - Jabra 8010. Sometimes people I talk to tell me that they barely understand me because they hear disruptions/discontinuance in a voice coming from my side. This almost never happens for voice coming from other party. I am not saying the "couple" is responsible for this but it gets me thinking... What could be the reason for this? Why voice is not corrupted in both direction (up&downlinK)? Ohh, I have the BT configured to Stereo, but I think there is no difference in case of mono…
Is there any way I could test the voice quality coming from/to Jabra? Resco Audio Recorder? Anything else….?

jabra 8010 promblem with athena
i have the same problem.

This problem not only happens with my Jabra BT8010, but also with my other bluetooth headset i.Tech Clip D.

I have the same problem too, but not always happen this. Sometimes the quality is good, sometimes bad. If the headset properties on Athena is hands free the outcoming voice is clear. If you're connecting the Jabra with Athena and there aren't any stereo icon on taskbar coming up, the problem dont ocure.
I have WM5 on athena. Perhaps WM6 will solve this bug (Or a new Jabra update).
I tried it with another phones and it worked good.

Hi!
I have contacted HTC support for this and just received their reply. Man, they are "really quick" - 2.5hours - for the bullsh#!#t answer they provided...
Her is the reply:
"Good morning
We are very sorry to hear you are having problems with Bluetooth. You may find that Windows Mobile 6 may cure this problem when it is released for your device on the HTC eClub.
For now we would recommend using a compatible recommended Bluetooth headset as below:
http://www.expansys.com/htc/p_htc_item.aspx?i=150737
Thank you for your enquiry, Should you have any other problem, please do not hesitate to call us. Your Local number can be found at http://www.europe.htc.com/support/csbyphone.html
"
I shall install Resco Audio Rec and try to record one of these problematic calls. Maybe it will make a difference presenting direct "evidence"...
Any other ideas?

I've got an X7501 Advantage with WM6 on it. I'll be getting the BT8010 in a week or so. I could test this out if that would help.

I have X7500 WM6 Jabra BT8010.
It just disconnects at random times. I will go back to my Jabra BT500 and use the BT8010 only when I want stereo music or other audio output.
Hopefully Jabra will take a look at this problem.

Bluetooth priority patch?
Just curious, have you guys tried installing the Bluetooth priority patch?
http://forum.xda-developers.com/showthread.php?t=262119
I believe it increases the priority given CPU wise for the bluetooth audio. It actually resolved a problem I was having with my BT8010 and the Universal, the audio during a call was a little choppy and callers reported that my voice was frequently dropping out no matter how close the device and headset were. After downloading and installing the registry edit in the 1st post of the thread I linked to above, problem is gone.
Please let me know if this works, I'm considering purchasing an Advantage and would want to know if it works with my Jabra BT8010.
Thanks,
Galt

hi guys
i've got the same problem.
but not only when using my jabra bt250v
but also when using the wired headset, or no headset at all
so imho this is not a bluetooth related problem
after installing wm6 the problem didn't improve at all.
HTC produce the best WM devices out there
and the Advantage is their flagship device.
These problems with the most basic function shouldn't happen.
And HTC's answer is just poor!
I'm sure they know about this problem and also know that WM6 doen't fix it
(or at least not the ROMs available until today).
I'm still waiting for another RadioROM to fix this fault.

hi galt,
Thanks for your post. I have manually entered the fix form your link:
"Make a new Dword value and name is Priority256 and then for the DWORD Data value make that 60 save and reboot. Presto no more lag, cuts or audio drop outs." since the attached reg file did not have the contents the author has been talking about. I made this reg file with a fix and would like to share with you...
I will test it and let you know how it goes...
Uros

Could someone monitor battery consumption with this fix?
There was a similar fix with A2DP and the current consumption was crazy, so I uninstalled it...

Good news so far
1. With the fix installed and the X7500 "at rest", there is no additional current drain = 90 mA.
2. With BT on playing music throught the Jabra BT8010 the current drain is about normal = 320 mA.
3. With BT off, the current drain returns to normal "at rest" current of 90 mA. With A2DPfix the current drain remainded at 400+ mA.
Good news so far!
NOW: the remaining question: Does it solve the problem of dropout?
I'll try it for a day or so and report back.

GREAT news so far
After 4 hours of listening to music (X7500 WM6 BT8010) with Priority256 installed, I can report:
1. One BT dropout that lasted less than 1 second!
2. Normal battery drain!
I have not used the phone enough to know if there will be and BT disconnects or voice issues, but I will report back on these issues soon.
Looks very good at this point.

So far so good
Hi,
It worked for me as well . Almost completely gone, except some tiny/small discontinuance from time to time... GREAT!

I've been using this fix for 3 days and so far having no complain from the people I talked to. Good fix indeed.

Thanks for posting the zip file, makes installation painless. Testing right now!
Well, so far so good. I did experience 2 or 3 drop outs during music play, but I can not contribute them to the device as I was in my office and an ambulance put on their sirens, somehow there must of been some interference.
The best thing about music play was that when the player switched to each successive song, there used to be an audible click or bump, that just isn't there now!

Did anyone ever confirm if this fixes outgoing audio problems? I've had several callers complain of noise/breakups coming from me, when they sounded normal. I know it wasn't a signal issue since this happens when the Advantage is next to me, and I've used my 8010 from 50 feet away through multiple cube walls plus one real wall...

techntrek said:
Did anyone ever confirm if this fixes outgoing audio problems? I've had several callers complain of noise/breakups coming from me, when they sounded normal. I know it wasn't a signal issue since this happens when the Advantage is next to me, and I've used my 8010 from 50 feet away through multiple cube walls plus one real wall...
Click to expand...
Click to collapse
Try to upgrade your Radio ROM to v1.50. That'll solve most of your bluetooth problems.

Big trouble with BT handset on Orbit 2. Need Help.

Well....
I happiness owner of XDA Orbit 2 (same as HTC Polaris at other form factor).
All work very fine, but one thing just kill me.
Orbit not work propertly with BT handset (Jabra JX10). I tried all posible ROMs: Bepe, BlackWidow, Rus 6.1, original HTC Polaris (WM6.0), original Germany ROM from O2. With all ROM behavior of BT handset was the same:
1. HardReset
2. Search BT device and connect it
3. Tried make call to anybody (I call to my second phone, but it doest matter)
4. First 1-2 calls all good. Sound good, mic work.
5. Tried incoming call.
6. At handset normal alarm tone, press button and..... first 2-3 sec normal sound good - then just noise (as white noise) and mic blocked.
7. All other calls like char.6. Noise after 2-3 sec.
I tried to changed all posible value. BitPool, BitRate, WaveDev and all other.... Tried stoped many service who can block BT (OBEX, ActiveSync via BT). Nothing change.
I think about hardware malfunction, but when I tried connect other BT device like external GPS reciever or HP notebook - I get normal work via BlueTooth. So, it mean hardware of bluetoth works good and with BT not work only handset.
Please, help me.

I got the same problem, but slightly different: the first 2-3 phonecalls are perfect, then there will be no sound. I tried with my 2 blue tooth headser.
with my headset, it happens 2-3 tims also.
But I met once the phone is not working when I trying normal phonecall without BT ot any headset.
I tried different ROM, it remains the same.

Similar problems with HF Jabra SP5050
Hands-free functioning with my previous cheep Nokia was excellent. Now the same Jabra SP5050 with Polaris: TRAGEDY !!!

qinyugang said:
I got the same problem, but slightly different: the first 2-3 phonecalls are perfect, then there will be no sound. I tried with my 2 blue tooth headser.
with my headset, it happens 2-3 tims also.
But I met once the phone is not working when I trying normal phonecall without BT ot any headset.
I tried different ROM, it remains the same.
Click to expand...
Click to collapse
That is.
I tried all BT headset which I have, it Jabra JX10 and Jabra BT10. The same....

Janhura said:
Hands-free functioning with my previous cheep Nokia was excellent. Now the same Jabra SP5050 with Polaris: TRAGEDY !!!
Click to expand...
Click to collapse
You mean Nokia BT handset worked with Polaris very well?
What model name its handset? I try to test with my smartphone.
updt. It seems I understood what you mean. So, it my situation. Both Jabra BT headset works good with all my Nokia phones and not work with Orbit 2 (Polaris).

Henry_Lee & others:
Try turn off and on again (5 sec later) Bluetooth on Your Polaris when headset is on. Is it working?
Do it every time you start using headset. Need patch from HTC.

dj_nsk said:
Henry_Lee & others:
Try turn off and on again (5 sec later) Bluetooth on Your Polaris when headset is on. Is it working?
Do it every time you start using headset. Need patch from HTC.
Click to expand...
Click to collapse
Yep, its work. Thanks for that. But it black magic and not good solution.
updt. It work until to first sleep (power button) longer than 5-10 min.
Then again needed reboot BT on device. F...k.

So you said you tried all kinds of ROMs. There are some ROMs out there which include the test version of the Radio ROM. I'm a strong believer of the thought, that the Bluetooth part of the test Radio is flawed and leads to results like the one you suffer.
If I were you, I'd check my Radio ROM version and if it doesnt match the shipping one (which tops out at 1.58.21.23) I'd search for that version and flash it. After the flash, a Hardreset might not be the wrong thing to do.

schaggo said:
So you said you tried all kinds of ROMs. There are some ROMs out there which include the test version of the Radio ROM. I'm a strong believer of the thought, that the Bluetooth part of the test Radio is flawed and leads to results like the one you suffer.
If I were you, I'd check my Radio ROM version and if it doesnt match the shipping one (which tops out at 1.58.21.23) I'd search for that version and flash it. After the flash, a Hardreset might not be the wrong thing to do.
Click to expand...
Click to collapse
I wrote later that I tried flash original ROM for O2 Orbit 2. It ROM contain radio 21.23. And nothing changes.
But, I not wish change radio ROM. Last radio ROM very well and good quality of GSM and fast GPS more important for me. The more so because, BT still not work.

up.....

At me and many my friends (with Cruis) a similar problem. The first, second call - all is good. Then - break of BT communication. Works with SE is better, the Jabra is worse

andykha said:
At me and many my friends (with Cruis) a similar problem. The first, second call - all is good. Then - break of BT communication. Works with SE is better, the Jabra is worse
Click to expand...
Click to collapse
Yep, tha same ****.
Today I tried Motorola H680, it good work with O2....
I think, Orbit2 or Polaris not work with BT headset with bluetooth version 1.1-1.2. Only BT v.2 and it headset just last 1-2 year ago.

Is the problem solved ?
Hi everyone !
I've got the same problem with my Jabra BT Headset. But i've found a way to make it work : in fact you have to get your headset already powered-on when you launch BT on your Cruise. Then, you can have regular calls.
Sometimes, it seems to disconnect by itself, don't know why. You have to power off everything, reconnect BT Headset, then re-launch BT service on Cruise.
Have a try and keep in touch !

It seems to me, a problem not only in version BT 1.2 or 2.0. I speak so since has bought SE 712 w/BT 2.0 and has dug into the same problems.

Have you got some news about BT & Cruise ?

Plantronics 590E with Orbit 2 works flawlessly... Distance, sound quality and voice command function is perfect without any issues..
...and A2DP, AVRCP function is same also... with mp3 or movie files... (..need registry tweaks.. i'm find these tweaks in this forum..)
Sorry for my poor English... :|

Bluetooth and HTC touch problems

Does anyone else have a problem with their Bluetooth and HTC touch? I have tried 2 motorola and a LG BT headset and no one can hear me, but I can hear them. I tried pairing and repairing. I deleted it and added it as a new device. I have even tried the BT with another phone and it works with that phone with no problems, so I know it's my phone. I even tried a hard reset. Does anyone have a solutoin to this problem? I have the latest ROM update from HTC's website for a Bell HTC touch. My motorola headset was working fine, but I think after the latest Bell ROM update it stopped. Does anyone else have this problem or can anyone suggest a solution? thanks. paul.

my jawbone did this but my plantanics 510 fine

My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.

jarmijo said:
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
Click to expand...
Click to collapse
This thread is 7 months old...
What ROM are you running?

I am running the NFSFAN 6.5 rom V11 and have he same issue with a motorola BT headset.

edit: i just noticed that the initial question was about a newer ROM update and bluetooth, but ill leave my initial reply here, cuz i often look for solution in old posts, so if this can help anybody :
NFSFAN 6.5 rom V11 and bluetooth
i dunno, but my bluetooth stuff somehow works with the 6.1 update, if you cant find any working solution within an hour, id suggest using a "well tried and tested" ROM version, like the 6.1
i stopped picking the "latest and greatest" in cars, devices, apps, or O.S. for the last two years, and been living a whole lot happier since.
about my 6.1 bell mobility ROM and bluetooth :
i like to tweak my weapons alot, my htc touch has a 6.1 ROM update, and i use bluetooth everyday, and it KINDA works well, enough for me anyway...
listening to mp3 and flv everyday on the transit,
then switching at work on the audio dongle adaptor on the pc,
using an pair of sonorix bsh-100 ( foldable stereo headset + optional plug-in mike)
to me the thruth is that bluetooth is a ****ty technology, i love it, and it's well taught,
but the developpers quickly code ****ty interfaces to it.
my settings all work from htc touch to dongle, but i often have to connect the touch to the headset like up to 3 times, where it tells me its connected, but isnt, when i hear the beep, it means it actually IS.
same at work, connect sometimes once, twice, even four, it eventually connects.
it's isnt button wear off or bad contact, its just the code is ****.
i rented a SUV that had bluetooth, tried connecting my phone, worked first time, a week later we rented the same SUV model, and for the whole trip i wasnt able to connect at all... back at the rental we tested the SUV with the clerck htc touch ( nice coincidence ) it worked right away.
i want to add here that whenever i try to connect through bluetooth, it usually works the first time.
my point is, bluetooth creators did a fine innovative job, but werent supported by developpers.
test your bluetooth phone alot with friends owning bluetooth accessories, youll detect behaviors after a while, and will learn to know its "demons" !
a bluetooth everyday user

V13 seemed to fix the issue
Just upgraded to V13, seems like BT works a lot better.
A bit on my history with BY, I just upgraded from a motorola V710, had a Moto Q for a few months too. Never had any issues with BT using the same Motorola BT earpiece, and varouis others through the last 5 years or so. Always worked like a champ, this was my first experience with BT issues.

Bluetooth AD2P & Carkit connection

There are a lot of problems with carkit connections & the HD2.
I tried several things to get it working without success.
When I try to connect to the JVC KD-AVX44 it connects but give no sound at all. (making 2 connections, handsfree & stereo audio)
Then I tried the registry tweak mentioned into this forum and had success once. I was very happy because also the title track was shown onto the JVC display and also the phone was functioning ok both ways.
The sound trough AD2P was perfect. Only one time.
After that i get a lot of disconnects.
Then I tried to make only connection with the phone function and this is working ok now. When I want to make the connection trough AD2P then the problem is back. Also when you make it without making the phone connection
So I think the problem lies into the stereo connection. For instance when you skip a track onto the JVC then the connection will be lost and reconect again and giving 2 seconds of sound and then it's quiet again.
Also when to 2 connections exists the phone is blocked by incomming calls because it's thinking it's connected so the earpiece & mic are dead at that time. And also the radio.

Did you try the LineSpeed setting to 256 in the AV key of the Widcomm registry settings ?
Don't know if it could help in your case but it did for me, I don't have disconnects with my Sony headphones anymore and sound is better.

Bluetooth
Ok thx I will give it a try and post the results.

which registry tweak did you applied first, cause i too keep having issues...?

tweak
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone

Do I have to add this line somewhere? I found the AV key into widcomm but the line was not there

valos said:
After that i get a lot of disconnects.
Click to expand...
Click to collapse
Try turning WiFi off on the phone, it makes a big difference on my IO Play system.

valos said:
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone
Click to expand...
Click to collapse
Ok i make this in my BMW X5 and one of problems is solved - HD2 working correct when i am on call and power the car, but i have another problem - after 5 - 6 min on call Bluetooth connections is droped and i can't lisen nothing from Car or for Phone - i must to press Menu and switch off Hands free to continue conversation.

Ok but are you also making stereo connection. I only have the handsfree conected at this time and then the connection is stable. Only with the A2DP it goes wrong.

valos said:
Do I have to add this line somewhere? I found the AV key into widcomm but the line was not there
Click to expand...
Click to collapse
Yes, you have to add the key, sorry not have said that.

kmeta said:
Ok i make this in my BMW X5 and one of problems is solved - HD2 working correct when i am on call and power the car, but i have another problem - after 5 - 6 min on call Bluetooth connections is droped and i can't lisen nothing from Car or for Phone - i must to press Menu and switch off Hands free to continue conversation.
Click to expand...
Click to collapse
Strange, so far I didn't experience any disconnection.
I have conversations during more than 20 minutes daily and line quality is far better than with my Diamond, with no drops.
With the Diamond I had the BT stopping regularily on the phone, it was very annoying because I always discovered it when receiving a call and not being able to answer.
So far it didn't happen on the HD2, but it is really too soon to jump to any conclusion.
I don't use A2DP in the car as I didn't order the option, which I viewed as useless because the hard disk capacity of the iDrive is sufficient to hold a good collection, the audio quality and functionality is much better and I can still connect the phone to the USB plug as mass storage if I want to play or transfer something from it or any memory stick or external HD.
So maybe not having the A2DP profile active may help also.

I also not any problem with my old HTD HD and Cruize ... but with HD2 i have this issue.
Today i receive answer of my ticket from HTC: they offer me to contact with BMW and to ask them why they not support HD2 ... I think this is stupid becouse every new device must support old protocols and older devices.
Now the choice is to change Car or Phone ... sorry but HD2 not have any chance to survive.

kmeta said:
I also not any problem with my old HTD HD and Cruize ... but with HD2 i have this issue.
Today i receive answer of my ticket from HTC: they offer me to contact with BMW and to ask them why they not support HD2 ... I think this is stupid becouse every new device must support old protocols and older devices.
Now the choice is to change Car or Phone ... sorry but HD2 not have any chance to survive.
Click to expand...
Click to collapse
Yes how lousy is that
Got the same answer first, but they realised that BMW coudn't recall thousands of vehicles to do a BT upgrade just because HTC decided to adopt the crapy Widcomm BT stack.
So they say they are working on a fix, but given how many issues there are with this stack, they better switch back to the old MS stack instead.
To be clear, it is the Widcomm stack at fault here, not BMW. Every single phone not equipped with this stack, I could try on the BMW, worked flawlesly.
I hope they will recognise this officialy and not blame the others each time a customer opens a ticket about these flaws.
In the meantime, the registry hack works perfectly for handsfree profile, but it seems it doesn't fix everything when the A2DP profile is activated.

MacGyver4321 said:
Yes how lousy is that
Got the same answer first, but they realised that BMW coudn't recall thousands of vehicles to do a BT upgrade just because HTC decided to adopt the crapy Widcomm BT stack.
So they say they are working on a fix, but given how many issues there are with this stack, they better switch back to the old MS stack instead.
To be clear, it is the Widcomm stack at fault here, not BMW. Every single phone not equipped with this stack, I could try on the BMW, worked flawlesly.
I hope they will recognise this officialy and not blame the others each time a customer opens a ticket about these flaws.
In the meantime, the registry hack works perfectly for handsfree profile, but it seems it doesn't fix everything when the A2DP profile is activated.
Click to expand...
Click to collapse
After much playing around - I found a linespeed of 300 works best for the HD2. 256 still has questionable quality and 320 for some reason skips a lot. Reducing it to 300 seems to be a workable equilibrium!