Tasker uninstall not successful

Once the subscriptions screen is open, tap the refresh icon in the action bar to download the latest set of subscriptions from SmartThings. The second icon is a star icon which indicates that a subscription is in place and is being used for Tasker. A subscription can also have both a widget and Tasker subscription -- in this case, if you long-press and try to remove the subcription, SharpTools will only remove the Tasker subscription leaving the widget subscription in tact.

Similarly, if you have both a widget and tasker subscription and then remove the widget, SharpTools will remove the widget subscription but leave the Tasker subscription in tact. Now that we have a basic understanding of how the Widgets and Tasker push event features work, let's dig into troubleshooting a bit. As of SharpTools 2.

This is a great place to start for troubleshooting. If you don't see an ID, this likely means that something went wrong when trying to register your device with Google. This will send a push message to your device using the SharpTools. This is a great diagnostic feature as it completely takes the SmartThings servers out of the loop and directly communicates with SharpTools.

After pressing the 'Send Test Message' button, you should see a message indicating whether or not the message was successfully posted to SharpTools. After a successful post, the next message you should see is a receipt of the push event. If the Send Test Message feature works as expected, the next step is to troubleshoot events from SmartThings. Before we get started with that, it may be helpful to enable Push Event Debug Notifications.

Once this feature is enabled, SharpTools will display a notification anytime ANY push event is received. This is particularly helpful in troubleshooting Tasker profiles where the profile might need some additional adjustments to work properly. Using the 'Send Test Message' feature will give you an idea how this works -- a notification will be displayed which when expanded displays the content of the received push event.

If you want to see all of the subscriptions for your device, open the Subscriptions pane instead. See the Subscriptions section for more details. After Push Event Debug Notifications are enabled, check that the desired attribute is subscribed as expected.

To do this, open the Things screen in SharpTools and scroll down to your desired device. You should see a star icon in the top-right corner of the Thing card indicating that at least one attribute is subscribed. Further to that, if you long press on the device, you should see a menu of items you can subscribe to and unsubscribe from. You should see an "Unsubscribe from There is a bug with some Android versions that the reported signal strength is not updated until the device is turned off and on.

One of unknown, service, noservice, emergency, nopower. Please note that the clipboard can't be accessed while the device's screen is securely locked. See also: CPU Control. Note: ID is not a unique identifier for the device, but rather for the hardware of the device. Not available on all devices. On some devices, if the Android setting Auto Brightness is enabled, the value will always be See also: state Heart Rate.

See also: state Humidity. To access particular parts, use the Variable Split action. Android 5. Note that Android does not return a value until the light level changes, so to test the sensor is working you should put it near a bright light initially. See note.

This value is not set until an offset of the GPS time from the fixed time has been calculated should be after the first GPS fix because the value is meaningless until that point. Updated once per second. See Also: state Magnetic Field. If more than one of the other supported apps is playing simultaneuosly, behaviour is unspecified.

One of on , off or auto. If auto , Android will decide whether it should be in Night Mode itself. On some phones it doesn't work Android limitation , seems related to the type of SIM. Duplicate names will appear on the list only once. The list always starts and ends with a comma to make matching easier, if it's not empty. From Android 5. If the SIM has not been unlocked it will not be available.

One of unknown , absent , pinrequired , pukrequired , netlocked or ready. See also: state Temperature. These variables will be empty until the first time a text is received after they have been referenced because Tasker does not monitor texts unless it's needed.

Name is set to sender address of no contact could be looked up. On Android 1. 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. 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.

It's not possible for the Tasker developer to work around, but is reported as fixed in version 1. Depending on other things you connect your device to, you might be able to use one of the following as a workaround:. It's possible that you will only be able to receive, not make, phone calls as another symptom of this problem.

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.

If you don't have such an entry, Tasker is using its 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.

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:.

You can do that e. Remember to make it not-writeable again after making the change. 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. 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:.

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.

Pre-made Projects. Index: en es fr zh. Feature Requests. Report Issues. Why won't Android let me uninstall Tasker? Why can't I select Tasker for an application context?