I really like this app a lot better than the other device lock programs I've tried. I had the same problem with it taking tooooo long for the unlock screen to come up when using "devicelock". this one is really fast!. But, I have noticed that it doesn't play nice with some other apps. When using small menu I can still hit the "windows" button launching smallmenu. I can even move the stick around and launch programs. Even when its locked. It will not dial numbers though and the screen is still locked so atleast I won't call anybody by accident. I have also noticed when hitting the power button while streaming with windows media player, this will crash onlock. I have to then go into taskmanager and terminate onlock, and the go into the prefs and restart it. It does the same with googlemaps(ibm j2me emulator). if gmaps is running, turning off the device and back on will not bring up the unlock screen. it also crashes onlock and has to be terminated and restarted. I really hope there is fix available for this in future versions, cuz like I said before, I really like this app.
I had that very problem with smallmenu, but when I was using DeviceLock. Perhaps this is a problem with the built in lock itself. My software just triggers the lock. I will look into problems with other software soon. New version nearly ready. Sorry for the delay.
Ok new version. This version has a fully functional prefs app that can start and terminate the program. The lock will also prevent multiple instances from running at the same time. This version can also be installed anywhere (on device, ext rom, storage card, ect). I would advise against installing to an external card though, because if you take the card out, the lock will be terminated and if you forget to start it back up, you are left unprotected. You can if you wish to though. basically it will work anywhere as long as OnLockPrefs.exe and OnLock.exe are in the same directory. Or, if you choose not to use the prefs app, it doesnt matter at all. I also took out the notifications that OnLock is starting. If you think you want them back, let me know. Or I could make it an option. Let me know if you want that, otherwise it is a waste of space and code. I like it starting up quietly.
I will now try and modify the press and hold behavior. I am not sure if it is possible though. If anyone with some dev knowledge has ideas please PM me.
vinscuzzy, I made some changes to OnLock.exe. Let me know if it still locks up. Thanks for the continuing feedback.
I like the removal of the "onlock is starting" prompt; it's not necessary IMHO. Just want to reiterate kudos on this piece of software; it works wonderfully.
Looks great. Just gave it a go and it appears to lock MUCH faster than the vjDeviceLock I was using before. Also I really like not having to have the device lock today item enabled.
I will have to test this out for a few days and see what happens. I am particularly interested in what happens when calls come in and when alarm reminders popup.
Thanks. It should behave the same way vjDeviceLock did because it is triggering the same lock applet. When reminders and calls come, it will still allow you to dismiss the reminder and accept or reject the call, then lock the device from further interaction. The only way to change this behavior would be to write a whole lock program, rather than relying on the built in lock. I may try this later, but that part will be a little more difficult.
Thanks. It should behave the same way vjDeviceLock did because it is triggering the same lock applet. When reminders and calls come, it will still allow you to dismiss the reminder and accept or reject the call, then lock the device from further interaction. The only way to change this behavior would be to write a whole lock program, rather than relying on the built in lock. I may try this later, but that part will be a little more difficult.
I understand it is the same lock tool, but from what I read before your mentod of enabling it is a little different. Since you try and send the notification at shutdown, the lock should take place much earlier in the queue should it not?
I find that sometimes when the device is waking up for an event/call with vjDeviceLock that it tries to lock right in the middle. I think this is causing my phone to lockup on some calls, as well as cause some odd problems with the reminder popup dissapearing.
Might not be related but your version is already better since it does not need the lock plugin enabled on the today screen. I found it just wasted space, now the only plugin I have is SPB Pocket Plus with SPB Diary integrated.
Well I have tried and tried to modify the hold power button behavior. I tried several ways and did plenty of research. I only found one way to do it, and that one way isnt very reliable. It would involve me setting a key hook and watching the key events for the power key. The reason I do not want to use this is because WinCE 5 only supports one key hook at a time. So if any other app tries to hook the keys, that app will fail. Or if any app already has the keys hooked, my app will fail. I discovered this because my app could hook the keys in the emulator, but failed on my device. The reason was because I have PQZII installed, and PQZII hooks the keys. I will still try to see if there are any other ways, but I'm stumped for now. Let me know if you are having any trouble from the software.
Will watch and see how this program progresses; but I am looking for a program that can be run to "unlock" the phone. The reason is that sometimes the phone will get stuck while locked, and it can't be unlocked via the keyboard. In cases like this MS Voice command still works, and I can voice command a program to unlock and get access to the phone again.
Speaking of the password lock, my company just set the password policy on the exchange server.. I have had to stop using this lock program since my PPC 6700 seems to lock up each time that the system starts up password locked and is attempting to screen lock.
So here is an odd request. Could the program for a password lock instead of a screen lock on power off?
Hey, great job, JKingGrim. With the current WM5 "Password Lock" bug (that I describe in a different thread), your software is a welcome relief. It's doing it's job.
Question for JKingGrim...
(Bear with me... I'm writing a lot here.) With OnLock, when I turn the phone on, I see whatever was on my screen when I last shut it off, with "Unlock" on the bottom left. Now, when I hit that bottom left "Unlock", it basically calls the WM5 Unlock screen, so that I have to hit "Unlock" a second time in a different position on the screen (middle right). Is there any way in a future revision of OnLock to have it so that when we hit the first Unlock on the power-on screen, your program somehow in the background calls whatever it needs to in the WM5 Unlock screen and forces the unlock without displaying the WM5 Unlock screen or forcing that 2nd button push?
This would cut down not only the number of finger/stylus presses needed to unlock, but also cuts down having to look for the position of the 2nd Unlock button. (With WM5's Password Lock program, if had set the password to the same 4 numbers, I can almostly blindly unlock my screen once I find the position of the number. )
This would also make it so that what you see on the screen when you power on the 6700 doesn't disappear momentarily after you hit the first Unlock (as it does currently when the program brings up the 2nd unlock screen before returning you to your power-on screen.). Just wondering.
JkingGrim, just to let you know, I've been using your app for over a month now, and haven't had ANY problems. it works great! Now I just wish there was a way to unlock the device WITHOUT touching the damn screen, kinda like the treo's do.... I'm guessing someone would have to write an unlock app from the ground up to acomplish this though. Anyway, excellent job!
Just curious, am I the only one who can defeat OnLock using the start button the first time it runs (not using anything called smallmenu)? This is not meant to be a ding on jkinggrim...just curious if this program *really* works on standby as I thought it was supposed to. I just reinstalled OnLock (from page 2 of this thread) and here's what I do:
Verify that the phone is unlocked on the today screen. Press the power button to suspend the phone. Wait a couple of seconds, then press the power button again to turn the phone back on. Just before the screen comes on, hit the start button once (or a couple times if you're not sure of the timing). I always get the start menu up before the lock engages. Once the menu is up, I can choose one of the programs in there and select it, though once it starts I can't do anything else because the lock is engaged.
I only ask this because the program is supposed to lock on suspend (at least I thought so) and it appears not to be doing that, since I can get at least one button press in before the lock engages when I come out of suspend.
I'm not running .Net framework. I have VC1.6 installed on a Verizon 6700, if that makes any difference.
Just curious, am I the only one who can defeat OnLock using the start button the first time it runs
Oh my! You're right! Following your procedure, I was able to start the start menu and run programs from the start menu without "Unlock" coming up. It took some play with timing of hitting the Start Menu button, but two times out of several I tried, I could bring up the Start Menu without "Unlock" coming up. And from there, I started playing Solitaire in one instance and Total Commander in another (both in my Start Menu), and both were fully functional.
I noticed too that when OnLock is running and the 6700 is off... when I turn it on, I can use my I.E. button (press & hold), which is assigned to Voice Commander to do whatever... make a phone call, get the time, etc, all with "Unlock" sitting in the bottom left hand corner.
I then decided to try the same experiment Haus did, but using the green phone key this time, but I couldn't get the phone to come up and defeat the lock. So, for my purposes, that's great, because my goal is to not accidentally make a phone call. Works like a charm.
Login
Panel
