JRJ442 said:

I use Taskers built in Custom Settings. For Pixel and possibly most AOSP ROMs it's status_bar_clock. 1 to enable and 0 to disable. Some manufacturers and software may change the name for the status bar clock. You may have to do experiments to figure it out. Autotools has a nice way to figure out some custom settings too if you need help with them.

nickelnine said:

I'm also using custom settings to hide it with the help of AutoInput to detect when I'm on the home screen. Sorry if I wasn't clear, but I was asking how do you detect when you're on the home screen using AppContext in order to flip the value from 1 to 0 and back?

Here's the profile I use for you to check out. Actually I went back to using Taskers built in app trigger for the profile. Seems like sometimes App Context and the new EdXposed don't play nice together. It would stop working for me. Basically what I do is select the apps that I want the status bar clock to show in, enter task turns the clock on via custom settings, exit task turns it off. With that profile you can just select the apps you want it to show in.
https://taskernet.com/shares/?user=...48eVI7K2VB0199A==&id=Profile:Status+Bar+Clock

.:Addicted:. said:

AppContext also allows specific activity to ignore only & its not selectable. We have to manually find package name & activity name.

Regarding ignored activities, if you want to add one, you can select auto mode. Then you'll see an AppContext notification. If you open the specific activity you wish to ignore, and then tap AppContext's notification, it should be added to the ignore-list.

.:Addicted:. said:

It would be nice if we can use specific activity to trigger something in tasker.

This is a very good suggestion, and something I have been thinking about for a while! If I find the time, this will probably be one of the first things I work on.

kurci2 said:

Would it be possible to replicate functionality of this plugin with newly added Logcat function of Tasker?

I think Android's ActivityManager does print something to logcat whenever apps are opened and closed, so you might be able to act on those with Tasker's logcat functionality.

JayShortway said:

Good point. It is sort-of intended behavior, as AppContext simply checks whether the app's (or Activity's, actually) 'onStop' method is called. This method gets called when you turn the screen off. I might change this behavior in the future, or make it configurable. Until then, you could use the following workaround:

1. Profile: Event --> Plugin --> AppContext --> Start --> pick the apps you want to act on
   1. Variables --> Variable Set
      • Name: %appsRunning
2. Either: Clone the previous Profile, then go into Configuration --> Menu (3-dots) --> Configure context --> Stop
   Or: Profile: Event --> Plugin --> AppContext --> Stop --> pick the same apps
   1. Task --> Wait
      • MS: 500 (You can play with this number: smaller for a quicker response, bigger for more reliability detecting screen state.)
   2. Task --> If
      • Condition: %SCREEN equals on
   3. Variables --> Variable Set
      • Name: %appsRunning
   4. Task --> End If
3. Profile: State --> Variables --> Variable Value --> %appsRunning equals 1
   1. Perform your Actions here.

I hope this works for you (and others)!

And thanks a lot for the heads-up on the subReddit, that's actually a very good suggestion!

Click to expand...

cantenna said:

I tried this but [*]Profile: State --> Variables --> Variable Value --> %appsRunning equals 1 does not work despit Vars indicating %appsRunning eq 1

Seems this function of tasker is broken for me on Pie