This has been happening to both me and my brother's phones for a while. my phone has dcd3.20 and radio rom 3.42.50 My brother's phone is dcd 3.16 with one of the earlier gps enabled radios. we use whatever was the stock dialer for those kitchens. We are both on sprint. yes we should update to the newest rom/radio.
say I wanted to dial a contact named Miranda, so I push the green phone button, dial 6(m,n,o) ,4 (g, h, i) on the keypad and that narrows it down to 1 contact named miranda in this case, I push the green phone button and my phone will make a call. and then when the other party picks up I find out that I called the wrong number.
I swear this morning I even watched the status and it said, "dialing miranda" and showed her number, but when I connected I found out I had the wrong number and then looked at the call status and it displayed someone else's number (this time a number that is not in my contact list, does not contain the numbers 64, and probably not in my last 10 calls)
There have been other cases where dialing the first two or three letters of a contact's name narrows the contact list to a few contacts, then I might use the up or down on the nav button to select the right one and then push the green phone button to dial. And then my phone will call the wrong person, sometimes it calls someone that was not on the narrowed down contact list.
has anyone else had this problem?
This happens to my phone (DCD 3.20) and my bosses phone (DCD3.25) occasionally. I would say for me, it happens my 1 out of 50 times. It will be when I dial a number I have never dialed before--I will type in the complete number, hit send, and then the phone will dial something close to the number from my contacts.
I also have this problem as well with 3.2.6
I was trying to dial a pizza and it had the first 6 digits the same as a AC company I called the same day. I could not get it to dial the right number - even though like you say, it says it is. In the end had to use a friends phone. Only time it has happened to me though.
same
I often experience the same problem.
The way around it is to press the name of the person you want to dial before pressing the green dial button.
I.E. click on the name in the list- EVEN THOUGH it is already highlighted.
works for me.
Still a pain in the ass though.
I believe it has to do with the touch dial skin and smart dialing.
I have the same error on the stock sprint rom with the touch dialer skin installed.
I have also had this isue on multiple versions of DCD roms... not sure if the VZW rom had the issue was I was not on long enought to find out. I ended up calling my bosses cell one night at 1 am.... woops!
I have also had this problem as long as i can remember.
Here is an example to add to the list.
try to dial *72
you cannot simply just dial that.
It will dial the next closest number.
It will only work if I disable smartdial.
Go figure.
Same here. I will type the first two digits on someones name and number and it will only dial those digits even though I selected the name from the list before pushing call.
Clicking on the name just works some of the time. I thought I was going crazy...
So is this a random problem or can it be reproduced? Any of you cooked a DCD rom with the mogul dialer and noticed the same problem?
I hope we can figure out if this is a problem with the dialer or Smart dial itself?
I always get a 10 digit number dialed (from 2-3 digits pressed for smart dialer) , whether or not it is the number I want dialed is another issue.
don't know if there is a way to reproduce it, since it happens only occasionally.
this has been happeneing to all my 6900 users and its driving them/me nuts.
anyone know why its doing this or what a solution mght be?
Dito...
I had the same problem yesterday when trying to get to the EPST screen. The first time I dialed ##778# and realized that I didn't need the ending #. When I put in JUST ##778, it would still try to dial the one I already dialed. I had to delete it from my recent list to get into the menu.
Jon
kept happening over and over the other day again when trying to call miranda from my phone by using the smart dial keypad 6-4. noticed it is dialing 612-599-xxxx instead of her contact number. 612-599-xxxx is the first number that pops up when i just push 6, pushing 4 narrows it down to miranda in my contacts but the phone still dials the first choice for only pushing 6.
so it seems like the smart dialer display is a step ahead of the dialer?
Related
Hi,
Anybody knows if there is software to AUTO REDIAL a number found busy, like most cell phones do?
(Or maybe there is some settings that I am overseeing?)
Thnx
just press the green button twice, that dials the last dialed number again, as i keep doing it by mistake
Carnivor said:
just press the green button twice, that dials the last dialed number again, as i keep doing it by mistake
Click to expand...
Click to collapse
Thnx for the reply, but I meant AUTO redial. Like it is on any other cell phone (you don’t need to intervene since it will redial on its own till the number becomes available again)
:wink:
...
http://www.pocketmax.net/redial.html
when a call comes in, i either push answer on the screen or hit the green button. however, it takes a few seconds before the my phone actually picks up the call. has anyone else run into this problem?
i just tried calling myself and the phone just keeps ringing the extra ~3 seconds before the phone picks up.
Here's an article on how to fix that, but it involves a registry editor and adjusting a setting
http://www.wmexperts.com/wm-cdma-phones-have-delay-when-answering-call-data-connection-read
I actually have this problem but the registry fix isn't what's wrong ...is there any other ideas?
i'm pretty sure it has to do with WM - I have a coworker with the Mogul and he says he has the same delay that i have both with answering calls and hanging up calls.
mjchoi824 said:
when a call comes in, i either push answer on the screen or hit the green button. however, it takes a few seconds before the my phone actually picks up the call. has anyone else run into this problem?
i just tried calling myself and the phone just keeps ringing the extra ~3 seconds before the phone picks up.
Click to expand...
Click to collapse
Try this one
It is not a fix per say for what you wnat but it will make your phone ring soner.
Get into your msl settings by pressing ##778# on stock rom (you will need your unlock code) and then click on edit, then click your left soft key (should be view info) then go to modem settings and change the slot cycle index to 1. What this will do is make your cell phone check the tower for incomming calls every 1-2 seconds instead of every 5-7 seconds.
thermus said:
Try this one
It is not a fix per say for what you wnat but it will make your phone ring soner.
Get into your msl settings by pressing ##778# on stock rom (you will need your unlock code) and then click on edit, then click your left soft key (should be view info) then go to modem settings and change the slot cycle index to 1. What this will do is make your cell phone check the tower for incomming calls every 1-2 seconds instead of every 5-7 seconds.
Click to expand...
Click to collapse
I agree that this works. It helped my pickups be a little quicker and more consistent. If you don't know your unlock code, google for an app called "getspc"
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
pissinguoff247 said:
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
Click to expand...
Click to collapse
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Bigger problem
fookxixi said:
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Click to expand...
Click to collapse
I never had the phone to my face when I did my test calls - this was always phone in my hand and calling from my office phone.
I think I just came across a bigger problem - the dialpad doesn't work on incoming calls. I just called my phone from my office on the regular (not G-voice) number and pushed a bunch of buttons, and couldn't hear the tones.
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
bojackson63044 said:
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
Click to expand...
Click to collapse
Is this actually a bug? I posted another thread here and am trying to have people verify whether or not this is a real issue - if it's not a bug then I definitely need to replace the phone, 'cuz it's been factory reset as of last night.
my dial pad is missing when calling someone. screen flashes and the call screen is lost. but the call is normal.
a few times phone opened automaticly coming call. I checked all call settings, there is no anormal setting, please help.
I tried all versions rom. 2.1, 2.2, omg, chayogen etc. now I'm using 2.1 update, kernel leshak 2.6.29, lk2.08.1 samdroid
I have the same problem!
I have the same problem. It started about 3 days ago for no reason. When you press the call button after entering a number, the screen goes black and all the three buttons at base (back, windows and search) are not responsive. There is nothing you can do...you can't hangup or enter numbers until the other party hangs up, unless you reboot. (You can still talk and make the call as normal).
I tried rebooting, took battery out and also did a factory reset but nothing has resolved the problem.
However, I did find a workaround: flip phone over so it goes into speaker mode and then the dialpad becomes visible and you can end the call or use number pad, but you have to keep phone flipped over all the while. Another workaround is to use a Bluetooth headset when making or answering calls. Then the dialpad is always visible as normal.
If anyone knows what to do please respond!
there is no hope (from xda)
I decided to go service...(its doesnt matter I tried al versions rom, I hate this phone, enough, I tired to reload rom vs.)
This is something I hadn't encountered before--I find that none of my dialers (the marshmallow stock dialer or my usual app DW Contacts) sends a DTMF tone when I am in a call. Example: "press 1 to talk to Jack". I can press 1 but nothing happens on the other end, doesn't matter who I am calling.
Second problem: when I'm in a call, I don't see any options for hanging up. Maybe this is some strange marshmallow "optimization"? I've looked in the settings for stock dialer and DW Contacts but don't see anything to remove the option to hang up.
UPDATE: I flashed this same ROM but the 6.0 non-debloated version. The DTMF tones are now working properly and I'm getting DTMF tones (both on my end and registering when I call a number and press a key in response to the menu) and an option for hangup (a red "hang up" icon in the middle of the screen.) I don't know if this means the February update caused a problem, or possibly something was missing in the debloated version. It could certainly be that the SIM card which was previously in another phone wasn't working properly with this phone until I called AT&T and asked them to "register" my Pure on this SIM. if the latter, it took a while, since I was still having the problem an hour later when I downloaded and flashed the non-debloated version.
Anyway, that's how I solved this problem, if it's useful to anyone.
Thanks. Been having same issue!
kettir said:
This is something I hadn't encountered before--I find that none of my dialers (the marshmallow stock dialer or my usual app DW Contacts) sends a DTMF tone when I am in a call. Example: "press 1 to talk to Jack". I can press 1 but nothing happens on the other end, doesn't matter who I am calling.
Second problem: when I'm in a call, I don't see any options for hanging up. Maybe this is some strange marshmallow "optimization"? I've looked in the settings for stock dialer and DW Contacts but don't see anything to remove the option to hang up.
UPDATE: I flashed this same ROM but the 6.0 non-debloated version. The DTMF tones are now working properly and I'm getting DTMF tones (both on my end and registering when I call a number and press a key in response to the menu) and an option for hangup (a red "hang up" icon in the middle of the screen.) I don't know if this means the February update caused a problem, or possibly something was missing in the debloated version. It could certainly be that the SIM card which was previously in another phone wasn't working properly with this phone until I called AT&T and asked them to "register" my Pure on this SIM. if the latter, it took a while, since I was still having the problem an hour later when I downloaded and flashed the non-debloated version.
Anyway, that's how I solved this problem, if it's useful to anyone.
Click to expand...
Click to collapse
Thanks. I've been having the same issue on my new Moto X Pure (rooted on Sprint), and was starting to freak out today when I realized that my phone wasn't being recognized for menu options AND there was no way to hang up from a call.
Fingers crossed that this will work for me as well with the non-debloated version.