Database Develop

Tasker on gTab

I just started using Tasker on my Droid X running Liberty GB and am loving it. Last night I installed tasker on my gtab running CalkClem V6 and was wondering if anyone has any gtab/tablet specific profiles or tips?
So far I have only used Tasker on the gtab to automatically turn off the screen when the case closes. The profile activates when the light sensor is at zero. The corresponding actions are wait 4 seconds and then lock device. I'm betting I will have trouble with this profile when using the gtab in a very dark room, so I might have to restrict this profile to only daylight hours.
I'm also considering using tasker to shut down the gtab automatically every night at around 2AM just in case I left it running and it's not plugged in.
Anyone doing anything interesting with tasker and the gtab?

brettdwagner said:
I just started using Tasker on my Droid X running Liberty GB and am loving it. Last night I installed tasker on my gtab running CalkClem V6 and was wondering if anyone has any gtab/tablet specific profiles or tips?
So far I have only used Tasker on the gtab to automatically turn off the screen when the case closes. The profile activates when the light sensor is at zero. The corresponding actions are wait 4 seconds and then lock device. I'm betting I will have trouble with this profile when using the gtab in a very dark room, so I might have to restrict this profile to only daylight hours.
I'm also considering using tasker to shut down the gtab automatically every night at around 2AM just in case I left it running and it's not plugged in.
Anyone doing anything interesting with tasker and the gtab?
Click to expand...
Click to collapse
That's actually REALLY useful! I'm going to go find it on the market in a little bit...

Tasker is $6.42 in the marketplace, which seems a bit expensive for an automation app... until you've tried it. The dev's site has a 7 day trial apk if you want to give it a spin. You can backup all profiles from the trial and restore them to the purchased app if you like it.
http://tasker.dinglisch.net/
I just created a profile on my droid x that plays beyondpod and sets the media volume to a specific level every time my Bluetooth headphones are connected.
sorry if I sound like a shill, but it's just so awesome...

Oh, its a paid app.
I like the idea, but not enough to spend that much on it. Maybe if it were a 99 cent app.

I'm almost certain there is a free app to do just the case close screen off portion. I remember seeing it here on the forum a while back.

That would be clutch, as I just got my case today and would love to make that happen!

To the op, could you post instruction on how to do what you did with locking screen when light sensor is zero? I'm struggling. With it.

Tasker isn't the most intuitive tool in the world, so here is how I achieved the case close, screen off profile:
Open tasker
tap "New" to create a new profile and name it anything
tap "State"
tap "Light Level"
set top slider at 0 and set bottom slider between 1 and 4 (higher number will help if your case doesn't block all the light)
tap "Done"
tap "New Task" and name it anything
tap "+"
tap "Tasker"
tap "Wait"
The second slider is seconds. This will determine how long the delay is between when you close your case and when the screen turns off. I selected 4 seconds to avoid accidentally covering the sensor with my finger.
scroll down and tap "done"
tap "+" again
tap "Display"
tap "System Lock"
tap "Done"
Tasker will need to gain a new permission from the OS at this point. Be sure to read the warnings that will pop up.
tap "Done"
tap "Apply" and make sure the "On" check box is selected in the bottom right
That should do it. If this doesn't work you may want to confirm that your light sensor is functioning properly (I've only tested this on CalkClem V6). To do that I downloaded one of the "phone sensor" apps from the marketplace.

Nvm, I'm an idiot.

goodintentions said:
Nvm, I'm an idiot.
Click to expand...
Click to collapse
I prefer "dummy" myself

brettdwagner said:
I prefer "dummy" myself
Click to expand...
Click to collapse
Haha, my original problem was I couldn't find "system lock". But in the back of my mind I was trying to look for "lock system". Only saw "lock" but no "lock system". I was like "wtf?"
Then after going on a rampage through my kitchen, I went back to the gtab and found "system lock".
May be I should get my eyes checked soon. Been a few years since last time.
By the way, thank you for recommending this app for me. I'm waiting for my clip case to arrive. Man, it will be slick. Has tested it a dozen times now. The screen shut off every time.
The thing is too bad the other way around doesn't work. I tried to set up the reverse to turn it on when there's light and the gtab wouldn't turn on.

Any idea how to restrict this to daytime hours? Nevermind. My dumbass found it.

You can restrict it to daylight hours by tapping the left side of the profile and selecting "add." From there you can set the hours in which this profile can be activated.
Just in case any onlookers were interested.
Check out gestures in tasker too. You can do things like mute the tab by rotating it left then right.
http://tasker.dinglisch.net/userguide/en/gestures.html

[Q] Quick camera (tasker, ICS, lockscreen)

A nice quick camera app is "quickest camera". Unfortunately with no camera button on the i9000 and a lock screen it takes about 10 seconds to respond and then usually the moment has gone.
The best I can do do far is to:
use Tasker to
sense when the phone is on it's left side (a gesture is another way)
disable the lock screen
...and then run quickest camera.
(the screen is automatically relocked)
However:
- this happens everytime you put the phone on it's side so no landscape mode
- setting a button combination like vol down + power only while in the lockscreen would be quicker and probably save battery but I only see buttons as a task not a context...
- quickest camera isn't that quick. An app thatdoes use any UI might be quicker
Related threads:
http://forum.xda-developers.com/showthread.php?t=1110775
http://forum.xda-developers.com/showthread.php?t=745787
Notes:
Don't seem to need the secure settings plugin anymore for this particular thing:
http://forum.xda-developers.com/showthread.php?t=1217767&page=2
A little intro to tasker: http://forum.xda-developers.com/showpost.php?p=14923270&postcount=55
A big thread on tasker:
http://forum.xda-developers.com/showthread.php?t=1110775&page=81

Ok... no responses.
Thinking laterally, any of the Gingerbread alternative unlock screens can do it but none afaik can maintain a pattern or code unlock as well as the quick camera.
Edit to avoid bump:
Its possible to set shake to camera but it costs a bit of battery. Personally I'd like it to only do this when lock screen is on but I can't get tasker to detect the lock screen... please throw me a bone

jago25_98 said:
Ok... no responses.
Thinking laterally, any of the Gingerbread alternative unlock screens can do it but none afaik can maintain a pattern or code unlock as well as the quick camera.
Edit to avoid bump:
Its possible to set shake to camera but it costs a bit of battery. Personally I'd like it to only do this when lock screen is on but I can't get tasker to detect the lock screen... please throw me a bone
Click to expand...
Click to collapse
I know this is really old... but having just started getting really into tasker I was kind of excited to respond. LOL.
So here's what I'd do, you CAN in the curent version of tasker detect if the screen is OFF and therefore it's presumed the lock would be activated... The way I currently run my tasker set up is off of variables. Basically the logic works like this "if the screen turns off... set the "@LockScreen" variable to "1". So your profile logic would be be... if "LockScreen" variable is 1 AND the phone is shaken, run this particular task (turn on the camera).
If you haven't figured this out yet, I hope this is helpful. Now I'm off to create a variant of this!

btate0121 said:
I know this is really old... but having just started getting really into tasker I was kind of excited to respond. LOL.
So here's what I'd do, you CAN in the curent version of tasker detect if the screen is OFF and therefore it's presumed the lock would be activated... The way I currently run my tasker set up is off of variables. Basically the logic works like this "if the screen turns off... set the "@LockScreen" variable to "1". So your profile logic would be be... if "LockScreen" variable is 1 AND the phone is shaken, run this particular task (turn on the camera).
If you haven't figured this out yet, I hope this is helpful. Now I'm off to create a variant of this!
Click to expand...
Click to collapse
Cheers!
I never did get it working so the feedback is much appreciated. I'll give it a go later

[GUIDE] How to enable Ambient Display Proximity Wake feature on OOS

As most of you might know, OnePlus removed the proximity wake option from OOS lately, replacing it with the lift to wake feature. If you want to use the proximity wake feature, you either have to switch to a custom ROM or use an outdated version of OOS. Both options might be suited for most people, but in case you prefer to use latest OOS and still want to use proximity wake, I have some kind of workaround.
PLEASE NOTE: it seems that the given shell command does not work on Android Oreo (OOS Open Beta as of writing). Check the latest posts of this thread for any progress.
I came across this shell command, which will trigger the ambient display:
Code:
am broadcast -a com.android.systemui.doze.pulse com.android.systemui
A big shoutout to @Quinny899 for providing me the code to trigger ambient display by shell command.
You can use this command with Tasker to trigger it when the proximity sensor is covered for some seconds or even when you wave your hand over it. I haven't had the time to get such a profile working until now, but I know that it can be archived easily.
In case you use the above command, ensure you check the "use root" option in Tasker's context menu for the shell command!
EDIT: I managed to get this working :good: Below my implementation. I am sure there is room for optimization, but this is just a basic task and it works for me (OOS 4.5.13 with Tasker 5.0u6).
You need three profiles. Two of them will check the proximity sensor state while screen is off, the third one actually triggers the ambient display while screen is off and proximity sensor has been covered (by waving over it for example).
First of all, we need to ensure that Tasker will monitor the proximity sensor while screen is off. For this, open the three-dot menu, select Preferences and navigate to the Monitor tab. Set "Proximity Sensor" to "On". That's it.
Second, you have to enable the Ambient Display option via Settings -> Display, otherwise this won't work at all (thanks to @Devildire for confirmation)
Let's have a look at the needed profiles:
Code:
[B]PROFILE [I]Prox OFF[/I]
[/B]State -> Sensor -> Proximity Sensor -> invert
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity uncovered[/I]
[/B]Variable -> Set -> %Prox = false
[B]PROFILE [I]Prox ON[/I]
[/B]State -> Sensor -> Proximity Sensor
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity covered[/I]
[/B]Variable -> Set -> %Prox = true
[B]PROFILE [I]Wake Ambient Display[/I]
[/B]State -> Display -> Display State -> "Off"
State -> Variables -> Variable Value -> %Prox = true
[B]TASK [I]Wake Proximity Display[/I]
[/B]Task -> Wait -> 1s
Task -> IF -> %Prox = false
Code -> Run Shell -> am broadcast -a com.android.systemui.doze.pulse com.android.systemui (DON'T FORGET TO CHECK "USE ROOT")
That's it. Now turn off your screen and try to wake the ambient display by waving your hand over the proximity sensor.
EDIT: Tasker profiles can be found in post #7.
EDIT #2: @Arstoien provided us with an improved version of my basic tasks, check it out here.

Thanks for the guide on how to, great work from you for the community

OP updated with instructions. Feel free to comment and share your experience or any kind of optimization proposes. Please note that the implementation is only a rough imitation of the original proximity wake feature, most likely this implementation needs some polishing.

Hey there. Sounds intriguing... I'm not understanding the stacked profiles... It seems you've got it triggering with two conditions. How do you do that?
Or... Would it be possible to upload the profiles and tasks for importing?

@saccentekennedy
If you want to add another trigger to a profile, just long-press the first trigger condition and Tasker will prompt you with a popup window where you can select to add another trigger option.
If anyone else is interested, I might upload the profiles later.

Hi guys , any file so that we can import it on tasker (if it has such system) to get this. !!??!!

Please find attached the requested profiles.
EDIT: You might want to change the wait time within the wake ambient display task to 1s instead of 300ms, this one actually works way better.

Portgas D. Ace said:
Please find attached the requested profiles.
Click to expand...
Click to collapse
Works! Thanks for sharing this.

Is root required?

BloomerzUK said:
Is root required?
Click to expand...
Click to collapse
Yes look in the code last line

Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.

Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.

dre-z said:
Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.
Click to expand...
Click to collapse
As said before, this is just a rough workaround, it works for me (but not as perfect as the former in-built option). It works if you move your hand slowly over the sensor.
saccentekennedy said:
Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.
Click to expand...
Click to collapse
Hmm, I don't have this issue, but we might add another trigger option to the wake ambient profile: only trigger if display is face-up. This way it won't be triggered if the device is in your pocket.

After looking over what you steup in Tasker........The biggest question is "What does the phone do when it is in your pocket?" I think if you can figure out a solid Tasker-based solution to that question, this will be something worth using. Great work.

It works (more or less)

@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.

Portgas D. Ace said:
@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.
Click to expand...
Click to collapse
I think I am doing something wrong. Doesn't work at all. Thanks for your help anyways

Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?

Devildire said:
Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?
Click to expand...
Click to collapse
Did you check the "use root" option in the corresponding task?

I use the downloaded profles and yes, root is checked. Using OP5 up to date OOS.
Edit: maybe there is something wrong with shell execution. Can you give me information about what I have to enter using tasker's "send intent" action instead?

[HELP] Launch app on security lock screen

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".

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.