Since I developed Stay Unlock two years ago, it had received numerous feedback. I had also started the habit or was it a hobby, of developing small software utilities to do stuff that default Windows Mobile does not provide, e.g. Bluetooth Notification hack, and most recently LED notification. From applying my knowledge of Windows Programming acquired 10 years ago in Windows Mobile development, I have also finally decided to take the opportunity to explore C# and .NET programming. For sure, these development toolkits make development life of a Windows Programmer much easier, as compared to say 10 years ago. You always learn something new but it is also important that you know the fundamentals!Anyway, inspired by the comments from Stay Unlock users, I have decided to pull forward the upgrade effort which I had originally planned for during my year end vacation (now it looks like I can take a good break in December!). It took me a day, and I’m hoping that it will be useful for existing users of Stay Unlock, although I know during the last one year, many variant of Stay Unlock had surfaced. Anyway, here’s what you can expect from the new version of Stay Unlock
- Supports both Smartphone and Pocket PC Phone platform (WM5.0, WM6.0, WM6.1)
- Stay Unlock will always run in silent mode, and will never prompt. A log file is created instead.
- Stay Unlock now has a separate configuration tool, to support the following options
- Turn on/off Stay Unlock, i.e. override security policy enforced by your Exchange IT admin
- Always Stay Unlock
- Overriding Timeout setting
- Once you save your setting, the tool will prompt you if you want your running instance of Stay Unlock to reload this setting
- Stay Unlock will also allow override of time out value enforced by Exchange Server. This will address situation whereby users wants the device lock function but prefer a longer time out threshold value than what’s defined by their IT admin
- Stay Unlock will also default the timeout to 24 hours, when you set “Always Stay Unlock. There are technical and security reasons behind this implementation, instead of completely disabling device lock function. However, you can still turn off device lock by going to Settings > Personal > Lock, and turn off the checkbox “Prompt if unused for”. Stay Unlock is not responsible for your action to unsecure your device!
Stay Unlock Download Links
Click Here for WM5 PocketPC Phone, WM6 and WM6.1 Professional platform
Click Here for WM5 Smartphone, WM6 and WM6.1 Standard platform
If you appreciate my work, please feel free to donate your token of appreciation by clicking the icon below
Posted by janos on December 29, 2009 at 9:50 pm
Great app, but would be usable only with
- preventing from the encryption policy
- preventing from the signed app install/run policy
- preventing from some additional policies (disabling camera, wifi, etc. – configable custom reg keys to set?)
R, Janos
Posted by janos on January 11, 2010 at 11:56 pm
I got a custom profile so it woks as expected.
…worked as I moved to WinMo 6.5.3. I can not start the stayunlock app and the config all does not save the configurations – every start I got all of the option unchecked.
Do You have any idea what went wrong – or the 6.5.x is not supported?
R, Janos
Posted by janos on January 12, 2010 at 2:45 am
Creating the reg keys manually helped to run the app. Now testing with 6.5.3
R, Janos
Posted by janos on January 12, 2010 at 5:36 am
works great!
Posted by eddietainer on January 28, 2010 at 6:19 am
can you give directions for installation on windows mobile 6.5? You are talking about registry keys..where can ik find those.
On other forums I found that the policy is changed back after a hour of a few hours inspite of changing the registry keys. Do you experience the same problem??
Posted by eddietainer on January 29, 2010 at 7:18 am
Is it possible to make the tool also compatible for windows mobile 6.5???
I loved the tool on samsung omnia !!! Realy great!!
But now with my new HTC HD2 and windows mobile 6.5 is does not work..
What have I tried:
-I have tried with .NET CF3.5 (and made sure it ran with corect version of .net).
-I have tried manualy editing registry.. and did not work. (sorry for my comment before this one…)
-And..then fact stays that when manually altering registry the settings are reset after one or more sync (or a max of 24 hours)
Posted by zen on January 31, 2010 at 4:42 pm
sorry, I’ve been busy and couldn’t find time to work on this. I have my doubts about the compatibility issue with WM6.5, because they are all based on the same WinCE kernel afterall. You may want to elaborate what went wrong, the UI control panel crash, the background application not running, etc?
Posted by janos on February 1, 2010 at 2:10 am
Hi eddietainer !
It works fine on HD2 with both 6.5 and 6.5.3.
Try this:
- install the app
- check whether the reg keys created, create manually if not
- start the app (not the gui but the daemon) if not running
- check if the app stays running (with taskmanager->view->processes)
- check if the link is in the start folder, put the to auto start after reboots
- try to change the reg key manually and see if the app resets back the expected value.
R, Janos
Posted by eddietainer on February 1, 2010 at 8:26 pm
Stay unlock and windows mobile 6.5:
I received an error message (see in my entry below) when saving the settings, but the settings are saved and after soft reset the application does it work and my exchange plocy is bypassed.
And again I’m very(!) happy with stay unlock. Many thnxs
Steps:
1. installed StayUnlock.
2. configured stay unlock:checked all three boxes in the configuration screen, but only checking the middle box (always stay unlock) also does the trick.
3. I received error messages when saving the setting:
The error I receive when saving changed settings is a Win32 Exception at
System. Diagnostics.Process.StartWithShellExecuteEx()
System.Diagnostics.Process.Start()
Stay_Unlock_Config.Form1.menuItem1_Click()
System.Windows.Forms.MenuItem.OnClick()
System.Windows.Forms.Menu.ProcessMnuProc()
System.Windows.Forms.Form.WnProc()
System.Windows.Forms.Control._InternalWnProc()
Microsoft.AGL.Forms.EVL.EnterMainLoop()
System.Windows.Forms.Application.Run()
Stay_Unlock_Config.Program.Main()
4. The phone or OS or any application does not freeze at all. Just teh error message. And the settings still have been saved.
5. Soft restart device
6. StayUnlock has been added to your Startup folder and works fine.
Note 1: I did not had to change registry settings.
Note 2: I have .net Compact framework version 2.x and 3. installed. With a application found on modaco or xda-forum and called “.net configuration” I can set per application the version of .net CF I want to use. Stay unlock uses version 3.5.
Note 3: is it possible that some registry paths in windows 6.5 are bit different then windows 6.0??