Related
After installing Pocket controller an icon is place in today screen to change settings. The problem is I cannot access the settings dialog where there is the option of removing that icon. When I tap on it nothing happens.
Also there is created an acess to program settings in settings menu, but occurs the same, when tapping on it nothing happens.
The program works fine except of this. I want to remove that icon because it ocuppies one complete line of today screen. I've tried looking in registry but did not find any string or value to hide that icon. Tested with pocket controller pro versions 6.01, 6.0, 5,7... and always the same.
I had the same problem so I started using My Mobiler. It's free and does the job.
kiowa79 said:
After installing Pocket controller an icon is place in today screen to change settings. The problem is I cannot access the settings dialog where there is the option of removing that icon. When I tap on it nothing happens.
Also there is created an acess to program settings in settings menu, but occurs the same, when tapping on it nothing happens.
The program works fine except of this. I want to remove that icon because it ocuppies one complete line of today screen. I've tried looking in registry but did not find any string or value to hide that icon. Tested with pocket controller pro versions 6.01, 6.0, 5,7... and always the same.
Click to expand...
Click to collapse
I had the same issue with the original HTC ROM. Now I use bepe's ROM and it worked
Cendaryn said:
I had the same issue with the original HTC ROM. Now I use bepe's ROM and it worked
Click to expand...
Click to collapse
Any other solution apart from roming? Maybe a registry edit?
Here is a Regfile to switch the Trayicon off.
Menkul
menkul said:
Here is a Regfile to switch the Trayicon off.
Menkul
Click to expand...
Click to collapse
It worked!!!!
The strings added were
[HKEY_LOCAL_MACHINE\Software\Apps\SOTI\PocketController]
"enabletray"="OFF"
"KioskAdmin"="0"
"Log"="0"
[HKEY_LOCAL_MACHINE\Software\Apps\SOTI\PocketController\Video]
"enabletray"="OFF"
"Install"="\\Windows"
"Log"="0"
Now one only issue to be solved. When tapping pocket controller in settings menu nothing happens and you cannot access to progrma options.
Hallo everyone,
i have looked over all the threads here but did not find any solution.
My question is: Since SecureSettings (plugin) seems to be not developed anymore i need a new way to completely disable keyguard with Takser and ofc. reset to keyguard it was before.
Example: currenty i have a pattern to unlock. What i want to do: Profil "App X starting" -> Start-Task: completely disable keyguard (no "swipe to unlock", no pattern, no pin, nothing: tapping on power button => screen on with current running app); -> Exit-Task: restore pattern (with the pattern i was using before ofc)
Does any1 know any way how to do this? Currently i am running CM13 Snapshot (Android 6.0.1) on my GT-I9505.
thanks for any helpful answer
You can do that with Secure Settings, or the new AutoTools plugin
CrashOverride93 said:
You can do that with Secure Settings, or the new AutoTools plugin
Click to expand...
Click to collapse
SecureSettings disableing does not work on Android 6 (not only on my device). Thats why i started this thread. But thanks for the hint with AutoTools, i will try
did it work with autotools?
if it did, can u share the howto?
ty
liatgme said:
did it work with autotools?
if it did, can u share the howto?
ty
Click to expand...
Click to collapse
No, it did not (at least not for me), i did not even find the "disable keyguard" option like the SecureSettings Pluig-in had it
Still looking for a way to completely disable keyguard on Android 6 (CM13). Not even with my Smartwatch and "Smart Lock" i can REALY disable keyguard, i still have to swipe the Lock-Icon after reaktivating my phone
you can use secure settings on Lollipop and also on MM
try this with Terminal emulator:
https://dammit.nl/p/962
alegend1979 said:
you can use secure settings on Lollipop and also on MM
try this with Terminal emulator:
https://dammit.nl/p/962
Click to expand...
Click to collapse
Thanks, but i already knew this. The problem is not, secure settings does not find su binary. The problem is, secure settings -> disable keyguard is not working on LP&MM.
I am running Android 6.0.1... I use the Tasker plugin TouchTask (in Google Play) to disable the keyguard. It works perfect for me.
---------- Post added at 10:32 PM ---------- Previous post was at 09:58 PM ----------
I use a tasker plug in called TouchTask from Google Play. It works perfect for me on Marshmallow. I used the plugin to temporary disable the keyguard in order to allow voice commands when driving.
135Shadowsoul said:
Thanks, but i already knew this. The problem is not, secure settings does not find su binary. The problem is, secure settings -> disable keyguard is not working on LP&MM.
Click to expand...
Click to collapse
hi, this is weird!
Maybe I misunderstood something here, but I'm running MM, and Secure setting's disable keyguard runs fine here. I use it to turn off pin keyguard when at home, and turn it back on, with preset pin, when I'm out.
I'm running Tasker with Secure setting on 6.0.1. Also, Secure setting is enabled in Xposed, if it matters.
I don't see any problem so far...
p.s. I just saw another plugin from the same developer, it is called SecureTask, it claims to be able to clear/set pin, password too. Maybe a good solution to finally replace the dated Secure setting?
alienyd said:
hi, this is weird!
Maybe I misunderstood something here, but I'm running MM, and Secure setting's disable keyguard runs fine here. I use it to turn off pin keyguard when at home, and turn it back on, with preset pin, when I'm out.
I'm running Tasker with Secure setting on 6.0.1. Also, Secure setting is enabled in Xposed, if it matters.
I don't see any problem so far...
p.s. I just saw another plugin from the same developer, it is called SecureTask, it claims to be able to clear/set pin, password too. Maybe a good solution to finally replace the dated Secure setting?
Click to expand...
Click to collapse
Can you provide a link to this Secure Task plugin? Thanks
GrippingSphere said:
Can you provide a link to this Secure Task plugin? Thanks
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.balda.securetask
there you go, but I haven't tried this out, just saw that it claims to be able to do the job.
trukero said:
I am running Android 6.0.1... I use the Tasker plugin TouchTask (in Google Play) to disable the keyguard. It works perfect for me.
---------- Post added at 10:32 PM ---------- Previous post was at 09:58 PM ----------
I use a tasker plug in called TouchTask from Google Play. It works perfect for me on Marshmallow. I used the plugin to temporary disable the keyguard in order to allow voice commands when driving.
Click to expand...
Click to collapse
Can you share how you did this?
thanks for all the reply. Unfortunately nothing did work for me the way i need it
135Shadowsoul said:
thanks for all the reply. Unfortunately nothing did work for me the way i need it
Click to expand...
Click to collapse
how exactly do you want it to work?
alienyd said:
how exactly do you want it to work?
Click to expand...
Click to collapse
Like mentioned in my OP (and how it worked on 4.4.4 (CM11):
Profil "App X" => start task: disable keyguard => end task: enable keyguard
i am using unlock pattern usually. what i want is, while "App X" is active/running, keyguard will be set to nothing (not even swipe to unlock!). pressing power (or home button) on my Samsung Galaxy S4 (GT-I9505), wich has no fingerprint reader, returns me from black screen (screen off) to the running "App X", i was before pressing power button to screen off. If i stop "App X" the keyguard should be re-set to the unlock pattern.
The SecureSettings plugin did this job on android 4.4.4, but not on 6.0.1 for me
135Shadowsoul said:
Like mentioned in my OP (and how it worked on 4.4.4 (CM11):
Profil "App X" => start task: disable keyguard => end task: enable keyguard
i am using unlock pattern usually. what i want is, while "App X" is active/running, keyguard will be set to nothing (not even swipe to unlock!). pressing power (or home button) on my Samsung Galaxy S4 (GT-I9505), wich has no fingerprint reader, returns me from black screen (screen off) to the running "App X", i was before pressing power button to screen off. If i stop "App X" the keyguard should be re-set to the unlock pattern.
The SecureSettings plugin did this job on android 4.4.4, but not on 6.0.1 for me
Click to expand...
Click to collapse
I would recommend Xposed module App Settings, allow your app to show on lockscreen.
alienyd said:
I would recommend Xposed module App Settings, allow your app to show on lockscreen.
Click to expand...
Click to collapse
but xposed sometimes hard to hide with suhide or rootswitch
135Shadowsoul said:
but xposed sometimes hard to hide with suhide or rootswitch
Click to expand...
Click to collapse
there are, again, some modules just to do the hiding:laugh:
dorsetqpr said:
Can you share how you did this?
Click to expand...
Click to collapse
The task I use is the follwoing:
A1 Secure Settings, "screen & keyboard Lights on 4 s"
A2 Screen Unlock "Using the Plug I have mentioned"
A3, what ever else you want to do with Tasker
Please keep in mind that previously, I have disable the PIN using Tasker and Secure Settings when my cell phone is connected to my car's bluetooth
Keyguard is disabled/not an option in Secure Setting even I enabled legacy features. Did anyone figure it out how to disable keyguard on Marshmallow?
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?
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
*gentle push*, because the problem still remains
katerlouis said:
*gentle push*, because the problem still remains
Click to expand...
Click to collapse
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
fehrcomp said:
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
Click to expand...
Click to collapse
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
katerlouis said:
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
Click to expand...
Click to collapse
Yes! On my device Mate 1o Pro, it was Talkback as well that ¨obscured a permission request¨.
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
help please
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
YEESSSS!!! Thank you for mentioning this, I never would've make that connection and that's exactly what it was for me! I guess those pics weren't all that smart after all ?
Panshu Mehra said:
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
Click to expand...
Click to collapse
I have an Honor 8 pro and I'm facing the same issue. I've disabled all apps which draw on the screen and restarted my phone too.
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Wow, good call. I was having this same issue. Thanks!
Fix #2 - if it works
i was messing with my Samsung Galaxy J7 Core J701F/DS and I was trying to figure out your problem also because i got the same problem as yours so the thing that worked for me is going to Settings (Nougat 7.0/1)> Apps> 3-dot menu/optionsl settings/other settings> Special Access> Apps that can be on top> Disable all apps like literally disable them all and try to debug your phone again...if it works, enable apps in that setting one by one and repeat debugging process. If it doesnt work, disable the last app you enabled, and if it works again...that is the app that is doing the dirty work...mine was not in the system apps it was one of my apps which is AZ Screen Recorder lol....(why the app that is being used everyday need to be disabled....)
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Omg thank you so much for this. It was driving me bat**** crazy. I tried everything didnt even think this would cause it.
katerlouis said:
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
Click to expand...
Click to collapse
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
kapil1100 said:
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
Click to expand...
Click to collapse
This put me on the right track.
I have an LG G6 running Android 8.0. My Keeper Security app needs permission to Draw over other apps and since around December 2018 it has started acting 'flaky'. The app would warn me that I need to turn on this permission, but when I clicked "OK" in the Keeper app to take me to the Android setting for the app, it was always turned on. I could turn it ON/OFF, along with the setting that needed this permission in the Keeper app (called Keeper Fill) and eventually get it to work again, but it would always break again very soon after.
As I am getting ready to go on a trip, I installed Google's Datally app. It, too, wants me to turn on Draw over other apps, but when I tap "next" to be taken to the Android settings page to enable Draw over other apps, nothing happens (I usually expect an app detects it has been enabled and gives "success" message).
So I started disabling the 3 possible suspects listed by kapil1100. I had LG's Comfort View and some Accessibility options enabled, so I turned them off and: no change.
I disabled all other apps that have permission to Draw over other apps via: Settings > Apps & notifications > Special access > Draw over other apps, and: no change.
I use Evie launcher, so I went back to the stock one: no change.
I got thinking about what else could be modifying/accessing the screen and realized that LG has custom Home touch buttons.
I went to: Settings > Display > Home touch buttons > Hide Home touch buttons and DISABLED Show lock/hide icon and then tried enabling Draw over other apps for Datally and IT WORKED!.
I was then able to turn Show lock/hide icon back ON and everything has been working as expected. I suspect that, because I had Show lock/hide icon turned on during an upgrade, something got messed up and my turning it OFF and back ON fixed the issue.
I hope this helps someone!
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.