It is strange, but whenever I call with somebody, the screen just won't turn off when I put the phone to my ear. It turns off after few minutes because of the screen timeout, but sometimes I press stuff with my cheek.
Both G-sensor and light sensor work. Is it a common problem? This never happened with my previous HTCs :/
Matt.Murdock said:
It is strange, but whenever I call with somebody, the screen just won't turn off when I put the phone to my ear. It turns off after few minutes because of the screen timeout, but sometimes I press stuff with my cheek.
Both G-sensor and light sensor work. Is it a common problem? This never happened with my previous HTCs :/
Click to expand...
Click to collapse
I think I know your problem friend. Last I heard of this issue it was with a droid turbo. He was a hardcore conspiracy guy. So he had all the sensors n $hit covered. I'm not sure how long he had them covered. But after awhile his phone screen wouldn't turn off during calls. Once the tape was removed it worked. If that doesn't work. If your running a custom or stock based rom with tweaks just wipe the system and caches. And reflash the rom it will of course take its usual 10-15 boot up time because of the cache wipe. If you don't use custom stuff. Make sure you have your stuff backed up to google, and refer to a slightly up to date ruu thread to wipe and reset your phone.
Related
Hey guys so my Tilt 2 has been having an issue when I put it to sleep. It goes to sleep fine, but when I wake it up the screen remains black. The actual device turns on, but the screen stays black. I can still make calls, receive calls, play music, etc. but I have to soft reset the device if I want to be able to see what I am doing.
From what I can tell my problem is different from the normal Sleep of Death issue where the device simply won't wake up.
I've searched through the forums looking for solutions and have tried pretty much everything from doing a hard reset, using different roms, formatting the internal memory, etc. Even after doing all of this, my device still suffers from this issue.
Any insight into my problem would be greatly appreciated!
I assume you've tried a simple reset using the reset button or pulling the battery out and putting it back in?
Aaron McCarthy said:
I assume you've tried a simple reset using the reset button or pulling the battery out and putting it back in?
Click to expand...
Click to collapse
Yeah every time I the screen goes black I soft reset it in order to get the screen to turn back on. The problem is that the issue persists through soft resets. I currently can't suspend my device because I can't get the screen to turn back on...
hold down the volume down button and then press the reset button (the physical reset button) this should bring you into your bootscreen the multicoloured screen.. if you can get there then you can flash a new rom on your phone... and thats a whole other ball game. It gets a lot of hype as being hard but its really super easy to do if you just follow the directions.
Tilt 2 dark screen solved
With the tilt 2, if the screen does not wakeup, but you can answer the phone, hear music, etc..., it is a malfunctioning light sensor, maybe hardware, or software related (drivers), but it is fixable. Just eliminate all calls for use of the light sensor.
I had this problem and took quite a while to figure it out, as there are several apps that poll the light sensor that cause problems.
First, go to start/settings/system/power/backlight and uncheck the auto adjust backlight option
Second, go to start/settings/personal/buttons/backlight and uncheck the enable keyboard auto backlight sensor.
Last, open advanced config (need to download and install from touchxperience.com, if you do not have it), tab to light sensor and set light sensor polling to disabled.
Now, my phone works normal and will wake up properly from standby like it should. this all seems hardware dependant, as I have in my family 3 of these things and I dropped and broke mine, so bought a new one (4th in the series) and it had the SOD issues, but could restart with softrest. Took me the better part of the day to find a reliable fix, but now all is well again.
Hope this helps other Tilt 2 and similar issues.
I have a Touch Pro2 Vodafone, but unlocked, and flashed with custom 6.5 ROM and it continually has the problem of the screen going blank and not coming to life.
I have tried Energy Rhodium 29022 and another ROM but both have the problem.
I guess it might be a hardware fault, but not sure really.
Any suggestions for fixing?
task29?
Does it "always" go to the blank screen, or is it intermittent?
Also, when you say going blank and not coming back to life - does this mean when the phone is rebooting? When it's off and being turned on? What are you doing that induces this behavior? Has the phone always done this? Have you tried the stock ROM?
You could also try remapping one of your buttons as a 'Power Management' button using the keyboard configuration to see if your power button is at fault. If all else fails, try flashing the shipped Rom to see if the problem continues. Good Luck!!
Sounds like a failed light sensor. Somewhere there was an app you could install that would display the sensor reading. If it was 0 then you had a bad sensor.
wizardknight said:
Sounds like a failed light sensor. Somewhere there was an app you could install that would display the sensor reading. If it was 0 then you had a bad sensor.
Click to expand...
Click to collapse
I know of such a thing for Android, but does one exist for WinMo?
arrrghhh said:
I know of such a thing for Android, but does one exist for WinMo?
Click to expand...
Click to collapse
I want to say that there was. It wasn't the primary function of the app, but info you could get from it. It has been more than 6mo since I was fooling around with WM on the TP2.
I ran task29 before
Have tried three roms
Problem occurs e.g., today, blank screen, cannot activate, remove battery, try to turn on, get the buzzing sound which means it's turning on but still blank.
Press buttons, oops looks like I'm calling someone.
Phone still blank. Then get incoming call - it wakes up.
This happens regularly, blank and cannot wake up.
Usually charging it wakes it up.
Flash back to stock, if it's still occurring there it's probably a hardware issue. As was stated earlier, the proxy sensor is suspect for sure.
thelawnet said:
I ran task29 before
Have tried three roms
Problem occurs e.g., today, blank screen, cannot activate, remove battery, try to turn on, get the buzzing sound which means it's turning on but still blank.
Press buttons, oops looks like I'm calling someone.
Phone still blank. Then get incoming call - it wakes up.
This happens regularly, blank and cannot wake up.
Usually charging it wakes it up.
Click to expand...
Click to collapse
That really sounds like a bad sensor.
And the advantage to that is, if it is a bad sensor, you could always perform some surgery on your device and install a new screen & digitiser as I did on mine. I had a problem with a slightly rattly earpiece afterwards but I think it was something I did. Handily I was able to purchase a pre-built screen and digitiser as a single unit complete with ribbon cables, I just had to swap it out and reattach the various ribbon cables. Proximity sensor and LDR are all in the one unit above the screen... Which is quite useful as they're all tiny surface mounted components
If you don't want to invest money, and like android I think that FRX07.1 does not use the sensor. That build would let you use the phone as is.
thelawnet said:
Any suggestions for fixing?
Click to expand...
Click to collapse
Any updates there OP? Did you make any advancement? =]
my phone locks up every time i dial a phone number. the screen gets locked up (black screen) and even if i press the home button or the sleep button, it won't come back on. the only way it would comeback on is if the other person hangs up the phone. for example, i call 611, now as soon as i dial that number, the screen goes BLACK. nothing shows up on screen. only choice i have is to WAIT for the other person to hang up for my screen to light back on again. i can't hang up because the screen won't come back on until the other person hangs up. if i press power button, nothing happens. something if i press the home button. what is wrong with this phone?
btw, it is running lean rom. i previously had another rom (samething happened on it tahts why i'm on lean rom, and same issue).
i'm currently downloading the stock tmobile rom, lets see if this issue is resolved. if any of you have faced this issue please comment. thanks.
also, when flashing the roms, i always follow the correct procedure (recovery > wipe data > wipe cache > wipe delvic > install from zip. )
JoJo2211 said:
my phone locks up every time i dial a phone number. the screen gets locked up (black screen) and even if i press the home button or the sleep button, it won't come back on. the only way it would comeback on is if the other person hangs up the phone. for example, i call 611, now as soon as i dial that number, the screen goes BLACK. nothing shows up on screen. only choice i have is to WAIT for the other person to hang up for my screen to light back on again. i can't hang up because the screen won't come back on until the other person hangs up. if i press power button, nothing happens. something if i press the home button. what is wrong with this phone?
btw, it is running lean rom. i previously had another rom (samething happened on it tahts why i'm on lean rom, and same issue).
i'm currently downloading the stock tmobile rom, lets see if this issue is resolved. if any of you have faced this issue please comment. thanks.
also, when flashing the roms, i always follow the correct procedure (recovery > wipe data > wipe cache > wipe delvic > install from zip. )
Click to expand...
Click to collapse
I'm having the exact same issue, when I make a call the screen guess into sleep that can't be awaken unless whoever I was talking to hangs up. the only exception is when I'm in speaker mode but I would have to be quick before the screen guess black. I'm running ogwisdom's paranoid android and I flashed from stock Rom. any help would be greatly appreciated.
Sounds like your guys' proximity sensor isnt functioning properly.... it controls the screen dimming during calls by detecting our face. If it's not detecting your face properly, then when it thinks you have put the phone down (always) it will dim the screen and keep it that way until the call is completed like you described...
This happens often to some of us who have screen protector covering the sensor.
If the sensor is actually broken obviously you will have to replace it, but more likely its just being blocked by your screen protector or fingerprints?
You can just disable the proximity sensor like many people do. It's really not necessary anyway imo..
To diable it go to the "phone app" where your dialer is just bring up the menu, go to settings and uncheck the box that says "detect your face during calls and dim screen". Then you can just use your power button to bring the screen on and off during calls. Proximity sensor kinda worthless anyway...as far as I know.
Anyone know what use the sensor has other than screen dimming during calls? Theoretically I think it controls dimming at all times, but by default the dim kicks in after what 30 seconds(?) and who looks at their phone for 30 seconds without touching the screen unless a movie is playing (in which case auto dim is disabled!). So thats why I kinda think the sensor is useless...unless its doing something I dont know.
---------- Post added at 02:02 PM ---------- Previous post was at 01:49 PM ----------
Sounds like your guys' proximity sensor isnt functioning properly.... it controls the screen dimming during calls by detecting our face. If it's not detecting your face, when it thinks you have put the phone down it will dim the screen and keep it that way until the calls completed like you described...
This happens often to people who have screen protector covering the sensor.
You can replace the sensor if its broken cheaply,
You can remove whatever item is blocking the sensor if its being block
Or you can just disable the sensor like many people do. It's really not necessary.
In the "phone app" where your dialer is just bring up the menu, go to settings and uncheck the box that says "detect your face during calls and dim screen". Then you can just use your power button to bring the screen on and off during calls. Proximity sensor kinda worthless anyway...as far as I know. Hope that helps..
When im in a call my cheek makes the phone mute or speakerphone turn on it has even made it to airplane mode once. This has not happened to me on any other phone could this be the sensor. Has anyone else had this problem at all its very frustrating. The screen is always black like it is suppose to be during a call but buttons are still being pressed. Is there anything I could do?
enfurnic said:
When im in a call my cheek makes the phone mute or speakerphone turn on it has even made it to airplane mode once. This has not happened to me on any other phone could this be the sensor. Has anyone else had this problem at all its very frustrating. The screen is always black like it is suppose to be during a call but buttons are still being pressed. Is there anything I could do?
Click to expand...
Click to collapse
Are you stock?
yes I am still currently stock did the s-off from rumrunner that is it no custom roms
Hmm... I know it sucks but maybe try a factory reset just to make sure it's not software and if it still doesn't work it might be a defective sensor.
definitly worth a shot thanks
I've never hit the mute button specifically, BUT, I have dropped calls due to accidentally putting my phone in airplane mode with my cheek more times than I can remember. This happened a lot on stock. I'm on CM now and I think it has probably happened a few times, but not as much as stock - this could just be coincidence though.
Sent from my One using xda app-developers app
I'm was doing the same, but with turning on Speakerphone. You can try this sensor recalibration app and get it set to your liking.
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
EDIT: Thought I should give my current settings:
PS1_CANC: 9
PS2_CANC: 19
This turns the screen off from pretty far away, but eliminated the problem for me entirely.
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Had this happen as well. Not rooted. Can't remember but i vaguely recall this with other versions of android
mcgleevn said:
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Click to expand...
Click to collapse
got a crappy screen protector? that'd be my guess
Nope nothing, naked
mcgleevn said:
Nope nothing, naked
Click to expand...
Click to collapse
Same. And it doesn't happen every time.
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Possibly unrelated, but about every 1 in 5 reboots my screen won't turn on. Stays black, no back light. The phone still responds to ADB and fastboot commands, but nothing will turn the screen on until I hold down power to restart.
Same here.its happened multiple times. naked Pixel here, not rooted. its annoying.
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
honestly after some more calls with this issue, i think my dirty ear and is causing the close proximity reading... after the most recent episode, i went to the droid info app and it was reading the sensor at 0 cm and after wiping the notch off, it started to read correctly (5.0 cm) >>> i dont really want to give the haters another reason to dog the notch but, in my case, i think its going to be an issue. i may switch the "power button to end call" on and see if that will alleviate my issue for now -
mcgleevn said:
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Click to expand...
Click to collapse
Same exact thing happened with me yesterday, could it be a RAM management issue?
Roll3r said:
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
Click to expand...
Click to collapse
Thanks for the heads up. I have unrooted and naked 3 XL. This screen off thing was affecting all calls. If the remote party hung up, I was fine. If I got into someones VM, I had to sit quietly until the call dropped.
I added myself to the Phone app Beta program and updated. After several test calls, I think it's fixed.