Hi all there
I have been having problems with the touchscreen becoming unresponsive after any blackout - intentional lock, screentimeout, wake from phone call.
It's a fresh install and apparently this is a common problem: code.google.com /p/freexperia/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=&id=2410
I solved it by flashing the lightning kernel from the development forum.
Hope it helps somebody.
Daniel
stormsaber said:
Hi all there
I have been having problems with the touchscreen becoming unresponsive after any blackout - intentional lock, screentimeout, wake from phone call.
It's a fresh install and apparently this is a common problem: code.google.com /p/freexperia/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=&id=2410
I solved it by flashing the lightning kernel from the development forum.
Hope it helps somebody.
Daniel
Click to expand...
Click to collapse
It's because of double tap to wake which does not work on Xperia ZR disable it from display in options
harshal.rio91 said:
It's because of double tap to wake which does not work on Xperia ZR disable it from display in options
Click to expand...
Click to collapse
I think there might be a buck in FXP331 which prevents disabling of DTW? I couldnt disable it anyway but its disabled by default with lightning. Have had no problems or bugs at all with this setup, that I've found yet.
persistent dt2w has been in CM11 nightlies since a few weeks ago
chewdaniel said:
persistent dt2w has been in CM11 nightlies since a few weeks ago
Click to expand...
Click to collapse
Apparently I'm still having a problem with this, even though dt2w is disabled for me. It only happens after a call.
During a call, my screen goes black. Nothing I can do wakes it up.
If the other person hangs up first, the screen returns to normal.
If the other person does not hang up (e.g. answer phone, etc.) the screen remains black and I must remove the battery.
This is problematic for me. Is anyone else experiencing similar?
For now, perhaps there is a way to remap a key - for instance the shutter button - to hang up the call? Unfortunately the apk 'button remapper' (lifehacker.com /5705224/buttonremapper-reassigns-your-android-phones-buttons) did not seem to have any way to select that key. Does anyone have any other ideas or solutions?
stormsaber said:
For now, perhaps there is a way to remap a key - for instance the shutter button - to hang up the call? Unfortunately the apk 'button remapper' (lifehacker.com /5705224/buttonremapper-reassigns-your-android-phones-buttons) did not seem to have any way to select that key. Does anyone have any other ideas or solutions?
Click to expand...
Click to collapse
The relevant keys are 568 (soft press to focus) and 766 (long press to take picture). 766 is already set to WAKE the screen, and I just set 568 to do the same. I'm guessing it won't work though.
Hopefully someone else has had this problem and knows a solution...
Related
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Unresponsive phone perhaps, because as far as I know, nothing of the sort happened to me ever.
Also, does the screen light up when you end the call...let's say by using power button?
Not likely, but I'll mention anyway, check if anything is blocking the proximity censor - holding habit, cellphone case etc.
Similar issue,any way to disable the proximity senzor?
DrGreem said:
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Click to expand...
Click to collapse
I have pretty much the same problem,the screen remain turned off after i remove the phone from my ear and i can't activate the screen or press any buttons until the other person terminates the call.
I run a proximity test from the Hidden Menu and the sensor detects as NEAR all the time even though nothing is in front of it.
I reinstalled several roms and i still encounter the same issue therefore it must be a hardware problem.
I would like to specify that i don't use a screen protector therefore the senor is not blocked in any way.
Is there any way to disable the proximity sensor completely?is there a application or a setting for that?
DrGreem said:
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Click to expand...
Click to collapse
andreita99 said:
I have pretty much the same problem,the screen remain turned off after i remove the phone from my ear and i can't activate the screen or press any buttons until the other person terminates the call.
I run a proximity test from the Hidden Menu and the sensor detects as NEAR all the time even though nothing is in front of it.
I reinstalled several roms and i still encounter the same issue therefore it must be a hardware problem.
I would like to specify that i don't use a screen protector therefore the senor is not blocked in any way.
Is there any way to disable the proximity sensor completely?is there a application or a setting for that?
Click to expand...
Click to collapse
I have had the same problem, with many roms. I think if you are on some of the ICS roms, you will have to expect some bugs, like this. I am now on Temaseks build 135.1 with his kernel and I dont have any of these bugs. It seems ICS for our P990 is to be expected soon, so try a ROM as close to stock as possible and wait for our ingenious developers to get the last drivers working and you will see a lot of bugs disappearing. I would not recommend you to disable additional hard/software.
One app that has helped me though, with some of the ICS issues, is AnTuTu CPUMaster. A free app in Play and it allows you to set your minimum clockspeed a little higher than standard, I set mine around 400Mhz and it took care of many of the little bugs related to phone not reacting according to expectations.
Good Luck
Have the same problem and man... its a huge pain...
I am on the official CM7 latest release. I used to be on temasek's one and did not encounter the problem. As I can;t change ROMs these days, any quick fix, calibration app that would do the trick? Thanks!
I've noticed after using apps that need to be enable in Accessibility like "floating notifications " the lock screen becomes extra sensitive allowing just one little tap to unlock the device.
Is this normal? Or is it a bug.. And if so how to fix it?
Hello,
This seems to be plaguing all HTC Ones unfortunately.
http://forum.xda-developers.com/showthread.php?p=41725088#post41725088
I don't think there is a fix yet and I'm not sure if running non-stock Sense roms fixes the issue
@YoungAceAtlanta @vitallish
Thanks to you guys I noticed this issue and made a fix
http://forum.xda-developers.com/showthread.php?p=41744250
Yeah noled causes this as well. Even when phone is ringing while it is being locked, a plain tap can answer the call. I noticed the problem when I missed a call by accidentally tapping the reject button.
Greetings everyone. Device - XT1056, GSM unlocked. After going from Cm12.1 to stock 5.1 then back to Cm12.1 a problem occurred. When I'm getting a call with screen on, the screen with caller and answer button does not appear only sound . When it's on home screen I can switch pages, but no answer options. The solution I use is to turn off the screen with power button and the the incoming call screen appears. When I'm using any app and getting a call - app freezes and navigation buttons stop working. Same solution - to turn off the screen and then answer the call. So maybe someone knows what's this about and some ways to resolve this?
I had a similar issue on previous nightlies. Check today's build, I think this commit solved it: http://review.cyanogenmod.org/#/c/102378/
Thank you for the info, can't flash it right away, at moment I'm using it with activated "Heads-Up notifications" which partially solves the problem, it became possible to enter call screen through on screen notification.
hi, i'm having a issue with the proximity sensor. Sometimes when i answer calls, the screen stays black even if i press the lock button, sometimes i can't even answer because i can't turn on the screen. Once it had the problem, if i open an app to test the proxymity sensor it tells me that the screen in always covered. If i reboot the phone everything goes back to normal, until the next time it decides to malfunction. I don't use any screen protector and i had this problem with resurrection remix rom and CM 13 snapshot... Anybody had the same issue? Or knows how to fix it? the thing that is driving me insane is that it does this only sometimes, at random...
There's a fix to this. Go to accessibility settings and tick power button to end call. Then reboot. And then untick it. Itll be solved after it. Had the same in my nexus 6 too.
akholicc said:
There's a fix to this. Go to accessibility settings and tick power button to end call. Then reboot. And then untick it. Itll be solved after it. Had the same in my nexus 6 too.
Click to expand...
Click to collapse
I tried and it seemed to work at first, but today the issue was back...
mirko902 said:
I tried and it seemed to work at first, but today the issue was back...
Click to expand...
Click to collapse
I had same problem on my phone. I discovered Proximity Sensor Reset through another XDA post which fixed the problem for me. Google Play Store, it is simple and has remained effective through reboots and ROM updates. Maybe it will resolve for you and others too.
Sent from my Nexus 6 using XDA-Developers mobile app
I've had this problem with 2 different roms now (PureNexus, Chroma) on a few kernels (stock, ElementalX) so I'm not sure whats causing it but I need a fix. In a call, many times the screen just stops responding. Sometimes I can turn the screen on/off using power button and its fixed. Other times nothing works and I have to do a hard reboot by holding down power key since nothing else works on screen.
This is on latest version of the rom/kernels. Any ideas?
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Only when in contact with ears?
akholicc said:
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Click to expand...
Click to collapse
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
ECrispy said:
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
Click to expand...
Click to collapse
I'm having a similar issue from the last month.. I'm on DP5
when i get a call most times the screen is off.
To answer the call i've to put on the screen, unlock the phone and then go to the heads up notification and choose answer there..
waiting for nougat final hoping it'll fix this.
Tried fiddling around with notifications importance setting.. it helped a little but then there was the annoying heads up showing along with the regular incoming call screen.
Sometimes (very rarely, has happened twice) the screen just remains black and will only work normally after a reboot.
Anybody have any suggestions?
I was having similar issues, also on the Developer Preview and I ended up noticing that the phone app was blocked from showing any notifications despite the fact that I never set it that way. I would hear the call ringing but would never see the screen to answer. Just changed that setting and everything was back to normal. Perhaps something is causing the phone app to fail to show notifications for you as well.