Is there some way to trap or disable the physical camera button?
Mine is far to sensitive and it's really driving me up a wall, I continually turn on the camera at least a dozen times a day.
Thanks
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.
So I was curious if there were any apps for controlling your phone through the proximity sensor and I stumbled across this:
https://play.google.com/store/apps/details?id=novum.inceptum.proximity
The DNA is my first HTC phone, and coming from a Samsung Vibrant I can honestly say I can't stand the power button being mounted on the top. Add to that the slight angle of the phone's top edge and the stiffness of the button, and it's hard as hell for me to use the power button one-handed. Enter Proximity Actions. Now, I just wave my hand a couple times over the proxy sensor and it wakes and unlocks my phone. It can do other stuff too, but this is my main love of it. Even better, there's no need for root (for us poor folks who didn't have a chance to root before the OTA update), and it doesn't appear to drain the battery in any noticeable way. I just thought I'd recommend it since I have a feeling I'm not the only one with beef against that terrible power button. It also makes iPhone users VERY jealous... they act like you're performing voodoo or something I do think it's weird how you can see the faintest red glow from the proxy sensor while it's active... never noticed that on any other phone before.
rchrdcrg said:
So I was curious if there were any apps for controlling your phone through the proximity sensor and I stumbled across this:
https://play.google.com/store/apps/details?id=novum.inceptum.proximity
The DNA is my first HTC phone, and coming from a Samsung Vibrant I can honestly say I can't stand the power button being mounted on the top. Add to that the slight angle of the phone's top edge and the stiffness of the button, and it's hard as hell for me to use the power button one-handed. Enter Proximity Actions. Now, I just wave my hand a couple times over the proxy sensor and it wakes and unlocks my phone. It can do other stuff too, but this is my main love of it. Even better, there's no need for root (for us poor folks who didn't have a chance to root before the OTA update), and it doesn't appear to drain the battery in any noticeable way. I just thought I'd recommend it since I have a feeling I'm not the only one with beef against that terrible power button. It also makes iPhone users VERY jealous... they act like you're performing voodoo or something I do think it's weird how you can see the faintest red glow from the proxy sensor while it's active... never noticed that on any other phone before.
Click to expand...
Click to collapse
This is cool and all but if you want to you can flash Beastmode kernel with the S2W action so you can just slide your finger across the softkeys from the back button to the multitask button and it will wake your device. Just as impressive as using the proximity sensor but without using extra juice on your phone. :good:
Edit: Didn't read that part you said about not having a pre-OTA device! My bad!!
Sense 5 DNA
Very interesting!
I forgot to warn about the occasional ads that pop up... Kinda bugging me but I still love the app enough to deal with it. It's pretty rare for them to pop up outside the app itself.
And yeah, I really wish I could have all the neat features of a custom ROM... Oh well, maybe some day!
Sent from my HTC6435LVW using xda app-developers app
So I figured I would post this up just in case people are going crazy about turning on their display, and then having it turn right back off on them lol. There are sensors at the top of the device by the ear speaker. When turning on the device make sure your fingers remain clear of those sensors for 1 second, if those sensors do not pick up light source by being blocked off (try it, press the power button while covering the sensors), the display will turn back off. Same thing goes for Knock on, the display wont even turn on at all. Keep your fingers clear of those sensors!
I dont think this is a design flaw I think LG inadvertently did this to keep from the device from turning on in your pocket by accidentally hitting power on knocking on while in your pocket. it might also attribute to poor knock on feature in low light areas or night time.
Walter21026 said:
So I figured I would post this up just in case people are going crazy about turning on their display, and then having it turn right back off on them lol. There are sensors at the top of the device by the ear speaker. When turning on the device make sure your fingers remain clear of those sensors for 1 second, if those sensors do not pick up light source by being blocked off (try it, press the power button while covering the sensors), the display will turn back off. Same thing goes for Knock on, the display wont even turn on at all. Keep your fingers clear of those sensors!
I dont think this is a design flaw I think LG inadvertently did this to keep from the device from turning on in your pocket by accidentally hitting power on knocking on while in your pocket. it might also attribute to poor knock on feature in low light areas or night time.
Click to expand...
Click to collapse
There's also a bug which emulates the same symptoms,while the sensor is not blocked. Changing the screen-off effect to different effect, is a work around for those caught with the issue.
timsterzzz said:
There's also a bug which emulates the same symptoms,while the sensor is not blocked. Changing the screen-off effect to different effect, is a work around for those caught with the issue.
Click to expand...
Click to collapse
Its interesting that LG went with this sensor design. This sensor thing is kinda weird seeing as people will no doubt block this sensor and trigger this effect without even realizing what they are doing, making people think their device is broken. LOL im sure this is talked about in the instruction guide but who the heck reads those things now?
I am liquidsmooth 2.37, waiting for a stable kit kat and one bug has been killing me. the proximity sensor has been messed up for a while and will not turn the screen on during a call. neither will the power or home button. anyone know of an app that would either disable the proximity sensor OR keep the screen on during a call? I guess the AOSP call settings dont have a native feature
dougmod said:
I am liquidsmooth 2.37, waiting for a stable kit kat and one bug has been killing me. the proximity sensor has been messed up for a while and will not turn the screen on during a call. neither will the power or home button. anyone know of an app that would either disable the proximity sensor OR keep the screen on during a call? I guess the AOSP call settings dont have a native feature
Click to expand...
Click to collapse
Have you tried blowing compressed air into the earpiece trick? Mine was acting the same way on cm11. For me it seems to be an issue of developing dirt/dust in the proximity sensor which is very close to the earpiece grill. My sensor seems to stop working every few weeks like clockwork and blowing the compressed air into the earpiece fixes the issue. Just a thought.
yeah i did blow it in there a few times with no change. i saw people do it a few months back and tried then too. is it dirt of what because my phone doesnt react the to power button or home button pressing during a call. i need to press it 1000 times and hope i catch it, if it comes on. if there was an app or something that would force the screen to say on during a call that would be amazing. i know if i have a bluetooth connection or a wired headset in, things are great. just that damn prox sensor
I had to pry my S4 open, clean off the glass in front of the proximity sensor, then add double-sided adhesive around the speaker opening to stop this problem from reoccurring.
Are you using a case that covers the area around the sensor? Some "rugged" hard cases don't have openings large enough for the sensor to act correctly.
HyperDriven MK2
its a known aosp issue software wise. i dont know how to fix it but dust doesnt cause it
Sent from my CIA sanctioned device
Unpredictable, but at times, my phone will be on and working, but not respond to a press on the hardware power button. It also won't respond to a knock to wake attempt. The second screen is usually off as well, though at times, it is on but the main screen is still unresponsive. I press and press and eventually the screen will come on more often than not. Many times though, I'm forced to do a battery pull. Has anyone seen this?
I wonder if it is your proximity sensor? I say this because you mentioned that the second screen is also dark which happens when the sensor thinks it is in a pocket or case or laying screen down on a table. There are some threads here regarding cleaning it. (As a kind-of aside, there is a known problem with the power button not responding while in an active call, but I think that is different than your issue. I have frequent problems with mine waking up while on a call but my sensor is OK).
emtownsend said:
I wonder if it is your proximity sensor? I say this because you mentioned that the second screen is also dark which happens when the sensor thinks it is in a pocket or case or laying screen down on a table. There are some threads here regarding cleaning it. (As a kind-of aside, there is a known problem with the power button not responding while in an active call, but I think that is different than your issue. I have frequent problems with mine waking up while on a call but my sensor is OK).
Click to expand...
Click to collapse
I believe I've been having the in-call issue as well. In any event, thank you for the sensor insight, I'll search the forums and see if that's the culprit.
thanks.