yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] DamienDeDun:
WIFI Disconnect after a few seconds

Hello all,

I'm having problems with DSLR controller and my Camera (Canon 600D)

When I connect to the camera using WiFi (TP Link 3040) I hear the camera switch to Liveview and everyting is working fine for a few seconds (I see the DSLR Controller app on my tablet as well as the liveview images). Then I hear the camera switch back and I get disconnected from DSLR Controller.

If I connect the camera directely to the Tablet using a USB cable it's working perfectly fine.

I removed and installed DSLR Controller agin on my tablet but it did not fix anything. The first time I tried it I did not run into any problem. What could be wrong ?

***EDIT***

I've changed the USB cable that connect the TP Link to the camera. Using a Canon and Sony cable everything works just fine. It seems like the problem was comming from the noname cable.
[Paid Software Announcement and Discussion] sansnil:
Uh...what the heck does this have to do with Delayed Lock?
[Paid Software Announcement and Discussion] aznxcp4lyfez:
Attached is the log
[Paid Software Announcement and Discussion] downldr:
Installed trial on Samsung Galaxy S3 after installing (stock) Kit-Kat update. Admin permission and setting the pin will not stick. After granting admin permission, setting the pin, then locking/unlocking the attached error message is shown and the Admin and pin/password checkboxes are not checked. Have tried rebooting. Any suggestions?
[Paid Software Announcement and Discussion] j4velin:
Do you have any other device administrators enabled?
[Paid Software Announcement and Discussion] downldr:
Not to my knowledge. How does one check this?

---------- Post added at 10:24 PM ---------- Previous post was at 09:32 PM ----------

Found it. Only device administrator is Android Device Manager which was "Strongly recommended" to be enabled by the app.
[Paid Software Announcement and Discussion] downldr:
Update: could not change pineven with app dis as bled as administrator. Uninstalled app, changed pin, rebooted, reinstalled, and everything is happy. Not sure where the breakdown took place but it is working now.
[Paid Software Announcement and Discussion] milden:
is it required to show this messagebox with superuser notification after every unlock?

this is only since one of the last updates
[Paid Software Announcement and Discussion] Ingenium13:
If you go into the superuser app you can tell it not to display notifications for Delayed Lock.
[Paid Software Announcement and Discussion] milden:
thanks i always thought i can disable this only for all apps
[Paid Software Announcement and Discussion] dshanks:
Works ... Sometimes. Extremely flaky behavior.

I'm using the app on an non-rooted Verizon Samsung Galaxy S4. Installed late last week and am trying to decide whether to pay for this decidedly flaky app.

I have three lock delays set up: a location (my home), several WiFi SSIDs (my office) and the Bluetooth in my car.

At home, the location delay seems to work although I usually have to unlock several times before the unlock "sticks."

When I leave my home in my car with my Bluetooth off, sometime the app continues to delay the lock and the notification continues to say that the phone is unlocked due to location (even several miles from my home). I have also seen instances when the phone is paired and connected to the Bluetooth yet no notification shows and the phone repeatedly locks itself. But sometimes the app does work and reports that the delay is due to being connected to Bluetooth.

Right now, I am sitting in my office. The phone is connected to my office WiFi network but no delayed lock notification shows and the phone keeps locking itself. Yesterday, however, the delay worked while I was at the office and connected to the office WiFi network.

In short, sometimes the app works and sometimes it doesn't. Sometimes it fails to delay the lock when it should be delayed and sometimes it delays the lock when it should not. This last scenario is the scariest because it potentially exposes a lost phone to use by anyone who finds it.
[Paid Software Announcement and Discussion] j4velin:
The location plugin has some issues due to a bug in Android 4.4.2 which doesn't restart the location service if it's killed by the system. there isn't much I can do about that except from waiting this issue to be fixed in the next Android version.

The bluetooth and wifi settings however work very reliable on all my testing devices. Please install the attached debug version and send me the logfile if you think there's a bug in the app
[Paid Software Announcement and Discussion] dshanks:
Thanks for the quick response! :)

I've installed the debug version. The phone did not notify a delayed lock after installing, but when I reset the phone it notified that it was delaying the lock due to WiFi. Several questions:

Is it expected that the phone must be reset after installing Delayed Lock?

Because I had to reset the phone, do you want to see the log file? If yes, where do I find the log file?

I originally turned on the location plugin because the WiFi plugin was not delaying locks at my home. Shall I continue to use the location plugin and send you the log file if I see buggy behavior, or shall I switch to using the WiFi plugin at home (and send you the log file if I see buggy behavior)?

For what it's worth, my phone is running the stock Version version 4.3 (i545VRUEMK2), not 4.4.2.

Also, failure to restart the location plugin shouldn't prevent the WiFi plugin from delaying locks, should it? As I've mentioned, that's one of the buggy behaviors I'm seeing.

Thanks for your help. This looks like it could be a terrific tool if I could only get it to behave properly. ;)
[Paid Software Announcement and Discussion] j4velin:
I hope by "reset" you mean "reboot". WiFi, Bluetooth and location only get active when they detect a change in their status, when connecting to a wifi network for example. so after installing Delayed Lock, you might need to disconnect & reconnect if you want the wifi to kick in

the logfile is in /sdcard/

if you have wifi at home, i wouldn't use the location plugin (wifi is way more reliable)
[Paid Software Announcement and Discussion] dshanks:
Thanks again. Yeah, to a bare metal embedded programmer "reset" means "toggle the processor/system reset line." I should have said "reboot." ;)

I'll let you know what I find.
[Paid Software Announcement and Discussion] dshanks:
When I looked at my phone after typing the previous message I noticed it was locked again. As far as I'm aware, I have not been disconnected from my office WiFi since the lock delay was working a couple of hours ago. Even if I was disconnected at some point, I'm connected now and am having to repeatedly unlock.

The log file is attached (in a zip file).

Edit: It's possible that, while moving around the office I disconnected from one SSID and connected to another. Nonetheless, I'm currently connected to an SSID that is in my list of Delayed Lock networks and I'm still having to PIN unlock every time the phone locks itself.
[Paid Software Announcement and Discussion] j4velin:
according to the log, your wifi disconnected at May 28, 2014 3:40:20 PM, resulting in the lock being enabled at May 28, 2014 3:40:51 PM. In the meantime, you connected again to a wifi network at May 28, 2014 3:40:28 PM but that didn't stop enabling the lock which can happen for two reasons: 1) the ssid of the connected network is not in the wifi settings or 2) a SQLiteException was thrown when trying to lookup that ssid in the database.

Either way, please try the attached version which will do some additional logging in case of the exception being thrown
[Paid Software Announcement and Discussion] dshanks:
I'm quite sure any SSIDs I connect to while at work are in the delayed lock list. Is it possible there's a logic hole when WiFi re-connects before the disconnect-lock timer expires? I imagine a sequence something like this:

3:40:20 WiFi disconnects. A 30 second timer starts. Lock will occur when the timer expires.

3:40:28 WiFi re-connects.

3:40:50 The 30 second timer expires. Locking is re-enabled (at :51).
​

Locking would not be delayed again until some subsequent WiFi or Bluetooth connect event occurs. If that's what's happening, the problem could be resolved by insuring that the timer is canceled whenever the phone connects to a WiFi SSID in the network list.

I'll install the new debug version and do some experiments to see if I can confirm or refute my hypothesis.
[Paid Software Announcement and Discussion] j4velin:
that should not happen, the app disables the "enable timer" if you reconnect to a known wifi network. however, the missing entry in the log suggests that the newly connected network was either unknown to the app or it crashed while looking it up in the database
[Paid Software Announcement and Discussion] dshanks:
OK. I haven't seen yesterday's scenario since installing the latest debug version, but I can state with 100% certainty that the phone could not have been connected to a network unknown to the app at the time the problem occurred.

Here's another oddity. At 2:58 I looked at the notifications panel and saw "Disabled by Bluetooth" with a time stamp of 2:21 PM. But it is impossible for the phone to have been connected to my Bluetooth device at either 2:21 PM or at 2:58 PM. The only Bluetooth device the phone is paired with is powered by my car. That device is known to Delayed Lock. But my car has been turned off (which removes power from the Bluetooth device) and well out of range from my phone since approximately 1:30 PM. At 2:58 PM I would have expected the notifications panel to say "Disabled by WiFi." At that time the phone was connected to a WiFi network known to Delayed Lock.

Log file is attached.
[Paid Software Announcement and Discussion] j4velin:
Thanks, I might have found the issue. Could you test the attached version? Thanks
[Paid Software Announcement and Discussion] dshanks:
Installed and phone re-booted. I'll let you know if I see any more anomalies.
[Paid Software Announcement and Discussion] dshanks:
So here's another apparent anomaly. ;)

I have the External Power check box checked. I currently have my phone connected to my computer and the battery indicator shows the battery is charging. That means the phone is on external power, right? But the lock is still active.

With the check box checked and the phone connected to external power, shouldn't the lock be inhibited?

Log file attached.
[Paid Software Announcement and Discussion] j4velin:
The app is only notified about a change in the power state when you connect or disconnect your cable. In your case, the power cable was already connected when the device booted, so there was no "power connected" event and therefore Delayed Lock still assumes there is no power cable connected. Unplugging & replugging it once after reboot should fix it
[Paid Software Announcement and Discussion] Mquinteiro:
In the last versión, to change security to pattern I have to select «system delay disable» when I press it the security menu opens and can choose the pattern and then it saves preterm option.

If I do choosing pattern does the same but do not save me selection.

It works perfectly before.

Nexus 5 kit Kat 4.4.2
[Paid Software Announcement and Discussion] dshanks:
Today at 9:51 AM, the Delayed Lock says it's disabled by Bluetooth at 9:50 AM. The phone not connected to Bluetooth right now. It is also not connected to Wifi (although a known network is available).

Log file attached.
[Paid Software Announcement and Discussion] rbird2:
Delayed Lock app not on the Amazon App store.

Your "Delayed Lock" app is not on the Amazon App store.

I have some credit at the Amazon store and want to buy your app.

Please add your "Delayed Lock" app to the Amazon App store.

Thank you,

Rodger
[Paid Software Announcement and Discussion] j4velin:
thanks again, I think I finally found the issue. Non-debug version is attached and should now work as expected
[Paid Software Announcement and Discussion] dshanks:
Hi again,

I installed the non-debug version and purchased the unlock. It's been working correctly for the past two or three days. This morning, however, I'm back to buggy behavior. I'm at work and connected to one of the SSIDs in the Delayed Lock list (the last one in the list, if it makes a difference). There is no delayed lock icon in the notification area, nothing from Delayed Lock in the notifications list, and the phone is locking when the screen times out.

This app is great when it works, but ...

Thoughts?
[Paid Software Announcement and Discussion] j4velin:
Okay, then we're back at the debug version...
[Paid Software Announcement and Discussion] dshanks:
Don't know if the attached log file will help or not. I downloaded and installed the debug version. Behavior described above continued after the install. I allowed it to run like that for a few minutes and then restarted the phone. After the restart Delayed Lock behaved appropriately.

I'll keep the debug version on my phone for a while and send you the log if I see another failure.
[Paid Software Announcement and Discussion] dshanks:
I see the issue described in Message 846 again.

This morning my phone is repeatedly locking while connected to a known WiFi network. It is connected to WiFi SSID EngTest2GHz2 which is the last SSID in Delayed Lock's list of known SSIDs. There is no Delayed Lock icon showing in the notifications bar and no message in the notifications list.

Log file is attached.

EDIT: I think I figured it out. This appears to be user error. When I typed in the list of SSIDs for work into Delayed Lock I accidentally entered EngTest2GHz2 as EngTest2Ghz2. Not the case error for the 'H.' Since SSIDs are case sensitive, Delayed Lock did not recognize the network with the error.

The behavior I observed appears not to be a bug in Delayed Lock.

Thanks for working with me to get the program working properly.
[Paid Software Announcement and Discussion] qlulp:
quite cool, thank you :>
[Paid Software Announcement and Discussion] khaytsus:
I've been having problems where I'll get my phone out after a long period of time and find it at the slide unlock, when it's set to go back to my pattern lock 5 minutes after screen off.

Should I use this debug version and when I reproduce the error gather a log? I suspect Android is killing it at some point, which is annoying that it'd kill it. Show Notification, Show Button Below are both checked in settings, but "Display status bar icon" is not. I don't recall if I unchecked this or not. Would that lower its priority and make it easier to kill?

It works 90% of the time, but randomly I find it didn't re-lock.
[Paid Software Announcement and Discussion] j4velin:
That might be the case, especially if your device is running low on memory. Switch to "lock since last unlock" option instead of "screen off" to avoid relying on the background service
[Paid Software Announcement and Discussion] khaytsus:
Does that mean if I set it to 5 minutes and I use the phone for 10, it immediately locks when the screen goes off? I really want it to not lock for 5 minutes after the screen goes off.

My phone shouldn't be running low on memory, but we all know that Android has a big hammer and everything looks like a nail sometimes ;)
[Paid Software Announcement and Discussion] j4velin:
The attached version should handle those kills better: It starts as foreground service if the "since screen off" option is used and if it still gets killed, it will lock the device as soon as the system restarts the app.

Let me know if that version works better, then I'll implement the changes in the next Play Store version. If you still have issues, please send me the log created by this version, thanks
[Paid Software Announcement and Discussion] andy o:
4.4.3 seems to have fixed the bug of services not restarting after being killed, FWIW.
[Paid Software Announcement and Discussion] olivierg13:
Indeed, same thing with me :)
[Paid Software Announcement and Discussion] nagendraps:
j4velin, on recent change I cannot able update to Delayed Lock from google play , I am getting below error since yesterday. But i can able to update other apps.
[Paid Software Announcement and Discussion] j4velin:
I have several users reporting that issue, however I really don't have any influence on Play Store related issues. I attached the current version if you want to sideload it
[Paid Software Announcement and Discussion] TrancerSte:
Hey, I hope it's OK to request a feature here - I have skimmed the last few pages and not seen any similar requests. I would like to suggest the option to prevent lock when a wired headset or headphones are connected.

I appreciate the answer might be 'use Tasker' but I'll take the chance in suggesting this is very low-level functionality much like "Disable lock while connected to external power" that could benefit from being included in the app.

Thanks
[Paid Software Announcement and Discussion] nagendraps:
Thanks j4velin, it seems they fixed play store issue. I could able to update now.
[Paid Software Announcement and Discussion] vaguy:
Second user on 10.1 tablet - You seem to use FaceUnlock

Been using paid version of Delayed Lock on Galaxy Note II (Android 4.3) with no problems.

Just purchased a Samsung tablet 10.1 2014 (Android 4.4.2) 3G/Wifi

Installed Delayed Lock first on on tablet's initial account - works fine.

Added a second user

I've got the Samsung Screen lock settings set to Swipe.

During setup of Delayed Lock, I get to the point of choosing a Lockscreen

I select "PIN or password", enter and confirm my PIN and touch "Save".

Popup comes back with: Error - You seem to use FaceUnlock which is incompatible with deactivate PIN method!

It winds up changing the Samsung screen lock to the pin I entered.

I must then cancel to get out of the dialog.

There is no option for FaceUnlock

Am I missing something?
[Paid Software Announcement and Discussion] j4velin:
Try setting up a PIN lockscreen first in the Android settings
[Paid Software Announcement and Discussion] vaguy:
Nope, same error. I also tried deleting and recreating second account. Then reinstalled Delayed Lock. Same error
[Paid Software Announcement and Discussion] Saturn007:
Hi mate,

Just wondering if you have any plans to release this on the Amazon AppStore. I would definetely buy it from there if you decide to publish it there as well. Hope to hear from you.

Great app and have recommended it to a few of my mates.
[Paid Software Announcement and Discussion] j4velin:
Well, the error message is shown if Delayed Lock is unable to change your PIN code. Do you have any other app installed that prevents this? Or any system options enabled that might cause the issue, like some Smasung KNOX stuff?

I just uploaded the app to amazon, however it might take some time for the amazon team to review it.
[Paid Software Announcement and Discussion] j4velin:
Well, that's the issue: If you can not disable the lockscreen from the system, then Delayed Lock can also not disable it. So you have something on your device which has set a minimum requirement for the lockscreen. Exchange server? Custom certificates added? GotYa installed?
[Paid Software Announcement and Discussion] vaguy:
But it is working for primary user using Swipe method. As I indicated before, this is fresh out of the box, no exchange, no knox, no custom certs, no nothing - just firefox. Even though "None" is missing from Android 4.4.2 lock screen choices, Delayed Lock does work for primary user using Swipe method - a pain, but it does work. Based on your thought of a minimum requirement, I did some looking. Seems 4.4.2 has some issues with screen lock on other platforms include None option missing. Right now I have Delayed Lock running OK on Samsung Galaxy Note II (4.3), Samsung Galaxy Light (4.2.2), and primary user on Samsung 10.1 2014 (4.4.2). It's only giving me the inaccurate FaceUnlock error

with a second user

on my 10.1 tablet.

So I ask again. Has anyone monitoring this forum used it under 4.4.2 or with multiple users?

Is there a debug version I can piddle with to give you some diagnostic evidence?
[Paid Software Announcement and Discussion] Ingenium13:
It works fine for me on my Galaxy S4 with 4.4.2 and Nexus 7 with 4.4.3. I haven't tried multiple users.

I do remember having to play with the native lockscreen settings on my Nexus 7 (4.4.2 at the time) to get it to work right, like switching to different methods and toggling it off and on but it eventually worked. But I assumed that was just because I have a custom certificate installed which requires a PIN to be set.
[Paid Software Announcement and Discussion] RickPJ:
I've just tried it on my Nexus 7 as second user (4.4.2). There is no lock option in system settings for "none", and I get the slide lock during the period when DL is disabling the lock. No error message though.

So it looks like you will always have to at least slide to unlock in 4.4.*.
[Paid Software Announcement and Discussion] vaguy:
Thanks for replies.

I wound up trying a factory reset. Didn't help my cause, but learned a few things.

After a factory reset, there is a "None" screen lock option for the primary account, but not for secondary accounts.

On the primary account, once you make an Android screen lock choice other than "None" or "Swipe" the "None" option disappears never to be seen again. If you let DL set the PIN, the method changes to "PIN", but the "None" option remains

So after DL sets the PIN, I used the Android screen lock settings to set the automatic lock timer to "immediately", then set the screen lock method to "None". That keeps having to use a Swipe to unlock with 4.4.*

But my secondary account has never shown the "None" screen lock option and DL always fails with the bogus FaceUnlock message when setting it to use a PIN. I've tried setting up DL first on the secondary account rather than the primary account. Still fails and this is immediately after a factory reset. I've installed no Apps except DL. This a T-Mobile rendition. There are tons of CA certificates installed. No user certs.
[Paid Software Announcement and Discussion] j4velin:
okay, I guess Delayed Lock won't work with multiple users then
[Paid Software Announcement and Discussion] j4velin:
App is now available here: http://www.amazon.com/j4velin-Delayed-Lock/dp/B00L28UBDU/ Let me know if the in-app purchase works
[Paid Software Announcement and Discussion] PeterLustig61:
Thanks a lot for this app.
[Paid Software Announcement and Discussion] bagman002:
HTC One M7/M8

Hi j4velin,

I have had a search on this thread and was unable to find an answer to my issue.

I understand and you state that there is some issues with HTC devices but I wanted to know if there is a work around that can get the job done.

I want to trail it on my HTC One M7 (Rooted, with stock ROM) and if I can get it to work I will root my HTC One M8 (stock ROM)

Delayed lock will tell me in the notifications area that the phone is now "unlocked" but still requires a pattern. I have tried unchecking require manual unlock once which had no affect.

Hope you can help

Thanks

Brent
[Paid Software Announcement and Discussion] j4velin:
Could you try the attached version? Also please try entering any pattern at all if your device is supposed to be unlocked - it seems that HTC might still show the lockscreen but no actual pattern is required to unlock it. If it doesn't work, please send me a mail through the "report a problem" option so I get some system information, thanks
[Paid Software Announcement and Discussion] bagman002:
Thanks for the quick response. HTC still requires the correct pattern. I attempted using an icorrect pattern and I was still locked out.

I will install the APK you provided and see how I go.

EDIT: Unfortunatly the APK that you attached made no difference. Is this an issue with HTC Sense? If I installed a customer ROM will this application start working for me?