Phone fails to dial out the first try most of the time. - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Recently upgraded to the offical ATT JB rooted ROM. Since doing this I've noticed that MOST of the time when I try to place a call, it fails the first time.
I select my number or put in my number and hit send, after 2 to 5 seconds I hear a beep and it says call ended. I hit send again, it goes threw.
I just got my S3 a couple weeks ago but I do NOT remember it doing this on ICS.
Thoughts? This is really annoying.

I was having the same issue before I went back to ics. It would beep once then go to the lock screen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

asjdwf said:
I was having the same issue before I went back to ics. It would beep once then go to the lock screen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ah yes correct. I forgot to mention it would go to the lock screen most of the time, unless I managed to hit the send button again before it makes it to the lock screen.
Yes it would beep then drop out to the lock screen. VERY annoying.

Related

Vibrate when call connects

Is there a way to get the phone to vibrate when dialed number connects.
Right now it plays a tune, so it knows its connected, however can that be tied to vibrate as well?
My old phone did this, and its great to not have to hold the phone to your ear if the connection takes a long time to get through.
if you flash the cm7 Rom it has that option. i dont think any of the others do though.
I use Go Contacts, which comes with Go Dialer , and it has that option ...
Stock dialer does this, settings, call, call alert, answer vibration
Sent from my SGH-T989 using xda premium
i have that feature on miui
TLJester said:
Is there a way to get the phone to vibrate when dialed number connects.
Right now it plays a tune, so it knows its connected, however can that be tied to vibrate as well?
My old phone did this, and its great to not have to hold the phone to your ear if the connection takes a long time to get through.
Click to expand...
Click to collapse
If you have root then search "vibralert" in the market.
Top app with lots of options.
Sent from my GT-I9100 using Tapatalk
avarize said:
Stock dialer does this, settings, call, call alert, answer vibration
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
hehe, yeah I forgot you could do this on stock ... Great reminder ....
avarize said:
Stock dialer does this, settings, call, call alert, answer vibration
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
THANKS !!!

End Call Delay

When a call is ended, it takes a few seconds before it automatically closes and takes you back to home screen. My friend's T-Mobile Galaxy S III is much faster.
Setting to change this?
It would be nice to get rid of this, or if the back button made it happen instantly. I make many calls a day, 30-200 depends on business.
Sent from my SPH-L710 using xda app-developers app
That's weird he probably has different apps running that are not slowing down his phone. You might have something running to slow it down
Sent from my Galaxy Nexus using xda app-developers app
I got same problem, it takes awhile to go to home screen since day one, so nothing to do with other apps running, plus we have powerful phone, write?
Sent from my SPH-L710 using xda app-developers app
I usually press home after the call and it goes rather quick. Maybe I'm just not expecting it to be so quick, though.
Overstew said:
I usually press home after the call and it goes rather quick. Maybe I'm just not expecting it to be so quick, though.
Click to expand...
Click to collapse
I think the delayed screen is to give you access to reply with text or call back. Hitting the home button takes you home quicker than hitting back
Sent from my Jelly Bombed SGS3
I also noticed a delay in audio resume. long enough that I goto reach for the phone and then poof it starts playing again.
this is where I am listening to a podcast it rings so pauses the audio and I take the call when I am done it "resumes" the audio. on the S2 this delay was VERY short on the S3 this resume delay is really really long.
I call so many people during the day no delay and instantly back to dialer would be nice.
Sent from my SPH-L710 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Omega rom v33.3 has this fixed by a mod, but i cant seem to find the mod alone to flash it on my rom...
are there any standalone mod to flash? Or anyone know method to change this?

Any way to fix home button wake up bug?

Dont know what else to call it really but I know this is happening with all of our devices.. which is when the screen times out and u press home to wake it up it takes u back to default homescreen. The sgs3 doesnt react that way and ive had to get used to hitting the power button instead. Any ideas? This would be amazing and greatfully appreciated.
Sent from my SGH-T889 using xda app-developers app
I can't replicate this issue. I let my screen timeout and pressed the home button and it simply turned the screen back on to where I left it.
Sent from my SGH-T889 using xda premium
I've had it happen. You press he home button immediately after the screen goes black, and it wakes the screen up, but also takes out of what ever you are in and takes you to the home page. I've retrained myself not to go for the home button, but the power button.
stevessvt said:
I've had it happen. You press he home button immediately after the screen goes black, and it wakes the screen up, but also takes out of what ever you are in and takes you to the home page. I've retrained myself not to go for the home button, but the power button.
Click to expand...
Click to collapse
I've seen this behavior too. It's quite annoying.
Sent from my SGH-T889 using Tapatalk 2
j_shelton1988 said:
I can't replicate this issue. I let my screen timeout and pressed the home button and it simply turned the screen back on to where I left it.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
What firmware are you on.. no matter what rom im on if the screen times out it takes me back out of wher is was.
Sent from my SGH-T889 using xda app-developers app
pezlomd said:
What firmware are you on.. no matter what rom im on if the screen times out it takes me back out of wher is was.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Stock rooted. I tried it multiple times and the same thing happens, screen times out, I instantly press the home button and it turns the screen back on but keeps me on the web page, app, etc that I'm using.
Sent from my SGH-T889 using xda premium
No matter what I do wipes roms etc I have this problem..wtf
Sent from my SGH-T889 using xda app-developers app
This is really an issue, "immediately" hitting the home button when it goes to sleep? Why not just avoid letting it go to sleep or hit the power button? This seems like a non issue to me and I've never had it happen.
but my post does not help the OP so good luck with that, sorry for the editorial.
The point is my sgs2 gti9100, and sgs3 tmobile which both had physical buttons didnt react this way.. I find it to be strange.
Sent from my SGH-T889 using xda app-developers app
pezlomd said:
The point is my sgs2 gti9100, and sgs3 tmobile which both had physical buttons didnt react this way.. I find it to be strange.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Are you using stock LEAK ?
I think this is a Jellybean 4.1 issue. My Note 2 has the same problem, but my wife's Galaxy S3 didn't when she was on ICS. Last week the phone updated to JB and now the problem exists.
This is definitely related to Jelly bean but I'm not sure if it is strictly a Touchwiz Jelly bean issue. It happens when I removed S Voice from the home button double press. It happens on the S3 and when my Note II comes in I bet it will happen on there too.
There are a lot of people that noticed it and I even saw someone open an issue with Google, although I'm not sure it is entirely a Google issue.
http://code.google.com/p/android/issues/detail?id=39326
The last line is the issue maybe.
"I want the single tap to be more snappy - for that I must disable s voice, but when I do it this bug raises its head. "
Do you guys have s voice disabled on the home button to save that lag time?
I disabled the s voice on the home button but still have the lag.
Sent from my SGH-T889 using xda app-developers app

Screen Goes Dark During Call

Has anyone ran into issue where you make a call screen goes dark like it's supposed to however if you want to end call screen won't come back on until call ends on the other side. So if person doesn't answer I have to wait till voice mail picks up and hangs up on me after it times out.
Sent from my SPH-L900 using xda app-developers app
dmehcg said:
Has anyone ran into issue where you make a call screen goes dark like it's supposed to however if you want to end call screen won't come back on until call ends on the other side. So if person doesn't answer I have to wait till voice mail picks up and hangs up on me after it times out.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Tried the power or the home button ?
Is your fone rooted ?
HyperDroidJBXv1.4 powered GT-n7100 nitro injected by RedPill ref.0.11 and pimped by Afroguide
It generally happens when I put it on my ear. Otherwise it is always on.
Sent From Samsung's Galaxy Note II Using Internet
Phone isn't rooted. I have tried to hit all the buttons including power to turn it back on after it dims out and still nothing. I'm thinking of doing business factory reset but I rather avoid it if I could.
Sent from my SPH-L900 using xda app-developers app
Maybe that's the end solution
Sent From Samsung's Galaxy Note II Using Internet
That's what I figure, thanks for feedback
Sent from my SPH-L900 using xda app-developers app
It happens when you place your finger or any part of the body near the sensor.
Sent from my GT-P7500 using xda premium
Got a screen protect covering the proximity sensor? Yours might be too sensitive. I had the same problem with my n4. Solution was no protector or wait till dearth or whatever brand you use to not cover the sensor. That was the first and only phone I ever had that issue though.
Sent from my GT-N7100
Did reset still same issue. I'll try without case, however I have had no issues with case till now.
Sent from my SPH-L900 using xda app-developers app
Also heard of this bug in a German Android forum: there have been some users reporting the same problem without screen protector or case. Still don't know why this happened but You're not the only one with this bug
Handschriftlich von meinem Note 2 gesendet
I too face this problm when on 4.1.1, temporary solution was using power button..
After update 4.1.2, problem gone!!
Sent from my GT-N7100 using xda app-developers app
I have this problem on my rooted 4.1.2 without any kind of cover.
Sent from my GT-N7105 using Tapatalk 2
You can always go into the accessibility settings and set the phone to end a call when you hit the power button
Sent from my GT-N7100 using xda premium
D3_ said:
You can always go into the accessibility settings and set the phone to end a call when you hit the power button
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yesterday I wanted to read a numberplate from a picture to the person I was talking to. Had to text it to him later because the screen wouldn't turn on.
Sent from my GT-N7105 using Tapatalk 2
It's really frustrating! Makes me not want to make any fone calls
Sent from my SPH-L900 using xda app-developers app
Enter *#0*# in the keypad to open the "test menu".
Press the Sensor tile and test your proximity sensor's function bij moving a finger over it.
If it does not change value from 0 to 1 and make the screen go green, your proximity sensor is likely to be broken.
Replacing the front camera (which houses the proximity senor) will then fix your problem.
dmehcg said:
Has anyone ran into issue where you make a call screen goes dark like it's supposed to however if you want to end call screen won't come back on until call ends on the other side. So if person doesn't answer I have to wait till voice mail picks up and hangs up on me after it times out.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
press the home button or power button
I went into store today to speak to a tech that used to work with when I was a sales rep @ sprint. He told he has seen issue a couple of times. He says when that happens its a sensor issue. More common with fones that where 1st shipped out. He could of replaced it if I wanted but he wanted to avoid giving me a refurb. He did a couple of tests and it's been working since. He suggested if it happens again to bring it back again.
Sent from my SPH-L900 using xda app-developers app
ronin1973 said:
Enter *#0*# in the keypad to open the "test menu".
Press the Sensor tile and test your proximity sensor's function bij moving a finger over it.
If it does not change value from 0 to 1 and make the screen go green, your proximity sensor is likely to be broken.
Replacing the front camera (which houses the proximity senor) will then fix your problem.
Click to expand...
Click to collapse
Works after a reboot. Seems to be the solution to every problem with that sensor.
Sent from my GT-N7105 using Tapatalk 2
I admit this is sometimes frustrating for me too. I'm curious as to a quick fix.

[Q] Droid Incredible 2 Lock Button Won't work

I have a droid incredible 2 with android version 2.3.5, and miui version 112300. I have had a few problems with it. First of all, it won't let me pick up when people call me. I can call people, just not pick up. And then out of no where my lock button stopped working. I have to plug it in to unlock it and basically have to keep it on all day. I've done a reset and it didn't do anything. What should I do? Please help!
Maybe your lock button is faulty?
I think you can add an option for your volume buttons to wake up the phone.
Sent from my SCH-I535 using xda app-developers app
If I remember correctly miui 12.9 was the last usable build. Not saying that's what's wrong- just food for thought. 12.30 had issues
Sent from my Galaxy Nexus using xda app-developers app
Paxton16 said:
I have a droid incredible 2 with android version 2.3.5, and miui version 112300. I have had a few problems with it. First of all, it won't let me pick up when people call me. I can call people, just not pick up. And then out of no where my lock button stopped working. I have to plug it in to unlock it and basically have to keep it on all day. I've done a reset and it didn't do anything. What should I do? Please help!
Click to expand...
Click to collapse
maybe do a full wipe and reinstall will work
I have heard of those buttons going bad.
Use the volume rocker wake option. If you need to use the power button try taking the back off, then use it.
Sent from my Incredible 2 using xda app-developers app
Paxton16 said:
I have a droid incredible 2 with android version 2.3.5, and miui version 112300. I have had a few problems with it. First of all, it won't let me pick up when people call me. I can call people, just not pick up. And then out of no where my lock button stopped working. I have to plug it in to unlock it and basically have to keep it on all day. I've done a reset and it didn't do anything. What should I do? Please help!
Click to expand...
Click to collapse
As stated above, use 12.29
Sent from my R800x using xda app-developers app

Categories

Resources