Database Develop

Lock access to certain apps and settings

Dear Tasker-Masters,
My goal:
I want to limit the use of certain apps on my son's phone (running CM12.1) using tasker. Some apps (basically games) are time-limited, others shall not be accessible at all.
What I did (apart from deactivating the guest account):
I've defined a profile "No access" that activates when certain apps start (including play store and settings). This profile starts a task calling for a lock screen asking for a code. Locking settings is especially needed to deactivate the option to developer options and root access, access to other appstores, or the device admin section.
What my son did:
He found out, that the locked app appears in the app history. Clicking the locked app in the history immediatly brings up the lockscreen. However, there's a tiny time frame of maybe 0.1 seconds, where the locked app reacts to strokes on the display. This way, it's possible to scroll down the "setting" app until you get to the "security" and "device admin" section, and then to disable tasker from there. Now, profiles cannot read or react to whatever appears in the foreground of the display.
My question:
1. Can you think about a secure way to lock access to android settings? How would that be?
2. is it possible to deactivate the appearence of (only!) the android settings in the app history?

1. Create a profile -> Application -> Settings. This will trigger when someone goes into the settings app (yes even settings its an app).
In the task itself you can just "Go Home".
The task will trigger even if he goes to the settings from the recent app screen.
2. If your phone is rooted then just kill the settings app from running.
If not use AutoInput to press that "kill all" button (unfortunately).
Make sure also that tasker is a device administrator. You don't want your son to "accidentally" uninstall it.
You can't uninstall device admin apps without turning off that setting and he cant go into settings.
I hope these guidelines will help you.

Profile triggered by %time variable not firing

Phone is Pixel 3a running Android 10, Tasker is up-to-date.
I have a profile called PwrConnect that runs a task called Clock. The task simply launches my alarm clock app on the phone. The profile is primarily triggered when any power is connected to the phone but it has a secondary condition that specifies the time must be between 10:30pm and 6:00am.
When I plug my charger into the phone the profile is not triggered. If I remove the secondary condition (the time constraint) then the profile triggers when I plug in. But here's where it gets kind of strange. If I include the secondary condition (the time constraint) and I have the Tasker app open when I plug the charger in then the profile fires and runs the task which launches the clock app. Alternatively, I have also tried putting the time constraint in the task (%time > 2230) but that does not work either.
What am I doing wrong??? Or, is this a bug? Anyone else see anything like this?

Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?

ktmom said:
Do you have "reliable alarms" enabled?
Have you tried a simple profile to just test the time context?
Click to expand...
Click to collapse
I'm not sure what "reliable alarms" is. Is that a setting in Tasker or Android?
Anyway, I have done some more testing. I added another step to the Clock task to simply flash a message when the task runs and I have found that the task (and therefore the profile) is indeed being executed as it should be - that is: when power is connected and the time is between 10:30pm and 6:00am. I can tell this because the message flashes on the screen when I connect power. BUT... the clock app only launches if I have the Tasker app open when I connect power. If the Tasker app is not open then I see the message flash but the clock app does not launch.

Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
The following profile works fine for me with Tasker not in the foreground:
Code:
Time: From 11:44AM Till 3:44PM
State: Power [
Source:Any
]
Enter: Open App
A1: Launch App [
App:Clock
Data:
Exclude From Recent Apps: Off
Always Start New Copy: Off
]

ktmom said:
Reliable alarms is a tasker setting in preferences on the monitor tab. It helps tasker accurately execute time related activities.
What device and ROM are you on?
Click to expand...
Click to collapse
Device: Pixel 3a, ROM: stock Android 10 (not rooted)
I am fairly certain that the problem lies with the clock app that I am using. When I change the task so that it launches the stock, built-in clock app then everything works as it should. The clock app that I am trying to use (Kaloer Clock) is no longer in the PlayStore so has not been updated in a while. So, I suspect that there is something about it that Android 10 does not like. The app still functions fine and I can manually start it or Tasker will start it IF Tasker is running in the foreground. In fact this app has a setting that should start it automatically when power is plugged in but that stopped working about the time that I upgraded to Android 10, which is why I was trying to automate it with Tasker. I hate to give up on this app though because it is the only clock app I have found that allows me to tap anywhere on the screen to snooze the alarm (or long-press to cancel it). Everything else I have tried makes you tap an on-screen button which is difficult without my glasses.

Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.

ktmom said:
Using AutoNotification (or any tasker notification listener plugin), a scene and intents, you can make the Google Clock have a full screen snooze/dismiss "button".
I slapped together an example that I put on Taskernet. It's full screen, a tap snoozes and long press dismisses.
To run it as is, you will need AutoNotification installed. The "ktm" after the profile/task/scene names can be removed. I do this to help prevent name collisions with anything already existing during import.
Click to expand...
Click to collapse
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.

dremelts said:
Ktmom,
I installed AutoNotification and imported your project. I am assuming that I need to delete either step 2 or 3 in the Stop Alarm ktm task. But, the scene does not appear unless I have Tasker running in the foreground when the alarm fires. Just wondered if you have test this in Android 10? Seems as though all my problems started after I upgraded.
Click to expand...
Click to collapse
The action that you're not using can be deleted or left paused.
And no, sorry, I'm always slow to update to major releases. But, there's something to try.
Edit the scene that your using, without changing anything else, tap the 3-dot menu. Select "properties" and change the "property type" to "activity". Save out of the scene.
Now edit the task -> show scene action that you are using and change "display as" to "activity".
Save out of the task, and Tasker, then test again.

How to activate/deactivate a qs tile upon screen off/on?

In android 10,a new feature called as TURN ALL SENSORS OFF is available in developer settings. It also has a qs tile.
Is there a way to automatically enable this feature upon screen off and then disable upon screen on?

The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.

ktmom said:
The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.
Click to expand...
Click to collapse
1) In android 10,there is an option to disable all sensors in developer options. So i turned it on last night, and battery drain was less than 2 % in 4 hrs, compared to 1% per hour usually, with volte and 4g data on. I would get more accurate stats later on.
There's a qs tile available to activate it.
What I want to ask is, is there a way to automatically enable it every time the screen goes off, and then disable it when screen goes on, without any user input?Either as a shortcut or as a qs tile.
2) I am afraid i don't have enough knowledge to exactly understand the steps you are telling. Do you know of a pre made recipe to execute this. I tried to search but in vain. Or if you are on android 10,maybe you can try doing what i need.
Thank you.

There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.

ktmom said:
There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.
Click to expand...
Click to collapse
Will follow the steps. If I encounter any issues, will reply back here.
Big thanks.

Game mode profile

So I think just about every game on my oneplus 7 pro triggers a built in thing called gaming mode. Is it possible to create a profile that begins when that gaming mode starts and ends when that gaming mode ends. In this way I adjust things like volume levels and screen on time along with what the gaming mode does. And once for all of them instead of a profile for every game.

My guess is there is a custom setting that defines the status of the gaming mode. That's only a guess since I don't have a One plus.
You could use the native tasker settings -> custom setting action to see if you can identify what changes when the game mode turns on. Tapping the magnifying icon [emoji361] will bring up an assistant. Once you identify the setting, it can be used in a profile context (system -> custom setting).
From some online reading, I also think that the games that trigger game mode are entered in a list by a user. You could use an app context with each of those games selected so your profile activates whenever the game is in the foreground.
Hitting the gear/cog icon when the profile is selected will bring up settings for the profile. One of those settings is a toggle for restoring settings when the profile exits. In the case of an app trigger, when a different app is in the foreground, the settings made in your entry task will revert.

ktmom said:
My guess is there is a custom setting that defines the status of the gaming mode. That's only a guess since I don't have a One plus.
You could use the native tasker settings -> custom setting action to see if you can identify what changes when the game mode turns on. Tapping the magnifying icon [emoji361] will bring up an assistant. Once you identify the setting, it can be used in a profile context (system -> custom setting).
Click to expand...
Click to collapse
Upon starting a game that starts game mode the only thing that this method finds is a screen brightness change. when used from state. And nothing when used from event. Strange because if a game is triggering a system setting or something there should be something for tasker to see get triggered so a profile could tie into running while it is active. Much like a profile that would trigger upon phone charging for example and end when not plugged in to charge any more. Any other idea how i can identify what is triggered (for game mode on/off) to set a profile to run along with it?
ktmom said:
From some online reading, I also think that the games that trigger game mode are entered in a list by a user. You could use an app context with each of those games selected so your profile activates whenever the game is in the foreground.
Hitting the gear/cog icon when the profile is selected will bring up settings for the profile. One of those settings is a toggle for restoring settings when the profile exits. In the case of an app trigger, when a different app is in the foreground, the settings made in your entry task will revert.
Click to expand...
Click to collapse
Yes in game mode you add whatever games you want to trigger the mode. On my LG G4 I had a profile for each game but the profiles were problematic. Some of them would turn on and off while the game was still running. If I can have a profile that runs when game mode is active and ends when game mode is not then I would completely avoid having a new profile for every game.

I was suggesting using the custom setting action in a task to determine the setting. Then use that information in a profile to monitor it.
You can attempt to manually identify the custom setting (if that's what is controlling game mode). See here.
I'm thinking the mode reverts as soon as you leave the game to return to Tasker, so the built in assistant may not catch the change. Grabbing the settings via ADB and running a diff on the before and after may be the only way to go.
Otherwise, someone in the device forums might have insight how this mode is monitored.
As far as the app trigger approach, sometimes you can stabilize the task by putting a wait action at the start of an exit task and then stop the exit task of the calling profile is active (%PACTIVE).

Thanks for the reply with a method to identify the setting. Assuming that it is a setting. Using the custom setting action is a task when tapping on the icon it says to toggle the setting and return to tasker to find out what it is the results ended the same as attempting to use it by the other ways. It returned nothing or brightness found. I'll have to give the method in the link a try and see what happens. Will report back, might be a couple days.

I finally was able to identify the setting for making the profile, thanks much for the help.

Tasker keep screen on Android 12 issue

Hi,
I have set up the display timeout option with the settings below but it doesn't seem to work. I am using an oppo phone on Android 12.
Create a new task. Select the “+” button. Select “Display” followed by “Display timeout” Select the time span you want to set and then save. Now select “Profile” and click “+” and then “Applications” Mark the applications for which you want to activate this Tasker profile.
Then I open the app but after 15 seconds the screen turns off which is the default device screen timeout.
Is there no way to override this? Maybe get tasker to somehow keep interacting with the screen to keep it on?
I've tried this on a few apps and have got two different messages..
One says screen will stay on for 15 seconds which is the system screen time out.
Other says tasker will keep screen on but still times out after 15 seconds.
Really want this to work as some apps like games I don't want timing out after 15 seconds and I don't want to increase the system time to couple of mins for every app.

Hi,
I have the same problem on my OPPO A74 with Android 11 ((ColorOS Version V11.1). It seems impossible to create a task to change the screen time out; not in connection with a profile, shortcut or widget. The amazing thing, though - when you test the task in Tasker it works perfectly fine.
Media Volume, I think, also doesn't work. Other app connected profiles like autorotate or display brightness work well. I wanted to test more but I can't find the time.
I really miss the screen timeout though. It drains the battery too much to set it constantly to 15 minutes or so, but for some apps less simply is annoying.
The developer created some apk to help with some OPPO related problems, unfortunately, it didn't help with this one (sorry, I can't remember exactly what it was).
A kind of workaround: Once you've activated the Developer Options an your phone you can enable "Keep screen on while charging". When you need longer screen time, just plug into a charger.
But using a Tasker Profile would be much nicer.
Hope somebody knows a better trick.

Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
EDIT: Try first not move the task as exit task. ( make the task as normal entry task )

eeeemc said:
Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
Click to expand...
Click to collapse
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.

Dreamcatcher0664 said:
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.
Click to expand...
Click to collapse
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.

eeeemc said:
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.
Click to expand...
Click to collapse
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.

Dreamcatcher0664 said:
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.
Click to expand...
Click to collapse
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.

eeeemc said:
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.
Click to expand...
Click to collapse
I feel like I'm in Star Trek - "To boldly go, where no one has gone before" XD
When I try your suggestion, I only receive the message that my device isn't rooted.
Btw, for some tasks it is necessary to enable the Write Secure Setting Permission (f.e. Set Assistant), where xou have to setup ADB on your PC. Would such a procedure be registered by the phone as rooting? Anyway, I don't think I would dare to do something I know so little of.

Another solution I was thinking of, is it possible to create a tasker quick tile/ quick setting to change the system screen timeout.
So instead of having it change for certain apps which isn't working at the moment.
Maybe if we can change it from the system so will be for all apps. You can create two separate quick tiles to toggle between different screen timeout settings.

The newest version of Tasker (6.0.9) comes with Tasky.
Tasky offers the possibility to activate premade profiles. One of them is "Keep Display Awake For Apps". And that one works with my OPPO Phone.
I also tried "Auto-Mute Apps", another profile I couldn't get working. It also works fine.
To switch between Tasker and Tasky you just have to click on the "Three-Dots-Button" in the right top corner. It's not like switching apps but using different user interfaces.
Good luck!
- Sorry to say, but this seems to work for some apps and not for others. But at least sometimes it does work.

Thanks for replying back to this thread to inform me. I tried it and it works for the app I was trying to make it work for which is good! Makes it so much easier now.