Database Users

play sound through speaker and/or headset?

I want to be able to play sounds through the normal speaker, even though a headset is attached to the device (Blue Angel, in this case).
(The built-in telephone does this with its ring tones when a headset is attached.)
Only one WaveOut device is shown as present.
Anyone has a solution, or an idea?

nobody knows anything about this?

there's physical switch that disables the speaker after you plug in the earphones jack. its PHYSICAL, no amount of code will overcome this.

hey!!.. screw the last post. I managed to do what you wanted.
speaker + headset both rings, even when headset is connected... let me fix the code, then I will get back to you... ok

I'm waiting patiently!

Hi esbjorn,
din want to keep you waiting. but i think i finally found out exactly is going on.
there's only 1 device. however, the device enables both speaker and headset WHEN THERE'S AN INCOMING CALL, which you already know. Whether its hardware or software, I have yet to determine it.
I had a lot of code around and got confused. sorry if I gave you any false hope.
anyway, this is my hypothesis, windows has code to control only this 1 waveout device. when a call comes in, it decreases the volume of all sounds being played. it then plays the ringtone at a volume based on its registry. (try changing the attentuation in SoundCategories->Ring) it gives the effect (a loud ringtone and soft background audio) that there are actually 2 waveOut devices when there's only 1.
I will be working on it further, let me know if you make progress too.

How to prevent OS from muting audio output when making a phone call

I'm working with an app running at Windows Mobile 5.0 pocket pc. And I
use 'waveout' functions to play some audio file, sometimes my app need
to automatically make some phone call using TAPI. Here comes the OS
behavior which I don't want: the audio output is somehow muted. I want
the audio output keeps the same volume, is there any way do it? Thanks
a lot!

When call is in progress, audio path is changed. This is a hardware feature (you can read about it in many posts about answering machines).
Currently there is nothing that can be done about this.

I had not actually tested this so I gave it a go. No sound gets through when I programmatically play a sound or when I use the media player. I belive Levnum is correct because when I play a sound and hang up the phone during the play back, the sound returns but is choppy for an instant. That would be caused by the path of the audio being switched. When i programatically change volume it is normally very clean, eg loud to soft but with not noise between.
a bit off topic...
One thing that bothers me about this isolation of the phone audio hardware is the presence of the GSM 6.0 input properties for the microphone. If the hardware is truly isolated from the system then why have this sampling format? Wouldn't the phone be doing its own sampling and not need windows to have this capablity?

What a bad news! Thank you anyway.

experimenting with the volume during a call
In June played a lot with audio levels on my hp h6315 while using TAPI and recorded my results. The 6315 isn’t an HTC device but I think it probably works similarly. I have a wizard too, but haven’t experimented as much with it.
Here are my notes that I typed when I did it:
(perhaps they will be useful to someone)
[size=+2] Playing wave stream while establishing a GSM call using built-in phone software[/size]
Inbound GSM call with ear bud (speaker and phone volume low setting)
Sound continues through ringing
Sound cuts out for ~1 second after selecting answer
Sound continues mixed with call
After call hang-up sound still continues
Inbound GSM call without ear bud (speaker and phone volume highest setting)
Sound switches to a lower setting (front speaker?)
After selecting answer, sound changes momentarily to high
Then Sound cuts out for ~1 second
Sound then resumes at lower level
If phone is put on speakerphone the sound goes to high level
Sound continues mixed with call
After call hang-up, with call on speakerphone, sound continues after a brief interruption
After call hang-up, sound reverts to loud and continues. There is a gap as in Speakerphone case, but it isn’t as noticeable since the change in volume helps to mask it.
Outbound GSM call with ear bud (speaker and phone volume low setting)
Sound is interrupted for about 1-2 seconds after hitting talk
Sound then continues through answer and hang-up. (mixed with call)
Outbound GSM call without ear bud (speaker and phone volume highest setting)
Sound is interrupted for about 1 seconds after hitting talk
Sound resumes at lower volume through call
Sound has brief interruption at hang-up while on speakerphone.
Sound reverts to higher volume after small gap at hang-up while not on speakerphone
[size=+2]Recording while establishing a GSM call using built-in phone software[/size]
Inbound GSM call with ear bud (mic on gain 5)
Recording continues through ringing
Slight break while answering then resume for brief time then changes to much lower gain.
Remains at lower gain
Inbound GSM call with ear bud (mic on gain 1)
Same as mic gain on 5, didn’t seem any quiter, also same with mic on AGC
OutBound GSM call with ear bud (mic on gain 5)
Slight break after pressing talk then resume for brief time then changes to much lower gain.
Remains at lower gain
Click to expand...
Click to collapse
I think my largest problem was the microphone gain, but I don’t remember for sure. On my typical volume settings, the cases where the volume level lowers, it often lowered so much that I couldn’t hear it without listening very carefully. Originally, I thought it was totally muted.
To help minimize the change in volume level, try adjusting the regular system volume to a relatively low level and put the phone volume on max. This helps some, but to fix the problem try multiplied the audio samples by 2 or more before playing them to the speaker. Find the best multiplication factor by trial and error.
Of course, your’s may be different.
For the off topic part, I thought the audio path for the microphone always was available to windows mobile and only the audio to the “telephone receiver” wasn’t.. There is only one microphone, but two speakers. The main system speaker is the one that you use to play wave files. The “telephone receiver” is the one that as far as I now is only used for telephone calls. I expect that this telephone receiver speaker is connected directly to the GSM chipset. I think when put on speaker phone the sound goes out through the main speaker. (I don’t have my phone with me so I can’t check right now)

Yes that is what I think as well. So if the phone "chip" is recording/playing the sound using the same hardware why dose windows need to be able to sample at that rate? Its the phone that needs to do the smapling.
The drivers on individual devices can vary a lot when it comes to sound. For example, on some of my devices playback will comence as soon as I add buffers that are appropriately prepared. This is not correct behaviour - the driver should wait for the waveOutWrite before it starts. On other devices the driver continues playing until a buffer is finished even if the waveOutReset is called. When it comes to setting the volume with waveOutSetVolume I have has more varying results on just about every device. Because of this I think it is not very usefull to spend a lot of time perfecting code for this sort of thing. Even if as a programmer you do everything correct its going to sound wrong somewhere.

If the phone can stream the call to and from a bluetooth headset then doesn't this mean the in call audio is accessible programmatically somehow?
Or am i missing something

Actually there was a theory floating around that if you could create a 'fake' / virtual BT driver you could capture and send sound from and to the phone.
As far as I know no one on this forum has done this.
It should be noted that some companies like gigabyte are producing phones with built in answering machines.
I think the hardware separation thing may just be an HTC thing and even then only for certain models.

reddreamster -
If you just want to play the audio to the user at the local end, and not down the phone line it is possible. As the others have said HTC keep the phone and local audio completely separate, so you can't play the audio down the phone.
Calling TerminateProcess to kill off cprog.exe can reduce the amount the system interferes in your TAPI calls ;-)
But to re-enable the local audio output this will probably not be enough. You need to call entry point 218 in \Windows\ossvcs.dll
This function takes 1 DWORD parameter, and you should pass the value 1.
I can't remember the return details, but it can be treated as a boolean:
if (return_code)
{ it succeeded }
Make this call AFTER you have made the TAPI connection, and it will re-enable the local audio output.
Hope that helps
Stuart

Solution
Microsoft published the anwser to this in Jan (2007). It's probably no longer of interest to reddreamster, but I thought I would publish a link to the answer in hopes that I might help the next person with the same question that manages to find this thread.
http://blogs.msdn.com/medmedia/archive/2007/01/04/the-wavedev2-gainclass-implementation.aspx
Also, you might be interested in this about the Mixers
http://blogs.msdn.com/medmedia/archive/2007/01/12/what-do-you-mean-by-mixer.aspx
Keywords that might have helped you find this:
mixer api mixerapi wave api waveapi tapi wavedev2 audio gain gainclass volume waveOutMessage waveOutSetVolume wave device

levenum said:
Actually there was a theory floating around that if you could create a 'fake' / virtual BT driver you could capture and send sound from and to the phone.
As far as I know no one on this forum has done this.
It should be noted that some companies like gigabyte are producing phones with built in answering machines.
I think the hardware separation thing may just be an HTC thing and even then only for certain models.
Click to expand...
Click to collapse
Yes there was a theory. And here is the final answer to that too:
http://teksoftco.com/forum/viewtopic.php?t=34&start=15
We had another attempt of making PhoneREC possible - by intercepting the voice flowing through the BT driver when a Bluetooth headset is connected:
1) when a call is established, the software would have enabled voice routing to Bluetooth headset
2) if a headset was not present, it would have been emulated (to be able to use the device without headsets with phonerec too)
3) voice data over bluetooth would have been in the form of SCO packets
4) our software would have intercepted the SCO packets, extract the voice data, record it to a file, and play it on the device's speaker (so no need of using the headset to hear the other party in the call)
Unfortunatelly this failed too, as the SCO packets are handled in the hardware, so we found no way of capturing those from a software program.
The only remaining option is to use a custom made wired headset with PhoneREC. This works and assures high fidelity sound for both parties, but the phoneREC user can only record the phone call by using the special wired headset.
Click to expand...
Click to collapse
So consider the subject closed, and sorry for the bad news,
Radu

playing audio thru phone's speaker

greetinz,
Whether the subj. is possible on WM? I'm wondered if it is possible to make good VoIP-software that will output the audio not thru the external (loud) speaker (that plays music and ring sounds), but thru the phone's conventional voice-speaker. It's quite awkward to turn round the phone to make a call
p.s. i found that there's only one wave device, so the solution is somewhere else

i dont believe so i believe that the pda phones at least from htc
are a audioWise a pda and a phone in the same device with each their
output
which seem to be why people cant record phone conversation well or make auto answering machines

Touch screen issue and headset question

Hey, just got my new wizard. Flashed it up with the slim edition of 6.1 which works very nicely, no stability problems so far, and very quick responsiveness..
anyway, I have 2 questions:
- When I first recieved it, I couldn't get past the calibration screen, it registered the screen tap on the first screen "tap here to begin" but after that I couldn't get it to pick up the tap in the center. I found I had to tap somewhere else in the screen to get it to work. I eventually found a spot "near" the center that registered enough (and did the 4 corners accurately) that it let me pass. When I did that the accuracy of the touch screen was horrible, BUT it did work all across the screen (in the notes program I could draw all over, the lines were not exactly where I drew, but they worked all over the screen). Later I learned that tapping the screen with a larger tip (my fingernail) worked perfectly even in the calibration program, but using the fine pointed stylus does not work... Very strange. Any suggestions about this? I see replacement touch screens on ebay for like $12, so would it make sense to pick one of these up?
- Second question, if I am using headphones (With an adapter to the smaller plug) to listen to MP3s. It pauses the music and rings through the headphones. That is great... I take the headphones off and answer the call. But I decided to see if I could answer with the headphones on, and hear the caller through the headphones, and speak back into the phone as normal (using the builtin mic, since my headphones are not a phone headset, just regular earbud headphones). When I answer the call I can hear the caller, but they cannot hear me. However if I can hear myself through the headphones, so the device is still picking up the speaker, it simply isn't passing on the audio to the other end. Also if I unplug the headphones, they can hear me, then if I plug them back in mid call, they can still hear me now... So this leads me to believe it is a software issue that can be potentially fixed. Does anyone know of a hack/change/update/registry key that I can use to change this behavior so I can use my regular (higher quality) headphones to listen to music, and just speak into the phone normally when a call comes in (without taking off headphones)
Thanks!

Theory: Two way Call Recording

Our HD2 can not do Two way Call Recording by default.
However:
rule 1: Samsung Omnia II Can do Two way Call Recording by tweaking registry
rule 2: Samsung Omnia II have a Hacked Sense ROM
now...
If Samsung Omnia II + Hacked Sense ROM + Two way Call Recording Registry Tweak
can do two way recording
Then
WM 6.5 disable HD2 two way call recording on purpose OR HD2 missing some system file OR HD2 need to replace some system file from Samsung Omnia II ?
ELSE
The HD2 Sense disable two way call recording on purpose? How about Samsung Omnia II disable sense UI, can it do two way recording ?
I don't have Samsung Omnia II, can not do the test...
Please help if you can.

htc disabled it because they don't agree with silent recording (which has legal implications in some countries).

If someone have both phone, they can confirme that.

Mine works!
dwin said:
If someone have both phone, they can confirme that.
Click to expand...
Click to collapse
My HD2 DOES record both ways when using Resco Audio Recorder. My outgoing voice is crystal clear, while the incoming voice is just slightly more quiet (but very easily understood).

PeterHTC said:
My HD2 DOES record both ways when using Resco Audio Recorder. My outgoing voice is crystal clear, while the incoming voice is just slightly more quiet (but very easily understood).
Click to expand...
Click to collapse
The easiest way to test if its actually recording properly or just picking up the mic through the speakers is to try recording whilst the headset is plugged in. If the incoming recorded voice level is the same with the headset plugged in (and in your ear so there is no chance feedback) then you have an element of proper 2 way recording.
If I have the time I may flash some different bases and see how they compare.
Mark.

mskip said:
The easiest way to test if its actually recording properly or just picking up the mic through the speakers is to try recording whilst the headset is plugged in. If the incoming recorded voice level is the same with the headset plugged in (and in your ear so there is no chance feedback) then you have an element of proper 2 way recording.
If I have the time I may flash some different bases and see how they compare.
Mark.
Click to expand...
Click to collapse
I'll try plugging in a headset and let you know. Give me a few hours. Guests just arrived.
Peter

I was wrong!
PeterHTC said:
I'll try plugging in a headset and let you know. Give me a few hours. Guests just arrived.
Peter
Click to expand...
Click to collapse
I was wrong! I connected a headset, made a phone call, and ONLY my outgoing voice was recorded. The incoming "caller" was NOT recorded.
Forgive me.

Vito Audio notes works like charm on hd2

equalness said:
Vito Audio notes works like charm on hd2
Click to expand...
Click to collapse
are you really sure? there are a number of ongoing threads about this and the consensus seems to be that when you test it, you make a call to your landline in a nice quiet room, and its actually picking up there other end through your mic.
try starting to record, then call your mobile so you get an engaged tone, maybe have tv in background, when you listen back, not a trace of engaged tone.

equalness said:
Vito Audio notes works like charm on hd2
Click to expand...
Click to collapse
Can you repeat the test from post5?
Mark.

RiAySoft makes Auto Phone Call Recorder (v.1.30) which I works really well on my HD2. Incoming call recording is direct and doesn't rely at all on the microphone. I had to pay a few bucks for it though but it's well worth it if you need it. Link below. http://riaysoft.perso.sfr.fr/en/?Windows_Phone:Phone_Call_Recorder

doesn't mention hd2 in compatibility list, have you tried it with the headset?

Yes, please plugin your 3.5mm Headset which you use to listen to music,
and make a call, see if both side is recored,
if yes, great news.

Try the free demo!
I don't know what I've done with the original headset I use my own earphones but go to the download site and just install it. It's an unregistered version with some reduced functionality I believe but it ought to be enough to test the earpiece out.

stammerx said:
RiAySoft makes Auto Phone Call Recorder (v.1.30) which I works really well on my HD2. Incoming call recording is direct and doesn't rely at all on the microphone. I had to pay a few bucks for it though but it's well worth it if you need it. Link below. http://riaysoft.perso.sfr.fr/en/?Windows_Phone:Phone_Call_Recorder
Click to expand...
Click to collapse
same problem.it's picking it up through the mic. with the head set theres nothing from the other end, and to be fair this end is pretty faint through the wired mic.
the open mic is pretty good,I can see how you wouldthink it's working correctly.

Try covering the mic
Here's what I did before:
Try getting someone to help you make a test call without the earpiece in. Next try covering the mic while the other party is talking and you won't hear the difference when you play back the recorded file. On the other hand if you were to cover the mic whilst you were speaking into the hd2 you'd get an audible drop in volume.
I have also considered the fact that the mic might be picking up vibrations through the phones body (this would in reality be very unclear because phone mics are designed to pick up modulations in air waves which move much slower than they do through solids). Another quick test to prove this would be to compare the relative volumes of recorded audio using both different programs. Unless ACR has code artificially reducing the volume of incoming sound (doubt this) then both software should demonstrate similar results.
My guess is that the earpiece might require yet another set of code to enable recording of the rerouted audio.

my take is that it is carrying through the body to the mic, my reasoninhg being that even if you cover the earpiece, the ambient sound of the caller is still pretty clear.it almost sounds like its coming out of the back speaker too. maybe the rigid glass makes the sound carry without too much distortion.
someone will figure it out, its not s priority for me,I can wait.