Notices

Yeah, definetly a QtQuick problem. Appears you haven't got QtQuick installed on your device which would explain why the UI isn't being displayed.

I think you need to do the following to fix it, if it does work then I'll add the packages as dependencies in the next version.
If that doesn't fix it then try this:

Hello Spartan,
Thank you so so so much. It worked. One more question while testing I tried to lock savecpu.py file but didn't locked the software. I tried on conversation and it worked. Although, I need the software for conversation,email, filemanager, camera, photos only but still wondering is the software working only for conversation email etc?
I understand you like to get feedback. One small bug in this software when I click start daemon still the pop up remains. Its no big deal but I know you always like to improve...Thank you once again for this awesome app...

Excellent, was it the first one that I gave you that worked or the second? Just need to know which dependency I need to add for the next version.

Yeah, at the moment I am busy working on implementing support for Python and Bash scripts (.py and .sh) but it is not yet finished so while you can lock them it doesn't actually lock the phone when one of those scripts is opened. It should work for most other applications though, you can see what type of application it is by clicking on it and reading what is says below the application's name. Currently Binary, DBus and Complex applications are all supported.

The popup when you click Start Daemon should only remain there as long as it takes to start the daemon, just a way of showing that it is busy working until I can get a decent "I'm Busy" dialog written up . If it stays there for over a few seconds then something may be wrong, try restarting your phone and checking again maybe? It could be that DBus hasn't picked up the new service file for the daemon.

Thanks for the reports though, every little one helps make the next version better

@Spartan, I am trying to lock other apps like email, photos, SIb, filemanager etc lock icon is shown but it is not locked..Only converssation icon is locked in my first attempt which was my first attempt. sorry to keep troubling you

Thanks Spartan for quick response.
The fist command worked for me so I didn't tried second option you gave me.

You are right about the start daemon pop up.

Could you please just let me know which apps could be locked. I tried Notes,Sib, filemanager, email, setting, photos and midnight commander. Only conversation worked because that was the first app I locked for experiment but in next attempt when I opened the app and tried to lock above app. it showed lock icon but it is not locked.

Thanks once again

Thankz alot guys... its working plz tell me how to lock keyboad press ....

@linuxnoob
I ran a bunch of tests and managed to come up with the following results:
Notes: doesn't lock*
File Manager: doesn't lock*
Photos: locks
Email: locks
Settings: doesn't lock*

*It appears that although these applications specify that they support launching via DBus, they aren't actually launched that way. So in this case I will write up some override files for these applications and include them in the next release.

@brokensmile
You no longer need to, that is all done automatically when you choose to lock an application for which I have written an override file to support keypresses. Currently only Phone and Contacts support this feature.

Thanks Spartan, I ran test on few other software too. Would just like to update you that these software also not working even though they all are dbus.
Appmanager,
extended call log
xterminal

This is the most awaited software for me. I can't thank you enough.

Okay, I will look into them and write up override files for the next release.

Alright, v0.3.3 is in extras-devel and on my website. It is mainly a release to cover the apps linuxnoob identified that don't lock correctly for some reason or another.