Hi,
got a refurbished desire s back from htc service after bricking my first one now my phone dosen't wake up after a call. I've to connect it to charger to wake up again.
Sometimes i can avoid this bug when i press the "end call button" and then go to app drawer or something else...
Is it normal, that the screens turns off instant when doing a call although i don't have it on my ear?
I guess it's a faulty proximity sensor? Is there a way to check that the sensor works properly?
I got this bug with hyperion and endymion rom. Couldn't verify if its on stock also because i flashed custom directly.
Thanks in advance for help
That does sound like a hardware issue.
Swyped from my Desire S using XDA Premium
Hey,
I have this same problem. Also happend with my Stock ROM. Any clues?
After I receive a call the screen stays black. When I connect it through USB (charger or PC) it wakes up again.
papaganz said:
Hey,
I have this same problem. Also happend with my Stock ROM. Any clues?
After I receive a call the screen stays black. When I connect it through USB (charger or PC) it wakes up again.
Click to expand...
Click to collapse
This issue also occurs in endymion ROM.for temporary solution, just Swype your finger giving little pressure over top right part of your screen I.e just right part from where HTC is written.I think there is proximity sensor.this makes your phone to wake up.but this never happens in miui. May be software issue.
Related
For the past 5 days I have not able to answer any calls while my phone is locked. I have tried deleting all my apps and doing a master reset and can not figure out what the problem is. As soon as I set the phone down and wait 30 seconds for it to lock I can not answer any calls unless I keep the screen on which is draining my battery. I really love this phone but this problem is very annoying. I have to decline the call and then call them right back. Has anyone experienced this yet with their phone? I hope I'm not the only one.
Are you using some kind of application to lock/unlock your phone, instead of the power button or screen time out?
I had the same problem when I used tasker to put a delay on the lock when my screen turns off. In tasker I have set it to unlock the phone as soon as the screen turns off, wait 10 secs, then lock again if the screen is still off. I had this setting so that I do not need to keep on unlocking if the screen suddenly turns off while I'm still using the phone. This caused my call screen to only display the 'end call' button when a call comes in. After disabling the rule on tasker, I did not have that problem anymore. So if you are also using another app to lock the phone, that might be your problem.
I had an app called Mr. Number installed and it was causing the same problem on my phone. Once I uninstalled it, incoming calls worked just fine.
I did have the app Mr. Number installed and since uninstalling it have had no problems. I emailed Mr. Number and they're trying to get a sensation to test this problem on so I dont know how long this problem will last.
Sent from my HTC Sensation 4G using XDA Premium App
Not sure if any of you had this but I notice my phone when placed on speaker mode, after calling my screen goes blank and none of the key function work (all buttons including home, power, etc) and I had to do a battery pull. I assume this may not happen as often but I recently get it a couple times already.
I spoke with the S2 guys and notice this happens to their handheld due to the sensor set. One best way to work around is simply Turn off proximity sensor under Call setting.
This happen when I had a 2.3.6 TGY KK5 stock rom.
Moodaleon said:
Not sure if any of you had this but I notice my phone when placed on speaker mode, after calling my screen goes blank and none of the key function work (all buttons including home, power, etc) and I had to do a battery pull. I assume this may not happen as often but I recently get it a couple times already.
I spoke with the S2 guys and notice this happens to their handheld due to the sensor set. One best way to work around is simply Turn off proximity sensor under Call setting.
This happen when I had a 2.3.6 TGY KK5 stock rom.
Click to expand...
Click to collapse
yeah buddy same thing happens with my device as well.. bt it doesent always have to be on speaker mode. on normal mode also sometimes my device goes blank..
anyone here help please.....
Several users on our russian forum have reported same problem on different ROMs (2.3.4, 2.3.5 and 2.3.6). Most of them are using phone calls about 60-90 minutes per day.
I never had this issue with my 2.3.5 Germany ROM, but I am using my phone for calls just for 5-10 minutes in a week.
Tip
You don't have to replace battery. Just long press power button (over 10 seconds), and phone should reboot.
I've seen the same problem on my phone, but after I pressed the power button for about 7 seconds and let go, the screen came back and I was able to hang up the call. I've turned off the proximity sensing (settings -> calls -> proximity sensor) and haven't seen the issue since then.
cocoa7 said:
I've seen the same problem on my phone, but after I pressed the power button for about 7 seconds and let go, the screen came back and I was able to hang up the call. I've turned off the proximity sensing (settings -> calls -> proximity sensor) and haven't seen the issue since then.
Click to expand...
Click to collapse
okk i wll give it a try........
my gf is experiencing this issue on her SGR as well. After a call, the phone will become unresponsive and the red spot(light sensor) near the speaker at the top of the phone will be lighted up.
using stock + ardatdat's 1.3A kernel (default settings).
will try the proximity sensor solution and hope the issue goes away.
PauseZ said:
my gf is experiencing this issue on her SGR as well. After a call, the phone will become unresponsive and the red spot(light sensor) near the speaker at the top of the phone will be lighted up.
using stock + ardatdat's 1.3A kernel (default settings).
will try the proximity sensor solution and hope the issue goes away.
Click to expand...
Click to collapse
yes buddy after unchecking the promixity sensor in call option it 0does work... bt still sometime red sensor glows and slows my phone down..... if anything of this kind is experienced then do share..
should be fine once you switch the proximity sensor off as thats what it seems to cause all the prob and the only thing u have to live with is ur screen doesnt go dim when you stick it to ur face while talking
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
peslap said:
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
Click to expand...
Click to collapse
I wouldn't worry too much about it, its just a glitch, it happens to me sometimes too , when i put it on speaker and i get close to the phone , the screen turns off and it comes back after a while. it doesn't bother me too much. It might be that the sensor is too sensitive. Have you tried a custom rom ?
This issue happens to my son's phone too.
Anyway, it shouldn't be random, please double check if it happens ALWAYS after a phone reboot, this is the behaviour of mine
I want the moderator to ban me.
display issue
Hello,
I have started to face the same issue mentioned above.
On googling I came across the motorola forum (google search: Moto G Proximity Sensor Software Issue)
It seems the issue is being discussed there and apparently they need more moto g users with this issue to help them out solve this.
On using z device i noticed the proximity sensor value stuck at 3 with no change covered/not covered (sensor) [Phone running without restart for 6+ hours]
After restarting the phone the sensor value in z device changes. 100 (uncovered) to 3 when covered.
I will keep checking this every few hours to see when does the proximity sensor stop working without restarting the phone. (uptime)
Can the DEV's here help us out? looks like Motorola may take some time in finding a solution to this issue.
This seems to have went away with 4.4.3 and the new Dialer app.
At work yesterday my phone was fine..I pulled it out of my pocket during a break and the screen wouldn't turn on..then I noticed the backlight was on and I can feel the screen vibrate when I hit where the home button should be but no picture. I am able to hear notifications and use my moto360 to make phone calls etc but no picture just a black screen and backlight is on.. Using my nexus 5 currently but wondering if anyone else has experienced this..T-Mobile said they would replace it under warranty.
Derekwolfee said:
At work yesterday my phone was fine..I pulled it out of my pocket during a break and the screen wouldn't turn on..then I noticed the backlight was on and I can feel the screen vibrate when I hit where the home button should be but no picture. I am able to hear notifications and use my moto360 to make phone calls etc but no picture just a black screen and backlight is on.. Using my nexus 5 currently but wondering if anyone else has experienced this..T-Mobile said they would replace it under warranty.
Click to expand...
Click to collapse
Hello.
I have the exact same issue, I got a phone with a broken screen, it only had black backlight, then I changed the screen with a new one and still the same thing happens. Tried with two screens.
After replacing the screen I repaired the software via Sony PC companion, but it didn't work.
Does anyone know what the issue is here? Is it a dead motherboard or something else? Just so that I know to stop trying to fix it.
My unit isn't under warranty anymore because it had physical damage so replacing it via Sony is a no go.
The phone boots fine, I get audio reading of menu options for the initial setup, even the touch works, I can select options but I have no image, only the backlight.
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Chasharv said:
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Click to expand...
Click to collapse
Just press the power button when that happens, screen will turn on again. Done.
Nexus 5 black screen: thanks, but more help needed
beekay201 said:
Just press the power button when that happens, screen will turn on again. Done.
Click to expand...
Click to collapse
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Chasharv said:
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Click to expand...
Click to collapse
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Nexus 5 black screen, solved
beekay201 said:
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Click to expand...
Click to collapse
Thanks for this, but the problem was that the screen blacked instantly on making or receiving a call and was unresponsive, so the only way forward was to press the power button. This either terminated the call or shut down the phone, according to how it was set, so neither was useful.
As I said originally, I suspected the proximity sensor was faulty as the a proximity detector sensor app always indicated that there was something close to it. Hence the phone would assume it was next to my ear when making or receiving calls, and so black the screen. This morning, for reasons that I don't understand at all as I have not changed anything on the phone, the proximity sensor is reported as working and the phone behaves as it should on making and receiving calls!
I suppose that either the sensor has an intermittent fault, or something in the phone's software has changed to permit it to work. I have a couple of week's left before the Amazon return window expires, so I will monitor the situation.
Thanks once more for the help.
Chasharv
I have the identical problem with my nexus 5 running stock kitkat. Makes it very hard to use the keyboard to reply to automated requests to "if... press 1, if.... press 2".
Is it possible to turn the proximity sensor off? I don't need it and it just causes problems for me.