Why isn't Tasker detecting when my Location Context changes ?
Your radius is probably too small.
As an example, if you are not using GPS the accuracy of your fixes is probably
around += 2km, so your radius should be also minimally 2km.
If you *are* using GPS, the accuracy may still be only +-400m in built-up areas.
Here's a good way to create a location context:
- go to the geographical location you want a context for
- make a new location context
- deselect GPS if you don't want to use it
- press Grab Fix, and wait till it's done
This will set your radius appropriate to the accuracy of the location providers at that spot.
If there's still nothing happening:
- check GPS is on in Android Settings, if you're using GPS.
- check your device has a view of the sky, if you're using GPS
- network connectivity is often needed to get GPS started, and always needed for a Net location context.
- realize that location is only checked every 10 minutes by default when the Display is off (to save power).
You can check more often by changing
Menu / Prefs / Monitor / Display Off Timings / All Checks
- try the general 'nothing happens' tips
- look at other possibilities for detecting your location
Why doesn't my repeating Time Context work ?
It's important to understand that a repeating time context is a series of instant events.
Trying to combine a repeating time context with another context that does
active monitoring usually won't work e.g.
Time: Repeating Every 5 Minutes
Task: Enable Wifi (no toggle)
State: Wifi Near
Task: XXX
Wifi Near is checked on a static schedule. You currently can't change the schedule dynamically,
so the above two profiles will only do XXX when the 5 minute repeat happens to coincide with
when Tasker is doing it's Wifi Near check.
Why aren't my exit tasks run / settings restored before the device shuts down ?
Android gives an app very little time to perform cleanup during shutdown, this is especially
a problem on slow devices.
Therefore (as of 1.0.9), Tasker only attempts to run Variable Set, Clear, Add and Subtract actions
when the device shuts down, since they take relatively little time.
In the future, Tasker will have some concept of default values which will then be restored when
it starts after the device has booted again.
On Android 1.5 devices, Tasker cannot do anything at shutdown because the system does not send a notification.
Why does my Cell Near state keep going inactive ?
Even when your phone is motionless, it will probably still often switch between
different cell towers. Going to a different room in your house may involve
a whole different set of cell towers.
When you notice your Cell Near state going inactive at your location (and assuming
you still have a signal), launch Tasker, click on the Cell Near context and edit
it. Click Scan and you should immediately see a new Cell added to the list.
Click Done and then Apply and your context should go active again.
Sometimes the new cell will only be visible for a few seconds and will not appear
when you press scan. In that case, press the Recent button and
select it manually from the list.
Why doesn't my Perform Task action work when I Test it ?
When task (a) runs a Perform Task action to start task (b), the order in which the two tasks are executed depends on their relative priorities.
A feature of the Test button is that the tested task (a) runs at extremely high priority
to ensure that the task runs even if other tasks are running in the background.
So testing Perform Task with the Test button will only work as expected if in actual usage task (a) will always have higher priority than task (b) or the Perform Task action has Stop specified.
Why doesn't my App Context work ?
First, we need to find out which method Tasker is using to detect app changes on your device.
Disable Menu / Prefs / UI / Beginner Mode then look in
Menu / Prefs / Monitor to see if you have an entry App Check Method.
If you don't have such an entry, Tasker is using its Accessibility Service.
If Tasker is using Usage Stats for app detection, you need to ask Android to give Tasker
permission to do that, see Menu / More / Android Settings / App Usage Stats.
Otherwise, you need to make sure Tasker's Accessibility Service is enabled in Android Settings,
see Menu / More / Android Settings / Accessibility service.
Further tips:
- if Tasker offers you the choice to use different methods, try the other methods. Remember to give Tasker permission in Android settings for the new method (see above).
- If you are using Nova Launcher, set
Settings / App & Widget Drawer / Advanced / Automatically Close to off.
- Some apps (very few) aren't detected by Tasker, usually due to their internal structure.
- Some custom Android ROMs also have special configurations which prevent Tasker's app detection working.
For the latter problem, there are a few things you can try:
- look for special settings in your ROM that relate to 'keeping the launcher in memory'. They should be disabled.
- change the build properties file. Look in
/system/build.prop (or possibly /system/local.prop or /data/local.prop) for a line like:
ro.HOME_APP_ADJ=-17
Change it in a terminal program to look like this:
ro.HOME_APP_ADJ=1
If you didn't find an existing line, just add the new line as above.
Note: you will first need to make /system writeable. You can
do that e.g. with Tasker's Remount action. Remember to make it
not-writeable again after making the change.
- try detecting apps with a state using the %WIN (window title) variable; create a new state
Variable Value, %WIN, Matches, TITLE
where TITLE is the title of the window of the app you are interested in. For this solution to work, you also need to enable Tasker's Accessibility Service in Android Settings.
You can check what %WIN shows for the app you are interested in with this profile:
Event: Variable Set, %WIN
Alert / Flash, Win is now %WIN
Why doesn't the Keyguard action work properly ?
Android does not officially support toggling of the Keyguard by an app. The Keyguard
action was introduced in an early version of Tasker when a reliable workaround was
possible.
In more recent Android versions, the workaround is no longer so reliable due to
internal changes made within Android. If Keyguard works at all, there may be
disturbing side-effects.
The Keyguard action will likely be most reliablewhen the display is on and and the
Keyguard is already unlocked.
Some people have more luck with the same functionality provided by the
Secure Settings plugin. After install, you can find the
Secure Settings plugin in the Plugin action category. Note that a rooted
device is not needed to use this part of Secure Settings.
Why doesn't Tasker show my Local Media images anymore ?
When you select a Local Media image, Android grants Tasker rights to keep using
it.
However, when you uninstall Tasker, Android forgets those rights and doesn't
reassign them when you install Tasker again. This is clearly a failing in
Android... On some devices Android also forgets the rights when the device is rebooted, but this is very rare and almost certainly a problem with the particular device
involved.
To fix the problem, you wil unfortunately need to reselect the Local Media images
in the Tasker UI so that Android grants it access rights again.
