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
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
I have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Try Wiping and flashing a new rom or doing a factory reset from within the recovery
Atheyst said:
I have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Click to expand...
Click to collapse
If you want to know what ROM you're on, go into Settings > About > Software information and it should say something under Software number. Mine says the name of my ROM.
Then just for fun you can pull down on the bottom of the list and see it stretch out and then boing back up when you let go. :cyclops:
But yeah, try wiping and if you do a factory reset make sure you back up any files you want to keep. Do a fresh flash if that doesn't fix it.
SOLUTION - PROXIMITY SENSOR CALIBRATION
Someone on here posted an app for rooted only devices that alters the sensitivity of the proximity sensor.
Dust can be causing the issue or you can use this app to fix it for you. The app fixed my problem instantly.
+Detailed information:
After the problem occured, I flashed back the stock rom with odin, then installed cyanogenmod 10.1.2
I can use my phone to do anything, apart from making calls
++Doing calls
When doing a call, the screen will be black, apart from the status bar. I cannot drop the call, unless I press the home button and hope to get the error message as written above. Sometimes, it gives me the option to drop a call in the pulldown menu. Furthermore, the screen does not switch off, when putting the phone to the ear, as it used to do.
While the call is in progress, I can hear everything clearly and on the other end of the line they can also hear me well.
++receiving calls
When my phone is ringing and I use the slider to pick the call, it will tell me "incomming call", but it will not establish connection. On the other end of the line, the seconds are already counting, but I don´t hear anything. Sometimes the phone freezes totally to the extent that I remove the battery and reboot.
++Environment
When the problem occurred, I didn´t change any settings or software.
Before the problem occured, I put the phone togehter with a container of ghanean millet-beer in a plastic bag, unfortunately the phone got wet at this occasion. As I said, this is the only problem that occurred, everything else is still working like a charm!
Because I was suspecting Software Problems, I first restored a nandroid backup and later installed the latest stable from scratch.
Now I also changed the provider and Sim, so the problem is certainly not from the network.
copy from galaktos @cyan ogenmod. com
it is because my problem is same with him
I put the phone togehter with a container of ghanean millet-beer in a plastic bag, unfortunately the phone got wet at this occasion
Service centre repair .
when I call some one or I pick up someones call the screen turns off and I cannot access the screen until the person whose calling cuts the call I observed that this does not happen every time but when I restart the phone it works fine also that this problem does not occur in mini roms .
plz need help I'm sick of this problem
ak_bagade said:
when I call some one or I pick up someones call the screen turns off and I cannot access the screen until the person whose calling cuts the call I observed that this does not happen every time but when I restart the phone it works fine also that this problem does not occur in mini roms .
plz need help I'm sick of this problem
Click to expand...
Click to collapse
I had also faced this annoying problem in some ROMs, and it is related to the proximity sensor. I found a modified LineageOS dialer apk from this thread, which had the proximity sensor disabled during calls.
https://forum.xda-developers.com/nexus-4/help/how-to-disable-proximity-sensor-nougat-t3453008
POST : https://forum.xda-developers.com/showpost.php?p=71364200&postcount=26
I have tried this only in LineageOS, and it solved the problem. The only thing is that you'll have to manually lock the screen during calls.