Notices

@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

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.

@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

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!

@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

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

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.

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

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?

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: