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.
Related
Hello. I've had this device for awhile now and it's probably the best phone I've ever had.. except I started to have problems with regards to calls just recently. I actually rooted the device about 2 months ago and am currently using the Rombie mod v2 (JPC), if that helps. Anyway, the problem happens in the middle of a conversation, where the proximity sensor somehow disappears and the speaker mode is activated on its own (or maybe it gets in contact to my skin, I'm not sure, since the screen is supposed to remain blank). After that, the device becomes unresponsive: the touch sensitive menu and back keys don't work, and neither does the screen itself..but the hard key home button works and I could still hear the other caller via loudspeaker. I force a reset and everything goes back to normal (I mean this call issue doesn't happen all the time). I don't have any screen protector to affect the performance of the sensor. Anyone can help me out with this? Thanks!
Hi there
I'm quite happy with my Nexus One... a very nice change from my old BlackJack 2. However, I have one issue.
When I get an incoming call, sometimes the screen won't wake up at all. Pressing the trackball, etc. does no good. I installed a program called noblock and now it's waking up after the call is over, but the other end has to hang up first.
This has to have something to do with the screen lock in relation to the proximity sensor or something. I'd really love it if I could just set the screen lock to manual, so I can press the power button to turn the screen off and on, getting rid of the slide to unlock screen entirely.
I tried a fix from an older thread to disable the proximity sensor, but it had no effect. It was adding a line (gsm.proximity.enable=false) to build.prop.
Can anyone give me a direction to go? Thanks!
i have some issues with turning my screen on sometimes, it will come on briefly and turn off with just the backlight for capacitive buttons on
2.3.4 ? Are you sure ?
It's some CM nightly ?
Hi!
Because I didn't get any answer in the help-thread I try it this way.
When you receive a phone call on your XZ, does the screen turn on again when you move the phone away from your ear?
This problem drives me crazy! Every phone call (active and passive...) the display of my phone turns off (as it should) when I put the phone to my ear. When I put the phone away from my head, the screen doesn't turn on again. I always have to press the power button to enable the display again. In rare cases, the display turns on as it should. But when a phone call is longer than a few seconds, the display won't turn on again.
The only reason for this problem I've found on the internet is the usage of a screen-protector. Actually I have a screen protector installed, but is has a cutout around the proximity sensor. I've also tested the proximity sensor with an app - it turns on/off correctly when I move my hand in front of the phone...
Does anybody of you experience this issue? I've tried a lot of firmware versions, but it's everytime the same... No matter if I use CM10.2 or different stock roms...
I hate it so much - not being able to stop a call before being redirected to an answering machine only because this piece of shi*** refuses to turn on the display during a call.
I'm looking forward to your answers - I can't imagine that my XZ is the only one that shows this behaviour.
Regards
is there really nobody with any screen on/off during call problems? can't imagine that my XZ is the only one... or is there an android-"feature" I donn't know?
I've already removed my screen protector... but nothing has changed...
I also have this problem frequently, i enabled power button to end calls under accessibility setting so if i press it, it ends the call, so could be partial solution to allow you to end calls, but not a real solution at all if you want an option not to end the call but to have the screen turn on only. Let me know if you find any other solutions
Sent from my Sony Tablet S using Tapatalk
Actually stopping phone calls isn't my main problem. But it annoys me that I can't check the current time by removing the phone from my head for a second. Also when I have to interact with an answering machine (windows activation hotline for example^^) - everytime I have to input a number during a call this f*cking screen is off and I have to press the power button.
Don't people use their XZ for making telephone calls? Am I the only person on earth who uses the phone for other things than watching movies and surfing the net?
I also want to know if this is a general Jelly-Bean problem... If so, replacing my phone with another one would be meaningless.
Press the power button twice to activate the screen during call.
Sent from my C6603 using xda app-developers app
Pressing the power button ONCE also works to turn on the screen during a call. But that's the point. I do not want to press this damn power button. What does the phone has a proximity sensor for??? When I start a call and remove the phone from my head after a few seconds, the screen will mostly turn on itself. But after a while (a minute or longer) moving the phone away from the head will not turn on screen anymore...
Is it too hard for phone manufacturers to build a phone that can be used as a phone? If I wanted to have a tablet I would have bought one...
Problem solved. I have a Nexus5 now and it is just awesome. May the new owner get angry with this piece of sony sh*t.
Sent from my Nexus 5 using xda app-developers app
Turn off phone
Press firmly on proximity sensor
Turn on phone
Once on main screen
Press firmly on proximity sensor
Try to make a call
I hope it works for you
Sony experia z1 how to on proximity sensor.
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...
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.