Active Topics
-
[M7] [Announce] HP41cx (0)
to Applications by Halftux - 7 hrs, 48 mins ago -
Camera phone competition March 2023 "Endless" (21)
to General by Maemish - 1 day, 6 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 3 days, 10 hrs ago - more...
|
2011-06-22
, 21:26
|
|
Posts: 96 |
Thanked: 51 times |
Joined on Jul 2010
@ India
|
#32
|
Originally Posted by SPARTAN563
Thanks for showin intrest. I'm really looking forward to that app.
Hi, it should be since it will compile to native code (doesn't have to run through an interpreter). That being said it will still chow battery until I can get it to stop intelligently.
Am in the process of coding up an early version now, hopefully it will be ready for early testing in a few days time. Also, since I am coming from a Windows/.NET background it will take a bit of fiddling to figure out how to get a list of running processes (looks like I'll have to make use of /proc) but once that is done it shouldn't be too hard.
May also consider making it have some DBus calls so you can pause it or start it using a shortcut or something on your desktop (you could call the lock thing anyway when you do so just to prevent them from doing it themselves) which would prevent it from sharpening its claws on your precious battery
Will let you know when I have something to show for it.
Regards,
SPARTAN563
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.
| The Following User Says Thank You to warhawk007 For This Useful Post: | ||
 |
|
2011-06-23
, 05:58
|
|
Posts: 92 |
Thanked: 92 times |
Joined on May 2011
@ Stellenbosch, South Africa
|
#33
|
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).
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).
__________________
Sierra Softworks
Sierra Softworks
| The Following User Says Thank You to SPARTAN563 For This Useful Post: | ||
|
|
2011-06-23
, 08:17
|
|
Posts: 96 |
Thanked: 51 times |
Joined on Jul 2010
@ India
|
#34
|
Originally Posted by SPARTAN563
Wow...thats great news!! I'm eagerly waiting for a release.
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).
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!
| The Following User Says Thank You to warhawk007 For This Useful Post: | ||
|
|
2011-06-23
, 11:23
|
|
Posts: 92 |
Thanked: 92 times |
Joined on May 2011
@ Stellenbosch, South Africa
|
#35
|
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
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:
Code:
[D-BUS Service] Name=com.sierrasoftworks.NETKey Exec=/opt/netkey/NETKey -d
Code:
[D-BUS Service] Name=com.sierrasoftworks.NETKey Exec=applock --launch "/opt/netkey/NETKey -d"
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
__________________
Sierra Softworks
Sierra Softworks
| The Following 2 Users Say Thank You to SPARTAN563 For This Useful Post: | ||
|
|
2011-06-23
, 15:49
|
|
Posts: 92 |
Thanked: 92 times |
Joined on May 2011
@ Stellenbosch, South Africa
|
#36
|
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:
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
__________________
Sierra Softworks
Sierra Softworks
| The Following 2 Users Say Thank You to SPARTAN563 For This Useful Post: | ||
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.
Sierra Softworks
Last edited by SPARTAN563; 2011-06-22 at 16:37.