Unlock with Wifi and Car now in Tasker Wiki

[UncleMike]

I uploaded my project that disables the PIN lock based on Wifi connection or car mode to the Tasker Wiki.  It builds upon my Extended Variables & States project that I uploaded last week.

Here's a link to the new project: http://tasker.wikidot.com/unlockwificar

[mark kal]

thanks just finished d-loading.   i'm sure all my personal information including passwords, credit card info, paypall, blah-blah is on its way.   ha!  

klidding aside.... thanks for this post.   instructions are great and easily followed.  i'm at a "trusted site" now.  but so far everything looks to be working as intended

i'm relatively new w/o lots of experience with tasker. have set up lots of ezpz profiles myself.   copied some from wiki. yours is most interesting. thanks for sharing!!!  exactly what i wanted.   but since i am new i'd kind of like to get a better understanding of the flow and process of what's going on under the hood.   what is the best way to folllow along? 

needless to say i am interested in any additional profiles you may be sharing.  will they be posted here?

mark

[UncleMike]

I'll generally post here any time I add something to the Wiki.

What's happening in the profiles used here is:

myTRUSTEDWIFI profile - if you're connected to one of the networks configured in that profile (a "trusted" network), the variable %myTRUSTEDWIFI is set to true.  If you disconnect, the exit task waits 1 minute, and sets %myTRUSTEDWIFI to false, but only if the myTRUSTEDWIFI profile is not active.  The net effect is that if you're connected to a "trusted" network, or have were connected less than 1 minute ago, the variable %myTRUSTEDWIFI is true, otherwise it's false.

myDISPLAY profiles - each time one of the Display events is triggered in Tasker (these are Display On, Display Off, and Display Locked), the variable %myDISPLAY is set to a value corresponding to the most recent Display event.  This allows us to, at any time, know the current state of the display (something you can't do with just an event).

myUIMODE profiles - if the device is powered and in an upright orientation and %myDISPLAY is unlocked, %myUIMODE is set to car.  If the device is powered and on its left side and %myDISPLAY is unlocked, %myUIMODE is set to desk.  If the device is not powered and neither of the previous two profiles are active, then %myUIMODE is set to normal.  The net effect is that once the device is powered and upright, or powered and on its left side, %myUIMODE will be set appropriately, and will remain set that way until power is removed.

Trusted profile - whenever %myTRUSTEDWIFI is true AND %myDISPLAY is unlocked, the PIN lock is disabled.

Car Mode profile - whenever %myUIMODE has a value of car and %myDISPLAY is unlocked, the PIN lock is disabled.

Untrusted profile - whenever %myTRUSTEDWIFI is false and %myUIMODE is not car, the PIN lock is enabled.

The net effect of these three profiles is that if the display is unlocked and, connected to a "trusted" network OR in car mode, the PIN will be be disabled.

I've been trying to find a good way to explain why the device must be unlocked before the PIN is disabled, and right now I'm equating it to "approving" the disabling of the PIN.  This more important in the car, since you don't want anyone finding your lost (and locked) device being able to unlock it simply by plugging it in and holding it upright.

[mark kal]

This more important in the car, since you don't want anyone finding your lost (and locked) device being able to unlock it simply by plugging it in and holding it upright.

can't imagine that dope would be reading your posts. xD  

running your project on a galaxy s3.   your script runs as intended on my phone.   that is to say flawlessly!  thanks.  

[UncleMike]

I don't necessarily think that anyone would know to plug the phone in and hold it upright to unlock it, but I think if someone finds a phone and intends to not return it, they'll likely plug it in at some point - but maybe not if they can't unlock it first.

[Fernando Pena]

Where to configure what are the trusted networks? Where should I put the SSID?

[Tyler Burton]

Nice work, UncleMike! I've been searching for a good intro to Tasker and this script does just that plus unlocks my phone while on WiFi.

However, I'm wondering if I'm experiencing an edge case. When it's on a trusted network, my PIN is disabled but I still have to press enter (as if I'm entering a PIN) to unlock it. Also, Secure Settings coughs up an error each time, saying: "An error occurred while executing Action: Password/PIN".

Anyone else seeing this? Know a workaround/solution/way to fix the error?

I'm on a Moto X.

Many thanks!

[UncleMike]

Do you have Secure Settings setup as a device administrator?  You may also want to edit and re-save all your Secure Settings actions that set the PIN - the actions are encrypted and if the key doesn't match, it won't work, though it should give you an error message indicating what the problem is.

[Tyler Burton]

Yep. I checked all the above and can confirm. I do know other folks with the Moto X had errors with the SkipLock app (which does basically the same thing) and had to work with the Dev to get them fixed. For all intents and purposes, though, the script does work, it just throws an error on execution. If I do figure out the reason/fix I will post it to the board. 

[J Willcox]

Hi UncleMike, hoping you can help me, I am new to android and tasker. I just downloaded your project and I am trying to set it up on my phone but struggling. I saw the part which says:

promisedlan*/z6hb7/w3wq2/1ae2bb/85qy2

And I am assuming I need to change that to match my network. I tried changing the promisedlan part to the name of wifi network, but do I need to change the other numbers to something? Currently I get a message that says: An error occured while executing action/pin!