Does anyone notice that when you hold it from the bottom, the grip sensor activates and causes unwanted audio interference? My music sounds terrible with it constantly crackling.
I've disabled the grip sensor in settings, but it still does the same stuff, so it must still be activated. Is there a way to disable it completely?
Ok, I popped open the phone, and removed the sensors.
My camera button doesn't work anymore (it is connected to the grip sensor cable), and neither does the grip sensor, but there is no more audio interference.
That's a way to do it
echo 0 > /sys/class/sensors/grip_sensor/onoff
But of course, you can just put it away
Related
I'm having trouble with the proximity sensor on my HD2. It works if the phone is pressed up directly on my ear, but if I move it away just the slightest, the screen comes back. Is there somewhere I can access the proximity sensor settings, and give myself a bit more room? Like, say, anything inside an inch shuts off the screen?
ROM info is in the sig, and I'm using the HTC phone dialer, if that makes any difference.
http://forum.xda-developers.com/showthread.php?t=624206
Aw balls, I hate it when there's a thread for this, and my impatience with searching failed to find it.
Thanks!
Doesn't sound like that app does anything for the sensitivity, unless i missed it. it just makes the screen stay off after the sensor is activated.
However the point of the proximity sensor is to shut off the screen so your ear isn't pressing buttons. If you've got the phone far enough away from your ear to reactivate the screen, then there's no longer a need to turn off the screen to prevent ear dialing.
If you're worried about power savings, the screen should shutoff in a minute or so, depending on your screen timeout options
d0ug said:
Doesn't sound like that app does anything for the sensitivity, unless i missed it. it just makes the screen stay off after the sensor is activated.
However the point of the proximity sensor is to shut off the screen so your ear isn't pressing buttons. If you've got the phone far enough away from your ear to reactivate the screen, then there's no longer a need to turn off the screen to prevent ear dialing.
If you're worried about power savings, the screen should shutoff in a minute or so, depending on your screen timeout options
Click to expand...
Click to collapse
correct, I haven't found a way to change the sensitivity for it, just turn it on or off. I believe the way the sensor works like a motion sensor in a store, either you are there or not... Hardware driven on sensitivity, not software.
Nibbley15 said:
correct, I haven't found a way to change the sensitivity for it, just turn it on or off. I believe the way the sensor works like a motion sensor in a store, either you are there or not... Hardware driven on sensitivity, not software.
Click to expand...
Click to collapse
I actually posted about the sensor in another post. The sensor is just an IR LED and a photo diode. The photo diode looks for the reflected IR when the phone is near something like your ear.
The IR LED only turns on during a phone call. Try this get a digital camera with a live preview and aim it at the 2 dots where the proximity sensor is, you'll see the IR LED light up when you initiate a call
The same photo diode is used to alter the screen brightness depending on the ambient light that hits it
seen quite a few people complain about this so just thought id toss out a quik possible fix.
http://www.mariusb.net/blog/2010/11/htc-desire-problems-with-proximity-sensor/
Proximity sensor functionality in my G2 had become intermittent and worsened until it recently stopped working completely. The screen would stay on during calls even if I covered the sensor area completely with my finger, and the sensor showed no response when checked via a testing app.
I sprayed bursts of air (from canned air) into and across the speaker grill area in different directions, then used a DataVac with a narrow attachment to vacuum the speaker grill area. The proximity sensor is able to sense again!
Well, I've searched the forums for this phone and I haven't found anyone with this issue.
When I make or receive calls, the proximity sensor either doesn't turn off the screen or, more often, it does but turns it back on after a while. This results in random keys being pressed making noise and, eventually, it presses the button to end the call or puts the call on hold and dials another number.
It's very, very annoying. Could it be something on the settings? Hope it's not hardware... Any sugestions on how to solve this?
I'm using Miui 1.9.9 with franco.kernel from 10 set.
The proximity sensor is located at the top left corner of the phone (next to the speaker) and flashes red while active. Make sure you cover this area with your head when speaking. I am left handed and sometimes the sensor doesn't detect anything because of the way I hold it, this could be the case with you also...
There are some apps that can help you test the sensor if it works or not.
Mine was stupid too with stock rom, but with custom roms it works very good. detects even finger in 3cm range and turns on screen after 2 seconds.
Any idea if I can manually tweak proximity sensor behavior? I have problems during call, when I slightly move phone, it seems that it turns on screen for moment and I usually press mic mute button. Happens on every third call, hate it. My idea is to make proximity sensor react slower, for example with 500ms delay. It would be enough to handle these problems when phone turns on screen and I'm stuck with disabled mic.
Phone is rooted, with latest RR.
I searched, and didn't find any other posts about this, but the search engine here seemed a bit flaky.
I installed SlimKat 4.4.4.build.8.0 on my Samsung Galaxy S3, um, last year I think it was. I had previously been using SlimBean, having dumped the original Samsung ROM fairly shortly after I bought it. Since then there has been weirdness that relates to the proximity sensor.
I used E-Robot to disable the screen when anything is close to the proximity sensor. So put it face down, screen off; put it in my shirt pocket face inwards, screen off; leave it on the desk face up so I can see the screen, screen on. Naturally - hold it to your ear on a phone call, screen off, though that's a basic function of the proximity sensor, it did that anyway. On the flip side, if it was blanked and you uncover the sensor, the screen would come back on, but it would be the Lightning Launcher lock screen that I prefer. I got used to Lightning Launcher from SlimBean.
After installing SlimKat, when covering the sensor, first the volume controls show for a few seconds, THEN the screen goes off. Coming out again, the Lightning Launcher lock screen would not show. This got a bit awkward before I figured it out. I usually put my phone in my shirt pocket screen inward, so that the sensor triggers the screen disable. But now, since the volume control is showing for a few seconds first, I discovered that my chest would brush against the screen, randomly adjusting one of the volumes as it went in my pocket. Since I usually have the volume turned all the way up, the only way was down. I missed a few phone calls that way before figuring out why my phone wasn't ringing.
So I have disabled that E-Robot thing now. BTW, there's no way to turn the SlimKat screen blanker off? I would have tried that first, but could only find how to set the timeout, not how to turn it off.
More recently, though this may be a new hardware problem, but it's a big coincidence ... now the proximity sensor refuses to work at all. It always thinks it's covered. This is a really big pain, since as mentioned above, the proximity sensor is designed to disable the screen when you hold it to your ear, only now it disables it the moment the phone call starts, AND refuses to enable it after the phone call is over. The sensor still thinks it's being held to your ear, the screen stubbornly refuses to switch on, no matter what buttons I press. Only way I can get out of that state is to pull the battery. This is not good. (On the other hand, this sort of thing is why I always get phones with swappable batteries, as a very experienced computer dude, I know that sometimes you just have to kill the power.) So anyone I call gets to hear my swearing as I rip the case open and pull the battery out, before I can end the phone call. Though pulling the battery naturally ends the call. lol
About the same time I noticed the proximity sensor no longer working, I noticed the up volume button also isn't working. That could have been broken for awhile, I rarely use either volume control. Part of the reason for doing this entire proximity sensor disabling the screen thing is so I could avoid wearing out the physical buttons. The S3 is old, but I like to keep my computer hardware running for a long time.
Sooooo, proximity sensor and volume controls interact in odd ways, then both fail. That's a pretty big coincidence. Though having just written that, I have come up with a new theory. Maybe some common part of the physical circuitry for the sensor and the button was going flaky, such that the sensor triggering sent noise through the up volume control, triggering the on screen volume controls before blanking. Still, a coincidence that it only happened after installing SlimKat. Also, wouldn't this trigger both volume controls and screen disable at the same time, rather than within a few seconds? No idea how Lightning Launcher fits into this new theory.
So I'm still not sure what's causing this, or how to fix it. Other than going back to SlimBean to see if that fixes anything. It doesn't look like I can go forward, 4.4.4 looks like the last SlimRom made for the S3. At least according to OTA.
Anyone got any ideas? "Buy a new phone" isn't a good answer for me right now, can't afford it.
onefang,
I have a S3 that I ran the Slimkat 4.4.4 build 9 on for a while (9 months). There is a known issue with the CM package (used in SlimKat) that causes the volume button not to work correctly. When you are on a call, the call volume can not be raised or lowered. There may be other issues. I am currently running the CyanogenModCM12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att rom and the performance is much better than Slimkat.