AKU 3.3 and M$ VoiceCommand 1.6

[NeoCole]

Okay,

How many of you thought AKU 3.3 was going to fix VoiceCommand v1.6? I DID, and so far, it's the same crap. I see no difference in the VoiceCommand 1.6 with this new AKU. I thought for sure I'd start hearing the anouncements over my BT headset.

What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)

I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.

-B

[JohnieWalker007]

Hi,

I also expected AKU 3.3 to solve the problem with MS Voice Command 1.6. But I'm in the same boat as you are. And it's strange because everything was programmed by Microsoft: bluetooth stack, WM Mobile and VC 1.6

[Chatty]

Probably by different teams (AKA left and right hand, if you understand that phrase).

[ebadger]

NeoCole,

What device are you using? The OS doesn't matter if the bluetooth drivers which are written by the OEM aren't supporting audio gateway correctly.


Okay,

How many of you thought AKU 3.3 was going to fix VoiceCommand v1.6? I DID, and so far, it's the same crap. I see no difference in the VoiceCommand 1.6 with this new AKU. I thought for sure I'd start hearing the anouncements over my BT headset.

What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)

I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.

-B

[xcsdm]

Ok, so MS and HTC aren't playing well. And here we get this shiny new upgraded rom. MS and HTC SAY they are working on it, but as long as this issue has existed, I find it hard to believe they have even made the attempt.

This ROM SHOULD have fixed everything, and yet we are stuck.

I personally have given up hope of it ever working correctly (at least by MS or HTC's work) I will continue working on a fix that WORKS 100%, I've been getting closer, but It will take some time.

XCSdM

[szlevi]

What is this problem exactly?

[NeoCole]

NeoCole,

What device are you using? The OS doesn't matter if the bluetooth drivers which are written by the OEM aren't supporting audio gateway correctly.

I'm using the HTC TyTN with AKU 3.3

[NeoCole]

What is this problem exactly?

Have you installed M$ VoiceCommand v1.6?

The problem is with Bluetooth.

The first feature of v1.6 is that you can place calls with a Bluetooth headset. However, when you activate the headset, the audio is still routed through the Pocket PC and not the headset.

The second feature is that notifications are to be routed through the headset. This doesn't happen either. THe headset activates, the audio is still routed through the device.

Microsoft said that it was because of two things, 1. AKU 2.3 is an issue. 2. HTC modded bluetooth stack on AKU 2.3. Both said that feature works with AKU 3.3.

Now that AKU 3.3 is out, nothing has changed. No improvements with Bluetooth Stereo, and no improvements to make VoiceCommand work.

[GliTCH82]

What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)

I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.

-B

I'm having the same problem although I was about to go to AKU 3.3 to try to fix it, I haven't yet. Honestly this is the only thing bugging me about my phone right now.

I have an 8125 with AKU 3.3 that works the way everyone in this thread wants their 8525 to work. Is there anything anyone could suggest looking at for comparison between the two (specific registry keys, etc.) in order to find out what we need to do to make it work?

[jcb_home]

Has anyone tried this with the RUU load of the Cingular ROM. It has a ver different radio that contains the Bluetooth stack?

Just a thought.

[szlevi]

Have you installed M$ VoiceCommand v1.6?

The problem is with Bluetooth.

The first feature of v1.6 is that you can place calls with a Bluetooth headset. However, when you activate the headset, the audio is still routed through the Pocket PC and not the headset.

The second feature is that notifications are to be routed through the headset. This doesn't happen either. THe headset activates, the audio is still routed through the device.

Microsoft said that it was because of two things, 1. AKU 2.3 is an issue. 2. HTC modded bluetooth stack on AKU 2.3. Both said that feature works with AKU 3.3.

Now that AKU 3.3 is out, nothing has changed. No improvements with Bluetooth Stereo, and no improvements to make VoiceCommand work.

I see, thanks. It sounds bad- however I have used mine with a SE headset and IIRC when I tested voice dialing it worked fine... will test it again...

[szlevi]

Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.
I press the top button on the headset, I hear a beep first in my ear then I hear the typical dull 'noise' sound of VSD (both in my ear and from the TyTn), signaling I should start speaking (VSD simultaneously displayed on TyTn), I speak (into my headset), it recognizes and plays it back into my ear and launches the call. When other party picks up we talk via my headset. When we're done, I press the top button on my headset again and call ends.

Isn't this what you're looking for? I mean I understand it's not actually MSVC but in terms of functionality...? What extra MSVC offers if there's any?

[GliTCH82]

Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.
I press the top button on the headset, I hear a beep first in my ear then I hear the typical dull 'noise' sound of VSD (both in my ear and from the TyTn), signaling I should start speaking (VSD simultaneously displayed on TyTn), I speak (into my headset), it recognizes and plays it back into my ear and launches the call. When other party picks up we talk via my headset. When we're done, I press the top button on my headset again and call ends.

Isn't this what you're looking for? I mean I understand it's not actually MSVC but in terms of functionality...? What extra MSVC offers if there's any?

Ok, this is NOT happening for me. I have a Jabra XJ10, a Cingular 8525 with the stock ROM (forget the version but it's 09/2006). I assume the other people in this thread are having the same issue I am, which is, they can speak INTO the headset but the confirmation (the robot voice that asks you "call blah blah at work, or mobile?") does NOT play back through the BT headset. I can only hear it through the built-in speaker.

After it dials, BT audio works properly as usual.

So, once again, everything works except the robotic voice is never played through the BT headset.

[goestoeleven]

The OEM Cyberon dialer is crap -- and it requires voice-tagging all of the contacts you'd like to call.

This is one of the biggest reasons to want to use MSVC...

[dny238]

This is the main thread for Voice Commander 1.6 work. They are discussing AKU 3.3 there as well, might be time to all look in the same spot.

http://forum.xda-developers.com/showthread.php?t=283412

[NeoCole]

This is the main thread for Voice Commander 1.6 work. They are discussing AKU 3.3 there as well, might be time to all look in the same spot.

http://forum.xda-developers.com/showthread.php?t=283412

No one is talking about AKU 3.3 and VoiceCommand in that thread. A new thread that is specific to AKU 3.3 and a TyTN/Hermes is justified. Did you even read that thread?

[johnburn]

Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.


szlevi, the issue is not with the built-in Voice Speed Dial. It's with the after market product Microsoft Voice Command (you have to purchase it separately).

I agree with everyone else. I was under the impression that AKU 3.3 was supposed to fix this, as M$ implied it was an OEM problem. I'm really ticked that HTC haven't fixed it yet. They're becoming even less responsive than ever.

John

[teknics]

Just an observation:

The AKU 3.3 rom is not finished, or even in polished condition. Heck - that's why it's called a LEAK. Why get all bent out of shape about something that isn't finished.

[johnburn]

Just an observation:

The AKU 3.3 rom is not finished, or even in polished condition. Heck - that's why it's called a LEAK. Why get all bent out of shape about something that isn't finished.

You may be correct teknics, but I don't think so. Usually when HTC provides ROMs to carriers for testing, it's the final product that will end up being the shipping version. The only thing that will make HTC release a newer version is if the carrier finds a "show stopper" that will prevent them from releasing that version. A carrier will not retest a version just because it changed from "TEST" to "SHIP", they'll want to see that the version numbers are still the same.

Nevertheless, it's still unexcusable that we have had to wait this long for a fix, whether it is M$'s problem or HTC's.

John

[MrDSL]

I just installed the newest Cingular test rom and VC does work with the hack located in the link above. I am using version 9f. I have not tried notifications but I'm sure they don't work correctly.

[daedalia]

## Double post ##

[daedalia]

There seem to be a few features of AKU 3 that are not present in this ROM. WPA2, lack of CF2 pre-installed, aspects of the bluetooth stack, so it is fair to say it's not worth complaining about a ROM which we were never intended to use. As it says, it is a test. Wait for the final release, I'm sure we wont be disappointed.

For anyone iterested, see below for what should be in AKU3:
http://www.mobile-review.com/pda/articles/wm-aku-en.shtml

[johnburn]

There seem to be a few features of AKU 3 that are not present in this ROM. WPA2, lack of CF2 pre-installed, aspects of the bluetooth stack, so it is fair to say it's not worth complaining about a ROM which we were never intended to use. As it says, it is a test. Wait for the final release, I'm sure we wont be disappointed.

For anyone iterested, see below for what should be in AKU3:
http://www.mobile-review.com/pda/articles/wm-aku-en.shtml

You're correct daedalia, we shouldn't be bitching about something that doesn't exist yet (in theory). It's just that my patience with HTC (and I guess M$) is starting to run very thin. We shouldn't have to wait so long for so many issues to be fixed!

Thanks for the link, very useful indeed. I had seen this before. Unfortunately, his report stops at AKU 3.0, it would be nice to know what is in the post-AKU 3.0 releases.

Regards,
John

[johnburn]

I just installed the newest Cingular test rom and VC does work with the hack located in the link above. I am using version 9f. I have not tried notifications but I'm sure they don't work correctly.

We're all (patiently, or no so patiently as the case may be!) waiting for a fix that does not require the hack to be installed, i.e. it works the way M$ intended it to...

John

[daedalia]

You're correct daedalia, we shouldn't be bitching about something that doesn't exist yet (in theory). It's just that my patience with HTC (and I guess M$) is starting to run very thin. We shouldn't have to wait so long for so many issues to be fixed!

Thanks for the link, very useful indeed. I had seen this before. Unfortunately, his report stops at AKU 3.0, it would be nice to know what is in the post-AKU 3.0 releases.

Regards,
John

I hear you fella and agree. I had the mis-fortune to buy a HTC branded Bluetooth stereo headset, confident that it would be compatible only to find it produces terrible quality sound with the MS Bluetooth stack when compared to other headsets. Hoping the next release will resolve it. We have waited long enough.