Develop Bugs

Wifi profile timer?

I'm looking for an app that can enable & disable wifi at certain times of the day/days of the week etc.
Basically so that while I'm working, my wifi is switched off to preserve battery power, but when I'm out at lunch or home in the evening the wifi is on automatically.
I looked around the site at things like wifiprofiles app, and monsterwifi app etc but unless I missed something I don't think they allow shedules for when wifi automatically switches on & off do they?
Sorry if I'm being thick or missed another option!

you should check out phoneAlarm Pro -- I've been using this for years, it is a powerhouse of control for all sorts of things -- profiles (automatically switchable) include WiFi on/off as well as Data, Ringtones, Volume, Backlight, customizable alerts, etc. I could go on and on... this is my one and only "must have" app!

oh, and of course it's skinnable! you can find plenty of skins and support in the pocketmax.net forums...

Thanks for that. Installed the demo version.
In theory it's spot on, but in practise I can't get the automatic (scheduled) profile switching to work.
I set a time for it to swap from 'Out of hours' to 'Work' and noticed my phone still shows as having the ringer on even though I set the Work profile to be silent etc.
What I don't understand is the relationship between the profiles in this software and the profiles that the phone uses normally.
Ie when installed, I can't see anything that illustrates what profile this software thinks it is currently using, just the usual volume/ringer icon at the top of the screen.
If I change the system volume with the hardware volume button for instance, does this directly influence what profile gets used on Phonealarm? Or should Phonealarm disable the system related profiles/volume control etc?
Me = a bit confused!

yeah, it can get a bit daunting at times cuz it does so much...
can I assume you're on WM 6.5 and Manila/Sense? back in the day, phoneAlarm ran as a Today screen app (still can) -- but now with 6.5/manila it can run as a 'background host' -- so you don't really see it unless you call it up. you can have an Icon 'stick' to the taskbar, but I keep mine hidden and have a key shortcut to bring up "paHost". now, depending on the skin used, you can see what profile is active as well as alarms, status, time, weather, etc...
basically, the profiles 'overtake' the WM settings -- they're still there, just set by phoneAlarm. for example, you can still change the volume as usual, but on the next profile change it will be reset per the profile's settings.
the profile schedules and the custom email/sms alarm are probably the most difficult to understand (or to get working as you'd expect) -- I would recommend downloading the 'user guide' -- it explains things far better than I could here.
lastly -- get familiar with the forum! the FAQ and Support threads cover just about everything, and "Penguin" (the developer/moderator) is really very responsive to everyone's questions and/or needs.

maybe an example would be helpful...
here's how I do it -- when I arrive at work, I plug my HD into a cradle at my desk and it (usually) stays there all day. the ActiveSync connection triggers the "work" profile, which sets volumes/tones, turns on bluetooth headset, etc. etc.
now once I unplug it -- it switches to "car" profile, as I'm (usually) now on my way home. note the "on end" setting in screenshot #2.
when I get home, I manually switch to "home" profile. this would be where you could get into location-based rules -- from gps, cell tower, etc. -- to automatically know you're home, but I don't have them set up at the moment.
then, it will switch to "night" mode at 10:00pm, turning off bluetooth, data, lowering volume & screen brightness, etc. etc.
when I get to work the next day we start all over again. (also note weekdays, as in you could do something different on the weekends)
I hope this helps you -- I think once you get the hang of it this is a truly awesome app. I'll be happy to answer any specific questions you have if I can. Good Luck!

Thanks for the assistance mate.
I think I've got the hang of it now after your posts and looking at the manual (I should have learned by now!). There's a few bits I'm not 100% certain about but it's mainly doing what I want and looks promising.
The phone is guzzling battery power since I installed it but I think I have found why. I have found that the wifi logo is visible all the time but red instead of blue, and previously this was not the case. I notice in the settings it describes toggling 'wireless lan' on or off but not perhaps in the same way as going into comm manager and selecting Wifi on or off. Not sure how I can get round but I need to make it turn off properly as it's burning my battery like the clappers!!
I like it though apart from teething problems!

[Q] Bluetooth calls from PIN locked Screen

Howdy Folks,
I may have ran into a show stopper on the Samsung Galaxy S3 from Telus. I need to have a PIN on my phone or some locking mechanism that is secured, swipe doesn't cut it, as I have working documents and phone numbers that I don't want easily accessed. I have a blueant S3 and a Motorola 505 hands free bluetooth device that work great when the phone is unlocked. However, S Voice doesn't appear to work when the phone is locked. When I try to place a call, I can see the phone light up, and have confirmed that S Voice is initiated, however, it does not accept the voice command. I have checked my call settings and the make outgoing calls when locked is checked. It works when swipe is engage, however, this is not an option for me.
Something I have found is that if I initiate the call with the hands free unit, click emergency call on the phone, click the return button from the emergency call, S Voice will start up. Sometime's it'll make the call, sometimes it won't.
Are there some settings that I'm missing?
Does anyone have a solution?
I sure hope so, otherwise, I will have to return the phone.
TIA for your responses.
Thanks,
Greg

I found a solution. I installed Tasker and Secure Settings. In Tasker, I create a profile for when a bluetooth connection is made to my handsfee unit. I then created a task that disables my PIN. I also created a profile that re-enables my PIN when the bluetooth connection is lost.
After a month of searching, I finally found a solution. I still say that Samsung has this screwed up and I'm very disappointed that I even had to install third party software to make something work.
Greg

This has been a problem for me also. I don't want to leave my phone unlocked all the time. Are those two separate programs?

RandyMP said:
This has been a problem for me also. I don't want to leave my phone unlocked all the time. Are those two separate programs?
Click to expand...
Click to collapse
They are two seperate apps within play store. Secure Settings is a plugin for Tasker, so you access it through it. Here's more detail on how to set it up:
Profile->Bluetooth Connected
Task->PlugIn->Secure Settings->Password/Pin->Disabled
I then added an Exit Task
Task->Plugin0>Secure Settings->Password/Pin->Enabled (Set to my old
PIN number)

Perfect! I definitely wouldn't have figured this one out without your help. I'll test it out tomorrow and see how well it works.

Couldn't get it to work with Samsung S4
Great suggestion on using Tasker, but unfortunately, I could make it work with my Galaxy S4. I successfully created the macro in Tasker and could get the lock on the lock screen to disable, but I could not get the phone to turn off the lock screen altogether (I'm running 4.2.2 unrooted). Couldn't find the ability in Tasker with Secure Settings to altogether turn off the lock screen (not just clear the lock). My phone is set to allow dialing from an accessory with the screen locked, but the phone isn't following that. If I have any lock screen (even with no lock set), bluetooth won't complete the call until the lock screen is cleared (even if it only requires a swipe). After not succeeding with this, I also tried to use Tasker to activate a couple unlock apps from the Google Play store, but those too had no capability to altogether disable the lockscreen so that the power button takes you directly to the home screen. Further research revealed an app called BtWiLocker that is designed to unlock the phone and clear the lockscreen when BT or WiFi are connected and relock when done. I've used that for a day so far, and it seems to be working OK after playing with it a little to get the settings correct.

I got it to clear the password when a BT connection was made, and reset the pin passcode when the BT connection ended.
The key thing is to create another profile for the BT connection when not connected. This can be done by checking off the "inverted" check box.
Initially, I only got 1/2 of it to work where it will clear, but if the device sleeps it will be locked again.

[GUIDE] Use NFC to unlock your phone, Galaxy S3 or other!

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

[Q] Lockscreen shortcuts seem to be missing...

Alright, so I was setting up my ls990 and during the setup of everything (apps/widgets/screens/you know) I managed, or perhaps my phone managed, to simply stop displaying lock screen shortcuts. I know what you may be thinking, no, there are no passwords, knock codes, pins, locks, mods, extras, or anything that *could* cause this.
It's a simple swipe to unlock, that's it, there are shortcuts 'set' in the lock screen settings as you'd expect, but no matter what fiddling, swiping, or press-and-holding I try will bring them back. Every last combination of settings and lock screen fidgeting and 'oops I deleted the default circle lock screen widget thingy but found out how to bring it back and also learned how to set the default lock screen page that will show when I turn the screen on'-ing will make them show again... So after on and off and mostly on playing around with it over the last 10 hours or so, and seeing how it is now 5 am where I live, and certainly the tunnel vision has set in or I'm just plain ol' dumb and/or incapable of swiping my own buttons, I'd figure that somewhere in the population of LG g3 owning & xda browsing intelligental(wo)mens there could be somebody to set my plain ol' dumb button pushing straight.
Any ideas?
Posting on the chrome browser from my nifty ls990 via my Wi-Fi connection, tanks.

Well anything? Need smart people please, I'll consider this a bump.

Do you see the Emergency Call box at the bottom? I just had that same issue, and it appeared to be triggered by a lack of signal or going into roaming mode. Setting the device into Airplane Mode brought the shortcuts back for me. Here's exactly what I did:
1. Set the device into Airplane Mode (I used the shortcut from the notification shade).
2. Lock the device.
3. Hit the power button to bring up the lock screen. Verified shortcuts were there.
4. Shut off Airplane Mode (once again, used shortcut).
Let me know if that works...

[Q] My screen locks too often (requiring pattern or pin very often). Why?

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