-
Solved
Stuck on Install Welcome Screen
Device: Fire HD Tablet 10 with Google Play Services Installed
I was able to download tasker from Google Play Store but I am getting stuck on the "Before We Get Started" setup screen. I am able to check off the three boxes but there is a gray box below that says "Check all checkboxes to proceed".
Any work arounds for installing this? I triple checked to make sure that Tasker is not running with battery optimization.
-
autovoice headset rerouting not working on Android 12
Using Autovoice to Control BT for enabling headset sound (forcing audio through hfp profile ) isn't working on Android 12 device.
-
AutoTools Bluetooth Permission
Unable to determine how to add the required bluetooth connectivity permission on a OnePlus CPH2459 Nord 20 5G. When running a bluetooth related AutoTools action in Tasker, a notification will inform a requested permission is required. But selecting the notification does no action. Also attempting to add the permission via the App details page does not seem to be an available option to enable.
Android Build - CPH2459_11_C.13
-
Scene resolution NOT updating when exported to Factory KIDS APP
I make a scene and it is 910w by 525h. I export it as an app. I then later decide I want my scene to be WIDER, so I change the width from 910 to 925. Looks normal in Tasker. When I export it as an App however, the resolution is still 910w instead of the new 925 and all my buttons are pushed horizontally into the others if they were on the edge past 910 pixels.
-
Tasker disable Accesibitily Service of other apps
When Tasker enable Accesibility Service for itself, it disable Accesibility Service for other applications.
Uso la pulsación prolongada del botón de volumen-arriba para lanzar una tarea de Tasker. Para ello necesita tener habilitado el Servicio de Accesibilidad. Este servicio se desactivaba cada dos o tres días y tenía que volver a concederlo.
También uso constantemente el programa Quick Cursor, que también necesita el Servicio de Accesibilidad, pero nunca lo perdía.
Cuando se añadió la opción de que el propio Tasker vigilara si había perdido el Servicio de Accesibilidad y lo volviera a conceder, me alegré y lo active tanto para
-
Solved
Per app display rotation toggle prevents apps from entering recent in OneUI 5.1
So I have this Tasker profile which enables display rotation for some apps, and when I exit the app it disables it. However this seems to interfere with Samsungs recents button, as it glitches out and prevents those apps from entering recents. Disabling that Tasker profile fixes the issue. I don't know if this is a Tasker issue or Samsung issue... Any help or advice would be appreciated.
-
Solved
apps closing
i want tasker to open a specific link in multiple apps as a task like opening google in 5 browser and added enough timeout between actions and it work well but when i check open apps list just the last one is open.
even i have tried playing the task step by step but before opening an app it close the previous one.
also tried to just open apps by it and made a task to open 5 apps but again after opening each app it close the one opened before that.
how should i stop that ?
-
Solved
Profile without 'Restore Settings' do infact restore the sound settings
Sound setting to another level in the profile are placed back when the profile ends, without Exit Task or anything else.
-
Solved
Comprei a versão do tasker em inglês,veio em português! Quero meu reembolso!
Nas fotos do Google play estava em inglês,porém baixou em português,quero meu reembolso
-
The vibration doesn't work.
Hi. Vibrate, Vibrate Pattern actions don't work. There is no error, but there is no vibration. Android 11 Lineage Tasker beta 6.2.12-rc. All permissions from settings are obtained, as well as write_secure_settings
-
Solved
%VOLM and other global volume variables reporting incorrect value
Weirdly enough, tasker is not reporting the correct volume level on my head unit (Chinese aftermarket). Lots of tasks work normally, but when checking my volume level, it always returns the same value (e.g. 13 VOLM and 7 for VOLS). Anyone encountered this issue and/or has a lead on how to solve/debug this?
-
Alert -> Notify: Variable Values in Action Label Not Passed To %caller for Action
When using a variable to create part or all of the Action Label for an action within the Notify action, the notification correctly displays the variable value in the label. However, when clicking the action label to perform an action, the performed action's %caller variable displays the variable name instead of the variable value.
Steps to Reproduce:
- Create a task with the Alert -> Notify action.
- In the Notify action, scroll down to the Actions section and add an action.
- Give the action a label that includes a variable.
- Set the action to Alert -> Flash. Set the Flash action's
-
Display -> Status Bar Incorrectly Warns that Accessibility is Needed
On my Pixel 6a running Android 13, I have found that the Display -> Status Bar action incorrectly wants me to enable accessibility for it to work. I understand that on some devices accessibility is in fact needed.
This results in a few interesting quirks:
- When creating a Status Bar action, if it is set to Expanded, Tasker warns that I need to enable the accessibility service. But the action works fine to open the notification shade even if I decline to enable accessibility.
- If the notification shade is open, the Status Bar -> Collapsed action works as expected. But
-
Tasker on WearOS please?
This post is probably not within the scopes of what Tasker should be able to do, but I would be happy if it can happen.
I have AutoWear already and don't get me wrong, it is a great tool. However, versus the average individual who has their phone and watch synced all the time, I am not really into that. I like my device to be self-sufficient. One of the things I liked about AutoWear was it allowed me to deploy somewhat of a miniature routine to the watch in the background. For example, I used the AutoWear (default buttons)
-
Required Permissions in App Factory
The "Required Permissions" list presented by the App Factory while creating a kid app is preventing the devs from removing "required" permissions. This means that some permissions that by Google are classified as "sensitive" will be present in the APK even if not actually needed by the app, requiring full verification by Google, which may take long time for no reason. During the app testing stage it should be up to the dev to determine which permissions ACTUALLY are required for the app to function properly, not (what sometimes seems to be the case) by generalized "guesses" by the app
-
Tasker tasks don't work without internet connection [ Direct-Purchase Version ]
Hi, I have a Direct-Purchase licence registered on an Android device dedicated to old games and in this device the tasks do not work without an internet connection. I know that the Google Play version has this limitation but does Direct-Purchase also have this limitation ?
If I export the task to APK can it work without internet connection?
Regards.
-
Profile starts but action does not trigger
Hi,
I created a location profile that runs when I back to home. It starts always correctly. The linked Action for this profile is an Http Request (GET) to a specific address. If I run manually the Action in tasker It works fine, but it doesn't work automatically when profile starts.
This is my exported task (obviously in the http address I replaced my personal data like home coordinates and http key with fake chars):
I know that Ifttt has it's own location trigger but it works very bad. So after more and more tentatives I'm trying the Tasker way.
-
Dialog actions crashes Tasker in some circumstances
I would like to report a possible bug related, to the following actions, when used in the same task (or different), but when one of them is executed just after the other without any delay in between:
- Progress Dialog (1st)
- Pick Input Dialog (2nd)
It sometimes happens, and in other situations doesn't.
-
Load URL doesn't work for WebView element if the scene is not hidden/unhidden first
Source: https://www.reddit.com/r/tasker/comments/17d0dbq/load_url_doesnt_work_for_webview_element_if_the/
I'm building a project where I use the WebView element on scenes, and I noticed a possible bug that I wasn't aware about it until now.
Basically, I'm visiting www.google.com on first scene launch, using the Load URL option of the Element Web Control action. It works as expected.
The problem comes when you have an action (ie: scene button) that call the same base URL, and use it to reload the page when the scene is just created. Just like what the Home Button of a web browser does. Here, to make it work, you need include