yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] mercado79:
It happened with both PIN and Pattern lock. I also thought it might be related to using different kinds of reboot scripts or apps, be it from with the Titanium Backup app or using Quick Reboot, and so I started shutting down manually and the same thing happened.

The biggest problem was that until this weekend, I had no way to make Nandroid backups because SafeStrap isn't yet compatible with Kit Kat, but someone figured out a work around. So, I don't mind troubleshooting since I can finally come back quickly.

********

Before you put more time into this, let me try what you suggested above and get back to you. For one, I just reinstalled and shutdown manually (using pattern and the wifi plug-in) and it's working.

Sent from my Moto X
[Paid Software Announcement and Discussion] mercado79:
Alright. I have some test results for you.

Using Pattern lock:

Shutdown (normal): No problem.

Reboot via Xposed/Gravitybox Advanced Power Menu (APM): No problem.

Reboot Recovery via Xposed/Gravitybox APM: No problem.

Reboot Recovery via Titanium Backup's Menu Option: Bug manifests itself. Can't recover from it.

Soft Reboot via Xposed/Gravitybox APM: Bug manifests itself. Can't recover from it.

Using PIN lock:

Shutdown (normal): No problem.

Reboot via Xposed/Gravitybox Advanced Power Menu (APM): No problem.

Reboot Recovery via Xposed/Gravitybox APM: No problem.

Reboot Recovery via Titanium Backup's Menu Option: Bug manifests itself. Screen goes black, but eventually boot completes. In this case, my homescreen widgets were corrupted (Nova Launcher). No lock required until after it finished loading up at which point it shut off the screen and then requested a password.

Soft Reboot via Xposed/Gravitybox APM: Bug manifests itself. Screen went black, but eventually it completed. (Can't remember now if I held in power and attempted to boot again or if it fixed itself on the first shot). No lock required until after it finished loading up at which point it shut off the screen and then requested a password.

Either way, it seems that it depends on the method the dev uses to implement reboot and reboot recovery. In the case of Titanium (and Quick Reboot, etc.) there's no shutdown followed by a reboot. It's as if the power was pulled. In the case of APM via Gravitybox, I actually see a shutdown message and even the Delayed Lock root access toast on screen. I imagine this is because Delayed Lock is relocking the device before it shuts down.

Side note, on Moto X devices that have locked bootloaders, the current root process requires that the user reboot into "recovery" (which has been replaced by a modified boot image) in order to disable system write protection. That's the main reason I reboot into "recovery" at all. Also, when using SafeStrap, there's an option in the tool itself that says "Reboot recovery". I think that too shuts down ungracefully, but I didn't test it this time around.

Don't know if you'll have a solution for me (us Moto X users), but it'd be great to not have to worry about what app we're using to reboot. Also, let's say I stop using apps to reboot / reboot recovery, what if an app causes a boot loop / unplanned reboot? Do you think that would also lead to the same bug manifesting itself? If so, then maybe I really shouldn't use the app (with Pattern lock at least).

Thoughts?
[Paid Software Announcement and Discussion] j4velin:
okay, I guess the bug is caused by Delayed Lock changing the ownership of one of the system files, where it disables the lock. if it receives the DEVICE_SHUTDOWN broadcast (which is send by the system on a proper shutdown), it restores the old owner value. if you use a root script, the system does not send this broadcast, so the app doesn't know that the device is going to shut down.
[Paid Software Announcement and Discussion] mercado79:
Would you happen to know what the proper shutdown command is/should be? I think I may send requests to the devs of Titanium Backup, Quick Reboot, and others as I come across them, asking them to consider doing reboots the right way.

What do you think about my last question in my response above?
[Paid Software Announcement and Discussion] j4velin:
well, they need to send http://developer.android.com/reference/android/content/Intent.html#ACTION_SHUTDOWN intent before shutting down. not sure if that's possible though, as only the system is supposed to do this.

boot loop should not be a problem, as (on a proper shutdown) the ownership is restored on shutdown. Delayed Lock changes the ownership again when receiving the BOOT_COMPLETE broadcast. so if the bootloop happens before that, it shouldnt a problem. any other "unplanned" shutdown however will cause this issue (it seems to only effect some devices, Nexus 4, 5 & 7 seem to not care about who the owner is at all)
[Paid Software Announcement and Discussion] mercado79:
so, fixable from your end do you think? is it on your to do list for bug fixes? it stinks that this only started with android 4.4. never had a problem prior to that on my nexus devices or on this moto X.

oh, i meant to say (in response to your "device incompatibility" comment on Google Play), pin lock did actually work for me; however, I it required a reboot before it'd work consistently. maybe that was a fluke though as i was only testing for a few minutes this morning.

***EDIT***

Two more comments. I thought I'd mention that the first time I came across this bug, it was due to my battery dying, not rebooting using an app/script. Also, I've emailed the Titanium and Quick Reboot devs. We'll see what they say...
[Paid Software Announcement and Discussion] imre.fabian:
Uninstall Root-Helper for Delayed Lock

To J4velin:

You write that to uninstall Root-Helper for Delayed Lock an app like Titanium could be used.

Now I have installed Root-Helper for Delayed Lock and would like to uninstall it but I cannot find the correct App-name.

I have installed the Dutch language version of ICS.

How can I recognise the correct App?

Btw, it works so it should be correctly installed.

Cheers,

Imre Fabian
[Paid Software Announcement and Discussion] j4velin:
I think it should either be "SystemHelper" or "RootHelper"
[Paid Software Announcement and Discussion] imre.fabian:
SystemHelper

OK, I've found it allready. it was SystemHelper. The icon didn't help though!

It works now but not entirely to my satisfaction. It involves several different Apps that do not all perform as expected. I will keep on looking for a better solution.

Thanks and Cheers, Happy Christmas or whatever.

Imre
[Paid Software Announcement and Discussion] mercado79:
I have no idea what has changed, but... I'm no longer running into any issues. I'm at a loss for words. I decided to give SkipLock a try (since the dev completely rewrote the app) and it worked without any problems. I was shocked that none of the quirks/bugs appeared and so I thought to give Delayed Lock a try. Absolutely no problems. I literally tried a dozen different security configurations and / or methods of shutting down/rebooting just trying to get my phone to lock up and... nothing.

[MENTION=1246899]j4velin[/MENTION], I do not envy the work you do trying to troubleshoot bugs like this that crop up out of the blue and disappear without notice. In my case, maybe it was a conflicting app that has since been updated. There have been plenty since I took a break from Delayed Lock last month (which was awful by the way... I do love your app).

Thanks again for the great work. Looking forward to the new 3.0 release. The description in the Play Store mentions it, but I haven't gotten the update pushed to me just yet. Looks like it'll be a nice one.
[Paid Software Announcement and Discussion] stackingreasyBBs:
Hi j4velin,

Just got the 3.0 update the other day. It looks great, but I'm curious: in the previous version there was an option to keep the phone unlocked if at least one of the plugins was active (can't remember the exact wording, sorry). Did that option go away for some reason?
[Paid Software Announcement and Discussion] j4velin:
yes, I currently removed that option, it's now the default behaviour to keep the device unlocked while at least one plugin is active. I might add it again as an option if there is interest, but from what I got it seems that most users want it that way
[Paid Software Announcement and Discussion] sansnil:
I would very much like to see this option return as it breaks Josh's Tasker plug-in. In the previous version of Delayed Lock I was able to disable this setting and the Tasker plugin worked great but in the current version there's no way to resolve this.

Please add it back, thanks!
[Paid Software Announcement and Discussion] Ingenium13:
Josh here. How is your profile setup? I haven't had any issues with it on the latest version, but I can try to replicate your scenario if I know how you're using it.
[Paid Software Announcement and Discussion] sansnil:
Hey Josh -- I sent you a PM so as not to clutter up this thread with a lot of back and forth.
[Paid Software Announcement and Discussion] stackingreasyBBs:
Gotcha, thanks :)
[Paid Software Announcement and Discussion] Akira181:
I have a Nexus 5, unrooted, and latest stock android. I'm running the trial version at the moment and having some issues, wonder if there is something wrong with my settings.

I've got my location unlock set up and I reduced the range from 100m to 20m as I felt 100 was quite big. I have GPS tracking apps always running in the background, not sure if that would help with location accuracy, but the location plugin is always able to unlock my phone in the correct places.

The issue I have is a lot of the time is that even though the location plugin is able to unlock my phone correctly, the enable wifi when entering location does not always work. The notification bar will have the delayed lock notification saying "disabled by location" but wifi remains off.

Any reason for this? The wifi signal is strong in my apartment and I can get a signal across the street. Shouldn't have any issues in connecting.
[Paid Software Announcement and Discussion] j4velin:
yeah, I think that definitly helps

Reason might be that the WiFi is only enabled once when "entering" the location. So if the location plugin enables the wifi, but you're not really already in range of your wifi network, it might get turned off again (for example by the wifi plugin)
[Paid Software Announcement and Discussion] bornoxt:
Thanks, that explain why my WiFi isn't always activated properly by the location plugin.

Other question:

Is there a way to reduce the time until my N5 remembers that I'm in a "safe" location?

If I get home from work, park my car and go inside (2-3 minutes) the location plugin doesn't recognize that I'm at home and doesn't enables my WiFi.

If open the location plugin and tap the button to show maps it didn't show me my actual location.

I'm pretty sure that this isn't a problem of your app but maybe you have some advice.
[Paid Software Announcement and Discussion] sansnil:
@j4velin, I haven't been able to resolve this even with Josh's help (big thanks!). I'm not sure exactly why Josh can't replicate it but it may be because he's not using the DL Widget, or combination of plugins that I am (BT, Wifi, Location, Remote Lock) -- but if I use the previous version with the 'Keep unlocked if any plugin is active' it works perfectly. Is there any chance you can restore this option? Perhaps make the default setting checked if you think most people want that?
[Paid Software Announcement and Discussion] j4velin:
could you tell me what exactly doesn't work? I also use the tasker plugin and I think it works just fine. The new version should behave just like the old version with the "keep unlocked if at least one plugin is active" option checked. I don't think bringing back an option to disable that would help you in any way
[Paid Software Announcement and Discussion] sansnil:
Oh sure -- basically the Tasker plugin stops working to lock/unlock DL. If I start from a refresh reboot, I can use the Tasker plugin just as it should work. But after a short while, sometimes after using the DL widget to manually toggle lock/unlock but also sometimes just in regular use, the Tasker plugin stops working to toggle DL's lock state. I have a feeling that one of the plugins or the widget is registering as an 'active plugin' and therefore the Tasker plugin isn't able to lock the device. I have installed and use the WiFi, BT, Location, Remote Lock, and Tasker plugins plus the DL widget. If I revert back the the previous pre-3.0 version I have the same issue if the 'keep unlocked if one plugin is active' setting is enabled, but if I disable it, the Tasker works perfectly. That's why I think it must be that setting.
[Paid Software Announcement and Discussion] j4velin:
Oh okay, then the app is working as expected (it will keep the device unlocked while one of the plugins wants to keep it unlocked). If you want the "lock the device as soon as one plugin wants to lock" option, then please post it to https://j4velindevelopment.uservoice.com/forums/203548-android-apps and I'll implement it again if there are more users wanting that feature
[Paid Software Announcement and Discussion] sansnil:
Done. I was hoping there wasn't a tremendous amount of effort around restoring the functionality since it existed in previous versions.

For now I'm going to revert back to the pre-3.0 'upgrade' since there's no benefit beyond the cosmetic UI interface.
[Paid Software Announcement and Discussion] j4velin:
actually, there wouldn't be much work necessary to restore that option, but I just want to remove the options which nearly nobody uses. I got a lot of negative reviews saying "the app is too complicated" - the average users seems to be confused with too many options...
[Paid Software Announcement and Discussion] sansnil:
I get that. I can't believe how stupid average users are lol. Maybe you can put it in as a set of 'Power User' options, or better a hidden advanced settings menu. I'm sure it's hard to satisfy both average users and power users at the same time.
[Paid Software Announcement and Discussion] NoSpamDan:
Missing the inverted UI on the new version, although I don't open it every day or anything. Not a fan of blinding white. Great app though!
[Paid Software Announcement and Discussion] smalis:
Great app, been using the paid version for years now. One feature request - would it be possible to give users the option to color the status bar icon? All my icons are ICS blue except for the white DL unlocked icon, and it would be nice to get it to match. No biggie, but thought I'd ask.

Thanks!
[Paid Software Announcement and Discussion] diiacoo:
i love this app!

---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------

hi
[Paid Software Announcement and Discussion] chrisrozon:
I'm curious about the BT Low-Energy function - running 4.4.2 on a Nexus 4 with an Automatic Link (www.automatic.com) in my car.

Delayed Lock isn't seeing the Automatic, are there any tricks or suggestions to get them to recognize each other? I know it's an experimental feature so I won't be heartbroken if it doesn't work ;)

(Apologies if this has been addressed already, 'Automatic' and 'Link' are the two worst words you could chose for your product name if you have any hope at all of search engine optimization!)
[Paid Software Announcement and Discussion] andy o:
The BT plugin should be seeing the list of all paired devices even if they're not connected. Your adapter is not showing on the list when pressing "add all paired devices"? I also have an OBDII adapter, it just shows up.
[Paid Software Announcement and Discussion] chrisrozon:
OK, I disconnected and re-paired the the dongle and it works perfectly now. Sorry for the false alarm :)
[Paid Software Announcement and Discussion] jonwdavidson:
Experiencing same MotoX bug as mercado79

[MENTION=1246899]j4velin[/MENTION], I'm afraid I've been experiencing the same bug as [MENTION=1257613]mercado79[/MENTION]. I'm on a VZ Moto X Developer Edition running 4.4, rooted with SuperSU, and also Xposed Framework. When the bug occurs I'll have an unresponsive black screen after boot which flashes periodically (for 1 second every ~20 seconds or so) and then goes to black. Even during the flashes it is unresponsive to touch and I have to revert to a nandroid backup or factory reset in order to resume.

It took me a while to narrow down the issue to DelayedLock but I've been experiencing it since initially setting up the device in early December. Here's what I've figured out so far:

It occurs after an ungraceful power-off or restart (e.g. crashes, power loss, etc).

It will occur upon reboot after DelayedLock is upgraded/re-installed if it hasn't been re-authorized for root privileges in SuperSU

It occurs consistently after an adb reboot command

I have a suspicion that it's related to the MotoX Active Display functionality as the frequency of the brief screen flashes roughly matches cadence of the Active Display "breathing"

While some of these are avoidable (being careful following a DelayedLock upgrade, not using an adb reboot command, etc.), it seems like it catches me every week or two and I'm forced to restore from a backup and weep over smaller things I've lost. The frustration regularly tempts me to uninstall DelayedLock, but I really love the app.

I think I've identified at least a few ways to evoke the defect and I'm happy to test anything to help diagnose and/or resolve it. Thanks.
[Paid Software Announcement and Discussion] mercado79:
Jon, sorry to hear you're running into this now. It hasn't affected me in weeks, thankfully, though I can't say why. Very strange. Let me know if I can help out with testing or troubleshooting. Also, thanks for the reminder to create a fresh Nandroid!

Sent from my Moto X
[Paid Software Announcement and Discussion] sansnil:
Hey guys, this is kind of a shot in the dark but it sounds a little similar to an issue I was having with DL awhile back so it might be worth trying the next time you experience it.

The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:

/data/system/locksettings.db

/data/system/locksettings.db-shm

After deleting those try rebooting and see if you can make it back.
[Paid Software Announcement and Discussion] floepie:
Would there be a chance of allowing the wifi plugin to work in the opposite manner? That is, when connected to specified wifi network, the delayed lock function turns off such that a PIN or other secure lock would be required?
[Paid Software Announcement and Discussion] j4velin:
there is a suggestion for such a feature but I doubt many people would need it
[Paid Software Announcement and Discussion] Ingenium13:
If you have Tasker you could use my Delayed Lock plugin and make it do this.
[Paid Software Announcement and Discussion] joluke:
Very handy application :D :good:
[Paid Software Announcement and Discussion] KONY2000:
hello i read a few of the 70 pages of that thread but couldnt see the update

i did read on google play's incompatibility section that using DelayedLock with pattern unlock will not work with SAMSUNG GALAXY S4

I have this phone and i did install the system helper, because i somehow understood (maybe wrongly) that it would help bypass that incompatibility

i'm sick and tired of PIN Password (when i'm out of my home wifi), and i would like to be able to used pattern unlocking as before

is that now possible or not with that app and galaxy s4 ?

thanx
[Paid Software Announcement and Discussion] j4velin:
it's not, the app does not work with the S4 when using pattern lock
[Paid Software Announcement and Discussion] KONY2000:
OK thanx for the answer

it will save me some time trying to solve that issue
[Paid Software Announcement and Discussion] jonwdavidson:
[MENTION=724527]sansnil[/MENTION], thanks for the trick, just had another failure that would have typically required restoration from nandroid backup. Deleted the two files you mentioned and was able to boot successfully - excellent! Lost some security settings and wallpaper but nothing significant apparently.

[MENTION=1246899]j4velin[/MENTION], any thoughts on this issue? I'd love to see a longterm solution with DL. Thanks!
[Paid Software Announcement and Discussion] j4velin:
Delayed Lock needs to change the permissions of these files if you want it to work with the pattern lockscreen. All the device I have, don't have a problem with these files having another permission then they had before using Delayed Lock, but it seems like some devices have. Delayed Lock restores the old permissions on shutdown but if there is no proper shutdown then it can't change the permissions
[Paid Software Announcement and Discussion] KONY2000:
i installed the widget and set it up to TOGGLE-KEEP UNLOCKED

first of all, i read in a few posts back that you removed some features because the average user wants to keep it simple...that's fair...but then i don't quite undestand why there are so many options in the widgets when the difference betwen some doesn't really appear to be so obvious :

TOGGLE LOCK

TOGGLE-KEEP UNLOCKED

ENABLE-DISABLE DELAYED LOCK (doesnt seem to work properly as i once disabled it but i was still asked (more than one time) to do the password)

Honnestly there might be a way to make it less confusing by merging some features there

anyway, i wanted also to point out the strange behaviour of the widget sometimes :on TOGGLE-KEEP UNLOCKED, if i ENABLE the Lock and switch off my screen...then i would have to type my password logically...fine...but then why oh why the widget would still mention "DISABLED" when i actually asked it to enable the lock...

another time it was mentionning ENABLED, on the same occasions...all in all this information doesn't seem to be super reliable and it ends up confusing the user a bit more actually regading "what is the actual status of the lock?"

thanx
[Paid Software Announcement and Discussion] andy o:
I've been thinking about encrypting my N5 (stock, rooted). I understand that pattern lock can't be used with encryption, but does Delay Lock work? There was a previous post that implied it didn't but it was made almost 2 years ago.
[Paid Software Announcement and Discussion] j4velin:
I'll add some explaining text in version 3.1

sorry, but I don't understand that question. The app does not work with full device encryption enabled if that's what you mean
[Paid Software Announcement and Discussion] andy o:
Yeah, that's what I meant. Thanks.
[Paid Software Announcement and Discussion] itsano:
Would it be possible to add a feature to stop sync when disconnecting from Wi-Fi? :)
[Paid Software Announcement and Discussion] mrsaccess:
It seems to work for now. Let's see if it stays this way. :)

Hello, my girlfriend bought today a license to delayed lock through IAP as her trial period expired yesterday. The problem is that now the app doesn't work. We tried everything we could think of (uninstall - reinstall, reboot, remove/grant admin rights, etc). She has a Nexus 4 with the latest update from Google.

The app just seems to not want to lock the phone anymore. I enabled the app's notifications and they never show for locking (could this indicate that the app doesn't even try to unlock? ). Other notifications (for example to grant admin rights) work fine.

I use the unlock key version on my phone for almost a year now and I am very happy. Any help is appreciated.
[Paid Software Announcement and Discussion] poo706:
So I had previously purchased delayed lock and managed to get it converted when the licensing changed. Decided to try the location plugin but it keeps telling me to buy delayed lock to use this plugin. What should I try?

[poo]
[Paid Software Announcement and Discussion] ositoe:
I'm having this same issue

I've tried reinstalling the main (trial app), the unlock key, and the location plugin, but it still hasn't worked.