Related
I can't remember if I've seen this as possible; seen this as a want; or it already exists.
I don't use a lock screen on my phone at all. Sometimes I worry about security, but not enough to deal with a lock screen all the time.
Solution would be that if your phone is out of Bluetooth range of your watch, then you hit a lock screen (with password). If you leave your watch at home or something, then you get to enter your password when you turn on your phone. When you have your watch on, no lock-screen.
This already out there somewhere? Wonder if Tasker could do something like this.
Looking at:
http://forum.xda-developers.com/showthread.php?t=955092 with Bluetooth plugin, but is there something like this in the Gear store somewhere?
This feature is included in Gear Manager. I use it and it works great.
lyall29 said:
This feature is included in Gear Manager. I use it and it works great.
Click to expand...
Click to collapse
I just saw the option, but 1 problem - it seems to force you to use a slide unlock when the gear is in range, and pattern unlock when it is not.
Any way to use *no* lock screen when gear in range?
Not that I know of.
lyall29 said:
Not that I know of.
Click to expand...
Click to collapse
Thanks for the replies. Hmm - additional security vs pain of lock screen.
Question I'll have to go look up - I haven't used a lock screen since I was going crazy in my Widget Locker days. I remember reading a lot about being able to customize the screen a bit and/or add some more basic info - how customizable is tge default lock screen nowadays?
Edit: Nevermind, I just went to lockscreen to turn on 'swipe' and got a page full of stuff that disappears when you select 'none' (which is where I was a minute ago...)
polstein said:
Thanks for the replies. Hmm - additional security vs pain of lock screen.
Question I'll have to go look up - I haven't used a lock screen since I was going crazy in my Widget Locker days. I remember reading a lot about being able to customize the screen a bit and/or add some more basic info - how customizable is tge default lock screen nowadays?
Edit: Nevermind, I just went to lockscreen to turn on 'swipe' and got a page full of stuff that disappears when you select 'none' (which is where I was a minute ago...)
Click to expand...
Click to collapse
Did anyone find a way yet to use a pin rather then pattern lock to use with autounlock? anytime I activate autounlock it prompts for a pattern which is not what I like. I want to use a pin if possible...
Maybe try this app?
https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en
I'm not sure if it only disables the lockscreen when you don't have password on, hopefully there's some settings you can mess around with.
I've looked for a solution but none of them work.
I'm looking for a simple Profile to turn the screen off when the proximity sensor is covered, which is simple.
But I don't want the profile to trigger if the sensor is just briefly covered so I want to add a task to only trigger the profile if the sensor is covered for 5 seconds.
I've tried adding a Wait task but that doesn't work. According to the tutorials I've seen, a Wait task should work. When I pass my hand over the sensor instead of turning off immediately, it waits 5 seconds then turns off.
I'm looking for similar functionality to the F-Droid app F2L.
Thanks.
i'm in the same, what i do is when the sensor and no light switch time of screen to 15s. I set time of screen to 2m.
Using your way you have to make 2 profiles 1 with sensor on off variable, the second with a entry task with wait 5 seconds and screen off and exit task to stop the first one. the second profile must be activate when the variable of the first one is set to true (or what ever you want)
Enviado desde mi SM-G900M mediante Tapatalk
Spookymyo said:
I've looked for a solution but none of them work.
I'm looking for a simple Profile to turn the screen off when the proximity sensor is covered, which is simple.
But I don't want the profile to trigger if the sensor is just briefly covered so I want to add a task to only trigger the profile if the sensor is covered for 5 seconds.
I've tried adding a Wait task but that doesn't work. According to the tutorials I've seen, a Wait task should work. When I pass my hand over the sensor instead of turning off immediately, it waits 5 seconds then turns off.
I'm looking for similar functionality to the F-Droid app F2L.
Thanks.
Click to expand...
Click to collapse
Proximity Sensor.prj.xml
Download the project and import it.
A code shell is used to power off the screen, so root is needed. If you don't have root, then use System Lock tasker action.
I hope it's working as you want.
EDIT: Ops, someone already replied. I was writing this post.
#Henkate said:
Proximity Sensor.prj.xml
Download the project and import it.
A code shell is used to power off the screen, so root is needed. If you don't have root, then use System Lock tasker action.
I hope it's working as you want.
EDIT: Ops, someone already replied. I was writing this post.
Click to expand...
Click to collapse
Thanks for the reply. I downloaded your XML project from media fire but when I tried to import it I got an error saying it failed to import data. I checked the XML in a text editor and noticed a lot of text strings with "media fire" and "Google". I don't think that should be the case.
Edit: Nevermind. I opened it in a different browser and it downloaded the proper file. I'll test it and see if it's what I was taking about.
Edit 2: That's money dude! That's so much easier than I thought. I had 4 different tasks and a few different variables. Thanks a ton!
Edit 3: I added a notification sound when the screen actually turns off. That way I'm not wondering if it did or not.
I noticed that when I turn the screen back on the flash text (Please wait 5 seconds) always displays. Does this mean that your project is always polling the proximity sensor even when the screen is off? In Tasker preferences, under the monitor tab, I have the proximity setting at No.
Spookymyo said:
Thanks for the reply. I downloaded your XML project from media fire but when I tried to import it I got an error saying it failed to import data. I checked the XML in a text editor and noticed a lot of text strings with "media fire" and "Google". I don't think that should be the case.
Edit: Nevermind. I opened it in a different browser and it downloaded the proper file. I'll test it and see if it's what I was taking about.
Edit 2: That's money dude! That's so much easier than I thought. I had 4 different tasks and a few different variables. Thanks a ton!
Edit 3: I added a notification sound when the screen actually turns off. That way I'm not wondering if it did or not.
I noticed that when I turn the screen back on the flash text (Please wait 5 seconds) always displays. Does this mean that your project is always polling the proximity sensor even when the screen is off? In Tasker preferences, under the monitor tab, I have the proximity setting at No.
Click to expand...
Click to collapse
I'm glad I helped you. I'm still a noob
I've tried again and it seems that you're right about the flash text. And I've figured out why: because when screen was going on after it was off, the variable %PROX still had value 1 (so it was triggering the profile), but then it was going to 0. I think that's it. In any case, I've made some changed and now that problem is gone.
I've made following changes:
- added two profiles to know if the screen is locked or unlocked. When it's unlocked, it also means that the screen is on
- added a state not call any, so the screen won't turn off when you're in a call (because when you have the phone at ear, the proximity sensor stays on, so we don't want our profile gets triggered that time)
- added a state display on at proximity profile which play with the %PROX variable, so the proximity sensor won't get triggered when you have the phone in pocket for example. It will trigger only if the screen is on
NEW version here
PS: let me know how it goes with the battery drain , if is minor or major. I'm just curious because i didn't use a profile with proximity sensor and I don't need this one.
#Henkate said:
I'm glad I helped you. I'm still a noob
I've tried again and it seems that you're right about the flash text. And I've figured out why: because when screen was going on after it was off, the variable %PROX still had value 1 (so it was triggering the profile), but then it was going to 0. I think that's it. In any case, I've made some changed and now that problem is gone.
I've made following changes:
- added two profiles to know if the screen is locked or unlocked. When it's unlocked, it also means that the screen is on
- added a state not call any, so the screen won't turn off when you're in a call (because when you have the phone at ear, the proximity sensor stays on, so we don't want our profile gets triggered that time)
- added a state display on at proximity profile which play with the %PROX variable, so the proximity sensor won't get triggered when you have the phone in pocket for example. It will trigger only if the screen is on
NEW version here
PS: let me know how it goes with the battery drain , if is minor or major. I'm just curious because i didn't use a profile with proximity sensor and I don't need this one.
Click to expand...
Click to collapse
This version didn't work at all. It won't display the flash text. And it won't turn off the screen, it only dims. I'll just modify the first one with some of your new code.
Spookymyo said:
This version didn't work at all. It won't display the flash text. And it won't turn off the screen, it only dims. I'll just modify the first one with some of your new code.
Click to expand...
Click to collapse
Huh, it worked for me.
Do like you said.
I tried something a little different with the exception of using two profiles.
Profile one: Cover Closed
State-Proximity Sensor -> Task: Screen Off(Wait; one sec.,Turn Off; Dim off, Lock on)
Profile two: Cover open
State-Not Proximity Sensor -> Task: Screen On(Stop; Task Screen Off, Turn On; Block Time five hundred)
How launch app when screen is off and security lock? (I want the radio to wake me up) I try: 1. Secure settings --> Configuration:Screen & Keyboard Light On (10sek) 2. Wait 1sek 3. Show Scene --> Name: Popup ,Display As: Activity 4. launch App: "(in my case is "eskaGO" This task try launch this app but can't launch to the end. When Task is end nothing happened. But when I manually unlock screen and see what app work in background I see this app. It's look like this task try launche app but can't launch it to the end.
I try too with AutoLunch but is this same.
Can anybody help??
Can you use Smartlock to prevent your device from locking at home?
lauralbaby said:
Can you use Smartlock to prevent your device from locking at home?
Click to expand...
Click to collapse
This not solves the problem. I don't need this only in home. I a lot travelling.
I try with secureTask plugin with off and on keyguard but this disable all securelock.
Well it sounds like the app just can't launch over the keyguard, so the task can't complete till the phone is unlocked. If you're comfortable with it, you can change the timeout (time it takes for the lock to be activated) to a really high number before you go to sleep, then after the app wakes you up, have it changed back to normal.
Thanks for solution but this not solve the problem. In Your idea every day before I go to sleep (when I activate alarm) I should count how many time screen should be unlock. I not everyday wake on this same time or it's time when I stay 1-2 weeks in this same place and wake up every day in this same time.
Every time when I set alarm I must count and set unlock screen Is not good idea.
Maybe somone else have Idea how to launch it?
gonzolex said:
Thanks for solution but this not solve the problem. In Your idea every day before I go to sleep (when I activate alarm) I should count how many time screen should be unlock. I not everyday wake on this same time or it's time when I stay 1-2 weeks in this same place and wake up every day in this same time.
Every time when I set alarm I must count and set unlock screen Is not good idea.
Maybe somone else have Idea how to launch it?
Click to expand...
Click to collapse
which counting are you talking about? I think he meant setting the grace time of lock screen to something like 7*24 hours, that way even if screen is off, you don't really engage the lock.
This could be a security drawback and might affect your Moto display/Samsung Always screen on function if you have them.
OK maybe I something wrong understand.
Maybe You can write how I should configure this task? It will be very helpful to me
Now in task profile I set time to start and end my alarm task.
alienyd said:
which counting are you talking about? I think he meant setting the grace time of lock screen to something like 7*24 hours, that way even if screen is off, you don't really engage the lock.
This could be a security drawback and might affect your Moto display/Samsung Always screen on function if you have them.
Click to expand...
Click to collapse
lauralbaby said:
Well it sounds like the app just can't launch over the keyguard, so the task can't complete till the phone is unlocked. If you're comfortable with it, you can change the timeout (time it takes for the lock to be activated) to a really high number before you go to sleep, then after the app wakes you up, have it changed back to normal.
Click to expand...
Click to collapse
Can You help me understand this and write how should look like this task?
gonzolex said:
OK maybe I something wrong understand.
Maybe You can write how I should configure this task? It will be very helpful to me
Now in task profile I set time to start and end my alarm task.
Click to expand...
Click to collapse
When the screen is turned off, it takes time to activate the keyguard/lock. Usually it's set to 1 second or less, so as soon as the display is off, the lockscreen is on. This can be changed (and in fact this is what Smart Lock does) so it won't activate as fast. Smart lock won't work in your conditions, so we can use Tasker plugins.
You need to get the plugin Secure Task if you are not rooted, Secure Settings if you are. Secure Task needs permissions granted in ADB, but the Help will explain the process.
Once you have it working, you can add the "secure settings" action for lockscreen timeout (see screenshots, it may be called something different on your device.)
There's a read action as well as write, you should read the initial value before changing it, save it, and restore it after the alarm goes off.
(In the Secure Settings plugin it's called Device Settings but other than that similar.)
Thanks for this
Now I undarstand that:
I have other profile where is task what will launch my app and where I set time to start this profile.
If I want that profile work - app launch correctly - I must before I go sleep launch other task (this what You wrote) what don't secure lock my screen.
Right? Did I understood correctly?
Yes, if you have a sleep profile, or if not, set it to activate at 2230 or whenever your bedtime is. The task will simply be Secure Task - secure settings - Read secure lockscreen_timeout (or whatever your device shows), so you can have a global variable of the typical timeout. Then Write secure lockscreen_timeout 99999999, as I posted in the screen shots.
And then have your wake up task activate at 7 or whenever, and then redo the lock timeout to the saved variable.
Ok,
But for example:
1. If I set this task to start 23:30 but since 23:10 i will not touch my phone this not work because screen still wil be secure lock ?
2. If I set this task to start earlier for ex. 21:00. On this time my phone is not protect if some one stole it and any one who get my phone will be have full access. Not always in this same time I will in the home.
Idea to solve my problem is good maybe someone else will need it.
For me is not good
It's not solve my problem
Maybe somone else have any idea how I can launch app when screen is secure lock
+ wifi condition
+ cell location
alienyd said:
+ wifi condition
+ cell location
Click to expand...
Click to collapse
yes, yes
+ anti theft application
I don't know what happened because to March everything working in my phone. In March I musted do factory reset and launch app in secure screen stoped working ;/
Earlier I use to tasker autoinput plugin and was working , now it write that autoinput can't unlock screen :|
So maybe something was changed/app had update and to launch app in secure screen now is other plugin
hmm that's weird. You must have done/changed something. I don't think any app, especially Tasker has changed anything since then.
alienyd said:
hmm that's weird. You must have done/changed something. I don't think any app, especially Tasker has changed anything since then.
Click to expand...
Click to collapse
I know that that is weird. But I don't know what happened because I done nothing special. Just made a task and profile and that was working. Earlier when I changed Rom and restore task everthing work good. Now stop working and I dont know why :|
Better... When this stop working I had try allone and try searching solution.
I made task like this:
1. Secure Settings - Configuration: Screen & Keyboard Light 10sek
2. Status Bar Set Expanded
3. Launch App: eskaGO
4. Wait 10 sek
5. Autoinput Action - Configuration Type: Text Value: Tasker
6. Autoinput Global Action - Configuration Action: Home
And this WORKED! it worked but every second time. Exactly the second time.
Because I thinked that is problem with my phone I made factory reset one more time and this it stopped working completely.
So I don't want belive that so powerful app like Tasker where is so much plugin and a lot of people who very good know this aplication that no one find solution for this.
Sorry I still don't understand your explanation...
If I have it right, you are trying to make an alarm clock out of the radio app.
Here is what I did to implement this idea:
trigger:
- display off
task:
launch app: notepad
alert: beep
result:
as soon as the screen turns off, I heard the beep. When I turned on the screen, I saw notepad app in the foreground.
requirement:
you will need to add something to trigger this during screen off. That extra condition should not turn on the screen. If it does, you should re-consider this whole condition.
The fact that notepad is running in foreground after unlocking means that the task was carried out as intended. If you can run the radio app, the playing should be turned on automatically the moment the app starts, or error you will have radio app running without actually doing anything.
if all these fail, please post a screenshot of your profile, task and log.
good luck!
How about using Appcloner for this? You clone the app and give it the capability to run on to of the lock screen. That's it. Good luck.
jdelcaribe said:
How about using Appcloner for this? You clone the app and give it the capability to run on to of the lock screen. That's it. Good luck.
Click to expand...
Click to collapse
I will try It
Can You tell me where in this app is this setting?
gonzolex said:
I will try It
Can You tell me where in this app is this setting?
Click to expand...
Click to collapse
Sure. Under display options, then choose " show app on lock screen".
...and to set the brightness to a specific value? I can do this easily in Windows, but not in Android.
Perhaps you figured it out by now, but just in case, the answer is definitely yes, I use that very functionality for brightness on my phone:
1. Create a new task
2. Add a "Display Brightness" action to this task (the value in this action doesn't represent percentage, so you might need to experiment with the number to get the desired brightness)
3. Add a "Tasker Shortcut" widget to your home screen. It will lead you to select the name of the task you created.
-It will also require you to select an icon for the widget, which you will do with the 9 squares at the bottom of the task edit screen (I already selected an Android robot icon in the picture).
-When adding the widget, you may also encounter an error message requiring you to open Tasker and exit with the back button to close it out properly in order for the widget to work.
There would be a similar process for volume, but you'd have to choose the appropriate action for which volume you want to adjust: ringer/system/media, etc.
Yes, I did figure it out, but thanks for posting that clear explanation, which is rare. It will probably help someone.
My most interesting program so far is a reliable way to turn the display off and on automatically to save battery power and, more importantly, to extend the lifetime of the power button.
Even with a reliable program, though, Tasker sometimes delays responding when it is closed and the display is off, so I've found that Tasker must be left running all the time. This is easy to arrange: in Android task viewing mode, click the lock icon at the top right of the screen view pane so that it becomes solid.
Such locks persist forever, I think, and are therefore quite confusing to newcomers to Adenoid, I mean Android.
You're welcome. Hopefully it might. I sympathize with the new user, since often it's difficult to get a solid, helpful answer from an advanced user regarding a beginner's topic.
As for Tasker being killed on occasion, unfortunately the circumstances surrounding that vary dramatically between devices. For example, whatever lock icon you're talking about to fix the issue on your device is not on my phone at all, so it would not work as a solution for me.
Do you have the option to "Use reliable alarms" in Tasker? I'm not sure if its presence varies between Android versions. I have that option set to "always"*, and I've never had a single time where Tasker fired late or was killed. It uses a persistent system alarm to keep tasker "in mind" all the time.
*And battery optimization for Tasker turned off, of course
david0001 said:
Yes, I did figure it out, but thanks for posting that clear explanation, which is rare. It will probably help someone.
My most interesting program so far is a reliable way to turn the display off and on automatically to save battery power and, more importantly, to extend the lifetime of the power button.
Even with a reliable program, though, Tasker sometimes delays responding when it is closed and the display is off, so I've found that Tasker must be left running all the time. This is easy to arrange: in Android task viewing mode, click the lock icon at the top right of the screen view pane so that it becomes solid.
Such locks persist forever, I think, and are therefore quite confusing to newcomers to Adenoid, I mean Android.
Click to expand...
Click to collapse
Enabling Use Reliable Alarms doesn't help. I think at this point I would say that getting Tasker to work when the display is locked is not obvious. Perhaps it is documented somewhere.
Basically, the bad symptom is as follows: after the display has been locked for a few minutes, moving the device fails to turn the display on again. Something kicks or locks Tasker out, but only after more than just a few seconds.
Sorry about not realizing that locking an app in memory is not part of Android. I'm using an inexpensive TCL A3 device sold by Tracfone. Locking is nice when you want to avoid startup delays for a task.
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.