Develop Bugs

Need help on disable proximity sensor TP2

Hi
how can i disable the proximity sensor on my HTC Touch Pro 2, windows mobile 6.1 ?
I use a screen lock app that dims the screen during calls but when coming near proximity sensor during call, the screen is turned on again - a real pain.
Please if any onw have an advice to shut it off cpmpletely or when i am on bluetooth i would be really happy for some help
PS i thought paroximitysensor was supposed to disable when tp2 is connected to bluetooth - but its not ??
thanks
Nolan

no one ?
regards nolan

having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.

thisisallen said:
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
Click to expand...
Click to collapse
Hi
could you test teh cab and tell us here if that can turn of permanemtly the proximity sensor ?
regards Nolan

TurnOffTheLight works to turn off the backlighting but as soon as you move the phone the proximity sensor kicks in again.

in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?

thisisallen said:
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
Click to expand...
Click to collapse
Hi
light functionality would not solve the problem regarding proximity sensor - its 2 different matters unfortunately
regards Nolan

i have allmost the same problem. my sensor is broken and alwayas is "On". so when i make a call on my hd2 android 2.2 screen goes off and never goes on again. how to kill it???

Called today helpdesk with same problem, cant be turned off , must go for a repair.

Proximity Sensor behavior and solution
I am a late comer to this bb! Hey,I thought all the bugs would be worked out by now! My keyboard did not work right, .... and I have had several other problems with the touchpro2. What are the Chinese doing over there? I had programmed many embedded units and microprocessor systems, but, really, how can they mass produce units like these? Too many cooks in the soup? They are leaving their quality control to the general community.
My problem was I use my gps for bicycling, and if I place it in the support case, the proximity sensor would shut off the screen, even though I was not placing a call. The screen would blank and not come back on. I noticed there was no problem if the physical keyboard was opened and also if the unit were held horizontally. It did this all the time, regardless of the app running.
There are two sensors at the top of the unit: proximity sensor and light sensor. This is a problem with the proximity sensor, at the left.
So I just placed duct tape over it. Now it does not blank.

[Q] Ambient light sensor - does Cyanogenmod change it

Does Cyanogenmod modify how the ambient light sensor works? My E4GT sucks at adjusting because it does it to often to drastically and to quickly. I have a touchpad that when running webos it controls ambient light sensor very different than the cyanogenmod does.
If that is not part of the rom is there a way to modify/improve how the sensor works?
PS i know there is an alpha.

Should I take that as a no?
If its a no is there something I can do to improve the way the sensor responds?
My main reason is when holding the phone horizontally and my hand goes slightly over the sensor it darkens so quickly, its just annoying.

Auto-brightness (dimming) works ONLY when tilted back (face-up)

Hey guys,
I've noticed this weird behavior and I was wondering whether anybody else came across this: if the auto brightness is ON and the light sensor is exposed to stronger light, it increases the screen brightness accordingly (so far so good!) - HOWEVER the weird thing is that when the ambient light diminishes (even when the sensor is completely covered) the screen brightness goes down ONLY if/when the phone is tilted back - facing up. The screen (auto) dimming seem to be interlocked with the accelerometer sensor - in other words, it doesn't react to ambient light changes until the phone is tilted back (or by the screen timeout).
To recap: in stronger ambient light, the screen brightness does increase automatically but when the ambient light dims down, the screen brightness gets adjusted (lowered) ONLY if the phone is tilted back (screen facing up).
On the other hand the light sensor test (*#0*#) shows no problems whatsoever - the lux value changes accordingly/dynamically, whether vertical or tilted - everything seems fine.
Even after a factory reset the symptom was still the same - anybody else noticed this?
My environment:
- SGH-I317M
- Stock 4.1.2, rooted
Thanks
PS: Please don't come recommending 3rd party apps that may resolve this issue. I'm interested in tackling THIS very specific occurrence.
-----------------------------------------------------------------------------------------------------------------------------------
EDITED: After some digging, it seems the whole culprit lays with 4.1.2. I reverted to 4.1.1 (clean) and this problem doesn't exist. As soon as I put back 4.1.2 (clean, not from nandroid) the symptom came again as described. Also confirmed by demo models from 3 carriers - being on 4.1.1.
Galaxy S2 with 4.1.2 also seems to be affected (even worse).
Please confirm/comment!

Ambient light sensor blinks when screen is off

So I just happened to notice that the sensor blinks on and off rapidly because I was using my webcams mirror mode and saw it flashing (invisible to the human eye). I cant help but wonder why on earth it is active while the screen is locked? Any thoughts? Or anybody actually know why?

Because it is used as a proximity sensor: the phone senses when it is in your pocket or not so it can change the ring tone volume. I think it is also used as a "mute" sensor when you lay your phone screen down on the table but I am not sure of that.

Touch screen problems? Maybe actually proximity sensor (which is terrible).

One of the touch screen issues I sometimes experience is when swipes are "broken" and register as shorter swipes and taps. This makes me think maybe the accidental touch protection, which is supposed to be triggered by the proximity sensor, is being triggered when it shouldn't. We all have read complaints about how the proximity sensor does not work very well.
So on a hunch, last time I had this issue (trying to swipe in gboard), I stuck my finger on the front-facing camera, and interestingly, swiping worked fine (I expected the screen to be disabled - guess that only actually is supposed to happen when you're on a call?).
Since this issue is so random it's hard to really test it. But I've had quite an experience with the proximity sensor.
I wanted the AOD to turn off when the phone is in my pocket, which is the norm on other phones I've used but for some reason Samsung does not do. So I set out figuring out how to do this in Tasker. I got a sensor test app and noticed the proximity sensor basically has two values: 0.0 and 5.0. It is very slow to respond (slower for "uncover" events) and seems to only switch to 0 if my finger is right on the camera. So I set up Tasker to turn the AOD off if the proximity sensor value is < 1, or on if it is >= 1. I also made it vibrate briefly so that I could tell when the sensor was toggling even if I couldn't see the AOD.
At first it worked fairly well. If I manually covered and uncovered the camera, the AOD would dutifully toggle (not instantaneously). But in "real life" practice, it turned out to be quite unreliable. There would be phantom proximity changes while I was using the phone or carrying it -- most interestingly, it often toggles the AOD off briefly when I pick up my phone -- but I didn't really notice any surprise vibrations while the phone was in my pocket. After a couple hours, when my living room got darker (not completely dark), the whole thing went crazy and the AOD would toggle every few seconds with the phone sitting on a table.
So I think the whole "let's ditch a dedicated proximity sensor and use other things to get the same result" is not quite mature yet. And perhaps it is buggy enough to cause one of the issues we think of as a touchscreen one.