Develop Bugs

Jabra BT800 problem - or is it just me? - It is just me

Hiya, I got a BT800 for Christmas from my lovely wife and am having a hell of a time getting it to activate voice dialling!
Having paired it and chosen to use it as the hands free device, I can use it for phone calls that I start from the phone, but the Exec doesn't do anything when I 'tap' the answer button (one beep) or squeeze it(beep, pause, beep).
I've even just restored the original rom (hard-reset, basic install) and it still doesn't do anything...
Did anyone else have this problem? Is there a stage I'm missing out?
Hope someone can help, I've a nasty feeling it's too late to return it to Amazon...

Might be a daft question, but have you added your voice tags (or re-added after hard reset)?

Thanks for the reply, I was never intending to use voice speed dial (preferring voice command by miles) and so didn't record any tags. Even without any, you should still get the app launching and a message that there aren't any tags recorded. My problem was that I wasn't even getting that.
I can't claim to have solved the problem, but at least I no longer have it! I reinstalled the original O2 ext_rom and did a nice clean "Basic" install then put my customised ext_rom back and reset again. Having paired the headset I was able to launch voice speed dial from it, so went ahead and installed voice command, made the registry change to launch VC from the headset and am laughing.
I wish I knew what had caused the problem so I could avoid doing it again! I suspect that it was an attempt to restore my bluetooth registry settings on a rebuild that was the cause... Certainly I didn't try to set it up automatically the second time round and it *did* work, but there are too many variables to be sure.
HTH someone!

The Universal has no NATIVE support for Voice Dial using Voice Command. You have to do the following so it will work via VOICE COMMAND as it has to bypass the Installed Vocie software:
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
This should now launch Voice Command
Maybe you made a mistake like missing a letter?
If you have done the above and it still doesnt work, then i'm just as lost as you are

sorry, browser problem, message was posted twice

I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?

MvanIperen said:
I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?
Click to expand...
Click to collapse
Which button do you have to press to activate the voice dial? The left or the right button under the LCD? Is it Tap or Hold, the button i mean?

@jorgee: 1st post - thanks, that's what I meant earlier when I said I'd done the reg fix and it all worked
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
@ MvanIperen, I'm using the latest BT800 firmware too, when I did a couple of rebuilds, the problem went away and it now behaves as you describe.
@ all, thanks for the replies! It was just me after all! Mental note: Mess with the registry at your peril!

[quote="this_mike
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
[/quote]
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?

Jorgee said:
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?
Click to expand...
Click to collapse
Maybe I misunderstand what you're asking.
You posted the registry change to make this work higher up the page.
Pressing the answer button on the headset does fire up Voice Command but only if the display is open or in portrait mode. If it's closed in your pocket protecting the screen then it won't work

I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.

Jorgee said:
I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.
Click to expand...
Click to collapse
On the BT800:
- To activate voice dialling (whether using MS Voice Command or the 'standard' voice dialling app) using a BT800 headset, press briefly the button nearest the headset microphone.
- To redial from the headset the last number dialled, press and HOLD the button nearest the headset microphone.
This works for me whatever situation the Exec is in: open, closed, portrait, landscape. I'm using the default voice-dialling software, not the MS one. Hope this helps.

Thanks SiliconS,
That was the answer i was looking for, sorry i had to bother you guys instead of reading the manual as my manual is in Spanish and i am only a beginner-intermediate level reader.
Again THANKS!!!! Very appreciated

Are any of you folks running WM2003SE? See, I was able to make that registry change and do a soft reset and have Voice Command working through the BT headset on my old machine, but it was running WM2003 (not the second edition version). From what I have read, SE doesn't seem to like that registry change, as when you make it, all that will happen is the connection opens when you tap the button on the HS, but the ability to use VC is not there.
I know there must be some way to do this. Any opinions or suggestions would be fab!
Thanks much!

Bluetooth and WM6 - Pairing and Voice Command 1.6 Questions...

1. Is it possible to have the BT headset announce incoming calls but still have the phone ring with Voice Command 1.6?
Seems like it's an all or nothing deal so far... either ring and announce through the BT headset (by selecting "Announce Incoming Calls") or ring and announce through handset... Notifications work fine though. The handset would play the alert then the BT headset will announce the reminder. (See here for more details.
2. My BT headset and handset don't automatically re-pair after returning in range or resetting the handset. Anyone else experiencing this?
Everytime I walk out of range or reset my phone, I would have to turn off my headset then turn it back on for the two to pair back up. I sometimes forget and when I hear the handset ring, I pick up w/ the headset only to find that they're no longer paired. Is there a way to have the two automatically pair back up? I never had this problem when I was using AKU3 roms and the stock Cingular 2.25 ROM.

a2dp problem and phone not ringing when call come

hi i have this a2dp bluetooth problem ? its to do with the a2dp problem
anyway when connected with A2DP mode, all incoming call ringtone will play to the stereo headset and the phone will not ring at all, (its as though the ringtone is diverted to the phone)
but if i switch it to headset mode (not A2DP), the ringtone will play on the phone and the headset with play a beep sound for incoming call.
how do i fix this?? I want it to be connected to a2dp and yet the ringtone still ring on my dopod phone...

I havent found away to fix this but every windows phone i have used will route all sound to the head set when using a2dp, but the intresting thing is that when i installed microsoft voice command it would play through the loud speaker

jathomas0910 said:
I havent found away to fix this but every windows phone i have used will route all sound to the head set when using a2dp, but the intresting thing is that when i installed microsoft voice command it would play through the loud speaker
Click to expand...
Click to collapse
hi i dont understand..ms voice command can do wt?

porkchop83 said:
hi i have this a2dp bluetooth problem ? its to do with the a2dp problem
anyway when connected with A2DP mode, all incoming call ringtone will play to the stereo headset and the phone will not ring at all, (its as though the ringtone is diverted to the phone)
but if i switch it to headset mode (not A2DP), the ringtone will play on the phone and the headset with play a beep sound for incoming call.
how do i fix this?? I want it to be connected to a2dp and yet the ringtone still ring on my dopod phone...
Click to expand...
Click to collapse
Under Windows Mobile 5 it worked but not under 6. Under WM5, all phone rings would come thru the external speaker (I liked this) and music thru the A2DP headset. Now under WM6, I get rings and music thru the headset. No phone ring externally. I hate this as I miss calls all the time because the earbuds are not always in my ears. I plan to search for some reg settings tonight (on my own). Anyone had any luck with changing this behavior?

jathomas0910 said:
I havent found away to fix this but every windows phone i have used will route all sound to the head set when using a2dp, but the intresting thing is that when i installed microsoft voice command it would play through the loud speaker
Click to expand...
Click to collapse
Thanks.. Your comments helped to solve my issue.. I always want all audio routed to headset except for "Phone Ring". I want the phone to ring externally because I do not always have my earbuds in my ears therefore I miss calls. On all Faria WM5 roms, the phone would ring on the external speaker but under all WM6 roms (had not used Faria's yet; I am using 3G's) ALL audio is routed to headset including phone ring. It appears the reason Faria's ROM would ring externally is because Voice Command is cooked into the rom and voice command will rout rings externally because of voice notification (even though voice notification does not work in 1.6). I installed Voice Command 1.6 last night and the Phone now rings externally with all other audio routed to my A2DP headset. Been at this for weeks trying to figure out the behavior. I am now completely happy. I have a very stable WM6 ROM and A2DP that behaves the way I want.
L8

species8472_rules said:
Thanks.. Your comments helped to solve my issue.. I always want all audio routed to headset except for "Phone Ring". I want the phone to ring externally because I do not always have my earbuds in my ears therefore I miss calls. On all Faria WM5 roms, the phone would ring on the external speaker but under all WM6 roms (had not used Faria's yet; I am using 3G's) ALL audio is routed to headset including phone ring. It appears the reason Faria's ROM would ring externally is because Voice Command is cooked into the rom and voice command will rout rings externally because of voice notification (even though voice notification does not work in 1.6). I installed Voice Command 1.6 last night and the Phone now rings externally with all other audio routed to my A2DP headset. Been at this for weeks trying to figure out the behavior. I am now completely happy. I have a very stable WM6 ROM and A2DP that behaves the way I want.
L8
Click to expand...
Click to collapse
Suppose I should have provided an update.. It only works on the first phone call after powering on the headset. Once I accept a call via the headset, it nevers rings externally again..

searching Bluetooth Headset (Display / Vibration)

Hi!
First of all, sorry for my english, I'm from germany.
I'm new here, waiting for my O2 Diamond to be released
Therefore I'm searching for a Bluetooth headset. I don't want to carry the Diamond everytime in my trouser pocket but (if I have it with me) in my bag. I hate ringin phones so I'm searching for a headset that could notify me with vibration on incomming calls. Best would be if the headset has a display that shows me who is calling. Can you suggest me some headsets?
It would be terrific if the headset could notify me on incomming SMS / mail. Is that possible?
Regards
Daniel

Jabra bt8010
is a pretty good head set has caller id, 30 number phonebook, silent,vibrate,ring and ringtone from handset, also stereo headset

hi!
Thanks for your reply, I found the bt8010 myself. But I normaly need no stereo headset. I would prefer the bt800 (if I can get it anywhere).
Do you have the bt8010? Which OS is installed on you phone?
Any experiences about the caller id function? Is it possible that the Headset shows the same IDs as in your phonebook of your mobile?
And can someone give me a hint about the SMS / mail notification?

Kenny183 said:
hi!
Thanks for your reply, I found the bt8010 myself. But I normaly need no stereo headset. I would prefer the bt800 (if I can get it anywhere).
Do you have the bt8010? Which OS is installed on you phone?
Any experiences about the caller id function? Is it possible that the Headset shows the same IDs as in your phonebook of your mobile?
And can someone give me a hint about the SMS / mail notification?
Click to expand...
Click to collapse
I believe the BT800 has been discontinued and replaced with the BT8010.
The phonebook/caller ID function is great, but the catch is you have to download the software separately, and manually input the entries into the headset itself, and it can only hold 30 entries.
Anything not in the headset's address book will just display as the number, not the name of the person calling.
You can get the software and such here:
http://www.jabra.com/bt8010
The stereo speaker is detachable, so if you don't want stereo, just don't attach it.
I'm running Windows Mobile 6 on a Moto Q9c, and can't say enough good things about this headset. It has adequate sound quality and noise reduction mic; I've never had someone complain when talking on it.
As for email notification...I doubt it; the headset doesn't alert you when a new text message comes through (though the phone still reacts as normal).

Thanks for your answer Oh SoS
Oh SoS said:
I believe the BT800 has been discontinued and replaced with the BT8010.
Click to expand...
Click to collapse
Yes, I think so. But maybe I can get the BT800 somewhere (eBay or so). Probably that woul be cheaper.
Oh SoS said:
..., but the catch is you have to download the software separately, and manually input the entries into the headset itself, and it can only hold 30 entries.
Anything not in the headset's address book will just display as the number, not the name of the person calling.
Click to expand...
Click to collapse
Are you sure about that? Is it impossible that the display shows the caller ID that is in the mobiles phonebook? or would that maybe work with some phones?
Oh SoS said:
..., and can't say enough good things about this headset. It has adequate sound quality and noise reduction mic; I've never had someone complain when talking on it.
Click to expand...
Click to collapse
I heard only good stuff about Jabra so I think it will be one of them.
Oh SoS said:
As for email notification...I doubt it; the headset doesn't alert you when a new text message comes through (though the phone still reacts as normal).
Click to expand...
Click to collapse
hihi, me too. But it would really be ingenious if that would work. I plan to have the headset the only thing in my pocket, so I would need the vibration of the headset to notice new text messages. I hate ringing phones.

yeah I have the 800, but its uncomfortable to wear for long periods and the display is not that bright. The 8010 can be worn as a mono headset. The 80l0 was a good start but the 8010 is much better, also can connect to 2 phones, not at the same time.

Hi Harry,
as you have the BT800, can you tell me if it notifies you for incoming SMS/mail?
Whit what mobile-phone do you use the BT800?

YABtI - Yet Another Bluetooth Issue

After getting my US TMo TP2 last month I've been pretty sure everything Bt was working properly.
Giving commands is 100%, I can touch the call button on my Moto S9's and say Dial <contact>, or Dial <555-1212> or What are my appointments tommorrow?, etc. and it works great.
I thought notifications were working as well. Calender appt. announced via my S9's and the text to speech was impressive as it read them out to me but something was missing and I just realized what it was. Incoming phone calls were not being announced properly. I did hear it ring and I could press the headset button and take the call just fine but it was the default S9 ring not my ringtone and I did not hear VC announce the number or contact. I was having to look at the phone to see who was calling.
So I went searching XDA and found this post that has just about everything you need to know about MS VC. After reading thru it thoroughly and trying many of the settings and reg tweaks I found out how to make VC announce incoming calls but it will only do so thru the device speaker an not thru Bt Handsfree. I've tried everything in that post that might help but to no avail.
Any one here have any idea?
S

Microsoft are working on it apparently.