Its real power is the flexibility to combine contexts and tasks however you wish: ⚙No repetitive tasks for you, let your Android device handle it!⚙ The *asterisk in setting A2 are * given manually. The *asterisk in Mac and IP are fields left blank I also tried to give a comma after untrusted zone and before asterisk but still no luck Regardless of how you get the profile into the forum post, Description is the "format" you want to export in.ĥ Seconds Package: Name:Secure Settings ] If I usually choose Dropbox (you'll need Dropbox installed to do this) because the file is then automatically synced with my desktop and I can easily copy/paste the profile from the exported file into the forum post. This brings up a choice of apps to handle the exported file. When I need to do this, I long-press on the profile and select Export, the Description to Email. If you're having trouble getting your profile to work, your best bet is to post the profile here so others can see exactly what you're doing. Without the second comma (at the end), it will match untrusted zone, untrusted zone1, untrusted zonephone, etc. The reason I originally had the profile name bracketed by commas is that it specifies a complete profile name, and will only match if a profile named untrusted zone is active. What the statement above is doing is checking the %PACTIVE variable (the list of active profiles maintained by Tasker) to see if untrusted zone appears in that list. A single "Not Wifi Connected" profile with both an Enter and Exit task would possibly go the other way, meaning that if the device is turned off when out of range, then turned on when in range, the PIN might not be disabled (much safer than the other way, but still not ideal).Ĭlick to expand.Asterisks are wildcards, and will match any text of any length. The reason I'm using two separate profiles, instead of a single profile with both an Enter and Exit task is that by using a single "Wifi Connected" profile, if the device is turned off while the PIN lock is disabled, and next turned on when out of Wifi range, the PIN would remain disabled (the profile would not exit during shutdown, or during startup).The "Wait For Unlock" makes it so that if someone finds my phone, they can't simply bring it within range of my Wifi to unlock it - it must be unlocked once while connected, or already be unlocked when it connects, then it will remain unlocked for as long as it remains connected.The 30 second delay allows time to reconnect, in the event that I briefly go out of range.State: Not Wifi Connected Ī1: Wait Ī3: Secure Settings [ Configuration:Screen DimĪ4: Secure Settings State: Wifi Connected Ī1: Secure Settings
I haven't had any problems in the past 2-3 days. So in my task that enables the PIN lock, I use Secure Settings to turn the display on for 5 seconds immediately before enabling the lock. I found this to be unreliable with regard to locking the device after disconnecting from Wifi. What I'm doing is using the Secure Settings plugin to enable/disable the PIN lock based on Wifi connection. But if your Wifi Sleep Policy allows your Wifi to sleep when the device is off, you'll find that your Keyguard turns on each time your Wifi goes to sleep (because you're disconnecting from Wifi when Wifi sleeps).Īlso, the Tasker help indicates that Keyguard changes may not be reliable unless the screen is on and unlocked. If you leave Wifi on all the time, these two contexts may appear to almost identical on the surface. One thing I notice about your profile is that you're using the "Wifi Connected" context, whereas the profile in the Wiki uses "Wifi Near". I've been doing the something similar recently, and know others have done so before, but I wanted to do it on my own and learn from the process.
0 kommentar(er)
