car kit Now Fixed !

[Guest Gav-B]

Hi I tried all things I can find but none work. Can anyone help?

HFK=http://www.expansys.com/motorola-hfw8000-bluetooth-car-kit-104292/

Background;

I've got a Motorola HFW8000 (old I know) and had a nokia 6820 which worked well with this kit.

This HFK supports two modes, voice dialling on your phone or it's own tags.

I've only every used my phones voice tagging.

So I pushed the right had button and could speak my voice tag and it would dial the number, great

Could receive call too no problem.

But, since I've now ditched my Nokia and have my SF, I can pair the kits together no problem, I can receive calls no problem just push the blue button as normal, but when I want to make a call I push the 'talk button' on my HFK and nothing. I assume this is because my last phone had a dedicated push to talk button and the SF doesn't?

I tried putting the HFK into voice training mode so I could record voice tags on it and do it that way but it's ignoring command send to from my SF so can't do it this way...

Anyone any ideas I can use my HFK again?

Thanks for any help.....

****FIXED*****

This HFK supports two modes, voice tags stored on the phone or voice tags stored on the HFK. My previous Nokia 6280 supported voice tags on the phone so worked well. My SF doesn't support this. Although there are ways round this as oh!dougal has kindly posted. This method relies on a data connection to process your spoken word though.

I fixed my problem by switching to voice tags on my HFK.

To do this is trivial but a bit time consuming.

1:) you can only programme this HFK with a motorola phone! luckily my wife still had her old phone so I could do this.

2:) you need to create a voice tag for each of your contacts then enter the number to call.

This works well, but if you need to change/add a contact you need to dig out the old motorola...

Edited February 13, 2011 by Gav-B

[Guest Azurren]

Have you got "Google Voice" installed on your device?

Have you tried putting into into "Car mode"? (Its a stock Froyo app)

These may help but I really can't say anything about your bluetooth kit as never owning one ;)

[Guest oh!dougal]

Lots of aspects.

"Voice tags" is IIRC a Nokia thing.

Welcome to the forum and Android.

Android 2.2 opens up the possibility of voice dialling over Bluetooth.

AFAIK you can't do it in 2.1

As to whether you can do it - properly - with 2.2.0 on the SanFran ... I'm still trying!

I have two basic headsets -- a Samsung WEP495 and a Jabra BT2070.

Pressing the big headset button when nothing is going on, produces different effects with each!

The Jabra is ignored.

The Samsung kicks off a last number redial.

Both will answer a ringing call, and end an active one by pressing that button, which is fine.

I've been using the Jabra, but bought the Samsung (cheaply from Orange) because it boasted of its noise cancellation tech (and I couldn't find where I'd set down the Jabra - but it turned up in the end.)

I'm not sure anyone has properly explored BT on the SF.

One person was convinced of differences between Orange's stock stuff and other operators' stock stuff, let alone anything properly custom. (That was trying to use some car-diagnostic thing called IIRC "Torque".)

But it certainly does matter what firmware you have on your phone (you didn't say).

At present I have Seb's DX2 (a 2.2 or "FroYo"), with which I've been using Vlingo (free from Market) for voice control.

Its pretty good.

And does Bluetooth Voice Dialling.

But pressing the headset button will not make Vlingo "listen" (as seems to be the case with some phones and headsets).

You have to tap the button on the phone's screen to start and then wait a second or so while it opens up the BT connection. But after that, its excellent at listening to the BT spoken command and interpreting it. (It uses a data link to their server to process the speech, so some data usage and, especially on a 2g link, some time is consumed. Vlingo also exposes an Android 2.2.0 bug (said to be fixed in 2.2.1 but which we don't yet have) - this causes a phone reboot when you turn off BT (but that's manageable - just pick your moment to turn it off!)

Edited February 5, 2011 by oh!dougal

[Guest Gav-B]

Have you got "Google Voice" installed on your device?

Have you tried putting into into "Car mode"? (Its a stock Froyo app)

These may help but I really can't say anything about your bluetooth kit as never owning one :P

Yes I've got Google voice and have tried car mode, doh, should have put that in OP.

AFAIK pressing 'push to talk button' on my HFK must have triggered the push to talk button on the nokia, but the SF doesn't have that button :-(

I hope there's a way round it....

Many thanks for taking time to reply....:-)

[Guest Gav-B]

Lots of aspects.

Yes, sorry :-)

"Voice tags" is IIRC a Nokia thing.

Cool.

Welcome to the forum and Android.

Many thanks :-)

Android 2.2 opens up the possibility of voice dialling over Bluetooth.

AFAIK you can't do it in 2.1

As to whether you can do it - properly - with 2.2.0 on the SanFran ... I'm still trying!

I have two basic headsets -- a Samsung WEP495 and a Jabra BT2070.

Pressing the big headset button when nothing is going on, produces different effects with each!

The Jabra is ignored.

The Samsung kicks off a last number redial.

Both will answer a ringing call, and end an active one by pressing that button, which is fine.

I've been using the Jabra, but bought the Samsung (cheaply from Orange) because it boasted of its noise cancellation tech (and I couldn't find where I'd set down the Jabra - but it turned up in the end.)

I'm not sure anyone has properly explored BT on the SF.

One person was convinced of differences between Orange's stock stuff and other operators' stock stuff, let alone anything properly custom. (That was trying to use some car-diagnostic thing called IIRC "Torque".)

But it certainly does matter what firmware you have on your phone (you didn't say).

Yes sorry for the omission. I've upgraded to Jellyfish RLS9 so I'm on 2.2 :-)

At present I have Seb's DX2 (a 2.2 or "FroYo"), with which I've been using Vlingo (free from Market) for voice control.

Its pretty good.

And does Bluetooth Voice Dialling.

But pressing the headset button will not make Vlingo "listen" (as seems to be the case with some phones and headsets).

You have to tap the button on the phone's screen to start and then wait a second or so while it opens up the BT connection. But after that, its excellent at listening to the BT spoken command and interpreting it. (It uses a data link to their server to process the speech, so some data usage and, especially on a 2g link, some time is consumed. Vlingo also exposes an Android 2.2.0 bug (said to be fixed in 2.2.1 but which we don't yet have) - this causes a phone reboot when you turn off BT (but that's manageable - just pick your moment to turn it off!)

oh Vlingo sounds promising, pity it needs their servers to decipher

I'll try downloading vlingo now....

Many thanks to you....

Edited February 5, 2011 by Gav-B

[Guest Phoenix Silver]

have you edited audio.conf 2 lines to change ?

[Guest oh!dougal]

... Android 2.2 opens up the possibility of voice dialling over Bluetooth.

AFAIK you can't do it in 2.1

As to whether you can do it - properly - with 2.2.0 on the SanFran ... I'm still trying!

I have two basic headsets -- a Samsung WEP495 and a Jabra BT2070.

Pressing the big headset button when nothing is going on, produces different effects with each!

The Jabra is ignored.

The Samsung kicks off a last number redial.

Both will answer a ringing call, and end an active one by pressing that button, which is fine.

...

At present I have Seb's DX2 (a 2.2 or "FroYo"), with which I've been using Vlingo (free from Market) for voice control.

Its pretty good.

And does Bluetooth Voice Dialling.

But pressing the headset button will not make Vlingo "listen" (as seems to be the case with some phones and headsets).

You have to tap the button on the phone's screen to start and then wait a second or so while it opens up the BT connection. But after that, its excellent at listening to the BT spoken command and interpreting it. ...

Ummm. Seems like I wasn't doing something right ... !

IT WORKS !

Pressing the button on the Jabra SEEMS to be ignored (nothing happens)

BUT

(with Vlingo InCar) when you press the button on the Jabra and then say "Hey, Vlingo!" it wakes up (hearing that over Bluetooth) and does stuff (including voice dialling) over BlueTooth.

IT WORKS !

You do NOT need to tap the screen (or touch the phone), IF you use Vlingo InCar ... (and the Jabra...)

However there may be a new issue in getting the Market to let you have Vlingo.

It won't show it to me on the phone any more, and from the computer the new browser-market says it is not compatible with my "Blade".

But dammit, IT WORKS !

[Guest Gav-B]

Ummm. Seems like I wasn't doing something right ... !

IT WORKS !

Pressing the button on the Jabra SEEMS to be ignored (nothing happens)

BUT

(with Vlingo InCar) when you press the button on the Jabra and then say "Hey, Vlingo!" it wakes up (hearing that over Bluetooth) and does stuff (including voice dialling) over BlueTooth.

IT WORKS !

You do NOT need to tap the screen (or touch the phone), IF you use Vlingo InCar ... (and the Jabra...)

However there may be a new issue in getting the Market to let you have Vlingo.

It won't show it to me on the phone any more, and from the computer the new browser-market says it is not compatible with my "Blade".

But dammit, IT WORKS !

Yes, works for me too, well sort of. I got Vlingo from market ok?

Anyway works but not great, first off you need to have you're phone out of your pocket -and I use a wallet type cover so need to take out of that too coz to wake up Vlingo you need to be speaking to the phone. I'd prefer speaking to my HFK, that's what it's for!

Then as you right said you need to have data enabled on your phone so vlingo can interpret your commands :-(

@Phoenix have you edited audio.conf 2 lines to change ?

And do what, change what?

[Guest oh!dougal]

...

Anyway works but not great, first off you need to have you're phone out of your pocket -and I use a wallet type cover so need to take out of that too coz to wake up Vlingo you need to be speaking to the phone. I'd prefer speaking to my HFK, that's what it's for!

Then as you right said you need to have data enabled on your phone so vlingo can interpret your commands :-(

@Phoenix have you edited audio.conf 2 lines to change ?

And do what, change what?

1/ The point of my last exultant post was that you CAN wake up Vlingo by pressing the headset button and speaking "Hey Vlingo!" over Bluetooth -- but you MUST be in Vlingo InCar for it to work, it doesn't wake up over BT with the main Vlingo app. But in the main Vlingo app, you can start InCar ...

However it ain't going to work properly with my Samsung headset (as it stands) because pressing its button always kicks off a last-number-redial (unless the phone is ringing or in a call).

2/ In a thread I started in this forum, I pointed out that there are two lines 'commented out' in the standard (very bog-standard) Bluetooth audio.conf file that - if they were UN-commented - MIGHT help to make the Blade 'play nicer' with some Bluetooth kit, maybe even my Samsung headset (that being the only other BT thingy I have.) But for now, I have a very usable Jabra. :P

3/ Oh and note that Google's VoiceSearch, etc, also uses a datalink to do the voice recognition in a server farm somewhere in the cloud, rather than in the phone!

Edited February 7, 2011 by oh!dougal

[Guest Gav-B]

1/ The point of my last exultant post was that you CAN wake up Vlingo by pressing the headset button and speaking "Hey Vlingo!" over Bluetooth -- but you MUST be in Vlingo InCar for it to work, it doesn't wake up over BT with the main Vlingo app. But in the main Vlingo app, you can start InCar ...

Ah, pitty it doesn't wake up via BT without intervention first. You know what it's like, you get used to your 'old' system and this seems like a backward step...

However it ain't going to work properly with my Samsung headset (as it stands) because pressing its button always kicks off a last-number-redial (unless the phone is ringing or in a call).

strange....

2/ In a thread I started in this forum, I pointed out that there are two lines 'commented out' in the standard (very bog-standard) Bluetooth audio.conf file that - if they were UN-commented - MIGHT help to make the Blade 'play nicer' with some Bluetooth kit, maybe even my Samsung headset (that being the only other BT thingy I have.) But for now, I have a very usable Jabra. :P

Yes I can see lines commented out...but don't know which do what...?

3/ Oh and note that Google's VoiceSearch, etc, also uses a datalink to do the voice recognition in a server farm somewhere in the cloud, rather than in the phone!

Ahh didn't realise this was the case, many thanks again.

What I really want is when I push my 'talk' button, in then in turn starts up Vlingo car mode......hmmmm

[Guest beatingbigbrother]

The real difference between 'voice tags' and using google voice is that google voice compares your spoken text with a text string AS PRONOUNCED BY AN AMERICAN.

Many foreign names are not spoken correctly by Americans, wit all respect. So...to use google voice for dialling the user is expected TO PRONOUNCE THE NAME AS HE THINKS AN AMERICAN MAY HAVE DONE IT.

Well...that does not work at all. How about a name like "Gerrit van Scheveningen" as pronounced by a Dutchman? When pronounced by an American poor Gerrit would not recognize his own name for sure!

The only answer is to introduce VOICE TAGS to your contacts. A voice command is then simply matched to the tag. The user may pronounce a name anyway he wants, it will be matched when he does it again when dialing. Simple!

I WANT VOICE TAGS FOR MY CONTACTS!

My 5 year old Nokia could do it, no problem, now I have to do a step back with my 'smart'-phone. Somehow this is very very hard to explain to Americans. Must be a cultural, centre of the world view, thing :-\

[Guest oh!dougal]

...

The only answer is to introduce VOICE TAGS to your contacts. A voice command is then simply matched to the tag. The user may pronounce a name anyway he wants, it will be matched when he does it again when dialing. Simple!

I WANT VOICE TAGS FOR MY CONTACTS!

My 5 year old Nokia could do it, no problem, now I have to do a step back with my 'smart'-phone. Somehow this is very very hard to explain to Americans. Must be a cultural, centre of the world view, thing :-\

Not a cultural thing - its a knowledge thing! :P

On the phone open Contacts.

Find Gerrit van Scheveningen

Edit his details.

Just after his last name there is a 'down arrow' button. Tap it.

And - oh look! Now you can enter

Herrid as his "phonetic given name" and

van skay-venning-en as his "phonetic family name"

However that's for a Dutch name in a British-English-speaking phone.

There is even more that you don't know, which makes your complaint that

... google voice compares your spoken text with a text string AS PRONOUNCED BY AN AMERICAN.

Many foreign names are not spoken correctly by Americans, wit all respect. So...to use google voice for dialling the user is expected TO PRONOUNCE THE NAME AS HE THINKS AN AMERICAN MAY HAVE DONE IT.

seem somewhat under informed ...

From the home screen go to Settings. Scroll down and select Voice Input and Output Settings.

If you have Google selected as the Voice recogniser, then when you go to Voice Recogniser settings, you can then choose Language and see that it is not limited to recognising text "AS PRONOUNCED BY AN AMERICAN". as you claimed in Capital Letters! My phone is offering me 27 recogniser language choices ...

I have mine set to English (UK).

And actually I set it to the Vlingo recogniser (which does for now only offer a choice between UK and USA English), because Vlingo seems to work over Bluetooth.

The whole voice recognition thing is quite cool actually. (Even if it does need an internet connection.)

I'm running Seb's DX2 with Vlingo. Trust me, it works fine.

Edited February 11, 2011 by oh!dougal

[Guest beatingbigbrother]

Not a cultural thing - its a knowledge thing! :P

On the phone open Contacts.

Find Gerrit van Scheveningen

Edit his details.

Just after his last name there is a 'down arrow' button. Tap it.

And - oh look! Now you can enter

Herrid as his "phonetic given name" and

van skay-venning-en as his "phonetic family name"

However that's for a Dutch name in a British-English-speaking phone.

There is even more that you don't know, which makes your complaint that seem somewhat under informed ...

From the home screen go to Settings. Scroll down and select Voice Input and Output Settings.

If you have Google selected as the Voice recogniser, then when you go to Voice Recogniser settings, you can then choose Language and see that it is not limited to recognising text "AS PRONOUNCED BY AN AMERICAN". as you claimed in Capital Letters! My phone is offering me 27 recogniser language choices ...

I have mine set to English (UK).

And actually I set it to the Vlingo recogniser (which does for now only offer a choice between UK and USA English), because Vlingo seems to work over Bluetooth.

The whole voice recognition thing is quite cool actually. (Even if it does need an internet connection.)

I'm running Seb's DX2 with Vlingo. Trust me, it works fine.

Ha I almost thought you got me! But regretfully that is not the case (at least not entirely :-))

Take the "phonetic family name", for a Dutchman "Gerrit" does not need any explanation. By filling in a "phonetic family name" I have to enter a string SO THAT AN AMERICAN WILL PRONOUNCE IT LIKE SOMETHING APPROACHING DUTCH. Meaning it is still all from the american perspective! I don't want to be forced to think like an american when all I need is a voice tag. Then anybody can speak whatever they want and the system can blindly recognize it, not by trying to translate it into a string, but simply by pattern matching. Nokia did exactly what is needed.

But...the 'recognizer languages' is an avenue I will investigate and see where it gets me. Just an idea: these approaches may be combined. The system should try to match first with explicit voice tags assigned to a string, and only then apply its recognizer logic. Voice tags as helpfull hints for the recognizer...

Anyway, thanks a lot for your comments. For the moment I need my ZTE Blade to use my bluetooth car link and actually make the call I want with voice activation. Tomorrow I'll jump on the recognizer languages...

[Guest beatingbigbrother]

Ha I almost thought you got me! But regretfully that is not the case (at least not entirely :-))

Take the "phonetic family name", for a Dutchman "Gerrit" does not need any explanation. By filling in a "phonetic family name" I have to enter a string SO THAT AN AMERICAN WILL PRONOUNCE IT LIKE SOMETHING APPROACHING DUTCH. Meaning it is still all from the american perspective! I don't want to be forced to think like an american when all I need is a voice tag. Then anybody can speak whatever they want and the system can blindly recognize it, not by trying to translate it into a string, but simply by pattern matching. Nokia did exactly what is needed.

But...the 'recognizer languages' is an avenue I will investigate and see where it gets me. Just an idea: these approaches may be combined. The system should try to match first with explicit voice tags assigned to a string, and only then apply its recognizer logic. Voice tags as helpfull hints for the recognizer...

Anyway, thanks a lot for your comments. For the moment I need my ZTE Blade to use my bluetooth car link and actually make the call I want with voice activation. Tomorrow I'll jump on the recognizer languages...

Hmmm. The recognizer language was already set to Dutch, well... couldn't tell the difference. Put in some easy dutch contact names like 'joop' and it suggested to call the police! Have to make do with selecting a contact on my car screen - the bluetooth connection works ok. Nice try! :-)

[Guest Bump Here]

I use a THB Bury 9060CC for my Bluetooth kit. It handles all the voice tag element and just passes BT instructions to the handset. Sorts out all the problems and means I don't have to load different profiles as I have both a personal and work phone connected to it most of the time.

[Guest beatingbigbrother]

I use a THB Bury 9060CC for my Bluetooth kit. It handles all the voice tag element and just passes BT instructions to the handset. Sorts out all the problems and means I don't have to load different profiles as I have both a personal and work phone connected to it most of the time.

Ha this is the app. Explicit linking a voice tag to a contact. This is the functionality we need!

http://www.androidzoom.com/android_applica...-dial_taaz.html

But...have to try it first.

Edited March 6, 2011 by beatingbigbrother