[Q] Keypad issues with conference calls or any calls - AT&T Samsung Galaxy S II SGH-I777

I can dial the number just fine but, when asked to put in the conference call password/id, or voicemail password, the keypad thinks i'm touching the numbers several times instead of just the one time... example 4197 equals 4447719777
any ideas?
cyanogenmod 7.2 on att samsung galaxy sII

Sort of found out what is going on. Whenever i have in my headphones with microphone and try to punch in the numbers, it doesn't work. Even if the phone is on speaker, no work.
BUT, if i have it as a regular phone and type in the code for my voicemail, code for the conference call, it works.
So, the use of mic/headphones, or speaker phone, no punching in codes. Weird.

sparkymoffett said:
I can dial the number just fine but, when asked to put in the conference call password/id, or voicemail password, the keypad thinks i'm touching the numbers several times instead of just the one time... example 4197 equals 4447719777
any ideas?
cyanogenmod 7.2 on att samsung galaxy sII
Click to expand...
Click to collapse
Yeah, I too have this issue... This happens with headphones on,.. Does not happen without headphones

Related

[Q] No incoming calls

I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Zjoske said:
I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Click to expand...
Click to collapse
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
Straight to voicemail. But I've figured it out after 3 days
There's an option to automatically block all incoming calls in the settings. Must have accidentally been activated when the phone was in my pocket.
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
In my case, the phone does not ring when I get a call at all. I have searched hi and low and I cant find a solution. I have rebooted, i have reflashed, I have changed my ringtone and nothing seems to work, please help!!
Hello my girlfriends SGS 2 has almost the same problem it cannot receive calls sometimes even though she can call everyone. The problem seems to fix by itself sometimes and it appears random.
I read that there was a problem with the samsung galaxy s when using 2G/EDGE connection with data activated and the problem was that the user could not receive calls randomly.
Can you confirm that you are using 2G/EDGE connection and Data activated? I am also trying to find the cause of this problem...
Hope my research helps good luck and waiting for your reply. (http://www.samsunggalaxysforum.com/...eive-incoming-calls-and-sms-while-using-edge/)
Later EDIT ---
She also has a vodafone provider but i have the same provider and never had this issue. Also no call filtering is done.
Make sure Call Forwarding is Disabled under Settings- Call- Call forwarding. And also try to delete the Voicemail number if you had set any.
Regards.
it's nothing Call Forwarding is Disabled related it is because of EDGE connection you can't have a sync or internet connection and while "dialing" data receive calls if you want to call anyone the network prioritizes and let's you dial whoever you want but it is not the same thing for incoming calls
^ Went over my head !
had the same problem in a bad 3g/data coverage area. solution was simply to turn data off and the calls started to come through.
turned data back on and now working ok.

[Q] keypad not working on calls: how to?

when making calls i need the keypad to enter numerical choices for voice prompts. however my keypad is not making that 'beep' sound that the prompt listens for. so the call does not progress.
what can i do to use the keypad for those calls that require numerical inputs for voice prompts?
rab1412000 said:
when making calls i need the keypad to enter numerical choices for voice prompts. however my keypad is not making that 'beep' sound that the prompt listens for. so the call does not progress.
what can i do to use the keypad for those calls that require numerical inputs for voice prompts?
Click to expand...
Click to collapse
you don't need any beep sounds in order to control numerical choices, just press the digits and it works.
tjtj4444 said:
you don't need any beep sounds in order to control numerical choices, just press the digits and it works.
Click to expand...
Click to collapse
i tried it on a different phone number and the keypad does work.
it was only on that phone number which probably relied on keypad sounds to activate the prompts.
the annoying thing is that was the phone number of my cell service provider which i had to reach!
rab1412000 said:
i tried it on a different phone number and the keypad does work.
it was only on that phone number which probably relied on keypad sounds to activate the prompts.
the annoying thing is that was the phone number of my cell service provider which i had to reach!
Click to expand...
Click to collapse
This doesn't make sense, something else is wrong. The digits you press during the call to a landline (without any beep in your end) causes the correct beep sound to be generated by the mobile network and sent to the other end of the call.
I just tested this myself by calling my home number to be sure I wasn't lying
I think you are searching for the wrong solution to your problem.
EDIT: here is the ETSI spec describing how it works if you like specifications
http://www.etsi.org/deliver/etsi_i_ets/300500_300599/300532/01_60/ets_300532e01p.pdf
there must be something wrong with my cellphone providers support prompts.
i tested with my bank and 2 other credit cards and the keypad does register input with them.
it is only with that one number that i am having issues on.

Bluetooth Voice Dialing Problems

I have been having trouble with my Note i717 voice dialing over Bluetooth. I pair it to my Pioneer DEH-P710BT care stereo, transfers phonebook and works when dialing with phone manually or by selecting name on deck.
My problem is with the voice dialing from the deck. I say the name but it keeps selecting a wrong name/number for each name I say. It will have the same wrong name for one name that I say, no matter how many times or clear I say it. It will give a different wrong name for another name that I say. I have tried saying last name before first name as well and it still doesn't select the right name. It feels like its just translating it wrong into text since it keeps selecting the same wrong name for each specific contact???
I had the same problem with my Nexus S. The exact same setup works fine with my Galaxy S2 i9100, HTC Nexus one and LG GW620. They all call the correct name.
-I have no lockscreen lock or password
-I have tried google voice search and Vlingo as default voice input
-Listen via Bluetooth is selected in Vlingo (tried without selected as well)
-Phone & Media profile are selected in the bluetooth settings for the deck
I am hoping there is a fix and its not some compatibility issue with certain samsung phones and my Pioneer deck. So far only 1/3 of my samsung phones work.
Anyone else have this problem? Ideas? thanks
How did you change between voice search and Vlingo as the default voice input? I have similar problems with voice dialing on a number of android phones and I'd like to try some other programs to see if it's a software fixable issue, but I can't get the phone do launch anything but Vlingo.
hausman said:
How did you change between voice search and Vlingo as the default voice input? I have similar problems with voice dialing on a number of android phones and I'd like to try some other programs to see if it's a software fixable issue, but I can't get the phone do launch anything but Vlingo.
Click to expand...
Click to collapse
Settings/Voice input and output/Voice input/Voice recognition
I have the Rogers Canadian SGH-I717R.
Changing that setting on the AT&T version does nothing, unfortunately....vlingo always picks it up. Oh well, was worth a shot since I've had better luck with cyberon voice commander.
Same issue here. At first I thought it was my car 2012 Hyundai Sonata. Deleted contact list out of the car a couple of times and tried pairing multiple times. The GNote pairs fine but gets the wrong name frequently.
Mine gets the wrong contact all of the time.
Doesn't anyone else have this problem?
Sure...had that since my first Android handset. So I started using Cyberon, which works better and has a confirmation mode (since I got tired of Android ringing up some bagel shop in Hoboken every time I tried to call my mom - I live in California BTW), but the Note doesn't offer the ability to have the bluetooth multi-function button start any app other than Vlingo, which doesn't meet my needs because it doesn't work through the phone lock screen when my phone is suspended.
If I'm going to have to pull the phone out of my pocket, unlock it, and then voice dial, what's the point.
WM6.5 had this functionality working beautifully in about 2007.
hausman said:
Sure...had that since my first Android handset. So I started using Cyberon, which works better and has a confirmation mode (since I got tired of Android ringing up some bagel shop in Hoboken every time I tried to call my mom - I live in California BTW), but the Note doesn't offer the ability to have the bluetooth multi-function button start any app other than Vlingo, which doesn't meet my needs because it doesn't work through the phone lock screen when my phone is suspended.
If I'm going to have to pull the phone out of my pocket, unlock it, and then voice dial, what's the point.
WM6.5 had this functionality working beautifully in about 2007.
Click to expand...
Click to collapse
Odd... are you saying you can't voice dial thru your car's BT without physically unlocking the phone?
I can voice dial just fine (locked & unlocked) on mine through the Ford Sync in my car.
Sent from my SAMSUNG-SGH-I717 using XDA App
Are you screen locked or password locked? I haven't tried it in my car yet (don't really need to as my car can read the phone book and I can dial by touch), but Vlingo will not respond to my bluetooth headset at all when the phone is PIN/password locked.

[Q] Issues With Note II on Straight Talk

Hello,
I have a Verizon Samsung Galaxy Note II running the stock verizon rom with a Straight Talk AT&T Sim card. When someone calls me the call log shows the number with a + in front of it, i.e. "+999-888-7777". If I select that number to call it back I get a voice prompt that says "Your call cannot be completed as dialed, please try again". I discovered that if I dial the number either without the + symbol (i.e. "999-888-7777") or if I dial the number with +1 (i.e. "+1-999-888-7777") then the call goes through fine.
Because of this issue I cannot use the call log on my phone to call numbers back and when my contacts call me the caller ID doesn't show the contact because I don't have the contact numbers stored with a + in front of them. Can this be fixed? I tried calling straight talk and was basically told they don't know what's going on and they can't do anything about it.

[Q] Forward all calls when out of range instead of unanswered

After a bunch of clicking and rebooting I got auto call forwarding working when Bluetooth disconnects, but it's not what I expected. It's only forwarding calls when unanswered.
I want to walk away from the phone and leave it behind and have calls forwarded immediately, all calls. I thought that was the point of this feature. I don't want them to have to ring for 20 seconds.
Is there some way to make this happen? I noticed it changes the network settings for unanswered, busy, and unreachable to forward, but all call forwarding is never enabled by auto forward.
Lucent said:
After a bunch of clicking and rebooting I got auto call forwarding working when Bluetooth disconnects, but it's not what I expected. It's only forwarding calls when unanswered.
I want to walk away from the phone and leave it behind and have calls forwarded immediately, all calls. I thought that was the point of this feature. I don't want them to have to ring for 20 seconds.
Is there some way to make this happen? I noticed it changes the network settings for unanswered, busy, and unreachable to forward, but all call forwarding is never enabled by auto forward.
Click to expand...
Click to collapse
Wild guess you have AT&T?
Uniquebarbee said:
Wild guess you have AT&T?
Click to expand...
Click to collapse
Nope, T-Mobile. Why? Are there ways around this on non-AT&T carriers?
Lucent said:
Nope, T-Mobile. Why? Are there ways around this on non-AT&T carriers?
Click to expand...
Click to collapse
You could try this
AT&T and T-Mobile both use the same method, which lets you change the number of rings right from your phone. To do it:
Dial *#61# from your phone. Tap Send.
You should see a new screen that displays a bunch of information about what's getting forwarded. You should see a line under "Voice Call Forwarding" that says "Forwards to +11234567890" (where 11234567890 is an eleven digit phone number, likely different from your phone number). Write down this number and tap Dismiss.
Now, dial **61*+11234567890*11*XX# and hit Send, where 11234567890 is the number that you found in step two and XX is the number of seconds you want to wait until voicemail picks up. You can set it in increments of 5, where 30 seconds is the maximum.
After you hang up that call, you can have someone call your phone and see if it worked. On some phones, you can dial *#61# again and see how long it's delaying your calls, but our test phone (the iPhone) did not show this information.
Alternatively, you should be able to call AT&T or T-Mobile customer service and have them change it from their end, if you're uncomfortable doing it yourself.
Another thing that may work for you is to get up a google voice number and just give people that number. Then you they call you, it will ring at both numbers and you wont have to use the call forwarding option.
If only I was not in an area were I cant port my current cell number over to google voice, i would have dont that years ago.
rfs830 said:
Another thing that may work for you is to get up a google voice number and just give people that number. Then you they call you, it will ring at both numbers and you wont have to use the call forwarding option.
If only I was not in an area were I cant port my current cell number over to google voice, i would have dont that years ago.
Click to expand...
Click to collapse
THIS is true I have google voice I haven't ported my number over but I get calls and text fine from both numbers
So while messing around with the settings for google voice and the gear s, I have found that if you activate google voicemail on your phone then the call forwarding option will not work when remotely connected to your gear. Calls forwarded TO the gear s work as they should. As soon as I deactivate google voicemail on my phone, and my phone & gear are connected remotely I have no issues with getting my calls from my main cell phone line forwarded to the gear. This is kind of a bummer cause I was hoping that i'd be able to use google voicemail and thier transcription service because tmo charges $3 per month for it. Womp comp. I rarely get voicemails so it's not the end of the world.
Lucent said:
I want to walk away from the phone and leave it behind and have calls forwarded immediately, all calls. I thought that was the point of this feature. I don't want them to have to ring for 20 seconds.
Is there some way to make this happen? I noticed it changes the network settings for unanswered, busy, and unreachable to forward, but all call forwarding is never enabled by auto forward.
Click to expand...
Click to collapse
I have a call forwarding widget on my Note 3 that I use all the time. It instantly forwards all calls to whatever number you wish. Works great as when I'm in my office at work, I have it forwarded to my land-line, same at home, etc. I do this now on my Gear S too as like you, I don't want to have people wait through long numbers of phones ringing before it reaches me.
pdqgp said:
I have a call forwarding widget on my Note 3 that I use all the time. It instantly forwards all calls to whatever number you wish. Works great as when I'm in my office at work, I have it forwarded to my land-line, same at home, etc. I do this now on my Gear S too as like you, I don't want to have people wait through long numbers of phones ringing before it reaches me.
Click to expand...
Click to collapse
which app/widget you speak of? i want to give it a try.
I just hate when people tell you something helpfull and dont provide a link to the help seriosly you come here tou tell about widget but didnt even mentioned wich widget you using to call forward .....dahhhh
idelgado782 said:
So while messing around with the settings for google voice and the gear s, I have found that if you activate google voicemail on your phone then the call forwarding option will not work when remotely connected to your gear. Calls forwarded TO the gear s work as they should. As soon as I deactivate google voicemail on my phone, and my phone & gear are connected remotely I have no issues with getting my calls from my main cell phone line forwarded to the gear. This is kind of a bummer cause I was hoping that i'd be able to use google voicemail and thier transcription service because tmo charges $3 per month for it. Womp comp. I rarely get voicemails so it's not the end of the world.
Click to expand...
Click to collapse
They both use the same conditional forward entry for your line. You can only have one. Not both. If you want to forward to Gear S, your own voice mail will never be reached. And vice versa.
billybkny said:
I just hate when people tell you something helpfull and dont provide a link to the help seriosly you come here tou tell about widget but didnt even mentioned wich widget you using to call forward .....dahhhh
Click to expand...
Click to collapse
I suppose, but honestly, it's not that hard to just get on the play store and look them up. They all function pretty much the same. The one I use is RedirectCall. All one word. Very simple and works great.
I couldn't get it to forward right away either. It's pretty simple to actually just forward the call to the Gear S manually. On T-Mobile devices dial **21*your ten digit number# then when you want to cancel it dial ##21# that's it works like a charm. I use tasker now to do it automatically and have had no hiccups. Although it would be nice if it just worked correctly through gear manager.

Categories

Resources