OnePlus and Pixel devices are also experiencing this issue.

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.

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, profile catches this, %errormsg parsed, fix made, Task from %caller() ran again.

Thank you!

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.

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 to this: https://i.imgtc.com/PKYFbEb.gif

Currently the app already does this in some places.  For example, dragging a task over the garbage bin before dropping it will highlight the garbage bin icon, and dragging it over a project will highlight the project.  These are great!  They show the user where the item will land when they release their finger.

Unfortunately there is no visual indication of where an item will be dropped among a list when you drag and drop to reorder it.  This is especially problematic when dragging actions within a task, since tasks can involve many actions. Nested "if" "else" "end if" etc. statements in particular can be very confusing to get out of place.

Both of these problems exist while rearranging these items:

-Tasks

-Actions within a task

-Profiles

-Scenes

Thank you Joao!

Android version: 9

Tasker version: 5.2.bf1

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

06.47: eh: 47 <- 47,06.47: em: 47 -> 47,06.47: eh: 07 -> 7,06.47: expiry minutes: 47,06.47: expiry hours: 07

Profile: Volume Profile When Phone Shaken (81)
        Event: Shake [ Axis:Left-Right Sensitivity:Medium Duration:Medium ]
Enter: Start Volume Profile Scene (80)
        A1: Variable Set [ Name:%TIMED_VOLUME_PROFILE_DURATION_HOURS To:01 Recurse Variables:Off Do Maths:Off Append:Off ] 
        A2: Variable Set [ Name:%TIMED_VOLUME_PROFILE_DURATION_MINUTES To:00 Recurse Variables:Off Do Maths:Off Append:Off ] 
        A3: Show Scene [ Name:Volume Profile Display As:Activity Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Button:On Show Over Keyguard:On Continue Task Immediately:On ] 
        A4: Variable Set [ Name:%VOLUME_PROFILE_SCENE_ACTIVE To:true Recurse Variables:Off Do Maths:Off Append:Off ] 
        A5: Variable Set [ Name:%UPDATE_TIMED_VOLUME_PROFILE_WIDGET_TASK To:UpdateTimedVolumeProfileExpiryWidget Recurse Variables:Off Do Maths:Off Append:Off ] 
        A6: Perform Task [ Name:%UPDATE_TIMED_VOLUME_PROFILE_WIDGET_TASK Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop:Off ] 

Profile: Update Timed Volume Profile Widget (56)
        State: Task Running [ Name:Start Volume Profile Scene ]
Enter: UpdateTimedVolumeProfileWidget (57)
        
        A1: Anchor 
        A2: Perform Task [ Name:SecondsUntilNextMinute Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable:%seconds Stop:Off ] 
        A3: Wait [ MS:0 Seconds:%seconds Minutes:0 Hours:0 Days:0 ] 
        A4: If [ %VOLUME_PROFILE_SCENE_ACTIVE ~ true ]
        A5: Perform Task [ Name:Log Priority:%priority Parameter 1 (%par1):auto calling %UPDATE_TIMED_VOLUME_PROFILE_WIDGET_TASK Parameter 2 (%par2): Return Value Variable: Stop:Off ] 
        A6: Perform Task [ Name:%UPDATE_TIMED_VOLUME_PROFILE_WIDGET_TASK Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop:Off ] 
        A7: Goto [ Type:Action Label Number:1 Label:TOP ] 

Exit: Destroy Volume Profile Scene (85)
        Run Both Together
        A1: Variable Set [ Name:%VOLUME_PROFILE_SCENE_ACTIVE To:false Recurse Variables:Off Do Maths:Off Append:Off ] 
        A2: Destroy Scene [ Name:Volume Profile ] 

Location Mode action pre-Android 9:

+ Device Only = enables GPS
+ Battery Saving = enables WiFi + cell towers 
+ High Accuracy = enables GPS + WiFi + cell towers

Location Mode action on Android 9 (with "location accuracy" setting **disabled**):

+ Device Only = enables GPS 
+ Battery Saving = does nothing
+ High Accuracy = enables GPS

Location Mode action on Android 9 (with "location accuracy" setting **enabled**):

+ Device Only = enables GPS + WiFi + cell towers
+ Battery Saving = enables GPS + WiFi + cell towers
+ High Accuracy = enables GPS + WiFi + cell towers

---

Hence, on Android 9, I would expect the Location Mode action to: 

1.  Not show the option for "battery saving" since it's no longer possible to achieve. 
2. Toggle the "location accuracy" setting as needed. 

In other words, assuming location is off to begin with:

+ Device Only = enable location + disable "location accuracy" setting if enabled (equals GPS only)
+ Battery Saving = [don't show this option]
+ High Accuracy = enable location + enable "location accuracy" setting if disabled (equals GPS + WiFi + cell towers)

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

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.

My S20 has a feature called "Extra Dim" (to dim the display even more than the default minimum) which is identified by the Custom Setting "Find Setting" as (secure) "reduce_bright_colors_activated" with value 0 or 1.

I can ENABLE or DISABLE this specific setting without any problem using tasker, but surprisingly I cannot READ the current state, as Custom Setting doesn't return a value to the variable referred to by the "Read Setting To" setting (it returns the name of the variable, as usual when using uninitialized variables).

Furthermore while on finding this setting tasker informed me that it's possible to toggle the setting, the toggle doesn't work and throws an error msg in the error log, at a guess because it cannot toggle when it can't retrieve the actual state.

The peculiar thing is that the "find" mechanism on identifying the respective setting by manually changing the setting via android settings, is able to identify the name of the setting as well as the type of values it uses (0/ 1), so Tasker internally seems to be very well able to retrieve the values.

Btw: I do use Custom Settings for other settings like "Enhanced Processing" (Global sem_enhanced_cpu_responsiveness) and it works without any issues, I can ENABLE, DISABLE and READ current state just fine, so doesn't seem to be a general problem of Custom Settings.

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.

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.

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 Radio app is still running I'm having problems with.

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 conditionally only apply the fix to Android TV on Oreo because you can detect that.

So, this SOLVES all of the problems. What do you think?