Has anyone else had a problem with the Optimus G being more prone to accidental 911 calls so far? It's happened to me three times in the last week, more than my Galaxy S2 did in 2 years.
Obviously somehow the power button is activating the screen, and then pressure on the screen is activating the Emergency dial key. But why this phone and not the S2 or my Nexus One before? I've asked nottach if the emergency dial key can be changed from single button to something else in The Base ROM, but I suspect this is hardcoded.
I have never ass dialed anything in ever. With any phone.
I opened a text message by accident when the phone was in my pocket. Now I disable screen wake when receiving a text. The phone was in my front pocket. This is the first phone to do this. Probably because when I used iPhones I had to slide to open things and not just tap.
Sent from my LG-E970 using Tapatalk 2
I have never actually had a 911 call placed, but i have noticed that on a number of occasions the standard lock screen buttons disappear (the call, text, browser, camera ones at the bottom of the screen) and are replaced by the dial emergency button. I have yet to figure out what causes this to happen or found any way to force it to happen.
Fission_Chipz said:
I have never actually had a 911 call placed, but i have noticed that on a number of occasions the standard lock screen buttons disappear (the call, text, browser, camera ones at the bottom of the screen) and are replaced by the dial emergency button. I have yet to figure out what causes this to happen or found any way to force it to happen.
Click to expand...
Click to collapse
The only time i have ever seen emergency dial on any phone is from no service. Is it possible youre losing signal or your sim is not fully inserted?
Never happened to me.
Please ask all questions in Q&A. Thread moved there.
Isn't emergency dial the only other button available on the pattern lock screen when the screen wakes up?
I've used pattern lock for my lock screen since the Nexus One and never had a problem with accidental 911 calls before.
Sent from my LG-E970 using xda app-developers app
Related
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.
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Bmerz said:
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Click to expand...
Click to collapse
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
ingenious247 said:
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
Click to expand...
Click to collapse
Thank you, I will look into my settings and change it. But as for the other thing, one has to have their hand on/near the dialer in order to input more numbers. Perhaps I can angle the phone and my hand in a way that the sensor doesn't see my hand over the dial pad. (What a PITA! lol)
Nonetheless, thank you for chiming in!
When I get incoming calls I get 2 different screens at different times to answer. Sometimes it's the regular Android screen with the 2 bubbles you swipe to answer and others its square buttons you press to answer the calls. Why does this happen and how do I fix it?
Also I wanted to ask will I be able to update to kit Kat while using straight talk service?
0verwatered said:
When I get incoming calls I get 2 different screens at different times to answer. Sometimes it's the regular Android screen with the 2 bubbles you swipe to answer and others its square buttons you press to answer the calls. Why does this happen and how do I fix it?
Also I wanted to ask will I be able to update to kit Kat while using straight talk service?
Click to expand...
Click to collapse
I believe the bubble buttons appear when there's an incoming call and the phone is locked, while the square buttons when the phone is on the home screen. Not quite sure about straight talk though.
Updates are sent out by Google to the phone's manufacturer, in this case LG. Then they are sent up the ladder to your phone's branded service provider, again in this case AT&T. Lg will add their changes to the OS and so will AT&T when they get it. In the case of you having service with Straight Talk, it doesn't matter because ST still uses AT&T towers and service. So when AT&T pushes out the update for this phone, you will get it also because technically speaking, you are still on AT&T's network.
For the two different screens, Blitz is correct. There are two call screens. One when the phone is locked and one when its not (home screen). Hope that explains it for you.
Thanks to both of you for the help. I was curious about why it was different at different times. Love the phone bought it for $30 with a cracked digitizer and home button not working and fixed it for $30 and I think I like it better then the Samsung phone I just lost.
When ur screen is off and u receive an incoming call, u'll get bubble type option to answer or reject the call (swipe left or right). If your screen is active and there is an incoming call then u will get the option to simply press the green button to accept or red to reject..no swipe option if screen is active..
Sent from my LG-E980 using XDA Premium 4 mobile app
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
I have an issue with my new a52s: when it's in my pocket, often the screen turns on and starts digiting (I think in the emergency call window).
Of course I have enabled the accidental touch protection, but it doesn't work.
Is there a way to disable the emergency call button on the lock screen? Other ideas? :-/
Pegli010 said:
I have an issue with my new a52s: when it's in my pocket, often the screen turns on and starts digiting (I think in the emergency call window).
Of course I have enabled the accidental touch protection, but it doesn't work.
Is there a way to disable the emergency call button on the lock screen? Other ideas? :-/
Click to expand...
Click to collapse
Experiencing same issue
Pegli010 said:
I have an issue with my new a52s: when it's in my pocket, often the screen turns on and starts digiting (I think in the emergency call window).
Of course I have enabled the accidental touch protection, but it doesn't work.
Is there a way to disable the emergency call button on the lock screen? Other ideas? :-/
Click to expand...
Click to collapse
'We meet again'
I had the same issue. Never like that with a previous phone, it's really seems like a Samsung thing for me. I even accidentally actually called the emergency services from my pocket last week, first time ever that that happened :-(
I did seem to fix it for me though, by disabling double tap to wake (Settings|Advanced Settings|Gestures). In fact I cleared all the first four settings on that page.
So the way I have it configured now tapping or pressing the locked screen only let' me unlock with my fingerprint and nothing else, for all other use I have to press the powerbutton first.
Thanks Sanderbos
It's a shame to miss that feature, though... :-/