black screen during calling with the lumia 930

Hi every body I solved the problem so simply

why I am late because I broked my lcd 1 year ago and I didn't flow issus

notice that the double tap problem and proximity is one. this is because of the gap between sensor location and digitaizer.

what you need to do is to open the back cover and simply put some paper like visit card cuts there behind the sensor at the right top side of the screen and put the cover back again notice it should not to be think that much to confront closing the cover in other hand you need to push the sensor forward a little bit to get  aproximite of the distance in front of the phone .you dony need to replace any thing at all :) if it works for you let me know :) 

love microsoft

massuod-iran

There seem to be a number of causes suggested for this issue.

I have had my Lumia 930 for about 5 months and it has just started doing 2 things both of which are related and both appear to be related to the proximity sensor.

1 - Screen going black when making a call. This is very annoying as if you need to use the keys or switch to the speaker phone during a call. Even ending a call is not possible unless you bring the screen back up using the power button. Hardly convenient.

2 - Double tap to wake not working. Presumably the proximity sensor is telling the phone it's in your pocket due to the ambient light therefore 'double tap to wake' is disabled.

I have been over my phone with a fine tooth comb and cannot detect any physical imperfections. The proximity sensor was clean, there is no sign of anything being wrong with the screen fixing, no movement and no misalignment. Pressing on the area around the proximity sensor made no difference what so ever. I removed the third party screen protector and the third party case neither of which made any difference. I tried a soft reset which made no difference but before I tired  full factory reset I thought I would try one of the suggestions made earlier in this thread.

I switched off 'Double tap to wake' in Settings>system>touch.

Returned to start screen and did a 'soft re set' by pressing AND holding the power button for around 10 seconds until the phone vibrated and the Nokia log re-appeared.

When the phone starts 'Double tap to wake' is on by default and I found it works perfectly and the screen does not go blank during a call any longer unless the phone is lifted to your ear which of course is how it is supposed to work. If 'double tap to wake' is not on by default try switching it to on.

The above would suggest to me that on my phone at least and possibly some others this is a firmware issue rather than hardware related. Perhaps certain apps. are causing some sort of issue or conflict which is causing the problem but the above seems to work. Hopefully the update to Win 10 may solve it all together.

I would suggest that if this is the cause then sending the phone away for a hardware repair is unlikely to fix it permanently  either so this may be the preferred option for some and hopefully this will help somebody out there.

1. switched off ‘Double tap to wake’ in All apps » Settings » System » Touch,
2. returned to start screen, and
3. did a ‘soft reset’ by pressing AND holding the power button for around 10 seconds until the phone vibrated and the Nokia log re-appeared.

Yes, this was suggested before. In your case, did that solve your issue permanently?

Could still be hardware related, because that might have cleared a hardware capacitor. I do not want to insist on a hardware issue – however, because several Lumia 930 go out of warranty these days, I would rather send it in before it is too late, rather than going for false hope, you know.

Indeed I am aware this has been suggested before and in fact did refer to that fact in the part of my reply that you omitted. What I did note was different when that was previously suggested was that 'double tap to wake' had to be switched back on after the soft reset was done. On my phone I didn't have to do that as it does seem to be 'on' by default and was set to 'on' after the phone re-started even though I had switched it off before a did the re-set.

I can't say it has fixed it permanently on my phone, I just know that after several days now the problem has not recurred and even if it does (if it is a firmware issue it likely will) a simple carry out of the above should sort it.

I am not suggesting for a second that if people think their phone should be sent in for repair they should not. Of course they should - I am just suggesting there may be more than one cause of the problem, in my case my phone shows no sign of physical imperfections and pressing the phone corner near the proximity sensor had no impact either.

Its entirely your choice if you send the phone in or not, what worked for me may not work for you.

Good luck with what ever you decide to do.