110 replies to this topic

[lufeig]

thanks guys! you helped me saving some money!!!

US$ 39.00 in brazil is something like US$ 80.00 would be for north american citizens!!!

[vincentvan]

msjfb, on Nov 27 2008, 05:02, said:

I remember when I first got my Omnia I spoke to these people, and they told me that essentially the text is generic and they did not in fact test VC with the Omnia. The same text is repeated depending on which device you choose...

However, VC version 6 will (and does for me) work with the Omnia in this fashion:

- If you initiate VC with a hard button on the phone, it will start using the Omnia Speaker and microphone (NOT the headset). If it is quiet VC will understand your commands and initiate a call. At that point, audio is transferred to your headset and you can continue normally.

If you use a Stereo BT headset (I tried it with a Jabra BT-8010), you get a little extra: after pressing the button on the Omnia to initiate VC, you hear all the audio generated by VC in your headset , but the BT microphone is still not turned on. Also, if you ask something like "What time is it" you will hear the VC answer in your headset (providing it is quiet enough for the Omnia microphone to pick up your command). So it is a little better than with a mono headset, but the microphone is still not turned on until a call is connected.

It is a problem with the BT Stack and it apparently took Samsung one year to solve this very same problem on the BlackJack...

BTW, HH1/HG5 refers to the firmware (ROM) version of your phone. VC will behave the way described here whatever your frimware revision (up to now).

Hope this helps.

Oh yes man, it sure helped a lot.
Thanks so much.
I think I'll give VC a try then.
If it's good enough for you I reckon I can live with it until Samsung gets its act together.

One more thing , if you don't mind: since I have to buy VC on line (probably from your link) and therefor download it on a pc before transfer it to the Omnia, is there any particular procedure or  trick you would suggest?
How did you go about installing VC on your Omnia? And did you have to change some setting after installation to make it work?

Thanx again man, I hope I'll be able to be of some help to you too someday.

[savedid]

kslakhani, on Oct 4 2008, 21:22, said:

I have tried with Jetware 1.31 BT HFP extension, it has a option to use voice command or any voice dial soft, it activates the voice dialing but doesnt listen to your voice through headset.

Have you guys notice one more thing missing in Omnia setting/system Microphone AGC which you can find in HTC devices

its not a bluetooth problem but its a Microphone bc if you use wired or wireless headset nothing happen.

Its really bugging you have a nice Gadget but a very small feature doesnt work

I tried it on the wired headset and it works, so likely problem with bluetooth.
I also have same problem on omnia with HBH-DS200 bt headset. the button on the headset activates
the voice command and an icon shows, but dosnt then accept commands from even handset which is strange.
only if u use the handset vc button then it accepts commands from handset only.
any luck guys please lets know

Edited by savedid, 01 December 2008 - 11:08 AM.

[mkc_vx]

lufeig, on Nov 26 2008, 03:39, said:

has anybody tried this?

http://samsung-omnia.....voice command
:
:
:
:

Look dude I bought it from them for 40 bux and here is the info:

They allow you to download its Installer and it installs thru ActiveSync.

Once the installation begins Windows XP temp dir(you can access temp dir by typing %TMP% inside RUN in the Start Menu) has a folder named \_isA9 which has the following 4 files:

0x0809.ini
Setup.INI
_ISMSIDEL.INI
Microsoft Voice Command UK PPC 1.60 for M2M.msi

looking inside Setup.INI reveals that this version of MSVC is probably the latest 1.60.4630.0

To run MSVC on the Omnia you press the Main Menu button then it shows a small mic icon in the taskbar and beeps once and if you say "what can I say?" it reads you a help menu.

MSVC 1.6 does run ok on the Omnia.

My BlueTooth headset is Belkin F8T064UKHP while it is paired and working fine with the Omnia.

MSVC 1.6 did not work with it! Which is pissing me off a lot!!!

I think I am gonna return it to Handster and get my money back.

Forgot to mention that my ROM version was HJ1

Regards

Edited by mkc_vx, 01 December 2008 - 03:14 PM.

[savedid]

mkc_vx, on Dec 1 2008, 15:11, said:

MSVC 1.6 does run ok on the Omnia.

My BlueTooth headset is Belkin F8T064UKHP while it is paired and working fine with the Omnia.

MSVC 1.6 did not work with it! Which is pissing me off a lot!!!

I think I am gonna return it to Handster and get my money back.

Forgot to mention that my ROM version was HJ1

Regards

I am very interested in knowing how handster respond to such queries. Did they give u refund ?
do they agree that it should work with bt ?

[twentyone]

Sorry guys, a little off topic, but since you partly discuss MS Voice Command, anyone know how to make the button of the standard wired omnia handsfree as the "voice command button". I have ran out of ideas and I don't want to use a button on the phone itself as it kinda defeats the purpose of the whole program.

Thank you in advance

[Chris64]

[See all my answers in Vodafone forums and on different other forums (use google to find) Cyberon Voice Speed Dial works on the Omnia (you can ad voice tags to contacts - and then do voice dialing) BUT the function doesn't transfer to a Blue Tooth device (in other words you cannot do Voice dialing from your BT device. I have tried all 3rd party software and NO one allows you to do voice dialing from your BT.]

Same problem here.

I tried 2 phones & 3 headsets.

This is the problem of OMNIA.


Nobody???

[bobobird]

No solution unless samsung do something in the rom.

Chris64, on Jan 29 2009, 18:25, said:

[See all my answers in Vodafone forums and on different other forums (use google to find) Cyberon Voice Speed Dial works on the Omnia (you can ad voice tags to contacts - and then do voice dialing) BUT the function doesn't transfer to a Blue Tooth device (in other words you cannot do Voice dialing from your BT device. I have tried all 3rd party software and NO one allows you to do voice dialing from your BT.]

Same problem here.

I tried 2 phones & 3 headsets.

This is the problem of OMNIA.


Nobody???

[kslakhani]

I have read somewhere that they have fixed this in i910 and it works well.
why they dont release any hotfix or patch for this ?????

Let us escalate this issue to Samsung Omnia Team loudly, let us eat their heads together. they might be help us, we are still in hope, arent we????

Can somebody get contact details for Samsung Omnia i900 department so we can request this bug.

Or
can someone figure out how to get and install Widcomm BT Stack in Omnia?

[chokia]

yeah i also  heard  i910 verizon US version ROM has this problem fixed. (They claim the BT headset's mic works and can receive voice command.)

I wish someone can extract the setting or stack or BT module from that ROM and make CAB or cook in their ROM for everyone with non verizon omnia.

Edited by chokia, 02 February 2009 - 12:27 PM.

[dwallersv]

chokia, on Feb 2 2009, 04:25, said:

yeah i also heard i910 verizon US version ROM has this problem fixed. (They claim the BT headset's mic works and can receive voice command.)

I wish someone can extract the setting or stack or BT module from that ROM and make CAB or cook in their ROM for everyone with non verizon omnia.

Confirmed... I have a Verizon 910, and VC works flawlessly with my Plantronics Voyager 855 headset.

It's not because the 855 supports A2DP -- I can turn off that profile, and VC still works exactly as expected with the Handsfree profile.

VC always worked correctly over BT on my TREO 750 with WM6, so it's not that this is inherently buggy or hard to make work. Samsung apparently just screwed it up in the 900, and hasn't fixed it yet.

Edited by dwallersv, 02 February 2009 - 03:57 PM.

[efjay]

Samsung wont fix it, even the leaked roms still have this issue. They are taking the classic stance of ignoring a device once it has been sold to users and concentrating on their next devices.

[nalpt]

This is a major flaw and its a shame Samsung hasn't fixed it, especially since the problem has been solved for i910. It will be an even greater shame if Samsung persists in not patching this issue or solving it with a new rom.

In the mean time, can anyone get a dumped veryzon rom and extract the patch and adapt it to our Omnias?

Any experts out there up to the challenge?

Hope so.

Thanks

[liads]

I've been trying to do just that for the last several days.
Someone posted a dump of the i910 rom around here about a week ago.

I tried copying any changed bluetooth-related dll from the i910 to my i900 (on top of DXIA2), both drivers and OEMApps.
I had to re-pair my headset for it to work, but still no system audio was routed to the BT headset.
Also tried extracting VoiceCommand from that rom, and it didn't play anything other than the notification wave files (and even those were not routed to the headset).
After doing some reading, I checked and noticed that the audio driver is also different, but couldn't get the i910 driver working on the i900.

So far, my guess is that the problem resides in the audio driver (or hardware ), and that I either missed something when trying it on the i900, or that the audio hardware is different on the i910.

When I started I also compared the OEMDrivers registry, and now I have second thoughts about some differences I didn't think were relevant...
I might just give it another try.

Edited by liads, 02 February 2009 - 10:26 PM.

[Chris64]

liads, on Feb 2 2009, 22:24, said:

I've been trying to do just that for the last several days.
Someone posted a dump of the i910 rom around here about a week ago.

I tried copying any changed bluetooth-related dll from the i910 to my i900 (on top of DXIA2), both drivers and OEMApps.
I had to re-pair my headset for it to work, but still no system audio was routed to the BT headset.
Also tried extracting VoiceCommand from that rom, and it didn't play anything other than the notification wave files (and even those were not routed to the headset).
After doing some reading, I checked and noticed that the audio driver is also different, but couldn't get the i910 driver working on the i900.

So far, my guess is that the problem resides in the audio driver (or hardware ), and that I either missed something when trying it on the i900, or that the audio hardware is different on the i910.

When I started I also compared the OEMDrivers registry, and now I have second thoughts about some differences I didn't think were relevant...
I might just give it another try.

I’m crossing my fingers.

Thank you.

[nalpt]

iads: good luck. keep trying, cause were dying for a solution here!
Thanks

[liads]

Thanks
An update:
I disassembled the zylonite_wavedev2.dll of both the i900 and i910 and found a new method in the i910 being called when bluetooth routing events occur, and it does things related to something called "audio path". I think this might be it.
I found out that the i910 dll depend on some new and some updated dlls, which use some new registry settings, which give me headache
I still haven't been able to get the driver working.

Anyone knows about anything special that needs to be done in order to replace a driver?
The i910 drivers are signed with the same certificate, so this shouldn't be a problem.
I hope I'm not overly-optimistic to just copy the i910 driver over the ones in \Windows (hiding the ROM ones)...

[efjay]

liads, on Feb 4 2009, 21:03, said:

Thanks
An update:
I disassembled the zylonite_wavedev2.dll of both the i900 and i910 and found a new method in the i910 being called when bluetooth routing events occur, and it does things related to something called "audio path". I think this might be it.
I found out that the i910 dll depend on some new and some updated dlls, which use some new registry settings, which give me headache
I still haven't been able to get the driver working.

Anyone knows about anything special that needs to be done in order to replace a driver?
The i910 drivers are signed with the same certificate, so this shouldn't be a problem.
I hope I'm not overly-optimistic to just copy the i910 driver over the ones in \Windows (hiding the ROM ones)...

Hello, sounds like you have made some good progress. Try posting in the Omnia rom forum, some of the cooks may be able to help with your question.

[Borbarad]

Hi,

I'm quite new to cooking ROMs.
But I can tell you the following:
You can't just copy the *.dll from the extracted ROM to your phone.

But could you give me/us a list of changed and/or new *.dlls.
Today I'm writing my last exam and perhaps I can figure out, what to do to get it work.
And even if I couldn't find out some of the more skilled cooks have a basis to deal with the problem.

CU,
Borbarad

P.S.: I'm interested how you decompiled the dll. A list of tools or even a small tutorial-site would be great.

[liads]

Borbarad, on Feb 5 2009, 11:15, said:

You can't just copy the *.dll from the extracted ROM to your phone.

Thanks. I get it now. I tried copying the extracted i900 dll over itself in \Windows, and it didn't work either.
I wanted to avoid flashing, but I guess I'll have to cook the i910 driver modules into the rom.

Borbarad, on Feb 5 2009, 11:15, said:

But could you give me/us a list of changed and/or new *.dlls.
Today I'm writing my last exam and perhaps I can figure out, what to do to get it work.

Hope the exam went well
The driver I'm trying to replace is zylonite_wavedev2.dll, which uses MITsSvcs.dll, which uses a different version of DPRAM.dll .
Not sure if the DPRAM.dll changes are important, but some new registry keys are used by MITsSvcs.
The i910 rom can be downloaded from here.

Edited by liads, 07 February 2009 - 09:56 PM.