Here's the current beta version of MortSaver. The contained executeable is for the desktop PC.
Please be aware the "Switch off" option might still cause problems on some devices, so if you want to test it, better do a backup first... (though a soft reset should do it on most devices with problems...).
I recommend installing in the main memory, otherwise the power on notification might not work.
Under the settings, you can decide if you want it to lock during incoming or outgoing connect. If you do have it lock, it should lock after 5 seconds (whatever you set it to) and then come on again when you hang up (because you hit a hardware button), but turn off itself.
Well having tried PhoneLock and MortSaver 1.1 I have to say that MortSaver is the clear winner. PhoneLock frequently crashed the device. I'd just LOVE to see MortSaver auto lock the screen during a phone call. That would make it the perfect solution.
Originally posted by qtek9090 I installed the MortSaver 1.1 and i like it, but it drains off my battery muck quicker than the original lock.... anyone happens the same??
Unless you use the power off features, that's very likely.
The originial lock locks the buttons when the device is in standby mode (what WinCE calls "powered off"...), while MortSaver only turns off the screen and all programs keep running (that is, until the power off timeout of the system gets active).
In the new beta, there's a option to power off the device with activation of MortSaver. But I still don't know if the power off works fine by now. In older versions, there've been some problems to power on afterwards. In most cases, a soft reset works, but a backup might be handy...
Originally posted by qtek9090 After a few days testing, it remains the same, with mortsaver my battery goes in one day, with the original lock two days.... (normal use)
I'm using power off option and sometimes i've got the problem to switch on, only after clicking on power button i can bring up the phone again.
The Phone Edition seems to have two "power off" (standby) modes. If I turn off my MDA compact (I-Mate, HTC Magician) with the power button, the program receives a power on notification when it's turned back on.
But if I do the power down with the system routines, it doesn't.
I think the different battery drain might be connected with this, too.
I just don't know how to enter the "proper" standby mode...
OK, another beta...
I hope power down works better now. It seems like PE devices (and maybe some others?) ignore the power off command when the screen is off. In the former versions, I did turn off the screen in any case, and afterwards optionally the device.
Additionally, if the display state can be detected, the usual countdown appears if the screen was turned on by a message or the power button. If not ("Disable screen off check" option), the screen is turned off (almost) immediately.
On some devices, the phone buttons still work though MortSaver is running. I hope to find a solution...
Mirko,
Your program now works perfectly on the iPAQ 6315. The last beta version is the one I used. I have worked with you via email on a few other issues, but I think you have worked out all the bugs. I promised to send you a donation and now you have earned it. You should receive a donation shortly if it's not there already.
One last thing to make it perfect. Could you add a function to automatically run mortsaver after so many seconds of inactivity?
Similar to a screen saver on a PC.
Originally posted by IronMan805 You should receive a donation shortly if it's not there already.
Yes, it's there, thanks a lot!
Quote:
One last thing to make it perfect. Could you add a function to automatically run mortsaver after so many seconds of inactivity?
Similar to a screen saver on a PC.
I don't know...
There is a system inactivity timer. I do reset it in my MortPlayer to avoid auto power off. But I don't know how to retrain the current inactivity time. The reset command is quite known because of the auto power off issue, but I have to do some research about whether there is a command that works on (at least almost) all devices to get the current inactivity time.
Besides, the screen saver in any case won't get actived if a program with "keep alive" option is running (like most media players).
Another problem is that Windows CE closes programs if the memory runs low. Thus, the screensaver timer program might get killed and the screensaver won't get activated...
I downloaded and installed your program on my iPAQ H6315 and it works great!
I just have one question: does your auto-power-down effectively place the device in standby (same as pressing the power button) or does it just turn off the LCD?
Because from what I have read, if the device is placed into standby (you can still receive notifications and phone calls) then it takes less power than if the LCD screen were just switched off.
Mirko,
Could the program run in the background watching for key presses. The program should not do anything with the key presses, it should ignore them and let the OS and other program function as normal. If it does not see a key or screen press for x seconds it will then run mortsaver?
Is the "built in" power off function a part of the operating system. The function I am talking about is located in Start / settings / system / power / advanced / "Turn off device if not used for ".
This is the feature I would like to emulate. Instead of turning off the device, it should run mortsaver.
Originally posted by Myrmidus I just have one question: does your auto-power-down effectively place the device in standby (same as pressing the power button) or does it just turn off the LCD?
If you enable "Turn off device on activation" and "Turn off device if lock is not removed after power on" in the options, the device will remain in standby mode.
If only "Turn off device on activation" is off, it will start with display off, but will keep power off once the device was switched off.
If only "... after power down" option is activated, only the display will be turned off after the device was turned on (even if this was done by notifications!).
Otherwise, only the display is turned off.
Originally posted by IronMan805 Could the program run in the background watching for key presses. The program should not do anything with the key presses, it should ignore them and let the OS and other program function as normal.
No chance. The OS sends key presses (and not to forget touchscreen presses!) directly to the active application. Only the application buttons can be "catched" from another program, but even there can be troubles with other programs which want to do that.
I.e., I'd have to get somewhere in the system routines which send these messages, which is quite complicated, and probably very bad documented and/or device dependent.
Quote:
Is the "built in" power off function a part of the operating system. The function I am talking about is located in Start / settings / system / power / advanced / "Turn off device if not used for ".
That's the one I was talking about. Many applications do reset the "idle timer" to avoid this (e.g. it would be quite stupid if you want to use the PPC as MP3 player, and it turns off before the first track is finished...). But I don't know if/how it's possible to read the current idle time.
It's not possible to replace the "power off" with an application.
Originally posted by Mort If you enable "Turn off device on activation" and "Turn off device if lock is not removed after power on" in the options, the device will remain in standby mode.
If only "Turn off device on activation" is off, it will start with display off, but will keep power off once the device was switched off.
If only "... after power down" option is activated, only the display will be turned off after the device was turned on (even if this was done by notifications!).
Otherwise, only the display is turned off.
Excellent, thank you. It seems to be putting itself in standby, which is very good.
One problem though, is when brought out of standby by a telephone call, I can't seem to shut down MortSaver by hitting the trigger button... it just keeps flickering in the foreground, and I can't even answer the call!
It seems to do it no matter what the "off-screen check"'s state is in the configuration.
Originally posted by Myrmidus One problem though, is when brought out of standby by a telephone call, I can't seem to shut down MortSaver by hitting the trigger button... it just keeps flickering in the foreground, and I can't even answer the call!
It seems to do it no matter what the "off-screen check"'s state is in the configuration.
Strange... The countdown should appear, and thus disabling MortSaver with the assigned button should be possible...