Many users are reporting that the speakerphone action is broken. I know that it never worked on my Motorola Droid Turbo 2 with Nougat or my Samsung Galaxy S9 with Oreo.

OnePlus and Pixel devices are also experiencing this issue.

When exporting an app with App Factory the attached issue happens on some devices.

I want to report a bad behavior related to the Element Create action, under Scene category.

The problem is when the user loads that action again, after being created and edited, all the text content disappears. So, even you have an Anchor action where to save the current configuration (to be edited if needed), it has to be created again.

Note: A demo is included as an attached file.

Could the sliders (SeekBars) used by Tasker actions be improve or made customizable in settings? I find it impossible to use the press-and-drag method -- they just don't move, and the click method is very hit-and-miss.  Using the arrows is often impracticable when the value range is large since the arrows change the value by only +/-1.  Also in some cases a "logarithmic" (actually "exponential") scale would be more appropriate, e.g. for setting a Beep tone frequency where getting somthing in the middle of the audio spectrum on a linear scale that goes from ~0 to 16000 is extremely awkward. 

Sadly not a root free method, but rooted users can take a call in Nougat by using input keyevent 5 - Could this please be added as a Take Call action if root is available please? Thanks.

It would be pretty useful if when a Task or the like %err's, that this can be used as an Event Context. We already get notifications; But for cases where Tasks are expected (and sometimes required) to fail, such an event context would be useful.

An example of this is when wanting to dynamically adjust a Tasker service; say Accessibility. Task fails, %errmsg can be sent along with %caller() or the like.

It'd be sooo much better than adding tonnes of workarounds all over the shop to individual tasks when most errors can be remedied in identical ways. Task errors,

I made a short video to illustrate the problems.  Please view it!

https://www.youtube.com/watch?v=z86c_crDCyk

There are two problems with dragging and dropping items:

1. Dragging and dropping an item between two other items SHOULD place it between them.  But it does not.  It doesn't work properly.  It often either doesn't register any change in position, or it puts the item in the wrong place altogether.  Here is another video demonstrating the problem; in this one, the dragging doesn't do ANYTHING for the first few attempts: https://www.youtube.com/watch?v=kKYqYJBBMy4

2. There should really be some UI to indicate where a dragged item will land, similar

I want to disable my 'work' alarm when my calendar has an event 'holiday'.

The task 'Cancel alarm' only opens the alarm app on my phone, but does not cancel it. Makes no difference which mode (disable current, by label, any). I have a Samsung Galaxy S9 with Android 8.0, alarm app v7.0.92.4.

PS: The task 'Set alarm' actually does work.

PS2: also plugin 'ClockTask' wont disable an alarm.

I have a profile that detects when certain apps are launched. I found that if you launch the app from the app icon or launcher, it works fine (even if the app is currently in the recents list). If you re-open the app from the recents list, it doesn't detect the app as running or sometimes detects it but takes a long time and possibly only when you pull down the notifications. 

Android version: 9

Tasker version: 5.2.bf1

When programmatically updating two scene elements, one element will get the value of the other, at least for Number Pickers. `new_val` acts like a Singleton having just one state.

I've been seeing this behavior for the Expiry Hours element. Logging shows one value of `%new_val` before the assignment and a different value after the assignment.

Logging shows `eh` eventually getting the value meant for `em`.

Or at least create a new ISODATE variable that outputs date in YYYY-MM-DD standard.

The format changed from DD-MM-YYYY to M-D-YY and this is causing a whole lot of trouble with my automations :-(

The Location Mode action does not work as expected on Android 9. This is due to the new "Location Accuracy" setting which supersedes the three location modes that were used on previous versions on Android and that are still presupposed by Tasker. Details as per this post:

When copy pasting a scene element, the dimensions always change slightly. (e.g. a rectangle of 50x50 becomes a rectangle of 54x47).

If you immediately change the dimensions (before closing the element edit scene), then the changes will not save. You have to open the element again and change the dimensions.

Hi,

When I activate accessibility for Tasker on my Android TV (Mi Box) running Oreo I can no longer access the left bar of apps, only the cards on the right.

Check the attached image, normally you can access everything shown in the picture. But as soon as I activate accessibility I cannot move the "cursor" over to the left (circled in blue).

I am 100% that Tasker is the problem, tested on two boxes, same thing.

When I first used it I thought that the time settings were a timeout not the check condition timing. Some method should be provided so that if the condition never becomes true the action can timeout with an error code.

• Using the Element Value action on a slider, with the scene visible, fails to activate the Value Selected event task. The documentation clearly states that changing the slider value with this action should activate the event task.
• The text for the indicators does not scale with screen resolution, making them practically useless. On my device they look like periods.
• There is no way to change the color or width of the line the thumb slides on. Sky blue isn't always the best choice.
• There is no obvious way to make a vertical slider.
• During touch movement, the slider value does not

At least on some devices the action "Play Ringtone" does not stop playing the ringtone until Tasker is disabled or quit.

The action "Play Music" is not always a good alternative because it changes %MTRACK which can be used to trigger music playing causing unwanted profiles to become active.

So an action to stop the ringtone playing would be necessary or the ringtone should stop playing by itself after one loop or a configurable time.

My profile called "TuneIn Radio" is activated when the app TuneIn Radio is open.

The linked task is set to de-activate my "Start Spotify" profile, so these 2 do not collide.

-

Tasker seems to only sense the TuneIn Radio app when it is in the foreground though.

If it's in the background, or if the screen is off. Then Tasker runs the exit task, which is to enable the Spotify profile again.

Just to have said it. My "Start Spotify" profile and the tasks which disables and enables this profile works fine. It's just the part of telling Tasker that the TuneIn

I'm referencing this:

https://tasker.helprace.com/i426-android-tv-oreo-accessibility-problems-with-tasker

and this

https://tasker.helprace.com/i245-android-tv-oreo-accessibility-problems

Your case for reverting the fix was that it messed with the UI of the Volume Up / Down Indicator. Which, is a good point. BUT - that's only inconvenient on mobile, not on Android TV (it still happens but it's not that inconvenient - though Aaron has a fix for that as well below). Turning Accessibility on for Android TV basically breaks the Homescreen and is not even usable making any accessibility features almost useless on any app.

BUT BUT BUT - here is the fix to that: https://cloudup.com/cnBPalSffz7

AND - you can

I use a local work profile provided by Shelter for apps I need sandboxed for whatever reason. Unfortunately those apps don't show up in the list of apps for enter/leave profiles and things like AutoNotification just list resultant effects with a blank associated app (still works fine via title/text match though).

Source reddit thread