Thread: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
View Single Post
warhawk007 is offline warhawk007
2011-07-11 , 20:34
Posts: 96 | Thanked: 51 times | Joined on Jul 2010 @ India
#87
Originally Posted by SPARTAN563 View Post
Haha, excellent.

Yeah, the way it works is that anything that adds a search to the DBus monitor will only be applied AFTER you refresh the daemon. Can you let me know if there is a delay or a hang on the UI when you remove the locks on DBus apps, if there isn't or it is very short then I will add in the immediate add support again.

As for why contacts doesn't get unlocked correctly, it may be that the daemon is hanging, if you restart the daemon does it fix it?

Cool, thanks for pointing that out, unfortunately that is built into the phone application so I can't lock it when you open it there. But on second thoughts, since it is a very limited version of the contacts app it may be possible for us to class it as part of the Phone rather than Contacts. If you do want to lock it completely though then you best lock Phone and Contacts

I also need to get around to finding out what DBus methods get called when you open a notification for a message since that opens Conversations.


Sounds like it, though I am also working on a lot of other stuff for the next release, like command line matching so we can start locking scripts and python applications

As for a Beta, not quite yet, will do when we have a stable install -> run cycle
Yeah, there is a momentary delay when unlocking dbus apps like conversations.
And just like contacts can be accessed through the Phone, Conversations with the numbers in the Call Log can also be accessed this way even when conversations is locked.

Open Phone > Click on a contact in call log > Call or SMS > click SMS and this opens our conversation with them. This is not a big deal anyways as we can always lock the phone app if we want like you told.

Will locking the phone app also lock the Phone when a call comes in? I was just wondering. This would be a problem if so. But I dont think this will happen as Maemo always gives top priority to Phone call events which explains why we are able to answer calls even when phone is auto locked. But I asked because I was wondering whether the applock daemon would bypass it.

And what about the contacts application not unlocking even when we unlock it in the UI. I mean the contacts app still locks when we try to launch it from the menu launcher. It isnt the daemon hanging, as the keyboard search gets unlocked on unlocking contacts from GUI. Its just the actual launching via menu that locks the phone. But this isnt a dealbreaker for me. Its still a wierd bug though.

I guess you can push a v.3.1 with the updated permissions for settings file. This would solve most problems reported by various users before.

EDIT: Also dont forget to fix that issue where the UI cant be launched from the menu in the next release. I was just reminding
Last edited by warhawk007; 2011-07-11 at 20:53.
 

The Following User Says Thank You to warhawk007 For This Useful Post: