SPARTAN563 | # 31 | 2011-06-22, 11:54 | Report

Hmm, still hasn't been pushed into the actual repository yet, very strange. You can check here to see when it does, your you can install it directly from my website here

EDIT: Package is now available through Extras-Devel, not sure why it didn't get moved earlier but it seems throwing it into the build que again fixed the problem.

---

Last edited by SPARTAN563; 2011-06-22 at 16:37.

warhawk007 | # 32 | 2011-06-22, 21:26 | Report

Thanks for showin intrest. I'm really looking forward to that app.
Moreover I guess you could integrate SIMlock as a park of your App locking application like Advanced Device Locks for Symbian or Perfect AppLock for Andriod.
As a result you could end up with a complete locking systen for the N900. An app which can lock apps, phone & SIM..depending usage scenario.

SPARTAN563 | # 33 | 2011-06-23, 05:58 | Report

I was considering integrating it but to be honest I think it would be nicer for people to have 2 seperate apps. I may just add a virtual package which depends on both to the repos. The reason for that is that SIMLock's daemon only tries to run until it does so successfully and then it doesn't again until you reboot next whereas the AppLock would have to run continuously.

At the moment I am trying to find the DBus signals that are emitted when the device goes into its standby state (i.e. screen gets dimmed) though I am considering just making it listen to the lock events rather.

I have written up all the code for checking when apps get launched as well as parsing .desktop files to get the list of installed apps but I still need to figure out how to listen to DBus tio_application calls for certain apps (contacts, messaginge etc.) which are run as daemons in the background. Then I just need to write up a UI (am tempted to just release a console version initially).

warhawk007 | # 34 | 2011-06-23, 08:17 | Report

Wow...thats great news!! I'm eagerly waiting for a release.
By the way, you should also note that the contacts application can still be invoked by using the hardware qwerty keyboard. I dont know if there is anyway to disable it. But I wish there was.
And about the integration part, what I meant was a more centralised locking application with deals with all the locking functionality, for example an app called "DeviceLocks" which has both your Applocker & Simlock integrated with individual settings for each.
But that was just a suggestion. Releasing a standalone applocker is also fine. You are the only one in this community who actually responded to this request and understood the concept & I know there are many people out here who would really appreciate an app like this.
Once again, eagerly awaiting the release of your application.

cheers!

SPARTAN563 | # 35 | 2011-06-23, 11:23 | Report

Hmm, okay so I've been doing a lot of research and I think I've finally managed to come up with a way of monitoring applications which are launched using DBus calls.

My idea is as follows:
The standard DBus launched applications set the X-Osso-Service property in their .desktop files, this is then used to launch the service based on the file contained within /usr/share/dbus-1/services
So, since I can't seem to intercept method calls using QtDBus, I was thinking it would be possible to modify the service files in /usr/share/dbus-1/services to go from something like this:
to
That could then be done on a per-app basis when the app gets locked, making a backup of the original .service file of course, which would then in theory route the launch of that application through AppLock.

Then I would also run a background daemon which could scan constantly for any applications that were launched which don't use DBus calls and, if they are on the list of monitored apps, lock the phone.

If you have a better idea though, or know how to intercept DBus calls to the top_application() function then I'd be happy to hear them. But I was also thinking, just intercepting top_application() would mean that each time the application was focused it would lock the phone, which could get VERY annoying. At least this way it should (in theory) only lock the phone when you click on the menu link or on a shortcut.

Will let you know if it does work as expected or if it just ends up dying horribly

SPARTAN563 | # 36 | 2011-06-23, 15:49 | Report

Okay, here is a new thread for discussing anything related to AppLock and its development.

http://talk.maemo.org/showthread.php...50#post1037350

So far the following functionality is available in my dev build:

• Add .desktop files for apps to the blacklist using the command line
• Show a list of locked apps from the command line (these aren't necessarily running)
• Lock the phone when an app is launched but don't keep locking it as long as that app stays open
• Lock the phone if another "locked" app is launched while a locked one is running but unlocked