Related
Hi,
I am new to my XDA Orbit and am liking it very much. One annoyance (which is probably due to my ignorance) is that when I receive a text or an alarm goes off, my Orbit the device turns on / comes out of powersave mode and hence the screen is active whilst it is in my pocket (could be dangerous).
Is this the correct behaviour? Surely not, as input can be made from contact with your pocket? Is there a setting to change this behaviour? What does everyone else do?
Thanks in advance for any advice
Gary
Dosn't the XDA version have the screen lock like the mda?
It's a little padlock icon at the bottom of the today screen which says device unlocked, you tap it and the screen is locked from in pocket pressing, all buttons are locked too except the power button. when the device is switched on manually or by an event the screen is only active after using a 2 tap pattern, unlikely to happen by accident.
I must admit, I thought this was part of WM5 and not T-Mobile specific, strange it's not there on the xda.
It is possible to lock the screen before you turn the orbit off but it is a bit of a pain in the arse to have to remember to do that every time you turn off the device.
I was hoping for a program that would allow alarms and text message notifications without the screen becoming active.....
True, or you could re-train yourself to only do the screen lock and have the device auto-off in 3 mins or so, and it would be exactly the same.
Personally I find the screen wake up useful.
I can't say I've tried, but what happens if you go to Start - settings- Sounds & Notifications - Notifications
and go through all the text message received etc and untick "Display message on screen"??
http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
this battery status plug-in works on mda compact iii and it has a setting to lock the device on wake up so all you need to do is switch it off to lock it.
macguffin said:
http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
this battery status plug-in works on mda compact iii and it has a setting to lock the device on wake up so all you need to do is switch it off to lock it.
Click to expand...
Click to collapse
So it does!! I didn't notice. This is an excelent piece of software to have anyway, so this is just a double bonus, unless you are unhappy with the 2 screen taps required to de-activate the lock.
Hitting the lock icon requires the stylus whereas the power button does not - much easier and intuitive.
Will have a look into the alerts settings
Thanks for your help
Can't say I've had any difficulty hitting the lock (and definately not the unlock buttons) with my thumb, one handed, but see above for auto locking option, you 100% don't need to get the stylus to unlock.
i auto lock when the screen goes off and unlock with my thumb one handed, easy and intuitive
Hello everyone
After trying all the phone lock software out there I still can’t find what I’m looking for, what I’m looking for is so simple an icon in the start menu to lock the phone then r2u or t2u & unlock when phone rings and that’s it. I don’t like the idea of having to press the power button to wake up the screen to be able to unlock the device I’m also not interested in all of the other features that most of the phone lock’s have. Can someone help?
I have tried sensor lock I did like it a lot but I was unable to configure it and you could tell it was running in the background as the screen would jump. Plus throw in my case and a few beers and I know I’m going to drop it.
Many Thanks Jez
A list of phone lock programs you will need to search for them as some of the links aren’t applicable any more and I did need not save the ones that are working
Throttle lock
S2u2
Sunscape
Touchlock pro
Phone buddy
M lock
Organic lock
Pocket shield
Sensor lock
Lock me tight
Stylus lock
try Auto Lock (CSDEVCTRL), you could slide to the right on the screen to unlock the phone or use the windows default unlock.
Hello gbjack
Just tried that app and it’s just to much setting up and I don't think it’s going to do what I want it to do. Just hope someone is willing to write a program going by all the forums I have searched it will be popular
Cheer’s for the reply and suggestion
I tried many lock apps as well, but in the end the standard windows lock is what im using. No hassle, and it simply works as intended. I just press the "hangup" virtual button, and after the second vibration feedback i can be sure that the phone is locked. Doesn't get any simpler than that.
Then you have to try " WWE-Chobit Company SmartLock 1.7B". Only four or five options but it cannot lock your hardware key during call.
http://forum.xda-developers.com/showthread.php?t=505032&highlight=Lock
Then you have to try " WWE-Chobit Company SmartLock 1.7B". Only eight very simple options but it cannot lock your hardware key during call.
http://forum.xda-developers.com/showthread.php?t=505032&highlight=Lock
Just tried that app and it’s not even showing in programs for me to set it up, so I will have to keep looking, it amazes me that no one has written a program like I’m after considering it’s so simple.
gbjack said:
try Auto Lock (CSDEVCTRL), you could slide to the right on the screen to unlock the phone or use the windows default unlock.
Click to expand...
Click to collapse
This is good specialy the turn on bluetooth on call feature, but when we have an income call, the app takes ages to know what to do and the phone only begins to ring 5 secs after. Lockmelite it's the best one around but has a problem with alarms going to background after unlock. The "almost perfect" one is s2u but huge memory consuption makes background app's close or restart.
Hello jpl69
Tried this app found it to involved to setup and still does not do what I am looking for which is tap the screen to wake up so I than can unlock the phone using a s2u app. I find it bizarre that there are many apps to unlock the phone but you still have to push the power button to operate them. Surely it can’t take much program writing to add this feature. Jez
We have to push an hardware ley to wake up our devices from a low battery consuption state (suspend mode) and unfortunaly only have the power and volume hard keys so if you want to wake up your device with a tap on screen you'll only have a couple of hours with a full charge.
Now it makes sense why the screen sleeps if the battery only last for a couple of hours. Just a shame that the power button is so fiddly to operate. Jez
Yes, and it makes no sense having an device lock app (except on incoming calls). I only use it because of my 2 year old son that found the little tiny power on key , and made a couple of phone calls.
P.S. with a registry tweak you can enable the volume keys to wake up your device.
May be this could be your appropriate application:
MortSaver
jez.stix said:
Just tried that app and it’s not even showing in programs for me to set it up, so I will have to keep looking, it amazes me that no one has written a program like I’m after considering it’s so simple.
Click to expand...
Click to collapse
It's not in the Programs folder, it's in the Settings Folder.
try smart lock 1.7b
biosxjj said:
try smart lock 1.7b
Click to expand...
Click to collapse
That is brilliant and can be found here.
Simple and effective (needs a reboot after install, and is found under settings.
Just to be helpful... here's the brilliantly useful Reg tweak to allow wake-up from the volume keys.
- HKEY_CURRENT_USER\ControlPanel\Keybd
- set key: defaultkeylock from 1 to 0
- softreset
LockMeLite is definitely my favourite (especially with the above tweak), but as mentioned already, the alarm snooze / disappearing to background problem is a constant frustration.
Hello flid
Sorry for the delay everyone just got back from Canada so been busy catching up and sleeping. So how do I go about tweaking the reg key? I know how navigate to the reg key on a computer but not on my mobile
I changed my left soft key to lock the phone on the Home start screen as it was doing nothing useful except jumping to a phone operators website:
HKEY_LOCAL_MACHINE\Software\HTC\Manila\HomeLSKPath = windows\Endkey.exe
HKEY_LOCAL_MACHINE\Software\HTC\Manila\HomeLSKText = Lock (or whether text you want).
You just need a windows mobile registry editor. There are several free ones. My current Dutty ROM has one inbuilt, but from what I can gather the popular options are Total Commander (free!), Schap's Registry (free), PHM RegEdit (which is built in to Dutty's ROM) and Resco Registry Editor (not free - but definitely the most finger friendly). There may well be others.
hi, I am curious where to go to set the tilt 2 to automatically lock to the winmo 6.5's screen after like a few minitues of not use. I konw that if I press the end call button for a few sec, it locks it but is there a way to do it automatically after a few minutes?
thansk.
Try This
I can give you a suggestion, but I have the Verizon version, so it may be a little different. I also may depend on your ROM...
Goto Settings > System > Smart Lock. Checkmark Dim Lock box.
Goto Settings > System > Power. Select Backlight, set backlight dim time, and then your device will auto lock when your backlight dims.
I also use Gyrator to auto lock my phone when I turn it upside down. (I always insert in my pocket upside down (Reverse portrait), but I never use it upside down, and this prevents unwanted button/screen presses while in my pocket.)
thnak you so much for the reply. It appears to me that the ATT version has slightly different setting for it. I do see the lock option but that would require a password, anyway to still let it enabled without any password? anyone with ATT can shine some lights.
Devoncoon said:
Goto Settings > System > Smart Lock. Checkmark Dim Lock box.
Goto Settings > System > Power. Select Backlight, set backlight dim time, and then your device will auto lock when your backlight dims.
I also use Gyrator to auto lock my phone when I turn it upside down. (I always insert in my pocket upside down (Reverse portrait), but I never use it upside down, and this prevents unwanted button/screen presses while in my pocket.)
Click to expand...
Click to collapse
PUTALE said:
thnak you so much for the reply. It appears to me that the ATT version has slightly different setting for it. I do see the lock option but that would require a password, anyway to still let it enabled without any password? anyone with ATT can shine some lights.
Click to expand...
Click to collapse
I believe the Lock Setting Devoncoon is referring to is fixed with SmartLock (app here on XDA). That might help to download that app, if you have not done so. Once you install it, set it up as Devoncoon instructed you, and you will not require a password lock.
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
I'm curious if anyone else has had this issue. I have to enable a PIN or pattern lock to allow a corporate secure wifi network setting to be saved and for something else (I think for my bank app). From the G4 settings it seems like you can set it to NOT lock when turning off with power button (last option), and a 30 minute timeout before it auto-locks. Yet despite that, mine still seems to lock requiring a pattern input and not just a swipe if I leave it on the table for just a minute. What am I missing?
Thanks all!
Verizon LG G4 VS986, stock.
CPngN said:
I'm curious if anyone else has had this issue. I have to enable a PIN or pattern lock to allow a corporate secure wifi network setting to be saved and for something else (I think for my bank app). From the G4 settings it seems like you can set it to NOT lock when turning off with power button (last option), and a 30 minute timeout before it auto-locks. Yet despite that, mine still seems to lock requiring a pattern input and not just a swipe if I leave it on the table for just a minute. What am I missing?
Thanks all!
Verizon LG G4 VS986, stock.
Click to expand...
Click to collapse
These settings are under Lockscreen. Right at the end. It should work, unless you have another app controlling locking.
Exactly.. it "should work"... but it isn't. It insist on locking all the time.. Could the fact that I"m connected to said secure WIFI cause that?? (vs just having an entry for it)
You could try going under the setting for Security - Phone administrators. Look if there is something that is controlling phone lock.
I know for my example, I must enable PIN locking, but my phone administrator for that account enables up to 30 minutes before forcing lock. So as long as I uncheck the setting for "Lock phone immediately on power button," my phone will immediately be unlocked within a 30 minute window where I don't need to enter my PIN.
KingFatty said:
You could try going under the setting for Security - Phone administrators. Look if there is something that is controlling phone lock.
I know for my example, I must enable PIN locking, but my phone administrator for that account enables up to 30 minutes before forcing lock. So as long as I uncheck the setting for "Lock phone immediately on power button," my phone will immediately be unlocked within a 30 minute window where I don't need to enter my PIN.
Click to expand...
Click to collapse
Right, that's what I'm going for / expecting. I have 3 in there, Android Device Manager, Support & Protection (Verizon thing it looks like) and AirDroid. Only Android Device Managers is checked ON. ADM can obviously affect the lock screen and can change the lock password, but I don't see anything else which would affect this timeout being ignored. hmmmm
(Thanks, BTW!)
I was looking at my Smart Lock section and read the blurb about On-body detection, which was the only Smart Lock I had enabled. It says "Just unlock once and your device stays unlocked as long as you keep holding your device or carry it on you." .... "Your device will lock when it detects that it's been set down"..!! So, I've now turned on-body detection OFF as, in this case, it's working against me. Seems it's not too well integrated with the other options (ignores the Security Lock Timer).
If I don't post back, it's probably working as hoped.
Disabling on-body detection has definitely solved my issue with the G4 locking shortly after setting it down on the desk.
SOLVED