All of a sudden my proximity sensor started working weirdly: at random, during a phone call, it either works perfectly, or it turns off the screen when close to ear but then it does not turn it on when far from ear, or even worst it keeps the screen on even if close to ear.
Any idea?
thanks
thegios said:
All of a sudden my proximity sensor started working weirdly: at random, during a phone call, it either works perfectly, or it turns off the screen when close to ear but then it does not turn it on when far from ear, or even worst it keeps the screen on even if close to ear.
Any idea?
thanks
Click to expand...
Click to collapse
Which OS ?
FerretAD said:
Which OS ?
Click to expand...
Click to collapse
of course I forgot to mention... sorry...
WM6.5 STOCK ROMA ITA 1.66 with CHT 1.8.5
HEEEEEEEEEEELLLLLLLLLLLLPPPPPPPPPPPPPP :-((((((((((
This is driving me crazy...
I did a hard reset a few days ago cos of insane battery drain and now this problem is resolved but this new one came out...
It really behaves at random... u make a call and it works, u make another call and it doesn't, u make a third call and it works partially...
If you have done a hard reset and it still does it then its terminal hardware failure.
Try the hard reset method 1st and see if that fixes it.
Good luck..
xlr8me said:
If you have done a hard reset and it still does it then its terminal hardware failure.
Try the hard reset method 1st and see if that fixes it.
Good luck..
Click to expand...
Click to collapse
actually...
... with original rom 1.44 this was working
... after upgrade to original rom 1.66 this was still working
... after hard reset still on original rom 1.66 this has stopped working
so no, I don't think it's an hardware problem.
I tried the pocket shield demo adn with its dialer the proximity sensor is working, so it must be a setting.... pls help!!!!!!!!!!!!!!!!!!!!!!
Hello. I have got two EU HD2s and problems with one of them. If I start a phone call with one of them on Sense builds the phone seems to 'freeze'. I can end the call by using the end call button but the screen stays black and the buttons stay illuminated.
There is no way to wake up the phone again and i need to pull the battery. Has anyone else had such problems and got a solution for me?
Edit: I just had an idea. Maybe the proximity sensor is the problem. How can i find out when it is toggled?
Edit2: installed a proximity app and its perma reporting 0,0cm. I will open the phone and see if something is wrong.
Ultimaex said:
Hello. I have got two EU HD2s and problems with one of them. If I start a phone call with one of them on Sense builds the phone seems to 'freeze'. I can end the call by using the end call button but the screen stays black and the buttons stay illuminated.
There is no way to wake up the phone again and i need to pull the battery. Has anyone else had such problems and got a solution for me?
Edit: I just had an idea. Maybe the proximity sensor is the problem. How can i find out when it is toggled?
Edit2: installed a proximity app and its perma reporting 0,0cm. I will open the phone and see if something is wrong.
Click to expand...
Click to collapse
Might be something wrong with the actual installation or the ROM itself. Try another ROM or re install.
Hey everyone. I'm having a problem with my phone where when in a call, the screen will stay black, and I can't turn the screen back on to end the call, use the number pad, or anything. Once the screen goes black, that's it. I have to do a battery pull to get the phone to function properly again. This has been going on since I got the device a few weeks ago. I don't think it has anything to do with the ROMs I'm flashing, I have had this problem with stock, cm7, nightly's, RCMix 3D, and absolution. This is a real pain in the ass, and I hope you guys can shed some light on this issue. Thanks in advance.
Not to state the obvious, but if you have this kind of problem with multiple ROM's the problem is probably hardware.
Though I can't for the life of me imagine what hardware that would be. Whatever circuit physically powers on the screen obviously works enough to get it to start on boot.
You could try disabling the automatic screen off feature during calls. Just bypass the problem by keeping the phone on. It's not a great solution because a 60 minute phone call will really sap your battery. But it might be a good temp solution until a real fix is found.
Did you try a full factory reset, rather than just a flash to a stock ROM? There might be some glitch in the software that a ROM flash doesn't cover.
Skipjacks said:
Not to state the obvious, but if you have this kind of problem with multiple ROM's the problem is probably hardware.
Though I can't for the life of me imagine what hardware that would be. Whatever circuit physically powers on the screen obviously works enough to get it to start on boot.
You could try disabling the automatic screen off feature during calls. Just bypass the problem by keeping the phone on. It's not a great solution because a 60 minute phone call will really sap your battery. But it might be a good temp solution until a real fix is found.
Did you try a full factory reset, rather than just a flash to a stock ROM? There might be some glitch in the software that a ROM flash doesn't cover.
Click to expand...
Click to collapse
I had this problem with full stock and s-on. The problem continued even after downgrading the radio and rooting with s-off and multiple ROM flashes. I wouldn't know what hardware it would be either. I don't really talk much, so your suggestion will work until I figure something else out. Thanks man.
Edit: I just tried keeping the screen on, no dice. As soon as I dial out, the screen turns off completely and none of the buttons work. I also tried the trackball hangup option, but no good.
Sent from my HTC Glacier using xda premium
i think the problem is the proximity sensor. it could be misplaced and covered by the front glass.
download sensor test on market to find out.
mniroy said:
i think the problem is the proximity sensor. it could be misplaced and covered by the front glass.
download sensor test on market to find out.
Click to expand...
Click to collapse
Downloaded and ran the app. All the sensors appear to be working, except the proximity sensor. It just reads 0.
Edit: I ran the test again, and when I first start it, the "0:" line for the proximity reads 9. As soon as I move my hand close to the screen, it will drop to 0 and stay there.
Sent from my HTC Glacier using xda premium
Well that certainly seems to be the issue.
I can't remember how to do it, but I'm almost certain there's a setting to disable to proximity sensor during calls. Sorry I've never actually used that setting so I have no recollection of where it is.
For all I know it might be the "screen on during calls" setting I refereed to originally.
I knew it was hardware though!
Also, I saw this app. I don't think it was designed to do what you want, but I think it ultimate does it. It was made so that you could answer the phone with a swipe. But in order to make sure the screen is on to be swiped, it disables the proximity sensor.
https://market.android.com/details?...wsMSwyLDEsImNvbS5pdHNtZTR1Y3ouc2NyZWVub2ZmIl0.
Skipjacks said:
I can't remember how to do it, but I'm almost certain there's a setting to disable to proximity sensor during calls. Sorry I've never actually used that setting so I have no recollection of where it is.
Click to expand...
Click to collapse
if youre a fan of miui, there is an option to disable in settings. def sounds like the proximity sensor is the culprit. have a screen protector or case thats interfering with it?
Dan_Brutal said:
Downloaded and ran the app. All the sensors appear to be working, except the proximity sensor. It just reads 0.
Edit: I ran the test again, and when I first start it, the "0:" line for the proximity reads 9. As soon as I move my hand close to the screen, it will drop to 0 and stay there.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
so your proximity messed up. the solution is easy, just remap your end call to hard button.
like this for example:
Code:
key 116 ENDCALL WAKE_DROPPED
mniroy said:
so your proximity messed up. the solution is easy, just remap your end call to hard button.
like this for example:
Code:
key 116 ENDCALL WAKE_DROPPED
Click to expand...
Click to collapse
If the screen is not coming back on even after the other person has hung up, this will not work. Its worth giving it a shot tho
Sent from my HTC Glacier using Tapatalk
mrmako777 said:
If the screen is not coming back on even after the other person has hung up, this will not work. Its worth giving it a shot tho
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
of course, but if that so, the problem must not be the proximity sensor isnt it.
mniroy said:
of course, but if that so, the problem must not be the proximity sensor isnt it.
Click to expand...
Click to collapse
um, yeah, it still could be the sensor
I had this issue without a screen protector or case. Do you think if I flash back to stock with s-on, HTC would warranty it?
Sent from my HTC myTouch 4G using xda premium
Dan_Brutal said:
I had this issue without a screen protector or case. Do you think if I flash back to stock with s-on, HTC would warranty it?
Sent from my HTC myTouch 4G using xda premium
Click to expand...
Click to collapse
i would think so if youre still under the warranty period, which is i think a year.
This ones a bit strange but ill try to explain as best as i can...
Got my phone last week - rooted, unlocked the bootloader and reflashed within about 10 mins or so - you can't not can you...its what they were made for....anyway, im not sure what's caused it to happen but in the last few days when i dial a number as soon as the number is dialled the screen goes blank (but working in the background as i can hear it ringing....the other persons answers, and then when i want to hang up i cant get the screen go come alive again) unless the other person hangs up and then it does. Ive tried another image but its the same and ive just upgraded the phone radio firmware to the 4.2.2 version but i makes no difference....anyone else had this or is it just me?
Cheers to anyone that has a clue....
ComfySofa said:
This ones a bit strange but ill try to explain as best as i can...
Got my phone last week - rooted, unlocked the bootloader and reflashed within about 10 mins or so - you can't not can you...its what they were made for....anyway, im not sure what's caused it to happen but in the last few days when i dial a number as soon as the number is dialled the screen goes blank (but working in the background as i can hear it ringing....the other persons answers, and then when i want to hang up i cant get the screen go come alive again) unless the other person hangs up and then it does. Ive tried another image but its the same and ive just upgraded the phone radio firmware to the 4.2.2 version but i makes no difference....anyone else had this or is it just me?
Cheers to anyone that has a clue....
Click to expand...
Click to collapse
Have you check to see if anything is blocking the Proximity censor (top left corner)? The Screen Protectors often do this if they are in the way...
Otherwise the Prox Censor is fudge.. its the only thing that will cause the phone screen to turn off when a call is in progress (this is so your face doesnt press buttons)
UberSlackr said:
Have you check to see if anything is blocking the Proximity censor (top left corner)? The Screen Protectors often do this if they are in the way...
Otherwise the Prox Censor is fudge.. its the only thing that will cause the phone screen to turn off when a call is in progress (this is so your face doesnt press buttons)
Click to expand...
Click to collapse
that was it! it was the LCD cover - peeled that off and its now working. Thanks very much for that!! Case Closed.
Recently my LG G2 Verizon has started having an issue with turning on.
1. will no longer turn on by knock on. (knock off works)
2. when i push the power button on the back about 75% of the time the screen turns on then immediately turns off or turns off as soon as i touch the screen. I have to push it a bunch while touching the screen to get it to stay on and let me unlock it.
3. pulling down the notification bar from the top only pulls down partially then closes a lot of the time.
I have tried:
1. Uninstalling a bunch of apps, no success.
2. did a data reset and wiped everything. no success.
Running:
4.2.2
VS98011A
TWRP 2.6.3.2
When i first went into TWRP i tried to do a factory reset and it just sat there with an error that i could not mount the cache. Then i rebooted, went back in and this time did a data wipe and typed "yes" to verify. It got stuck trying to do that as well, but this time when i rebooted it was reset and i had to reenter all my account settings etc. But it is still having the same issue. I am wondering if there is something in the cache thats causing it and i wonder if it did not wipe the cache when it wiped the data.
At this point i just want the phone to work but not sure why TWRP is having issues. Has anyone else had any of these issues? Can anyone help with these issues?
I wouldnt mind flashing the VS98011B rom but i am not sure TWRP is working correctly and want to make sure it works right before i try to flash a new rom. Should i use CWM? if so how do i get from TWRP to CWM? i need some help.
Any advice is extremely appreciated.
bump for help PLEASE.
I had that issue with one of mine. 1st make.sure ure screen protector is not over the prox sensor 2nd case isnt over it and 3rd clean. With the knock off on feture when the screen is off the prox sensor is on so iff u gots ure phone in ure pocket and double tap it wont come on i was holding my hand over the sensor and it pissed me off so bad. If all else fail shut off knock on and it may work then if not u have a bad prox sensor its what ive read about and found out
If this helps remember the thanx
TheMadScientist420 said:
I had that issue with one of mine. 1st make.sure ure screen protector is not over the prox sensor 2nd case isnt over it and 3rd clean. With the knock off on feture when the screen is off the prox sensor is on so iff u gots ure phone in ure pocket and double tap it wont come on i was holding my hand over the sensor and it pissed me off so bad. If all else fail shut off knock on and it may work then if not u have a bad prox sensor its what ive read about and found out
If this helps remember the thanx
Click to expand...
Click to collapse
Yea i think you are right about it being a bad prox sensor...
You stock? If so, which version? Rooted?
Sent from my VS980 4G