AppContext [0.4.7.2] - Better application context for Tasker with Xposed! [4.0.3+]

Hi everyone!

After years of reading, flashing, and gaining a lot of Android-knowledge on XDA-Developers, I felt it was time to create my own Xposed Module.
So hereby I proudly present to you my first app:


With AppContext, you can have Tasker react on running applications, without the downsides of the default implementation.

The default application context of Tasker has several downsides:
• it is inaccurate (in Android versions after KitKat)
• it needs an accessibility service (which disables screen lock for enhanced data encryption, but this can be re-enabled)
• it checks frequently which app is running
Especially the last point is inconvenient, as frequent checks may drain battery and infrequent checks means Tasker is slow to react.

AppContext solves these problems by utilizing the power of Xposed! It hooks directly into the Activity-class, letting Tasker react immediately when an app starts. This means no more periodic checking which app is running, so no more battery drain and no more slow reactions. It's also perfectly accurate and doesn't need an accessibility service, so your device's screen lock can be used for enhanced data protection again.
(Experimental support for reacting on Services is also present.)

AppContext may also work with other apps using the Locale API, such as Locale, Llama, Automate, Automagic and others. However, this is not tested extensively.

To support development, AppContext contains non-intrusive ads. These can be removed with a small in-app purchase. (Note that if you donate through PayPal on XDA, ads are not removed. Nevertheless, it is still highly appreciated)

Please understand that AppContext is still considered to be in beta. There may be bugs. Please report them in this thread, or by using the in-app Feedback button or sending an email to shortwaystudio@gmail.com.
Constructive criticism is highly appreciated!

DOWNLOAD
• Google Play
• XDA Labs
• Xposed Module Repository



COMPATIBILITY
• Android 4.0.3 and higher
• Xposed Framework
• Tasker (or equivalent)

CREDITS
• Crafty Apps EU/Pent for creating Tasker
• rovo89 for creating the Xposed Framework
• Google Play and the Google Play logo are trademarks of Google Inc.

XDA:DevDB Information
AppContext, Xposed for all devices (see above for details)

Contributors
JayShortway
Xposed Package Name: io.shortway.appcontext

Version Information
Status: Beta
Current Beta Version: 0.4.7.2
Beta Release Date: 2018-07-09

Created 2017-06-17
Last Updated 2018-07-09

Changelog

0.4.7.2 (Announcement)
Please report any bugs in this thread, or by sending an email to shortwaystudio@gmail.com.

• [FEATURE] Added Chinese (Simplified) translation (thanks to @smailzhu).
• [FIX] Some fixes to the Chinese (Traditional) translation (thanks to @smailzhu).
• [FIX] Bug-fixes.

Known Issues

0.4.7.2

• Support for Services is still experimental, and is completely disabled by default.

Bladehawkz said:

Oneplus one, running CM13 (sultan's) with my own custom kernel.

Seems to be working fine!

Click to expand...

Click to collapse

Thanks for the feedback, good to hear

lover said:

Oneplus3t with magisk and systemless xposed, The App does not detect xposed is installed and module has been activated!

Click to expand...

Click to collapse

Thank you for letting me know! I've put it on the Known Issues list, and I'm working on it!

Zoltair Wright said:

FYI you can still use disk encryption password with accessibility services. when you enable the service it disables the 'require passcode on boot' but you can just re-enable from the security settings and it works

great module by the way! thanks

Click to expand...

Click to collapse

That's interesting! Very unclear communication from Android though. I'll add your info to the first post, thanks for letting me know!
(And glad you like the module. )

pjohn23 said:

Don't know if i posted this right but the message shown in "not running" state is the same as the running one in tasker. Shouldnt it say when "this app is not running" or something like that?

A great module and very reliable

Xperia Z running RR 5.7.4 with xposed v87 for MM

Click to expand...

Click to collapse

Yes you're right! Thanks for the info and the screenshot. It's supposed to say "is in the foreground" or "is not in the foreground", but I see that "is" and "is not" have disappeared. Will be fixed in the next update.
Good to hear the module is reliable!

Hi everyone,

The first update (0.3.1) is live! It is now available on Google Play, XDA Labs and the Xposed Module Repository.
It is just a quick bugfix update. It should fix the typo in the Tasker blurb, the crash when pressing 'back' in the 'Pick apps' screen and also enable Magisk systemless Xposed compatibility.

For those of you with Magisk: AppContext will probably complain it can't find the Xposed Framework, but if you enable the module and reboot, it should work (and AppContext stops complaining). I would be glad if someone could report back.
I will probably make a more elegant solution in a 0.4 update.

Please report any bugs in this thread, or by using the in-app Feedback button or sending an email to shortwaystudio@gmail.com. Thanks!

Enjoy!

Stupifier said:

Interesting Module. I always thought Tasker's app detection was a bit unreliable. Never thought it could be improved though. Thanks!

Wonder if Tasker Dev (Pent) will/can implement this as a "fix"

Click to expand...

Click to collapse

I'm glad you like it!
I don't think Tasker can implement this though, as AppContext hooks directly into Android-classes, which is only possible with Xposed.

richardkemp said:

Very nice! You should post it in http://www.reddit.com/r/Tasker too.

If I set an app context using your plugin, then navigate to the app and toggle the screen off and on, the profile deactivates and activates again. Is this deliberate? I'm actually not sure what the in-built app context's behaviour is. I found it confusing since in that case I haven't switched app, per se.

Click to expand...

Click to collapse

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
      • To: 1
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
      • To: 0
   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!

Bladehawkz said:

Suggestion: currently on lollipop+(I think), location toggle is unable to be used, even with root. The workaround is to use another plugin app with root/adb privs, but I was wondering whether this could be changed using xposed (changing the location hook?), as it should be visible to tasker that's been granted root).

Click to expand...

Click to collapse

Do you mean something like a Tasker-compatible Xposed module that toggles location modes?

Bladehawkz said:

More like editing tasker so that the location toggles work when it's granted root, instead of actually requiring you to download another app/plugin and granting that root.

Considering that Tasker is able to have root privileges granted, clearly it should be possible for it to toggle location.

Click to expand...

Click to collapse

Got it! It's a good point you make. However it would require either an Xposed module, or an actual adjustment/update to the Tasker app (by Pent). In case of the Xposed module, it would be interesting to see if and how this can be done.