Looking for app - disable lock when connected to specific SSID - Nook Color General

I thought a while back I saw an application on the Market that would enable or disable the lock screen based on what SSIDs the device could see. I thought this would be a good idea for my Android devices, since I'm usually either at home or at work, and both places have WiFi. It would be bothersome to have to enter a lock code every time I want to use a device, but would be great to require that if I'm away from home.
I know I saw an app that does this, but for the life of me, I cannot find it!
Edit: Should clarify, it doesn't disable the lock screen, it disables the passcode - basically when it sees particular SSIDs, it disables the passcode. Then when you're not in range of those SSIDs, the passcode is required.

Yep, I was looking for this too and found your post. Then I remembered something I'd seen before:
www.symonds.id.au/marcopolo/
There's a link on that page for a modified version of it for Snow Leopard, you'll need to get it if you want to lock/unlock your PC based on your AP's MAC/essid and run 10.6.
Let us know how well it works for you! I'm using it for a simple case: keeping my computer locked at work, unlocked at home.

Related

How to skip WiFi configuration during initial setup of Nexus 7

I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I booted into the bootloader, then used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery ).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)​7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)​
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
organophosphate said:
Allowing The WiFi Setup Step To Be Skipped (Dangerous):
...
9. YOUR TABLET WILL FAIL TO BOOT IF YOU SKIP THIS STEP: adb shell chmod 755 /system/build.prop
...
Click to expand...
Click to collapse
Shouldn't this be 644?
Also, in case anyone wants to know, you can bypass activation after connecting to a WiFi network - you do not need to tie the tablet to your Google account.
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
cwoggon said:
Shouldn't this be 644?
Click to expand...
Click to collapse
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
nextelbuddy said:
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
Click to expand...
Click to collapse
Well, in my opinion, less is more
organophosphate said:
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
IIRC, this would have been helpful to a gentleman who was looking to bypass WiFi activation awhile back. I applaud little workarounds such as this... you never know when this information might be useful.
cwoggon said:
Well, in my opinion, less is more
Click to expand...
Click to collapse
True.
I was dissatisfied with the original approach because of the risk of causing boot failure, so I refactored the implementation to avoid the problem altogether. The updated procedure should be cleaner & more efficient.
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
ehh i still have to disagree with you there. this isn't the same as wanting to install a custom ROM.
installing custom ROMS and Kernels have true benefits whch are optimization and customization that stock does not offer aka more choice.
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice. as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
I know that many custom roms and kernels give me the ability to inccrease speed and add more options in the operating system that i am looking for hence i will choose to flash a new rom and kernel.
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Im not trying to be argumenative just to do it, im trying to determin your real actual justificaton for wanting this besieds "
its my device let me do what i want" because at no point did i say nor did anyone else say they wanted to flash new roms and kernels because it was their device and they wanted to do what they want, they did it because those options benefitted them in a way that the stock experience did not.
Just because someone is on XDA does not man they are here ot hack their device to pieces. there are many reasons people come to XDA..
talk and interact with others that have a love for media devices
ask questions about their devices
learn from others on how to modify their devices
completely change their devices
just to name a few.
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
nextelbuddy said:
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice.
Click to expand...
Click to collapse
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
nextelbuddy said:
as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
Click to expand...
Click to collapse
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
nextelbuddy said:
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Click to expand...
Click to collapse
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
nextelbuddy said:
Just because someone is on XDA does not man they are here ot hack their device to pieces.
Click to expand...
Click to collapse
Then this procedure is obviously not for them. That's perfectly okay.
nextelbuddy said:
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
Click to expand...
Click to collapse
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
organophosphate said:
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
Then this procedure is obviously not for them. That's perfectly okay.
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
Click to expand...
Click to collapse
Im only one person. I can appreciate your work into finding a valid work around and am in no way attempting to take that from you and im sure there will be many that will be happy and thankful with your hard work. Dont take what I said as any sense that this is how the community feels please.
keep on with your work!
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
nextelbuddy said:
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
lex1020 said:
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
Click to expand...
Click to collapse
That's a good reason!
Absolutely agree that you should be able to skip that step. AND no valid reason needed. Unless Google can show a valid reason for not letting you skip that step. I'm sure most of us have watched the Google, (and Facebook) 'net' close in around us. When I started on Android I thought it was so cool how it was all tied to Google and was cross device. Now I'm like: Google would you just get out of my way, I'll be more than happy to click on 'you' when I need something from you.
The latest insult is that annoying "Keep Shopping" prompt in the Play store. Clicking Back, and Keep Shopping does the exact same thing. I shouldn't have to do either. Since I used to be dropped back to the same place anyway.
While the initialization does require a Wi-Fi connection it does not require an Internet connection. I was able to connect to my printer Wi-Fi network and let the waiting bar run for 2-3 minutes then the initialization would continue to completion.
I didn't like this Google forced initial setup either but at least no information was broadcast this way. The Nexus 7 is very useful even when not connected to the Internet.
Chicken and egg
organophosphate said:
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery </path/to/clockworkmod.img>).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)​7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)​
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
Click to expand...
Click to collapse
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
violincello said:
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
Click to expand...
Click to collapse
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That's exactly what I did. I was sitting in a parking lot after purchasing my N7 and didn't have a hotspot nearby. I wanted to play with my tab for a few before heading home so I just fired up WiFi Tether on my Rezound.
Sent from my Nexus 7 using xda app-developers app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Click to expand...
Click to collapse
Absolutely. As I mentioned in the OP, this isn't the fastest solution. Hell, you can probably tell I don't even recommend it for common scenarios.
That said, the approach *does* work. Before I started this I searched and was unable find any other way to accomplish the specific goal of skipping/disabling WiFi connection during initial setup. Therefore, when I was finally able to get it working I wanted to document it for the community.
dr.m0x said:
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I tweaked the OP to indicate this more clearly.
Simply
Andie00 said:
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
Click to expand...
Click to collapse
When it happened to me, i just restarted it. It then booted to the homescreen.

Ok, how do I change wifi settings?

Let's say I pick up the ChromeCast put it into my pocket and take it to a friend's how to show it off. It still has my SSID programmed into it.
How do I reset it, while at his house, so that I can put her SSID into it?
I wonder if the hardware button resets it. I didnt see anything in the manual though.
I ran into this problem yesterday. I think you have to hit that little reset button because I couldn't change it at all.
If you take the Chromecast to a new location, it will display a screen stating that it cannot find the wifi it was originally configured to. At that time, it will broadcast itself as a wifi access point, and you can just run through setup again. ( Try google.com/chromecast/setup )
Alternatively, if you have an android device, you can download the Chromecast app to do some minor configuration. I found this was the easiest method to access the device on the same wifi network, and get details like ip address and so forth. It also looks like it's Google's method to install new apps to the device when they become available.
For a PC:
google.com/chromecast/setup
For Android:
Reset button.
That's all that works for me.

[Q] How to achieve this security setup

Ok so I have a strange setup that I would like to get working on my MotoX. I have delayed lock installed on my phone because I hate having to input the code every time I pick it up but I need some security on it. Right now I have it lock after 3 minutes of inactivity. So if I'm working on something or texting someone it doesn't keep locking on me. I would like to add the wifi plugin so that my phone will stay unlocked when I am at home. When I am enjoying media at home on my chromecast/roku/bluetooth speaker it is annoying to have to enter the code to make changes. I know netflix and certain apps display the basic controls on the lockscreen but my roku remote app for example would be nice. I can't just leave the phone unlocked whenever it is within range of my WiFi however. I have roomates and a completely vulnerable phone is just asking for trouble. What I would ultimately like to be able to do is have delayed lock keep the lockscreen off when I am on my wifi and activate another app that will password protect certain apps so that I can access the basics while protecting important things like my messages, photos, etc. When i leave home and disconnect from my wifi I would like the lockscreen to engage again via delayed lock but also the individual app codes to turn off as well as i don't want to have to enter two codes to get to my stuff. I know there is probably a way to achieve this but I haven't found a clean way to do it. I understand the best way to do it might be tasker, but I don't have any experience working with tasker.
thanks

Security and touchless control

Anyone figure out how to have a lock screen and use touchless controls... you know... touchless? Giant gaping hole by Moto.
Whoa - documentation here https://motorola-global-portal.cust...a_id/94881/p/30,6720,8696/action/auth#privacy
This implies we have the ability to do this but I'm not seeing the setting anywhere???
How do I use Touchless Control with the lock screen?
Touchless Control now includes two new features to make using Touchless Control with the lock screen easier. The first is voice pin entry. If you use a numeric pin code you will be prompted by Touchless Control when you encounter the lock screen to speak your pin. Simply say your pin code to unlock the phone to complete your request. The second feature is to allow the Google application to run in front of the lock screen without needing to unlock the phone. This feature requires you to agree to the terms and conditions before you use it. Enabling the feature can be done by agreeing to the notification or turning the feature on manually within Settings -> Touchless Control
Using Open Mic+ seems to be a viable alternative. Does it use the low power core from Moto though?
km8j said:
Anyone figure out how to have a lock screen and use touchless controls... you know... touchless? Giant gaping hole by Moto.
Click to expand...
Click to collapse
It's a necessity that it will not work as you want it if you secure your phone (there's really no way to have your phone be secure and has full access to the touchless controls). Your best bet is to buy something like a Cobra Tag alarm and use it as a trusted bluetooth. Turn it on/carry it with you whenever you don't want to have to unlock your phone. I use my car's bluetooth to keep my phone unlocked while driving. It works great because you can wake the phone up and tell google now to navigate somewhere or ask about the traffic all without touching your phone. I think the trusted bluetooth is another great feature that Motorola included that separates it from other phones out there currently.
I've also been beta testing the new SkipLock app for it's developer. It allows you to disable the lock screen when you're connected to trusted wifi points like at home and work. I've been using it a couple days and it has been working well.
http://forum.xda-developers.com/showthread.php?t=2523069
dustPile said:
I've also been beta testing the new SkipLock app for it's developer. It allows you to disable the lock screen when you're connected to trusted wifi points like at home and work. I've been using it a couple days and it has been working well.
http://forum.xda-developers.com/showthread.php?t=2523069
Click to expand...
Click to collapse
Egh this doesnt really solve issue because you could be at the office all day long. You dont want your phone unlocked there.
km8j said:
Egh this doesnt really solve issue because you could be at the office all day long. You dont want your phone unlocked there.
Click to expand...
Click to collapse
NFC tag on your desk?
shempmalone said:
NFC tag on your desk?
Click to expand...
Click to collapse
still too many use cases where this doesn't apply...
moto missed the ball here. this should be user changeable option. there is no security concern here. you dont have to give someone access to the messaging app, just send the damn message.
I use tasker + secure settings to keep my phone unlocked when within range of both my work or home wifi. I feel secure enough at work that I'm not too worried about having it unlocked. Anything extremely sensitive is locked up anyway. I also use my truck's BT as a trusted device which keeps it unlocked there as well.
So basically my phone is unlocked unless i"m not in my normal places.
Dmtalon said:
I use tasker + secure settings to keep my phone unlocked when within range of both my work or home wifi. I feel secure enough at work that I'm not too worried about having it unlocked. Anything extremely sensitive is locked up anyway. I also use my truck's BT as a trusted device which keeps it unlocked there as well.
So basically my phone is unlocked unless i"m not in my normal places.
Click to expand...
Click to collapse
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
mechanical tool said:
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
Click to expand...
Click to collapse
I've been using this setup for a while. I'm sure I didn't just figure it out but saw it somewhere but I don't have any idea where. The only gotchya is that with 4.4 you need to use the beta version of secure settings.
I use pattern lock, so I just create a task when connected to wifi to disable pattern lock. Secure Settings does need to have the 'helper app' installed too.
mechanical tool said:
Did you follow any specific Tasker guide on how to set that up? I have tried setting it up and haven't have much luck.
I have however just tried Skipunlock and it works well on my Moto X with 4.2.2.
Provided I can get it to work properly, I would rather use Tasker so that I can set it up to unlock when "near" a wifi network rather than being connected.
Click to expand...
Click to collapse
Here's the two Tasker projects I've been using to unlock my device while connected to a "safe" Wifi network. One of the projects maintains a set of variables that can be used as states or referenced within tasks. The other project handles the locking and unlocking, and depends on the first project. It's was working fine on my Galaxy Nexus for a long time, and appears to work fine on the Moto X as well.
There's a lot in the "states" project that's not needed for locking/unlocking, but it comes in handy for other things. You can probably just change the "Wifi Connected" state to a "Wifi Near" in the myTRUSTEDWIFI profile, and get rid of the Wait action and uncheck the "if" box in the remaining action in the exit task.
Yes!!!! New version of touchless control fixes this!!!
Sent from my XT1053 using Tapatalk

[Q] Smart unlock:places

Smart unlock: places is not working any longer. I have GPS locations turned on, set to High accuracy, Smart unlock is turned on and is also enabled in my trusted agents, and my home address is correct. This was working a couple days ago. But then suddenly stopped. I've also done a reboot several times. Any help please.
I heard something about there being a problem with the predefined locations "home" and "work". Try setting a custom trusted place and see if that works...
my experience says GPS for the Smart Lock is a bit off.....this workaround has worked for me and others:
leave your Home location, but add another one. In my case when the Map came up, it showed me in a slightly different location. adding that and keeping Home, has me working.
my home is at 472, and usually GPS gets it correct or sometimes its 470.....Now, in Smart Lock, it shows my home as 500.
HTH....GL
Thanks guys! I added my neighbors address. Lol. It seems to work now.
youre welcome, glad its working for ya!

Categories

Resources