Location tasks no longer working?

[Joshua Gordon]

Hi All,

I've had Tasker running on my Nexus 5 since the phone first came out (about a year and a half ago). One of my tasks is location aware and it basically looks at the cell towers to determine my work location. When I'm at work, it puts the phone on vibrate and does a few other notification things. When I leave the work area, it turns things back on. 

Recently, this stopped working. I didn't make any changes to my phone but I noticed Tasker was updated somewhat recently.

Has anyone else experienced issues with location tasks recently? Is there something I can check to find out what's causing this issue?

[Robert Ryan]

On Jul 21, 2015 9:14 AM, "Joshua Gordon" <jgor...@gmail.com> wrote:
>
> I've had Tasker running on my Nexus 5 since the phone first came out (about a year and a half ago). One of my tasks is location aware and it basically looks at the cell towers to determine my work location.

Are you using the Get Location action or the Cell Near action to determine your location?  

> Recently, this stopped working. I didn't make any changes to my phone but I noticed Tasker was updated somewhat recently.

IIRC, the update update did not affect either the Get Location or the Cell Near actions. I doubt Tasker is the culprit.

> Is there something I can check to find out what's causing this issue?

If you are using Cell Near, it is possible that your provider changed the quality or quantity of the towers in your area. Try re-scanning the towers.

Remember that the error of a non-GPS location can be >1km. So even if nothing changed the profile might not determine that you are at work.

[Joshua Gordon]

Robert,

I am using profiles and running tasks based on the location parameter with profiles. Worked perfectly for years and now all of a sudden it doesn't!

Other profiles that are time based work fine but not my location based one.

Any thoughts? Any way to diagnose the issue?

[Rich D]

> Other profiles that are time based work fine but not my location based one.
>
> Any thoughts? Any way to diagnose the issue?
>

Some times the data gets corrupted with a update.  I would start with making a new location profile and see if that works,

Are you using the GPS?

You can make a test task with a  'get location' action to make sure tasker can access your gps. 

[Robert Ryan]

Please post the description (not the XML! ) of the profile.

[Brian Houghton]

Hi Joshua,

I'm using the Cell Near state in my location profiles and they are triggering properly.

My suggestion:

1.  When at work, open the profile.

2.  Note the Cell ID's

3.  Scan for new Cell ID's

It's unlikely, I would think, but possible, that their ID's have changed.

My setup:  Note 4, Android 5.0.1, Tasker 4.7u3, no root

On Tue, Jul 21, 2015 at 6:31 PM, Robert Ryan <rbr...@gmail.com> wrote:

Please post the description (not the XML! ) of the profile.

--
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.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

-------------------------------
Regards,
Brian Houghton
bahou...@gmail.com

[skr]

Hi,

as mentioned here: https://groups.google.com/d/msg/tasker/gQnVIDlwaVw/v9LbBKilrdoJ
the location context (network only) stopped working on my Samsung Galaxy S6 after the android update 5.1.1.
Maybe you have the same issue. For me Tasker is now useless therefore I switched to the app "AutomateIt". This app works perfectly on Android 5.1.1.

Regards,
skr

[Preetham Rajan]

Hey guys, i'm going through the same problem. I have been using tasker for around an year now, using it for the location based triggers and auto-texting. I have a Nexus 5. I'm a frequent ROM explorer. Tasker did its magic on the stock ROM. For about the last month or so, the "cell near" triggering has ceased to function when the screen is off. I have enabled the new api, reverted to the old, tried both the workarounds as well. In vain, i recently moved from stock to Chroma ROM to CM12.1 hoping for things to work. I have restored backup and created new settings from scratch as well. Tasker worked fine for the couple of days (this week) post install of the new ROM but unfortunately has stopped working again. My last resort is to move to Automateit, but i have spent a good load of time learning and implementing my ideas on tasker in spite of being a novice. I don't want that effort to go down the drain. 

Currently running CM12.1 (non CAF) 20150716 build.

Attached is a log from tasker since the eve.

Any help will be appreciated. Thanks

Preetham

On Wednesday, 22 July 2015 11:09:43 UTC+5:30, skr wroteut :

[Marta Hintz]

Have you already tried checking that the cells haven't changed? Re scanning?

[Preetham Rajan]

yup, did that as well :(

[Joshua Gordon]

I've had 5.1.1 on my phone for some time now so I wonder if perhaps the recent issues related to location awareness not working are somehow a result of an update to Google Play Services or other core component that gets updated on a more frequent basis? I have Play Services 7.5.74 on my Nexus 5. Wondering if anyone has an older version of Play Services and can confirm that the location awareness works there and not on this new version? Or, is there anyone with 7.5.74 that actually has the location awareness working fine (so we can rule this out)?

Alternatively, can people using AutomateIt confirm that the similar function is working fine on that app? If so - it's clearly just a problem with Tasker.

Josh

[etc]

I have been using Tasker for years to track when I get home and when I get to work.  How I do this is with a Tasker javascript that I wrote to send the GPS data to my HA server.

I recently bought a Nexus 6 phone with Android 5.1.  I suspected that the google play services update was causing %LOC not to trigger a variable set event with the screen off (even though I have the display off monitoring set to every two minutes).

However, I figured out that somehow an option "Use Motion Detection" was checked under "Display Off Monitoring", and it appears this overrides the "All Checks Seconds" options when the display is off.  

I unchecked the motion detection option, but still things didn't work.  I had to use %LOCN to trigger the variable set event, while also keeping "Use Motion Detection" unchecked.

I'm going to try this some and see how things work.  The script the event calls actually queries %LOC, so hopefully that will still be set when the javascript gets the value for %LOC.  I'm going to test things this week and see how everything works.

[etc]

Ok using %LOCN to trigger the Variable Set event, then using a Task to trigger a Tasker javascript to get an updated %LOC works.  But using %LOC as the event trigger doesn't!?!