yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] daniello8:
Actually I deblaoted everything that has "knox" in the name. Only thing that pops up in TiBu when I search knox is "RCPComponents1.0".

And yes .. I have many administrators active:

Android device manager (as recommended by your app description), Cerberus, E-Mail, Lockscreen (don't really use it), Llama, Enable Screen Lock (this one is from buttonsaviour .. never used it), delayedlock, smart app lock, secure settings, screebl, tasker

Which one of those is common to all samsung reports you have received?
[Paid Software Announcement and Discussion] daniello8:
samsung lockup

I would really like to help with this samsung problem (out of own interest of course). Just had this lockup again and this time I connected to adb an piped a logcat to file while I entered the PIN (that is rejected) a few times. Sadly not the moment the lockup happend but maybe there is something "to see".

Zip file attached.
[Paid Software Announcement and Discussion] tggl:
Verizon Note 4

I installed and set this app up on my Verizon Note 4 today, and it works perfectly for my purposes - to keep the phone unlocked while linked by bluetooth to my Gear 2 Neo, and locking the phone with a defined 4 digit pin after the Gear 2 Neo disconnects or is out of range for 30 seconds. I have read with concern, however, the references to some Samsung phones randomly changing the PIN or otherwise locking out an owner using this app after working fine initially. The convenience of not having to enter an unlock code is not worth the risk of being locked out of my phone entirely. Should I just uninstall this until this issue is resolved?

Thanks,

Tom
[Paid Software Announcement and Discussion] j4velin:
Not sure if that's related, but in the log there is a crash of the keyguard (aka lockscreen) related to a xposed module:

E/KeyguardUpdateMonitor( 3395): Object tried to add another callback

E/KeyguardUpdateMonitor( 3395): java.lang.Exception: Called by

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardUpdateMonitor.registerCallback(KeyguardUpdateMonitor.java:1070)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardAbsKeyInputView.onResume(KeyguardAbsKeyInputView.java:425)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardHostView.onScreenTurnedOn(KeyguardHostView.java:1711)

E/KeyguardUpdateMonitor( 3395):	at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)

E/KeyguardUpdateMonitor( 3395):	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardHostView.onScreenTurnedOn(Native Method)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardViewManager.onScreenTurnedOn(KeyguardViewManager.java:570)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardViewMediator.handleNotifyScreenOn(KeyguardViewMediator.java:2142)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardViewMediator.access$2800(KeyguardViewMediator.java:167)

E/KeyguardUpdateMonitor( 3395):	at com.android.keyguard.KeyguardViewMediator$6.handleMessage(KeyguardViewMediator.java:1734)

E/KeyguardUpdateMonitor( 3395):	at android.os.Handler.dispatchMessage(Handler.java:102)

E/KeyguardUpdateMonitor( 3395):	at android.os.Looper.loop(Looper.java:157)

E/KeyguardUpdateMonitor( 3395):	at android.app.ActivityThread.main(ActivityThread.java:5356)

E/KeyguardUpdateMonitor( 3395):	at java.lang.reflect.Method.invokeNative(Native Method)

E/KeyguardUpdateMonitor( 3395):	at java.lang.reflect.Method.invoke(Method.java:515)

E/KeyguardUpdateMonitor( 3395):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)

E/KeyguardUpdateMonitor( 3395):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)

E/KeyguardUpdateMonitor( 3395):	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)

E/KeyguardUpdateMonitor( 3395):	at dalvik.system.NativeStart.main(Native Method)
[Paid Software Announcement and Discussion] daniello8:
Regrettably it doesn't give a hint about which module might be the culprit :(

I am currently looking for a logcat app that runs in the background and records to file with a file size limit (e.g. only the last 20 megs).. haven't found one yet .. but if I do I will leave it on.
[Paid Software Announcement and Discussion] daniello8:
Samsung lockup

I must now admit that I never took care of the last checkbox on your startup screen .. the one before the license check. I didn't exactly understand what to do and the option led me to a settings page that didn't help me understand. Now I set the wait time to zero and switch on the immediate activation of the lockscreen when the screen is turned off. As a replacement I set the timout in your app .. after screen off to two minutes .. I guess this is the way you meant it to be.

Maybe that was the conflict. With both settings in the samsung menu and no timout in the app everything actually worked well - except for the lockup that occured sometimes.

I'll have to see how it goes now.

Edit: Nope .. didn't help .. just had another one of those lockups :.-(
[Paid Software Announcement and Discussion] daniello8:
Some thoughts about the app:

- In Bluetooth section I can add all pairings. Why not make it possible to add from the known wifi list (maybe not all but select from that) .. instead of having to connect to the wifi to add it?

- A delete confirmation would be good .. swiping away entries is quite easy.

- A hint would be good that BT has to be restarted for the app to work. I wondered why my phone didn't stay unlocked when I added the BT in the car.

- I would appreciate the first unlock when connected to a known Wifi to be an option. At work I would want this initial unlock .. at home I wouldn't

Maybe you like some of those :)
[Paid Software Announcement and Discussion] daniello8:
Managed to make a verbose logcat of my samsung lockup. Will email it to the support address mentioned in the app description.
[Paid Software Announcement and Discussion] Ingenium13:
If you have Tasker you can pretty easily do 3 and 4 in your list. I manage the unlocks completely with Tasker simply because sometimes I want an initial unlock and sometimes I don't.

It also gives you flexibility over the charging lock control. I want the lock enabled when it's charging, even if on known wifi (like work) because it means I probably walked away from my phone. Whereas in my car I want it to be unlocked when connected to bluetooth regardless of whether it's charging or not.
[Paid Software Announcement and Discussion] daniello8:
Sounds very interesting .. I would dig into those suggestions when I get DL to run stable on my samsung .. still fighting with lockups :(
[Paid Software Announcement and Discussion] julz:
Used to work on my Oneplus One but since changing to a Galaxy Note 4 it doesn't work. All boxes are ticked but phone still asks for PIN even though my Android Wear device is in range. Can I get a refund?
[Paid Software Announcement and Discussion] j4velin:
Have you tried the "Disable while connected to any Android Wear device" option? Seems like the Note doesn't notify apps about connects/disconnects of Bluetooth Low Energy devices
[Paid Software Announcement and Discussion] julz:
yes, tried clearing the settings and setting it up again without any luck
[Paid Software Announcement and Discussion] j4velin:
Can you select "no lockscreen" in the Android settings?

Also, debug version is attached which should create a logfile after some time, please send me this file then
[Paid Software Announcement and Discussion] julz:
I haven't installed the debug version yet but it seems to be partially working. As long as my watch doesn't go out of range and lose connection it will unlock without the need for a PIN. As soon as it loses connection I have to put a PIN in again.
[Paid Software Announcement and Discussion] j4velin:
isn't that "fully working" then?
[Paid Software Announcement and Discussion] julz:
From memory I thought the phone should unlock without a pin once the watch comes back in range? This is how it used to behave with my Smart Watch 2
[Paid Software Announcement and Discussion] j4velin:
There is an option in the app to require at least one manual unlock, which is set by default
[Paid Software Announcement and Discussion] julz:
Ok thanks let me try this with the option unticked. From memory I didn't have to do this with my old Smart watch 2
[Paid Software Announcement and Discussion] Konstigt:
Hello

Couldn't find any info in Play Store or FAQ regarding Lollipop. But the app has stopped working since I upgraded my Nexus 5 yesterday. Any information on this?
[Paid Software Announcement and Discussion] j4velin:
Please guys, stop asking me about compatibility with a major Android update, which I received less then 12 hours ago. This is not my full-time job, I have to sleep and it generally takes time to fix things
[Paid Software Announcement and Discussion] julz:
No need to use this app with lollipop as it has this feature built in.
[Paid Software Announcement and Discussion] Ingenium13:
It has some of the features built in. But this app allows more fine grained control than is present in Lollipop, especially with Tasker.
[Paid Software Announcement and Discussion] daniello8:
Which fine grained control do you mean? The plugin only has very few options.

---------- Post added at 08:57 AM ---------- Previous post was at 08:54 AM ----------

Again I vote for an option to switch of the initial Pin entry just for selected APs. At home I have two APs. Because the switching between APs with the Same SSID doesn't work well I have to use different SSID .. when my phone switches to the other I have to enter a PIN.

Regardless of that .. I think even if switching between same SSID would work well a switch would still trigger the PIN. So maybe this would also be a case to consider. At offices you do change Access Points even though you remain in the same building.
[Paid Software Announcement and Discussion] julz:
Sure bit the lollipop features are probably enough for most people and work out of the box for those lucky enough to have lollipop
[Paid Software Announcement and Discussion] Ingenium13:
The feature that you're asking for is one of the things possible with Tasker, and is actually pretty easy to do. The plugin itself doesn't need any more options, Tasker takes care of the conditions, all the plugin has to do is tell Delayed Lock to enable or disable the PIN and you can replicate all the built in plugins.

I don't use the built in wifi or bluetooth plugins at all, I control it completely from Tasker. Unfortunately it's an all or nothing situation, because Delayed Lock doesn't have a way to tell other apps or plugins what its current state is. In other words, there's no way to see if the PIN is enabled or disabled and why. It's a one way street that makes mixing the built in plugins and the Tasker plugin almost impossible. So for power users you're better off just having Tasker manage all the states.

If you go that route, you can disable the PIN only on certain APs (including roaming with different SSIDs), or make it so the PIN has to be entered once in certain situations (like arriving at work) but not others (connected to car bluetooth). As another example, Delayed Lock currently lets you disable the PIN when plugged in, but I wanted the opposite. So now when my phone is charging the PIN is always enabled, unless I'm connected to my car's bluetooth. You can make as many exceptions and special cases as you like.

It's impossible for the app to have built in the exact functionality that everyone wants. There's too many possibilities, and some of them even conflict with each other.
[Paid Software Announcement and Discussion] daniello8:
I have tasker but I haven't really used it .. I usually stick with Llama which suits most of my purposes. I would like to understand how tasker can just activate the Pin once when connected and how you roam successfully between access points. Maybe you can shed some light with a screenshot or two.

BTW .. is DL turned on of off when you use tasker? I wonder if the program itself needs to be active when you use the plugin.

I understand that it's impossible to please everyone. My intention is only to make suggestions that the dev can evaluate and implement or not. Of course a feedback is appreciated but I understand if people are too busy.
[Paid Software Announcement and Discussion] Ingenium13:
Delayed Lock needs to be enabled for it to work. All the Tasker plugin does is pass along instructions to DL.

For multiple APs, you create a Tasker profile and select the wifi connected state. Then enter the SSIDs you want to disable the PIN. You can add more than 1 SSID, they're separated by a slash (/). Make the enter task use the Delayed Lock plugin to disable the PIN. Then make the Exit task re-enable it.

On the Exit Task, you can add a 1-2 second wait first and then check to see if wifi is connected to one of your SSIDs (via the %WIFII variable I believe). That way if there is a delay switching SSIDs it won't trigger the PIN to re-engage.

If you want to start mixing in bluetooth or doing more complex things you need to use Tasker variables to keep track of whether the PIN should be on or off (ie if there's a conflict, such as disconnecting from wifi but being connected to car bluetooth, you don't want the PIN to engage). I basically use 2 profiles, one to enable the PIN via DL and another to disable it. I control which one is active by using Tasker variables and other profiles. It can definitely get a bit confusing.

I've never used Llama, but I think it uses the same framework as Tasker, so the plugin will probably work there too. So if you're more comfortable using Llama give it a try.
[Paid Software Announcement and Discussion] daniello8:
Thanks for those instructions .. the two second wait is a good idea. Indeed Llama can use the tasker plugin but I haven't gone as far as you in optimizing what it should do so I'm not sure if it's that tweakable. What I miss in your instructions is how you make sure you just have to enter the pin the pin once on certain networks and not on others.

Right now I am still in the process of waiting for a "Samsung Lockup" .. I changed to Stock Kernel yesterday and it hasen't misbehaved yet .. but it usually happens soon after you write stuff like I just did ;)

Once it's stable it will be well worth to optimize.
[Paid Software Announcement and Discussion] Ingenium13:
Ahh ok. You need to use 2 profiles (I have them check to see if the variable $DISABLE_PIN is 0 or 1) that each just have an enter task and no exist task. The Disable PIN profile checks if $DISABLE_PIN=1 and also checks the device unlocked event. At the end of that task it disables itself (ie, disable the Disable PIN profile). That way it only runs once, which is after device has already been unlocked, but not after every screen unlock. You'll want to name this entry task because you'll use it separately later.

The Enable PIN profile uses the delayed lock plugin to turn the PIN on, and then enables the Disable PIN profile. It runs only if $DISABLE_PIN=0.

I then use other profiles to set $DISABLE_PIN to 0 or 1. If I don't want to require a PIN to be entered first, set $DISABLE_PIN to 1 and manually run the Disable PIN task you named above. This will disable the PIN immediately.

I hope that makes sense?
[Paid Software Announcement and Discussion] daniello8:
Makes sense .. indeed. Actually feels a bit strange that you have to take care of all this yourself even though you have a dedicated app .. but it's definitely great that there is a tasker interface.

Will deal with it more closely soon. THANKS FOR TAKING THE TIME!
[Paid Software Announcement and Discussion] Konstigt:
Partly, but not the same way.

I want to use the lock screen immediately but I don't want to enter password until after 3 minutes.

And I like how it can disable BT if not used.

---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------

Suggestion: Update post #1 and the information in the Play Store and you will probably avoid lots of questions.

And there has been L previews out for ~ 6 months so it isn't unreasonable to think that the app should have been updated already (I have lots of others that were ready from the get-go of the final release).

Edit: Btw, good luck coding so that the app will remain good even on L :)

Edit2: Lollipop also lacks option to disable lock screen security when on certain wifi networks.
[Paid Software Announcement and Discussion] owilsky:
I bought Delayed Lock via Amazon app store. When I click on License Verification nothing happenes. Any hints?
[Paid Software Announcement and Discussion] Wrapp:
Really? Dind't find it yet.

What I would need is:

-Disable lockscreen when connected to known WIFI

-Disable lockscreen when connected to known CellID

-Switch off WIFI if not connected to known WIFI for > x sec.

Can you tell me where to find it in stock L?

Anyway, I really appreciate a L compatible DL version.

Thanks a lot
[Paid Software Announcement and Discussion] UdiFlpb:
i bought it everything is checked i am rooted using htc one m7 verizon cm11 latest milestone and i dont know what i am doing wrong sometimes it works and sometimes it doesnt right now it doesnt work.

any hints ?
[Paid Software Announcement and Discussion] daniello8:
I think I found a good way to control DL in Llama .. still have to test though:

- Rule 1 "Pin off at home": If connected to known wifi then disable lockscreen.

- Rule 2: "Pin off at work": If connected to known wifi and user present (phone is being unlocked or is already unlocked) then disable lockscreen.

- Rule 3: "Pin on": If disconnected from any wifi network for longer than 30 seconds enable lockscreen.

If I am not mistaken this should solve all scenarios .. even without any variables.

Bluetooth I would add to the "at home" profile .. with an OR connection and I'd also have to explicitly add it to Rule three (also OR) but this would only be for one device in my case.

Note to j4velin: With the stock kernel DL seems to work rock stable on my Samsung phone .. will continue to monitor it.
[Paid Software Announcement and Discussion] j4velin:
Well, DL worked fine on the preview but doesn't work at all on the final version. So having the preview wasn't of much help :D

I'm aware of this issue and try to resolve it, but the Amazon IAP API reaaaaally sucks. If Amazon would provide a way to refund purchases, I'd refund all users and ask them to use the Play Store version instead...

That's impossible to answer as there are a million reasons, especially on a custom ROM. Some more information about your configuration (type of lockscreen, what exactly doesn't work, what other device admins are active, ....) would be helpful

When it comes to Samsung stuff, it's basically just hit or miss in my experience. It's like every Samsung ROM is different on each phone and each provider or something
[Paid Software Announcement and Discussion] daniello8:
I wouldn't be amazed if all the reported Samsung bugs are Custom Rom related. I figure that the custom kernel that comes with my rom is based on the Samsung's latest code release which is not the most up-to-date. With the new stock kernel I use now the phone behaves much better alltogether. So next time you get a Samsung report you may look out for this ;) I at least am happy the way it is now .. if it lasts.
[Paid Software Announcement and Discussion] hvihavai:
http://www.theverge.com/2014/11/24/7275085/android-5-0-trusted-places-any-android-phone-delayed-lock

:)
[Paid Software Announcement and Discussion] Ingenium13:
Unless I'm missing something, this app is still needed on Lollipop. Using trusted places or trusted devices just disables the lockscreen rather than changing it to swipe to unlock.
[Paid Software Announcement and Discussion] Konstigt:
Wifi based lockscreen-security-disable is part of Smart Unlock (yet?) but location based works almost just as good.

Is it possible to keep the feature of disabling bluetooth after a certain idle time?
[Paid Software Announcement and Discussion] samsungs3android:
how to uninstall Delayed Lock on s3?

Hi, this is a great app and it brings certain features that are not available on a regular software version of Jelly bean and other os version for Android. But I have problems uninstalling it and I already deactivated admin settings. I currently still have a 1 day trial left. Do I need to wait for the trial version to end to uninstall it completely? I'm freeing up space on my S3's memory capacity 'cause its running too slow.

*My phone's not rooted btw, so is there any workaround or force uninstall tips out there? Please, guys help. Thanks in advance if ever. :)
[Paid Software Announcement and Discussion] daniello8:
DelayedLock is telling me that I don't have root. I cannot find a way to enforce a new SU request and the app doesn't appear in the SuperSU App list :(

No root message

Don't know how to proceed with this.

Anyone?
[Paid Software Announcement and Discussion] j4velin:
Well, do you get any error message or what prevents you from uninstalling it like any other app?

Do you have any setting in SuperSU that might prevent the su request, like "enforce superuser permission" or something like that? Do other root apps work?
[Paid Software Announcement and Discussion] daniello8:
Yes .. everything else works brilliantly. I have about 20 apps in the list but not Delayed Lock.

edit: BTW .. my phone is not encrypted .. so I guess it shouldn't even require root.
[Paid Software Announcement and Discussion] j4velin:
It does if you have another device admin active, which requires a PIN/password
[Paid Software Announcement and Discussion] daniello8:
Ok .. any idea how I can force DL to request root?
[Paid Software Announcement and Discussion] daniello8:
Follow-up: The reason for the SU message was the Exchange-Gmail account I had set up. This worked well together with DL on my Galaxy S4. Chances are that the order in which you set up things is relevant. Regardless of that if SU is required when another app requires a PIN-Lock .. I don't understand why there is no SU prompt. I'll gladly test any version you throw at me.
[Paid Software Announcement and Discussion] j4velin:
are you sure about that? Android does not offer any way to prevent an uninstallation and the app doesn't change anything at all after the 7-day trial except for showing a popup dialog now and then
[Paid Software Announcement and Discussion] samsungs3android:
I don't know sir? Maybe some glitch? But that was my experience though. . .
[Paid Software Announcement and Discussion] j4velin:
Did you get any error message or something?
[Paid Software Announcement and Discussion] The_Drizzle:
I have a rooted S4. I came here looking to see how i can get the program to request root from SU as well. Right now the app is not doing anything.
[Paid Software Announcement and Discussion] daniello8:
What I can say is that after I used Omega Rom with stock kernel (which is not default) Delayed Lock worked very well on my S4.

On the S5 the culprit is that the security scheme for PIN Lock has changed. In situations where SU is required Delayed Lock expects a password.key file in /data/system and if it's not there it will not demand SU rights. This is e.g. the case when another installed administrator has a PIN policy in place. No password.key file to be found on S5 - at least not on mine :(

BTW this ist not my expertise but j4velin's. My thanks go to him for looking into this - even though there seems to be no fix.
[Paid Software Announcement and Discussion] Konstigt:
Will the function to disable BT after inactivity still work with LP if it gets a little love?

And if DL won't be what it used to be please break out that feature to a separate app :)

We are many people in my household that use the same BT devices (speaker, headphones, car, amplifier etc) and they way that BT often works, how it automatically reconnects to the last thing it was paired to, makes this annoying.

(For example, I start my BT speaker but my wife automatically connects to it because she used it last time)