I have an annoying problem that previously only bother me a little bit but now becoming more serious as I have missed several important calls.
The phone would froze up at accepting or rejecting call screen on random calls at least once a day without particular reason. I can push the volume button to turn off the ring but cannot pick up the call through the touch screen.
Anyone having similar problem?
Sent from galaxy s. JG4 + oneclick lag fix version 2.3
Related
I've got a Universal with all the default ROMs and whatnot. I also use SPB PocketPlus and vBar.
Recently, since I got a bluetooth earpiece (Motorola HS820) - though not when the earpiece is turned on/connected - my phone has started rejecting calls when I try and answer.
I normally have my phone closed (screen not showing). Since some bug stopped me from being able to talk on it whilst it is closed, I have been opening it so the screen shows (and the keyboard doesn't) before I press answer. However, now this rejecting problem has arisen. I get a call, I open my phone so the screen shows and then press the answer button on the spine. This stops the ringing, but the incoming call popup stays as though I haven't answered, the person doesn't hear me and I don't hear them, then I get a missed call notification.
This does not happen 100% of the time. So far I have only noticed it when I've been receiving calls from my mother. However, she's pretty much the only person who rings me
Anyone got any ideas as to what is causing this/how I can fix it?
Update: I've done a hard reset and it seems the button still isn't answering the call. It isn't rejecting the call, it just isn't answering it.
This phone is proving to be more trouble than it's worth...
Hi
I've got a Htc Touch HD from orange and maybe twice a day when I try to answer a call (either by sliding or pressing the hard button) the phone will freeze. It will still vibrate and ring but I have to do a soft reset to get it out of that state.
Nothing responds on the phone at all.
Sometimes it also cuts the other person off and doesn't crash, (so it looks like the other person hung up just before you answered it when they didn't)
Verrrry irratating! Esp when someone rings from withheld number!
Any ideas?
BTW, Making calls is fine no crashes, and experienced no other crashes on any other part of the phone except for this.
try downloading the patches from the HTC webby
hey all,
a while ago, suddenly one day without notice, my phone started behaving funny when receiving an incoming phone call.
Often, the Phone App's GUI wouldn't appear in the foreground. the phone would ring and vibrate properly, i could silent the ring with the volume rocker, but i have no way to answer the call. i know when it is finished ringing when i can see the missed call notification in the notifications bar.
also, during the ringing, i can continue using the app that was already in the foreground, the home button is disabled, and the notifications shade is disabled (cannot be pulled down)
i have no idea what i did to cause this (maybe playing with Handy Call?) and no idea how to get out of this state.
the worst part is, it seems to be random, i have no idea why it happens sometimes and not others. it is super annoying. ive actually started assigning specific ringtones to important people so i know immediately who is calling.
any one encounter this? any ideas?
xt907 running stock Rom 183.46.10, rooted, unlocked
Thanks to a Turkey Day special, I got my new Samsung Galaxy S5 free and have been enjoying it immensely. However, about a week ago, I started to have a problem making/receiving calls. The volume on calls (speakerphone & earpiece) was so low it was almost inaudible. Lowering/raising volume and even adding extra volume feature on calls failed to make the call any louder. The only thing that works is rebooting the phone. I am running the latest NI2 update and want to know if anyone else has this problem. Is it a bad phone? Do I need to replace it?
Also, for some reason I can't send/receive text messages to one contact on my contact list, wondering if it's a problem on my end or his.
This has been happening a lot ever since I updated to 2.1.2 and I haven't seen anyone else mentioning it. When on a call my mic will apparently just drop out and the other person can't hear me. The call is still connected but one of us has to hang up and call back. Happened twice today in quick succession. Sometimes when it happens I will look at the screen and it is as if I hit the conference call button and put the person on hold, even though I can still hear them. I thought maybe the screen wasn't turning off and my face was hitting buttons, but I determined this is not the case. The screen is off during the call and deliberate touches on the screen do nothing. Any ideas? I love the update and the OS overall, but this issue is a dealbreaker for me.
Zythos said:
This has been happening a lot ever since I updated to 2.1.2 and I haven't seen anyone else mentioning it. When on a call my mic will apparently just drop out and the other person can't hear me. The call is still connected but one of us has to hang up and call back. Happened twice today in quick succession. Sometimes when it happens I will look at the screen and it is as if I hit the conference call button and put the person on hold, even though I can still hear them. I thought maybe the screen wasn't turning off and my face was hitting buttons, but I determined this is not the case. The screen is off during the call and deliberate touches on the screen do nothing. Any ideas? I love the update and the OS overall, but this issue is a dealbreaker for me.
Click to expand...
Click to collapse
Following up...this problem is very real, very annoying, and happens every time I'm on a call longer than about 5 minutes. All the sudden the other person can't hear me and I look at my screen and it's as if the conference call button was pressed OR the screen is locked. Either way, my mic is muted. VERY annoying. Happens multiple times per call, every time. This is clearly a software bug and I find it highly unlikely that no one else is experiencing it. I even did a factory reset just as a test, and the problem persists. on 2.1.2