Voice Dialling Problem

[Guest derharne]

Hi

I have the excellent FLB-Froyo G2(r6) by fibblescan on my SF and it works's great.

I'm not sure if this problem relates just to this ROM or all versions of 2.2.

When I use bluetooth voice dialling it mostly recognises what I am saying, but when dialling out the phone only displays unknown for both the contact and the number. This isn't always a problem if I can hear the voice when it repeats the name back to me, and it is is the correct contact, but the voice is so quiet that I can't always hear it and need to look at the phone to see who it is dialling. Also the voice sometimes says the wrong contact but dials the correct one, for example I say "Call Michelle" the phone voice says "call Michael mobile" then dials michelle.

Does ayone else have the same problem or can anyone help me with it?

Thanks

Edited January 26, 2011 by derharne

[Guest Rotmann]

Maybe

will help?

[Guest oh!dougal]

It sounds :lol: to me as though the poster is ALREADY using Vlingo.

If not, I'd like to know how else "for example I say "Call Michelle" the phone voice says "call Michael mobile" then dials michelle.".

when dialling out the phone only displays unknown for both the contact and the number ...

If Vlingo is not able to recognise your dictation (perhaps because of background noise, or no data link, or whatever), it will say "unknown" -- so it can't dial anyone.

If it then proceeds to dial anyone, then the problem might appear to be with the contacts/dialler system in the BETA rom that the poster is using - and possibly its linkage with the App in question.

I would be asking whether the problems ONLY occur when voice dialling over Bluetooth, or as appears likely, voice dialling in general.

If it were to be only with Bluetooth, I'd be asking about the headset involved, and suggesting that testing be done where there is absolutely no background noise - since that bedevils voice recognition.

I think that a full problem description, including full details (like the version) of the App(s) being used ought to be of interest/concern to the rom developer.

However, I have the impression that Fibblesan is no longer supporting this rom, due largely to people not understanding the meaning of "Beta".

ADDED --

Also the voice sometimes says the wrong contact but dials the correct one, for example I say "Call Michelle" the phone voice says "call Michael mobile" then dials michelle

This is a simple user misunderstanding of Vlingo's action.

That is exactly the way Vlingo works if Michelle's (so-called) 'mobile' is her only number or her default number. To call a non-default number you have to say for example "Call Michelle at Work" ...

And you CANNOT store any number for Michelle in Contacts, without the number having some descriptor - and, yes, "Mobile" is what Android gives you, unless you change it ... so, if you put her landline number alongside the "mobile" tag, then yes, Vlingo will say "Michelle mobile" and dial her landline - but that is your fault, not Vlingo's and not the rom's.

Edited January 26, 2011 by oh!dougal

[Guest derharne]

I don't think I've made myself clear.

The app I'm using is the standard voice dial app the came with the installed rom which I believe is the standard Froyo app, I've never heard of Vlingo.

As I said in my original post most of the time my voice is reognised fine but while the phone is dialling out unknown is shown on the screen so I am unable to see who the phone is calling, even when it does dial the correct number it does not display this.

As for saying the name I said the digitised phone voice says "Michael" not "Michelle" as it should, it is not the saying "mobile" part that I'm concerned about as that is correct, it says the wrong name then dials the correct one. There is no user error at fault the app is doing this.

[Guest Spies]

This is probably happening because of the contacts fix, the voice dialler is probably still trying to reference fields in sql that don't exist.

[Guest oh!dougal]

I don't think I've made myself clear.

The app I'm using is the standard voice dial app the came with the installed rom which I believe is the standard Froyo app, I've never heard of Vlingo.

"Standard" is the bit in question.

You'd need to ask Fibblesan where he got that App. Maybe AOSP sourced?

AFAIK, Android only gets voice dialling with a North American flavour, sorry flavor !

Its not part of ZTE's release ...

As I said in my original post most of the time my voice is reognised fine but while the phone is dialling out unknown is shown on the screen so I am unable to see who the phone is calling, even when it does dial the correct number it does not display this.

This is a matter of integration between the voice dialler and the phone-call software.

Since the rom is Beta, you should report such bugs to Fibblesan.

BTW, I note (from user reviews) that TouchPal's Voice Dialler (in Market), possibly based on the same published source, also shows "unknown" as the call destination. So, this may well be a general problem with the source code that both Fibblesan and TouchPal have used. In which case, its quite probably for Google to fix.

As for saying the name I said the digitised phone voice says "Michael" not "Michelle" as it should, it is not the saying "mobile" part that I'm concerned about as that is correct, it says the wrong name then dials the correct one. There is no user error at fault the app is doing this.

I really don't think Fibblesan or anyone else is going to have much success altering Google's voice pronunciation. You might try entering the name rather more USA-phonetically, like Mee-Shell. It should manage to say that!

"Contacts" has optional fields for entering phonetic versions of names -- my guess would be that this would be why! :lol:

Vlingo (its free) works well, and (as well as voice dialling, texting and emailing, etc) it does dictation into any app (as though it was a keyboard).

BUT -

- it relies on a net connection to process/interpret your speech

- it does not start from a headset-button press. With my headsets and Jellyfish, I need to tap the screen to start.

- it exposes an Android 2.2 bug (said to be fixed in 2.2.1) which reboots the phone if you switch off the headset before Bluetooth!

Edited January 26, 2011 by oh!dougal

[Guest derharne]

Thanks for the advice, appreciated

[Guest Flumpster]

I have exactly the same problem using Pauls latest rom r11.