yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] OrTiN:
Really nice app, after testing I have purchased it, please keep go on! One idea from my side. Can you add check for connected headphone (line in) please.
[Paid Software Announcement and Discussion] Konstigt:
Found another app that can disable BT on idle:

Bluetooth Auto Connect

https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
[Paid Software Announcement and Discussion] Jayman007:
Is fingerprint authentication working/supported yet.
[Paid Software Announcement and Discussion] Jayman007:
Looks like it's not yet working on my rooted galaxy s5 running stock 4.4.2
[Paid Software Announcement and Discussion] ndno:
So I've been using this on a Sprint Samsung S3 for a year and it works flawlessly. About 4 months ago I switched to an S5 and I thought it was working fine until I ran into issues trying to enter my pin. It would say bad password so I retried 2 more times. After 3 times of failures, a message pops up saying that the pin doesn't match that of the system due maybe something else changing it (??) and if I want to reset the system's code to the one set by DL. So I say yes, the screen goes blank and I'm able to wake it up without it asking me for my pin! Wtf. This happens every day or 2 and when it does, I can enter any random password and the same message would pop up and if I just say yes, it will just let me in! When this scenario happens, there's no security! Anyone who uses my phone can just enter any password 3 times and say yes to reset it and be able to unlock my phone. Attached is the message that pops up. I also attached my settings.

Anyway to fix this security hole? My phone is running MOAR custom ROM and I have supersu granting DL all the rights. I don't have any virus and malicious apps running according to ESET that I have installed.

NOTE: I never had fingerprint sensor enabled since day one.
[Paid Software Announcement and Discussion] j4velin:
Debug version is attached: Please install this one and upload the DelayedLock.log file from the root of your external memory if the issue occurs again
[Paid Software Announcement and Discussion] ndno:
Ok, here's the attached log in which I just forced an incorrect pin 3 times to get that reset message window to pop up, which I answered yes and it immediately unlocks the screen, without requiring me to ever put in my original correct pin. I will send one when this happens for a pin I correctly enter but it still won't accept.
[Paid Software Announcement and Discussion] ndno:
Ok, just ran into scenario in which the correct pin entered was denied. After 3 times, reset window popped up, I chose Ok and it unlocked without me having to enter the correct pin. Attached is the log.
[Paid Software Announcement and Discussion] j4velin:
Please check if this version works better. Make sure to enable the android device manager in case the app is unable to reset your PIN now
[Paid Software Announcement and Discussion] Konstigt:
I have tested the app now (ver 3.7.7) on my Nexus 5 with Android 5.0.1. What I had before on KitKat and was looking to have again was to always have the lockscreen enabled but when I'm connected to a trusted BT device or Wifi network I should only have to enter the PIN/pattern once.

This is also how it works when I instead use the new SmartLock feature of Lollipop.

Now what I get is that the lockscreen is completely disabled and I when I press the power button I get straight to the home screen.
[Paid Software Announcement and Discussion] ndno:
Thanks. That works a lot better in terms of removing the security loophole I described. I'm no longer able to just unlock the screen without entering a correct pin after the reset. I'll continue testing to see if sometimes it won't accept my correct pin.

Can you push this to the release version on Google Play?
[Paid Software Announcement and Discussion] ornus:
Black screen on lock in lollipop

Hello. I'm on lollipop (CM variant). When I click on the lock icon in notifications to lock the device screen goes blank and I can only see navigation buttons at the bottom and status bar at the top. Everything else is blank. Clicking on any navigation buttons has no effect. Turning screen on/off has no effect..

Holding power button does bring reboot menu, but that's the only menu I managed to get into. Rebooting device fixes everything until I try to lock it again.

Any word of advice on how to fix the issue?

There's plenty of ram. I'm on pin code to unlock the phone

Thank you.
[Paid Software Announcement and Discussion] JHimmelbauer:
Delayed Lock does'nt work anymore on Note 4 & Lollipop

I love this great App and use it since years, but Delayed Lock does'nt work anymore on Note 4 & Lollipop - the lockscreen is always enabled....
[Paid Software Announcement and Discussion] sniper:
Same here but on an S4 with 5.0.2
[Paid Software Announcement and Discussion] j4velin:
Yes, the 5.0 workaround only works on non-Samsung devices
[Paid Software Announcement and Discussion] sniper:
Even on non-Samsung roms?

Also, I just noticed that the app doesn't request root access unless I hit uninstall inside of it. Would that be part of the problem or is root not required for the 5.0 workaround?
[Paid Software Announcement and Discussion] j4velin:
Don't know. Just test if - if it works, it works.

No root required for the workaround
[Paid Software Announcement and Discussion] sahbin:
Unfortunately not working on note 4 TW LP
[Paid Software Announcement and Discussion] Brent212:
Flashed Fusion Lollipop 5.0.2 ROM on my galaxy s5 a couple days ago, and delayed lock is working great for me so far, using the pattern lock screen.
[Paid Software Announcement and Discussion] Hampa_D:
just got cm12s on my oneplus and cant get DL working again, tried pin, pattern but no go.

cant find this workaround does anyone care to share some light on it?
[Paid Software Announcement and Discussion] Funkyspider:
Same issue here. Doesn't work on Cyanogen OS12 on OnePlus One (stock un-rooted) :(

I'm glad it's not just me
[Paid Software Announcement and Discussion] Hampa_D:
I went back to cm11s because of this and issues with xposed
[Paid Software Announcement and Discussion] patrickfree:
delay time setting

I've been using the paid certain of delayed lock for a long time but there is one thing I want that it doesn't have - ability to change the delay time through a shortcut. Different situations I would like to have different times, mainly plugging/unplugging headphones. I use Tasker to completely disable the lock for this, but I would rather just moved the delay out to 60 min from its normal 10. That way if I leave it laying around with them plugged in it still gets locked. Can Delayed Lock's 'delay time' setting be accessed/changed from Tasker.. Or some plugin? Or even better can you put in customizable shortcuts to the delay time?

Thanks
[Paid Software Announcement and Discussion] gen10:
Please fix this for the oneplus one on lollipop! :(
[Paid Software Announcement and Discussion] j4velin:
Sorry, I don't know what the issue on the OPO is and I do neither have a such a device nor any device running CM12S. If it's the same bug as in the Samsung ROM, then there is nothing I can do about it
[Paid Software Announcement and Discussion] gen10:
It isn't the same bug as the Samsung device. I think its something with the new Google lockscreen. I turn on delayed lock but I don't get any delay. I have to enter in my password every time. But I guess if you can't fix it that's very unfortunate. :'(
[Paid Software Announcement and Discussion] blue_v4:
Nice work ?
[Paid Software Announcement and Discussion] awatrin:
Hi, I've been using Delayed Lock for a long time with Android 4, and it usually locked the device by swipe, before the time-out to ask the pin. Now I've installed it in Android 5.0.2, and while the time-out isn't reached, the screen isn't locked by swipe anymore. Is it possible to get the old behaviour again?

Thanks
[Paid Software Announcement and Discussion] j4velin:
Only on Android 5.1, a bug in 5.0 prevents this
[Paid Software Announcement and Discussion] micris12:
Same black screen that needs reboot

I'm on stock Lollipop 5.0.2, no root, Moto G 2nd Gen phone, using the pattern lock feature and I have the same problem every time I use the widget shortcuts (e.g. to toggle locking ) . Screen becomes black, only navigations icons at bottom and the top sliding menu can be seen. It needs a reboot to have the phone usable again - this is very annoying. However I paid for this idea and now I still can use it but without widgets - turn on/off delayed locking directly from application option. But I would be happy if above problem would be fixed. Thanks.
[Paid Software Announcement and Discussion] Tormiasz:
I've installed this application on my encrypted phone, after a restart pf my phone my password is not working and I can't get into my phone :( What can I do now?

EDIT: I had to flash the system again.
[Paid Software Announcement and Discussion] khaytsus:
Sorry, that's nonsense. System doesn't change generally using the device, unless you're modifying it intentionally. And Delayed Lock does not touch /system. Perhaps you meant you wiped data/factory reset?
[Paid Software Announcement and Discussion] Tormiasz:
Most likely it was caused by Cerberus. I've enabled lock with pin "1234" and it propably changed the password. But I've tried to use it aswell and din't worked.
[Paid Software Announcement and Discussion] Tanker Bob:
Icon on CM 12.1

I just upgraded to CM 12.1 (Android 5.1.1), and often have a # on the right side of the status bar. I have tested quite a bit tonight, and believe that I have it narrowed it down to DL. I had some trouble getting DL to work at first, but it seems OK now. Any idea what the # icon is and how to get rid of it for good? Or am I barking up the wrong tree?
[Paid Software Announcement and Discussion] Tanker Bob:
Disregard. The # in the status bar apparently announces that at least on of the apps in the task manager rotation has root access. That can include DL, but may be others. DL triggers it sometimes when I wake the phone. I can only get rid of it by loading another rooted app and then closing it in the task manager. It's kind of annoying, but certainly not DL's issue. DL seems to work for the most part on Android 5.1.1.
[Paid Software Announcement and Discussion] aleggsue:
I'm writing this from Verizon s4, eclipse ROM 4.4 nc5, and I'm having a weird problem. Delayed lock used to work just fine, then I upgraded to Lollipop, and downgraded back to NC5. Now delayed lock doesn't work. The lock works after being set in settings but doesn't disable at all. Any help?

Update: The app now works, I had some sort of confliction with the settings passcode and the passcode enforced be delayed lock. Weird glitch, but everything works now. A-okay
[Paid Software Announcement and Discussion] Jemmy Ducks:
Delayed Lock no longer displays the notifications on my Moto X 2013. Nor does it display the status bar icon.
[Paid Software Announcement and Discussion] Jemmy Ducks:
And so it seems I had but to post this for my icon and notifications to appear. Never mind.

---------- Post added at 02:49 AM ---------- Previous post was at 02:45 AM ----------

Well cancel that cancel. The thing has disappeared again. Happened just after I opened the app.
[Paid Software Announcement and Discussion] Jayman007:
I would be ever so grateful if you could get the fingerprint unlock working on galaxy s5 running 4.4.2.

I would even upgrade to 5 off that meant it working.

I love this app but I need to use fingerprint unlock and this app won't support it.
[Paid Software Announcement and Discussion] kurci2:
Nexus 7 2013 Android 5.1.1 rooted - DL not working

I own Nexus 7 2013 WiFi tablet. Today I have installed Android 5.1.1 and rooted it. After that I have encrypted my device and set an unlock password (also requested when starting the device). After that I downloaded Delayed Lock app, configured it to disable lock for one hour after last unlock and granted the app root permissions.

Now when I unlock my device I have a notification saying that lock is disabled for one hour, but if I turn screen on and off immediately after first unlock, my device is locked.

Am I doing something wrong?

I am also using the app on encrypted Samsung Galaxy S3 mini running Android 4.1.2 and everything works great.
[Paid Software Announcement and Discussion] Pteer Griffin:
Having some random issue where a message would say that No lock selected, Delayed Lock won't work. It ran 180 hours without any issues, then it would soft reboot and the notification would pop up. The only thing I recall was installing a theme a couple of weeks ago, but would that affect Delayed Lock? Running Euphoria 1.1 June 13 (5.1.1)
[Paid Software Announcement and Discussion] j4velin:
Which lock method have you selected in the app ("PIN/Password" or "other")?
[Paid Software Announcement and Discussion] Pteer Griffin:
Pin (8-digits). Previously, I had a 10-digit PIN.
[Paid Software Announcement and Discussion] j4velin:
Can you make sure you set the app as device administrator? Which other device admins do you have active? Any of those being able to change your PIN?
[Paid Software Announcement and Discussion] Pteer Griffin:
I think the only other one is Android Device Manager that's ticked as device admin. I do recall setting Delayed Lock as device admin. Am I supposed to disable ADM in order for Delayed Lock to work properly? There's also the trust agents settings which include the Smart Lock toggle. Disable that as well? Never used it.
[Paid Software Announcement and Discussion] j4velin:
No, you should be able to leave both these options enabled without issues. Can you identifiy any pattern when that error appears?
[Paid Software Announcement and Discussion] Pteer Griffin:
Ok, I wiped the phone, installed the latest Euphoria build from June 30th, and reinstalled DL, running 2 days straight, no issues. Before wiping, I used Catlog to check what was going on. It said the crashes came from Nova launcher 3.3. I guess Nova launcher 3.3 wasn't fully compatible with LP 5.1.x which was causing the random reboots? Anyways, running with the latest Nova, and DL, no reboots.
[Paid Software Announcement and Discussion] mangoman:
Anyone got bug where lock screen is not working after uninstalling this?

On cm12.1, i installed this then uninstalled it. Dont know if it is related but now the phone does not lock when the screen turns off.

I am using pattern, and the option not to lock when connected to wifi.
[Paid Software Announcement and Discussion] kurci2:
Nexus 7 2013 Android 5.1.1 rooted - DL not working

Hello!

I am still having issue I described in post #1099

I have just upgraded Nexus 7 2013 to Android 5.1.1 version LMY48G. I still have the same issue: I enable Delayed Lock after that I lock screen and unlock it. In status bar I get notification that device is unlocked till (for one hour as I have configured), but when I turn screen off and on device is locked.

I provide here CatLog for one this lock - unlock - lock - unlock cycle. I hope it will help.

I realy hope for same help.
[Paid Software Announcement and Discussion] j4velin:
Which settings do you use in the app? which lockscreen? any task killers? xposed modules? custom ROM? device encrypted?
[Paid Software Announcement and Discussion] kurci2:
I use only delay TIME option: one hour after last unlock. And in setting require manual unlock once. I use stock lockscreen, no modification and stock Nexus 7 2013 Wifi rom. I have rooted device and i use xposed framework, but I also tried on fresh installation but it was the same thing. Yes I have encryped device with PIN which I have to enter during boot. If I disable that ask password during boot option Delayed Lock works, but the thing is that this Encryption with PIN or Password is necessary. I have a rooted device and Delayed Lock has root access.

Can I provide anything else to help?

Edit: If it is for any help. The app Smart Unlock works on my device (but it lacks time delay unlock option, so...).
[Paid Software Announcement and Discussion] j4velin:
What lockscreen setting have you selected on the first page of the app? Try using the other one once
[Paid Software Announcement and Discussion] kurci2:
Nexus 7 2013 Android 5.1.1 rooted - DL not working - SOLVED

OK. Now I realy feel uncomfortable. I have always selected PIN or Password option. Now I have selected Other (experimental) and it WORKS!

So the solution (if there is anyone else): Select lockscreen option: OTHER (EXPERIMENTAL).

Thank you for your help!
[Paid Software Announcement and Discussion] Lexee:
"Lock Now" doesn't turn off screen after a "screen off" cycle

Firstly, thank you so much for the app! You totally made my day! :)

I want to report one tiny little bug though.

"Lock Now" option in the notification bar only enables lock but fails to turn off screen if the phone has experienced "screen off" since the last unlock. If the phone has not experienced "screen off" since the last unlock, the option properly enables lock and turns off screen as expected.

So just to give a couple of use cases:

===1===

lock screen enabled, screen is off

press power, unlock phone

lock screen is disabled

tap "lock now" from notification bar => lock screen gets enabled, screen turns off. All good.

===2===

lock screen enabled, screen is off

press power, unlock phone

lock screen is disabled

press power, screen turns off

press power, screen turns on, no lock screen

tap "lock now" from notification bar => lock screen gets enabled, but screen remains on now!

Scenario 2 is repeated if the screen gets turned off with a timeout rather than the power button.

This is happening on my T-Mobile Galaxy S6 Edge, running nearly stock 5.1.1. with a kernel by [MENTION=1124755]Aou[/MENTION] (http://xdaforums.com/showthread.php?p=61532969) (kernel is meant to be almost stock but is necessary for root)

I've also attached two short logcat excerpts that show what happens immediately after "lock now" is touched, in the two scenarios. Although I'm afraid not much can be inferred from them. The one where it doesn't work there is simply no sign of PowerManagerService, for some reason. But otherwise they start off pretty much the same.

Thanks for your efforts!

Cheers!
[Paid Software Announcement and Discussion] sniper:
The app is working pretty well on 5.1.1 for me, but sometimes with a pin it'll say it couldn't unlock and then after the next unlock that my pin isn't entered into the app so I have to reenter it. Also, sometimes a different error pops up saying "an active device administrator on your devi...", but since it gets cut off I'm not sure what the error is with a device administrator. Any advice?

Is the "other" option supposed to have a simple swipe lockscreen when unlocked? It just turns on the device with no lockscreen for me.

Edit: apparently the stupid cm account manager keeps trying to add itself as a device administrator, which seems to have been causing one of the errors. I froze it and hopefully that piece of crap will stop causing problems.

Nope, even with delayed lock as the only device administrator I've randomly gotten that admin error again followed by it saying not being able to unlock and then no lock selected.
[Paid Software Announcement and Discussion] dtr145r:
I too am having problems with delayed lock on cm 12.1 it keeps putting up a notification saying lock screen not selected and my lockscreen usually gets disabled...
[Paid Software Announcement and Discussion] j4velin:
The "other" option also disables the swipe lockscreen

Please install the attached debug version and upload the "DelayedLock.log" file if those issues occur again
[Paid Software Announcement and Discussion] sniper:
Here's the log: http://pastebin.com/agTer6eP

It happened, then I disabled the app, uninstalled, reinstalled, set it up, and then it happened again.
[Paid Software Announcement and Discussion] j4velin:
Have you setup a VPN or anything else that requires a lockscreen to be enabled? Custom certificates? Exchange profile?
[Paid Software Announcement and Discussion] Lexee:
Thanks very much - my issue is fixed! Tapping "Lock Now" from notification bar now activates lock and turns off screen even after screen-off cycle!

EDIT: Actually sorry I pulled the trigger too quickly -- issue isn't fixed when I have TIME condition set to x minutes "after screen off" rather than "after last unlock", which is what I prefer and would like to use. But as it turns out, when the TIME condition is set to x minutes "after last unlock", then there is no issue and "lock now" from notification bar works properly.

I've attached delayed-lock.log
[Paid Software Announcement and Discussion] sniper:
Nope, none of the above. It seems random most of the time, but if I turn the screen off and then try to unlock less than maybe 5 seconds or so later it's more likely to happen. My lock is set to lock immediately though.
[Paid Software Announcement and Discussion] j4velin:
Sorry, I can't reproduce the issue and there is no mention of clicking on "lock now" in the log file
[Paid Software Announcement and Discussion] dtr145r:
Lock deletes itself...
[Paid Software Announcement and Discussion] DanderMan:
Unfortunately, Delayed Lock isn't working after the update on August 6, 2015 (I'm using CM 12.1) anymore. Before the update everything was working like a charm. Now the PIN lock isn't diabled after connecting to my WLAN - I've to enter the PIN everytime.

Any chance to get the apk of the last working version?
[Paid Software Announcement and Discussion] j4velin:
which method have you selected in the app? deactivate pin or hide lockscreen?
[Paid Software Announcement and Discussion] DanderMan:
Deactivate pin! Hide lockscreen is working
[Paid Software Announcement and Discussion] DanderMan:
Any news?
[Paid Software Announcement and Discussion] j4velin:
Not sure what CM 12.1 is based on, but deactivate pin won't work on AOSP 5.0 due to a bug in the system, which was only fixed in 5.1 - I guess that bug is still there in your CM version?
[Paid Software Announcement and Discussion] DanderMan:
CM12.1 is based on 5.1.1 and Delayed Lock was working until the current version.

Please, can you tell me how I can get the second last version - unforntunately I didn't backup this version?
[Paid Software Announcement and Discussion] j4velin:
Have you tried "unlocking" the device by just pressing the enter button on the lockscreen, once Delayed Lock should have disabled the lockscreen?
[Paid Software Announcement and Discussion] DanderMan:
Sorry, but I don't know what you exactly mean.

Normal behavior: WLan --> need to enter PIN once --> switch off display --> from now on I only have to swipe

Current behavior: WLan --> enter PIN --> switch off display --> need to enter PIN again (after a swipe) --> switch off display --> need to enter PIN again (after a swipe) ...

BTW: The notification area shows: Tab to enable lock / Lock disabled
[Paid Software Announcement and Discussion] j4velin:
You see the lockscreen -> you press enter -> you tell me what happens
[Paid Software Announcement and Discussion] DanderMan:
??? Where schould I press Enter

After switching on the Diplay I get following screen --> screenshot1

After swiping I got following screen --> screenshot 2 (Pin)
[Paid Software Announcement and Discussion] j4velin:
I mean that "check" in the bottom right corner of screenshot2
[Paid Software Announcement and Discussion] j4velin:
I mean that "check" button in the bottom right corner of screenshot2, below the number "9", right of the "0"
[Paid Software Announcement and Discussion] DanderMan:
Ok --> Wrong PIN

Edit: The "Time" isn't working too. I've entered 10 minutes but immediately after switching off and on the screen, the phone is locked (PIN-lockscreen).

Don't know if it's important, but I've a Nexus 5
[Paid Software Announcement and Discussion] DanderMan:
More details:

Same (latest) CM12.1 nightly and latest Delayed Lock on Nexus10 --> DL is working.

After a new installation on Nexus10 I have to enter the PIN after activating "Disable PIN/password lock". Nexus 5 isn't asking (unlike on the second last version - there DL asked for the PIN)