DroidLock -- protect your Android device!

[tattedupboy]

Hi,

If you check the DroidLock preferences, do you see that "Enable protection" is checked? If so, please email support@droidmate.com so we can investigate further.

Thanks,


Droidmate Support

Yes, that option is definitely checked. Even after rebooting and making sure it was checked again and making sure I had apps protected, I'm still not getting prompted for a password to access them. Should I just give it some time to let the settings kick in?

Sent from my DROID2 using DroidForums

[tattedupboy]

OK, so my first issue has been fixed. Now I've noticed that text messages (I use Go SMS Pro) and non-GMail email notifications are still accessible via the pull-down notification bar despite Go SMS and K-9 Email being protected apps. Is there a fix for this?

Sent from my DROID2 using DroidForums

[droidmate]

Yes, those can be protected as well. Reference a post I made earlier:

Start the main DroidLock application and go to Preferences > Protection Method and check "Interactive selection". This will prompt you to enable protection for any unprotected application that's started. Then, open GMail via the notification bar (you may have to send yourself a quick email to make it appear again). You will be asked if you want to enable protection; choose "yes". Then, go back to Preferences > Protection Method and uncheck "Interactive selection" (you can keep it selected if you wish, but normally you would only use this option to protect an application that can't be accessed via the launcher).

The "interactive selection" feature is what you want to use to handle these cases since notifications and the like aren't actually launchable applications and therefore you can't access them directly from the "add applications" portion of DroidLock. We will update DroidLock to automatically protect the notifications when you protect the application, just let us know which ones you need.

Thanks,


Droidmate Support

[sonicxtacy02]

I'm having the same problem as previous poster, the lock screen doesnt show up at all for chosen apps. And i'm sure i have lock enabled. This is using a droid bionic

[droidmate]

Hi,

I spoke with the other poster via email, and the problem is that he was using a custom ROM which disabled logging. Without logging, DroidLock, or any other lock app for that matter, cannot work. From my understanding, I believe you have to edit /data/local.prop and remove any setting that disables logging. Unfortunately, I don't know what that setting would be. Could you try contacting tattedupboy to see what he did?

Thanks,


Droidmate Support

[sonicxtacy02]

Hi,

I spoke with the other poster via email, and the problem is that he was using a custom ROM which disabled logging. Without logging, DroidLock, or any other lock app for that matter, cannot work. From my understanding, I believe you have to edit /data/local.prop and remove any setting that disables logging. Unfortunately, I don't know what that setting would be. Could you try contacting tattedupboy to see what he did?

Thanks,


Droidmate Support

Here's what i just figured out. I have to manually start DroidLock, then the locking will work. It appears whatever service you're using to do the launch monitoring doesnt automatically run when the phone boots. I'm running the factory rom, just rooted. I can actually set up DroidLock so it Tasker automatically launches it at boot, but Android kills it after some time of inactivity, requiring me to open it again to get the locking working again.

[droidmate]

That seems very odd. DroidLock actually uses a broadcast receiver that is notified when the phone boots, and then the service is started. If you have DroidLock notifications enabled (which is the case by default), you should see a DroidLock notification (either "protection enabled" or "protection disabled") as the phone boots. That will let you know that the service is started. That being said, there could be task management software killing DroidLock at boot or after some period of time. Have you whitelisted DroidLock in all your task killing software (i.e., told that software to ignore DroidLock)?

This is definitely the first I've heard of something like this, so I'd be interested in investigating further. If you don't mind spending some time collecting logs, running custom versions of DroidLock, and going back and forth, email support@droidmate.com and we can talk further. I can give you a free copy of DroidLock for your troubles.

Thanks,


Droidmate Support

[sonicxtacy02]

That seems very odd. DroidLock actually uses a broadcast receiver that is notified when the phone boots, and then the service is started. If you have DroidLock notifications enabled (which is the case by default), you should see a DroidLock notification (either "protection enabled" or "protection disabled") as the phone boots. That will let you know that the service is started. That being said, there could be task management software killing DroidLock at boot or after some period of time. Have you whitelisted DroidLock in all your task killing software (i.e., told that software to ignore DroidLock)?

This is definitely the first I've heard of something like this, so I'd be interested in investigating further. If you don't mind spending some time collecting logs, running custom versions of DroidLock, and going back and forth, email support@droidmate.com and we can talk further. I can give you a free copy of DroidLock for your troubles.

Thanks,


Droidmate Support

Thank you for the offer, but as a fellow software developer, you deserve to be paid for the work you do, and i'll gladly buy the full version once i figure out whats going on.. I'll conduct some more tests and will email you with some specifics. Thanks for your work.