When I'm on a call and my phone is up to my ear it goes blank (which works fine), but when I remove the phone from my ear the screen comes back to the home page instead of going to the call. I have to pull the notifications tab down and choose the call to bring it back up.
I reboot my phone and everything works for a few phone calls and then it happens again.
Anybody else ran into this issue?
Jamolah said:
When I'm on a call and my phone is up to my ear it goes blank (which works fine), but when I remove the phone from my ear the screen comes back to the home page instead of going to the call. I have to pull the notifications tab down and choose the call to bring it back up.
I reboot my phone and everything works for a few phone calls and then it happens again.
Anybody else ran into this issue?
Click to expand...
Click to collapse
try repair it with SEUS.. install xRecovery, some new ROM and try again
Jamolah said:
When I'm on a call and my phone is up to my ear it goes blank (which works fine), but when I remove the phone from my ear the screen comes back to the home page instead of going to the call. I have to pull the notifications tab down and choose the call to bring it back up.
I reboot my phone and everything works for a few phone calls and then it happens again.
Anybody else ran into this issue?
Click to expand...
Click to collapse
Are you using any type of task killers?
Sent from my X10a using XDA App
Related
Not sure why this started happening, but whenever I call my voicemail the phone goes dark and I can't turn the screen back on. Neither pressing the power button or the home button does anything, but I can still hear the phone call. Any ideas?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Now the screen won't even turn back on after the phone call has ended
Do you use a screen protector? Check if the protector doesn't covers the sensor. It is possible that the sensor doesn't react well when it's covered (I had a similar problem with the Dell Streak).
Also try to make a call with a wired headset or if you make a call and you can't turn on the screen plug the headset in.
Terryjgj said:
Now the screen won't even turn back on after the phone call has ended
Click to expand...
Click to collapse
Might be a little bit late, but maybe for others
worked pretty well on my Samsung S4.
download the app "proximity fix" from the playstore and run it.
Job done.
Hope that helps you or anyone who stumbles upon this!
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
sammy.sung.me.a.song said:
The least invasive solution will be to clear the cache for the all the apps affected and reboot.
Or just wipe cache from recovery and see where it goes.
Click to expand...
Click to collapse
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Flash cm10 or Sammy jb
Sent from my GT-I9300 using xda app-developers app
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
5aq1b said:
thanks i'll give that a bash.
Was also considering just flashing CM10 jelly bean?
Click to expand...
Click to collapse
How is that very different from a restore?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
Unfortunatlly mate, i think ur having problem with this stock rom did you try to factory reset your device to eliminate those bugs. or flash another Rom because this is definitly a Rom problem.
sammy.sung.me.a.song said:
How is that very different from a restore?
Click to expand...
Click to collapse
it's not lol but at least this way i'll gain as well by upgrading to jelly bean - 2 birds with 1 stone etc etc
kachrukamble said:
Reduce animation scale to 0.5
go to setting>developer option>animation scales
You can also set no animation so that phone will response in less time
Click to expand...
Click to collapse
i'll try this as well mate - thanks!
Same issues that I'm facing
I'm also facing the same issue.... Long black screen pause when exiting or moving from one app to other. Very very frustrating ....
Tried all the trick in world including those that mentioned below.... Will be returning the device and going for a iPhone 5 !
Same exact issue, any results?
5aq1b said:
Tried searching around for this but hopefully someone can help.
I've got an S3 running stock 4.0.4 firmware. I'm having 2 very frustrating issues with this phone:
1) At first I thought this was a Swiftkey issue but happens with stock keyboard. when i go into the messaging app occasionally, when pressing keys on the keyboard - nothing appears. I have to quit messaging app and go back in.
2) another very annoying issue is when in the phone book and pressing the green phone button to dial someone, sometimes it will take 10 seconds for the phone to make a call. If i happen to press it more than once during that 10 seconds, it will make the call, and say for example the other person has picked it up, the dialler will then place another call - to the same person! The other person tends to say - "why are you putting me on hold and calling me again!?"
Very annoying and not sure what to do. Really do not want to do a restore.
Click to expand...
Click to collapse
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
bvz2000 said:
I am having the exact same issue with my S3. Sometimes calls take up to two minutes before they register. The phone remains completely responsive the whole time, and I can try to dial a bunch of different numbers (doesn't matter if I dial a number directly or if I quick dial a favorite or whatever). Suddenly, two minutes later it appears to register that, "Oh, I'm a phone!" and then dials all of the numbers all at once. Two minutes is a very long time to wait for the damn thing to dial. Especially when some iPhone user is sitting next to me going, "Seriously? You put up with that?" It is embarrassing.
I am also on the stock android 4.0.4 (verizon) and I would really really rather not have to wipe it clean and re-install.
The rest of the phone is fast (I am using go launcher) with the exception of the "Negative Colors" widget and the "Assistive light" widget. Both of those act just like the dialer. I hit the widgets and sometimes nothing happens for a minute. Again, the phone is completely responsive the whole time and I can hit these buttons over and over. Suddenly it all registers and then my screen flashes between normal and negative about a hundred times (once for each time I hit the button in frustration), and the led flash strobes on and off (again, once for each time I tried to get it to work).
This does not happen every single time though. Sometimes it behaves properly. Other times, it is super slow, but once it reacts, then I can make calls quickly until I let it sit untouched for a while. Then it gets all slow again.
I thought I'd try flushing the cache, but I cannot seem to find what cache I should flush. I can't find a dialer app, and the only other app that looks appropriate is the Dialer Storage app, but it does not have a cache I can flush.
Can anyone point me to a diagnostic tool that I can use to determine just what the phone is doing at this time? I have tried emailing myself the logs using log viewer, but they are huge and I can't seem to find anything there that I can sink my teeth into. Any help would be appreciated. My iPhone owning friends are becoming insufferable.
Click to expand...
Click to collapse
have you tried a different modem( also use getril to match modem and ril)
slaphead20 said:
have you tried a different modem( also use getril to match modem and ril)
Click to expand...
Click to collapse
Thanks for the quick reply. I didn't know what a ril was and did a little research. Fascinating.
As far as I can tell, and please bear with me since I am a complete noob here (though I am resonably facile with Linux), since I am running the original ROM, I don't have any influence over the RIL. Is that correct? I downloaded getril, but it says that my device (Verizon GS3) is not supported.
What is the text that would show up in a log if I made a call? I'm going to try and search the logs again, maybe that will tell me something,
On jellybean
When I receive a phone call while the phone is off I get the option to either "Decline" or "Accept". I accept by pulling the green "Accept" button down and into the half circle. Immediately the phone turns off again, requiring me to push the power button again to turn it on. Although this is something that isn't terribly hard to do, it is annoying as many times I touch the speaker button. I would be nice if when I accept the call the phone would stay awake so I can just touch speaker.
I went through the settings but could not find anything. Any idea's?
mugsaway said:
On jellybean
When I receive a phone call while the phone is off I get the option to either "Decline" or "Accept". I accept by pulling the green "Accept" button down and into the half circle. Immediately the phone turns off again, requiring me to push the power button again to turn it on. Although this is something that isn't terribly hard to do, it is annoying as many times I touch the speaker button. I would be nice if when I accept the call the phone would stay awake so I can just touch speaker.
I went through the settings but could not find anything. Any idea's?
Click to expand...
Click to collapse
This is a known issue with the Proximity Sensor not working correctly. My phone does the same thing and I am currently in contact with HTC support. I will let you know what I find out
jdawg0024 said:
This is a known issue with the Proximity Sensor not working correctly. My phone does the same thing and I am currently in contact with HTC support. I will let you know what I find out
Click to expand...
Click to collapse
Ahh... Thank you
mugsaway said:
Ahh... Thank you
Click to expand...
Click to collapse
So after a couple emails back and forth with HTC. I have been escalated to a higher tech person. Waiting to hear back
Sent from my EVO using xda app-developers app
When i got this device i thought how stupid this was and hoped after flashing a custom rom maybe it would eliminate this stupid feature of this device. It seems HTC thinks it's a good idea to turn the screen ON after ending a phone call, WTF?
At work i use my bluetooth headset all day with my phone in my pocket. I will take my phone out, dial the number i want to speak to, press power to turn screen off, put device in pocket and have my conversation. I end the phone conversation with my bluetooth headset and guess what? The dang phone's screen turns on while it is in my pocket. I guess the light sensor has zero effect here! So now since this happens and my device has a timeout of 2min i set before screen turns off my phone accidentally "butt dials" people and without me knowing i'm now calling people randomly while i'm working!
Another case. I have my phone in my car's cupholder, i use bluetooth to make a call with my car, it initiates the call to my phone and again it turns the screen ON to make the call. WHY? I never pressed power on my device to turn the screen on to make a call. So again i press the power button to turn screen off while in call. I hang up the call when i'm done via the bluetooth in my car and again the device turns the screen back ON once i disconnect the call via bluetooth.
I just don't understand the logic behind this? Is this some HTC thing or all android? Coming from iPhone 4 never had this issue so was a first for me with this device. Just don't see the reason or logic for this?
Anyway to prevent this or stop this from happening? I mean isn't that the point of bluetooth to not need to touch your device thus no need for the screen to be turned on????
+1
It seems that this is not a HTC thing because I have the same behavior on my Samsung device. Same problem as well with pocket dialing during/after a call. Really annoying. I had the same thing on my old HTC Nexus One running Froyo, so this is not a new bug. Back then I tried a lot of different apps, and none helped. I even flashed CyanogenMod on it and it didn't change anything.
I really hope someone has run across a fix whether it's an app, a patch or a whole new ROM, because pulling my phone out of my pocket to turn the screen back off TWICE for every call I make or receive is getting to be a pain.
I can't believe this behavior is voluntary on the part of the designers. If it is, please someone explain why.
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
ethanon said:
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
Click to expand...
Click to collapse
Just downloaded but no idea how to use this thing. Not very saavy with this type of stuff. How can I use tasker to turn the screen off when ending a call ONLY while connected to a Bluetooth headset? This is my biggie since it's in my pocket.
Got it to work
Ok, I downloaded Tasker and I'm impressed.
Here's how I got this to work:
1: Create new profile using STATE, then go to NET, then hit BLUETOOTH CONNECTED. Here you can specify if you want only a specific device or any Bluetooth.
2: Set new task: SET plsLock to ON
3: Set exit task: SET plsLock to OFF
4: Create new profile using EVENT, then go to PHONE, and hit PHONE OFFHOOK.
5: Set new task as: SCREEN, SYSTEM LOCK
6: Hit IF, and specify if plsLock is ON
7: Create new profile using EVENT, then go to PHONE, and hit PHONE IDLE.
8: Set new task as: SCREEN, SYSTEM LOCK
9: Hit IF, and specify if plsLock is ON.
You're done.
Since I had the same problem with the wired headset, I also created a profile with HARDWARE, HEADSET that sets the variable plsLock to ON and exit task sets it back to OFF. You can name the variable anything you want and it will still work.
If anyone has a better/simpler way of programming this, please share. I just started using this program and am still trying to wrap my head around the way this is structured.
As this stands, it works... But it's still a patch on something that should be an option in Android.
Let me know what you think.
Ok thank you I'll give it a try. Yeah could never understand why my device thinks it's a good idea to turn screen back on after ending a call via Bluetooth or not? I receive call, I then press power button to turn screen off bit continue my call, the caller hangs up, boom my screen turns on displaying the phone dialer until my time out settings turn screen off. Dumbest feature I swear. Hello phone I pressed power offbutton to turn screen off, get the hint and keep screen off until I press power button and want it back on again. No sense...
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
ethanon said:
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
Click to expand...
Click to collapse
No unfortunately not. I would greatly appreciate that! I would think it's a simple task but honestly I'm very handicapped when it's comes to stuff like this.
Basically a string for tasker that would simply just do this:
When my device is connected to a Bluetooth device whether it be my car kit, headset, stereo headset, etc. and a phone call ends where by me pressing the End Call on screen button, by ending call with car kit, headset, etc, doesn't matter but will make the screen turn off. That's it.
When connected via Bluetooth, a phone call ends, screen turns off.
Now here's a kicker and not sure if this part would be harder. I'm connected via Bluetooth headset or device, I have screen on to manually make a phone call, then while on the call I press the power button to turn screen off while on call and put device in my pocket. Now when the call eventually ends I would want the screen to stay off.
I will read into the link you provided and mess with it somewhere. Thank you for your time and help.
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
ethanon said:
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
Click to expand...
Click to collapse
Correct BUT only when connected to a Bluetooth device. My gripe is on a Bluetooth call, place a call manually then talk on headset, car kit, etc. I press power button to turn screen off then put phone back in pocket, when call ends the phone turns screen back on for some reason. Never understood this?
Been having this for a while now. When you come off a phone call, and I hang up via the red hang up button, it takes 4 to 6 th sometimes 8 seconds to actually hang up.
If the other party didn't hang up, they could hear everything I say even after I press the hang up button.
I have tried Google dialer and it's not there but stock dialer is needed for a lot of dual SIM functions.
Any advice please?
Maybe try clear cache of the app
Reboot Removes Delay
everybodylovesfebs said:
Been having this for a while now. When you come off a phone call, and I hang up via the red hang up button, it takes 4 to 6 th sometimes 8 seconds to actually hang up.
If the other party didn't hang up, they could hear everything I say even after I press the hang up button.
I have tried Google dialer and it's not there but stock dialer is needed for a lot of dual SIM functions.
Any advice please?
Click to expand...
Click to collapse
Hi
I am having the same problem and just started looking for help. The only thing that stops this is a reboot of my phone. Gradually on a scale of calls made/received (not sure if it matters which), the length of time to hang up the call increases. When it gets to "painful" levels I restart the phone and it's nearly instantaneous again.
This is a bug in the stock LG dialer. Mine started after the latest Oreo update. Pre-update, I didn't notice any real issues.
This is driving me nuts as well. Has anyone found a fix for this? In my case even restart didn't fix it. The red hangup button is taking ages to respond and the call doesn't hangup until the other party hangs up