For some reason I can no longer answer an incoming call on my O2 Orbit (Artemis HTC3300)
The phone rings and pops up with call details. I hit green key or answer on screen and it just keeps ringing.
Has anyone else had this problem. The phone call is picked up by my service provider (O2) providing they leave a message. It is almost as if I have mistakenly set something to 'never answer'. The only thing I can think I changed was when I set to auto answer after 1 ring (when in the car) but I have reset this and unchecked it.
Help appreciated as it is useless as a phone now !
Thanks
Have you've tried to HARD-reset your phone, and tested it then?
Otherwise there might be an issue with your rom.
That's my 10 cents.
I have the same problem but not every time. 70% of the time a call comes in and I answer with either green hard button or screen button and the call just dies. I then end up with a missed call which I then have to return. My outgoing call usage has gone way up since I got this handset because I end up calling everyone back !
i have this same problem it will answer 70% of the time has anyone got any suggestions thanks
reflashing radio/updating radio may resolve this
mal_k100 said:
For some reason I can no longer answer an incoming call on my O2 Orbit (Artemis HTC3300)
The phone rings and pops up with call details. I hit green key or answer on screen and it just keeps ringing.
Has anyone else had this problem. The phone call is picked up by my service provider (O2) providing they leave a message. It is almost as if I have mistakenly set something to 'never answer'. The only thing I can think I changed was when I set to auto answer after 1 ring (when in the car) but I have reset this and unchecked it.
Help appreciated as it is useless as a phone now !
Thanks
Click to expand...
Click to collapse
The reason for this is when I am in the car and am using the bluetooth to answer the phone is in my case on my belt. When I get a call the screen comes on and even after the call is completed it stays on for 2 minutes. I then end up calling someone in the last called list if the screen bumps the case. I don't notice because my dumb car always wants to download the phonebook after every call and the stereo doesn't connect the outgoing call. Then someone tells me that they got 2 minutes of my music on their voicemail if they didn't answer. Ended up being very embarrassing when call went out and I made some comments that "someone" was not supposed to hear.
I looked with the advanced config tool but could not find anything.
Any ideas appreciated.
Tks
Perhaps stopping the screen from waking is too drastic. This means you effectively disable caller-id. I would suggest looking into installing a screenlock tool.
I am trying pocketshield for now. I was going to look at su2u but I was told that incoming calls still turned the screen on. Will see how this works for a few days.
Thanks
Well I tried pocketshield and it doesn't really do what I need. It still lets the damn phone call after I have hung up. It leaves the screen on and at the lasted called screen. bump the screen and it calls one of my last called list. Going to try Touchprolock now and see how that goes...
I have "locked" (AT&T stock ROM - using long press end key to lock) my device and then hit the power button momentarily.
This turns off the screen. When an incoming call hits, screens lights up. After call is terminated, screen turns off.
It has happened about 3 times so far that my phone has made a series of loud beeping noises that lasts about 10 seconds with no discernible cause. Changing the volume does not stop it until I put it all the way down into vibrate mode. It almost sounds like it could be ringing but it isn't the ringtone I have set. When it happens, I check my notifications and running apps to no avail. Has anyone else experienced this? This is my first Android phone so it is possible I am doing something wrong. Any ideas?
optimiss said:
It has happened about 3 times so far that my phone has made a series of loud beeping noises that lasts about 10 seconds with no discernible cause. Changing the volume does not stop it until I put it all the way down into vibrate mode. It almost sounds like it could be ringing but it isn't the ringtone I have set. When it happens, I check my notifications and running apps to no avail. Has anyone else experienced this? This is my first Android phone so it is possible I am doing something wrong. Any ideas?
Click to expand...
Click to collapse
Same thing here. The beeping starting happening sometimes when I rebooted but now it's been doing it pretty much every time I get a text message and it also randomly replaces my default ringtone when calls come in. It's a loud beeping down that lasts about two seconds and repeats over and over. Sometimes it stops itself after a few cycles but sometimes it will not stop until I acknowledge the notification (opening up the text or answering a cal). It's very annoying. Might have to try a hard reset soon.
Mainframe52 said:
Same thing here. The beeping starting happening sometimes when I rebooted but now it's been doing it pretty much every time I get a text message and it also randomly replaces my default ringtone when calls come in. It's a loud beeping down that lasts about two seconds and repeats over and over. Sometimes it stops itself after a few cycles but sometimes it will not stop until I acknowledge the notification (opening up the text or answering a cal). It's very annoying. Might have to try a hard reset soon.
Click to expand...
Click to collapse
Yeah, for some reason it seems the text notification ringtone will change back to that god-awful sound for no reason. Very annoying.
Do you have yurt phone setup to remind you of missed calls and text?
Sent from my Emotionless Beast of an Epic using the XDA App
Mainframe52 said:
Same thing here. The beeping starting happening sometimes when I rebooted but now it's been doing it pretty much every time I get a text message and it also randomly replaces my default ringtone when calls come in. It's a loud beeping down that lasts about two seconds and repeats over and over. Sometimes it stops itself after a few cycles but sometimes it will not stop until I acknowledge the notification (opening up the text or answering a cal). It's very annoying. Might have to try a hard reset soon.
Click to expand...
Click to collapse
This happens when you've rebooted and gotten a message. Your SD card, containing your ringtone, hasn't mounted yet. The media scanner is running. Following this operation, the ringtone will work once more.
From some few days, strange beeping sound comes sometimes through my phone .When I check my phone there is no notification,& the sounds last for10-12 seconds, please help me if someone knows the reason.My phone is redmi Note 4g
It seems that sometimes my calls get muted when my phone leaves the on-going call screen and switches to a something else/a different app.
Hopefully that makes sense, but I'm not even sure how/when it happens so it's difficult to describe. But basically, randomly, when I'm on a call the other person won't be able hear me. Every time this happens when I look at the screen I'm no longer in the phone app/on-going call screen. Once I swiped down on the notification menu and re-enter the ongoing call they can hear me again.
I've tried to duplicate the behavior by switching apps but can't seem to do so...Has anyone else experienced this? I'm wondering if it has something do with the the automatic do-not-disturb that enables during calls...?
Thanks
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
I dont have this problem.
pogano_celjade said:
When somebody calling me and I pick up, I can make conversation but phone is stuck on ringing mode, and after few moments hang up phone call, and I have missed call...
Somebody else have this problem? How can I fix this?
Click to expand...
Click to collapse
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
lbsilva said:
That's weird, I did never face this issue but my A2L is relatively new (1 week only).
I'll try to phone to my own A2L using different devices to see if I face this issue.
Click to expand...
Click to collapse
Yes, it is very weird and annoying. Not happens every time, but sometimes... ?
This happened to me yesterday for the first time, but I thought that was a problem of the person that was calling me.
It was a number I didn't have in my contacts, and after the bug I immediately called back that number, but it was not available.
I thought the person that was calling me had a very low battery charge and while calling me his phone turned off, causing the bug (because immediately after the bug it was unavailable).
To this date I still did not have this problem.
Me too, i cant answer and reject calls when i upgrade to android pie
Solved: Screen not turning on with incoming calls
Step 1: Go to Dialer or Phone app settings. To do so, you can either go to main settings, then open ‘Apps’, and then scroll down to Dialer or Phone App.
You can also access App Info page by long pressing the app icon, and then tapping the App info option or the small ‘i’ icon in the corner.
Step 2: Now select “App notifications” option and turn it "on"
Step 3: Now if App notifications are turned off, your display won’t wake up when someone calls you. Also if only the “Incoming calls” permission is off, your screen will not light up with incoming calls. Make sure required permissions are turned on and your issue will be fixed.
Xiaomi Mi 2 Lite. I cannot get incoming calls to show on my screen, so I can't answer. Tried switching notifications off and on again, tried forcing stop. Two days ago I did a factory reset and was OK for 2 days. I think this is since latest Android update about a 10 days ago.
Call answer bug
I have similar issue on Mi A1, been going for a while. Sometimes, call comes in, the answer key cannot pick and cannot reject the call. This happened after a certain update I just dont know which. I have noticed that this mostly happens at some particular GSM antennas, sometimes, just by moving away from that antenna (that's when in a car) solves the problem. But as long as I remained in that location at that time, i cannot pick or reject calls, I also can't make calls, I get the promt, network problem, even though the service bars r showing. And in some cases the people calling will tell me, that calls to me are not going through.
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
PeterSharpe said:
This is driving me nuts. When I get a phone call I get a bar at the top of the screen with two buttone, one saying Decline and the other sayng Answer. I can tap on it like a demented woodpecker, but nothing happens. If Itry to swipe it, the two buttons just disappear into a void and the phone keeps ringing with no way to answer. Very, very occasionally I get the normal notification that I can swipe to answer, but I have to phone nearly everybody back.
Click to expand...
Click to collapse
Clear data and cache of the "phone" App and if necessary reinstall the application