Jump to content


Microsoft Voice Commander and Bluetooth

- - - - -

  • Please log in to reply
11 replies to this topic

#1
pcbinternet

pcbinternet

    Newbie

  • Members
  • Pip
  • 38 posts
Hello, i have installed Voice commander on my Omnia and it all works fine from the the hardware button on the phone, however when using it via my bluetooth headset which is a BT8040 when i press the button on the headset the headset clicks as normal when voice dialling and the microphone symbol comes on the phone waiting for my command but when i say anything it is not picked up by the voice commander software. I also do not hear the beeps that Voice commander makes when starting up so obviously the internal speaker on the phone is being disconnected but i hear nothing and Voice Commander does not hear me. I have tried it with the option for wireless stereo on and off on the headset with the same effect. Has anybody had this problem and discovered a solution for this please?

Thanks

Paul


#2
efjay

efjay

    Diehard

  • Members
  • PipPipPipPip
  • 318 posts
Same problem, no idea how to fix it.


#3
blackhorse

blackhorse

    Diehard

  • Members
  • PipPipPipPip
  • 427 posts
  • Location:Harrogate
  • Devices:HTC Hero, HTC Touch HD
hmmm wrong thread! lol

Edited by blackhorse, 24 August 2008 - 07:45 PM.


#4
billbo

billbo

    Newbie

  • Members
  • Pip
  • 44 posts
  • Devices:Sasmung Omnia
I have the same problem!
Is there any solution yet?
Thanks!


#5
billbo

billbo

    Newbie

  • Members
  • Pip
  • 44 posts
  • Devices:Sasmung Omnia

View Postbillbo, on Sep 14 2008, 14:23, said:

I have the same problem!
Is there any solution yet?
Thanks!

Any news on this problem?


#6
CashMonkey

CashMonkey

    Newbie

  • Members
  • Pip
  • 27 posts

View Postbillbo, on Sep 17 2008, 08:46, said:

Any news on this problem?


Yeah, same issue here - nokia N95 has nil issue...what we should hear is the beep in our b/tooth headset asking us for the name etc....I have th grab the phone and press hardware button there.


#7
efjay

efjay

    Diehard

  • Members
  • PipPipPipPip
  • 318 posts
don't think this will ever be fixed by samsung, they don't seem as proficient as HTC in building a good WM rom.


#8
lastnikita

lastnikita

    Addict

  • Members
  • PipPipPipPipPip
  • 567 posts
  • Devices:Samsung Galaxy S
LOL, looks like you don't know about the many problems HTC never corrected ;)
Samsung is much more active up now with their rom updates.


#9
epicurean

epicurean

    Newbie

  • Members
  • Pip
  • 4 posts
  • Devices:Eten M600

View Postefjay, on Sep 17 2008, 19:22, said:

don't think this will ever be fixed by samsung, they don't seem as proficient as HTC in building a good WM rom.

Even so, I cannot understand why Samsung are unable to reconcile the bt stacks in its many firmware to enable such a popular WM program to work as its suppose to.

Has anyone tried Vito's Voice2go with the Omnia?


#10
lastnikita

lastnikita

    Addict

  • Members
  • PipPipPipPipPip
  • 567 posts
  • Devices:Samsung Galaxy S

View Postepicurean, on Sep 17 2008, 13:32, said:

Even so, I cannot understand why Samsung are unable to reconcile the bt stacks in its many firmware to enable such a popular WM program to work as its suppose to
Maybe because no one reported back that bug to samsung ?
I guess many person will complain on forum rather than complain directly to the manufacturer....
the danger of internet ;)


#11
msjfb

msjfb

    Regular

  • MoDaCo Ad Free
  • PipPip
  • 83 posts
  • Gender:Male
  • Devices:Samsung Galaxy Sii

View Postepicurean, on Sep 17 2008, 11:32, said:

Even so, I cannot understand why Samsung are unable to reconcile the bt stacks in its many firmware to enable such a popular WM program to work as its suppose to.

Has anyone tried Vito's Voice2go with the Omnia?

I have tried multiple builds of Voice Command, Voice2Go and Cyberon Voice Commander. None of them work.
In my previous PPC phone (Asus P525) VC would not work, but the ROM had VoiceCommander (not very good)  built-in. So I just renamed and copied over the exe and all was well... No such luck with the Omnia so far...

This bug and the inability to 'kill' the screen lock function (every 10 seconds) during a call is really starting to make me wonder if I will keep my Omnia long term.  I am keeping a close eye on the soon to be released Galaxy7 from Asus... In all my PDA phones prior to the Omnia (SE P800, P900, ETEN M600, M600+, ASUS P525) the Asus was by far the best phone I had ( excellent build quality, rock solid ROMS (and cooked ROMS), reasonable price).

Is there any official Samsung channel we can use to submit these legitimate concerns?


#12
efjay

efjay

    Diehard

  • Members
  • PipPipPipPip
  • 318 posts

View Postlastnikita, on Sep 17 2008, 07:32, said:

LOL, looks like you don't know about the many problems HTC never corrected ;)
Samsung is much more active up now with their rom updates.

Actually before the Omnia I have previously owned HTC devices - imate Smartphone 2, Blue Angel, Tytn, Excalibur (T-Mobile Dash) and O2 XDA Orbit. I never had any glaring issue that was not resolved. Samsung on the other hand managed to release a device in 2008 which does not support BT voice dialling and have the gall to say the phone has everything. And as for Samsung being more active with rom updates I think that is an illusion, HTC have released more updates for the Diamond recently and have got it to a state that people are now happy with its performance, the Omnia has had only 1 official internet update and several minor service center updates and still there are problems with battery drain, screen responsiveness all while running the seemingly high risk of bricking your phone while updating. I think Samsung has a long way to go with their WM offerings.





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users