[Q] Turn off Nexus 7 completely when power is lost using Tasker? - Nexus 7 (2013) Q&A

I have seen in other threads that people use tasker to turn of their tablet when there is no power, for example when you turn of ignition in cars etc.
I want to do the same, since it will be getting cold here in a couple of months. This together with fastboot, will be good. But i see no option in tasker to turn off the tablet completely when there is no power present?
Anyone want to help me out?
edit; http://forum.xda-developers.com/showthread.php?t=2657308
Here you can see someone used tasker to turn off tablet completely

henrikrox said:
I have seen in other threads that people use tasker to turn of their tablet when there is no power, for example when you turn of ignition in cars etc.
I want to do the same, since it will be getting cold here in a couple of months. This together with fastboot, will be good. But i see no option in tasker to turn off the tablet completely when there is no power present?
Anyone want to help me out?
edit; http://forum.xda-developers.com/showthread.php?t=2657308
Here you can see someone used tasker to turn off tablet completely
Click to expand...
Click to collapse
I hope you're familiar with how Tasker works. If not, please read some basic tutorials.
Create a new profile State->Power->Power
On the State edit leave the Source as Any and tick the Invert box, so this works when it is not charging.
Create a new task and add a new action System->Reboot
On the Action edit view there is a Type selector, when you tap it you're presented with a list of different options, one of those is shutdown, select it and that's it.

alresave said:
I hope you're familiar with how Tasker works. If not, please read some basic tutorials.
Create a new profile State->Power->Power
On the State edit leave the Source as Any and tick the Invert box, so this works when it is not charging.
Create a new task and add a new action System->Reboot
On the Action edit view there is a Type selector, when you tap it you're presented with a list of different options, one of those is shutdown, select it and that's it.
Click to expand...
Click to collapse
Thank you, only problem is system reboot is red here and says unavailable for me, i already rooted using geohots method, do i need to do more?
nvm, i haven't installed superuser
im so stupid
Thank you so much for answering me Really appreciate it

Related

[Q] How do I make my screen NOT auto-dim when plugged into AC

I have the setting checked to keep screen on while on AC, but it still auto dims to about 10% after 30 seconds or so. I want to stop it from doing this and just keep the screen at 90% all the time. Auto-brightness is already off, and that didn't change anything.
I'm trying to setup a tasker profile to turn the brightness to 90% during the day when in the car. Everything works fine, I can see the screen get brighter, BUT it still dims after 30 seconds and I can't see the display when it's bright out unless I touch the screen, then it comes back to full brightness again.
Help please?
settings - display - screen timeout - never turn off
bigmoogle said:
settings - display - screen timeout - never turn off
Click to expand...
Click to collapse
I don't have that option. Only goes to 30 min. I'm running CM6.
bigmoogle said:
settings - display - screen timeout - never turn off
Click to expand...
Click to collapse
But the screen still dims to about 10% (even with Sense and even while plugged in).
Maxy6 said:
But the screen still dims to about 10% (even with Sense and even while plugged in).
Click to expand...
Click to collapse
Exactly.
I've temporarily resolved this by having tasker open car home, then opening pandora.
When car home is running, it won't dim the screen.
Now I have to figure out how to make it do this without car home open.
bump
Did anyone ever find a solution?
Settings > Applications > Development > Stay Awake (Screen will never sleep while charging)
This is true but the screen still dims.
Still searching for an answer.
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
spalding1028 said:
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
Click to expand...
Click to collapse
Nice find Going to try it now....
SOLVED
spalding1028 said:
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
Click to expand...
Click to collapse
Works great! Thank you for coming up with a fix!
spalding1028 said:
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
Click to expand...
Click to collapse
THANK YOU!
From time to time I've searched for a solution to this annoying problem, but came up dry. For months I've been using the built-in Power Control widget to manually toggle between Auto-bright when on battery, and Full-bright when on the charger, but NEVER AGAIN
I mean, if your phone's on the charger, why wouldn't you want to take advantage of the plentiful juice pouring out of the charger to power the screen? (Maybe, and I don't know if this is true, but maybe the battery will charge slightly slower with the display sucking a bit more of the available 0.5 max amps over USB.)
IMO, this problem is really worthy of being solved by a standalone app, apart from the more general Settings Profile Lite (but now that it's solved... I don't feel the urge to code it anymore.)
ChargeBright app
FWIW, I did finally end up writing my own app to solve this problem. Check out the ChargeBright app @ market.android.com if interested.
Settings Profile Lite was overkill since I only needed to tweak one setting: display brightness when charging. ChargeBright saves resources and is better tailored to the specific task in any case.
spalding1028 said:
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
Click to expand...
Click to collapse
Worked like a charm! Thanks!
spalding1028 said:
I had the same problem. After some searching I found this over on android forums and it's working like a champ for me. Hope this helps! (I don't think there's any system setting that will change this, unfortunately)
Download the app "Setting Profiles Lite". Lite is free and only lets you create 1 rule at a time, but multiple profiles (Actions you want it to do when the rule is happening)
1. Create a profile that simply changes the screen time out to "Screen Never Times out" Save it as whatever name you want.
2. Create a rule. Under conditions add a condition for Battery that when "plugged into any charger", hit OK. Now add an action to Activate Profile, and choose the profile you made above.
Bam! When plugged into the charger, the screen timeout goes to never, and the screen stays bright, unplug it and time out goes back to whatever you had it set at!
I have been using this for about 10 min now so I'm a rookie but it seems to be working! Make sure if you screw around in it that you don't accidentally disable the rule (I did that because I tried to make another and the Lite won't let you make 2 rules, and it disabled the first one. Just had to long press to enable it again)
Click to expand...
Click to collapse
2 years later and this still works like a charm. THANKS.

Touch Key Light Duration (ICS)

I posted in another thread about a problem with ICS concerning "Touch Key Light Duration", but feel it needs it's own thread.
My problem is "Touch Key Light Duration". Seems to be a problem with the little bit I googled. I can set it the duration to "Always On, but it has a mind of it's own. Somethings will turn off the light; I have to go back into the settings to reset the light.
I've played with all of the power setting, power saving, display settings I can find, but cannot find a way to keep the lights on the way I want. I've done Factory Reset, I've changed the duration, changed power settings,etc to no avail.
Anybody else having this problem?
Anybody have a solution, or an app to fix this?
Same problem here.....I had to choose 6 seconds option in order to get it to work.
I have exact same thing as droid_ra.
I hope somebody will come up with a fix, it's really annoying.
Are you guys running Stock? If so ICS or GB?
alphadog32 said:
Are you guys running Stock? If so ICS or GB?
Click to expand...
Click to collapse
Didn't have the problem with GB.
Now I'm running stock ICS. I even tried to do a wipe and reinstall with no success. May try it again.
Haven't tried rooting yet, although I've read in another thread that it may fix it.
I'm running stock ICS rooted, but the problem started right after I upgraded from GB to ICS.
So this problem is not ROOT dependent, but rather ICS's fault.
Like a someone else said, if you adjust it to 6 seconds delay, it will work properly.
However, I like to keep it at "Always On".
Sent from my SGH-T989 using xda premium
I too have the same problem. I'm running stock ICS that has been rooted. I did not have the problem when I was running stock GB that was rooted. Hmmm....
I was looking for confirmation and a fix when I created this thread.
Looks like a bug and Samsung/T-Mobile needs to fix this one.
Perhaps a dev can look into this?
yeah this is quite annoying. "always on" just simply doesn't work. 6-seconds is what I use now but I really wish I could go back to "always on" and have it work. Again, all since ICS update. Overall pretty please with the update but this and the mobile-life sync thing are annoying...
Same problem here, not rooted but happened going from GB to ICS, will have an Siii this week so hoping it's not an issue there.
Work Around
Hey guys I found a work around.
I used tasker and screen filter together to make the backlights light up whenever I turn the screen on.
I made a new tasker profile with the event Display On then put one screen filter task set to 96% and softkey lights off and another screen filter task right after it at 100% and softkey lights on. It takes a split second after turning the display on but 90% of the time it works every time.
jgbenito7 said:
Hey guys I found a work around.
I used tasker and screen filter together to make the backlights light up whenever I turn the screen on.
I made a new tasker profile with the event Display On then put one screen filter task set to 96% and softkey lights off and another screen filter task right after it at 100% and softkey lights on. It takes a split second after turning the display on but 90% of the time it works every time.
Click to expand...
Click to collapse
My apologies in advance for my ignorance, but how does one go about creating a "tasker profile?"
rabilancia said:
My apologies in advance for my ignorance, but how does one go about creating a "tasker profile?"
Click to expand...
Click to collapse
You go into your tasker app then hit new. Then after you name it, it will pop up with "first context" and choose event--->display--->display on.
jgbenito7,
Thank you VERY much! I had no idea that there was such an app. It's been a while since I've used anything like tasker so I'm going to go slowly: read, read some more, then experiment. Thank you again,
Rich
rabilancia said:
jgbenito7,
Thank you VERY much! I had no idea that there was such an app. It's been a while since I've used anything like tasker so I'm going to go slowly: read, read some more, then experiment. Thank you again,
Rich
Click to expand...
Click to collapse
No problem!
Did you get it to work? The only problem is that tasker is a paid app but its great for little workarounds like these.
I'm still reading how to use the tasker app. I think I understand the event section figured out but having some trouble figuring out the actions (e.g., "filter task set to 96% and softkey lights off....").
LifeHacker has two great articles: here http://lifehacker.com/5599116 and here http://lifehacker.com/5601133. I also downloaded the 14 day trial here: http://tasker.dinglisch.net/download.html . That way I can decide if I want to spend the money. Right now, it looks like I will.
rabilancia said:
I'm still reading how to use the tasker app. I think I understand the event section figured out but having some trouble figuring out the actions (e.g., "filter task set to 96% and softkey lights off....").
LifeHacker has two great articles: here http://lifehacker.com/5599116 and here http://lifehacker.com/5601133. I also downloaded the 14 day trial here: http://tasker.dinglisch.net/download.html . That way I can decide if I want to spend the money. Right now, it looks like I will.
Click to expand...
Click to collapse
I guess I could have been a little bit more specific...
There are two apps to download "Tasker" and "Screen Filter."
You open up Tasker then hit "new". After naming your profile hit okay then "First Context" window will appear. Hit "event". Then "Select Event Category" will appear. Hit "Display" then "Display On". The priority box will pop up but just hit "done". That is your event that triggers the actions. You should then be in "Task Edit". Click the "+" sign then "Plugin" then "Screen Filter". You should see "edit" across from "configuration". Click on edit then adjust the brightness to 96.1% (not 100% on the first one because it wont work right) then uncheck the "enable soft-key backlight" box. Hit save. Now add the second action by hitting the "+" sign again and do the same steps except this time have the brightness at 100% and the box checked for "enable soft-key backlight". The second action toggles the backlight therefore enabling it and also gets rid of the notification in the status bar. After you are finished hit "done" and then make sure to hit "apply". Test it out!
Got it! Thanks again. I was missing the "Screen Filter" app. I have the Task (event and action) up and running. It didn't work first try because the "Settings / Display / Touch key light duration" was set at "6 seconds." When I changed it to "always on" it started working. I'm looking forward to really getting into "Tasker!"
Had the same problem on every single rom!!
Posted in general, q&a and the rom threads abt this
A clean stock gb/ics doesnt have the problem i tested it for days
Seems like no dev cares abt the problem so i got used to the 6seconds option, i suggest that u do the same
Sent from my SGH-T989 using xda premium
Same problem here with rogers Official ICS on the Skyrocket, tried Google & saw lots of posts about the problem, but no real solutions. I don't think that it's carrier related... It's either Samsung or Google's problem. It's a pita!
Sent from, The Eclectic Chair.

[Q] Can someone please help me with Tasker/lockscreen issues?

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.

[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

Tasker

I just downloaded tasker. It seems like an amazing application but for the life of me, I can't figure out how to use it. Here are the tasks that I would like to program:
1) Set Wifi On when I am at home using cell towers
2) Set Wifi Off when I leave home
3) Change volume level to vibrate when I plug it in to the charger and allow emergency calls from certain phone numbers (I read you can do this)
4) Set volume level to highest setting when the phone is unplugged
5) Launch Pandora when my phone is connected to bluetooth
If someone could post step by step instructions that would be great. My hope is once I learn to do these, I can figure out how to program other tasks. Thanks.
ILowry282 said:
I just downloaded tasker. It seems like an amazing application but for the life of me, I can't figure out how to use it. Here are the tasks that I would like to program:
1) Set Wifi On when I am at home using cell towers
2) Set Wifi Off when I leave home
3) Change volume level to vibrate when I plug it in to the charger and allow emergency calls from certain phone numbers (I read you can do this)
4) Set volume level to highest setting when the phone is unplugged
5) Launch Pandora when my phone is connected to bluetooth
If someone could post step by step instructions that would be great. My hope is once I learn to do these, I can figure out how to program other tasks. Thanks.
Click to expand...
Click to collapse
1+2) New Profile "Home" State->Phone->Cell Near - Under Cell Tower press scan and walk around the house to register a few cell towers.
Go to tasks and create new task "Enter Home" - New - Wifi - On
Repeat with a task "Exit Home" - New - Wifi - Off
Go to profiles long press "Home" select Enter Home as entry task and Exit Home as exit task.
Same logic for the others
stathis95194 said:
1+2) New Profile "Home" State->Phone->Cell Near - Under Cell Tower press scan and walk around the house to register a few cell towers.
Go to tasks and create new task "Enter Home" - New - Wifi - On
Repeat with a task "Exit Home" - New - Wifi - Off
Go to profiles long press "Home" select Enter Home as entry task and Exit Home as exit task.
Same logic for the others
Click to expand...
Click to collapse
I can't get the silent mode one to work. It seems pretty simple so I don't know what I'm doing wrong. This is what I'm doing
Create Profile - State-Power-AC
Create Task-Audio- Silent Mode On- Set as Enter Task
Create Task-Audio-Silent Mode Off- Set as Exit Task
Doesn't work.
ILowry282 said:
I can't get the silent mode one to work. It seems pretty simple so I don't know what I'm doing wrong. This is what I'm doing
Create Profile - State-Power-AC
Create Task-Audio- Silent Mode On- Set as Enter Task
Create Task-Audio-Silent Mode Off- Set as Exit Task
Doesn't work.
Click to expand...
Click to collapse
It should work. Are you plugging it on AC or USB? Does the profile activate? (is it green?)
stathis95194 said:
It should work. Are you plugging it on AC or USB? Does the profile activate? (is it green?)
Click to expand...
Click to collapse
I'm plugging it into the wall. Here is a screenshot of my profile screen
ILowry282 said:
I'm plugging it into the wall. Here is a screenshot of my profile screen
Click to expand...
Click to collapse
Wow! I'm an idiot. I had tasked disabled. Haha! How do I create an exception for the silent mode task to have certain numbers get through?
ILowry282 said:
Wow! I'm an idiot. I had tasked disabled. Haha! How do I create an exception for the silent mode task to have certain numbers get through?
Click to expand...
Click to collapse
Have a look here:
http://tasker.wikidot.com/sleepmode
Tasker has unlimited capabilities. I find myself learning something new about tasker every single day
stathis95194 said:
Tasker has unlimited capabilities. I find myself learning something new about tasker every single day
Click to expand...
Click to collapse
Ditto! I also find myself completely baffled by it every day, despite having used it for years and being a programmer. The more complicated stuff you try to do, the more you'll be both amazed and confounded by the capabilities

Categories

Resources