Hi!
since a few weeks I have a problem concerning the display behaviour during and after calls. When I do a call (does not mind if I start it) and I activate the prox. sensor (e.g. when taking the phone to my ear) the display goes off as it should, but most of the time, when I take it back down, it doesn't turn on again. I read about some problems with uncalibrated prox. sensorsand some issues with CM Mod but all these threads finished with the problem beeing solved by a recent version of CM. Therefore I am not sure what to do now and so far, I didn't find a solution.
When this happens, I always try to switch it off to standby and back on... after several tries it usually works again until the next call.
So far, I tried to flash different roms... all of them more or less recent nightlies. Right now, I am using CM Nightly 258.
Would be very glad if someone can help!
Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
Display does not turn on again after calls
Started by tomcatoggo, Nov 24 2011 08:33 PM
6 replies to this topic
#1
Posted 24 November 2011 - 08:33 PM
#2
Posted 24 November 2011 - 09:38 PM
Hi there. You may have the same issue that I have. My proximity sensors do not work. My screen goes off when I answer a call and it can be a nightmare to get it on again. Sometimes I had to pull the battery especially when checking my voicemail.
I work around it most of the time by going to settings>CyanogenMod settings>Input and ticking Trackball wake. If I make or answer a call I can usually get the screen to come on again if I press and hold the trackball for a couple of seconds.
There is a small app available for free from the market called "sensor test" . Get it and run it and it will show the outputs from your sensors.
Mine shows
LIGHT
CM3602 Light sensor
0:10.0
1:0.0
2:0.0
PROXIMITY
CM3602 Proximity sensor
0:0.0
1:0.0
2:0.0
These values never change on mine which I think means they are not working. If the values change on yours when you cover or uncover the sensors then you have a different issue. Hope this helps.
Col
I work around it most of the time by going to settings>CyanogenMod settings>Input and ticking Trackball wake. If I make or answer a call I can usually get the screen to come on again if I press and hold the trackball for a couple of seconds.
There is a small app available for free from the market called "sensor test" . Get it and run it and it will show the outputs from your sensors.
Mine shows
LIGHT
CM3602 Light sensor
0:10.0
1:0.0
2:0.0
PROXIMITY
CM3602 Proximity sensor
0:0.0
1:0.0
2:0.0
These values never change on mine which I think means they are not working. If the values change on yours when you cover or uncover the sensors then you have a different issue. Hope this helps.
Col
#3
Posted 25 November 2011 - 12:35 PM
Hi!
thanks for your answer!
the proximity sensor values change: from 0:0:0 (dark) to 9:0:0 (bright), but not in steps... just the two values.
the light sensor also works... values change significantly when I hold the device below a lamp e.g.
thanks for your answer!
the proximity sensor values change: from 0:0:0 (dark) to 9:0:0 (bright), but not in steps... just the two values.
the light sensor also works... values change significantly when I hold the device below a lamp e.g.
#4
Posted 25 November 2011 - 02:50 PM
So your sensors are working, have you tried wiping the dalvic cache in recovery. Sometimes it will fix glitches and it will not break anything.
#5
Posted 25 November 2011 - 07:03 PM
...no... wiping the Dalvik cache doesn't help
#6
Posted 18 January 2012 - 07:30 PM
I have the same problem since I used s2e to move everything but /data to sd ext . Do you use the script to ?
#7
Posted 15 February 2012 - 11:28 AM
Try to disable both Screen-on animation and Screen-off animation
Settings->CyanogenMod settings->Display
This works for me
Settings->CyanogenMod settings->Display
This works for me















