Proximity Sensor is confusing Shake action?

[Nixx]

I have three profiles.

1. Display-On profile
2. Proximity Sensor profile (which is turned on for 10 seconds by the 1st profile)

3. a shake profile (which is completely unrelated to 1 or 2)

When I trigger the Proximity Sensor (and the action is executed) it somehow also triggers the shake profile and that action is executed too

is this normal ? :)

[Pent]

I would start by checking the Run Log.

Pent

[Nixx]

On Saturday, September 15, 2012 5:20:21 PM UTC+2, Pent wrote:

I would start by checking the Run Log.

When I do so the status of the Shake Profile gets set on "instant" at the same second the Proximity Profile was set on "active"
(this while the phone is flat on the table)

[Nixx]

Here you can find the RunLog file.

I stripped down the project and renamed the tasks so it makes a bit more sense and did some isolated tests (the previous situation was in a bigger project).
8/9 out of 10 times the Shake profile is also executed, which is odd, as I need to shake the phone firmly to enable the shake profile alone.



On a side note (not related, but confronted during the testing process)

When working with multiple projects in tasker one has many tasks & profiles spread over the different projects.
It would be great to have a settings in the UI menu to disable the ability to see tasks/profiles/scenes that are not related to the current project (with the active tab)
This way you don't have to scroll through 100+ tasks when assigning a task to a profile or run task / stop task action etc.

For me this is often the reason to temporarily delete a whole project(s).

[Nixx]

On Saturday, September 15, 2012 7:49:38 PM UTC+2, Nixx wrote:

Here you can find the RunLog file.

I stripped down the project and renamed the tasks so it makes a bit more sense and did some isolated tests (the previous situation was in a bigger project).
8/9 out of 10 times the Shake profile is also executed, which is odd, as I need to shake the phone firmly to enable the shake profile alone.

it might be worth to mention that the shake profile is more often triggered when the phone is not shaken.
If I recall correct this is most often when I plugin the usb cable or when it wakes up after a long time not using.
I always dismissed it as a random bug thing and didn't really care...
Thought that the phone had been moved rapidly while the screen was off and activated with delay when the screen was turned on again.


btw. the shake profile is set to only respond while the screen in ON via the options in the tasker settings.

[Pent]

Could you export here the descriptions of the 3 relevant profiles as
well please ?

Thanks,

Pent

[Pent]

> When working with multiple projects in tasker one has many tasks & profiles
> spread over the different projects.
> It would be great to have a settings in the UI menu to disable the ability
> to see tasks/profiles/scenes that are not related to the current project
> (with the active tab)
> This way you don't have to scroll through 100+ tasks when assigning a task
> to a profile or run task / stop task action etc.

Isn't that going to be annoying if you want to assign a task/scene etc
from outside the project ? In other words, we would need a way in the
UI to quickly turn on / off this feature. Anyway, I'll put it on the
list.

Pent

[Nixx]

Isn't that going to be annoying if you want to assign a task/scene etc
from outside the project ? In other words, we would need a way in the
UI to quickly turn on / off this feature. Anyway, I'll put it on the
list.

Perhaps it would be a good spot to put it in between the long press button of projects, that's it's quick enough reachable.
It would be great to have this also with the variables: show only of 1 project and to be able to only clear variables of one project.

[Nixx]

On Sunday, September 16, 2012 9:00:30 AM UTC+2, Pent wrote:

Could you export here the descriptions of the 3 relevant profiles as
well please ?

to be complete, here is all:

Profile: Screen_on (9)
Event: Display On
Enter: Turns_on_proxPRF (3)

Turns_on_proxPRF (3)
A1: Profile Status [ Name:Proximity Set:On ]
A2: Wait [ MS:0 Seconds:6 Minutes:0 Hours:0 Days:0 ]
A3: Profile Status [ Name:Proximity Set:Off ]
A4: Variable Clear [ Name:%ID_PROX Pattern Matching:Off ]


Profile: Proximity (8)
State: Proximity Sensor
Enter: Prox_task (7)

Prox_task (7)
Run Both Together
A1: Variable Set [ Name:%ID_PROX To:%ID_PROX  + 1 Do Maths:On Append:Off ]
A2: Vibrate [ Time:75 ] If [ %ID_PROX = 1 ]
A3: Perform Task [ Name:SubProxTask Stop:Off Priority:5 Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: ] If [ %ID_PROX = 1 ]
A4: Run Shell [ Command:one light on Timeout (Seconds):2 Use Root:On Store Result In: Continue Task After Error:On ] If [ %ID_PROX = 1 ]

A5: Vibrate [ Time:75 ] If [ %ID_PROX = 2 ]
A6: Stop [ With Error:Off Task:SubProxTask ] If [ %ID_PROX = 2 ]
A7: Run Shell [ Command:all Lights on Timeout (Seconds):2 Use Root:On Store Result In: Continue Task After Error:On ] If [ %ID_PROX = 2 ]
A8: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A9: Run Shell [ Command:Lights off 0 Timeout (Seconds):2 Use Root:On Store Result In: Continue Task After Error:On ] 

SubProxTask (2)
A1: Notify [ Title:darkness Text:remove to enable Icon:<icon> Number:0 Permanent:Off Priority:3 ]
A2: Wait [ MS:0 Seconds:33 Minutes:0 Hours:0 Days:0 ]
A3: Notify Cancel [ Title:instant.LUC.darkness Warn Not Exist:Off ]

Profile: Shake (10)
Event: Shake [ Axis:Left-Right Sensitivity:Low Duration:Long ]
Enter: Shake_Task (4)

Shake_Task (4)
A1: Run Shell [ Command: other light stuff Timeout (Seconds):0 Use Root:On Store Result In: Continue Task After Error:On ]

[Matt R]

This seems like a longshot, but maybe try removing the vibrate actions from your proximity task? Perhaps the vibration motor in your phone is just close enough to the accelerometer to trigger it ...

Matt

[Richard Davis]

Have you tried starting from scratch? I just tried these 2 profiles and could not get the test shake to fire with the test prox.  All work as it should..

Rich....

Profile: Test Prox (268)
State: Proximity Sensor
Enter: Test Prox On (269)
A1: Notify [ Title:Prox On Text: Icon:<icon> Number:0 Permanent:Off Priority:3 ]

Profile: Test Shake (270)

Event: Shake [ Axis:Left-Right Sensitivity:Low Duration:Long ]

Enter: Test Shake On (271)
A1: Notify [ Title:Shake On Text: Icon:<icon> Number:0 Permanent:Off Priority:3 ]

[Nixx]

On Sunday, September 16, 2012 7:17:51 PM UTC+2, Matt R wrote:

This seems like a longshot, but maybe try removing the vibrate actions from your proximity task? Perhaps the vibration motor in your phone is just close enough to the accelerometer to trigger it ...

Matt

actually, it vibrates after the shake-task has been triggered as that one is executed before the proximity tasks.
and it only does the shake-task once (and it vibrates 3 times when I trigger the action twice)
So from that i'd guess it's unrelated to the vibrate (I think I even added it later to see if it still happened as I thought it was related to the run shell action)

[Nixx]

will give it a try later on to recreate it. I'm actually thinking that it is related to the "screen-on" profile, did you include that one too?

 

[Richard Davis]

Just added this...

And all still works as it should...

Hope this helps.... Rich

Profile: Screen On (272)
Event: Display On
Enter: Screen On (273)
A1: Profile Status [ Name:Test Prox2 Set:On ]

A2: Wait [ MS:0 Seconds:6 Minutes:0 Hours:0 Days:0 ]

A3: Profile Status [ Name:Test Prox2 Set:Off ]

Profile: Test Prox2 (268)

State: Proximity Sensor
Enter: Test Prox On (269)
A1: Notify [ Title:Prox On Text: Icon:<icon> Number:0 Permanent:Off Priority:3 ]

[Nixx]

Okay, finally looked at this one again.

Have recreated the project, but my shake action is still triggered by the proximity sensor 9 out of 10 times.
Have attached the project. Would be great if someone could give it a shot to see if it happens on other phones too?

tnx!

[Richard Davis]

OK.....
I downloaded and tested

At first I could only get the shake to activate 1 out of 10 times at best and that  was only when sitting on a hard surface. It would not activate when i had the phone on a soft surface.

I disabled the vibrate and could not get the shake to activate at all ( except of course when i shook the phone)

So i would say that it does behave as expected on my device.

I have a moto droid 4 running 2.3.6.
Using. Tasker  Version 1.3.1m.  NOT rooted

It has been reported that the key guard has some flakey behavior.  Perhaps try to immediately exit the key guard and see if it still miss behaves.

Rich....

[Nixx]

On Tuesday, September 25, 2012 12:54:25 AM UTC+2, Rich wrote:

OK.....
I downloaded and tested

At first I could only get the shake to activate 1 out of 10 times at best and that  was only when sitting on a hard surface. It would not activate when i had the phone on a soft surface.

I disabled the vibrate and could not get the shake to activate at all ( except of course when i shook the phone)

So i would say that it does behave as expected on my device.

I have a moto droid 4 running 2.3.6.
Using. Tasker  Version 1.3.1m.  NOT rooted

It has been reported that the key guard has some flakey behavior.  Perhaps try to immediately exit the key guard and see if it still miss behaves.

Rich....

Thanks for testing!

The vibrate only happens the second time that the proximity sensor is triggered, here I get it with the first and/or second time and on both soft and hard surfaces.
I do use a delayed screen lock app (and no key guard)

Maybe it's interesting to see if someone else with an Xperia U encounters the same issue.. perhaps it could be internal? (or is that not possible)

 

[Nixx]

There is definitely something wrong with it on this phone.
I went back to the basics and used the following setup without the "screen on" trigger to exclude screenguards etc.

proximity profile (always on)
action > flash "proximity"

shake profile  (always on)
action > flash "shake"

And also with only these settings the shake flash is shown when the proximity has been triggered, the more the proximity is trigerred, the more it gets mixed up.
I've tested while holding the phone still in the air without movement or flat on the desk (without touching the desk)

I tried all sensitivity settings for the shake from low & short to high and long and in different directions. In all cases it gets mixed sooner or later
sometimes after the 1st trigger, other times after a few triggers in a row (phone is as fixed as possible at all times)

Will check with other xperia U's user around here, see what's happening with them

[Richard Davis]

Are you rooted? I have read that some ROMS have tasker issues.

[Nixx]

On Tuesday, September 25, 2012 3:17:04 AM UTC+2, Rich wrote:

Are you rooted? I have read that some ROMS have tasker issues.

Yup I am, but this would be the first root-rom related issue then I think.
Apart from the limited bitmap memory on this phone all other features seem to work inline with what's happening in bug-land

[Richard Davis]

I think you are on the right track to figuring it out. I would suggest posting on a device and rom specific forum (like xda )  looking for tasker users. Just to cover more bases. 

I do have another suggestion  for your profile when you hopefully get it working.  I believe the way it is set up now with the quick triggered nature of the proximity context and having the task set to 'run together '  you could get several occurrences of the task running at the same time and with waits involved you might get some unreliable results.

If what you are after is to 'do stuff' on the second occurrence of the proximity sensor after the screen comes on then I would suggest using two profiles with proximity contexts.  The first would have a stop as a entry task and set a variable on the exit that would trigger the second profile with a proximity and variable value context. Then 'do stuff ' in the entry task and reset the variable and shut off the profiles in the exit.  ( not tested but it should work) 

Just a thought .... hope you don't mind... Rich

[Nixx]

I never mind good thoughts, thanks for those.
I did have a split setup before (without run together) but this setup is also worth a shot.
But yeah, first to figure out the confused triggers.. asked another Xperia U user to check this thread.