Hi,
I have a couple of questions:
1) I have a default corporate install 02 Exec and a Motorola BT H3 headset.
When the devices are all paired up, I can receive incoming calls no problem. But when I try and initiate a call from the headset by tapping it, I sometimes get a responding beep from the voice dialling software, other times not. When I don't get an audio response, the device just doesn't seem to even notice and nothing changs on the screen.
I have tried all the usual, re-pairing, reboots etc, but no luck.
I also can't pin down exactly when it does it. Sometimes I can start a call when the device is in 'standby' ie if I haven't used it for a while, other times not.
My next step is to find someones phone and test it with that and see if it is the headset or the exec.
2) My backlight does not come on when I tap the screen or a key despite having ticked the correct setting to enable this. Each time I have to press the power button.
Has anyone else had similar problems?
thanks,
/Mad
Ok,
have now done a complete hard reset and a new corporate install and the BT headset is stll not working 100% of the time.
I have tested it on another phone and it works a treat there, so it is not the headset.
thanks,
/Mad
Scrap the below info. This only works if the Exec has been off for a short time. Anything longer than a couple of minutes and it doesn't switch on with a tap.
I have O2 swapping it out over the next couple of days. Let's see if these issues are widespread. but judging by the responses to my pst, I take it I am the only one having trouble?
/Mad
Ok,
With problem 2) I have found that if I do a hard reset and install as O2 rather than corporate, when I open up the device in clamshell mode the backlight comes on and if it is already open, a tap on the screen or key does switch on the backlight.
So, this particular 'issue' appears to be related to the type of install. That is it works in O2 but not in corporate mode.
Still no joy with the intermittant BT headset voice dialling.
Either way, I have O2 swapping it out over the next couple of days. Let's see if these issues are widespread
/Mad
Last night I updated to the most recent O2 ROM (as per their website) and now...
it appears that the first time I press the BT headset button, nothing happens, but then on the second press it brings up the voice dial software.
I have had a damn good trawl through all the other posts about voice dialling and it seems that the first press connects the headset to the exec and the next button starts the app.
Is this correct? Anyone else had similar problems?
thanks for your time.
/Mad
I had similar behaviour when I used my SonyEricsson HBH65 headset with my Exec. When I bought a Jabra BT800 suddenly my Bluetooth experience was transformed, and the combination works perfectly.
I think the latest models of headset work much better with the Exec than those a year or two old.
Maybe this helps. Hope so.
Thanks for your reply.
I took my BT headset back to the shop today and got them to try a jabra (don't know which version) it still wasn't bringing up the voice dial software every press.
Spoke to O2 support today and they admitted that BT is flakey on the Exec and that it is a known fault with HTC.
Oh well, at least it isn't just me!
/Mad
Related
Hi everyone!
New to this forum but got my Qtek S100 a couple of weeks ago and found an irritating bug in it..
When I use my SonyEricsson HBH-300 Bluetooth headset everything is fine until I've talked for ~7 minutes.. after that the other party doesn't hear me while I still can hear the other party.. Sometimes my mic never comes back during that call but sometimes it's back after about half a minute or so.. the funny thing is that if it comes back it goes away againg in about 14 minutes.. and perhaps 21, 28 and so on.. haven't really made that long calls with that headset because of the bug..
The headset works fine with other phones, at least SE Z1010, SE P900, Nokia 6630 etc..
And the S100 works fine with my Bluetooth GPS..
Has anyone experienced anything similar?
Have you got other bluetooth headsets, do they work for long ( +7 minutes) calls?
Cheers
/Rikard, Sweden
di7riks said:
Hi everyone!
New to this forum but got my Qtek S100 a couple of weeks ago and found an irritating bug in it..
When I use my SonyEricsson HBH-300 Bluetooth headset everything is fine until I've talked for ~7 minutes.. after that the other party doesn't hear me while I still can hear the other party.. Sometimes my mic never comes back during that call but sometimes it's back after about half a minute or so.. the funny thing is that if it comes back it goes away againg in about 14 minutes.. and perhaps 21, 28 and so on.. haven't really made that long calls with that headset because of the bug..
The headset works fine with other phones, at least SE Z1010, SE P900, Nokia 6630 etc..
And the S100 works fine with my Bluetooth GPS..
Has anyone experienced anything similar?
Have you got other bluetooth headsets, do they work for long ( +7 minutes) calls?
Cheers
/Rikard, Sweden
Click to expand...
Click to collapse
That also happened to me in the beggining after erasing the handsfree from my devices and paired it once more its running fine since then!
HI!
di7 riks.....I am using a Motorola HS810 Bluetooth handsfree with my O2 XDA II Mini and the same 7 minute problem is happening to me also. Initially it was 12 minutes but now it is down to 7. I can hear the other party but they can't and then I have to disconnect and dial again.
think I will do as katsj did...try pairing teh device again.
U
This is a known issue. Apparently, what is happening is that the device is going to sleep, and bringing down part of the bluetooth with it. The quick'n'dirty solution is to set your device to never power off, and just turn it off manually. Hopefully this will be fixed in the next round of ROM updates :?
I have an "almost" similar problem: I answer the call with the HBH-300 and talk for about 10 seconds after which I can hear nothing (the other part hears nothing also). If I close the handsfree from the MDA Compact then I can continue talking from the MDA (the call is not ended).
If I close the call and make a new call I get the same problem. But if I switch off the HBH-300 headset and switch it on again then the problem stops and in the following calls I can talk using the HBH-300.
This problem appeared only twice in the 15 days that I am using the MDA.
Obviously the phone did not power off in 10 secs (it was on when I had the problems) so the "sleep issue" mentioned previously could not have created the problem. Only the backlight goes off in 10 seconds. Do you think that the backlight might cause problems to the bluetooth?! :shock:
atsois said:
I have an "almost" similar problem: I answer the call with the HBH-300 and talk for about 10 seconds after which I can hear nothing (the other part hears nothing also). If I close the handsfree from the MDA Compact then I can continue talking from the MDA (the call is not ended).
If I close the call and make a new call I get the same problem. But if I switch off the HBH-300 headset and switch it on again then the problem stops and in the following calls I can talk using the HBH-300.
This problem appeared only twice in the 15 days that I am using the MDA.
Obviously the phone did not power off in 10 secs (it was on when I had the problems) so the "sleep issue" mentioned previously could not have created the problem. Only the backlight goes off in 10 seconds. Do you think that the backlight might cause problems to the bluetooth?! :shock:
Click to expand...
Click to collapse
I am facing both problems described here. Does anyone know of a solution?
This is a known issue, but unfortunately it is not stated on Club IMate as a known issue.
This is concerning, because I assume i-Mate Techs are not working on this issue.
Over at Howards Forums Bengalboy states if you press the devices call button twice the headset incoming audio gets reactivated. I have yet to test it, because my caller hangs up before I get the device out of the case to press the call button twice.
One of these days I will beat the clock.
1.5 years ok, way back in Oct-03 I remeber many of us scrambling about all the MS Stack issues on the MDA II/XDA II, etc, and eventually tools were developed to help the issues.
I get rid of the PDA2K, because of all it's issues. Now the PDA2K has a better ROM and a new fix for the Broadcom stack.
Oh the misery.
I pressed the power switch on and also pressed the call button twice...I dont know which worked but my call did not get disconnected after the 7th minute...
Ujj
BT headset cutting out
I have the same problem - BT headset cutting out after a limited period of time, ~10 seconds.
Same problem here, when using bluetooth headset people can't hear me after 8 minutes, pressing the green talk button twice restores the connection.
Second problem: phone does not answer call automagic with bluetooth headset. (jabra BT 200)
Third problem: no voice dialing and no possibility to hear who is calling.
Are these MS Bugs or HTC Bugs?
_________________
T-mobile compact
ROM version 1.01.00 WWE
ROM date 10/21/04
Radio version 1.00.10
Protocol version 1337.36
ExtROM version 1.01.124 WWE
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
bamse said:
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
Click to expand...
Click to collapse
This is interesting - I'm running rom 1.06.00 WWE and extRom 1.06.115. I noticed that they have a extRoom 1.06.116 there, is that the one you are running?
espenleknes said:
bamse said:
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
Click to expand...
Click to collapse
This is interesting - I'm running rom 1.06.00 WWE and extRom 1.06.115. I noticed that they have a extRoom 1.06.116 there, is that the one you are running?
Click to expand...
Click to collapse
Yes, 1.06.116 it is.
It adds another issue though, making GPRS unable to reconnect after a phone call or USB Active Sync.
Hit the power button to reactivate - not the Green call button.
I also have this problem, when the device goes back to sleep my bluetooth headset microphone no longer works. I can still hear the other caller, however i need to hit the power button (Red one on the side) to get working again.
No need to disconnect the caller.
I have experienced a strange problem with my JasJar bluetooth radio. The bluetooth radio seems to turn itself off from time to time. I think it is somehow related to WM2005, because I had the same issue with a Himalaya running WM2005 (thanks to Buzz). What is weird is that the blue light continues to blink. If you go to the wireless manager applet, it sometimes shows the bluetooth as on and sometimes as off, but if you go to the bluetooth setting, it shows the radio as off. Turning it on, with the applet, or in the bluetooth settings, is only sometimes successful in actually getting it working again. Ressetting the device works every time. No need to re-pair.
Any suggestions?
TIA
Panabax
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
craigiecraigie4 said:
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
Click to expand...
Click to collapse
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Edit: i've made a mistake in the registry... found by ekapco. THANX.
uploaded new cab below...
buzz
Buzz, you're a legend!
Trying it right now, will report back tomorrow.
Can u not help us on all our other problems (http://forum.xda-developers.com/viewtopic.php?t=28343)? Your posts on Buzzdev.net indicate that you're far more technically savvy than most ppl here.
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
ekapco said:
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
Click to expand...
Click to collapse
BlueAngel? I think, this is a Universal fix.
BlueAngel? I think, this is a Universal fix
Click to expand...
Click to collapse
So ????
Registry is almost the same on this issue.
ekapco said:
In your headset fix shouldn't reg setting be hds1: instead of hds1 ?
Click to expand...
Click to collapse
of course... i'm so stupid... sorry...
should be hds1:
THANX ekapco...
buzz
ThExSenatoR said:
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Click to expand...
Click to collapse
WOW!
That was a helpful post. Thanks.
Buzz; can you explain what your fix actually does? I don't have a cab extractor here to look at the contents.
fix sets hds1: = dword:0 for 'unattended' system power state.
hds1: is headset device identifier.
bkl1: is backlight
wav1: is wave device
dsk1: is block/disk device
etc...
let's have some fun with those power settings...
open your regeditor and change
[HKLM/system/currentcontrolset/control/power/state/on]
"bkl1:"=dword:4
and
[HKLM/system/currentcontrolset/control/power/state/backlightoff]
"bkl1:"=dword:0
after changing the regs, press power button to off and on again. that will flush and apply new settings.
ok. the above settings will REVERT backlight's behaviour. I mean, when device is on, backlight is off. after inactivity timeout, light goes on.
well... funny experiment...
that proves, that devices could be powermanaged from here.
if you've had enough fun, revert those settings to normal. ;o)))
now set in:
[HKLM/system/currentcontrolset/control/power/state/unattended]
"bkl1:"=dword:0
that SHOULD turn the backlight on, when you leave the device untouched for a longer time (when the display goes off) or if you press the power button.
so leave it untouched and watch the display to see what's gonna happen on the 'unattended' state.
after approx. 5 minutes (never measure that), just when the display is about to off itself, BACKLIGHT FLASHES for a second and goes OFF.
why? we just said, bkl1:=0 (ON)?
so our settings are overriden. maybe that 'flags' settings?
lets see later, but exactly the same happens with BT connection even if we say ON, it goes off...
I have to sleep now in 'unattented' state, but meanwhile you can look at msdn, coz I saw those flags description there.
good night
buz
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
EyeOfTheStorm said:
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
Click to expand...
Click to collapse
Please follow my last post here or you have to tell me your wifi device handle.
I try to find the device ID
In "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Power/Interfaces" i fount this 4 IDs
{8DD679CE-8AB4-43c8-A14A-EA4963FAA715} Power-manageable block devices
{98C5250D-C29A-4985-AE5F-AFE5367E5006} Power-manageable NDIS miniports
{A32942B7-920C-486b-B0E6-92A702A99B35} Generic power-manageable devices
{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1} Power-manageable display
Does this help? Or am I wrong?
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
craigiecraigie4 said:
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
Click to expand...
Click to collapse
...stupid question, but:
does it actually have MS BT stack??
buzz
there is another problem, it seems that my mobile doesn't accept any connection from any nokia mobile, it says to them (unable to connect), i don't know why???????????
I too am experiencing Bluetooth problems with my O2 Exec and a Motoroa HS810 headset. I use voice tags quite a bit and for the most part this works well however sometimes the EXEC fails to respond to the button press on the headset.
I first noticed this when I did the reg hack to make MS Voice Command the default Voice dialler and presumed that maybe there was a problem with MS VC so went back to VoiceDialler. However the same thing happens with VoiceDialler. To get it working again i have to turn off bluetooth in the Wireless Settings panel and then turn it on again. After this it starts to work again (but not ideal if your driving).
I think this might be the same problem mentioned above, i.e. bluetooth says it is on, the blue led flashes on the phone, but in reality it has switched itself off. I did some more testing while the headset was not initiating voice dialling and called the Exec. After a short time, the headset icon appeared on the "Incoming Call" message area and my headset burst into life. This would make sense I suppose because doesn't Headset mode start bluetooth up when a call is received (presuming it is off)?
Looked at Buzz's reg hack for Bluetooth but didn't really understand it
Here's what didn't fixed it for me.
After more reading today I realize I was way wrong.
Re: Here's what fixed it for me.
I can confirm that these registry settings work perfectly on the blueangel Great job.
Hi,
does anyone know how is it possible to disable the LAST NUMBER REDIAL function? If my BT headset is in my pocket it happens many times, that the "-" button is pressed and it activates the LAST NUMBER REDIAL. It is very annoying....you can imagine. Is there any REGISTRY hack or somehing like that to solve this problem?
THX
That has to be one of the most annoying things!
Especially when you are having a moan about someone after the original call!!
Vijay??
Nobody has the same problem?
me too - it happens for me because I changed the LaunchAPEnable registry setting from 1 to 0 to send the sound to my headset over BT
WOlfgang
Can you clarify this problem? Which button is it that's being pressed? Hardware key or on the headset?
Explain clearly and I'll look into it and if I can help...
V
Vijay, you're too kind for your own good.. heh heh. (but we all appreciate it )
I had this problem with my BT headset and speaking for myself, it's when you hold down the button on the headset, you'll initiate last number redial.
If you just press the button you'll launch Voice Dialler..
I used to keep my BT headset in my pocket and I had both these issues.. eventually I resolved both of these problems by buying a £3 neck strap off ebay and wearing the headset round my neck.. :wink:
cheers,
gaspx
--
BT on for nearly 2 weeks!!
gaspx: there is a technique I'm working on which might help us out here.
It's messy and very very early stages right now, and sent me over the edge last weekend. But if the technique works, it'll open some very interesting doors. Please remind me in a few days. I'm afraid that I can't think of a quick solution, but in my usual style, an unnecessarily complicated solution might surface...
V
i have had the same problems aswell...
although i have been looking into the phone tools that only turn the bluetooth on when you have a phone call,
i am wondering if that will allouw bluetooth to turn on when transfering audio
VJVolubilis will automatically enable bluetooth and transfer audio (or attempt to).
V
Anyone figure out a way to do this yet? It sucks because I keep accidentally calling people from my headset.
I've looked around for a solution to this problem for a while now. Anyone come up with something? Vijay?
Any development on this issue yet? I accidently called twice today. Very annoying because I kept my BT headset in pant's pocket. Please help, Vjay and others professors.
How about powering down the headset? Maybe I don't get it but....
I just triple-checked, my Motorola H500, H820 & H700 will reconnect when I power them back up & press the button once as long as the phone's BT is on, even mid-call. Do these newfangled machines not offer that? What I do is answer the call on the unit w/ one ear and if I think it'll be more than a minute, I put the headset on the other ear to power it up, press to connect, and I don't miss a word (not on the H820, I'll take a pause to switch to that one when I pull it out of my gadget-laden diaper bag. Every mom needs a BT headset!). I think it'll hook up even during ringing, but calling from my skype seemed a little overkill for this response.
(I'm using a modified/very-simply-reduced version of the Jaguar ROM on a wizard at the moment, and many of Vijay's venerably ingenious tools.)
Anyone here use VC1.6 with Bluetooth?
Has anyone else noticed that the confirmations don't work?
I've seen threads on other forums about this, but no solution yet over there.
Figured I'd bring it up in case folks here have the answers.
Basically, here's my conversation:
Press BT button
Device: *Beep*
Me: "Call John"
Device: "Call John?"
Me: "Yes"
Device: *Timemout Beep*
Now, the confirmation works when used on the device just fine.
When on the headset, its like it gives up without trying to hear me.
MS Voice Command v 1.6 works almost perfectly on my Sprint Mogul. It has one flaw - when the button you map is first pushed it does not give off the beep, but the small microphone on the top bar shows up. When the little mike shows up, you can say your commands and it works perfectly.
The next time the button is pushed, the beep is heard and the mike shows up.
Also, VC is activated by my Motorola S9 stereo BT headset. If I push the right button on the headset, I hear the beep and can give the command into my headset even if the headset is in my backpack.
The failure to beep on the first button push is a small problem I'm sure can be worked out. For me it is no problem at all. I just push the button and begin speaking.
I own many other HTC products and VC works as well on the Mogul if not better than any of them and I haven't even hacked it yet.
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
ImCoKeMaN said:
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
Click to expand...
Click to collapse
Yeah, this makes browsing media impossible!
I used to say "Play music" wait until it asks me what type to sort by "Artist"... wait again "Dream Theater"... and then the music would start.
Now, I can't get past the first prompt because the mic is shut off. Very weird indeed...
Voice Command 1.6
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Traumtanzer said:
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Click to expand...
Click to collapse
Scratch that, I wasn't able to duplicate this, so seems to be a random occurrence, I know that every once in a while it does seem to work correctly, but that's very rarely.
List of Voice Commands
Has anyone got a list of voice commands, and is there any way to add new commands?
My VC 1.6 bluetooth problem is even more frustrating. It always recognizes my contacts, but the confirmation doesn't work AND I CAN'T DISABLE IT!
I uncheck the confirm box on the VC settings, but it still tries to confirm.
Is there something I'm missing?
Sprint does it again
WM6 has voice command built-in, but Sprint decided to disable it and not make it part of the ROM, so when you install 1.6 over the already there application, is when you lose part of the functionality.
Ha! I found my voice command problem -- I had a duplicate contact.
What voice command said (even after I turned off confirmation) was "Joe Blough at Home 3 found" and then it displayed one of them. When I removed the duplicate and turned off confirmation -- IT WORKED!
Now, if they would just fix the confirmation to work properly...
Ok.....my problem is it will not announce incoming calls, no matter what i do...everything else seems to work fine, but it will not announce incoming calls threw the bluetooth nor speaker, am i missing something???
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
TC1 said:
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
Click to expand...
Click to collapse
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Is there an echo in here? What part of "needs to be updated to work 100% with WM6" didn't you understand?
I was saying it isn't buggy as you said, it works great for the OS it is intended to be used on.
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Shaska said:
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Click to expand...
Click to collapse
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Dishe said:
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Click to expand...
Click to collapse
And also doesn't always confirm commands. At least from my experience.
primenall said:
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Click to expand...
Click to collapse
I have the Alltel 6800 with WM5 and am experiencing the same problems as you WM6 folks.
It seems to be an issue with the Mogul/MSVC combo like you said, also a friend of mine put the WM6 Rom on his 6700 and he says MSVC confirmation works fine.
Maybe a Radio incompatability, I'm just a novice though?
Hey there,
I have seen connectivity issues, but not this particular issue so...here goes:
This problem has been sporadic for me, but recently lasted for the past week.
I can connect my bluetooth earpiece to my HD2 just fine.
If someone calls I can hear it through the phone and pick up.
I can have a conversation through it.
What I cannot do at this time (and could a few days back) is press the button on my earpiece, hear the "blip" which prompts me to speak, say call [insert name], hear the name repeated back to me, I confirm and away we go!
If I am looking at the phone while I am doing this the microphone symbol will show up when I press the button.
If I then say, "Call home" it will show the contact page for "home."
If I then say "yes" it will dial "home."
All of this is done with no sound confirmation.
This is obviously not good for hands-free driving!
I have changed no settings and yes, it has been working with all ROMs, but as I noted, I have had this problem sporadically and now it is going on a week since I had this functionality.
Yes, I have done several soft resets, turning bluetooth on and off as well as unpairing and redetecting the device.
Any thoughts?
OK...it just worked for me.
Like I said...sporadic.
The only thing I can think of that I did differently was that I turned on bluetooth then turned off the phone (just clicked the power key, did not power down) then put on my bluetooth and once paired I tried the function and it worked.
The last few times I had not clicked the power key as I was waiting for the pairing and then attempting to use the function immediately thereafter.
hmmmm...
I don't know if this counts as a "fix" yet.