[MOD][XPOSED] ActivityForceNewTask - Xposed Framework Modules

Introduction:
Apps can launch other apps' activities inside their task. This makes it impossible to switch back and forth between the two. This module sets the FLAG_ACTIVITY_NEW_TASK flag when starting a new activity, which 'fixes' that.
Originally requested by jacknicholson here.
Screenshots explanation:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Xposed Framework.
Filtering:
A quick toggle is available in the settings. Just check "Disable module" and the changes will take effect immediately. No need to restart.
You can use the blacklist or the whitelist to filter activities. If the blacklist is selected, all activities except those excluded will launch in a new task. If you use the whitelist, only matching activities will launch in a new task instead. The preferred way to add entries is through the log.
The activity components are output to the logcat. You can filter it for "activityforcenewtask componentString:" to see them. A line is logged for every started activity (you probably don't want to keep the log constantly turned on.)
A log viewer is also present in the app. You can press a log entry to directly add it to the currently active list. I'd advise you to only enable the log when needed.
Source code:
https://github.com/GermainZ/ActivityForceNewTask
Download:
http://repo.xposed.info/module/com.germainz.activityforcenewtask
Changelog:
2.1.3:
Compatibility with Lollipop.
Added Spanish translation and updated Portuguese (Brazil) and Slovak translations. Thanks to Jose Artuñedo, meatboy371 and ja-som.
2.1.1:
The blacklist/whitelist settings are now only reloaded when necessary. Shouldn't make a big difference unless you have huge lists.
4.4.3 fix: get the context using a different method (fixes logging on 4.4.3).
Added Portuguese (Br) translation by meatboy371.
2.0.3:
Only use context for logging;
Try to get the context in an alternate manner if the first one fails;
Bug fix: current package wasn't being detected properly;
Only start activities in a new task when the caller does not expect a result (different, more general implementation.)
2.0.2:
Reverted back to hooking ActivityRecord's constructor. Should solve the issue where some activities' launches weren't being detected.
Updated Slovak translation.
2.0:
Ignore activities that are launched by their own apps;
Added filtering options back. You can choose between the whitelist and the blacklist, but the no filtering option has been removed;
Added help dialogs for the whitelist/blacklist/log;
Bug fix: duplicate log entries when returning to the app with the log viewer open.
Other minor changes: use icons for action bar items, reorder preferences.
1.9:
Removed none/blacklist filtering options. The whitelist is always used now (renamed to "Enabled Components") which means that you must configure the module, as it won't do anything by default.
Reverted back to hooking Activity.startActivity(Intent, Bundle). Other methods used to start an Activity require the usage of FLAG_ACTIVITY_NEW_TASK, so it doesn't actually make sense to hook anything else. Also removed the alternate way to get a context as it shouldn't be needed anymore.
Check if FLAG_ACTIVITY_NEW_TASK is already set, and do nothing if that's the case (the activity won't be logged either.)
Updated Slovak translations (by ja-som.)
1.8.1:
Fix some crashes at startup;
Add FLAG_ACTIVITY_NEW_TASK flag instead of overwriting it. This fixes issues with XHalo and some apps showing in recents when they shouldn't;
Updated translations.
1.7:
Different hook, the previous one didn't catch all new activities.
1.6.1:
Removed unnecessary logging.
1.6:
Added whitelist.
1.5:
Added option to enable/disable the blacklist (and log.) The blacklist requires a few extra calls which are unnecessary if you don't use it, so I'd advise you don't enable it unless you need it.
Cleanup/better performance for the log viewer.
1.4:
The mod will now only modify intents that should be modified. This should fix all breakage without needing the blacklist. \o/
Log viewer improvements: tapping on an item now removes it from the list after adding it to the blacklist, and a toast is shown to indicate if it's been added to the blacklist.
1.3:
Use flat text file for storing the logs instead of SharedPreferences. This is much better for performance, especially if the log gets long.
1.2:
The blacklist is now for activities.
You can enable/disable logging from within the app.
Added log viewer to the app. You can tap a log entry to directly add it to the blacklist.
Fixes.
1.1:
Fixes for the two icons appearing in the launcher.
Disable text correction when adding a blacklist item.
1.0:
Initial release.
Click to expand...
Click to collapse
Thanks:
rovo89 and Tungstwenty for the Xposed Framework;
egingell for helping out with what to blacklist;
defim for advice on which intents to modify;
Ja_som for Slovak translation;
Sanguinus112 for German translation;
All testers.

Great idea, testing during the next days. So far only a cosmetic bug. After the installation of the module two icons appear in the launcher. Restart also did not change that.
Posting from the moon with Moto X and Tapatalk.

Update:
1.1:
Fixes for the two icons appearing in the launcher.
Disable text correction when adding a blacklist item.
Click to expand...
Click to collapse
Thomas_BA said:
Great idea, testing during the next days. So far only a cosmetic bug. After the installation of the module two icons appear in the launcher. Restart also did not change that.
Click to expand...
Click to collapse
Oops, fixed.

GermainZ said:
Thanks:
rovo89 for the Xposed Framework;
egingell for helping out with *what* to blacklist.
Click to expand...
Click to collapse
Thank you for trying to help me with my problem. I was looking at your SettingsHelper class and I think I need to start thinking of the Xposed side and Android side as separate apps and code it as such. But I'm too tired and achy to test right now.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

@GermainZ
To add to blacklist
Code:
com.android.internal.app.ResolverActivity
http://grepcode.com/file/repository...om/android/internal/app/ResolverActivity.java
If you want to be able to upload a picture through Tapatalk. I imagine there's a billion other uses to it. Might break module functionality in some cases? *shrugs*
NOT VALID ANYMORE

@GermainZ
Great idea. Would be nice if you clould find a way to detect apps which don't work and the blacklist could be removed

defim said:
@GermainZ
Great idea. Would be nice if you clould find a way to detect apps which don't work and the blacklist could be removed
Click to expand...
Click to collapse
I'm not really sure how that could be achieved. @[email protected]
The blacklist is good enough, but I feel like there's only going to be a handful of entries shared by specific people since people are morbidly afraid of logcat and I'm sure even more of filtering it.
Doesn't matter much in the end, I'm a happy user. Niche product for niche people?

polobunny said:
I'm not really sure how that could be achieved. @[email protected]
The blacklist is good enough, but I feel like there's only going to be a handful of entries shared by specific people since people are morbidly afraid of logcat and I'm sure even more of filtering it.
Doesn't matter much in the end, I'm a happy user. Niche product for niche people?
Click to expand...
Click to collapse
I can never get its built-in filter to work. I always have to resort to piping it through grep.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

egingell said:
I can never get its built-in filter to work. I always have to resort to piping it through grep.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Not sure where the issue lies, but that's usually what I use
ie:
adb logcat Xposed:V *:S
Show everything Xposed, hides everything else for instance. You can go fancy and do other things but if you're just looking to extract something real quick that will do.

Hi,
great idea, thanks.
regards
starbase64

polobunny said:
Not sure where the issue lies, but that's usually what I use
ie:
adb logcat Xposed:V *:S
Show everything Xposed, hides everything else for instance. You can go fancy and do other things but if you're just looking to extract something real quick that will do.
Click to expand...
Click to collapse
I do that, but it always seems to show everything anyway.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

EDIT: OUTDATED
Not sure if anyone else has been seeing a slight lag when selecting apps from Running Services, but blacklisting
Code:
com.android.settings.Settings$ManageApplicationsActivity
has solved it for me.

I got a bug report: If the launcher icon is hidden via your option you can't open the module from the module list because it says that your module doesn't have an UI. Reproducible.

theknut said:
But I got another bug: If the launcher icon is hidden via your option you can't open the module from the module list because it says that your module doesn't have an UI. Reproducible.
Click to expand...
Click to collapse
I can confirm this. I was able to get back in by using System Tuner Pro to re-enable the Activity named Preferences Alias.

EDIT: OUTDATED
Not a bug, but rather personal preference. If anyone's ROM settings ever open a separate package (eg. to pull up an additional settings page), and you don't want that cluttering up your Recents, add this:
Code:
com.android.settings.Settings

polobunny said:
@GermainZ
To add to blacklist
Code:
com.android.internal.app.ResolverActivity
http://grepcode.com/file/repository...om/android/internal/app/ResolverActivity.java
If you want to be able to upload a picture through Tapatalk. I imagine there's a billion other uses to it. Might break module functionality in some cases? *shrugs*
Click to expand...
Click to collapse
That'll basically nullify the module's effect when you don't have a default app set. (OUTDATED INFO)
defim said:
@GermainZ
Great idea. Would be nice if you clould find a way to detect apps which don't work and the blacklist could be removed
Click to expand...
Click to collapse
I can't find any reliable method
polobunny said:
The blacklist is good enough, but I feel like there's only going to be a handful of entries shared by specific people since people are morbidly afraid of logcat and I'm sure even more of filtering it.
Doesn't matter much in the end, I'm a happy user. Niche product for niche people?
Click to expand...
Click to collapse
I'm going to add a logger you can turn off and on when needed. Checking the logcat is better though because you sometimes need live input to decide (e.g. if an activity instantly launches another.)
theknut said:
But I got another bug: If the launcher icon is hidden via your option you can't open the module from the module list because it says that your module doesn't have an UI. Reproducible.
Click to expand...
Click to collapse
My fault, will be fixed in the next version.

GermainZ said:
That'll basically nullify the module's effect when you don't have a default app set.
Click to expand...
Click to collapse
Yeah that's what I thought too, because it grabs everything with a user choice. Still, Tapatalk is so weird it breaks on everything. @[email protected]

Someone tell me how to use it?

shibliaftab said:
Someone tell me how to use it?
Click to expand...
Click to collapse
Read the first post. Everything is explained very clearly, GermainZ made it clear. If you still don't understand then this module is not for you.
You'll need to know how to use logcat at minimum.

I can already feel this making life easier. Thanks Dev!

Related

[MOD][XPOSED] Phab7 v1.00 no-reboot UI Switcher

Phab7 is an on-the-fly UI switcher: select Phone, Phablet, or Tablet, then tap the Change button. The switch happens immediately - no reboot needed. A separate option lets you switch settings screen layouts (e.g. the Settings app) between Phone-style (separate screens for categories and details), and Tablet-style (categories and details, side-by-side).
Unlike other solutions, Phab7 has no effect on your apps beyond for their Settings screens. In particular, it will not alter the size or layout of your launcher's icons or dock (nor will it cause the tablet-style app-drawer icon to appear).
Note: Google removed Tablet mode from KitKat, so it is not available if you're running Android 4.4.x.
Installation
Important: if you have a beta version of Phab7 (v0.9x) currently installed, you must uninstall it before installing v1.0. Android will refuse to install it if one of the betas is present.
if you don't already have XposedInstaller on your system, see this thread
install Phab7.apk the same way you'd install any other sideloaded app
enable Phab7 by reopening the XposedInstaller app and selecting 'Modules'
tap directly on the checkbox next to Phab7, then back out and reboot
after the initial reboot, you can open the Phab7 app and change UIs as many times as you wish without further reboots
Notes
Tablet UI mode is only available when running ICS or JB (v4.03 thru 4.3x). While Phab7 supports KitKat, it does not add back the Tablet mode that Google has removed.
Whether Phab7 works on your device depends almost entirely on your ROM's creators. If they removed the graphics and layouts needed for a given UI mode, SystemUI.apk is guaranteed to force-close when you select that mode. A "Keep-Or-Cancel" dialog will automatically restore your settings after 12 seconds if this happens when you choose an incompatible UI mode. Clear the "Unfortunately" popup and you're good to go.
the Settings-layout feature takes effect when an app is first launched. To see its effect on running apps (e.g. the system's Settings app). tap the "Recents" button and swipe the app away , then reopen the app.
File
Phab7.apk - v1.00
Credits
barrmulio - the first to identify the system changes needed to implement alternate UIs
_TB_TB_ - author of TabletUI trigger who first realized that UI-switching could be done by an Xposed module
History
2014/01/22 - v1.00 - initial stable release
2014/01/05 - v0.99 - added keep-or-cancel dialog
2013/12/13 - v0.97 - added scaling for all modes
2013/12/10 - v0.96 - fixed KitKat-specific bug
2013/12/09 - v0.95 - added Tablet UI scaling
2013/11/30 - v0.92 - added support for KitKat
2013/11/27 - v0.90 - initial release
Gonna try it on S4 v4.3
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------
Ring of FC ;p
Sent from my GT-I9505 using XDA Premium 4 mobile app
Tried it, changes fine to tablet mode. Just a few layout issues. And the nav glow doesn't fade.
See screenshot.
Xperia Z running eXistenZ 4.10 rom.
Subscribed, this looks promising.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Z Beast
For me with android 4.1 only settings work and status bar and nav bar don t work
Sent from my LT26i using Tapatalk
Great job. tested working on CM10. status bar looks monster
it could have better you provided DPI settings along with phab7. though i can manage with app settings
the give attachment is flashable zip i just extracted phab7.apk and installed normally
why this is not available in xposed Repo..
reversegear said:
why this is not available in xposed Repo..
Click to expand...
Click to collapse
I think because it's new and in beta
Sent from Z Beast
Now we need not wait for updated Paranoid!! OK Paranoid does do some of this stuff better/more consistantly than AppSetting and this module, but ...
Great!
Wanna outdo Paranoid: Tablet mode mostly more usable in landscape, so ... get the idea?
EDIT: Results using the mod on my LG P500 running cm-10.2 with 4,4 Google Now launcher: I can use AppSetting module to force this launcher to rotate but it does not handle this correctly.
Settings UIs work as promised! This is what I really missed not having Paranoid.
Navigation bar: Question -- what if I do not use one (phone has HW buttons--remember those)? Module should accept phone setting.
Anyway, tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Went back to default: Icon bar, no navigation bar.
If I remember from Paranoid, tablet mode put notifications bar on the bottom right. Phablet left it on top, opening to half-height, had to change dpi to fit it to screen width correctly. So tablet mode, once working, would either have both at bottom right justified or just the notifications as chosen in the phone's settings! Someone check current Paranoid.
Compatible with KitKat?
Wysłane z mojego Ascend G510 przy użyciu Tapatalka
Don't flash that zip!
reversegear said:
the give attachment is flashable zip i just extracted phab7.apk and installed normally
Click to expand...
Click to collapse
OMG!!!! My apologies! The zip that was posted (in error) was only for the Hisense Sero 7 Pro and contained a tablet-specific mod to SystemUI.apk.
The script in that zip checks for the model, so it should have failed if you tried to flash it on any other device. However, if somehow you succeeded in flashing it, you will have to restore your ROM's original SystemUI.apk. The original, along with SystemUI.odex if present, is in your /system/app folder with '-org' appended to it. If you have problems handling this, I can create an update.zip to do this for you.
Again, my apologies - it was late...
This's amazing. Thanks a lot dev. Looking forward for new versions:laugh:
Saeedblack said:
For me with android 4.1 only settings work and status bar and nav bar don t work
Click to expand...
Click to collapse
Dovidhalevi said:
tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Click to expand...
Click to collapse
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings.
Setting default ui to phablet didn't help either.
Debug log: https://www.dropbox.com/s/zlp89tbus6o23qi/xposed_debug_20131127_194414.log
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
for me it have been FC for first run and after reboot it never appear again but don t have FC
also here you are i attached log that you notice
No TabletUI in KitKat
MMeester said:
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings. Setting default ui to phablet didn't help either.
N7(flo)-Rastakat-franco.kernel
Click to expand...
Click to collapse
Is this a KitKat-based ROM? Sadly, all of the code and resources needed to support Tablet UI have been stripped from Android v4.4. Because Phab7 v0.9 doesn't make provisions for this change, the UI switcher doesn't work. I will fix that ASAP so that at least Phone and Phablet are available. Restoring Tablet UI may be more than an Xposed module can/should do, but I'll investigate...
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Dovidhalevi said:
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
Click to expand...
Click to collapse
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
dolorespark said:
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
Click to expand...
Click to collapse
I first tried it before rebooting, then realized that it cannot work that way and rebooted. Then Phab7 worked as described.
Since wisdonsky operates on the notifications bar, could be that the interaction with tablet mode trying to move that is what is noted.
dolorespark said:
Is this a KitKat-based ROM?
Click to expand...
Click to collapse
Yes.
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Click to expand...
Click to collapse
Sadly, no change in settings app after a reboot. Do you need any logs?
Thank you for looking into the issue.
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Any help appreciated.
Metallijim said:
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Click to expand...
Click to collapse
Phab7 is designed to do as little as possible to achieve its goals - in some cases, perhaps too little. For Phone and Phablet, it does some setup when SysUI starts and that's it. For Tablet, it has to be slightly more intrusive but not much.
Sadly, I had no way to test compatibility mode so I'm not surprised that it has issues. Recovery from most any problem should be as simple as switching to another UI. In this case, getting out of TabletUI, then returning without touching the compatibility button should cure what ails you.
If you get repeated FCs in SystemUI, one way out is to leave the toast up there, then from ADB, delete /data/data/com.e_vertise.dopa.phab7/shared_prefs/settings.xml. When you dismiss the toast and SysUI restarts, you should be back to your device's default settings.
Note: if I understand things correctly, Android may try to reload SysUI's Java code several times using the same process before it gives up and kills that process. Once it restarts SystemUI using a new process, you're certain to be back to normal if you've deleted Phab7's settings file.
We'll soon find out if it works on KitKat. Yes I know how to disable Xposed from recovery. Using it on KitKat doesn't seem to cause any crashes, but it doesn't do anything at all on KitKat.
Sent from my Nexus 7 using Tapatalk 4

[Mod][Xposed] Alarm Clock Plus 2.0

There was a similar tweak for iOS back in the days when i was an iphone user which i was always missing on my Android device.
Now i just created it myself because i was bored yesterday :>
Do you enjoy snoozing in the morning as much as i do? Hate how you always have to look at your phone to determine if you can snooze
one more time or not?
This tweak tells you the time, everytime you snooze your alarm. Actually, it can tell you about anything.
You can set your own text and use a variety of variables. (Currently there are only a few. More might follow, if people like this tweak - for example unread mail count, weather, etc.)
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Compatibility:
I tested this tweak on a Nexus 5, running 4.4.2 Stock.
Alarm Clock Plus should be working on about any Device and any version of Android that has the stock Clock app.
(Please let me know if it works for you or if you have any issues, thanks)
This only works with the standard Google clock!
Package: com.google.android.deskclock | com.android.deskclock
Currently the Interface is still pretty raw and ugly.
I will work on that soon. Also I have some ideas for more features, which I'm going to implement over time.
Changelog:
1.0
Initial release
1.0.1
Small bugfix (disable dismissed now working)
1.1
added: Can hide icon from launcher
added: Auto save settings on exit
added: Voice speed control
added: Voice language selector
added some logging for debugging
possible fix of the TTS not firing
1.2
added: Support for CyanogenMod 11
(and possibly other roms that use the standard aosp clock app or derivates of it)
Thanks @pdcrzylazy for testing!
1.2.1
added: Support for Android 4.4.3+
(Let me know if this still works on 4.4.2 and lower please)
2.0
complete rewrite of the module.
it should be much more stable and reliable now.​
added: Tasker support (You asked for it and here it is!)
added: New Variables - %I (Hours 12h), %p (Am/Pm)
changed: Settings - No more need to reboot the device after changing settings
2.0.1
fixed: Test tasker-task on dismiss
fixed: Forgot to shut down the TTS engine
2.1
added: Check if your device/ROM is compatible
added: Check if you have TTS installed
added: Button to let you install more language files
reduced package size
2.1.1
fixed: Bug that broke the module on some devices
2.1.2
added: Option to remove leading zeros for the time and date variables
Click to expand...
Click to collapse
Download:
[QRCODE]http://repo.xposed.info/module/com.chrisxe.xposed.alarmtelltime[/QRCODE]
http://repo.xposed.info/module/com.chrisxe.xposed.alarmtelltime
If somehow you really like this tweak and want to support me, you can also buy this tweak from google play for little money
(This is the same version as the free one in the Xposed repo. It is just a donation package)
Alternatively you can click here to donate via paypal
Thanks to:
- rovo89 for the Xposed Framework.
- MohammadAG for all of his source codes on github.
Great idea. Like this very much. But unfortunately I'm using cyanogenmod 11 on my nexus 5.
And cm is not using the standard google clock. Is it possible that you can port this module to run also on devices with cyanogenmod?
Thank you.
Great potential...when it is ported to work with cyanogen I will definitely give it a try.
Sent from my LG-P936
thanks for the feedback. i'll try to look into it, to get it to work for cm
andreasf93 said:
Does it require internet to work? Because I tried it this morning and I snoozed it twice without hearing anything.
PS: Stock 4.4.3
Click to expand...
Click to collapse
have you tried to open the settings of the tweak and then hit the "save" button?
seems like for some people you need to do this first (im working on it!)
or maybe your locale isnt supported by text-to-speech. currently the tweak uses the default locale which is set by the system (i'll add a switcher to set a custom locale soon)
andreasf93 said:
My locale is English (UK) so it should be fine. When I press the Test button the voice is just fine. And yes I've pressed the Save button multiple times, still not working.
PS: Are you Greek?
Click to expand...
Click to collapse
it should work just fine then. are you using the standard aosp clock from google? (com.google.android.deskclock)
PS: no i'm not
andreasf93 said:
Oh okay, because Mythos is a Greek word
Yep, I have the default clock since I bought my Nexus 5 and did not install any other alarm apps :s
Just tried rebooting, reinstalling the app, still did not work
Click to expand...
Click to collapse
can you try to set an alarm and watch your logcat for errors when you hit the snooze button?
or maybe check the log in xposed installer
__EDIT:
oh and you did enabled the module, right? sorry, im not assuming you are dumb, just making sure
andreasf93 said:
Ye I have enabled it, I checked myself twice to make sure
Nothing shows up in xposed log, not sure how to check logcat though.
Click to expand...
Click to collapse
mhm. then im out of ideas for now, sorry ;(
maybe it is not 4.4.3 compatible. i dont know if the clock app changed or anything else xposed related.
i'll look into it
Another possible feature that you might look into -
Announcing the time on request (say, when I press the volume button) - BEFORE the alarm goes off. When I'm half asleep in the morning and not sure whether it is time to wake up, I want to be able to press the volume key and hear what time it is. I was trying to do it via tasker this weekend but didn't quite achieve what I was looking for.
So, if you can implement something to this effect in your module, that would be awesome.
Is not work on my galaxy s5
Sent from my SM-G900F using XDA Premium 4 mobile app
Please check the first post, I updated the module.
Changelog also in first post. Might have fixed the bug andreasf93 was experiencing
(Please let me know if it works now (Encountered the same bug as you, another reboot seemed to fix it for me))
@bagarwa
very good idea!
I'll probably implement that soon
Not sure if their name is copyrighted, but you may wanna change the name of this:
https://play.google.com/store/apps/details?id=com.vp.alarmClockPlusDock
Would hate to see a wonderful developer get a lawsuit! How about "Alarm Clock ADVANCED"
can you add option to turn off/on all the alarms that are setted ?
super charge for clock
It doesn't work on my GS4 on stock GPE 4.4.2. Voice is heard when press test buttons but when alarm goes off.. Snooze our cancel alarm didn't produce any sound.
Any ideas?
MythosXe said:
Please check the first post, I updated the module.
Changelog also in first post. Might have fixed the bug andreasf93 was experiencing
(Please let me know if it works now (Encountered the same bug as you, another reboot seemed to fix it for me))
@bagarwa
very good idea!
I'll probably implement that soon
Click to expand...
Click to collapse
Suggestion: an option to perform a tasker task when alarm is snoozed/dismissed would be awesome!
Will be useful for news, custom text, unread messages/emails/whatsapp messages, opening custom apps, etc
Would absolutely love this, thanks!
Great idea and very cool module! Working good on my Galaxy S4 running 4.3.
- Sent from my Galaxy S4 using the XDA app.
also rocking cm 11, this clock seems interesting tough. Would definitely try it if you came around to making it available to cm roms.
Can someone on CM 11 test if this one is working? (see attachment)
If it doesnt work first try, can you reboot a second time and try again? thanks :>
MythosXe said:
Can someone on CM 11 test if this one is working? (see attachment)
If it doesnt work first try, can you reboot a second time and try again? thanks :>
Click to expand...
Click to collapse
I'm running CM11. I installed the test APK and used the Test functions in the app interface. Those are working. Tested the clock app and the voice worked when I snoozed the alarm. Seems successful on CM11. Nice job.
pdcrzylazy said:
I'm running CM11. I installed the test APK and used the Test functions in the app interface. Those are working. Tested the clock app and the voice worked when I snoozed the alarm. Seems successful on CM11. Nice job.
Click to expand...
Click to collapse
Thanks for testing :>

[MOD][Xposed] Notification Count

Requires Xposed Framework by rovo89. Special thanks to him!
Notification Count badge for all Android versions
Shows a notification count badge on StatusBar icons providing a quantity.
Makes this badge customizable and extendable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This module adds a badge with a number next to notification icons, when the notification has a quantity (e.g. messages).
This is a built-in Android functionality, this module works as enabler for this function.
See Xposed Repo information for details about the current features of the module.
Download
You can download this mod from the Xposed Repo official website:
http://repo.xposed.info/module/com.woalk.apps.xposed.notifcount
Alternatively, there is always an APK on GitHub tied to a release tag.
But for Download counting purposes, I would ask you to use the Xposed Repo if it's no problem for you.
Have fun with the module!
Bug reporting:
IMPORTANT. Please read.
Please do not report bugs like "Hey noob-dev, it doesn't work, bye.".
Always attach at least your Xposed log to an error report.
Also, additional information can never be bad. Android version, Xposed version, device/ROM; exact behavior when the error occurs (e.g. "No number badge is shown, on no notifications, neither on the debug notifications nor on any app's.").
This will make fixing easier, faster and better to understand for everybody in the thread maybe having the same issue.
Thank you.
Changelog:
Version 3.2
Fixed some Xposed errors on Marshmallow.
Added secure lockscreen count.
Version 3.1
New app list engine.
RAM management should be better.
Loading time is a lot faster.
The list is searchable.
Switch to Material design on older devices, too; smaller UI changes.
Added "Extract number from notification content".
Fixed system integration on HTC Sense Lollipop devices.
Added possibility to change alpha value of number badges.
Version 3.0
You can now adjust the notification badge style freely (color, size).
You can now change the behavior of the 'Exception list' from blacklist to whitelist (again).
The Notification Count settings can now be integrated into Android's notification long-click menu.
Version 2.0
Cancel test notifications before sending new ones, to apply appearance changes faster.
Added Russian language (partially). Thanks GitHub user GromozavrStas.
Added `auto-decide` feature:
Automatically choose which way to use to fetch a number from a notification that does not provide a value by itself.
Use either the title, summary or update count for this purpose.
Some apps that cause problems can be forced to use a specific way of the available ones.
UI updates to fit those needs.
Version 1.1.1-re
Fixed bug that only let save whitelist items currently visible on screen.
Version 1.1-re
Added ability to hide launcher icon.
New 'workaround' mode: Extract number from notification description.
This new mode only works on KitKat and later for now.
Only enable this for apps that provide a notification number in their notification's small description!
Version 1.0-re
Restart of version numbering.
Initial version.
Main changes against the old module:
- Added support for Lollipop.
- Added ability to customize number badge.
See https://github.com/woalk/NotifCount/releases/tag/v1.0-re for full version changes against the old module.
See the git tag description of this release (can be found under https://github.com/woalk/NotifCount/tags) for programmer-related changelog.​
Author & Copyright Information
This module was first developed by GitHub user bbukowski.
His version was not updated since August 2014, and did not work on Lollipop.
I forked his repo and added my changes.
I added a pull request for my changes and will let him keep the 'right' ownership about this module if he wants to.
Look for README.md in my GitHub repo of this module for more information.
XDA:DevDB Information
Notification Count, Xposed for all devices (see above for details)
Contributors
Woalk, bbukowski
Source Code: https://github.com/woalk/NotifCount
Xposed Package Name: com.woalk.apps.xposed.notifcount
Version Information
Status: Stable
Current Stable Version: v3.2
Stable Release Date: 2016-05-31
Created 2015-05-06
Last Updated 2016-06-02
Working very well on JB 4.3, good job[emoji122] [emoji122]
Works with Android 5.11 CM12.1?
HGT - S5 G900F - Oneplus One - Tesla TTL7
KuaQ said:
Working very well on JB 4.3, good job[emoji122] [emoji122]
Click to expand...
Click to collapse
I'm happy that you're happy.
HorstiG said:
Works with Android 5.11 CM12.1?
Click to expand...
Click to collapse
Doesn't CM have this feature out-of-the-box?
But, yes, it should. Even while it may need you to enable the feature in CM settings (setting preference Settings.System.STATUS_BAR_NOTIF_COUNT, if I'm not completely wrong).
Just try it out.
this is a nice module.. thx..
a few suggestions..
- is it possible to enable new options (currently the display style) on the fly instead of rebooting?
- for the option styles, would be nice if a combination of styles (transparent+small) is allowed..
- for the option styles, customisable colour would be nice..
iamelton said:
this is a nice module.. thx..
a few suggestions..
- is it possible to enable new options (currently the display style) on the fly instead of rebooting?
- for the option styles, would be nice if a combination of styles (transparent+small) is allowed..
- for the option styles, customisable colour would be nice..
Click to expand...
Click to collapse
Yes, display style applies for every new notification instantly after selecting.
It does however not apply for already present notifications.
You can test this out with the 'Debug' options: Create any notification with a number, change number appearance, then swipe away your notification and select the option "without number" to force creation of a new notification.
After that, you can either use "with" or "without number" again to test the new style.
If it applies to a specific app depends on whether the app stores the existing notification for re-use or creates a new one.
Suggestions noted, I feared that they would be requested.
Will work on that soon.
and maybe also an option to hide the launcher icon, as i usually use xposed installer to manage all those modules?
Doesn't work on my Nexus 5 with stock 5.0.1
iamelton said:
and maybe also an option to hide the launcher icon, as i usually use xposed installer to manage all those modules?
Click to expand...
Click to collapse
Yes, on GitHub already, will be in the next release.
reallyimjesus said:
Doesn't work on my Nexus 5 with stock 5.0.1
Click to expand...
Click to collapse
That's a shame... Xposed log?
Thank you for this module only problem is that Whatsapp notifications constantly increment without having incoming new messages running CM12.
Sent from my LG-D415 using XDA Free mobile app
DallasBelt said:
Thank you for this module only problem is that Whatsapp notifications constantly increment without having incoming new messages running CM12.
Click to expand...
Click to collapse
That's interesting. Will look into it today.
WhatsApp is using the 'workaround', isn't it?
Woalk said:
Yes, on GitHub already, will be in the next release.
That's a shame... Xposed log?
Click to expand...
Click to collapse
I am sorry for the trouble! I was having the older Notification Count module active instead of this one (the old one DID not work; but this one does yaaay!!). Silly me... :silly: Sorry again!
reallyimjesus said:
I am sorry for the trouble! I was having the older Notification Count module active instead of this one (the old one DID not work; but this one does yaaay!!). Silly me... :silly: Sorry again!
Click to expand...
Click to collapse
Ah, that's a relief. No problem, it works, and this counts.
New version 1.1
A new version is available on Xposed Repo!
Changes are the ability to hide the launcher icon (requested by @iamelton)
and a new kind of 'workaround' mode, where the number of the notification is extracted from a string in the notification usually containing its number.
This may be a fix for WhatsApp (reported), try it out @DallasBelt, as I don't use WhatsApp that much.
The style suggestions will be added later, don't worry.
Have fun.
Woalk said:
A new version is available on Xposed Repo!
Changes are the ability to hide the launcher icon (requested by @iamelton)
and a new kind of 'workaround' mode, where the number of the notification is extracted from a string in the notification usually containing its number.
This may be a fix for WhatsApp (reported), try it out @DallasBelt, as I don't use WhatsApp that much.
The style suggestions will be added later, don't worry.
Have fun.
Click to expand...
Click to collapse
Nice! A little review:
It would be nice if it also searched for number of notifications in the title of the notifications (example: google play: N apps updated).
The "whitelist" section is necessary? Couldn't the app just first try to find a number normally, and then if no number is found switch to any of those methods, until it finds any? Like this.
(Notification on the text for some app appears)
1) Check for the number in the notification number count. Nothing found -> switch to 2)
2) Check for the number in the notification title. Not found -> switch to 3)
3) Check for the number in the notification text. Found (only if not found switch to 4)
4) Count updates
Some apps could have wrong info, so the app still should have some "exceptions" list for rare cases like whatsapp, but not a global whitelist for like 90% of the apps I think.
Thad't be awesome!!
Also, the count style only changes if you dismiss the notification, why? couldn't you make it that when generating one test notification you first close the other one? so this would be done automatically. Right now it closes too but the new style isn't applied..
Edit: I just tested increasing the test notification until >999 (yes I spent some time hah). Why >999 and not 1xxx? In small numbers it can be there lol. Also the > is half broken lol
Thanks a lot! :good::good: Keep up the nice work.
RusherDude said:
Nice! A little review:
It would be nice if it also searched for number of notifications in the title of the notifications (example: google play: N apps updated).
The "whitelist" section is necessary? Couldn't the app just first try to find a number normally, and then if no number is found switch to any of those methods, until it finds any? Like this.
(Notification on the text for some app appears)
1) Check for the number in the notification number count. Nothing found -> switch to 2)
2) Check for the number in the notification title. Not found -> switch to 3)
3) Check for the number in the notification text. Found (only if not found switch to 4)
4) Count updates
Some apps could have wrong info, so the app still should have some "exceptions" list for rare cases like whatsapp, but not a global whitelist for like 90% of the apps I think.
Thad't be awesome!!
Also, the count style only changes if you dismiss the notification, why? couldn't you make it that when generating one test notification you first close the other one? so this would be done automatically. Right now it closes too but the new style isn't applied..
Thanks a lot! :good::good: Keep up the nice work.
Click to expand...
Click to collapse
Number in title: Yes, right, that should also be an option. I somehow missed that out...
Whitelist: At the first thought I would say it is necessary, because really every notification would get a number without... But maybe this isn't even bad, as you say. Needs to be tested how it acts in real use. I will try it out.
Style applying on-the-fly: At least for the 'Without number' notification it's obviously needed that the notification updates instead of creates itself newly. But right, the 'With number' should be totally ok with creating a new one. If it makes you happy to see the style change with two touches less on the screen...
Applying the style completely on-the-fly, i.e. not only for the test notifications but for all app's, would be a bit more complicated. Maybe it will be implemented when I implement 'real' custom styles as requested in the thread, have to see how this will act on performance.
Thank you very much for your suggestions!
This is constructive feedback I'd like to see more on the internet.
Woalk said:
Number in title: Yes, right, that should also be an option. I somehow missed that out...
Whitelist: At the first thought I would say it is necessary, because really every notification would get a number without... But maybe this isn't even bad, as you say. Needs to be tested how it acts in real use. I will try it out.
Style applying on-the-fly: At least for the 'Without number' notification it's obviously needed that the notification updates instead of creates itself newly. But right, the 'With number' should be totally ok with creating a new one. If it makes you happy to see the style change with two touches less on the screen...
Applying the style completely on-the-fly, i.e. not only for the test notifications but for all app's, would be a bit more complicated. Maybe it will be implemented when I implement 'real' custom styles as requested in the thread, have to see how this will act on performance.
Thank you very much for your suggestions!
This is constructive feedback I'd like to see more on the internet.
Click to expand...
Click to collapse
Awesome
Constructive feedback? A lot of devs hate me cause I spam too much suggestions :laugh::laugh:
PS: You didn't notice the >999 issue tho :laugh:
Will it work on Xposed Super Alpha?
I'm using Moto G GPe 5.1 stock.
RusherDude said:
Awesome
PS: You didn't answer the >999 issue tho :laugh:
Click to expand...
Click to collapse
You didn't say anything about that...
Does it behave strangely then, like I would think now?
That would not be my fault, the basic implementation of the numbers are by Android itself... ?
But I'll see if I can get around them and replace it like "99+".
Phew, a big To-Do list growth for one day.
Umer520 said:
Will it work on Xposed Super Alpha?
I'm using Moto G GPe 5.1 stock.
Click to expand...
Click to collapse
I don't know, as I can't test Xposed for 5+ in an emulator (arm-only) and I don't have a developer device running 5.1 currently. Maybe I'll try installing the newest CM in the next days or week..
If you're ready to take the risk — as you are, because you installed Super Alpha — you can try for yourself, I would be curious how it does.
Woalk said:
You didn't say anything about that...
Does it behave strangely then, like I would think now?
That would not be my fault, the basic implementation of the numbers are by Android itself... ��
But I'll see if I can get around them and replace it like "99+".
Phew, a big To-Do list growth for one day.
Click to expand...
Click to collapse
I did hehe:
Edit: I just tested increasing the test notification until >999 (yes I spent some time hah). Why >999 and not 1xxx? In small numbers it can be there lol. Also the > is half broken lol
Click to expand...
Click to collapse
But I think u were replying already so missed it , like my edit on the previous post haha :laugh:
Do not reduce the number of digits! at least 3 is necessary lol, but ending in + instead of the > is better yea

[MOD][4.0+][XPOSED][WhatsAPP] WhatsApp Extensions - Add extra features to WhatsApp.

WhatsApp Extensions is a Xposed module which adds additional features to standard whatsApp application.
This module is much similar to WhatsAppX module.
Features include:
Option to directly call over phone.
Lock facility to individual chats.
Reminder - Reminds you to reply to a contact.
Highlight Chats.
Per contact custom wallpaper.
Permanently archive chats.
Hide last seen.
Hide read receipts.
Hide delivery reports. ( Unstable. See bugs section )
Hide Camera Button from bottom bar.
Zoom profile photo.
Replace call button ( works only for supported languages )
Click messages to reply/forward/see info
Get stats about messages ( per chat ) - github like implementation of monthly activity
More to come.
Click to expand...
Click to collapse
Bugs:
If your internet connection is off and someone sends you messages. after connecting to internet delivery reports will be sent.
If you experience delay in messages enable delivery reports - turn off option in module.
black ticks and hide tabs options will no longer work because whatsapp changed something in their code from v 2.17.x. There could be a solution but not known.
Click to expand...
Click to collapse
FAQ:
see this post
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use:
- To unarchive personal chats you need to first unhide it from menu then long press the chat, click unarchive button from top WhatsApp bar.
- You need to restart WhatsApp once you unhighlight a chat to avoid unwanted effects.
check out this video by @ashokmor007
Download links:
Read FAQs before downloading.
http://repo.xposed.info/module/com.suraj.waext
if you find this module useful please Donate to me
If you are willing to contribute:
Source code:
https://github.com/suraj0208/WhatsappExtensions
Please mention credits and give source code link if you use my code anywhere.
Libraries used:
https://github.com/martin-stone/hsv-alpha-color-picker-android
https://github.com/jdamcd/android-crop
https://github.com/chrisbanes/PhotoView
Thanks to:
Code:
rovo89 for Xposed frameword
BreitbandModem for original WhatsAppX module
All who supported this module
Everyone I forgot
Thanks for translating:
Code:
Portuguese - killer7Mod
Spanish- omoiyume
German - MDXDave
Italian - nevernat_theoriginal
Dutch - fnotsje
Turkish - edorewiel
Changelog 5.5
Hiding status tab is optional
Replace blue ticks with black
call button from menu is not aesthetically pleasing
replace call button works on only english language I dont have translations from other languages.
Stats implementation ( beta ) works best when you have 20+ messages for chat. Does not consider past data for now.
everything I forgot.
Note:
if you see frequent toasts like 'unable to uodate privacy setting' after enabling hide status, enable hide toasts. It will disable all toasts. WhatsApp has implemented very few toasts so it wont affect you much.
Click to expand...
Click to collapse
Changelog v5.0
Custom contact picker - Blacklist/Whitelist a group
Lock Archived Chats
Asking for password when critical preference needs changes
Send Read Receipts during chat session
Hide message preview for locked contacts
Fixed - Chat not opening from notification for locked contacts
Fixed - Exception while opening profile photo
Fixed - margins in Main Activity of module
compiled using latest sdk 25
Writing error to log while database reading
Minor performance improvements
Click to expand...
Click to collapse
Changelog v4.6
Blacklist/Whitelist contacts for Read Receipts
Fixed removing contacts from list
Lock for WhatsApp web is optional
Hiding notifications from locked contacts is optional
Removed black ticks option for now
Click to expand...
Click to collapse
Changelog v4.5
Always online feature - You'll be seen as online until you clear WhatsApp from recent Apps
GBWhatsapp profile photo bug may be fixed.
Lock added for WhatsApp web - if you have at least one contact locked you need password to open WhatsApp web
Read Receipts whitelist - allows specific contacts to see Read Receipts
Notification are hidden for locked contacts
Reduced logs
Added Turkish translations - thanks to edorewiel
Click to expand...
Click to collapse
Changelog v4.1
Fixed always 'online' bug ( you were always shown 'online' unless you clear WhatsApp from recent apps )
Dutch language support ( thanks to fnotsje )
Click to expand...
Click to collapse
Changelog v4.0
Click messages to reply/forward/see info
Hide delivery reports - only single tick will be shown ( only works on whatsapp 2.16.310. see bugs section in OP )
German language support - thanks to MDXDave
Italian language support - thanks to nevernat_theoriginal
Click to expand...
Click to collapse
Changelog v3.6
Spanish language support ( thanks to omoiyume )
Click to expand...
Click to collapse
Changelog v3.5
replace call button
hide tabs
hide blue ticks ( only double ticks will be shown )
Portuguese language support ( thanks to killer7Mod )
Click to expand...
Click to collapse
Changelog v3.0
Hide Camera Button from bottom bar. ( Experimental )
Zoom profile photo.
Improved UI of module.
Improved highlighted group UI.
Click to expand...
Click to collapse
Changelog v2.7
- Permanent archive feature is no longer version dependent ( will work on beta ).
( Now finding the class and field name at runtime )
- Support for pre lollipop devices.
Click to expand...
Click to collapse
Changelog v2.6
- Separate color for individual chats.
Click to expand...
Click to collapse
Changelog v2.5
- Permanent archive feature for personal chats.
- Highlight feature for individual chats. (Access from menu -> more -> highlight)
Click to expand...
Click to collapse
Changelog v2.2
- Hide last seen - experimental feature ( still see others' )
Enable it from main app.
Click to expand...
Click to collapse
Changelog v2.1
- ClassNotFoundError handled.
Click to expand...
Click to collapse
Changelog v2.0
- Added feature to permanently archive groups - access from group - >menu->hide. ( You need latest whatsapp with latest module version for this to work, that means with every new WhatsApp version you need to update module also)
- Highlight groups layout bug fixed - now setting proper margins.
- Lock feature improved. - now hooked onPause of Activity.class.
Click to expand...
Click to collapse
Changelog v1.5
-Added per contact wallpaper feature - access via menu -> more -> Custom Wallpaper
give proper permissions to access storage otherwise it wont work.
- Several performance improvements - Now caching views better performance when you use highlight group feature.
Click to expand...
Click to collapse
Changelog v1.2
-Timeout settings changed - Locks after you exit WhatsApp.
-Added Highlight group feature.
Click to expand...
Click to collapse
...
FAQ
Some chats are not highlighted How do I fix this ?
Those facing issue when particular chat is not highlighted,
edit that contact and add your country code to the contact ( for ex: +91 for India ). This is workaround until the issue is fixed.
Thanks @NightRaven49 for reporting and testing the solution.
Changing delivery report setting has no effect is this a bug ?
you need to open whatsapp once for delivery report setting changes to take effect.
I see frequent toasts like 'unable to uodate privacy setting..' after enabling hide status
Enable hide toasts. It will disable all toasts. WhatsApp has implemented very few toasts so it wont affect you much.
After trying to add contact to blacklist it is not actually added
please read this post
http://forum.xda-developers.com/showpost.php?p=70286351&postcount=581
Why WhatsApp asks superuser permissions after installing module or why the module itself needs superuser
please read these posts
http://forum.xda-developers.com/showpost.php?p=70290016&postcount=592
https://forum.xda-developers.com/showpost.php?p=70983415&postcount=786
I cannot remove contacts from blacklist/whitelist
see this post
https://forum.xda-developers.com/showpost.php?p=70347841&postcount=628
How to translate special strings ?
there are currently one string and one string array you need to watch out for.
First one is "menuitem_call"
Procedure: Select your target language on phone. Long press on whatsapp call button. A toast will appear. Translate the string to whatever message appears in the toast. Important thing is to make first letter lower case.
Second one is "oneclickactions"
Procedure: Same as above. You have to long press Reply, Info, Forward, buttons and put whatever comes in the toast.Do not make first letter lower case here.
Friend can suggest an interesting feature? He would not work a lot with Xposed, it would be with the root itself. In the case would merge the current database with an old backup. For example you have a conversation with someone and formats the phone and install WhatsApp again without backing up, then you again talk with the person, able to merge the new conversation with the old would be very good, and can restore already deleted conversations of a backup/old database
And other, I think this would be more for the Xposed: the module save each image/audio/voice note/call each person in a folder with your number. I like to save pictures of friends who sent me (I have until 2014) and it would be very good a module that automatically organize all
Works on x86 and GBWhatsApp?
Sent from my ASUS_Z00AD using Tapatalk
Ferreira_F10 said:
Works on x86 and GBWhatsApp?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I think it should. It is designed for WhatsApp_2.16.225 and working perfectly. Give it a try.
It looks promising! How long do you think it'll take before you can implement a "hide last seen" switch without the 24 hour limitation?
ThimoH said:
It looks promising! How long do you think it'll take before you can implement a "hide last seen" switch without the 24 hour limitation?
Click to expand...
Click to collapse
can you explain what exactly do you want ?
Dev thanks so much for this promising app. Work great at advertise. Pls can u add contact color highlight and hide last seen. Jst like whatsappx.
Feature request are welcomed. I'm also learning xposed framework. I'll try my best to implement them.
IMPORTANT: Please update to latest version. The bug in call buttons is fixed.
Surajkumar said:
Feature request are welcomed. I'm also learning xposed framework. I'll try my best to implement them.
IMPORTANT: Please update to latest version. The bug in call buttons is fixed.
Click to expand...
Click to collapse
So you're considering what I suggested? If yes, thank you!
per chat background wallpaper please :crying:
Thank you very much for your work! I hope you can add per chat wallpaper feature soon
Súper thanks. [emoji1] [emoji1] [emoji1] [emoji1]
Enviado desde mi XT1563 mediante Tapatalk
Surajkumar said:
I think it should. It is designed for WhatsApp_2.16.225 and working perfectly. Give it a try.
Click to expand...
Click to collapse
Not working on GBWhatsApp, I think it's only working on official WhatsApp
Enviado de meu ASUS_Z00AD usando Tapatalk
Per contact wallpaper and lock confirmed?
What about fingerprint per contact lock?
Edit:
Tested it and so far really good. The only thing left with the contact lock is every time I use immediately lock, when opening a picture I have to reinsert the password. The 1 min timeout is nice, but what about a timeout + lock when leaving the app itself.
Currently it interferes with whatsappx features, thus I can not use it (it works, but the whatsappx section is gone)
Features I would love to see:
Timeout + lock when leaving the app
Fingerprint lock, pattern lock
Per contact wallpaper
Sent and received messages counter
Keep up the good work dev!
Sent from my OnePlus 2 using Tapatalk
FPSUsername said:
Per contact wallpaper and lock confirmed?
What about fingerprint per contact lock?
Edit:
Tested it and so far really good. The only thing left with the contact lock is every time I use immediately lock, when opening a picture I have to reinsert the password. The 1 min timeout is nice, but what about a timeout + lock when leaving the app itself.
Currently it interferes with whatsappx features, thus I can not use it (it works, but the whatsappx section is gone)
Features I would love to see:
Timeout + lock when leaving the app
Fingerprint lock, pattern lock
Per contact wallpaper
Sent and received messages counter
Keep up the good work dev!
Sent from my OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
Feature request: Highlight chats. That's my most sought after feature in WhatsAppX! That would be freaking awesome!
Sent from my SM-G930F using Tapatalk
I can translate the menus in Italian, let me know how I can do it
Inviato dal mio HTC One utilizzando Tapatalk
FPSUsername said:
Per contact wallpaper and lock confirmed?
What about fingerprint per contact lock?
Edit:
Tested it and so far really good. The only thing left with the contact lock is every time I use immediately lock, when opening a picture I have to reinsert the password. The 1 min timeout is nice, but what about a timeout + lock when leaving the app itself.
Currently it interferes with whatsappx features, thus I can not use it (it works, but the whatsappx section is gone)
Features I would love to see:
Timeout + lock when leaving the app
Fingerprint lock, pattern lock
Per contact wallpaper
Sent and received messages counter
Keep up the good work dev!
Sent from my OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think Timeout + lock when leaving the app is a good idea.
Fingerprint lock, is not possible afaik, if you know any module that can use oneplus's fingerprint sensor put link to it.
Per contact wallpaper, highlight contacts can be implemented. Give me some time.
Not activating and throwing error message. I've attached the screenshot. How to get the latest Xposed bridge 82. I have 54 installed.
Sent from my Micromax Canvas 4 A210 Jellybean 4.2.2 (Lollipop themed rom by FSadino + Gravitybox).

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

All 5-star Play Store reviews disappear right after they are posted for some reason.
If you want to give a 5-star rating, please first give a 4-star rating and then update it to 5 stars.
Thanks!​
AppContext was featured on XDA Portal!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
AppContext
Better application context for Tasker with Xposed!
Now available on Google Play, XDA Labs and the Xposed Module Repository.​
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 [email protected].
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 [email protected].
[FEATURE] Added Chinese (Simplified) translation (thanks to @smailzhu).
[FIX] Some fixes to the Chinese (Traditional) translation (thanks to @smailzhu).
[FIX] Bug-fixes.
0.4.7.1 (Announcement)
Please report any bugs in this thread, or by sending an email to [email protected].
[FEATURE] Added Chinese (Traditional) translation (thanks to @smailzhu).
[FEATURE] Compiled for Android 8.1.0 (API 27).
0.4.7 (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] The Requirements-section collapses automatically when all are met.
[FEATURE] Works with *official* Xposed for Nougat! Yay!
[FIX] A crash preventing AppContext to be launched is fixed.
[FIX] Minor bug fixes.
0.4.6 - Yet another minor one (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] The Requirements are more descriptive.
[FEATURE] Merged the 2 Tasker requirements ('installed' and 'enabled').
[FEATURE] You can now collapse the Requirements-section.
[FIX] Some bugs in the Dialogs are fixed.
[FIX] Internal code restructuring.
[ALSO] Migrated to the Play Billing Library.
0.4.5 - Another minor update (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] Opening an existing Context now shows a Snackbar with 'Configure' button.
[FEATURE] The Requirements-section is clearer.
[FEATURE] Minor optimizations. Mainly foundations to be implemented later.
[FIX] Rewrote some of the Dialogs.
[FIX] Minor bugfixes.
0.4.4 - Minor update (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] Compiled for Android 8.0 Oreo. (No Xposed for Oreo, so ¯\_(ツ)_/¯.)
[FEATURE] Slight optimizations.
[FIX] All currently reported bugs fixed.
[FIX] Some UI tweaks.
0.4.3 - Moar bugfixes (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] Changed hooking of Services again, to prevent some problems.
[FEATURE] Toggling the experimental Services feature now requires a reboot to take effect.
[FEATURE] Moved 'Ignore Recents' to experimental features.
[FEATURE] Improved app detection.
[FIX] Another attempt to fix random crashes.
[FIX] Fixed some Xposed-related errors.
0.4.2 - Another bugfix release. (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] Completely different way of hooking Services...
[FEATURE] ...which removes the reboot requirement...
[FEATURE] ...and should work much better.
[FIX] Another attempt to fix random crashes. If they still occur, please keep reporting them. Thanks!
[FIX] Minor bug-fixes.
Tested on unofficial Xposed for Nougat.
Some code restructuring.
0.4.1 - Bugfix release. (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FIX] Sometimes not all apps were shown in the 'Pick apps' screen. Shouldn't happen anymore. (Thanks for testing @Infy_AsiX & @JKL22.)
[FIX] Some Xposed-related errors were fixed. (Thanks for testing @JKL22.)
[FIX] Hopefully fixed the random crashes. If not, please keep reporting them. Thanks!
0.4 - Service support is here! (Experimentally, but still.) (Announcement)
Please report any bugs by using the in-app Feedback button, or by sending an email to [email protected].
[FEATURE] Now supports Services for Event Contexts. Enable it under 'Experimental features'.
[FEATURE] Completely rewrote the 'Pick apps' screen.
[FEATURE] The Search bar is now a Search button.
[FIXED] Tasker blurbs are a bit clearer now.
[FIXED] The website-version of Tasker is properly recognized.
[FIXED] Some other minor bugs.
0.3.2 - Another bugfix release. (Announcement)
Please report any bugs in this thread, or by using the in-app Feedback button or sending an email to [email protected].
[FIXED] AppContext recognizes the Xposed Framework properly when installed (systemlessly) via Magisk.
[FIXED] The search bar was sometimes unresponsive. Not anymore.
[FIXED] The minimum Xposed Framework version required was downgraded to 86, as per request.
[FIXED] Some other minor bugs.
0.3.1 - Bugfix release. (Announcement)
Please report any bugs in this thread, or by using the in-app Feedback button or sending an email to [email protected].
[FIXED] If AppContext's module is enabled, it won't complain about not being able to find the Xposed Framework.
[FIXED] Pressing 'back' when picking apps to act on does not crash the app anymore.
[FIXED] The Tasker blurb in a State profile makes sense now.
0.3 - Initial release.
Please report any bugs in this thread, or by using the in-app Feedback button or sending an email to [email protected].
Known Issues
0.4.7.2
Support for Services is still experimental, and is completely disabled by default.
The following issues are fixed in the current version.
0.4.7.1
Support for Services is still experimental, and is completely disabled by default.
0.4.7
Support for Services is still experimental, and is completely disabled by default.
0.4.6 - Yet another minor one.
Support for Services is still experimental, and is completely disabled by default.
0.4.5 - Another minor update.
Support for Services is still experimental, and is completely disabled by default.
0.4.4 - Minor update.
Support for Services is still experimental, and is completely disabled by default.
0.4.3 - Moar bugfixes.
Support for Services is still experimental, and is completely disabled by default.
0.4.2 - Another bugfix release.
Support for Services is still experimental, but should work much better.
0.4.1 - Bugfix release.
Support for Services is still experimental.
0.4 - Service support is here!
Support for Services is still experimental.
Some apps do not show up in the 'Pick apps' screen.
AppContext sometimes force-closes.
0.3.2 - Another bugfix release.
None yet.
0.3.1 - Bugfix release.
None yet.
0.3 - Initial release.
Currently doesn't detect systemless Xposed via Magisk.
Pressing back when selecting apps to act on causes a crash. Instead, please tap either 'SAVE' (upper right) or 'X' (upper left).
A typo in the Tasker blurb.
Oneplus one, running CM13 (sultan's) with my own custom kernel.
Seems to be working fine!
Oneplus3t with magisk and systemless xposed, The App does not detect xposed is installed and module has been activated!
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!
JayShortway said:
• it needs an accessibility service, which prevents using screen lock to enhance data encryption
Click to expand...
Click to collapse
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
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. )
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
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!
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"
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 [email protected]. 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.
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.
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:
Profile: Event --> Plugin --> AppContext --> Start --> pick the apps you want to act on
Variables --> Variable Set
Name: %appsRunning
To: 1
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
Task --> Wait
MS: 500 (You can play with this number: smaller for a quicker response, bigger for more reliability detecting screen state.)
Task --> If
Condition: %SCREEN equals on
Variables --> Variable Set
Name: %appsRunning
To: 0
Task --> End If
Profile: State --> Variables --> Variable Value --> %appsRunning equals 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!
Nice! Checking this out. Thx!
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).
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?
JayShortway said:
Do you mean something like a Tasker-compatible Xposed module that toggles location modes?
Click to expand...
Click to collapse
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.
Any location/GPS usage gets the message "For Android 2.3+ Google have made changes such that it is no longer possible for a normal app to change GPS without user-interaction. If you wish to continue.. blah blah blah.. consider rooting and installing the secure settings plugin".
Considering that Tasker is able to have root privileges granted, clearly it should be possible for it to toggle location.
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.

Categories

Resources