Has anybody figured out how to turn the knock code on/off using Tasker? I would like to turn security off when I'm on WIFI and back on when I'm not. I know how to do it with a PIN but not with knock code.
It should work regardless of pin or knock knock code.
I have my set up the same way. To disable lock screen when connected to a particular Wi-Fi and enable when disconnected. When I get in front of a computer I will add more details for me set up.
cpatel112 said:
It should work regardless of pin or knock knock code.
I have my set up the same way. To disable lock screen when connected to a particular Wi-Fi and enable when disconnected. When I get in front of a computer I will add more details for me set up.
Click to expand...
Click to collapse
Thanks, that would be really helpful
Lockscreen Enable/Disable
cpatel112 said:
It should work regardless of pin or knock knock code.
I have my set up the same way. To disable lock screen when connected to a particular Wi-Fi and enable when disconnected. When I get in front of a computer I will add more details for me set up.
Click to expand...
Click to collapse
First you will need two (2) Tasks Set up
Disable Lockscreen Keyguard Set Off
[a] In the task column: Hit the + button>Display>Keygaurd>Set to off
Enable Lockscreen: Keyguard Set On
In the task column: Hit the + button>Display>Keygaurd>Set to on
The Profile it self. I have mine set up to when I am, connected to my network(s) to disable the lockscreen
+ Button> State>Net>Wifi Connected
In the SSID Type in the SSID of the networks where you would like the lockscreen disabled. If you have multiple SSIDs separate them with "/", for example: XDA 1 and XDA 2 as SSIDs Type in "XDA 1/XDA 2" with out quotation marks.
Have Disable Lockscreen as the Enter Task and Enable as the Exit Task.
cpatel112 said:
First you will need two (2) Tasks Set up
Disable Lockscreen Keyguard Set Off
[a] In the task column: Hit the + button>Display>Keygaurd>Set to off
Enable Lockscreen: Keyguard Set On
In the task column: Hit the + button>Display>Keygaurd>Set to on
The Profile it self. I have mine set up to when I am, connected to my network(s) to disable the lockscreen
+ Button> State>Net>Wifi Connected
In the SSID Type in the SSID of the networks where you would like the lockscreen disabled. If you have multiple SSIDs separate them with "/", for example: XDA 1 and XDA 2 as SSIDs Type in "XDA 1/XDA 2" with out quotation marks.
Have Disable Lockscreen as the Enter Task and Enable as the Exit Task.
Click to expand...
Click to collapse
is there a way to do this exactly as is if there is an exchange email account on the phone? I wouldnt mind having a password lock when im not home but at home its just damn annoying.. right now i have exchange lock disabled completely
theraker007 said:
is there a way to do this exactly as is if there is an exchange email account on the phone? I wouldnt mind having a password lock when im not home but at home its just damn annoying.. right now i have exchange lock disabled completely
Click to expand...
Click to collapse
Not sure I that. But I don't think it would matter if you have exchange or not. But I haven't used it so not sure.
I have Gear Fit and I can't get to work with my G3 when I have set Knock Code. If I don't have any security on lockscreen everything is working good. Here is my settings. Could you please check it. Thanks.
These are working settings without Knock Code (sceen_1 and screen_2). And here are settings which are not working for me when I have Knock Code (screen_1 and screen_2)
I would appreciate your help.
If you are using Xposed then try "no lock home" module, this works perfect!
cpatel112 said:
First you will need two (2) Tasks Set up
Disable Lockscreen Keyguard Set Off
[a] In the task column: Hit the + button>Display>Keygaurd>Set to off
Enable Lockscreen: Keyguard Set On
In the task column: Hit the + button>Display>Keygaurd>Set to on
The Profile it self. I have mine set up to when I am, connected to my network(s) to disable the lockscreen
+ Button> State>Net>Wifi Connected
In the SSID Type in the SSID of the networks where you would like the lockscreen disabled. If you have multiple SSIDs separate them with "/", for example: XDA 1 and XDA 2 as SSIDs Type in "XDA 1/XDA 2" with out quotation marks.
Have Disable Lockscreen as the Enter Task and Enable as the Exit Task.
Click to expand...
Click to collapse
For some reason this doesn't really work - most of the time, sometimes it does. The tasks work fine if I run them but after a while the lock/keyguard is activated again for no obvious reason. What can I have done wrong?
Do you have another Profile set up, which toggles Wi-Fi?
That may cause it to not work appropriately.
Also, I have noticed if Disable Task is running, and you hit the "Home" Button, so some reason the task stops working.
Hi i have a similar question how do i set up a profile with tasker that when im on a trusted WIFI the knock code is disabled but to still have the lockscreen but with swipe?
im new with tasker thanks in advance for the help.
People I think knock code is a feature of the rom itself and for that tasker does not have that ability if you are running stock rooted. I am running the lastest CyanogenMod 12 and I got working perfectly a similar tasker profile. This is made posible by Cyanogen.
hi cpatel112
I have my profile setup as you defined and it works.
however, i have noticed that after a while, when i click on my home button on LG G3 it does not go to homescreen but flashed up my lock screen and then goes back to previous screen
also the recent apps button does not work - only the back button works
any ideas why this may be happening and did it happen for you too?
thanks
litfoo
cpatel112 said:
Do you have another Profile set up, which toggles Wi-Fi?
That may cause it to not work appropriately.
Also, I have noticed if Disable Task is running, and you hit the "Home" Button, so some reason the task stops working.
Click to expand...
Click to collapse
I am not sure as to why it does that to be honest with you. I have disable that profile. In order to have the nav buttons working as they should be, for some reason when you hit any of those it will take you to the lock screen. And for them to work as well, you have to go through the step.
litfoo said:
hi cpatel112
I have my profile setup as you defined and it works.
however, i have noticed that after a while, when i click on my home button on LG G3 it does not go to homescreen but flashed up my lock screen and then goes back to previous screen
also the recent apps button does not work - only the back button works
any ideas why this may be happening and did it happen for you too?
thanks
litfoo
Click to expand...
Click to collapse
Related
I have Googled this to death. Some sources say it can be done, some say not without root, some say not at all. I don't know what to think. I've tried so many things. I'm not a total noob, but I am certainly not as educated as you guys are about Android. I'm just learning. Please go easy on me. Also, I put this here because it seems, from my research, to be an issue with S2 and S3 phones, not Tasker itself. Please let me know, however, if you feel I should move it, Mods.
What I want to do is to disable the PIN lock on my phone when I'm at home on our wifi and in the car. No reason to unlock my phone every time I want to use it at home and I can't get voice commands to work consistently when it's locked in the van. With a teen driver watching my every move, I don't want to touch the phone.
Here are the details:
*I'm stock, unrooted
*I'd rather not root, because (unlike my Vibrant!) this phone works fine the way it is. That being said, I'd do it if it finally. Makes. This. Work!
*I've tried this with NFC tags and NFC Task Launcher
*I'm using Tasker
*I've tried it with and without Secure Settings
For the van, I always have it plugged in, so I think I can accomplish this by just setting the screen to not time out.
Home is the real issue. Sometimes I can get it to work, but it never *stays* working. I've tried turning my PIN Lock and all lockscreens off via my device settings and setting a task that triggers when I leave "HomeWifiName" to 1. Secure settings, configuration, set PIN 2. Secure Settings, configuration, keyguard enabled. It doesn't work at all. I've tried so many other variations of this I can't list them.
I wonder if I'm getting confused between the PIN and the keyguard. Is there a difference between the lockscreen and keyguard?
I'd really appreciate any advice you guys have for me.
If using the pin lockscreen, that is key guard in Tasker.
So key guard off = no lock screen at all. You don't need Secure Settings for this anymore. But you may need root.
Now, regarding your wifi near context, that doesn't work for me either. It's unreliable at best. Instead, use if connected to X wifi network as your context.
Let me know if you need any more help.
Aerowinder said:
If using the pin lockscreen, that is key guard in Tasker.
So key guard off = no lock screen at all. You don't need Secure Settings for this anymore. But you may need root.
Now, regarding your wifi near context, that doesn't work for me either. It's unreliable at best. Instead, use if connected to X wifi network as your context.
Let me know if you need any more help.
Click to expand...
Click to collapse
Thank you very much for this. I'd rather use connected not just near, so if I leave the house I'm protected.
If I do that, set it to keyguard off in Tasker while connected to our wifi, it works once or twice, but not consistently. I have the exit task to enable keyguard when I disconnect.
Am I missing something? Honestly the challenge of figuring this out has now become more important to me than actually getting it to work.
I had a profile that did this for a while, but I felt like it was a security risk. I just don't feel comfortable with that level of automation. But to each his/her own. When I typed the first post I was on my phone. On PC now so I can elaborate a bit.
New Profile > State > Net > Wifi Connected. I entered all 3 details; SSID, MAC, and IP. You can get it all right from the little scan applet that is already on your screen.
It's entry task will be Keyguard > Off
It's exit task will be Keyguard > On
So when you are connected to your home wifi, keyguard will be off. And when it disconnects, keyguard is turned back on. If this doesn't always work in this configuration, then it should be considered unreliable and not used. If this is the case, it's an issue with the app, not with your Tasker-fu. But with Tasker 4.0, you no longer need Secure Settings for a lot of things. Keyguard being one, GPS control being another big one.
Aerowinder said:
I had a profile that did this for a while, but I felt like it was a security risk. I just don't feel comfortable with that level of automation. But to each his/her own. When I typed the first post I was on my phone. On PC now so I can elaborate a bit.
New Profile > State > Net > Wifi Connected. I entered all 3 details; SSID, MAC, and IP. You can get it all right from the little scan applet that is already on your screen.
It's entry task will be Keyguard > Off
It's exit task will be Keyguard > On
So when you are connected to your home wifi, keyguard will be off. And when it disconnects, keyguard is turned back on. If this doesn't always work in this configuration, then it should be considered unreliable and not used. If this is the case, it's an issue with the app, not with your Tasker-fu. But with Tasker 4.0, you no longer need Secure Settings for a lot of things. Keyguard being one, GPS control being another big one.
Click to expand...
Click to collapse
I really appreciate the information, the concern, and your patience. I do think this is something I'm going to have to admit defeat on. I've tried everything I can think of and the lockscreen will not stay off. It's not really a big deal to hit a few numbers when I want to get into my phone or tablet. It also keeps small, curious people out. :laugh:
I've solved the issue for in the van. I just use an NFC tag on phone cradle in the van. Since my phone is always plugged in while I'm in the van, I just set the screen timeout for 30 minutes. Problem solved.
Good to know my Tasker-fu isn't in question. I have to admit that made me laugh.
UPDATE!!! There's a new XPosed Framework module in town that makes this whole thread obsolete. Check out the new NFC Unlock module, forked from the NFC LockScreenOff Enabler module already used in this project. Way simpler, fewer moving parts to configure, and works well. Check it out. Otherwise, this has been a fun way to learn how to use Tasker! Thanks, all!
Original Post
This is a guide to show you how to set up your phone to be unlocked by an NFC tag. There are several other threads on the subject for various phones and carriers, but it took me several weeks worth of research and testing to come up with something that actually worked on my phone, and this tutorial is the culmination of that effort. In theory, it should work for a wide variety of ROMs (including Stock), phones and carriers, and even survive ROM updates (provided you maintain root), but I have only tested it on a Sprint Galaxy S3 (model d2spr) that is rooted and running CyanogenMod 10.1.
DISCLAIMER! I am NOT responsible for any damage to your phone, loss of data, use of your phone, or spontaneous sharknadoes that may occur if you try these steps! It worked for me, but I make no guarantees that it will work for you! Back up all your data and your ROM, and use this at your own risk!
HARDWARE REQUIREMENTS
An NFC capable phone, like your Sprint Samsung Galaxy S3 with Root Access enabled
An NFC tag, such as Samsung TecTiles
SOFTWARE REQUIREMENTS
XPosed Framework
ONE of these XPosed Framework plugins:
MoDaCo Toolkit Plugin for the XPosed Framework (NFC Always On or On When Unlocked)
NFCLockscreenoffEnabler.apk for the XPosed Framework (lets you choose between Always On, On When Unlocked OR On At Lockscreen for better battery life)
NFC Task Launcher from the Play Store
Tasker from the play store
Secure Settings Plugin for Tasker
STEP 1: Install the software!
Install all of the software listed above.
Open XPosed Framework and enable the MoDaCo Toolkit OR the NFCLockscreenoffEnabler.apk in the Modules tab
STEP 2: Turn on NFC scanning all the time
Normally, Android only scans for NFC tags when the phone is unlocked. We need to scan for NFC tags when the phone is locked, and in our case, when the screen is off. Open the MoDaCo Toolkit app and check the box to Enable NFC when screen is off under Settings -> Wireless
WARNING!!! Turning on NFC scanning when the screen is off may adversely affect your battery life!
STEP 2 ALTERNATIVE: Turn on NFC scanning at Lockscreen
Open the NFCLockscreenoffEnabler.apk app and select Enable NFC when phone is locked, but the screen is on. This option should be a little easier on your battery. (Thanks to @nacron for finding this!)
STEP 3: Make Secure Settings a Device Administrator
Open Secure Settings and go to the Configuration Menu by tapping the wrench icon in the upper-right hand corner. Once there, check the box next to Device Administrator and select "Activate" on the confirmation screen.
STEP 4: Teach Tasker how to Lock and Unlock your phone
We can either do this the easy way, or the hard way.
Easy Way - Import the Tasks
Download and unzip NFC-Unlock-Tasker-Tasks.zip and copy the enclosed XML files to your phone
Open Tasker and long-press the Tasks tab
Select Import and open the files that you just copied
There is no step 4.
Hard Way - Manually Enter the Tasks
If you don't trust the import function, or just want to learn more about creating tasks in Tasker, you can create the tasks manually.
Open Tasker and select the Tasks tab. Create a new Task by tapping the big "+" sign, name it "LOCK", and add the following actions:
Select Task -> If
Under Condition on the LEFT side of the condition, type TRUN (the variable for Tasks Running)
Tap the Condition Operator icon (the grey button in the middle) and select Doesn't Match, or !~
On the RIGHT side of the condition, type *Unlock*
Under the If statement, select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button On
Select Plugin -> Secure Settings then tap Edit.
Select Lock Device and set the following options:
Box for Device Admin Enabled is checked
Select Task -> End If
Create a new Task named "Unlock", and add the following actions:
Select Task -> Stop And select the Lock Task that we created earlier.
Select Plugin -> Secure Settings then tap Edit.
Select Wake Device and set the following options:
Wake Type: Screen & Keyboard Lights On
Duration: 30 seconds
Select Task -> Wait and set duration to 100 MS
Select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button On
Select Task -> Wait and set duration to 100 MS
Select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button Off
Check box Run in background (No Notification)
If you run this Task now, you probably won't notice anything different right away. However, if you lock your phone and then unlock it, you'll notice that any security that you had set up is now bypassed. That's why we needed to teach Tasker how to lock your phone, as well.
STEP 5: Teach NFC Task Launcher to Unlock your phone
Open NFC Task Launcher and create a new task for NFC named "Unlock Phone".
Take your NFC tag and follow the instructions on the screen to write the tag for this task.
Add a new Task by tapping the big "+" icon in the upper right corner.
Select Category Tasker
Check "Tasker Task" and tap "Next"
Type "Unlock" in the field next to the magnifying glass icon under Tasker Task and tap "Add to Task"
Congratulations! You can now unlock your phone with your NFC tag! Of course, as we mentioned above, this leaves your phone without any passcode protection that you may have previously enable. Which leads us to our final step...
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
Now when the screen goes off, your phone is secure again.
That's it! My hope is that this tutorial is easy to follow so that anyone who wants to unlock their phone with an NFC tag can get it working. While there are a lot of steps, I tried to make them clear and specifically looked for a method that was flexible enough to allow me to update my phone or even use a different phone with this method, without having to track down a modified NFC.apk for my specific firmware every time I wanted to update.
In regards to how battery life is affected by having NFC turned on all the time, my personal experience shows no appreciable decrease in battery life. I went all day yesterday without charging (about 15 hours) with typical usage for me, which includes 2-3 hours of podcast playback over both wired and bluetooth headphones, occasional GMail and Facebook usage, Solitaire, and 45-60 minutes of phone calls, which is on par with what I was getting before the hack. As with all things, your mileage may vary. If battery life becomes an issue, try the new NFCLockscreenoffEnabler.apk plugin that @nacron found instead of the MoDaCo one which gives you the On At Lockscreen option in addition on Always On. It should save you a bit on battery life.
Many thanks to the authors of the software I used (XPosed Framework, MoDaCo Toolkit Plugin, NFCLockscreenoffEnabler.apk, NFC Task Launcher, Tasker, Secure Settings Plugin), as well as this thread and this web page for giving me the framework to construct this rather elaborate NFC hack.
I would love to hear from others if this works on other phones.
Changelog:
2013-09-05 - Add NFCLockscreenoffEnabler.apk option for NFC on at Lockscreen (thanks @nacron for this!)
2013-08-14 - Changes to the Tasker Tasks that make the lock and unlock functions run a bit more smoothly by avoiding collisions. (i.e., if you're unlocking the phone, it won't try to lock it until the unlock is done.) I've also added easy-to-import XML files for the Tasks, so you don't have to type them in manually anymore!
2013-08-09 - Initial release (can you "release" a process?)
Wow, thanks for the info.
New instructions and importable task files make getting this set up a whole lot easier! Updates in the OP!
I've attached a cheap NFC tag to my watch wristband, cleverly disguised by gold nail polish, and unlock by NFC is now my preferred unlock method.
I like this. Posting to keep track of it.
Well, as soon as root is found for the DROID MAXX, I will be using this.
Sent from my Nexus 7 using Tapatalk 2
Hello,
After trying this on a Samsung Galaxy S3 Stock 4.1.2 and Slim Bean (worked like a charm), I have found a glitch on the stock firmware. When making a call the screen would go off via the Proximity sensor so <b>Tasker</b> would lock the phone.
So I made a little addon to the following part and the problem stoped:
Original:
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
Modified:
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
[*] Select Display off (long-press) -> Add -> State -> Sensor -> Proximity sensor -> Check invert
That's it!
Now when you get a call and answer it Tasker will know that the proximity sensor is used and will not lock the phone
Hope it works for you too.
Thanks,
[/QUOTE]
stealthdave said:
New instructions and importable task files make getting this set up a whole lot easier! Updates in the OP!
I've attached a cheap NFC tag to my watch wristband, cleverly disguised by gold nail polish, and unlock by NFC is now my preferred unlock method.
Click to expand...
Click to collapse
Thats slick man. I may have to use that for myself lol :good:
This is great, thanks man but one problem. When I use my tag to unlock the phone, use the phone then hit the android home button to return to my default screen, it locks the phone instead. If I unlock it normally (Entering PIN) it doesn't display this behavior. What am I doing wrong.
Deleted
LevanG said:
Hi, can I use this method to unlock my LG Lucid2?
I want to use it on GSM network...
Click to expand...
Click to collapse
Wrong kind of "unlock", I'm afraid. This unlocks your screen so that you can bypass the lock screen; it doesn't do anything for carriers locking the phone to their network. Think of this as using an NFC tag as your password.
OK, sorry and thanks for your reply
lloydcabraham said:
This is great, thanks man but one problem. When I use my tag to unlock the phone, use the phone then hit the android home button to return to my default screen, it locks the phone instead. If I unlock it normally (Entering PIN) it doesn't display this behavior. What am I doing wrong.
Click to expand...
Click to collapse
Try adding a 200ms delay to the beginning of the LOCK Task. This seemed to make things a bit more predictable on my phone.
stealthdave said:
Try adding a 200ms delay to the beginning of the LOCK Task. This seemed to make things a bit more predictable on my phone.
Click to expand...
Click to collapse
Actually, already have added a delay at the beginning to the Lock task but it didn't do anything to correct the behavior to the Home button. I should probably add that I'm using this with an HTC One that already has a funky Home / Menu button configuration. Home button works fine when I unlock normally but seems to get remapped to go back to the lock screen when I unlock it using NFC.
lloydcabraham said:
Actually, already have added a delay at the beginning to the Lock task but it didn't do anything to correct the behavior to the Home button. I should probably add that I'm using this with an HTC One that already has a funky Home / Menu button configuration. Home button works fine when I unlock normally but seems to get remapped to go back to the lock screen when I unlock it using NFC.
Click to expand...
Click to collapse
Likewise. I have the same problem as well. The physical Home button just takes me back to my pin lockscreen if I had unlocked via NFC. If I unlocked my phone manually by entering my pin then everything just works fine.
EDIT: Should also say that my phone is the S3.
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
stealthdave said:
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
Click to expand...
Click to collapse
Not at all, I appreciate your help. I'm using ElementalX kernel that remaps the HTC logo as a menu button but leaves the back and home button alone. Maybe that's the issue? It's just funny that I only have the problem if I use my NFC to unlock the phone using the supplied scripts. Oh well, no biggie but if you can help me figure it out, it would be great. I can send you a cwm backup (wiped of course) if you'd like to try my setup?
lloydcabraham said:
Not at all, I appreciate your help. I'm using ElementalX kernel that remaps the HTC logo as a menu button but leaves the back and home button alone. Maybe that's the issue? It's just funny that I only have the problem if I use my NFC to unlock the phone using the supplied scripts. Oh well, no biggie but if you can help me figure it out, it would be great. I can send you a cwm backup (wiped of course) if you'd like to try my setup?
Click to expand...
Click to collapse
Actually, it would probably be easier for you to just try a different kernel and see if it still works. Given the description of what it does, my guess is that might be the issue.
It also might be an issue with the XPosed Framework or MoDaCo plugin on the HTC One specifically. (It does have its own special installation procedure.)
- Dave
stealthdave said:
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
Click to expand...
Click to collapse
I'm on 4.1.2 (Samsung based rom with stock kernel). I'm also using Nova launcher and I just tried stock Touchwiz launcher but same result.
I'm thinking it may be just something to do with Samsung Touchwiz or HTC Sense based rom (If lloydcabraham is also running HTC based rom or stock).
Thanks for your help stealthdave.
For some reason I can't get my phone to recognize the NFC tag when the screen is off or even in the lock screen. Only when I'm past the lock screen will the NFC tag recognize. The xposed framework was part of the ROM i'm using (M.O.A.R.) and I just installed the MoDaCo mod via the link. I checked off NFC on always and restarted several times but it still won't recognize when the screen is off.
[EDIT]
Got it to work using this xposed module instead of the MoDaCo one for always on NFC.
http://forum.xda-developers.com/showthread.php?t=2122019
Also having issues of lock coming back on after doing any action post unlock via NFC. I think it's a hack Samsung put together for the latest firmware upgrade after the whole problem with the bypassing the lockscreen by going through the emergency screen. The op wouldn't have this issue as he's not using a TW rom. I wonder if there is a way to have it input the key instead of bypassing the key.
[EDIT 2]
Overcame this issue by using the secure settings to reset the pin to nothing when unlocking via NFC and enable the pin when the screen goes off. This method even prevents the phone from locking during a call. I have a new issue of the swipe screen coming back right after NFC unlock. I'll post my findings a little later. It's not the most elegant of fixes but it prevents the lock screen from coming up when pressing the home button. I also removed all the waits and made lights and keyboard on for 5 seconds, makes unlocking faster.
The action for password/pin reset in Secure Settings is in All Actions > Dev Admin Actions > Password/Pin. You just select disabled when unlocking and it removes your existing pin and when you select enabled for lock, it prompts you to enter your pin twice in the settings. Not sure how secure this is or where it stores your password/pin. The only problem with this method is that you'll have to change the password/pin in secure settings if you decide to change your password/pin in the android settings or you'll end up with 2 different passwords/pins
Not sure if this works if you have pattern unlock. Haven't had time to test that.
So this is how my unlock task looks like:
1. Stop task lock
2. Secure Settings > configuration > Screen and keyboard lights on for 5 seconds
3. Secure Settings > configuration > clear password
4. Secure Settings > configuration > Keyguard disabled
and my lock is simply
1. Secure Settings > sonfiguration > Set Pin
and my profile is
Display Off > Lock
[EDIT3]
Figured out why it was presenting the swipe lock screen when doing a quick NFC unlock removal . I'm using the hacked version of AnyTAG NFC Launcher, instead of the NFC Tag Task Launcher, that detects NFC Tag removal as well as placement. Thought this app would be more extensible in the future. The only problem with this is that it will keep insisting on launching on NFC Tag removal if you don't set something so I just set the task to do nothing and that was locking the swipe screen again. I just set it to the same task as unlock and it doesn't pull up the swipe screen anymore.
Also, the battery replacements from Sprint suck. It's a generic sprint branded battery that DOES NOT have an NFC antenna in it. Picked up the replacement along with tectiles yesterday and couldn't figure out for the longest time why this unlock thing wasn't working. Their battery part number is BSML71021L. Gotta call them up to see if they can give me back my old battery or give me a real samsung replacement.
[EDIT 4]
After trying to get this to work consistently, I've disabled it. I can get tasker to remove/reenable the pin consistently but only sometimes will it clear the lockscreen automatically.
nacron said:
For some reason I can't get my phone to recognize the NFC tag when the screen is off or even in the lock screen. Only when I'm past the lock screen will the NFC tag recognize. The xposed framework was part of the ROM i'm using (M.O.A.R.) and I just installed the MoDaCo mod via the link. I checked off NFC on always and restarted several times but it still won't recognize when the screen is off.
[EDIT]
Got it to work using this xposed module instead of the MoDaCo one for always on NFC.
http://forum.xda-developers.com/showthread.php?t=2122019
Click to expand...
Click to collapse
Thanks for this find! I've added it to the OP for others. It's worked pretty consistently for me with this new module for the 30 minutes I've had it installed, and hopefully it will lead to better battery life. (Battery life wasn't too bad, but I was starting to notice a difference with NFC always on.)
nacron said:
[EDIT 4]
After trying to get this to work consistently, I've disabled it. I can get tasker to remove/reenable the pin consistently but only sometimes will it clear the lockscreen automatically.
Click to expand...
Click to collapse
I'm sorry to hear that it's not working for you. Hopefully Google will eventually enable this functionality in Android proper. The Moto X certainly shows that it's not only possible, but practical.
- Dave
Is there any way to disable the swipe to unlock on the G3 and just have it open to the phone when I tap the screen?
Let me explain... I followed the guide on here ( bliynd dot com *slash* archives *slash* 289) which allows you to use tasker and secure settings to write a profile that will disable your lock screen when you are on your home wifi (it is basically what the next version of android will have built in). I have a pin screen that welcomes you when you wake the phone whenever I am out but when I am on my home wifi it just shows the "Swipe in any direction to unlock" screen but I just want to be able to turn on the screen and have it just show my phone.
Is this possible?
demonjrules said:
Is there any way to disable the swipe to unlock on the G3 and just have it open to the phone when I tap the screen?
Let me explain... I followed the guide on here ( bliynd dot com *slash* archives *slash* 289) which allows you to use tasker and secure settings to write a profile that will disable your lock screen when you are on your home wifi (it is basically what the next version of android will have built in). I have a pin screen that welcomes you when you wake the phone whenever I am out but when I am on my home wifi it just shows the "Swipe in any direction to unlock" screen but I just want to be able to turn on the screen and have it just show my phone.
Is this possible?
Click to expand...
Click to collapse
just put it on none
jaythenut said:
just put it on none
Click to expand...
Click to collapse
I just noticed that tasker was not running. Enabled tasker and it worked.
Hello all you lovely people I recently upgrade to LP and now the switcher I used on KK isn't working. I used Easy Profiles to switch my lock screen from "none" to "pattern", also used security settings to make it work. It has other features but what I'm looking for is a profile manager that will change the lock screen based on my location/wifi/whatever. EP turned off my lock screen when I connected to my home wifi and turned on the pattern lockscreen when I left my wifi. I could also easily tap a profile and it would change the settings then. I've tried several profile managers (sorry I can't remember them all... basically if you search "profile manager" in the play store, I tried it) and none manage the lock screen. Does anyone have any suggestions? I went to the EP webpage and they aren't planning on development for LP at this time
nursemm05 said:
Hello all you lovely people I recently upgrade to LP and now the switcher I used on KK isn't working. I used Easy Profiles to switch my lock screen from "none" to "pattern", also used security settings to make it work. It has other features but what I'm looking for is a profile manager that will change the lock screen based on my location/wifi/whatever. EP turned off my lock screen when I connected to my home wifi and turned on the pattern lockscreen when I left my wifi. I could also easily tap a profile and it would change the settings then. I've tried several profile managers (sorry I can't remember them all... basically if you search "profile manager" in the play store, I tried it) and none manage the lock screen. Does anyone have any suggestions? I went to the EP webpage and they aren't planning on development for LP at this time
Click to expand...
Click to collapse
Llama at the play store will do that!
pcmanager said:
Llama at the play store will do that!
Click to expand...
Click to collapse
I tried llama before I found easy profiles, I found it difficult to understand/navigate. I tried it again recently and it wasn't switching the lock screen when switching profiles. I'm beginning to wonder if it's not a 5.0 limitation. It was a limit with 4.4 (I believe that was the build) and the work around was to install security settings and set a few items. That worked in conjunction with EP to show/hide the lockscreen
nursemm05 said:
Hello all you lovely people I recently upgrade to LP and now the switcher I used on KK isn't working. I used Easy Profiles to switch my lock screen from "none" to "pattern", also used security settings to make it work. It has other features but what I'm looking for is a profile manager that will change the lock screen based on my location/wifi/whatever. EP turned off my lock screen when I connected to my home wifi and turned on the pattern lockscreen when I left my wifi. I could also easily tap a profile and it would change the settings then. I've tried several profile managers (sorry I can't remember them all... basically if you search "profile manager" in the play store, I tried it) and none manage the lock screen. Does anyone have any suggestions? I went to the EP webpage and they aren't planning on development for LP at this time
Click to expand...
Click to collapse
LP has built-in profiling called "trust agents" that will do just that. It basically allows you to set a trusted location based on wifi/bluetooth/NFC using the trusted agents in "security" within settings on the stock LP ROM with Touchwiz. I have mine set to only use my lockscreen when at home and to use the secure lock screen with pattern/fingerprint/pin/password when anywhere else. I hope that helps.
I'm not on a stock ROM. I looked under security>trust agents but it's greyed out and I can't select it. And so is "smart lock". I'm running "BOB7V3Final ROM
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
+1
Sent from my Nexus 5X using Tapatalk
hmmm, you can try to use command 'input keyevent 26' , for tasker task...
this will required root though.
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
minnemike said:
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
Click to expand...
Click to collapse
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
jpen said:
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
Click to expand...
Click to collapse
Any solutions yet?
scottfreeze said:
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for this! Added it as a Tasker shortcut for double-tap gesture in Nova and it works like a charm.
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Pumpino said:
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Click to expand...
Click to collapse
There's a known list of Android commands that software can use to simulate some hardware presses, etc.: http://thecodeartist.blogspot.com/2011/03/simulating-keyevents-on-android-device.html
Tasker or using the keyevent 26 will not interfere with the system in any way. By sending the keyevent 26 you are doing exactly what pressing the Power button does - only with software. It does nothing to change any system settings. Not sure about the Soft Lock Screen app, but I suspect that like other software, if you use that, you will prob need to re-enter your password/pattern/pin and the fingerprint won't work. By sending the keyevent 26, you can still unlock it using the fingerprint sensor.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
minnemike said:
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
Click to expand...
Click to collapse
It does require root to be able to let Tasker run a shell command. You would not need Nova launcher as you can easily put a widget to launch the Task within Google Now Launcher or any other launcher. Nova launcher is nice because it enables gestures and double tap to do certain actions. I have Nova to launch my phone app when I tap the Home button on the main home screen. Double tap runs my Task to turn off the phone. Pinch in, pinch out, two finger swipe down/up, etc.
Could you have something trigger Tasker to temporarily change the screen timeout to 1 second (and then change it back after the screen is off)?
solara1973 said:
It does require root to be able to let Tasker run a shell command
Click to expand...
Click to collapse
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Pumpino said:
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Click to expand...
Click to collapse
Nova launcher does not have a function to send keyevents or turn off the screen etc.
You can always try some of the Screen Off apps on the playstore and see if anyone of those allow you to unlock the phone again using Imprint. Swipe-Lock, Screen Off and Lock, Screen Lock, etc.
this one works (experimental) https://play.google.com/store/apps/details?id=com.iglint.android.screenlockpro&hl=en
it is paid one