yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] Brent212:
After fiddling with settings for way too long, I've finally gotten this working (so far) with my Galaxy S5 and the "pattern" lock screen. Here are my settings, in case it'll help anyone with the same/similar phone. My phone is rooted, btw, with the SuperSU app granting root access to apps that request it.

System lock screen settings:

- Lock type = pattern

- Lock automatically = immediately

- Lock instantly w/ power key = checked

System lock screen settings:

- Lock type = pattern

- Lock automatically = 5 seconds

- Lock instantly w/ power key = checked

Delayed Lock settings:

(first page)

- Enabled = checked

- Admin permission granted = checked

- Lockscreen selected = FaceUnlock or pattern

- System delay disabled = checked

(second page)

- Time = 1 seconds after last unlock

For some reason Delayed Lock always disables the lockscreen when the phone is unlocked, even when no wifi or bluetooth connection exists. Setting this to 1 second makes it enable the lockscreen somewhat immediately, so with the notification disabled in settings, it simulates having this weird "always disable lockscreen" feature turned off.

- Wifi

- Enable lock when disconnected for 2 sec

- Bluetooth

- Enable lock when disconnected for 2 sec

(third page)

- Settings

--- Require manual unlock once = unchecked

--- Show notification = disabled

--- Disable swipe lockscreen = unchecked

--- Wake to lock = checked

SuperSU settings:

- Turn off "toast" notifications for Delayed Lock. Otherwise I get a "toast" pop up message saying Delayed Lock granted root access everytime I unlock the screen, even when not connected to wifi or bluetooth.

I'm using Delayed Lock to disable the lock screen when on certain wifi networks or connected to my car stereo through bluetooth.
[Paid Software Announcement and Discussion] hgoldner:
Just curious, are you running the Xposed Framework as well?
[Paid Software Announcement and Discussion] Brent212:
No, not running that. Stock ROM that came with the phone, but rooted.
[Paid Software Announcement and Discussion] tatrajaan:
I finally remebered that I had Samsung account.

I logged in from web and set OPEN SCREEN.

Screen opened and after that the old PIN worked again :))

Very strange.
[Paid Software Announcement and Discussion] hotsync100:
[MENTION=1246899]j4velin[/MENTION] Any plan to fix the reboot bug on MotoX KitKat 4.4.2?
[Paid Software Announcement and Discussion] NicoDJ:
Thanks for adding the 'Simple Lock now' widget.

But I'm sorry to say that there seems to be a problem with it.

When I place the widget it works as expected, but when i make the phone sleep (short press of the power button) and then wake it again, that same widget doesn't work anymore.

I have a stock Motorola Milestone 2 phone.
[Paid Software Announcement and Discussion] Therev86:
Im using the same motorola and it's working fine.. dont know what i did differently
[Paid Software Announcement and Discussion] j4velin:
mh yeah that's a strange problem ^^

somehow I was able to reproduce the bug on my phone but I still don't extactly know why it doesn't work... nevertheless, I slightly changed the widget's behaviour and now it seems to work again. I just uploaded version 2.0.4 which contains this fix and should be available on the next market refresh. Hope it works for you too
[Paid Software Announcement and Discussion] NicoDJ:
Yes, works perfectly now.

Thanks a lot!
[Paid Software Announcement and Discussion] GTIVRon:
Not working with Widget Locker. Can't tell you how specifically because it does something different all the time.

SGS phone (captivate). Sometimes I hit the power button to unlock and it goes straight to home screen. (been doing that consistently, no longer shows widget locker screen...)

Before this it would show the nag screen then show widget locker even if i wake the phone immediately after the screen turns off.

Before that it was acting like it always did. without running the app.

If i hit the lock button manually, then unlock, it shows the standard lockscreen then quickly changes to the widget locker lock screen then that closes and it shows the nag screen. Other times i hit lock and it turns the screen off, then when i hit unlock it goes back to the home screen instead of WL lockscreen.

Very inconsistant and not a fix for the annoying widget locker locking itself every time immediately after screen times out. But at least then I know what it's going to do, with this app I never know if im going to end up on my WL lockscreen, the home screen, or the nag screen...
[Paid Software Announcement and Discussion] GTIVRon:
Just now when i went to unlock it showed the nag screen, after closing it took me to widget locker screen. then after unlocking i was at the nag screen again...
[Paid Software Announcement and Discussion] hi-tech:
Nice app, must have for non sense based roms (missed the "lock screen after...." setting. Is their away to update the slider arrow image (basic skinning) and remove the "slide to unlock" and percentage texts on the simple lockscreen? Otherwise perfect.
[Paid Software Announcement and Discussion] j4velin:
sorry for my late response, had very limited internet access these last days...

@GTIVRon: have you checked the "unlock widgetlocker" option in the settings? can you send me a bugreport through the "report a problem" button (so that a small log is included) the next time it happens? thanks

@hi-tech: thanks :) i will try to implement some skinning stuff for the lockscreen. edit: version 2.0.6 will include all the features you requested. release should be in the next days
[Paid Software Announcement and Discussion] Tanker Bob:
I'm using delayedlock on a Moto Atrix with Android 2.2.1. Delayedlock seems to work at first, but after several cycles of operation it stops invoking the device screen lock. I tried the admin lock which worked better, but always presented delayedlock's lock screen after unlocking the system, requiring me to clear two lock screens to use the phoe. So, I turned th admin lock off.

More troubling, today the phone started turning itself on rather than going to the system lock, draining the battery. The delayedlock lock screen remained on the screen. I turned the device off, but it came on again later.

I'm using the fingerprint unlock for the system, and am about at my wits end with delayedlock. The concept is very helpful, but its behavior has not been. Any help would be appreciated.

Added: I'm also using the BT and WiFi extensions, both of which seem to work fine. I have the lock enable/disable widget on a home screen as well, and it also seems to work OK. I'm going back to the admin lock for a while, but would really appreciate if the delayedlock lock screen did not appear after clearing the system screen lock.
[Paid Software Announcement and Discussion] j4velin:
hey, sorry that it doesn't properly work on your device. can you send me a log through the "report a problem" function if the problem with the missing lockscreen occurs again?

i thought i implemented a method to close the simple lockscreen when the real lockscreen appears, but it seems that i have forgotten that - will update it as soon as i'm at home again (probably monday)
[Paid Software Announcement and Discussion] Techvir:
Is there a way to limit the phone from waking up with only the power button.

(Now with delayed lock app phone wakes up with anyhardware button)
[Paid Software Announcement and Discussion] Tanker Bob:
Thanks, sent. Since it hasn't activated the system lock in hours, I assume that's current in the log. Have a great Easter.
[Paid Software Announcement and Discussion] Tanker Bob:
I re-enabled the Admin lock. That seems to solve the system lock triggering issue. The appearance of the light lockscreen seems intermittent after clearing the system lockscreen. Sometimes it's there when I unlock the system lock, sometimes it is not.
[Paid Software Announcement and Discussion] j4velin:
unfortunately not. without a lockscreen, the device will wake up with every button

i just published a new version to the market, hope this fixes your problem
[Paid Software Announcement and Discussion] Tanker Bob:
Yes, it does. Clearing the system lock screen no longer brings up the DelayedLock light lock screen. Thank you!

Just a note, but the Moto Atrix requires the Admin option for DelayedLock. Otherwise, it rarely enters system lock and the screen can come on and remain on unexpectedly.

Great application! Thank you for your continued work with it.
[Paid Software Announcement and Discussion] CCCMikey:
Galaxy Tab?

Hi :)

I have a GT-P1000

Still on the trial version. It seems to only work intermittently even though I'm attached to my home WiFi.

When it doesn't work, and I unlock using a PIN it says "Lockscreen should be disabled now..."

Not sure if it's not compatible, or if it's because it's a trial version. I assume that because I'm using the WiFi option the 10 minute limit doesn't apply?

When I leave the WiFi I get a message every 10 seconds or so "WiFi Disconnected - activating lock screen." It would appear no matter what application I was in so I had to uninstall the WiFi plugin.

The bluetooth plugin seems to work, using a bluetooth keyboard as a 'dongle'. Quite handy actually - just have to keep the tiny keyboard in another pocket, press a button on it (which wakes it up and pairs it) and I'm away.

Unfortunately I wanted to pair it with my Nokia E51, but the plugin requires an active bluetooth session, not merely the presence of the device.

Cheers, Mike.
[Paid Software Announcement and Discussion] substance12:
how do I prevent the settings from opening after I unlock the simple lock screen?
[Paid Software Announcement and Discussion] j4velin:
@CCCMikey:

the trial version disables the lockscreen only for max 10 minutes, even with the plugins. but besides that, the trial is the same as the 'normal' version, so if it the trial doesn't properly work with your device then it's very unlikely that the paid version works - sorry :/

by reading the FAQ in the first post ;)
[Paid Software Announcement and Discussion] CCCMikey:
Righto. Well, perhaps it will work in the future. It seems to work but the WiFi plugin appears to have issues with this device.

I think yours is the only program that unlocks with Bluetooth and that is for me potentially more useful than WiFi unlocking as it allows me to use the mini Bluetooth keyboard as a security device.

Is it possible for your Bluetooth plugin to work simply by viewing visible devices, or is it only able to view active connections?

So, if the software works OK with the Bluetooth plugin, perhaps it's still worth it :)

Cheers, Mike

Edit: Bought it anyway. For $1 what does it matter :)
[Paid Software Announcement and Discussion] j4velin:
mh you could try the wifi plugin attached to the very first post in this thread: it doesn't reenable the lockscreen immediately but waits 60 seconds after disconnecting. maybe this will help...

as far as i know, the android system only sends broadcast when succefully connected/disconnected to a device. so actively searching for other devices would constantly drain battery...
[Paid Software Announcement and Discussion] j4velin:
If you mean the issue with the wrong ownership of the locksettings.db files after a hard-reset/battery pull: No, I can't fix that
[Paid Software Announcement and Discussion] dzap:
Would you mind updating your Play Store listing to note it as a device incompatibility? I was just about to factory reset my Moto X for a third time in 2 days before I did some heavy digging and found out that Delayed Lock was the root of the problem and deleted the lock settings files in recovery.

I just received this Moto X and was just going to RMA as I seriously thought this was a hardware defect.

I think the least you could do is warn future users of this...it clearly is a terrible bug.

I've banished this app from my Moto X and will be purchasing Skip Lock as it seems to work without this issue.

I do really love this app, and will be continuing to use it on my Nexus 5, but if the bug is unfixable on the Moto X, you should notify your users, by at the very least stating it in the Play Store description that it will soft brick your device.
[Paid Software Announcement and Discussion] j4velin:
Actually this is not a device incompatibility. If you need to hard shutdown your device, that is a hardware defect and you should RMA it.

I attached another version which changes the file ownership before and after each change if you want to test that

Edit: I guess this is kind of a fix, so I'll take my "not fixable" statement back ^^
[Paid Software Announcement and Discussion] dzap:
No the issue occurred immediately after I initiated a Soft reboot. Not a hard shutdown. I can replicate this easily on a clean install. Not a hardware issue and a hard shutdown can be initiated any Android device for any reason. Same issue that others with Moto X's have complained about in this thread since February...

Hmm. I may give this a shot. I'll let you know in a bit on how it goes. :laugh:
[Paid Software Announcement and Discussion] j4velin:
did you shutdown using the normal power button or did you use some root script? the power button cleanly shuts down the device and the system sends the SHUTDOWN broadcast then. delayed locks restores everything to the way it was when receiving that broadcast (assuming it gets root access then)
[Paid Software Announcement and Discussion] ssmaster:
Nevermore.
[Paid Software Announcement and Discussion] mhoepfin:
Things have been working great doing a bluetooth unlock. After the latest update this isn't working any more. Even though I am connected to the Bluetooth device, it doesn't unlock.

I have checked everything, removed and added back the bluetooth devices, etc.

Any ideas?
[Paid Software Announcement and Discussion] j4velin:
please try the attached debug version and send me the log if the issue occurs again
[Paid Software Announcement and Discussion] mhoepfin:
Just wanted to follow up, I deleted the bluetooth devices again and added them back and it is working again! Did not need the debug version.
[Paid Software Announcement and Discussion] dzap:
I used the Advanced Reboot Power menu provided by Gravitybox. It's an Xposed Module, but several ROMs the same feature.

Anyway, just to give you a heads up that I tried multiple apps like Titanium Backup and their reboot methods, the GravityBox reboot method, and the reboot methods in HKThemeManager and they all flawlessly rebooted my Moto X without issue. Doing some of these reboot methods before would send it into the SystemUI crashing and having to go into recovery to repair the system. Thank you very much!

Is there a reason you can't push this version the Play Store?
[Paid Software Announcement and Discussion] j4velin:
I did, but I'm already getting negative reviews because the "Delayed Lock has been granted root permission" is now shown too often -.-

Also note that Delayed Lock might not be the only app relying on the ACTION_SHUTDOWN broadcast, so in general I recommend powering down the device only with the power button
[Paid Software Announcement and Discussion] Sp0KI:
I didnt read all the posts with the shutdown problem. So sorry if i ask,

I used the reboot function of the xposed installer twice during the last 2 days and after every reboot my nexus 5 was in a bootloop. Very annoying :(. Did your app cause it? Is this the same problem which dzap had to struggle? And it is now fixed? I think i had the the fixed version before the bootloop. A lot of root permission notifcation appeared.
[Paid Software Announcement and Discussion] andy o:
I don't think it's the same issue. I've had the N5 "soft" reboot like that many times and this didn't give me any trouble like that. This seems to be a problem with the Moto X only.

Gravity Box provides 2 reboot options, you should just use "reboot", not "soft reboot".
[Paid Software Announcement and Discussion] Sp0KI:
I used a nandroid image with the bootloop and deleted locksettings.db locksettings.db-shm with recovery and the bootloop is gone. So happy I found the issue ;)

So the problem can also occur on a nexus 5 :(
[Paid Software Announcement and Discussion] ryuseiken:
Hello, since last update is not working correctly on my gt-i9506. I deleted data to start again and still not working the lock pattern, even setting it correctly.

Can you check if something is failing since last update? I bought the app and it is very useful in my day.

Greetings.

EDIT: After the last upgrade it worked again :D thanks
[Paid Software Announcement and Discussion] andy o:
[MENTION=1246899]j4velin[/MENTION] just a heads up. I installed Google Play Services 4.4, which has begun to roll out (slowly apparently) on my N5 and N10, and on both Delayed Lock got kind of screwed up. It's working, but when it should show the slide lock, it shows the pattern lock. You can still swipe in any direction and it will unlock though, so the pattern is not active, it just looks like it. With PIN unlock it's apparently working fine. Reboots don't fix it. I'm on stock 4.4.2.
[Paid Software Announcement and Discussion] acmcelwee:
Ditto. Just noticed this happening, as well.
[Paid Software Announcement and Discussion] khaytsus:
I'm on 3.3.9 on AOKP 4.3 and since the last update to Delayed Lock the phone was never locking, stayed on slide to unlock, so I manually set it back to pattern lock and now it's always on pattern lock, never slide.. Doh.

I might try reverting to the previous version, perhaps a bug in trying to fix Samsung weirdness etc.

---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------

And right after I post I check and find a market update which seems to have fixed it :)
[Paid Software Announcement and Discussion] ldsteele:
Info

Great info
[Paid Software Announcement and Discussion] andy o:
So that was a quick fix. Thanks [MENTION=1246899]j4velin[/MENTION]
[Paid Software Announcement and Discussion] tracerit:
Newest update seems to break my phone. I can't boot in. It just gets stuck at the screen after the "Google" screen, so in my case at the SlimKAT screen. I've narrowed it down to Delayed Lock, luckily I had a one day old nandroid backup whew!
[Paid Software Announcement and Discussion] sansnil:
See my post (link below) if that happens to again - it will at least get your device to boot.

http://xdaforums.com/showthread.php?p=50057958
[Paid Software Announcement and Discussion] diogo.sena:
lucky me too.. just today resolved to be more safe and made a backup..
[Paid Software Announcement and Discussion] dzap:
Soft Reboot restarts SystemUI which I need for HKThemeManager. A full reboot wipes the changes,. I know what the differences are, thanks.

---------- Post added at 07:46 AM ---------- Previous post was at 07:42 AM ----------

So...interesting. I still have my Nexus 5, and it died on me last night. Woke up this morning...wouldn't boot. Was scratching my head this morning wondering why. Disabled Xposed. Nope..that wasn't it. Disabled HKThemeManager..nope. Hmm. Odd. Flash different kernel. No...

...thought it over.. remembered seeing the Delayed Lock SuperSU prompt at some point last night again..and then thought "Oh god...it didn't."

Went into Recovery and deleted the locksettings.db and locksettings.db-shm file..

...and it booted.

So...now while this has fixed on the Moto X, it has now pushed the problem to the Nexus 5, which is way more popular. Uh...time to revert to the old apk I suppose? I don't mind using different apks on my different devices, but this is probably going to cause you a lot of bad reviews if this is bootlooping Nexus 5's, which is a lot more popular.

I recommend you post this fix to your Play Store listing for root users, as I'm sure a lot of N5 owners are going to be pissed off about this..

---------- Post added at 07:51 AM ---------- Previous post was at 07:46 AM ----------

Wish I could donate to you. Truly a lifesaver. You got my Moto X..and now..my Nexus 5 to boot back again.
[Paid Software Announcement and Discussion] j4velin:
So does anyone have this issue with a stock ROM? I spent the last 2 days trying to reproduce the issue on my N5, N7 (stock with root) and a Note 10.1 (CM) but without "success". Note that the last version of the app does not change the owner at all and reverts the chmod permissions after every access to the locksettings file. So I really have no idea what could be a problem with those files
[Paid Software Announcement and Discussion] Sp0KI:
Im using the xposed framework and the Stock n5 Rom. Didnt have a Problem before the updates. It seems some update broke it. But for now im not using your app, dont wanna risk another Bootloop. Although i really like the app.

Gesendet von meinem Nexus 5 mit Tapatalk
[Paid Software Announcement and Discussion] dzap:
I am stock on both my Nexus 5 and Moto X. Just rooted on both, so I can use Xposed and such.

Let me see if I can get it to do it again and pull some adb logs during boot for you so it can help you out.
[Paid Software Announcement and Discussion] tdotM:
Using Paranoid Android on my Nexus 5. Same problems as mentioned above - after the update my phone went into bootloops.

I reverted to a backup, uninstalled the app and installed the new version - now I can't give delayed lock root access.

Hope that helps a bit and I really hope the problem is resolved soon because it's a great app.

(Let me know if I can help - at least I know how to run a logcat if you want mine as well)
[Paid Software Announcement and Discussion] j4velin:
Okay let me rephrase the question: Anyone without Xposed having the issue?
[Paid Software Announcement and Discussion] diogo.sena:
Yes, n4 with cm11 and art

Enviado de meu Nexus 4 usando Tapatalk
[Paid Software Announcement and Discussion] aznxcp4lyfez:
Stopped working with pattern lock on motox

Pattern luck stays on with wifi and Bluetooth enabled

Pin and password works prefectly fine though.

Stock sprint rom with root
[Paid Software Announcement and Discussion] tdotM:
I have the same issues with and without Xposed.

i.e. Uninstalled Xposed, flashed PA update, tried a new install of delayed lock but I can't give it root access.
[Paid Software Announcement and Discussion] tdotM:
All working again - with PA and Xposed.

I had some other issues with my wifi and I did clean install. As far as I can tell I must have restored the wifi data from another ROM way back and it was causing conflicts. Thanks for the updates!
[Paid Software Announcement and Discussion] aznxcp4lyfez:
just updated and still doesn't work

i miss my delayed lock:crying:
[Paid Software Announcement and Discussion] j4velin:
please install the attached debug version and send me the log if the issue occurs again
[Paid Software Announcement and Discussion] olivierg13:
Doesn't work anymore on motox too with pattern.

I changed to pin and it's ok.

I think I will stay on pin so.
[Paid Software Announcement and Discussion] Roelander:
Wrong PIN

Hello

Had it two times today after spontaneous reboot.

Unlocked once with samsung account.

Unlocked once by deleting locksettings.db and locksettings.db-shm

in Aroma filemanager.

Both are working.

I made a tasker task that enables data after sending a sms with keyword to locked phone.

After that I can use Samsung account.

Can somewone make a aroma zip that deletes the two files ?

With that it only takes a little time to get started again.

Greetz.