After the ota to jb on my wifes stock non rooted xt912 the proximity sensor stays on. I assume because it stays illuminated. While locked its a bit dim yet fully illuminated while unlocked causing a noticeable battery drain. It still works just wanted to know if anyone else had this issue or how to resolve it. Of course I have done the basic trouble shooting for a stock device FDR .. safe mode... let it die and recharge... thank you kindly for your time...
Sent from my DROID4 using xda app-developers app
Try "phone tester" free on play store
It basically tests the different phone sensors ,
At least you'll no if it's a hardware fault
Sent from my XT910 using xda app-developers app
well I swapped out the main board of the device to see if it was an issue with the screen itself yet the main board with the new screen still does it and the old screen with the new board does not... so it must be a software issue ... I guess I'll just have to wait for the fast boot to leak... unless it has already in that case could one point me to the link to download... thank you kindly for your time... sensor testers say its working and show change in proximity...
Sent from my DROID4 using xda app-developers app
Related
I don't know what happened but this morning all of a sudden my proximity sensor is now working wasn't working last night don't know if this was posted somewhere else but I'll tell you this I'm excited
Sent from my EVO using xda app-developers app
Halomage said:
I don't know what happened but this morning all of a sudden my proximity sensor is now working wasn't working last night don't know if this was posted somewhere else but I'll tell you this I'm excited
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
what rom u rockin? i would do a headspin if my sensor worked rite again!!
Halomage said:
I don't know what happened but this morning all of a sudden my proximity sensor is now working wasn't working last night don't know if this was posted somewhere else but I'll tell you this I'm excited
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Are you outside? I notice that my p. Sensor works perfectly when I'm outside (bright light), but when I'm inside or low light it doesn't work
Sent from my EVO using xda app-developers app
Full stock, I haven't gotten the balls up to root yet, but not sure if I'm keeping this phone, screen flickers a lot but it work inside and outside its gotten annoying now because I got so used to hitting the power button after a call to call up the screen now I turn it off lol
Sent from my EVO using xda app-developers app
I just noticed mine still stays on after a call. I see that red light at night on all the time but it's random.
Sent from my EVO using xda app-developers app
evo401 said:
what rom u rockin? i would do a headspin if my sensor worked rite again!!
Click to expand...
Click to collapse
The CM10 proximity fix greatly helped the issue for me. Note: I am NOT running CM10. I am running stock rooted Jelly Bean.
[MOD] [CM10] Proximity Sensor Fix
I tested using Proximity Sensor Finder before and after. Before nothing happened, after it went from 9 to 0 when covered.
jdawg0024 said:
Are you outside? I notice that my p. Sensor works perfectly when I'm outside (bright light), but when I'm inside or low light it doesn't work
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
+1, i've also noticed that it works better in the morning, opposed to the evening
ThrowingKs said:
The CM10 proximity fix greatly helped the issue for me. Note: I am NOT running CM10. I am running stock rooted Jelly Bean.
[MOD] [CM10] Proximity Sensor Fix
I tested using Proximity Sensor Finder before and after. Before nothing happened, after it went from 9 to 0 when covered.
Click to expand...
Click to collapse
Does anyone know what will happen if I try flashing this through the stock recovery (Completely stock and unrooted) I've notice that if I get in to the recovery from the HBOOT and press the vol up I get the stock E3 recovery that will allow me to flash "update zips"
That fix relies on int.d support, in your case not being rooted it would not work.
#Root-Hack_Mod*Always=SG3
I'm on CM10 and have never had any issues with the sensor. What are you guys talking about? (Not trying to be rude btw)
Sent from my EVO using xda app-developers app
My S2 makes this weird noise sometimes when using Torch. It sort of sounds like a buzzing. And as I'm typing this, it started doing it without Torch on. The sound is coming from where the camera and LED are at. When it does this, I just flick/thump on the spot and it stops making the sound. What could be the cause of this?
Sent from my i777 using xda app-developers app
It's the auto focus mechanism for the camera, not sure why it does it. Toggling torch off usually stops it or a reboot, doesn't seem to cause any issues with the camera, but it can cause a serious amount of battery drain if it stays active.
Sent from my GT-P5110 using XDA Premium HD app
The warning specifically states that the unusual high power of the light frequencies may/may not damage your phone in some way, although maybe that's a problem they had not anticipated :/
Sent from my P2H-I777-HTCTerrorist using xda app-developers app
HTCTerrorist said:
The warning specifically states that the unusual high power of the light frequencies may/may not damage your phone in some way, although maybe that's a problem they had not anticipated :/
Sent from my P2H-I777-HTCTerrorist using xda app-developers app
Click to expand...
Click to collapse
True, but I never use it for more than a few seconds.
Sent from my i777 using xda app-developers app
It's been a while since I researched this but from what I can remember, all of the apps like torch that utilize the flash for a flash light activate the camera as well as the flash so the camera will try to focus even though you aren't trying to take a a pic. I have never figured out why my the camera focus mechanism flakes out one time but not the next seems to do it worse on certain rom versions than but I have never flashed backwards to see if the problem returned.
Sent from my GT-P5110 using XDA Premium HD app
I have the smane problem.
It is a video from someone on youtube that have the problem too:
http://www.youtube.com/watch?v=toDlY8Txb4M
any one know how can fix it?
Thanks
It appears to be a mechanical issue with the camera's focus motor. It may need to be replaced if it really bothers you. I've heard some parts for the s2 are easy to repair yourself, but I don't know if this is.
Sent from my SGH-I777 using xda app-developers app
Hi, everyone
First time posting here so hoping I've posted in the right place
Just wondering if anyone is having the same issue as me on the non functioning back capacitive button
Sometimes it would just stop working completely and will respond after 30-60 seconds
It gets really annoying.
A temporary fix is to power the screen off and then turn it back on to get immediate response
This leads me to believe it is a software fault and if it is HTC need to know about it.
Also there's a screen protector fitted on the screen but that shouldn't be a problem
Sent from my HTC One using xda app-developers app
This would get far more replies in the HTC One Q&A and Troubleshooting forum. First check if anyone has a similar problem and a solution for it, then either ask a mod to move it there or create a new thread (all assuming that your question doesn't get answered before then of course).
Thanks
Sent from my HTC One using xda app-developers app
Sorry, but wrong section mate.
Thread reported.
"To err is human, to forgive is divine"
Sent from my SGS II
Happens to me as well...really annoying. Back button just stops working/unresponsive and then starts working again after some time. Generally the sensitivity is too low, looks like a software issue but we need to wait long before carriers approve any updates and push it to us. So hopefully some custom rom or mod will fix this.
Just re calibrate you screen and lightly tap the buttons when requested. It should fix the sensitivity. And The others are right wrong forum.
GNayim said:
Hi, everyone
First time posting here so hoping I've posted in the right place
Just wondering if anyone is having the same issue as me on the non functioning back capacitive button
Sometimes it would just stop working completely and will respond after 30-60 seconds
It gets really annoying.
A temporary fix is to power the screen off and then turn it back on to get immediate response
This leads me to believe it is a software fault and if it is HTC need to know about it.
Also there's a screen protector fitted on the screen but that shouldn't be a problem
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
C Murder said:
Just re calibrate you screen and lightly tap the buttons when requested. It should fix the sensitivity. And The others are right wrong forum.
Click to expand...
Click to collapse
Tried it, I still have the issue.
Sent from my HTC One using xda app-developers app
---------- Post added at 09:07 AM ---------- Previous post was at 09:04 AM ----------
One way I found to replicate the issue, in case you need to show someone like a tmobile rep, is to go into the app drawer and press the back button repeatedly until it stops vibrating. Then open up an app, and you shouldn't be able to back out of it for a bit.
Sent from my HTC One using xda app-developers app
Known problem with all HTC One's. Don't bother swapping it out.
Allegedly it gets fixed in the 1.29.XXX.12 OTA. Unbranded phones in Europe and Asia are the only ones to have received this OTA so far but they all report the issue is solved after applying it.
Please see this thread: http://forum.xda-developers.com/showthread.php?t=2245637
http://www.pocketables.com/2013/04/...-issues-with-capacitive-hardware-buttons.html
Can confirm calibrating the screen through the HTC keyboard settings fixed mine. Trick is to barely touch the screen when calibrating the sentence. And I mean like barely brushing the screen. The Buttons work great now.
Sent from my HTC One using xda app-developers app
tbae2 said:
Can confirm calibrating the screen through the HTC keyboard settings fixed mine. Trick is to barely touch the screen when calibrating the sentence. And I mean like barely brushing the screen. The Buttons work great now.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I just recalibrated mine, and the problem is still there. I also tried a demo one from best buy and the back button worked perfectly. The vibration was even more evident. I don't know what this means for me, but I'm still going to swap it out.
Sent from my HTC One using xda app-developers app
m03sizlak said:
Known problem with all HTC One's. Don't bother swapping it out.
Allegedly it gets fixed in the 1.29.XXX.12 OTA. Unbranded phones in Europe and Asia are the only ones to have received this OTA so far but they all report the issue is solved after applying it.
Please see this thread: http://forum.xda-developers.com/showthread.php?t=2245637
Click to expand...
Click to collapse
I don't think you can say that it's a problem with all Ones. I've tried everything suggested to try to reproduce the problem on my phone, and my buttons work fine.
I wouldn't disagree that HTC had some supply chain problems with the One. But, that some people have posted problems in forums doesn't mean it's as widespread as you may think.
ptweasel said:
I don't think you can say that it's a problem with all Ones. I've tried everything suggested to try to reproduce the problem on my phone, and my buttons work fine.
I wouldn't disagree that HTC had some supply chain problems with the One. But, that some people have posted problems in forums doesn't mean it's as widespread as you may think.
Click to expand...
Click to collapse
I agree 100 percent. Like I said, the demo version had no problems.
Sent from my HTC One using xda app-developers app
I was starting to have issues again oddly after the calibration attempt. Just flashed trickdroid based on 1.29 update and the cap buttons are way more sensitive and I spammed them to death no issues. Will report back after using this for a day but it does appear the 1.29 update fixes the issue
Sent from my HTC One using xda app-developers app
tbae2 said:
I was starting to have issues again oddly after the calibration attempt. Just flashed trickdroid based on 1.29 update and the cap buttons are way more sensitive and I spammed them to death no issues. Will report back after using this for a day but it does appear the 1.29 update fixes the issue
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip, I just flashed the same rom. My phone is working beautifully now.
Sent from my HTC One using xda app-developers app
erniev said:
Thanks for the tip, I just flashed the same rom. My phone is working beautifully now.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Glad it worked ! Used it all day today and the capacitive buttons worked beautifully. So there's the answer as far as I can tell. Either flash a Rom based on the 1.29 update or wait for the OTA from T-Mobile
Sent from my HTC One using xda app-developers app
Hi there don't know off any one fixed this issue yet but last night I installed a new digitizer in the 4g as this issue presented itself it is a pain tbh I have been usin the phone for a while it has a custom rom on olypus I think not sire atm. But this is the issue.
About a 1cm bar the leamth of the screen ant sujestions please folks
Sent from my HTC Desire HD A9191 using xda app-developers app
I just got tha same problem today and i saw your topic just before posting a new one.
I got the problem using the MROM-ICS (of course i dont blame the developer or the rom for that). Basically i had a lot of problems with the rom and my old (gingerbread) data and apps so i has flashing the rom/gapps and restore all the time witch turned me mad... then i just pressed the screen a little harder (really little) when pluging in the charger. I saw he screen doing this weird color when you press it (like the pc monitor does) so i think that this is my fault.
So if i understood right you had the problem before and after digitizer change ? Sorry but i am not sure of what i read here
PS: I tried pds fix but with no luck.
The digitizer is not good /doa. You'll probably need another new one. Happened to me times.
Sent from my MB860 using Tapatalk 2
That is a pain on the 4th on already
Sent from my HTC Desire HD A9191 using xda app-developers app
Mine had the same problem same place but it's spread to the centre as well now
I think it's with the stupid flex cables and something to do with the faulty design of fingerprint scanner position
No one has permanent solution for this but for temporary purpose you can insert a piece of credit card inbetween the battery top location and check
Sent from my MB860 using xda premium
Has anyone experienced issues with the screen sensor not responding well while on a call?
Sometimes if you lock the screen while on a call and you try to unlock it the screen with shut off as soon as you touch it and will remain on that behavior until the call is ended, therefore not letting you unlock the phone or perform any other activities on the phone.
Anyone?
Sent from my HTC One using Tapatalk 2
Yes! It happens to me rather frequently. Thanks for starting this post. Hopefully someone can shed some light on this.
Sent from my HTC One using xda app-developers app
girlygirl00 said:
Yes! It happens to me rather frequently. Thanks for starting this post. Hopefully someone can shed some light on this.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It's funny because this is the 2nd HTC phone that I can report with this bug. I had the Evo 4G LTE before this one and it suffered the same issue even after all official updates.
The only solution with that phone was to flash a custom ROM which was good, but up to now I'm still on the fence about rooting this one; stock on this phone is stable and bloatware is minimal, I haven't justified taking the plunge yet.
Sent from my HTC One using Tapatalk 2
I'm with you there. I did root mine... but only for data restore purposes. It may sound crazy.. but I don't want SwiftKey to start over with learning my typing habits. Other than that, like you, this phone and my Nexus 4 are the only two phones that I have had no desire to install a custom ROM. Fingers crossed that there is a solution other than that.
Sent from my HTC One using xda app-developers app
megabiteg said:
Has anyone experienced issues with the screen sensor not responding well while on a call? Anyone?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, happened with me quite a few times. Once a call is initiated (phone speaker on or off) and the screen goes black (due to proximity sensor), no amount of tinkering will bring it back until you press the power button which kills the call. It is damn annoying and am hoping there is a fix.
The phone is on 1.29 M7 TMobile ROM, rooted with S-OFF
I had that problem too on LG L7. Tried with various roms and nothing. But I fixed somehow with the app called "proximity actions". It lets you command your phone with hand suggestion via proximity sensor. I only installed it to check the hardware, wether the sensor works. I have no idea what happened, but it started to work again. The app somehow toggled the sensor and brought it back to life.
Sent from my LG-P700 using xda app-developers app
Not sure if all ROMs have the option but you can go in to the accessibility options and turn off power button ends call.
Sent from my HTC One using xda app-developers app
I've noticed this issue has significantly increased amongst other things like freezing since I unlocked my bootloader. :what:
Sent from my HTC One using xda premium
sbihue said:
Yes, happened with me quite a few times. Once a call is initiated (phone speaker on or off) and the screen goes black (due to proximity sensor), no amount of tinkering will bring it back until you press the power button which kills the call. It is damn annoying and am hoping there is a fix.
The phone is on 1.29 M7 TMobile ROM, rooted with S-OFF
Click to expand...
Click to collapse
Never once has this happened to me. Bone stock.
Guess that's another reason I don't trust "IMAROM CHEFS!" ROMs that are "cooked up" on some random internet user's computer.
Stock is fine these days, IMO. Outgrew the glitchy nature of kitchen ROMs and such.
ericshmerick said:
Never once has this happened to me. Bone stock.
Guess that's another reason I don't trust "IMAROM CHEFS!" ROMs that are "cooked up" on some random internet user's computer.
Stock is fine these days, IMO. Outgrew the glitchy nature of kitchen ROMs and such.
Click to expand...
Click to collapse
Been using ROMs for years and I've hand,y ups and downs, I can't say I've had a horrible experience with any ROM I've used on any of my past phones. Now I do agree with you about the stability of stock ROMs these days and also the better specs of the phone. For instance I haven't rooted nor unlocked my phone because I personally feel that the delivered product is good and haven't felt the necessity to tinker with it. The issue described is with stock, not custom ROM.
With that said or you haven't had the scenario for it to happen or your just the lucky one....
Sent from my Nexus 7 using Tapatalk 2