Does anyone else have this problem? On previous CleanROM builds and now on the latest ICS leak I have to turn the power on to see my screen. It is very frustrating when wanting to hang up or mute and unmute calls.
thanks.
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
mjones73 said:
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
Click to expand...
Click to collapse
Interesting. Thanks for the response.
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
tCizler said:
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
Click to expand...
Click to collapse
Not seeing any issues like that either. I was on a 40 min call this morning where I had to dial in an access code after making the initial call, I was able to mute/unmute multiple times and towards the end I was checking my email and facebook before it was over without any lock ups or anything.
I cannot find a setting for using the proximity sensor during phone calls. I thought my old EVO had a setting like this!?
I am having the same issue. Proximity sensor shuts the display off, but doesn't turn back on after moving away from head.
Started with latest "official" leak. 3.14.605.5 71ORD
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Thanks for the response. I am gaining confidence that it is not my phone.
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
jayochs said:
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Click to expand...
Click to collapse
I have had mixed results. Seems to be better after a reboot.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
If you really want to know whats causing it, make a phone call while you're plugged into your computer, and run logcat. It will show you whats going on with the prox sensor.
flying_pigs said:
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
Click to expand...
Click to collapse
No but I was thinking about trying it, but it's a lot of work just to test it.
Sent from my ADR6425LVW using Tapatalk 2
works fine here too... fully stock 3.14 leak, frozen bloatware.
I had this problem and like the rest of you thought it was the rom/leak I was using.
It wasn't. The HTC proximity sensor is extremely sensitive. It is right above the left end of the checkmark next to the verizon logo at the top of the phone.
If you are using a screen protector and it does not have a cutout for the proximity sensor, you're going to cause problems. I used both a crystal clear, then an anti-glare screen guard and even though they are obviously quite clear they both screwed with the proximity sensor.
I found the RND Power Solutions screen protectors DO have a cutout for the sensor and work flawlessly. No more issues.
I have this problem too I'm on the .22 ICS leak if I go back to GB it works fine might try the 5/7 leak and see if it happens on that.
Sent from my ICS Rezound
I had this problem but then soon realized it was my screen protector.
I would get a call and as soon as I answered it, without even putting my phone to my ear, the screen would shut off.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Well, i stand corrected... I took my screen protector off, no luck. I reverted back to GB, no luck. I downloaded several sensor testing apps and all said the proximity sensor was dead. I got a "new" phone coming in the mail tomorrow. As much as i didn't want to hear it was a hardware issue, you were correct. And after a very easy google search apparently this is almost an epidemic with the rezound. Oh well, here's to hoping my replacement doesn't have way more problems than just a proximity sensor.
Thanks again flying_pigs
Related
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
Rezound is S-0ff.
Makes calls and allows view of keypad during calls fine with G-Bread.
However;
Did latest ICS leak, and phone won't stay lit AT ALL during calls.
Can't press "3" now because I can't see it anymore. Sometimes have to
pull the battery to get out of a call.
Last nite late I reinstalled my last nandroid of GB after doing 2.01RUU.
And now the proximity sensor is fine again.
Do any of you ROMmers have an idea, or is this specific to 1 phone?
A lot of people have reported issues with dust in the sensor, me being one of them. I piped my phone open to recolor the softkeys, and cleaned out the sensor while I was in there. Now it works great. Maybe it is just a difference in the way the two use the sensor? Try blowing it out with compressed air.
if could be that the rom you are using has a ro.rill that may delay blackscreen i was testing my rezound today and figered that out
GrayTheWolf said:
A lot of people have reported issues with dust in the sensor, me being one of them. I piped my phone open to recolor the softkeys, and cleaned out the sensor while I was in there. Now it works great. Maybe it is just a difference in the way the two use the sensor? Try blowing it out with compressed air.
Click to expand...
Click to collapse
I did the exact same thing and it worked. After I installed ViperRez the phone would sometimes stay lit going towards my ear, then go dark when I took it away. Pretty much opposite the way it's supposed to LOL. Then I read (on XDA) about dust getting in the sensor area, just below the earpiece speaker just below the speaker and a little to the left of the Verizon V logo. I wiped it clean, then when I got home I CAREFULLY blew it out with compressed air, and that did the trick. I haven't had the problem since.
hey all
loving the 1 year+ with the atrix, but a few problems still affecting me. On neutrino 3.02 is anyone is wondering.
1)most of the time, when i take calls, the screen turns off as normal due to the proximity sensor, but refuses to turn back on after i take the phone away from my ear. no amount of pressing any buttons, physical or capacitive, will turn it on, and a battery pull is required.
2) im pretty sure i've read that this is a manufacturing defect with the atrix, so please correct me if i'm wrong. sometimes the screen will randomly press buttons, even when my hands and the screen itself is dry.
any solutions to the above?
thanks in advance
AFAIK, no to both
andresrivas said:
AFAIK, no to both
Click to expand...
Click to collapse
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
sidewinder_x5 said:
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
Click to expand...
Click to collapse
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
andresrivas said:
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
Click to expand...
Click to collapse
Ah okay, i see. thanks for the clarification. its a shame the stock rom isn't any good for me then, otherwise i wouldn't be having this problem!
as for the screen, my experience is that it happens when the screen first turns on, no matter what app i'm using. doesn't happen when the screen is already on, which is interesting. i remember reading a thread which said that the digitizer wasn't properly attached for this phone, meaning that it's destined to go bad at some point. i'll have to see if i can find the thread again.
once again, thanks for the clarification!
I am rooted, and currently runny no-name ROM but rom doesnt seem to matter. My proximity senser is giving me issues. Testing it showed that if i cover it it will recognize it but then is stuck not sensing me removing it. I dont have any case or screen glass that is covering it. Anybody else having this issue?
Yes I have had this issue since day 1. Stock not rooted
Sent from my LG-H901 using Tapatalk
Have had the same issue since day one, 11/10/15. Not rooted. Aside from an ok battery life, this is the only problem I have with the LGV10.
i have this problem also.. its happening more and more when hanging up a call. I have to press the back button to get the screen back on.
Ludeape said:
i have this problem also.. its happening more and more when hanging up a call. I have to press the back button to get the screen back on.
Click to expand...
Click to collapse
Now it does it every call on mine, but test with app Aida64 works fine
Me too .. Any Fix can solve that ?
₪HuEx₪
I noted each time I make a call, the display immediately turned black. It auto turn black without me even taking up the hone up to my ears. I needed to press the power switch to have the display lit up again. Is this a proximity sensor defect ??
Same issue
mobile88 said:
I noted each time I make a call, the display immediately turned black. It auto turn black without me even taking up the hone up to my ears. I needed to press the power switch to have the display lit up again. Is this a proximity sensor defect ??
Click to expand...
Click to collapse
Yea I'm dealing with the same issue on my at&t model, it's definitely a proximity sensor issue. Also, I find that the proximity sensor functions relatively OK outside of the phone app when I'm on a call in terms of lighting of fading to black...I haven't found a fix yet, hopefully it's a software issue though somethings telling my it's not... Just another defect in a long line of LG phones as of late
Applez2androidz said:
Yea I'm dealing with the same issue on my at&t model, it's definitely a proximity sensor issue. Also, I find that the proximity sensor functions relatively OK outside of the phone app when I'm on a call in terms of lighting of fading to black...I haven't found a fix yet, hopefully it's a software issue though somethings telling my it's not... Just another defect in a long line of LG phones as of late
Click to expand...
Click to collapse
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
thebiker said:
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
Click to expand...
Click to collapse
I've cleaned it several times to no avail
I have noticed occasional "quirkiness" while in the phone app, but not to the point of requiring a battery pull. Example, connected via Bluetooth, while plugged to a charger in a call, no way to wake the phone without pulling the charger.
Sent from my VS990 using Tapatalk
thebiker said:
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
Click to expand...
Click to collapse
Thank you. Thank you. Your proposed solution works very well. Now no more this problem. Had never thought the sensor could be dirty or blocked over time. I had the phone only about 2 months
Problem update
Okay, I've found new info on the proximity sensor problem. Firstly, I noticed that my proximity sensor still works with the second screen, if I cover it up when my screen is off it goes black and comes back on when I remove my finger. Secondly, if I was on the phone but not actually in the phone app it would behave normally sometimes. Now today I found out that when I'm in the phone app, if I'm talking on the phone through the speaker the screen does not go black, as soon as I take it off speaker, the screen goes immediately blank. Still have not found a fix, but just more info that may help define what the actual problem is.
anyone have any update on this? this issue seems to be getting worse for me
Same issue, drives me nuts. This phone is a disappointment to me overall. Have an S7 on pre-order with Verizon. Can't wait to get my hands on it!
Had same issue just happen on the AT&T LG Escape 2. (Yes I know its a year since this thread was started)
It was the proximity sensor but the "T-shirt wipe" method didn't work for me.
What I did realize there was some gunk on the sensor, and I used a cotton swab (Q-tip) with alcohol and rubbed it till it was visibly clear of gunk. Now it works fine again..
odesskiy said:
Same issue, drives me nuts. This phone is a disappointment to me overall. Have an S7 on pre-order with Verizon. Can't wait to get my hands on it!
Click to expand...
Click to collapse
Turn of Gestures
Was facing the same issue
Went into settings
Call
Turn of both gestures auto answer and flip to silence