Database Develop

Open app profile without Tasker accessibility services

Hello!
I have a question about profile to execute task when opening or closing app without accessibility services turned on.
So I want my phone to automatically do some stuff when I open a particular app.
Is is possible to detect app open or close without enabling Tasker accessibility sercice.
Why I want this? I have Nexus 5x rooted with TWRP, so I want encryption enhanced with my password, which is not possible when one have any accessibility service enbled.
So, is there a way to detect app opening or closing without tasker accessibility service?
Thank you!

How experienced are you? You can use this as a guide, but since oom_adj values behave differently for other devices, you'll need to take the concept and modify it to your needs...but yes, you can create your own looping task to detect the launch or closing of any app. Here's how I detect that Tasker has closed:
Code:
Detect Tasker (355)
Run Both Together
A1: Variable Set [ Name:%newline To:
Do Maths:eek:ff Append:eek:ff ]
A2: Variable Set [ Name:%space To: Do Maths:eek:ff Append:eek:ff ]
A3: Run Shell [ Command:ps Timeout (Seconds):0 Use Root:eek:ff Store Output In:%apps Store Errors In: Store Result In: ]
A4: Variable Split [ Name:%apps Splitter:net.dinglisch.android.taskerm Delete Base:eek:ff ]
A5: Variable Split [ Name:%apps1 Splitter:%newline Delete Base:eek:ff ]
A6: Variable Set [ Name:%last To:%apps1(#) Do Maths:eek:ff Append:eek:ff ]
A7: Variable Set [ Name:%taskerpidline To:%apps1(%last) Do Maths:eek:ff Append:eek:ff ]
A8: Variable Split [ Name:%taskerpidline Splitter:%space Delete Base:eek:ff ]
A9: Variable Set [ Name:%taskerpid To:%taskerpidline4 Do Maths:eek:ff Append:eek:ff ]
A10: Run Shell [ Command:cat /proc/%taskerpid/oom_adj Timeout (Seconds):0 Use Root:eek:ff Store Output In:%oom Store Errors In: Store Result In:%Aresult ]
A11: Flash [ Text:%oom Long:eek:ff ]
A12: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A13: Goto [ Type:Action Number Number:1 Label: ] If [ %oom < 2 ]
A14: Write File [ File:DetectTasker/shutdownlog.txt Text:%DATE %TIME Append:eek:n Add Newline:eek:n ]
You'll need to change A4 to the package name you want and insert a flash of %oom in the loop so you can understand how the value behaves for you when opening and closing the app...then change the check on A13 to what works for you. A14 writes a file, so you could use a File Modified context to trigger whatever tasks you want.
Sent from my SM-G928C using Tapatalk

Well, to be honest, I am not that experienced, and this is a bit too much for me.
Specifically I want to automatically execute some tasks when opening and closing Nexus 5x Camera app (stop music playing when opening and opening Snapseed when closing and other). I know that this is not very serious life dependant stuff, but Tasker is all about making life easier ?. Tasks are easy to create, but I am not knowledgeable enough to understand everything you proposed.
Thank you for your effort anyway!

deleted

kurci2 said:
Well, to be honest, I am not that experienced, and this is a bit too much for me.
Click to expand...
Click to collapse
No worries. One of the beautiful things about Tasker is that there's almost always multiple ways to achieve your intended result.
kurci2 said:
Specifically I want to automatically execute some tasks when opening and closing Nexus 5x Camera app (stop music playing when opening and opening Snapseed when closing and other).
Click to expand...
Click to collapse
If you really want this and feel overwhelmed by the shell scripts above, you can probably avoid trying to detect the camera app altogether by making a shortcut out of your task and using it to launch the camera instead of the app icon. Set an icon and save a shortcut to your desktop or whatever that turns off the music and launches the camera. Always use that shortcut icon to open your camera app instead of the camera app's icon.
You could do a variety of things to avoid detecting when the camera closes. You could make a task that runs the tasks you wish to perform when camera closes, then kills the camera itself... And you could display an invisible overlay scene that performs that task when you long press it....or you could use Xposed Additions module to map that task to the Back and Home buttons... Lots of options there.
kurci2 said:
I know that this is not very serious life dependant stuff, but Tasker is all about making life easier ?. Tasks are easy to create, but I am not knowledgeable enough to understand everything you proposed.
Thank you for your effort anyway!
Click to expand...
Click to collapse
Overcoming these kinds of challenges is what helps you master Tasker. [emoji2]
Sent from my SM-G928C using Tapatalk

RuggedHunter said:
Overcoming these kinds of challenges is what helps you master Tasker. [emoji2]
Click to expand...
Click to collapse
Hello again!
I have started to learn tasker, but I am only at basics. For example I configured WiFi ON/OFF based on cell towers around me and I automated SMS backup.
But I am still far away from understanding your script (for example I do not know what to write in "To:" section and I do not know that does ff mean).
Before I had multiple wishes for tasker to do. I wanted it to automatically make all the pictures black and white when would enable that profile, but I found other quick ways with Snapseed and photoshop. After that I wanted automatic photo uploading and then I figured that Google Photos is the greatest of them all and already automatic. Etc.
There is only one thing left that I can not solve without this tasker script. I want to turn off camera sounds. I know about deleting camera sounds in system folder, but if one uses HDR that is not effective, because HDR makes its own sound. Those camera sounds are really annoying to me.
So I am asking you if you can help me to create a tasker profile and task to enable Do not disturb mode when camera app is opened and restore to previous volume setting when camera is closed. I use stock Google Camera on Nexus 5X, and I think this is the best and most straight forward android camera app.
So my question is if you can help me to configure this profile. This is kind of my last thing from Nexus perfetion .

[SOLVED] - Accessibility services and password enhanced encryption
Hello!
I have managed to solve my problem and I want to share it with everyone else who (like myself) does not know this workaround.
Issue description.
So as I mentioned, I have a rooted Nexus 5X with TWRP recovery (like many other here I am sure). As we know, to protect my data form beeing accessible directly via TWRP one must have "Password enhanced encryption". But the problem is, that when one enables any of the Accessibility Services the message pops uot, that the following action will disable "Password enahnced encryption" - unacceplteble security issue for some.
Solutin.
It turn outm that you can easily re-enable "Password during boot" option in security.
Steps:
Settings --> Accessibility --> Enable any of the services you want (Tasker in my case).
You will get the message stating: "If you turn on Tasker, your device won't use your screen lock to enhance data encryption."
For now you just click OK and procede. Note, that your device encryption is now not password enhanced.
It turns out, that one can just re-enable password protected encryption back in security settings.
Settings --> Security --> Screen Lock --> Chosse which one you perfer --> Enable "Reqire password to start device" and voila
You will see a message saying that the service won't be accessible till the device fully boots, but after that everything runs perfectly.
So, that's it.
It turns out, that I actually do not need all these comlicated Tasker scripts after all.
I would like to thank everyone for help. (Reddit source: https://www.reddit.com/r/Android/comments/3vry8k/users_running_lollipop_or_newer_may_be_using_a/)

Hi, I tried Tasker on encrypted device and now I uninstalled Tasker, reboot and TWRP + boot don´t wont PIN. It seems like device is not encrypted now. But in settings - security is "encrypted". How can I fix it? Thanks
---------- Post added at 11:26 AM ---------- Previous post was at 11:17 AM ----------
I can´t find "Password during boot" option. I have Pure Nexus (7.1.1_r21). Now I uninstall Tasker, reboot but TWRP / Boot don´t requite PIN. Settings - security says encrypted. How can I fix it please?

[Guide] OnePlus 3 custom Tasker shell commands

*This requires root!*
So i was tweaking around with Tasker and I came across this tutorial online: http://www.notenoughtech.com/tasker/tasker-run-shell-commands
I decided to use the 3 commands he uses to make a list of shell commands that we can use. Basically this will allow you to change settings that are only found in Oxygen os and thus you can't normally change within Tasker. (I recommend you check out the page and try some things for yourself. There are more settings like these. The ones below are just the ones I thought would be most useful.)
Some examples of what you could use this for: A better power saving mode that disables all gestures and backlighting. Or automatically lock the hardware buttons when watching a show or movie, etc. This is not a guide for Tasker. If you don't know how Tasker works then I recommend you go watch some tutorials on YouTube. It definitely has a learning curve, but it is 100% worth it.
To add the shell script in Tasker:
create a task>'+' button>Code>Run Shell>enter the command line
Make sure you select the 'use root' checkbox, otherwise this will not work!
I've tested all of the commands below (on Oxygen os 4.0.3), however I'm not responsible for any damage that might occur to your phone.
Lock hw buttons
(You don't get the notification to re-enable the buttons. To do so you have to toggle the quick tile. Keep this in mind!)
On: settings put system oem_acc_key_lock_mode 4
Off: settings put system oem_acc_key_lock_mode 0
[Choose any percentage. If you go to battery settings and then tap 'Turn on automatically', it will set the value to 0. (So if you want to keep your settings, don't do this.)]
Auto enable battery saver at XX%: settings put global low_power_trigger_level XX
Capacitive button backlight
On: settings put system buttons_brightness 1
Off: settings put system buttons_brightness 0
Seconds in the clock
On: settings put secure clock_seconds 1
Off: settings put secure clock_seconds 0
Advanced reboot
On: settings put secure advanced_reboot 1
Off: settings put secure advanced_reboot 0
Double click power for camera
On: settings put secure
camera_double_tap_power_gesture_disabled 0
Off: settings put secure camera_double_tap_power_gesture_disabled 1
[For the button commands you can set it to multiple values (0-10). Below is a list of what the values mean. Replace the 'X' in the command line by the number of your choosing.]
0=No Action
1=Open/Close Menu
2=Recents
3=Search Assistant
4=Turn Off Screen
5=Open Camera
6=Voice Search
7=Open Last Used App
8=Open Shelf
9=Open/Close Notification Center
10=Open/Close Split Screen
Button Commands:
Long press home: settings put system key_home_long_press_action X
Double tap home: settings put system key_home_double_tap_action X
Long press Recents: settings put system key_app_switch_long_press_action X
Double tap Recents: settings put system key_app_switch_double_tap_action X
Long press back: settings put system key_back_long_press_action X
Double tap back: settings put system key_back_double_tap_action X
Screen on Gestures
Flip to mute
On: settings put system
oem_acc_sensor_rotate_silent 1
Off: settings put system
oem_acc_sensor_rotate_silent 0
3 Finger screenshot
On: settings put system
oem_acc_sensor_three_finger 1
Off: settings put system oem_acc_sensor_three_finger 0
[The screen off gestures work a little different. Every gesture has a certain number (written below). You have to add up the values of the gestures you want to have enabled. So everything enabled is 128+64+1+30=223 and nothing enabled is 0+0+0+0=0. Replace the 'XXX' in the command by the value you get.]
Double tap to wake=128
Open camera=64
Toggle flashlight=1
Music control=30
Screen off gesture: settings put system oem_acc_blackscreen_gestrue_enable XXX
I've tested these on Oxygen os 4.0.3. I'm not sure if they work on other versions/on the OnePlus 3t. I believe that the 'seconds in clock' and the 'lock hw buttons' weren't available before. So I doubt that those will work on marshmallow versions of Oxygen os (aside from maybe the marshmallow open beta). The others should be fine.

[Help] Combine AOD & Ambient Display

Hi everyone!
I'd like to have a new feature to my S7 Always on Display, kind of like Motorola did with their Ambient Display.
In particular I want to toggle the AOD on and off when the display is off by waving over the proximity sensor or double tap on the display.
And as an extra (nice to have but not absolutely necessary), it would be nice to turn AOD on when I grab my phone and I have notifications.
I've tried my best, but the AOD won't get to work when the display is off. So I hope here are some talented users who can do something like that (or even have it already done).
I appreciate every help from you guys.

If you're rooted I used tasker to do exactly this. I could export an apk file for you.
I have a few versions:
- wave hand over proximity and AOD turns on for 10 seconds, then back off
- AOD turns off when proximity covered (so it's not on in your pocket) and turns back on when proximity uncovered.
- wave hand over proximity and wake to lockscreen
- wave hand over proximity to unlock (requires longpress home to unlock option enabled)
Edit: Wow...i just realized this IS the tasker forum, sorry!
Run Shell [settings put system aod_mode 0] use root: on
That will turn AOD off, if it's currently displayed
To turn it on, you set to 1 but its a little more tricky... you have to toggle the screen on/off after setting aod_mode to 1....but that will make your screen flash on for a split second (which you dont want)....so.... create a full screen, black scene...show the scene before toggling screen on and destroy it after toggling screen off..... you'll never know...
Code:
Profile: Proximity AOD Off (595)
State: Proximity Sensor
State: Display State [ Is:eek:ff ]
Enter: AOD Off (621)
A1: Run Shell [ Command:settings put system aod_mode 0 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
Exit: AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, Full Display, No Bar Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Button:eek:ff Show Over Keyguard:eek:n Continue Task Immediately:eek:n ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
- wave hand over proximity and AOD turns on for 10 seconds, then back off
- AOD turns off when proximity covered (so it's not on in your pocket) and turns back on when proximity uncovered.
Click to expand...
Click to collapse
Wow, that seems to be pretty complicated. Could you upload the xml file for the quotes things above for me? That would be great

ichbinich said:
Wow, that seems to be pretty complicated. Could you upload the xml file for the quotes things above for me? That would be great
Click to expand...
Click to collapse
Its really not all that complicated. Here ya go:
Air AOD
Proximity AOD Off
Blocking Scene
?
Of course, you don't want to use both of these at the same time.... they're sorta opposites. If you keep AOD Off normally and want it took appear for 10 seconds when you wave your hand, use AOD. If you keep AOD On normally and want it to turn off when in your pocket, etc...Then back on when out of pocket...use Proximity AOD Off.
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
Its really not all that complicated. Here ya go
Click to expand...
Click to collapse
Thank you very much for sharing, I really appreciate that. But for some reason I cannot import those because they are invisible when I want to select them for importing. Any suggestions on that?

Make sure you've put the files in the proper folders.
/sdcard/Tasker/Profiles
/sdcard/Tasker/Scenes
Sent from my SM-G955F using Tapatalk

Thanks! It's working pretty well but is it the same with your device?
- After waving over the proximity sensor it takes about 5 seconds or so for AOD to show up
- Before AOD shows up, the light of softkeys as well as a SuperSU message are showing up for a short time

It takes a second or two, yes. If you're seeing soft keys and/or toasts, then the blocking scene probably needs to be tweaked for display size. Play around with it, you'll get it.
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
It takes a second or two, yes. If you're seeing soft keys and/or toasts, then the blocking scene probably needs to be tweaked for display size. Play around with it, you'll get it.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
I set the scene up with my size (1080x1920) but I still get this:
1) less than 1 second the lockscreen (or homescreen, cannot say properly, it goes that fast)
2) SuperSU toast + softkey lights
3) black screen
4) than finally the AOD
that is awkward that it doesn't work properly on my device. Do you have any further ideas what I can check in order to get it working?

ichbinich said:
I set the scene up with my size (1080x1920) but I still get this:
1) less than 1 second the lockscreen (or homescreen, cannot say properly, it goes that fast)
2) SuperSU toast + softkey lights
3) black screen
4) than finally the AOD
that is awkward that it doesn't work properly on my device. Do you have any further ideas what I can check in order to get it working?
Click to expand...
Click to collapse
Hmmm.... I'm really not sure. Which profile are you using...Air AOD or Proximity AOD?
Are you saying that the display turns on and you see the whole lockscreen.... then it goes black except for the nav buttons and toast?
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
Hmmm.... I'm really not sure. Which profile are you using...Air AOD or Proximity AOD?
Are you saying that the display turns on and you see the whole lockscreen.... then it goes black except for the nav buttons and toast?
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
I'm using the Air AOD. Please look at the attached video (the softkey lights starting at the moment when the lockscreen is on).

ichbinich said:
I'm using the Air AOD. Please look at the attached video (the softkey lights starting at the moment when the lockscreen is on).
Click to expand...
Click to collapse
I see...The purpose of the blocking screen is to prevent that from happening. I think if you turn that Wait action on in A4 it might work for you.
However I see that the profile I linked is an old version that I must have uploaded a while ago...it doesn't match the description that I posted above. It shouldn't be the reason you're having problems, but I recommend deleting that profile from Tasker and from /sdcard/Tasker/ then import this one. Sorry about that.
https://www.dropbox.com/s/3zpgje43mhijxh6/Air_AOD.prf.xml?dl=0
I anticipate you'll have the exact same issue. If so, if you insert a Wait Acton between A2 and A3 for 1 sec or so, I think it'll work.
Sent from my SM-G955F using Tapatalk

Unfortunately that didn't change anything.

ichbinich said:
Unfortunately that didn't change anything.
Click to expand...
Click to collapse
Huh, I'm out of ideas unfortunately. Sorry it's not working for ya. It works well on my s8+
Sent from my SM-G955F using Tapatalk

Hello, @RuggedHunter
I'm sorry for bumping a 6+ months old topic but I think you can help me out with my problem. Here goes:
AOD is set to be 'Always' on from its settings.
I am using the second option from this tutorial: https://www.xda-developers.com/automatically-toggle-samsungs-always-on-display-when-charging-app which toggles the AOD option to on when the device is lying on a table for example with the screen facing upwards and toggles it off if this condition is not met. Now this works perfectly, but my problem is as follows.
If the screen is turned off, the new AOD setting won't take effect unless I turn the screen back on and turn it off again. So, for example, if my phone's in my hand and AOD is off with the screen off, when I leave it on the table facing up AOD won't show up, despite the proper condition being met. Now I tried the SecureSettings plugin way to wake up my screen for 1 sec but that didn't work at all for some reason. Could you help me out with this thing, please? I saw that you've made some black overlay and turn on the screen then apply this blocking overlay until it turns back off, but I'm no expert with Tasker so it was a bit confusing. Would you explain to me what to do in Tasker (step-by-step if possible, I know the basics things like how to make profile, task, etc btw) in order to make that AOD switch profile work perfect (aka to set aod_mode, turn on screen, show black blocking overlay while it's on, turn, screen back off, destroy overlay when screen turns off)?
Sorry for such a long post, I'm using a ported S8 ROM on my Galaxy S5 called Nemesis Reborn V4 but the "aod_mode" stuff works so anything S8 should.

@koragg97 yeah I had the same problem and worked around it like this... Here's my AOD ON task. The blocking scene is just a full display overlay blocking that is all black #FFFFFF and the keyevents toggle the dismay on/off quickly... they can both be 6 if you want.
AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, No Bar, No Status Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Buttonff Show Over Keyguardn Continue Task Immediatelyn ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk

RuggedHunter said:
@koragg97 yeah I had the same problem and worked around it like this... Here's my AOD ON task. The blocking scene is just a full display overlay blocking that is all black #FFFFFF and the keyevents toggle the dismay on/off quickly... they can both be 6 if you want.
AOD On (622)
A1: Run Shell [ Command:settings put system aod_mode 1 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A2: If [ %SCREEN ~ off ]
A3: Show Scene [ Name:Blocking Display As:Activity, No Bar, No Status Horizontal Position:100 Vertical Position:100 Animation:System Show Exit Buttonff Show Over Keyguardn Continue Task Immediatelyn ]
A4: Run Shell [ Command:input keyevent 1015
input keyevent 6 Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A5: Destroy Scene [ Name:Blocking ]
A6: End If
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Had to change the keyevent apparently but it works nicely. I also made a check so that it works just when the phone is locked to prevent accidental screen turn off if I cover the proximity sensor when I'm just using the phone. Also added an InCall safeguard since phone is technically locked during a call and the power button simulation ends the call lol

[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

Setting pin when away from home? Not quite working.

I have a profile to set a pin code when I am not near my home WiFi, using Secure Settings. It seems to work except the pin doesn't activate until I unlock the screen and relock it. Is there another step I need to have tasker do to jump start this.
Sent from my SM-T820 using Tapatalk

That's expected behavior. You can leave the pin always set and use a tasker shell action to set the lock screen timeout to a ridiculously long period at home. The command with a 10 day time out would look like:
settings put secure lock_screen_lock_after_timeout 86400000
Then the exit task would set the timeout back to a sane number:
Settings put secure lock_screen_lock_after_timeout 5000
notenoughtech.com has a write-up on using the shell in tasker to replace secure settings.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Thanks. Unfortunately looks like that requires root. My phone is unrootable last I checked into it.
It actually does work once I turn screen on and back off since setting pin doesn't require root. Next step I'm going to see if having tasker turn the screen on and back off after setting the pin.
Disabling the pin when I'm back home works without issue.
Sent from my SM-T820 using Tapatalk

The AutoTools (paid) plugin for Tasker has a secure settings replacement. It doesn't require root, but gets permissions set through ADB commands.
In the tasker action:
plugins -> autotools -> secure settings
You can configure:
lock screen -> automatic lock
And set the time out for the lock screen similar to what I did above. It basically sets the same command I'm doing through the shell but doesn't require root.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

in my experience, this plugin Profile Shortcuts for LineageOS is the best to achieve this Secure Settings or AutoTools, you will have to depend on your ROM though, and cannot backup the profile.
Create 2 system profiles, leave everything unchanged, just use
Don't ask for PIN or password
and
Use system default
As Android is getting more and more 'secured', we user have less options to mess around on a system level. This method uses native system function, do it should work without problem.