Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000 using XDA App
Mh? Why not pressing the home button during call.
Screen is enabled then...
Anyway MIUI got this option to switch it off.
Don't know if this setting is available in Stock ROMs.
screen should go back on when you move your head out of the ~5cm sensor radious. if it is not happening there are two possibilities:
- something wrong with firmware -> reflash phone with pure unrooted samsung firmware and check if problem persist
- someting is wrong with proximity sensor -> use warranty and send it to service center with proper description of the problem
Thanks for the replys the home button won't work as the proxy is up the spout had it checked the chip is blown, when u press the home key won't work as the phone is trying to find the proxy then eventualy it will crash and force close.
No software update will do it as its a hardware fault unless it turns it off so will have a look at the one you suggested.
There is def a stock version but i fear it is only on the s2 to turn blank screen off il check my bro's firmware, till then keep the suggestions coming in thanks....
Sent from my GT-I9000 using XDA App
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
SADист said:
Here is a possible solution. Check the + 3.7 volts at this point, if there is no tension, then feed it thither with a jumper
Click to expand...
Click to collapse
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)? Is there a way of hardware disabling the sensor? the software testers report 0.7 mA leakage on a sensor (which is faulty anyways)
lusjash said:
Thanks for the tip. Where can i get 3.7 V from? (which part of the MB)?
Click to expand...
Click to collapse
You can do this:
Related
I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?
Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.
It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.
It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).
Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!
Most probably replaced the phone's MB.
Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...
I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.
The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.
Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App
Does anyone know of a way to remove the proximity sensor drivers or shut it off completely my screen just goes black during a call and i need to use the keypad during calls i have tried all the proximity apps on market and it has no effect, have tried calibration etc odin firmware updates to the point i killed my phone just got it back from repair and was told it needs a new chip to rectify the problem.
I have spent weeks going through forums for a solution and i know on my brothers sgs 2 it has a setting in the menu to turn it off.
This seems to be a common problem with no resolve so im looking for someone to resolve this problem and make alot of people happy.
We all no As these phones age this will be more and more common.
Techies get ur teeth into this or even software writers make An app n earn some cash,
This would b a great ego booster for someone to say i solved that when no one in the world could.
Thanks...........looney
Sent from my GT-I9000 using XDA App
If it is only proximity sensor then you can disable it simply by going into settings>display >brightness> un-tick automatic brightness. And also disable power saving mode too.
Thanks evrest yeah have tried that but unfortunately that dosnt work, though using a headset does what i could do with is the same coding used in headset mode to be the same in handset mode
sent by looney on his galaxy gti9000 via xda app u no u gotta love the droid
try
Hardware Disabler in play shop
but you should know what driver for proximity
on xperia mini pro its
apds9702
Click to expand...
Click to collapse
try this app should work
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.
I have now purchased two different digitizer, and both of them suffer from inverted touch screen. It also seems to be off from being directly inverted.
Is there any rom, or fix for the scenario or app to resync the touch accuracy.
Thanks
Have the same problem. Tried two diffrent sellers and three different digitizers. The option and back buttons also don't work. Have you found a solution or someone who actually sells working ones?
I remember hearing about this issue before. I remember reading something about a manual calibration app from a Chinese android tablet that we tried to get working on here, but I don't think it worked out...
As for the buttons not working, do you mean that they work but aren't the correct function, or they just flat out don't do anything?
Sent from my LG-D415 using XDA Free mobile app
Same issue with my d-415
I Just installed a new LCD on my l90 and got the same results. The y- axis is inverted. Both the back and menu keys don't work at all. I did notice that when I rotate the screen the samex-axis is inverted . Which leads me to believe it to be a hardware issue and not in the firmware. Because the same inverted axis would move with the rotation right? ... I am going to do some more research. Probably disassemble and check over the connections with usb scope and see what I can't find. Let me know if you figure it out. Thanks!
Part of my m7 touch screen isnt working .. its kinda crazy cuz the phone never got dropped .. i saw that many people had that problem its between this two parts of screen that doesnt work theres a line that working..sometimes the touch isnt working at all !!
(when people call me sometimes).
its really disappointing cuz i like htc very much !
another problem that im having and saw that many people has it too : screen brightness always go maximum ! auto off for sure but still the brightness making problem tryed to reset the phone didnt help( not hard reset) it sucks to have a bunch of problems in a new phone ..
please please help me !
post.img.org/image/6naksobvx/
delete the dot in postimage ! sorry but this photo will help you understand and i have to share it !
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Val D. said:
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Click to expand...
Click to collapse
some times the screen back to full funcanlity
and please help about the other problem with the brightness .. its look like one of the sensors is broken in the phone .. maybe its the problem ?
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Val D. said:
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Click to expand...
Click to collapse
lollipop not root and other .. i deleted everything , did a soft reset not the hard type . no but i download lux to see if its help and it doesnt help either
The only thing left to try on a software side is factory reset the device. Many users report it clears various OTA Lollipop update bugs. The process takes about 10-15min, the OS will go through Android system update process again and the device will be reset to factory default state (don't forget to backup all your data). During the initial setup process don't restore your online account backup, make clean setup. Test the screen and digitizer before installing any 3rd party apps. Make sure your screen protector (if you have one) is not bugging the digitizer. If you have the same issues, then it's definitely hardware related (screen/digitizer assembly or connecting ribbon cables).