Proximity sensor always on on new ICS device

[baudi]

I just got a new Galaxy s3 and I've porting my app settings, data, etc. from my DroidX to it. The only trouble I'm having is with the proximity sensor: according to Tasker, it's always on. I tried removing the context for the profile, then inserting it again and covering and uncovering the sensor several times, but it still shows "on".

I have an app called AndroSensor that correctly shows its value, so I'm not sure what's going on.

Any ideas?

[Pent]

Reboot ?

Pent

[baudi]

First thing I tried. I'd try uninstall/reinstall but I'm afraid I'd lose all my settings. Any way to avoid that?

On Tuesday, July 10, 2012 3:22:34 AM UTC-4, Pent wrote:

Reboot ?

Pent

[baudi]

Uninstalled. Reinstalled. Fixed it.

[Pent]

> Uninstalled. Reinstalled. Fixed it.

Had you restored Tasker with a backup tool previously ?

Pent

[baudi]

Yep. Titanium Backup. I figured that's what caused the problem, hence the reinstall.

[Pent]

> Yep. Titanium Backup. I figured that's what caused the problem, hence the
> reinstall.

Yes, you carried over the calibration value, same happens with light
sensor.

Pent

[baudi]

I guess that calibration can only happen the first time you ever include a proximity context on a given device, not when you delete all the proximity contexts, then reintroduce one and try to calibrate. Which is what I tried before reinstalling.

Anyway, its working fine now, and I'll no doubt forget that this is a problem by the time I get my next new phone. :-)

[Matt R]

Can you try making a profile with just the proximity sensor as a context? Then test that with screen on/off. Does that work correctly?

Matt

[MZ Guy]

That's actually the second thing I tried after creating the phone ringing profile. I just neglected to mention in my original post. I tried to set a vibrate action for a proximity sensor context (by itself). It didn't work... or more accurately... it worked by immediately vibrating regardless of whether anything was near the sensor, then never triggering again. I then added the other contexts to determine that it only seems to work correctly when joined with a phone ringing context.

[Matt R]

Could be something weird about the HTC one.  Maybe try to find a sensor test app on google play (I know they exist).  See if that gives you any more clues.

Matt

[Bob Hansen]

Sounds like the proximity sensor is continously blocked.

Do you have a screen protector on the phone? Some screen protectors activate the proximity sensor on some phones.

[MZ Guy]

It's something with Tasker, perhaps specific to the HTC One. I now have Gravity Screen Off installed, with proximity sensor features working very well, even with screen off.

I have no screen protector.

[MZ Guy]

Pent,

Can you confirm this is a bug? Any idea how to fix or workaround?

[Osh]

Apologies for resurrecting such an old thread but I'm experiencing the same problem with a HTC One mini.

A simple profile with Event, Proximity Sensor triggering a message to flash just results in the profile being active continuously even if the sensor is uncovered.

Does anyone have any ideas?