Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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:

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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...

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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 :)

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@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

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@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.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

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.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@Spartan
Dats gr8 thankz..... it works damn gr8!
As we hav browser switcher app ... i want app installer switcher so dat i can switch to default app manager to fast app mang

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

I'm afraid I don't see the point in writing an application like that. If you want to install a deb file without using HAM then simply use a terminal with DPKG, it is a lot faster and probably less prone to problems than using FApMan. If you really want an application to do that then look into learning C++ (using the Nokia SDK) and research how to change MIME type registrations on the N900. You would also probably have to contact the people who wrote FApMan and get them to add a command line command for installing a deb package.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@spartan...sorry was away and busy so couldn't thank you.I updated to 3.3 version from app manager but it seems like it still has problem...should I uninstall and reinstall it all again to work it properly...sorry for giving u so much trouble

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

I was at my university and sadly didnt get a chance to test v3.1 & 3.2 as my N900 had to go through a reflash due to an issue with multiboot and I didnt have access to a PC. :(

So well, flashed my N900 yesterday and installed v3.3 and I'm really impressed. This is just what I wanted and 3.3 seems almost flawless. Everything works as it should. And like any of Spartan's bug-fixing releases, this was fast.
Testing this app was more like an adventure with Spartan being a dedicated developer offering quick assistance and almost immediate bug-fixes. Hence, I step up to say a big "Thank You" for this release. :)

Doesnt this qualify for beta now ;)

Cheers! :)

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@linuxnoob, that is weird. I must admit I am stumbling around a bit with those applications since I am not entirely sure what Hildon uses to start them. It looks like 1 or 2 of them get started using AppLauncher, the others don't get launched using DBus (leading me to assume that they are being launched by their path) but if it isn't detecting them when they are launched that way...who knows. I will see if I can get around to releasing a new version early next week. Unfortunately this week I have to write up a website to handle voting for our residence's house committee which is taking a good deal of time.

@warhawk, yeah my N900 is being a bit irritable of late, if I boot into NITDroid I have to manually flash or sit in a reboot loop when I try to get into Maemo. Regular pain in the rear ;). Glad to hear v0.3.3 is working for you though, that is excellent news :). I like the "dedicated developer" part LOL, still in the process of learning C++ so that is quite neat to hear :) but I'm glad I was able to get stuff done fast enough for you guys ;) (It was SERIOUSLY slow by my usual standards), thanks anyway.

Not sure yet, unfortunately I can't promote it to extras-testing because it depends on QtQuickCompat...Will do a bit of research for the next release to find out how to fix that and then I will try pushing it to testing. But I guess you can assume it is ready for a bit of beta testing right now since I haven't heard of it killing anyone's phones yet ;)

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

hello.. spartan563, first of all thank you very much for creating such an useful application. this is my first install of your app i.e i have installed the latest version - 0.3.3
i thought to share some bugs which i noticed and might be useful.. do guide me if there's any solution for the same.
- conversation app locks quite efficiently but i tried other apps such as media player, though the lock icon did appear beside it and the daemon restarted still the t fails to lock on launch of the app
- secondly i tried locking file manager, the moment i click on it the applock crashes and fails to register the lock.
i have not tried previous version and this is the fresh install i am working with.
thanks for the help.
keep up the good work

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

hello Spartan,
Sorry I was away and little busy myself thats why couldn't reply you quickly Nobody can complain even if you delay for a month since you are pretty fast in commenting and working for this awesome software plus we all know how much university work comsumes time so take your time. wont use applock for 3-4 days since I am thinking to repartition it. One thing I would like to tell you is that the when the sms comes it is displayed in yellow box and if we click on yellow box we can still read msg. Is there a way that when the message arrives then only software locks or hides the message cuz right now only when we click on conversation then only applock locks the screen. I am guessing it would be very hard thing to do since it isphone default feature that whenever sms comes it is displayed on the yellow box screen.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@constantine
Thanks for letting me know, unfortunately I am busy working quite hard at university, both doing university work for my engineering course and also finishing up some applications that need to be completed this week for different events around campus. I did look a bit harder at those apps you mentioned and TBH I am completely confused by how Nokia decided to launch them. Seems like some use the "maemo-invoker" tool so I tried messing around with my DBus overrides for them to detect when they are launched but nothing working yet. I also managed to replicate the bug you're getting with File Manager, that confuses me a lot and it looks like it will take a bit of time to figure out why exactly it is doing that (I really miss .NET's error reporting there).

@linuxnoob
Thanks, makes me feel better about not getting around replying to this thread yet. As for locking the phone when an SMS comes through, I'll take a look but I don't usually get all that many SMSes (use IMs a lot more) and I never remember to check what DBus calls are being made when I do, will try and remember to check next time I get one. Otherwise you are welcome to see if you can figure it out. Just open up a terminal and run "dbus-monitor" before clicking on the yellow popup, then read through the output from dbus-monitor and see if there is anything in there that looks like it is opening the conversations app. If you can find one then PM it to me and I'll add it to the override file. Unfortunately though, if there isn't a DBus call when it is clicked it will make it extremely hard (impossible in my case, since I haven't learnt how to inject libraries) to detect. I guess another method would be to monitor the conversations database to check when the number of unread messages decrements and lock then, but that would probably aggravate people whenever they clicked on a new message in an already unlocked conversations app.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

i installed applock and it drains my battery too fast while in idle state. is there any fix? i have tested my idle battery usage with applock installed and without applock. so anyone can helpout?

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Hi Sanros,
Could you do the following for me to help test why AppLock is draining your battery:
Open up a terminal and type: "ps | grep AppLock"
Remember the Process ID that comes up and run it again, see if it changes. If it does then it sounds like AppLock isn't starting the daemon correctly and it may be a problem with the Upstart script. As a temporary fix in that case you can type this into your console to prevent Upstart from starting AppLock:

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

hello spartan
thank you for your reply:)
this is what i get ---

Nokia-N900:~# ps|grep AppLock
8033 user 61812 S /opt/applock/AppLock -d
9614 root 2092 S grep AppLock
Nokia-N900:~# ps|grep AppLock
8033 user 61812 S /opt/applock/AppLock -d
9620 root 2092 S grep AppLock
Nokia-N900:~# ps|grep AppLock
8033 user 61812 S /opt/applock/AppLock -d
9623 root 2092 S grep AppLock
Nokia-N900:~# ps|grep AppLock
8033 user 61812 S /opt/applock/AppLock -d
9718 root 2092 S grep AppLock
Nokia-N900:~#

is it ok or there is a problem with the daemon? coz its eating my battery when i unistall it everything is fine then.
i just locked conversations using this aap
hope i can use this app with good batterylife

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Hmm, it appears to be working correctly so I'm not sure why it is killing your battery. I'll look into it along with the other problems as soon as I get some free time on my hands. Unfortunately I have been quite busy of late, with no let up in sight :)

Otherwise, you are welcome to grab the code yourself and look at it if you understand a bit of C++.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

i have tested my battery drain with and without this app.
i just used aaplock to lock conversation only.
as u said app is working fine but i really don't think so because its using alot of battery its using cpu % in background i think when n900 is idle.
i hope you get some time soon to fix this bug so that we all n900 users can enjoy this wonderfull app
as for now i will uninstall this app coz i am not such a advance user i am lil more than a noob :D but not so skilled to work on app commands
thank you for your hardwork Spartan

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Hey Santos,
Have been testing the all extensively for the past 2 days on my phone with no noticable detriment to battery life. Leads me to believe that maybe there is something else going on which is being excaserbated by AppLock, maybe another app launching and closing a lot or one which spams DBus name requests.

You could try running "dbus-monitor" and see what it outputs, if it keeps outputting lots of stuff and doesn't seem to pause then you may want to look into what is doing that. Will still look at the code again when I get the chance, since there are still a few small bugs which need fixing.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Hello Spartan, sorry for replying to u late...was little busy..I want to point out that my battery started graining too after applock but I am not sure and wont be sure until I reformat the phone..Removing the applock didnt solve the problem though...I would install applock again to test dbus monitor thing...sorry I tried the command but it didnt work..could u plz explain me more how to do it......really noob here so bare with me...explain the steps and I would do it when any sms comes...as far as battery concern I think there might be some file which is draining the battery but not applock...maybe my battery got old too cuz its almost one yr now...who knows...anyways sorry and thanks once agan look forward to check dbus monitor...

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

hello SPARTAN,
i was away for a while,
i am also facing battery drain after uninstalling the app( as linuxnoob stated)
so please help me out by guiding me how to manually delete remaining files of the app( may be they are conflicting with some script)

how to use dbus-monitor? in xterm?

thank you for your help

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

this is the result after running dbus-monitor command in xterm as root ---


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ root


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Nokia-N900:~# dbus-monitor
signal sender=org.freedesktop.DBus -> dest=:1.359 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.359"
method call sender=:1.359 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_call'"
method call sender=:1.359 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='method_return'"
method call sender=:1.359 -> dest=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "type='error'"
method call sender=:1.29 -> dest=com.nokia.HildonDesktop.AppMgr serial=422 path=/com/nokia/HildonDesktop/AppMgr; interface=com.nokia.HildonDesktop.AppMgr; member=LaunchApplication
string "browser"
method call sender=:1.30 -> dest=com.nokia.osso_browser serial=525 path=/com/nokia/osso_browser; interface=com.nokia.osso_browser; member=top_application
method call sender=:1.85 -> dest=com.nokia.HildonDesktop.AppMgr serial=44 path=/com/nokia/HildonDesktop/AppMgr; interface=com.nokia.HildonDesktop.AppMgr; member=LaunchApplication
string ""
error sender=:1.85 -> dest=:1.30 error_name=org.freedesktop.DBus.Error.UnknownMetho d reply_serial=525
string "Method "top_application" with signature "" on interface "com.nokia.osso_browser" doesn't exist
"
method return sender=:1.30 -> dest=:1.29 reply_serial=422
method return sender=:1.30 -> dest=:1.85 reply_serial=44
method call sender=:1.85 -> dest=com.nokia.HildonDesktop.AppMgr serial=46 path=/com/nokia/HildonDesktop/AppMgr; interface=com.nokia.HildonDesktop.AppMgr; member=LaunchApplication
string ""
method return sender=:1.30 -> dest=:1.85 reply_serial=46
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=154 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string ":1.360"
string ""
string ":1.360"
method call sender=:1.360 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method call sender=:1.360 -> dest=org.gtk.vfs.Daemon serial=2 path=/org/gtk/vfs/mounttracker; interface=org.gtk.vfs.MountTracker; member=listMountableInfo
method return sender=:1.7 -> dest=:1.360 reply_serial=2
array [
struct {
string "sftp"
string "sftp"
array [
string "ssh"
]
int32 22
boolean true
}
struct {
string "http"
string "http"
array [
]
int32 0
boolean false
}
struct {
string "trash"
string "trash"
array [
]
int32 0
boolean false
}
struct {
string "obex"
string "obex"
array [
]
int32 0
boolean false
}
struct {
string "computer"
string "computer"
array [
]
int32 0
boolean false
}
struct {
string "network"
string "network"
array [
]
int32 0
boolean false
}
struct {
string "dav"
string "dav"
array [
]
int32 0
boolean false
}
struct {
string "localtest"
string "localtest"
array [
]
int32 0
boolean false
}
struct {
string "ftp"
string "ftp"
array [
]
int32 21
boolean true
}
struct {
string "burn"
string "burn"
array [
]
int32 0
boolean false
}
]
signal sender=:1.4 -> dest=(null destination) serial=30 path=/com/nokia/alarmd; interface=com.nokia.alarmd; member=queue_status_ind
int32 0
int32 2147483647
int32 2147483647
int32 1312837200
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=155 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string "com.nokia.adobe-flashplayer"
string ""
string ":1.344"
method call sender=:1.344 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RequestName
string "com.nokia.adobe-flashplayer"
uint32 1

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@linuxnoob
Not a problem :), weird that you say your battery started draining AFTER you removed it. I haven't tried that so I'll do that tomorrow and see if it works. My battery is only around 9 months old now and actually lasts longer now than it did when I first got my phone (thanks to a lot of tweaks :))
As for running the dbus-monitor command, don't worry about it. Managed to do it myself when I did finally get an SMS and it looks like the only DBus messages that are emitted are done so by Telepathy in order to let everything know that the message has been read. I would rather NOT lock the phone whenever it detects a message being read as that would get irritating very quickly :)

What I might try doing is launching dbus-monitor and then sending an SMS to myself to see if there is anything that gets sent there which is of any use (i.e. before the message is opened)

@sanros
The files for the app are located in the following locations:
Application files: /opt/applock
Settings files: /home/user/.applock

Thanks for the output, afraid that it doesn't look like there is anything there which is thrashing the DBus, but it is more dependent on how fast the messages appear rather than what messages do. Hence the reason I advised that you run it and look at the screen to see what is happening. I will keep trying to reproduce the situation on my phone but I am afraid I'm not having a lot of luck with it.

You may also want to check that you haven't recently overclocked your phone, or installed a different kernel or anything like that. Just tossing ideas out there

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

@ spartan, sorry mate I couldn't help u for one help u asked for...anyways thanks for looking up and explaining to me...been busy these days a lot not getting time to reformat my phone..actually after installing applock i could see my battrery was draining and it continued even after uninstalling but I would actually come to know only after repartion....I would like to install ipk games so for that I will repartition plus hopefully it would solve my battery problem..I want to ask u one question regarding pythn 2.5. I know its not related to applock application but by any chance do u knwo P.R 1.3 has preinstalled python 2.5 cuz when I was trying to install cleven 1.3 it said it needed python 2.5 complete version..when I tried to download from FAP .it said its broken or corrupt so the cleven never worked on phone...

Thanks in advance

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Not a problem, afraid I still can't find anything on my side that points to battery drain, so I'm going to assume it is something else that you guys have hit on for the mean time. Will also be porting AppLock over to MeeGo/Harmattan within the next few weeks (provided Harmattan does use DBus as much as Maemo) and that will give me the chance to do some more work on everything.

As for Python, I really am not sure if it comes bundled. I had it installed on my phone when I first wanted to use it, but it could well have been there from a previous application install. You could always try installing it manually from the console:
As for Cleven, I'd recommend you don't install it unless you actually have a legitimate reason to be running penetration testing. Doing so without permission is HIGHLY illegal and can land you up in jail very quickly if you aren't careful. Besides, cracking WPA networks (which most people run now) will take way too long on your N900 to be of any use, and I highly doubt you are running a WEP network? Anyway, just my $0.02, good luck anyway :)

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Just to clarify things - Pentesting Your own network is perfectly legal, no matter if You do it with aircrack, or a hammer. Which, of course, is think every fAircrack/Cleven users do, yes? ;) (pentesting own network, not hammering it).

Those hacking other people networks without permission - we don't even want to talk with them ;)

Sorry for off-topic, but since thread owner started it anyway...

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Tomorrow I might reformat the N900 so will know about battery..you might bethanks guys...I really dont need to crack any network since i right spartan since there are so many softwares we use so it might one of them...thanks for testing for us...really appreciate it..
I have my own net but it is for testing...I never tried it so wanted to test it on my own net..I have little bit of ocd so wont keep the software after I tested it on my own router.

Thanks

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

I hope ur software works on MEEGO too..best of luck spartan

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Fair enough, look forward to hearing back from you RE the battery life issue. As for MeeGo, I'll let you know as soon as I get my N950 (hopefully that will be next week or the week after).

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Okay, excellent news:
I managed to find and fix the battery usage issue as well as fix the crash when you clicked on the File Manager entry in the menu. Will upload my nightly build to Extras-Devel though I plan on doing some extra work on the UI to match the Harmattan UI guidelines since they seem to look pretty decent :)
Will also be looking into porting this app over to Harmattan on the N9/N950 which should be fun. Hopefully Harmattan doesn't have one of these "maemo-launcher" things which wreaks havoc with locking certain applications. I am still trying to figure out a way to fix that when I have the time.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Version for N950? For all 250/300 of them? :rolleyes:

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Sure, why not? I'm getting one so I figure it would probably be kinda cool to have one of my apps running on it ;)
Besides, if it runs on the N950 then it should run on the N9 (not sure how many of those will be sold tho)

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

I just hope that You'll backport to N900 every possible "new" feature of maemo6harmattanhalfmeego version.

Of course, it's perfectly up to your discretion what You do with your free time, but it would be - IMO - big waste, if even part of Your nice effort would sink in halfmeego blackhole.

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

Of course, since it really is only a compile away to get it working, and I am already using QML it really shouldn't be hard. Besides, I have absolutely zero intention of giving up my N900, I love it :) but it never hurts to write an app up for a second platform.

Also, unfortunately the biggest problem with the N900 is simply that not enough people know about it and have one. Now, I know Harmattan is a horrible hodgepodge between MeeGo and god knows what, but it does have the advantage of at least having the opportunity to appeal to a wider audience. So instead of sitting here going "Gah, look at how horrible that is", why not rather try and make it better? I mean, that's what the community did with the N900 isn't it?

Re: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
 

this does not lock file manager nor file box!!!!!!! photos and notes are asking the code but not file manager why?

can anyone help me???????