[GUIDE] How to enable Ambient Display Proximity Wake feature on OOS - OnePlus 5 Guides, News, & Discussion

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?

Related

Screen off with timed prox sensor

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)

[GUIDE] How to turn on your phone without using your hands [S8/S8+][Other devices]

[UPDATED]
Hello guys,
A little introduction:
I'm an XDA user for quite a while now, but never started an own thread. As I like playing with mods like Xposed, magisk or, in this case Tasker, I'd like to share my profile with those who find it handy too. Also I think there're way more advanced tasker guides and tricks and this is rather easy, but I'd love to share it anyways with you
What does this profile do?
It's pretty simple and basic. This profile lets you magically wake your phone with holding your hand (for example) close to the approximity sensor, but also (only on S8/S8+) trigger the Iris scanner, which would usually need to be tapped on, since Samsung doesn't allow 3rd-party apps to wake the phone! But we'll get this anyways But here's a video. You will see what I mean:
Click here for YT video (XDA embedding doesn't seem to work here)
Requirements:
Magisk (root) (*note: If you have rooted your phone with another method Secure Settings won't work, due to lack of development)
Secure Settings (*note: If you know another tasker plug-in, which can wake the device feel free to take that)
Tasker of course
Within Tasker you need to set proximity sensor (Under UI) to "yes". This ensures, that the sensor won't be killed from doze or anything else
And of course you need a working Secure Settings App. Make sure System+ module is active and granted root (Works very well with Magisk). Because it's enabled by default, it might be necessary to disable and re-enable it
If you meet all the requirements: Let's start
So step 1 : Create a new profile in Tasker with 3 status:
Sensor -> Proximity sensor
Display [Turned off]
Variable -> Variable value = %ONLYONCE to Undone (This is important, so the screen will be woken up only once after you turned off your device and not every time you put your hands to the sensor)
Name the executed task "Wake device" for example and let it run: (Go on in step 2)
Step 2: The executing task of the profile you just created should run this:
Task -> Wait = 350ms (adjustable to your needs)
Plug-In -> Secure Settings -> Configuration -> Wake device = Screen dim 15 seconds (adjustable)
Variable -> Set variable -> %ONLYONCE to Done
Code -> Run shell -> Command = "input tap 840 190" (No quotation marks) [Use root = yes] (*note: this creates a tap input, as if you were tapping on that specific spot, and triggers the Iris scanner. Also make sure that tasker has root privileges)
Step 3: Create a 2nd profile with the event Display -> Device unlocked
The executed task to this profile should be:
Task -> Wait = 3 seconds
Variable -> Set Variable -> %ONLYONCE to Undone
And that's about it Any time you wave your hand over the proximity sensor now or let's say pull it out of your pocket the screen goes on, the Iris scanner is triggered and your phone unlocks
Please hit the thanks button if you could find any benefit of this Guide and the profile and please feel free to leave some feedback You can also import the profile to your tasker. I attached it at the bottom
*Note: All iris scanner related tasks and profiles can be adjusted to devices without Iris scanners, but this profile isn't that handy on other devices apparently

[GUIDE] Device Settings Menu | Part III - Display, Lock screen, Biometrics, Security

Device Settings Menu Guide, Tips & Discussions
Part 3 - Display, Lock screen, Biometrics and security​
If you're new to this series or want to see the index, please read the Introductory Post first.​
Display
Auto brightness: When you change brightness in Auto mode, your device is smart enough to learn your usage patterns to determine the best level according to the environment as per your preferences. 'Reset usage patterns' in case you think your phone is drunk when in Auto mode.
Blue light filter: Learn why you should use it here. I've set it to 'Turn on as scheduled' > 'Sunset to sunrise'. You can toggle it from the notification panel as well.
Night Mode: (Pie update) Enable it to make use of true blacks on your AMOLED screen, save battery and put less strain on eyes. I know you want it to only enable at night, so hop up to developer mode and set 'Night mode' to Automatic. I don't know why Samsung has put up such a useful mode here.
Screen mode: I've set it to 'Adaptive Display'. Do play with other modes and toggle them when needed. Customize 'Full screen colour balance' (and Advanced) when 'Adaptive Display' is enabled in case you don't like the default setup.
Font size and style; Screen zoom: I've set 'Screen Zoom' to 'Small' and 'Font Size' to Level 2 in order to get more content in a screen view. Please tell if there's any better font on Galaxy Apps.
Screen resolution: By default, you don't get the resolution enabled what your Note9 is capable of. I've changed it WQHD+ for getting the most out of the best display in the market. I've the resolution set to HD+ in Medium Battery Saver mode in case I'm on Survival mode.
Full screen apps: I customize it when needed for an app.
Screen timeout: Mine is set to 10 minutes. You know, pro users!
Home screen: Self-explanatory and I use Nova Launcher. Do enable 'Quick-open' notification panel.
Edge screen: Do you need a seperate guide for this? Or can anyone provide a link to one. If you use it right, this can make your life much simpler.
Edge panels: You can set a maximum of 9 panels. Explore options of each panel and try more of them from the Store. I've enabled Apps edge (also make app pair and folders), People edge (upto 10), Smart select (take portion screenshots, make screen GIFs, pin a screen's content), Clipboard edge (auto-categorizes items), Reminder, Device maintenance (useful to review device performance OTG), Tasks edge (explore all available tasks), Quick tools (must have), Calendar. Tap Menu and 'Reorder' the panels as per your needs. In 'Edge panel handle', I've set the Transparency to highest and Size to smallest. I've dragged the handle to Right near power button so that I can always guess where the handle is.
Edge lighting: For me, it feels great to have it for some very important notifications that too 'when screen is off'. Do note that if you enable it for screen on as well, it will disable heads-up notifications. Play with 'Edge lighting style' as it shows the effect generated as you customize one. For me, {effect=basic, color=app_color, transparency=low, width=narrow} works. You can customize the lighting color for each app separately as well. In 'Manage notifications', you can define those apps for which you want this effect enabled.
Menu > Quick reply: Do define a reply because it can be useful in cases where you can't or don't prefer to type or check messages.
Navigation bar: I've enabled 'Hard press Home button' (great alternative to physical home button) and set the pressure to lightest (since I don't want to hurt my screen). With Pie, you can enjoy the immersive display by setting 'Navigation type' to 'Full screen gestures' and disabling 'Gesture hints'. I eventually got used to this. You can use Nav bar button on Quick Settings by dragging down the notification panel to toggle showing navbar then.
Accidental touch protection: Really useful because I keep my phone screen faced to my leg side when inside pocket so that it's protected from the outside cruel world.
Screensaver: In case phone is your life even when it wants to get charged peacefully.
Lock screen
Screen lock type: I use Pattern with Biometrics (Intelligent Scan and Fingerprints or sometimes Fingerprints only). Fingerprints remain the best security and battery-efficient method till date atleast for me. Use Iris for more security than regular face recognition. Also, with Iris, your device won't get unlocked while you're sleeping or with your photo. Use 'Intelligent Scan' for bit more ease (read about it here).
Smart Lock: It's a Google feature that can unlock your phone via On-body detection, Trusted places/devices and Voice Match. I used it once with On-body detection but couldn't impress me. Read about it here.
Secure lock settings: Disabled 'Make pattern visible'. Set 'Lock automatically' to 15 seconds in case I want to turn on the screen immediately without unlocking it. Anyways, 'Lock instantly with power key ' is enabled when I explicitly want it to get locked. Use 'Auto factory reset' carefully as someone could initiate this by simply making incorrect attempts. I've enabled 'Lock network and security' especially for theft use-case.
Always On Display: For customizing it, go to 'Clock style' below. Guide on AOD here and video here. With Pie, you now have new display mode as 'Tap to show' AOD for 30 seconds. I've set it to 'show as scheduled' such it doesn't glow when I sleep. Also, I get an idea that it's time to get to bed when AOD stops showing up (same for wakeup).
Content to show: 'Home button and clock' feel elegant for me.
Double tap Home button: Changed to 'Quick launch Camera' since I want it more often and I can turn on the screen by hard pressing anyways.
Auto brightness: Enabled. If you are okay with manually controlling this brightness less often by double tapping the AOD clock, disabling can save you some battery.
Show always; Set schedule: If you often check clock at night, you can enable the former. I've disabled AOD during my night sleep schedule so that I additionally get a hint when it's already time to go to bed and whether it's time to get up or not.
Turn off to save battery: Enabled. Do you need AOD in survival mode too?
Clock style: You can customize AOD with different clock styles, pictures, GIFs, Calendar and roaming clocks. Blue 'colour' gives a soothing effect every time I look at the clock for me. Similarly, you can customize your Lock Screen clock style here.
Roaming clock: I had to disable it as every operator in India puts SIM to Roaming mode when you're out of your circle (mostly defined to a state) and I get two identical clocks whenever I travel out of state.
FaceWidgets: Enabled all available choices and will decide about the reordering or need of each of them after I arrive at the use-cases. Same goes for you maybe.
Contact information: Do fill it. I've include my name and number on it. Can be useful when stolen, lost or misplaced. You can include email or alternative mobile number as well since the primary number would probably be in the device itself.
Notifications: I've kept the defaults. 'Hide content' if you don't want people to read your notifications. I rather do this on per-app basis (like messages for OTPs, sensitive apps). 'Notifications icons only' makes it similar to AOD style notifications and I want description of notifications once I go over my AOD screen. Toggle 'Transparency' if you find it difficult to read notification over the wallpaper or want your wallpaper to expose. 'Auto-reverse text colour' makes it easier to adapt with the wallpaper. You can define 'Where to show' your notifications here (AOD or Lock screen or both).
App shortcuts: Define the two shortcuts you see on the bottom screen corners while on lock screen. You can choose any app though default (phone and camera) works for me.
Biometrics and security
Biometrics: You can remove biometrics data and configure 'Samsung Pass' to use these here. You can enable 'Screen-on' scan for making the device scan for your face/iris as soon as screen turns on. This increases brightness immediately while it's scanning (can be annoying) and will drain some battery. 'Samsung Pay' works only with 'Fingerprint' and 'Iris Scanner'. Try different ' preview screen mask' for 'Iris Scanner'. In 'Fingerprint Scanner', you can add as many as 4 fingerprints (reserve one for Secure Folder). Put your finger on the reader and you can see the detected one highlited.
Screen transition effect: Disabled as I want things at fastest.
Google Play Protect: Enabled. Read more here.
Find My Mobile: 'Remote controls', 'Google location service' and 'Send last location' enabled. This should be the first things to review once you buy the device. Prepare yourself with a demo on findmymobile.samsung.com.
Security update: Shows the patch level and gets updated with 'Software Update'.
Samsung Pass: Similar to 'Google Smart Lock' for passwords but with biometrics and less support as of now.
Install Unknown Apps: Allow/Disallow existing apps to install apps from APK.
Secure Folder: The replacement for Samsunh My Knox. Must use feature to serparate your very private and confidential part of the phone. Guide here and video here.
Secure startup: Disabled for me. Should be enabled if you want your SIM, notifications, alarms and anything related to device startup not to start without passing the lock screen after the device boots up. For the kind of short-term memory loss I have, I want to call my phone or want it recieve inputs if in any case it gets misplaced with maybe low battery.
Encrypt SD card: Okay, so your phone is secured by Knox or 'Device encryption'. What about your SD card? Anyone can take it out and access your data, right? Encrypt it here and it won't be accessible to any device beside yours. Be careful to decrypt it in case you want to use it somewhere else or even when you are going to format your device.
Other security settings: 'Set up SIM card lock' disabled (same reason as in 'Secure startup'), 'Make passwords visible' disabled, 'Security policy updates' auto update enabled (Here is what are these), 'Send security reports' enabled. Set 'Device admin apps' with care (Learn about them here in case you haven't). You need to remove an app from here before uninstalling it. 'Creditial Storage' for CAs and user certificates (Learn more about CAs here). 'Pin windows' is a very useful feature for me. In cases where you need to give your device to someone (for like watching a movie or seeing the gallery), if this is enabled with 'ask for pattern before unpinning', when you 'pin' that app (video player or gallery), people will have to pass the lock method to get out of that app. Configure which apps can have 'Usage data access', 'Notification access' and 'Do not disturb permission'.
Location:
Allow apps and sites to detect your device's location. I've enabled it since I use too much location-specific content. You can turn it off if you suspect your dad working in NSA (approx locality can still be tracked through IP, use VPN).
Locating method: Change the method as per your requirements. I use 'High accuracy' while you can use 'Battery saving' to save a significant amount of battery that GPS uses. I simply turn off 'Location' from the notification bar when not needed or during survival mode.
Improve Accuracy: You can turn this off for WiFi and BT in case you don't want apps to override your decision of not making them search for WiFi or BT when you have explicitly turned them off!
Recent Location Requests; Location Services: Do review the apps that your girlfriend may have installed in your phone; Do review Google Location History and Sharing settings.
App permissions; Permission usage monitor: You can review the 'Permission History' here and enable/disable notifications for permission access on per-app per-permission basis. You suspect an app tracking your location occasionally and want to prove this instead of not granting it the permission? You can do it here.
-- Reserved for FAQs --
Why are you posting this??
There's a very good "USER MANUAL" on the "Samsung"-site available:
User Manual Samsung Galaxy Note9
henklbr said:
Why are you posting this??
There's a very good "USER MANUAL" on the "Samsung"-site available:
User Manual Samsung Galaxy Note9
Click to expand...
Click to collapse
You have commented the same query on each of my parts. I have already answered you here where the similar discussion is already going on. Let's discuss there and keep this thread clean. Also, the 'why am I posting this' is already described in the Introductory Post.
thanks, op for the posts, very useful

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

In android 10,a new feature called as TURN ALL SENSORS OFF is available in developer settings. It also has a qs tile.
Is there a way to automatically enable this feature upon screen off and then disable upon screen on?
The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.
ktmom said:
The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.
Click to expand...
Click to collapse
1) In android 10,there is an option to disable all sensors in developer options. So i turned it on last night, and battery drain was less than 2 % in 4 hrs, compared to 1% per hour usually, with volte and 4g data on. I would get more accurate stats later on.
There's a qs tile available to activate it.
What I want to ask is, is there a way to automatically enable it every time the screen goes off, and then disable it when screen goes on, without any user input?Either as a shortcut or as a qs tile.
2) I am afraid i don't have enough knowledge to exactly understand the steps you are telling. Do you know of a pre made recipe to execute this. I tried to search but in vain. Or if you are on android 10,maybe you can try doing what i need.
Thank you.
There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.
ktmom said:
There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.
Click to expand...
Click to collapse
Will follow the steps. If I encounter any issues, will reply back here.
Big thanks.

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.

Categories

Resources