I'm actually surprised you were able to do anything once you started solitaire. I will try that later, but for me as soon as I manage to bring a program up, then the lock engages.
OnLock is still incredibly useful; I agree with you that it prevents pocket calls, etc. which is the most important thing for many of us.
I am having trouble getting the cab file to install. I unzipped the file to a cab file, copied it over to my ppc6700 with activesync, double clicked on the cab file and it opens it instead of installing it. Any ideas?
When I first wrote this program, my intention was also to write a complete lock from the ground up that would allow me to incorporate more features and flexibility. That way I could do things like customizable deactivation. Someone has also asked if I could make it unlock with voice command. Perhaps some of these things are possible but my knowledge of PPC programming is not very extensive. I could probably do them if I wrote a complete lock, but my previous attempts have failed for lack of knowledge. I will try again though, and any help from someone with dev knowledge would be appreciated. Thanks.
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.
This is due to the design of the OS. When you hit the power button to turn the device off, the system sends out a notification just before the device powers down. There are simply not enough Processor cycles from the time my app recieves the notification to the time the device powers down. When the device powers back on, my app must wait to recieve Processor time again to actually lock. Threads with higher priority than mine are granted time first. So in that delay, you can get a key press in. So my method is not perfect, but it works much faster than the other method of starting at the 'power on' notification that most lock utilities use.
That being said, I did create another method where rather than waiting for the power off notification, my app installed a keyhook and detected immediately the moment you pushed the power key. This method had other benefits, besides the fact that it could lock before the device even turned off. I wanted to make it so that pressing and holding the power key would lock and turn the screen off. The reason that I chose not to is because win ce 5.0 imposed a systemwide limmitation of one key hook. For a while I couldnt figure out why my app worked in the emulator and not on my device. Then I found out PQZII also installed a key hook, and therefore my app couldnt. I did not want to write an app that may or may not play fair with other apps, so I abanoned that method.
About the solitaire incident , my guess is that first you selected solitaire on the menu, then it locked, then solitaire came up. Therefore, the solitaire window had the focus, and was able to accept input. Other random problems people have with still being able to use certain buttons when locked are problems with the built in lock. My app just invokes it. This is another reason why I want to write a full lock. That way, I could deal with these problems. But see above post. I will have another crack at it though. Any help would be appreciated.
Ok this time I am making lots of progress. I already have a proof of concept kind of deal. Right now, when the device comes on it locks the screen and keys, and deactivates when the windows key is pressed. Ive got lots of plans for it, so stay tuned!
All right - I installed the program, soft reset, turned the phone off, and it is now locked. When I use the regular screenlock I can unlock it using the left softkey. But the only way I can do that with the program installed is to soft reset and then the softkey lets me unlock the phone. I've read this thread about 20 times trying to get a clue. Help! - sheureka
Yes. It doesn't say "unlock" (like it does with the builtin program) and the left softkey does nothing. I've now uninstalled it, so I don't remember whether it just had the default "calendar" for that softkey or something else. But I think on the screen the only indication the phone was locked was the "lock" icon, and the "Device locked" next to it. So this isn't how it's supposed to work? - sheureka
Has anyone experienced random failures of the device lock to start with OnLock? I've just hard reset yesterday (re-building what I hope to be a stable setup) and I've noticed that at times no matter how many times I suspend and power up, the device lock doesn't engage. Then if I hit the device lock on the today screen it engages just fine.
The major change recently is that I've installed .NET Compact Framework 2.0 SP1 (that's service pack 1), which I installed entirely to main memory. It's frustrating, this program worked so well for a long time and now inexpicably it isn't working reliably. Is there a log file generated somewhere that I can use to try to troubleshoot what's going on?
Rally1, are you asking me? If you are, I'm not sure what you're asking. The version of .NET I was using is 2.0 SP1, I don't think there's a point release beyond that (if there is, I can look for it)...I'm not sure what the version of OnLock is...how do I find it?
Switching back to .NET 2.0 (no SP1) seems to be working perfectly again. Maybe going latest isn't always greatest.
I believe he meant what version of OnLock are you using. That is very odd that the new version of the framework should do this. The .NET framework should not affect OnLock.exe. It only runs the prefs panel. Perhaps with the new framework, it is not successfully starting up onlock.exe. Can you verify using a task manager (I attached the TrianglePowers app incase you dont have one) that when this happens onlock.exe is actually running?
I have been hard at work on the new version. This will be a Pro version of onlock. Think OnLock + mortsaver + more customizability. With this version, you will be able to unlock it using voice command, by pressing (and optionally holding) an app key, or even a certain combination of keys, kinda like a key password. You can choose a full screen display that blocks everything before you unlock it, something similar to the built in, where you can still see the screen, or something in the middle. You can also optionally assign a key to onlock and make it lock and turn the screen off, lock and turn device off, or just lock. I may post some screenies later.
I might also do a private beta if anyone wants to help out. It is completely stable and has never crashed from day one, but I do need some tweaking on its behavior (such as how it reacts to incomming calls) and feedback would help. Not at that point yet, but stay tuned!
jkinggrim, thanks - I was having other problems with the framework SP1 - it was causing another app that depends on having CF 2.0 to run erratically. I switched back to plain 2.0 and everything is working *perfectly*. So I think something either went awry with my install of SP1 - odd right after a hard reset! - or there's something weird going on with that service pack. Either way, I unfortunately can't devote time to delving into it more closely for the next couple of weeks, but I'm happy to report that with framework 2.0 it's great again, just like it always was.
Fantastic! I can't wait to take it for a ride. Hope I can help you out with this. I like testing good worth while programs out. Let me know and good luck with getting it done.
Does it work well even if the system password lock is enabled? I had some problems with the current one locking up if the system password locked during the startup cycle.
I just tested it with the system password set. Doesnt look like there are any problems. Of course, I will do more testing to be sure, but so far so good.
, my guess is that first you selected solitaire on the menu, then it locked, then solitaire came up. Therefore, the solitaire window had the focus, and was able to accept input. Other random problems people have with still being able to use certain buttons when locked are problems with the built in lock. My app just invokes it. This is another reason why I want to write a full lock. That way, I could deal with these problems. But see above post. I will have another crack at it though. Any help would be appreciated.
Fantastic! I can't wait to take it for a ride. Hope I can help you out with this. I like testing good worth while programs out. Let me know and good luck with getting it done.
Login
Panel
