I'd like to start by saying that this is NOT critical, but it sure would be handy for some folks. I would like to see an option in the dialer to automatically mute the mic during touch tone generation.
Here's why: On some phones, the speakerphone speaker is very close to the mic. If you're in a call to an automated response system, and speakerphone is activated, and the option to play touch tones is selected, then sound coming from the speakerphone can feed back into the mic, and cause erroneous responses. Of course, you don't SEE this because the display only shows the digits that you pressed.
I discovered this when using a conference calling service. I carefully entered the conference code, and it was displayed properly on the phone, but the system rejected it. Fortunately, the system read back the incorrect entry. In all cases, one or more of the digits was duplicated.
Obviously, there are workarounds. I can turn off speakerphone; I can turn off touch tones, I can cover the mic with my finger, or I can manually mute/un-mute the mic as needed based on what's going on in the call. (And I've determined that all these workarounds do address the issue.)
BUT, how nice would it be to have a dialer setting called something like "Mute mic during touch tones" with possible values of "Never", "Always" and "On Speakerphone". In all likelyhood, this setting need only be applicable if the "Dial pad touch tones" option is enabled.
Thanks for your consideration!
Related
I have added to "my Ring Tones" a couple of tracks which fit the pitch of my hearing (which isn't the best). However, If i change to profile (silent) then return, the factory based ring tones show - not my specifics even though those specifics remain in my RingTones folder.
This phone - which I like, has so many really annoying idiosyncracies. Like defaulting to Touch Keypad when I've set the default to Key Pad!
Would someone tell me what i might be doing wrong - or have left out.
Yhanks
bill
Everything worked fine until I installed MS Voice command 1.6. At first incoming calls would still ring fine, but then I tried to enable the "announce incoming calls" option and instead the phone stopped ringing completely AND also did not announce incoming calls.
I've tried disabling that option, disabling Voice Command altogether, uninstalling Voice Command completely and rebooting, and all without success. Incoming calls produce no ring sound at all, under any circumstances. I've checked and double checked all sound & notification settings, ring volume, settings etc, and nothing makes any difference. Voice command must have changed some registry setting somewhere and I just cannot get it to change back, no matter what I do.
Can anyone help? Is there any way to restore the ring function? The little incoming call window pops up but there is just no ring sound, at all, ever. It works fine when I test/preview the ring under settings, but not when a call comes in!!
paleozord said:
Everything worked fine until I installed MS Voice command 1.6. At first incoming calls would still ring fine, but then I tried to enable the "announce incoming calls" option and instead the phone stopped ringing completely AND also did not announce incoming calls.
I've tried disabling that option, disabling Voice Command altogether, uninstalling Voice Command completely and rebooting, and all without success. Incoming calls produce no ring sound at all, under any circumstances. I've checked and double checked all sound & notification settings, ring volume, settings etc, and nothing makes any difference. Voice command must have changed some registry setting somewhere and I just cannot get it to change back, no matter what I do.
Can anyone help? Is there any way to restore the ring function? The little incoming call window pops up but there is just no ring sound, at all, ever. It works fine when I test/preview the ring under settings, but not when a call comes in!!
Click to expand...
Click to collapse
Have you tried backing up device and then doing a hard reset?
Hi,
I'm searching for a tool, preferably command line driven with options, to do something quite unusual : Set Ring/SMS notifies to "vibrate" but WITHOUT altering the global sound volume.
I recently evaluated PhoneWeaver which is quite neat and highly configurable and I was able to do that. I altered the profiles (night/day) in order to set all notifies to vibrate but at the same time, kept the global volume configuration untouched!
Unfortunately, PhoneWeaver is a bit overkill for what I really need and I don't need a so featured software.
Why would I want that ? Simple... late at night when I go back home, I love listening music with my neat headphones but if I receive a phone call, I want it to be quiet
Setting volume mode to "vibrate" puts the volume at mute level so I can't enjoy my music.
Anyone knows how to achieve that ?
Well,
I've investigated as far as I could and found a partial solution that works for now only for SMS.
Using the amazingly excellent MortScript, I could alter registry to make SMS notification behave like I want :
HKCU\ControlPanel\Notifications\{A877D65B-239C-47a7-9304-0D347F580408}
and set "Options" to DWORD "2" for "Play sound" and "1" for "Vibrate".
Well, it's fine for SMS but I can't get it to work for the Phone part. HKCU\ControlPanel\Notifications\Phone => Options
seems to have NO effect.
Altering HKCU\ControlPanel\Sounds\RingTone0 => Script
to switch between "apw1r" (Play sound) and "av1r" (Vibrate) does not produce a real time effect (only after soft reset).
Anyway, it works when using "Sounds and Notifications" applet directly so it seems that I lack a simple "refresh system" command to make it take these news settings effective.
Any clues on achieving that goal ?
Thanks.
In a meeting kept getting IMs, and the watch beeped every time. It was distracting and I was annoying people in the room so I pulled down the settings and clicked on the speaker icon. The symbol is now the speaker with the line through it but the sound is not Disabled !!!!!!
What can I be doing wrong ? In some situations it is inappropriate for the watch to make sounds but I can not turn sound off.
hello,
never happen to me, I will investigate and if possible give you feedback.
regards
AstroDigital said:
In a meeting kept getting IMs, and the watch beeped every time. It was distracting and I was annoying people in the room so I pulled down the settings and clicked on the speaker icon. The symbol is now the speaker with the line through it but the sound is not Disabled !!!!!!
What can I be doing wrong ? In some situations it is inappropriate for the watch to make sounds but I can not turn sound off.
Click to expand...
Click to collapse
Not sure if you are new in android. Android has 3 volume for adjustment. You need to control them one by one. You mute the media volume, but you will still get sound from notification, or ring.
Check out more audio option in the option menu, not the quick slide down icons.
mcdull said:
Not sure if you are new in android. Android has 3 volume for adjustment. You need to control them one by one. You mute the media volume, but you will still get sound from notification, or ring.
Check out more audio option in the option menu, not the quick slide down icons.
Click to expand...
Click to collapse
It also has One Setting to turn the Speaker On and Off. This is what did not work yesterday.
Turn the Speaker off at the meeting on again when it ends. Easy if it worked
Looks like the App "Feel the Wear" was causing this issue.
The developer updated the app and now turning the speaker off mutes notifications.
I posted yesterday about the facebook app being unable to retain any notification sound I've set for it once the app has been stopped. Well, there is another issue on the same phone. It may be related - I'm not sure. This OS is Android 7.0 (Nougat). The symptoms are below.
Two-symptom issue:
1) The 'call end tone' (which sounds like a pingy "bloop") cannot be disabled. The toggle slider can be turned off at Dialer > Settings > Call Alerts > Call end tone, but the tone still fires after each call disconnect.
2) The 'call end tone' not only fires after every phone call disconnect. But strangely, it also fires after any notification sound from another app has fired. For example, when Tapatalk or Facebook fire off a new message alert notification sound, the call end tone fires immediately afterwards. I also notice that each time the call end tone fires, a slash mark momentarily appears through the speaker icon on the notification strip.
I've tried wiping the cache partition and, as mentioned, toggling off all call alert settings. But none of that has worked. And by the way, this is the installation of Nougat that was on my S7 edge when I received it back from Samsung's repair center a few weeks ago. I'm hoping to avoid doing a factory reset. It looks like that may be the next step, though. Any thoughts?
Okay, I was wrong. It's not the 'call end tone' that I'm hearing at all. Instead, it's the same sound that fires when you change from silent or vibrate mode to audible mode. That little "bloop" is what's firing after every notification sound. I've checked and it's the following file: /system/media/audio/ui/TW_Silent_mode_off.ogg ... I'm not rooted so I can't remove or rename it.
So that's why the 'call end tone' toggle slider under Call Alerts has no effect on the little "bloop" sound. I only thought it was the 'call end tone' because it always fires when a call disconnects. But it's apparently just doing the same thing it does when each notification sound fires. Whatever the root cause, upon each sound event it seems to send a signal to briefly mute the speaker (hence the slash mark across the speaker icon for a split-second) and then immediately un-mutes it again. But I have no clue why. I thought it might have something to do with SoundAssistant -which I installed several days ago- but uninstalling it makes no difference. So I'm stumped.
I'm open for any ideas. The 'bloop' after every notification sound and call disconnect is driving me nuts. I'll probably do a factory reset if no one can think of anything else.
I've identified the cause. It's an app that normalizes the ringtone level, called 'Disable Increasing Ring.' When I toggle off its normalization mode, the problem is gone. The reason I even installed the app is because of the forced ascending ring volume for incoming calls that's imposed by Android 7.0. In my view, there's simply no excuse for Google/Samsung not to provide users an option of whether or not they want ringtone streams to ascend from weak to a normal volume level. Forcing that sort of thing upon everyone seems ridiculous. And of course it caused this headache for me. But it's their system... so oh well.