Why doesn't Tasker work in the background on my device?

To make sure Tasker and the AutoApps run in the foreground:

Why won't Android let me uninstall Tasker ?

You can disable it by going to Android Settings / Location & Security / Device Administration.

Why isn't GPS coming on for my profile with Time And GPS Location contexts ?

Why can't I select Tasker for an application context ?

Why does it take my Wifi Near state so long to exit ?

Wifi Near requires two check periods to pass without seeing the Access Point before the profile exits. This is intended to avoid the context activating and deactivating if the AP is briefly not visible.

Note also that there are different check periods for when the device is on or off, and by default the off-period is much longer than the on-period. See Menu / Preferences / Monitor/ Display On/Off Timings.

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:

Why does Tasker mess up the app launching when I have an Application Context for it ?

Some applications are sensitive like this. Probably all you have to do is put as the first action in the Enter task the action Wait and give as a parameter e.g. 300ms. If that doesn't work keep increasing the value until it does.

That gives the application time to finish initializing before messing around with the screen brightness etc.

Why aren't my settings restored ?

• if your profile sets setting x to on, then if x is already on when the profile goes active, it will be left at 1 when the profile exits. Test for this by putting an Alert / Notify action in the enter task to see what the original value was.
• some other apps installed on the system can cause Tasker to be killed and therefore the original settings being forgotten e.g. this has been reported to be a problem with Titanium Backup.
• similarly, if the system is rebooted suddenly, some devices aren't fast enough to save all the settings before the system turns off.

Why does my profile not do anything ?

• 'Task Killers'
• Quick System Info
• Autostarts

After that:

Why does nothing happen when I click a Tasker widget ?

Why does Tasker crash when I try to create a Location Context ?

Why can't I see any Tasker widgets in the home screen widget selector ?

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 ?

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 location exit task fire multiple times ?

A quick fix is to add a Cooldown to your profile. Click on a context, select Profile then Properties and slide the Cooldown Time to 30 minutes.

The profile is then prevented from going active more than once every 30 minutes.

Why does my Cell Near state keep going inactive ?

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 Notify LED work ?

• not all devices support all colours. Many devices will only support red and green. In general, colours near the top of the list are more likely to be supported.
• some devices will only flash the LED when the device is off at the time the notification is received.

Why do Tasker widgets disappear after a reboot on my Wildfire ?

It's not possible for the Tasker developer to work around, but is reported as fixed in version 1.25.405.1 of the firmware.

Why isn't my docking station detected ?

Depending on other things you connect your device to, you might be able to use one of the following as a workaround:

• State: USB connected
• State: Power
• State: BT Connected (if it's a BT dock)

Why aren't I getting any cell data for the Cell Near state ?

I was able to fix this issue by going into the EPST menues using
##DATA# on the keypad and changing the EVDO Preferred mode from HDR to
Automatic.

It's possible that you will only be able to receive, not make, phone calls as another symptom of this problem.

Why isn't there a green light for the On/Off radio button on the main screen ?

Why does the action Display Brightness cause my keyboard or application to close ?

To avoid that, you can deselect the Immediate Effect checkbox in the Display Brightness action.

Why is the date in Tasker's notification list completely wrong ?

This occurs if you select a transparent Notification Icon at Menu / Prefs / Monitor, but don't specify a Custom Notification Layout.

Changing to a non-transparent icon or a custom layout will fix the problem.

Why won't Tasker install on my custom ROM ?

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 ?

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.

Why doesn't Tasker think my device is rooted ?

1. the su program must be in your path
2. one of the following must be found:
   • a superuser package
   • the word modversion somewhere in the file /system/build.prop

If root is not being detected on your device but you are sure that root can be used by Tasker, you can therefore probably fix that by adding a line like:

# modversion this line enables Tasker root support

to the top of the file /system/build.prop.

Why doesn't Tasker show my Local Media images anymore ?

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.