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:
Related
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!
My face/ear hits number keys while I'm talking on the phone which sounds off tones and is annoying when talking to someone, especially when I'm talking to my customers. Is there any way to lock the keypad while talking on the phone?
southernblonde said:
My face/ear hits number keys while I'm talking on the phone which sounds off tones and is annoying when talking to someone, especially when I'm talking to my customers. Is there any way to lock the keypad while talking on the phone?
Click to expand...
Click to collapse
Your screen should go off when you're on the phone, did you make any changes?
BWolf56 said:
Your screen should go off when you're on the phone, did you make any changes?
Click to expand...
Click to collapse
I've made no changes.
What ROM are you running.
There's a proximity sensor that is supposed to shut off the screen when the phone is next to your head.
If you hold the phone and place your finger across the top where the ear speaker is, does the screen shut off?
If it doesn't shut off, then you need to check if it is hardware or software prob.
You can get apps that will give you status on the sensor on Google play. Example, Phone Explorer.
With it, you can move your finger over the ear speaker area near the top of the phone and see if the sensor is working. Its range is up to 5 cm, about two inches.
There are also some settings in some roms to override the proximity sensor staying on whenever the headphone jack is in use. The setting in CM10 is that the proximity sensor is ignored when the headphone jack is in use, or not ignored, if you so choose in settings.
Sent from my SGH-I897
laughingT said:
What ROM are you running.
There's a proximity sensor that is supposed to shut off the screen when the phone is next to your head.
If you hold the phone and place your finger across the top where the ear speaker is, does the screen shut off?
If it doesn't shut off, then you need to check if it is hardware or software prob.
You can get apps that will give you status on the sensor on Google play. Example, Phone Explorer.
With it, you can move your finger over the ear speaker area near the top of the phone and see if the sensor is working. Its range is up to 5 cm, about two inches.
There are also some settings in some roms to override the proximity sensor staying on whenever the headphone jack is in use. The setting in CM10 is that the proximity sensor is ignored when the headphone jack is in use, or not ignored, if you so choose in settings.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'm using CM9 in Slim Bean 3.1.0 I called my other phone number and the phone screen did turn black whenever i was holding it against my ear. When I take calls for work, I have to press 1 to receive the call and I'm not sure whats happening because when i pressed 1 the screen turned black.
I read that dialing *#*#0588#*#* will change the proximity sensor but it didn't work for me.
I will check out a program you mentioned because I've had two customers hang up on me, they thought we just had a bad connection with all the tones. LOL Thank you!
southernblonde said:
I'm using CM9 in Slim Bean 3.1.0 I called my other phone number and the phone screen did turn black whenever i was holding it against my ear. When I take calls for work, I have to press 1 to receive the call and I'm not sure whats happening because when i pressed 1 the screen turned black.
I read that dialing *#*#0588#*#* will change the proximity sensor but it didn't work for me.
I will check out a program you mentioned because I've had two customers hang up on me, they thought we just had a bad connection with all the tones. LOL Thank you!
Click to expand...
Click to collapse
I found that someone had the same problem http://forum.xda-developers.com/showthread.php?t=842049&page=2 and it was corrected with Gingerbread....but now is it only me that's having this problem with Slim Bean/Jelly Bean?
southernblonde said:
I found that someone had the same problem http://forum.xda-developers.com/showthread.php?t=842049&page=2 and it was corrected with Gingerbread....but now is it only me that's having this problem with Slim Bean/Jelly Bean?
Click to expand...
Click to collapse
Here is what came up for Proximity in Phone Explorer:
Name: GP2A Proximity Sensor
Vendor: Sharp
Version: 1
Power: 0.8
Resolutio:n 5.0
Max: 5.0
Range:
Inches: 1
When I ran my finger in front of the sensor, it sensed me only about 1/2 inch away.
southernblonde said:
Here is what came up for Proximity in Phone Explorer:
Name: GP2A Proximity Sensor
Vendor: Sharp
Version: 1
Power: 0.8
Resolutio:n 5.0
Max: 5.0
Range:
Inches: 1
When I ran my finger in front of the sensor, it sensed me only about 1/2 inch away.
Click to expand...
Click to collapse
I would change the inches range to 2-3 inches, perhaps that will help.
BWolf56 said:
I would change the inches range to 2-3 inches, perhaps that will help.
Click to expand...
Click to collapse
Do you know how to change it? Looks like Phone Explorer won't allow me to change anything, just observe.
southernblonde said:
Do you know how to change it? Looks like Phone Explorer won't allow me to change anything, just observe.
Click to expand...
Click to collapse
I'm not sure if there are apps that allow it, although, script/code can be made so users change it, I'll look into it. Feel free to look for a app that allows it though!
EDIT: Sooo I found the needed coding but it's for an app build. I'm hoping someone already built an app for this though.
BWolf56 said:
I'm not sure if there are apps that allow it, although, script/code can be made so users change it, I'll look into it. Feel free to look for a app that allows it though!
EDIT: Sooo I found the needed coding but it's for an app build. I'm hoping someone already built an app for this though.
Click to expand...
Click to collapse
Right here in the Genius Forums! lol
http://forum.xda-developers.com/showthread.php?t=951858
Oh crap! Will it work with my phone?
I found this app: Rezound Prox Sensor Calibrator in Google Play store. I'll let you know how it goes!
hmmm,
have you got a dirty screen protector or anything else blocking those little windows next to the ear speaker?
Sent from my SGH-I897
laughingT said:
hmmm,
have you got a dirty screen protector or anything else blocking those little windows next to the ear speaker?
Sent from my SGH-I897
Click to expand...
Click to collapse
No, nothing's covering it.
The Rezound App is totally not working. The same issue is happening. I wonder if it could be the Slim Bean rom I'm using? Should I try a different rom?
It seems like your sensor calibration is off and I don't know if a rom change will fix it. Did the problem start after flashing slim bean? Is anyone else with Slim Bean reporting same problem
I'm running straight CM10.0 stable build, November 13 build plus Gapps. Proximity is okay.
Sent from my SGH-I897
laughingT said:
It seems like your sensor calibration is off and I don't know if a rom change will fix it. Did the problem start after flashing slim bean? Is anyone else with Slim Bean reporting same problem
I'm running straight CM10.0 stable build, November 13 build plus Gapps. Proximity is okay.
Sent from my SGH-I897
Click to expand...
Click to collapse
Yes. The problem started when I flashed Slim Bean. I tried a proximity sensor app but it failed me.
Did you try proximity screen off lite?
It looks like in allows you to set threshold levels in the advanced settings.
You could also try reflashing slim bean if other slim bean users are not having the problem
Sent from my SGH-I897
laughingT said:
Did you try proximity screen off lite?
It looks like in allows you to set threshold levels in the advanced settings.
You could also try reflashing slim bean if other slim bean users are not having the problem
Sent from my SGH-I897
Click to expand...
Click to collapse
Yes, I did actually see that app but it scared me away when I read the reviews of all the problems that may accompany it.
I'm gonna try your other idea to flash Slim Bean again. Is there anything I need to do before that like wipe the cache? Perhaps some crap was left behind from all the problems I was having flashing a couple weeks ago?
southernblonde said:
Yes, I did actually see that app but it scared me away when I read the reviews of all the problems that may accompany it.
I'm gonna try your other idea to flash Slim Bean again. Is there anything I need to do before that like wipe the cache? Perhaps some crap was left behind from all the problems I was having flashing a couple weeks ago?
Click to expand...
Click to collapse
Clear cache and dalvik before reflashing. If it still doesn't work, I'd say to try a different 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
hi, does the proximity sensor work when you are NOT in a call ?
for example samsung decided to disable it unless you are IN a call, probably to avoid the blinking you can see in pixel 5.
thanks
rejett0 said:
hi, does the proximity sensor work when you are NOT in a call ?
for example samsung decided to disable it unless you are IN a call, probably to avoid the blinking you can see in pixel 5.
thanks
Click to expand...
Click to collapse
Hi, I had exactly the same issue on my S10e. I am happy to report that the proximity sensor seems to be working outside the calling app! I have tried DevCheck and it reacts to my hand wave.
thank you very much!
I have also tried a push ups app and it works as intended. I don't have to actually touch the screen with my nose anymore to get a count. It is enough to be 1-2 cm near the phone. So, no fat spots on screen!
type .12345+= in calculator to test
jfgt7j8qgx said:
type .12345+= in calculator to test
Click to expand...
Click to collapse
First, I thought "troll" but then I tried! Nice hint buddy, thanks!
I have a stock s10 plus. at first, the issue happened when I tried to pull my notification panel down but realized touch screen isnt working but its localized toward the top. Over the next few days, the area spread from top of the notifications bar to half of the screen and finally to my fingerprint scanner. I though the display is damaged but testing it with *#0*# test prove its working. locking the screen and unlocking it seems to fix it temporarily but it happened after a minute or two. my device feels laggy when the display is working normally. No visual damage nor did I damage it in any way
Arizzrn said:
I have a stock s10 plus. at first, the issue happened when I tried to pull my notification panel down but realized touch screen isnt working but its localized toward the top. Over the next few days, the area spread from top of the notifications bar to half of the screen and finally to my fingerprint scanner. I though the display is damaged but testing it with *#0*# test prove its working. locking the screen and unlocking it seems to fix it temporarily but it happened after a minute or two. my device feels laggy when the display is working normally. No visual damage nor did I damage it in any way
Click to expand...
Click to collapse
Maybe try to factory reset to see if it resolves the issue.
Keno_I said:
Maybe try to factory reset to see if it resolves the issue.
Click to expand...
Click to collapse
doesn't work. i even tried using the firmware that worked before and had no issue but it doesn't work now
Saeremi said:
doesn't work. i even tried using the firmware that worked before and had no issue but it doesn't work now
Click to expand...
Click to collapse
Possible water damage?
It sounds like mobo issue... as the display tests normally and firmware doesn't fix it.
Try a hard reboot.
MOD ACTION:
Thread closed at the request of the OP.