• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Tasker 5.7.0 - Beta 3 through Beta 16

I was waiting on Beta and preparing to go to Beta 2 and Beta 3 was released. I went with Beta 3 on Android 6.0.1 and Android 8.0.0.

I have been using 4.9u4m on Android 7,0 for almost a year because of the problem with App Factory.

I can now successfully run …
Dev1
A1: Flash [ Text:- Dev1 - Long:Off ]
A2: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A3: System Lock
… from a Kid and it the Kid is authorized as a Device Administrator it immediately blanks the screen.

Under 5.6.5b on Android 8.0.0 every kid I created was marked as background and showed up in the background display. This has been corrected and they no longer appear there.

There were times wham many different Kids showed up in the background display and then changed. This would go on for about a minute and then settle down to the two tasks I knew should be in the background. I have not been able to zero in on and additional information yet.

… Thom
 
Went to sleep … checked 5 hours later … there were 13 tasks running in the background …
Cerberus
Tasker
11 Kids (some built with 5.6.5 and some with 5.7.0 Beta 3)​

I rebooted the system … now 7 hours later … did not run Tasker or any Kid … there are two tasks running in the background …
Cerberus
Tasker​

I always run a Kid that as created in 4.9u4m and it has never been listed as a task running in the background. I start this task with a Device Boot profile.

… Thom
 
Upvote 0
I tried to reproduce the problem of too many Kids being identified as running in the background and I was not able to reproduce it. This included monitoring it manually over an 8 hour period.

It now only identifies the two tasks I have running in the background. If Tasker is the active task it is not listed as a background task.

One curious thing … when I created a new Kid version it is identified as running in the background until I run it once. It is then no longer identified as in the background.

My guess is that the multiple Kids in the background issue was due to my environment and I did a Clear Cache of both Tasker and App Factory. I suggest it as a good practice for everyone.

… Thom
 
Upvote 0
It was suggested that I add Disable to each kid.

My testing to date … without Disable … all the kids are removed from the background list on exit and sometime after midnight they reappear. This was tested over two midnights. One kid that I created new never appears in the background list.

As a test I added Disable to 6 kids and not the others. After I pass the midnight threshold I will report if it solves the problem.

(The help description fir Disable appears to be describing a different kind of Disable.)

… Thom
 
Upvote 0
I am using Android 8.0.0.

(1)
I installed Beta 4 and created 12 Kids in the test. 7 Kids end with Dismiss. 5 Kids do not.

Under Beta 3 after creation all Kids are listed as running in the background until they are executed once.
Under Beta 4 after creation none of the Kids are listed as running in the background.

(2)
After 24 hours none of them appeared in the background list. Conclusion … Dismiss is not needed.

(3)
The one Kid I had in Beta 3 that never went into background now in Beta 4 always goes into background. The solution was to add the Disable action. That Kid is …

GetAmps (622)
A1: Java Function [ Return:mybatt Class Or Object:BatteryManager Function:new {BatteryManager} () Param: Param: Param: Param: Param: Param: Param: ]
A2: Java Function [ Return:%myamps Class Or Object:mybatt Function:getIntProperty {int} (int) Param:2 Param: Param: Param: Param: Param: Param: ]
A3: Flash [ Text:%myamps Long:On ]
A4: Disable

(4)
The Help displayed for Disable describes suspending Tasker and not suspending the task within Tasker.

… Thom
 
Last edited:
Upvote 0
Android 8.0.0 Tasker 5.7.0 Beta 5 The fixes I reported in Beta 4 are still true in Beta 5. After Beta 5 installation creating a Kid was odd … The first Kid was created in about the right amount of time. All Kids after that took about 2 min to
Android 8.0.0 Tasker 5.7.0 Beta 5

The fixes I reported in Beta 4 are still true in Beta 5.

After Beta 5 installation creating a Kid was odd …

The first Kid was created in about the right amount of time.
All Kids after that took about 2 min to build and then 2-3 min install. If I want away and did something else and came back the install would complete in a few seconds.

I did a power off/power on and they all build in 3-4 seconds and install in 3-4 seconds.

I removed the Disable in all but one Kid … they were not needed. That remaining Kid must have the Dismiss or it will always be listed as running in the background. (It is documented in an earlier post in this thread.)

… Thom
 
Last edited:
Upvote 0
Tasker 5.7.0 Beta 6 under Android 6.0.1 and 8.0.0

The Help screen for the Disable action is incorrect. It describes disabling Tasker and not disabling the Tasker task.

The time to create a Kid fluctuates. A simple Kid installed without change multipole times ...

Android 6.0.1 …
40 sec
23 sec
24 sec

Android 8.0.0 …
6 sec
80 sec
3 sec

… Thom
 
Last edited:
Upvote 0
Clarification of the Disable help screen report … the current help screen is ambiguous and the needed reset is incorrect.

What it currently says …
“Permanently turn off Tasker’s monitor and stop running tacks.
Tasker will not do anything further until enabled via the On/Off button in the Profile list screen.”

What it should say is something like …
“Turn off Tasker’s monitor and stop servicing Perform Task actions.
The Perform Task action will fail until three-dots/Enable Tasker is selected from the Profiles, Tasks, Scenes, or Vars screen.
Disabling the Tasker monitor is sometimes required in Kids created in Tasker App Factory to remove them from background processing. If the Disable action is executed in a Kid the Kid can then be run again without reenabling Tasker’s monitor. “

… Thom
 
Last edited:
Upvote 0
Android 8.0.0 …

An odd situation occurred yesterday that I have never seen before.

I have a number of Kids created with Beta 6 … many are very simple.

I invoke them from the home screen and when they run they terminate and I am back to the Home screen.

The odd thing that happened yesterday was that I invoked them and when they run the terminate and return to the previous app that was in the previous app list.

I did a power off/power on and they all returned to normal.

… Thom
 
Upvote 0
5.7.0 Beta 7 Android 8.0.0

The Disable help screen is incorrect.

What it currently says …

“Permanently turn off Tasker’s monitor and stop running tasks.

Tasker will not do anything further until enabled via the On/Off button in the Profile list screen.”

What it should say is something like …

“Turn off Tasker’s monitor and stop running Perform Task actions.

The Perform Task action will fail until three-dots/Enable Tasker is selected from the Profiles,

Tasks, Scenes, or Vars screen.

Disabling the Tasker monitor is sometimes required in Kids created in Tasker App Factory to remove them from background processing. If the Disable action is executed in a Kid the Kid can then be run again without reenabling Tasker’s monitor. “

If a Task is run within Tasker by a long press on the Task name and selecting the run icon … if Disable is included in the Task then Tasker IS NOT listed as Off at the top of the screen.

If a Task is run within Tasker by opening the Task and selecting the run icon … if Disable is included in the task then Tasker IS listed as Off at the top of the screen.

If a Kid containing a Task that is …
Perform Task
Disable
Flash
… when rerun it will execute all three actions.

… Thom
 
Upvote 0
I have never battery optimized any of my current devices.

The new Tip that was added says …
“important that Tasker is not battery optimized”
… and should say …
“important that the device Tasker running on is not battery optimized”

(Does this also include Kids or just Tasker Proper?)

The new Tip that was added on disabling battery optimizations … if you tap YES it takes you to a page that does not say anything about disabling battery optimization.

If the new Tip that was added is being displayed …if the screen times out … the tip is no longer displayed when the screen is back on.

… Thom
 
Upvote 0
Upvote 0
This was observed in Beta 3 through Beta 8. The time between the display Installing and the display App Installed varies.

Some installs of some simple Kids … normally wait 10s between each install …
3s
43s
44s
38s
3s
40s
39s
3s
37s
3s
45s
3s
40s

For each of those that took only 3s there was 60s after the previous install had completed.

… Thom
 
Upvote 0
Tasker 5.7.0 Beta 9 results …
  1. System Lock action run in a Kid still works. Thank you.
  2. Disable action help description is very misleading. For example, try Disable followed by Flash. The Flash is displayed.
  3. Task with Disable action run within Tasker by opening task and sleeting run … runs and Tasker Off is in upper left corner of screen.
  4. Task with Disable action run within Tasker by highlighting task name and selecting run … runs and Tasker off is not in upper left corner of screen.
  5. Task with Toggle Split Screen action runs correctly in Tasker and fails without comment if run in a Kid.
  6. The time to ins all a Kid still varies from 4sec to 45sec as reported in previous betas.
… Thom
 
Upvote 0
The change log for this one is just in the Play Store description.

- Handle errors when browsing url
- Don't ask to disable notification channel on Android < 8
- Fixed crash in main Tasker window
- If kid app don't show text in notification

About your issues, what about the help is misleading exactly?

What the Help in the Disable action currently says …

“Permanently turn off Tasker’s monitor and stop running tasks.

Tasker will not do anything further until enabled via the On/Off button in the Profile list screen.”

What it should say is something like …

“Turn off Tasker’s monitor and stop servicing Perform Task actions.

The Perform Task action will fail until three-dots/Enable Tasker is selected from the Profiles, Tasks, Scenes, or Vars screen.

Disabling the Tasker monitor is sometimes required in Kids created in Tasker App Factory to remove them from background processing. If the Disable action is executed in a Kid the Kid can then be run again without reenabling Tasker’s monitor. “

About 4, but is Tasker off after you do that? It's probably just missing a UI refresh.

Tasker is disabled and there is an option in the three dots to enable it. Itt would appear the screen was not refreshed after the task ended.

About 5, does the kid app have the accessibility service enabled?

It did not. When I enabled it it then worked from the Kid.

I suggest adding something to the help like …

“If using the Toggle Split Screen action from a Kid created by Tasker App Factory you must enable accessibility service for the Kid application.”

About 6, I don't control that :) That's up to Android and not related to Tasker at all...

This one is super weird.

… Thom
 
Upvote 0
Tasker 5.7.0 Beta 11 results …
  1. System Lock action run in a Kid still works. Thank you. (no change)
  2. Disable action help description is very misleading. For example, try Disable followed by Flash. The Flash is displayed. (no change)
  3. Task with Disable action run within Tasker by opening task and sleeting run … runs and Tasker Off is in upper left corner of screen. (no change)
  4. Task with Disable action run within Tasker by highlighting task name and selecting run … runs and Tasker off is not in upper left corner of screen. (no change)
  5. Task with Toggle Split Screen action runs correctly in Tasker and fails without comment if run in a Kid. (no change)
… Thom
 
Upvote 0
Tasker 5.7.0 Beta 12 was released ...
  • Updated Google Play Services libraries to latest versions
  • Fixed crash when choosing location on Android 9
  • When selecting a notification category in Notify action, only show user notifications
  • Make asking for profile name enabled by default
  • Show which permission is missing in flash message saying that no permission is given
… Thom
 
  • Like
Reactions: ocnbrze
Upvote 0
Tasker 5.7.0 Beta 12 results …
  1. System Lock action run in a Kid still works. Thank you. (no change)
  2. Disable action help description is very misleading. For example, try Disable followed by Flash. The Flash is displayed. (no change)
  3. Task with Disable action run within Tasker by opening task and sleeting run … runs and Tasker Off is in upper left corner of screen. (no change)
  4. Task with Disable action run within Tasker by highlighting task name and selecting run … runs and Tasker off is not in upper left corner of screen. (no change)
  5. Task with Toggle Split Screen action runs correctly in Tasker and fails without comment if run in a Kid. (no change)
… Thom
 
  • Like
Reactions: ocnbrze
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones