Hello there xda!
I have had this problem with my galaxy S for quite some time now but since I still haven't found a solution I turn to you!
Here´s the thing, whenever I make or receive a call on my phone the screen blacks out. It stays black until I yank out the battery.
Sometimes the screen comes back when the call ends but this is more the exception rather than the rule.
If I got my headphones/headset in, the screen does not go black, so I try to always have them plugged in.
My thoughts are that something is wrong with the proximitysensor in the phone and is blacking out the screen, I got an app that show all sensors and the values didn't change when I covered the sensor.
I have rooted my phone several times with different roms so when this problem occured I tried all kinds of different roms to see if it would fix the problem.
No stock roms or other roms have worked so I assume its a hardware fail but for whatever reason I cant help but think that its more likely to be a software issue.
I am currently running darkys 10.2.2 rom.
If you got any questions that could help you come up with an answer, don't hesitate to ask
EDIT, Solution!
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
Hey dude, i dont know how you can fix the proxmity sensor if it is broken,
however, i have heard of other people with the same problem.
And they solved it with an app called ProximityScreenOff wich is downloadable form market.
atleast you wont have to yank out your battery everytime you get an call!
Hope this helps!
pzayx said:
Hey dude, i dont know how you can fix the proxmity sensor if it is broken,
however, i have heard of other people with the same problem.
And they solved it with an app called ProximityScreenOff wich is downloadable form market.
atleast you wont have to yank out your battery everytime you get an call!
Hope this helps!
Click to expand...
Click to collapse
Tried some different settings but couldnt get it to work.. Screen still shut off during calls
Thanks for the try though! Might have to order a new proximity sensor and see if it fixes it
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
snelpiller said:
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
Click to expand...
Click to collapse
LOL, i was just ABOUT to post this EXACT same solution then read your post. I had the same problem and other problems that wererelated to the network, dropped calls, black screen after calls begins etc. and installing an earpiece from an T959's took care EVERYTHING. I'm not sure how this earpiece fixed the network problem. If somebody knows and would like to enlighten me, that's be great!
Related
Hi!
My GNote hangs up/becomes non-responsive when I receive or make a call, everything else is just fine, but it can't be used as a phone now.
I have tried many roms but the problem persists, according to my observation and research the proximity sensor is the culprit here, and it is a hardware problem, which can't be fixed by software, I suppose. But there might be a way to disable the sensor at all, in which way screen won't turn off while making a call, but who cares if I can make a call. I found a couple of threads describing the same problem but with no solution.
Is there a way to do the trick, if not, can you please guide me write my own kernel to disable the sensor, I am not an Android developer but I do have a Master's Degree in Computer Science so I am pretty much confident that I can do it myself if given some pointers.
Any help is greatly appreciated, thanks.
Have a good day, Regards.
have you tried disabling the screen off during calls?
nokiamodeln91 said:
have you tried disabling the screen off during calls?
Click to expand...
Click to collapse
Thank you sooo much, this did the trick..... Now I am wondering why I didn't think of that earlier.....
BTW is there any other way I could get rid of this problem completely, now my screen won't turn off during phone calls, causing unwanted operations.....
Thank you so much.....
if you have tried many roms then may be a issue with the sensor.. try consulting a Samsung service personnel
galaxy note N7000 freeze while during call 1000% solved
you just clean the sensor your prob will be solve 1000%
Hi i'm using a rooted htc one and people often complain they cant hear me during calls. I was wondering if there was anyway I could enhance the microphone so that my voice is louder. I'm using android 4.1.2 and sense 5. The case i'm using has a hole on the back in the top right corner and on the bottom to the left of the usb adapter jack where I think the microphone(s) are. I looked at other threads but I was having this problem before I rooted my htc one and was hoping that now it has been rooted there was some sort of hiden control I can use to turn up the michrophone setting. Thanks
bump
If it wasn't working right before you rooted it, then it means it is a hardware problem. I don't think this is necessarily a sensitivity issue. I think it has to do with the noise canceling.
Talk to HTC or whatever carrier you have.
Also, make sure to hide all signs of root!
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Xayden said:
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Click to expand...
Click to collapse
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Muhammad.Muayad said:
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Click to expand...
Click to collapse
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
layzz said:
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2183023
This ROM is based on 4.2.2 on 2.24 all my problems are pretty much fixed
I have this very same problem on my brand new stock device. I created a thread for the same problem. I found that the earpiece quality was brilliant but again people could not hear me or said I was very quite. I experimented with case on and case of and calls to different phones and 9/10 times the problem was there. I then decided to install android revolution hd to see if there was a problem with the stock rim for some reason. Sadly this didn't work. I then turned my attention to the lower microphone. Now I am not suggestion you do this by any means however in my case I felt I had nothing to lose as I was going to have to send the phone to HTC to get fixed if I could not sort it myself.
I got the small sim removal tool and stuck it into the mic hole in a bid to try and open the hole up abit as it seemed very small and I wondered also if it was blocked. I did this a little at a time and then tried calling people to see if there was any change. Instantly there was an improvement. However, now it seemed like 5\10 calls were low. So, I tried the same again.
I now have not had the problem in the last 15 or so calls I have made however what I have noticed is that now for what ever reason when I'm in calls the person on the other end sounds a little distorted through the earpiece. Don't know why this should be and maybe a completely unrelated problem or something linked to installing the other rom. Either way at least people can hear me now.
Sent from my HTC One using xda premium
Thanks everyone. The problem seems to be fixed after installing that custom rom
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
EDITED:
So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
alex.foto said:
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
Click to expand...
Click to collapse
Well, seems to be the same here. I have this posted under the Verizon HTC One > One Q&A, Help & Troubleshooting as well as here and at the Android forums. It seems that either no one else is having this issue, no on cares or no one can run this test with free programs. I dunno. The problems I have is that I use by bluetooth headset most of the time. I am a blue collar worker and try not to pull my phone out of my pocket when my hands get filthy. But, when I take or make a call using the headset, the display kicks on and then stays on because I can't use the proximity sensor to turn the screen back off. Guess I'll have to try other routes. This sucks. LOL
I haven't heard of the other issue you are referring to. I can tell you that I have not had that issue with my One. Doesn't mean that it's not a problem. Have you checked the Sounds settings for pocket mode and quiet ring on pickup? If so, I think I would try to either get with Verizon about it or maybe even HTC. It definitely sounds like it could be a phone issue. But I'm kind of new to all of this.
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
psicobelico said:
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
Click to expand...
Click to collapse
It's not a calibration issue. When the phone rings or you make a call via a headset and the proximity sensor is covered (ie. in your pocket or screen face down), the display kicks on and the prox sensor seems to default to "far" or "uncovered" (whatever term you like). It will remain at that value until you ACTUALLY uncover the sensor and then cover it back again.
alex.foto said:
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
Click to expand...
Click to collapse
The problem I have is that while the display is ON and sitting in my pocket, I have a chance of butt dialing someone or starting programs that drain the battery in addition to the dsplay being on. Not to mention, with the display on in my pocket, the heat builds up in the phone. I guess I have a $700 butt warmer? LOL
What steps will reproduce the problem?
1.establish a call
2.with the phone near your face, the screen turns off and you cannot hear the other party
3.move the phone away from your face, the screen turns on and you can now hear the other party
4.turn off the screen and you cannot hear the other party
i'm not going to ask for info on rom or kernel as i'm quite sure it's a hw problem
try reflashing stock rom but i doubt it can be fixed
Rudjgaard said:
i'm not going to ask for info on rom or kernel as i'm quite sure it's a hw problem
try reflashing stock rom but i doubt it can be fixed
Click to expand...
Click to collapse
Its not related by the rom...I installed lot of diferrent roms and nothing happened,actually cannot hear people while calling, they can hear me...when i put on spikerphone everything is ok.
I wish we could replace your faulty ear-speaker with words but we cant "yet?"
Faulty hardware as already Rudjgaard said.
Hello guys ...sorry if a similar question was already asked.
I have a problem with my phone. When i want to make a phone call the screen goes off. At first I thought that the phone switched itself off, but later I noticed that the credit was gone...:/ I happens even after the factory reset. It also happens with another dialer from google play...however, people can still call me and there is no problem...no problems with sms either.
I have 2.3.6 Gingerbread
Please help
I think that's normal. There's a sensor which causes this.
Lars124 said:
I think that's normal. There's a sensor which causes this.
Click to expand...
Click to collapse
so its not software problem? is it worth to replace it? how much may it cost?
i also checked another thing...its not only the screen there's no signal and a phone call is not made...:/
Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.
Lars124 said:
Every phone has this sensor. The intention is that you don't touch any button on your screen during the phone call.
You can try to reflash the stock rom.
Click to expand...
Click to collapse
I reflashed it...the problam's still there...but my friend call me back i called him but i didn't here any signal and the screen went off...:/
Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?
zombie1977 said:
Lars which sensor did You mean? Proximity sensor? Would that cause the phone to go silent (no dial signal)?
Click to expand...
Click to collapse
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...
zombie1977 said:
I run the proximity sensor test using *#*#0588#*#* and looks like it's broken...the screen is blue and displays "proximity x 1" covering the sensor has no effect, looks like the sensor is activated all the time...
I noticed some dust, maybe moisture in there so i think it will be a good idea to take the phone apart and clean the sensor...
Click to expand...
Click to collapse
I feel like a crazy person answering my own posts...
I took it apart, cleaned it, but the problem's still there. I bought a new assembly jack-speaker-proximity sensor on ebay for 7 euro...hope it will work after replacing this part...
The way it's all together explains why there was no dial signal.
When I replace the part i will let You know Thanks for Your help
No problem.
Tell me when you're done.
Lars124 said:
No problem.
Tell me when you're done.
Click to expand...
Click to collapse
Hello Replaced the part, tested, everything working beautifully Sweet I love this phone :cyclops: