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?
Related
Overall i am pleased with the update, but i believe i uncovered an issue that others are expriencing as well.
When i have a second line calling me the screen does not wake up allowing me to switch to the second call. In the past, when a second call comes in the proximity sensor would wake the screen and allow me to take or reject the call. Now i cant even see who is calling. Since i use the phone for business, this is a big, big issue. It still works but the screen only wakes up after like the third ring, whereas before it would wake up immediately Anyone else experience this? I tried this on my buddies Vibrant and its the same thing.
So the question to you guys is how do i get the old dialer app back which i believe controls call waiting. Does anyone else know a way around this annoying issue?
Is there something stopping you from pressing the power button to turn the screen on when you hear the call waiting beep?
The prox sensor is not perfect.
-bZj
_____
-sent from my Samsung Vibrant via XDApp
down8 said:
The prox sensor is not perfect.
Click to expand...
Click to collapse
Obviously, if it was perfect this thread wouldn't exist.
nermie said:
Obviously, if it was perfect this thread wouldn't exist.
Click to expand...
Click to collapse
Thank u. I tried the power button, but unfortunately it does not wake the screen.
Thread moved to Q&A.
bump - me too!
pressing the power button results in a lagged response. that is: call waiting call comes in, screen is black. press the button screen stays black. 5-6 seconds pass and then the screen comes on finally and shuts right back off. whereas NOT pressing the power button, the screen stays black for 5-6 seconds and then comes on and stays on.
I am experiencing this problem too. Just started since coming from stock to JI6.
bump... me too, but this happened on a friend of mine's vibrant who was using stock JI6 from the ota, no root nothing and every incoming call if she is on a call has the same behavior.
This issue has gotten so annoying for me, I have unfortunately decided to sell the phone. I loved it, but is failed in the function I use it most as, a phone. Got a g2. Not as glamorous as the vibrant, but it works as a phone.
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.
So just recently, I noticed that whenever a call ends, the screen remains black and the proximity sensor is still on (red). I've tried pressing the unlock/lock button, but nothing happens. I know the call has ended because I hear the 'ring' that it makes. I've tried it with and without "The power key ends calls", no difference. I have not flashed anything different recently. The only solution I found was to hold down the power button until it restarts, but when someone calls, I have to repeat the process all over again. It was never like this until today. Does anyone know of a solution?
I'm currently on UnNamed 1.3.2 with Entropy's 1/2/12 DD
I'm currently having the same problem with the stock (rooted) ROM... Occasionally after a call, the next time I try to activate the screen, it just stays blank. Sometimes after a call, it's similar to what you described with the end button call staying red and the screen frozen. I have to hold down the on button for 5-10 seconds to reboot the phone. This phenomenon just started about a week ago. The phone has been working flawlessly until then.
I thought that maybe it's some app update gone astray.
knimrod said:
I'm currently having the same problem with the stock (rooted) ROM... Occasionally after a call, the next time I try to activate the screen, it just stays blank. Sometimes after a call, it's similar to what you described with the end button call staying red and the screen frozen. I have to hold down the on button for 5-10 seconds to reboot the phone. This phenomenon just started about a week ago. The phone has been working flawlessly until then.
I thought that maybe it's some app update gone astray.
Click to expand...
Click to collapse
I forgot to mention that I found the culprit, it was my screen protector. I had ordered one of SGP's screen protectors since a lot of people were saying it was good, but when it finally arrived, I noticed that it was very sticky and had covered over the proximity sensor. Over the coming days, the screen protector attracted dust due to it's stickiness when I put it in my pocket. You can probably guess what happened, dust was covered over the area of the proximity sensor, causing it to malfunction like that, but after I took it off, all was well, and now I'm rocking my phone half naked - case but no screen protector. I think I'll leave it like that from now on, gorilla glass feels and looks awesome
When I answer the phone the screen immediately shuts off, I would like to keep it from doing it right away. For instance, if I want to turn on speaker phone I have to unlock and then press speaker phone while the person is wondering who has answered lol.
Poiuyt00 said:
When I answer the phone the screen immediately shuts off, I would like to keep it from doing it right away. For instance, if I want to turn on speaker phone I have to unlock and then press speaker phone while the person is wondering who has answered lol.
Click to expand...
Click to collapse
thats odd. I know the dimming of the display has to do with the proximity sensor, do you have a screen protector on that my be slightly covering the sensor itself? I had eclipse v2.1 and 2.2 and never encounter this problem. And i just looked through the phone settings on my x2 and cant find any settings related (im currently on cm9 though) may be possible you need to reflash eclipse 2.1 =(
Mine does the same thing and I'm on 2.1. Sometimes it drives me nuts. There's nothing I've found that will help. I'm pretty sure it has something to do with the position of the phone being level or not. That's more technical than I can explain. I've done it so many times now that its really automatic to when it comes to pushing the lock/unlock.
It just hit me: I have noticed that if you unlock the phone to select the speakerphone and or dialpad, I'm pretty sure it stays on. It's just the intial unlocking that's tricky, yet forgetful.
Thanks at least I am not alone in this. It happens other times also but always involves the dialer in some way.
I've been lurking here for a while and just registered so I could ask you all for help.
I have a vzw Galaxy S4 (about a year old) running Android 4.2.2 build MI1. It has been dropped in its has UAG case a couple of times but it has never been wet. So there are a few problems, some related some not. 1) I'm having issues with my screen randomly (so it seems) flashing green lines then going black when I wake it from sleep. The soft buttons will stay illuminated, the screen will let me swipe to unlock (I can here confirmation) but the screen stays black. I'll then hit the lock screen button again and it will go black again. The same thing happens if I go to wake the phone via the home button as well. I have a link to a video of it acting up (Two separate occasions, one where the screen just get's a funky green tint and the other where it goes black) but cannot post it since I'm a new member. Let me know if you want me to pm it to you. Does this seem more like a hardware issue or a software/firmware issue?
2) Whenever my headphones are plugged in all I get is garbled sound coming out. No matter what app I'm using or if I'm making a call. I have also noticed that since this started happening, my ear speaker simply will not work (even with the headphones unplugged). Sometimes, when I plugin headphones then unplug them, I will get no audio out of the rear speaker either. This rear speaker issue continues until I reboot the phone.
All of this is driving me nuts and I don't have the cash to replace the phone with anything comparable so I'd like to fix these issues myself if possible. Please let me know if you have ideas/resources that may help me fix this issues. Thanks.