While making a phone call the proximity turns the screen off and keeps it off, making it difficult to toggle the screen while in calls.
This is really annoying while calling your voicemail.
Currently running unofficial CM
Thanks for your thoughts.
Full story Here:
I get to mess around with the DNA for a few days, but i'm having a proximity sensor problem,
with CM and Stock Rom, do you have the same? Or is the device I have just defective.
It's a mostly an in call problem, where the phone screen goes blank and
(lets say you're in voicemail) you can't dial your password etc.
(The Screen won't come on even with the power button until 30 seconds after the call has ended.)
Your screen should come back on right when you take it away from your face. Do you perchance have a screen protector on it?
Sent from my VIPER DNA
I have the DNA and I am experiencing the same thing, but we probably have a little bit are a different scenario. Here are the details.
My digitizer broke so I bought a new LCD/digitizer assembly (LCD broke when trying to replace just the digitizer). Prior to it breaking I had CM 10.1 installed. When I replaced the screen I started experiencing the same issue described above. As soon as I place a call the screen goes blank and does not come back on until 10-20 seconds after a phone call. Regardless of formatting/wiping/etc. this has never gone away.
I installed Venom 1.3.1 to see if the ROM had anything to do with it and now, randomly, the sensor works. Also, even if the screen does shut off when press Send, I can press the power button to bring the screen back up (i.e. 5/10 phone calls the proximity sensor will work as it should. The other times the screen will go blank and pressing the power button will turn it back on.
I reinstalled CM 10.1 this afternoon to test a fresh install (I booted into recovery wiped factory data and formated SDcard then installed CM10.1) and the screen shuts off when I press send and stays off until the call is disconnected.
Is this a proximity sensor driver issue?
I have not tried using the phone after I returned back to stock flashing the RUU method.
Thanks for any feedback.
softBrikt said:
I have the DNA and I am experiencing the same thing, but we probably have a little bit are a different scenario. Here are the details.
My digitizer broke so I bought a new LCD/digitizer assembly (LCD broke when trying to replace just the digitizer). Prior to it breaking I had CM 10.1 installed. When I replaced the screen I started experiencing the same issue described above. As soon as I place a call the screen goes blank and does not come back on until 10-20 seconds after a phone call. Regardless of formatting/wiping/etc. this has never gone away.
I installed Venom 1.3.1 to see if the ROM had anything to do with it and now, randomly, the sensor works. Also, even if the screen does shut off when press Send, I can press the power button to bring the screen back up (i.e. 5/10 phone calls the proximity sensor will work as it should. The other times the screen will go blank and pressing the power button will turn it back on.
I reinstalled CM 10.1 this afternoon to test a fresh install (I booted into recovery wiped factory data and formated SDcard then installed CM10.1) and the screen shuts off when I press send and stays off until the call is disconnected.
Is this a proximity sensor driver issue?
I have not tried using the phone after I returned back to stock flashing the RUU method.
Thanks for any feedback.
Click to expand...
Click to collapse
i believe its controlled by the kernel.
reaverclan said:
i believe its controlled by the kernel.
Click to expand...
Click to collapse
I have never been very enthusiastic about flashing different Kernels (I haven't researched enough about them to know if I can flash any kernel with any ROM). I will research that and test accordingly. Thank you. I will report back here when I have reached a conclusion or with further questions.
you should be able to flash any aosp kernel on a aosp rom and sense ona sense cept for maybe sense 5 roms that im not to sure of.
reaverclan said:
you should be able to flash any aosp kernel on a aosp rom and sense ona sense cept for maybe sense 5 roms that im not to sure of.
Click to expand...
Click to collapse
I'll do some testing and see what happens. Thank you.
Guess I should have looked in the questions and answers section first. The app i reference in my second post here should fix it for the OP. Crank the top slider up to 100 and see if the 'far' or 'near' status changes when you put your finger over the sensor. If it does then adjust it to activate when an object is very close.
http://forum.xda-developers.com/showthread.php?p=43053376#post43053376
Sweet app used it to compensate for the thickness of the otterbox defender.
Sent from my VIPER DNA
Related
Hi everyone,
funny thing happened to my Mozart. Whenever I make a call the screen shuts off like it should, but it doesn't turn on again when i remove it from my ear until the call has ended.
Which works fine if the other person hangs up, but it means I can't hang up. Whenever I reach a voicemail i have to take out the battery to hang up!
First i thought it was a rom issue, i had just gotten my hands on the mango beta when i first noticed it. I thought it might be buggy.
But the problem remains after hard reset and flashing with a different rom (pre-nodo & nodo).
I found out that the sensor still works. The screen is reactivated when i shine a bright light (halogen spot or so) onto it - but only for as long as the source shines onto the sensor, else the screen shuts off again. wierdly enough, direct sunlight doesnt seem to be enough to trigger it anymore.
since i upgraded my phone with a 32GB microSD I guess I'm not eligible for warranty, huh? but im pretty sure it happen long after and i didn't accidently break something while opening the phone.
very weird... any ideas?
I had this problem on the weekend.
I removed the matt screenGUARD, and the problem disapeared.
Also you can reactivate the screen by pressing the on/off button...
thanks for your comments.
unfortunately, I don't use a screen protector and the standby-button doesn't work during a call
I have this problem also, with stock 7392 rom. The sensor seems to work when dialing, but stops a short time after a call is connected.
The power button works for me to turn the screen back on however...
Where is the proximity sensor ?
where on the device is the proximity sensor located?
I have been having difficulty with the screen not switching on during phonecalls and I have to remove battery to end outgoing calls. Pressing the power button doesn't help either. I don't have a screenguard to remove.
The problem started not long after, but not immediately after my daughter dropped the phone down the toilet. It took a few days for the phone to gently dry out and it worked again except for some residual water between the screen and the glass.
Richard Fantom said:
where on the device is the proximity sensor located?
Click to expand...
Click to collapse
The sensor is about 1 cm to the top and right of the htc logo. It's barely visible and it is dark violet. (Or something like that, I am not very good at naming colours.)
Anyway, I sometimes also experience problems with sensitivity with HTC Mozart, mostly during calls, especially when the proximity sensor has been activated. Sometimes the home button freezes after a call... It's a bit annoying.
Hello,
A few days ago I unfortunately dropped my HTC Legend at a music festival and the screen cracked quite badly. Other than that it seems fine, everything works and screen is intact, just glass cover cracked.. I'm writing this from the phone now.
However I've noticed one problem since then.. often when making or receiving a call, the screen will not come back on. It turns off like it normally does when it gets in proximity while in call, then just never turns back on again! It's still "alive", I can still be in the call while it's like this.
When the call's over (can feel vibrate and beep when hang up), the notification light will flash if I have any, like normal.
I press power button, hold it, home button, back button, hold back... Nothing. Have to battery pull and restart! It doesn't happen with 100% of calls, but most.
I haven't noticed anything else wrong.
It seems like once the phone app (not contacts/dialer) is launched after I chose someone to call, the screen turns off and there you go. Call still rings and goes through, but device becomes otherwise unresponsive and I think screen turns off before it should
I'm rooted and s-off with cyanogen 7.2 rc
I've tried wiping and flashing a newer cyanogen 7.2 nightly, same thing.
I don't think it'd be device specific so I'm posting here...
Anyone know what could have happened and how I can fix it??
Cheers!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sounds like your proximity sensor is completely broken. It's causing it to act like there is something blocking it which turns the display off. After all you did say you dropped it. Maybe the sensor just came out of place?
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
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
jfall said:
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
Click to expand...
Click to collapse
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
suyash1629 said:
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
Click to expand...
Click to collapse
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
jfall said:
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
Click to expand...
Click to collapse
Strange issue.. never had it ever, m flashing CM from more than a year.. Try to do a new flash downloading new files..
FYI - I am posting this in hopes that my experience may anyone that goes through this same problem. My phone is S-off and rooted.
I recently had to replace my screen. I bought one from ebay. You check it out the link below if you would like.
The digitizer flex cable was a little too long and seemed not be positioned where it should be, (too far left or something like that). I made it work and got my phone back together. The screen worked just fine until I made a phone call; upon connecting the screen turned off and would not turn back on until the call disconnected. I was running Viper DNA 6.0 originally when screen replacement took place. I could not find what I considered to be a solid lead on correcting the problem at first. I downloaded a different ROM, the teamEOS Droid DNA, same result. I searched more and seen in someones response, (unfortunately cant remember who), that they thought it had something to do with the Kernel. I downloaded JamieTheMorris's intelli plug kernel. When making a call the screen would turn off but, a press of the power button would make the screen turn on but, the screen would not respond to my touch. I tried using the recommended settings and that make my phone go haywire. So I wiped everything and downloaded Santod's NuSense SIX KitKat 6.0 and sometimes the screen cuts off when the call connects but, the power button makes the screen turn on and the phone responds to my touch.
I do not at all feel or claim that I have solved the problem of the replacement screen turning off when a call is connected but; due to the use Santod's ROM my phone functions and for now, that is enough for me.
If anyone has any more info on this problem, or is able to figure the problem please post below.
Replacement screen that I used - http://www.ebay.com/itm/White-HTC-Droid-DNA-Front-Panel-LCD-Touch-Glass-Digitizer-Screen-Assembly-OEM-/370828275337?pt=US_Cell_Phone_Replacement_Parts_Tools&hash=item5657166e89
Since it has RED menu buttons, I think this the screen for butterfly, hence the possible difference in positioning. I am not sure, just my 2c.
Does it have Verizon or HTC logo?
mobsterc said:
Since it has RED menu buttons, I think this the screen for butterfly, hence the possible difference in positioning. I am not sure, just my 2c.
Does it have Verizon or HTC logo?
Click to expand...
Click to collapse
It has a HTC logo at the top. I know it does not mean too much but; the listing says specifically Droid DNA Verizon, although I was questioning whether that was why the cable was not spot on.