Re: Proximity sensor always on

[Matej dro]

Same problem here.

Dne četrtek, 21. marec 2013 14:26:27 UTC+1 je oseba solides...@gmail.com napisala:

Hello Guys,

my proximity sensor seem to be always "on" if I'm referring to tasker :-(

I made a little task who set a variable %Proximity to "on" if sensor is coverd and the value is always "on".

My device is a Xiaomi Mi2. The proximity sensor is working fine in other app ...

Thanks in advance.

[Wodge]

If you have a Profile with State: Proximity Sensor, it will always have the proximity sensor on to detect proximity to trigger this profile.

If you have another trigger in the same profile, e.g. State: Proximity Sensor + State: Charging Any, then it will only turn on the proximity sensor to await the trigger if the second trigger item is triggered (i.e. phone on charge in this example).

Try pairing the proximity sensor with another trigger in the same profile to limit the time that the proximity sensor is on to trigger an event.

[Matej dro]

No, you don't get it. Proximity sensor always RETURNS on (profile with proximity sensor is always active regardless if sensor is covered or not).

[Wodge]

How is your profile triggers set up. Can you post them here?

[Matej dro]

I have it like this:

Context: Proximity Sensor
Entry Task: Alert "Proximity COVERED"
Exit Task: Alert "Proximity UNCOVERED"

And as soon as I exit tasker and profile is saved, it will display "Proximity COVERED" and it will never say "Proximity UNCOVERED" or exit profile. As I stated in other thread, sensor itself works fine. Other apps can see its value normally.

[Rich D]

1. One thing you could try Is to make sure Tasker is Set to 'run in the foreground' in preferences / monitor.  

2. Are you running a custom ROM?  Some custom ROM's have been known To create problems with tasker..

Rich..

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rich D]

One more thing I would try is to temporarily  remove the other apps that use the sensor to make sure they are not conflicting with tasker..

[Matej dro]

1. Already set.

2. Yes, I have custom rom but that is not the problem. Every other app can read proximity sensor value normally.

3. I have no proximity sensor apps that would run in background installed at the moment. Only one I have is z-Device Test which is normal application (stops working when closed).

Is there any debug feature I could turn on to give you more data?

[Rich D]

>
> Is there any debug feature I could turn on to give you more data?

Hmmmm,   sorry, that's all I got... I would post all your stats Here (device, tasker and Android versions, ROM... etc)  as well as check the user guide under "How do I"  there is info there on getting logs and contacting Pent ( the developer ) 

Rich...

[Rich D]

Actually I think we missed the most important step of all. Did you try searching the group.... there are a few threads like this one out there..

https://groups.google.com/group/tasker/browse_thread/thread/ef301db5c229e7cf/17fd0af739ee5a65?hl=en&lnk=gst&q=Proximity+sensor+always+on#17fd0af739ee5a65

[TomL]

Try this.  Remove the Exit Task from your profile.  Create another profile:

Profile: NotProx

context, proximity sensor, inverted

entry task: alert: "Proximity Uncovered"

What's your device and android version?  Which ROM are you running?

Tom

[Matej dro]

I did search the group, but I did not found that thread. And it worked!

Damn, how the hell did I forget that. Thanks!

[Matej dro]

Let me post another semi-related problem here:

Sensor appears to be always on - light inside sensor is always glowing. My profile is Proximity Sensor + Screen On event. Shouldn't sensor only turn on when screen turns on then?

[Matt R]

I think I remember the developer saying something like the state contexts will be monitored (in their hierarchy) so that when the event context occurs, it knows whether to fire or not.  So unfortunately, limiting it with an even context doesn't really work.  As a kludge, you could try having the screen on event set a variable %ScreenOnEvent to true and then false.  Then, remove the screen on context from your proximity profile and add a variable value state of %ScreenOnEvent ~ true.

Matt