Notices

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

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

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 but not so skilled to work on app commands
thank you for your hardwork Spartan

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.

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

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

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

@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

@ 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

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