Database Users

[Q] Proximity sensor not working correctly

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.

D800 Screen keys pressed while on call - build.prop mod?

I´ve searched this forum, but found nothing like what I am facing. As per title, whilst on a call, with the phone on my ear (left ear usually, if that means anything) the on screen buttons are pressed, because I usually end up with the call on hold. Other times, it finishes the call, other times it dials a number from the contact list...Here´s a list of what I have done so far with no success:
1. Calibrate proximity sensor with apps
2. Use hidden menu to test functionality (it works as advertised)
3. Calibrate motion sensor
4. Full reset of the phone
5. Clear dalvik cache
6. Test sensor functionality with app (again, works as it should). It detects when my hand is covering the sensor and it detects when my hand is taken away from it. Instantly. Also, left my hand covering the sensor for a while (simulating a call) to see if at some point it stopped working, but no, the darned thing worked as it should.
I read somewhere here that a mod on build.prop might help (it has to do with the delay time of the proximity sensor) but since the post didn´t explain the exact setting, i googled it, and found 2 settings that might apply:
1.) ro.lge.proximity.delay
2.) mot.proximity.delay.
Neither of them is in my build.prop file, so, the questions that pop to my mind are:
1.)Which one of the two would affect the described issue? Apparently those settings are modified by users that had a problem with black screens after a call or with long delays for the screen to come back after taking the phone from their ears to use the keypad, but no post that I read indicated which one of the settings influenced what. I have the feeling that one of them is for the proximity sensor to "kick in" while the other controls how long does it take for the screen to come back after the proximity sensor stops detecting your ear.
2.)Can I add that setting to my build.prop without risking a bootlop or a brick?
As the title say, I have a D800, with official AT&T 5.0.2 ROM, rooted, with stock recovery.
Any help would be highly appreciated. As you can imagine is terribly frustrating that I cannot use my smartPHONE as a PHONE because of this!
Thanks in advance!
Frank.

a small, shameless bump!

Some Questions about Moto Display

Hi all,
i love the moto display feature but i have some issues that make it less usable for me.
- on certain conditions the moto display seems to react to fast, while on other i had to wave 3-4 times until the screen was woken up. Does anybody know what makes the display not recognize the wave sometimes?
- i hate the fact that the notifications are an all or nothing feature. i might have 10 notifications, and i can only dismiss them all at once. But i want to dismiss onlyspecific ones and keep the rest on my lockscreen. Is this possible somehow?
- as the moto display dismisses all notifications at once, and the regular android lockscreen doesn't, creates situations where there are notifications on the drawer (which need to be dismissed manualls) vs. the Moto screen that doesn't show any notification.
Is there any way to make the dismissing of notifications work as on stock android (possibility to either dismiss all, or only specific ones).

I'm pretty sure its a proximity and light sensor of some sort, but other than that, I'm having the same issues as you.
Sent from my XT1254 using XDA Free mobile app

I believe that only the sensors on the top of the phone fact to the wave. I don't know what the bottom sensors do.
Why is it impossible to find a diagram listing the location and function of all of the sensors?

If you have many notifications and want to do each individually, then instead of using the moto display just hit the power button to go to the normal lockscreen.

pizza_pablo said:
I believe that only the sensors on the top of the phone fact to the wave. I don't know what the bottom sensors do.
Why is it impossible to find a diagram listing the location and function of all of the sensors?
Click to expand...
Click to collapse
Top sensor is for waving (as you said). Bottom sensors are there for when you pick the phone up. If you go to pick the phone up, once your hand covers those two sensors, the display lights up. I found this out somewhere on XDA because I had no idea what they did either lol.

you can disable the sensor, and it will work like the first generation moto x.
Still, the sensor works fine for me, they just takes a little time to turn on after the screen lights on (about 1, 2 seconds) so it's not instant.

chris23445 said:
Top sensor is for waving (as you said). Bottom sensors are there for when you pick the phone up. If you go to pick the phone up, once your hand covers those two sensors, the display lights up. I found this out somewhere on XDA because I had no idea what they did either lol.
Click to expand...
Click to collapse
Thanks!
I checked out the bottom sensors, and it appears that they do respond only to touch, as opposed to waving over. :good:

Proximity sensor doing weird stuff since installing SlimKat on my Samsung Galaxy S3.

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.

Weird Proximity Sensor Problem

Hello XDA,
I have a weird problem going on with my Note 3. I had an issue where my screen would not shut off during calls so I immediately figured I'd test the proximity sensor with some debugging app and also the built-in service menu. I went ahead and did that and noticed it was sort of working but one of the values (the main one that ranges from 0.0 to 8.0) stayed at 0.0 and didn't change. I did some research and used an app that I believe recalibrated it and it began to work perfectly… EXCEPT, when the screen goes off during a call and SHOULD be locked from touch events I can still touch the screen and it is responsive, meaning even thought the screen is black I can end the call, mute it etc granted I touch the right area seeing as I can't see anything. Another thing that's going on that leads me to believe this is some sort of software bug is, when the screen is turned off due to the takeover setting, when I press the home button to turn it back on, it turns back on BUT the front app is lowered and i am brought to the home screen as if the screen was on and I hit it. Weird huh?
Any help would be appreciated…
Verizon Note 3 running on T-Mobile and CM13