Whenever I receive a call when I'm already on a call, I never hear a beep or anything to indicate that a call is coming in. When I hang up, I see that I have a missed call. Once when I was looking at the screen, it showed an incoming call (call waiting), but no "beep" or anything...
Any ideas?
Did you ever fix this?
I'm having the same issue. Just wanted to know if you fixed it?
.
Never got it fixed...
same issue
Upgrading cyanogen constantly and finally downgraded for cyanogen3.4 to 3.3.8, cuz my phone was shutting itself off every 6 or so hours.. Now, it is running AMAZING... Just no BEEP for call waiting.. It isn't that big of an issue, but still would like it to work..
I think it is something that needs to be PUSHED into the phone and reseting the phone and taking battery out will not do it..
PLEASE HELP !!
Hate to dreg up a post from two months ago, but I'm having the same issue on my G1. I'm running soullife's Rogers 2.9.2, but have experienced this on other ROMs as well. Wiped, flashed, wiped again... nothing.
I've been scouring the forums to no avail. It's been reported a few times but I can't find a resolution.
Could it be something to do with stripped ringtones or notifications? I'll fiddle with them and see what I can find...
Any tips would be appreciated!
Ryan
Related
I have searched around and found no fix for my problem so far. Hopefully someone can help me out. I bought my Diamond used a few weeks ago and it came installed with a newer version of a Dutty ROM on it (not sure the exact version but I can retrieve it if needed) and it has seemingly worked fine. But the last couple days I have noticed that when anyone calls my phone, i touch the answer button and the phone acts like i pushed the deny/busy button and just sends my call to voicemail. No matter what I do every call now goes to voicemail. I havent tried actually pressing the busy button in stead while a call is coming, but I may try that to see if its switched or something. I tried a soft reset and didnt help... any suggestions for this strange problem????
My tilt will not dial out and seems to be missing incoming calls. When I try to call out it goes to the "Dialing..." screen as though its working, then just stops and makes a faint "dingdingding" noise from the speaker. After a rom flash the phone works fine for about an hour then goes back to the failed call symptoms again.
I have tried several roms and many radios/spl versions. I am on my last leg before re-locking and taking it to the store. Its past warranty and I wont be able to get an exchange. I have been surfing XDA periodicaly for 3 days looking for a solution.
If anyone is familiar with this problem, give me some advice or point me to the thread I can't find.
Thanks guys.
What is up with my phone? Everytime I try to make a call...after dialing, it never rings the other end, all I hear is an echo like Im on the phone with myself, then it disconnects shortly after. Wtf? I odined back to stock and everything, cant figure this out. I can receive calls just fine, its just dialing out I cant do and this just started a couple days ago, I figured it was nothing, maybe I was trying to call someone while they were trying to call me, but now I realize I cant call anybody! Help??
Nevermind. Problem solved. Oh thank you guys for all the replies and help....what a wonderful, friendly community!....sigh.... Man ya'll sure put the "A" in the Q&A forums, Thanks again!
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840
So, this started Im not sure how long ago, but it was sometime after Nougat got pushed out to the Note 5. More than 2/3rds of the calls I get, when I answer the call I hear nothing (no static, no beeps, absolute silence) and the caller is sent to voicemail as if I had rejected the call, even though my phone displays the active-call screen as one would expect it to while in a call. When calls work as normal, they work 100% normally with no errors or weirdness. Anyone have any idea what is going on? Im not rooted and Ive had the phone since a week before launch (thank you early shipment pre-orders) without issue. I have not tried a factory reset and dont intend to unless it ends up being my last resort, but I have tried multiple reboots.
Thank you for any assistance or guidance you may be able to provide :/