I am using the SX-66. The mortsaver works fine most of the times but it will lock up and i have to rest pda. Seems to lock phone up when i leave it alone for a period of time..about 30 mins.
Also does anyone know how to adjust time to have it automatically lock. I have made the record button lock it but i want to have it relock after i end a bluetooth call. It does not do that now so the phone is still activating commands. I would imagine it is something I have set wrong. Any help would be great
MortSaver is a tool that has become quite complicated and it has to deal with technical difficulties. From a user point of view I would like to see a different and a simpler approach. This may also avoid technical issues.
Currently, pressing the power button turns on/off the device. I find this very annoying and I prefer that the device is turned on/off (with flight mode on) when pressing the power button for two seconds. This is common on mobile phones. The power button, being pressed shortly, should be changed into the “mort button”, which is a configurable power button.
The “mort button” should have the following behavior:
Pressing the power button should turn the keys and touch screen off/on, display off/on, or device turned off/on (without flight mode). This is user defined. On an incoming call the device should wake up and the display should become active (light turned on). During an incoming call the power button will behave differently. On a wake up, the keys and touch screen are still locked and they can be turned on when pressing the power button. Pressing the power button will only toggle the keys and touch screen on and off during the call, nothing more or less. After the call (tapping the phone dialer away) the power button behaves normal again, that is, it can turn off/on the keys, touch screen, display, or the device. No countdown screen or any other popups are needed. Maybe showing an icon next to the “x” or “ok” tells whether or not the keys and touch screen are locked. Tapping the icon will bring you to the configuration screen of the “mort button”.
Holding the power key should turn off/on the device with flight mode on.
Has anybody tried OmegaOne's 1-Pass? I'm trying the trial version of the software and so far it seems to do as advertised on my Siemens SX-66 (Cingular). It locks my device buttons (it has different time intervals to choose from) and it enables a password based on user-defined timeframe . Here's the link: http://www.pocketgear.com/software_detail.asp?id=13462
It seems a bit steep at $19.99, but it might be worth it since it seems to keep my pda from running programs when I have it in its' case!
This app is almost perfect. if you want another app to do other things.. then go somewhere else!!! you are one person asking for alot, i don't want the features you are asking for, and besides mort is doing this for free.
The only way to make this app perfect in my opinion, is to make the display not come on at all when a hardware key is pressed. It should only come on when the user hits the right set button.
If you need help with this, i am sure you can talk to wei who made the program called screentoggle. That app is great, but it does not properly disable the phone edition buttons.
This app is almost perfect. if you want another app to do other things.. then go somewhere else!!! you are one person asking for alot, i don't want the features you are asking for, and besides mort is doing this for free.
Ever used a Siemens cell phone? They solved it nicely. You mean "This app is almost working". "Perfect" is a personal oppinion. I do not disagree with Mort's work, I just wrote some input. I do not go somewhere else, since this a forum where thoughts are shared. BTW. I did not ask too much.
Well, I'd love to do such things. Or rather, I'd love if they'd be build in. Hardware sliders for "hold" and "phone" would be the best solution imho...
But as it is, there are a lot of limits to me.
I can't detect whether the power button is pressed (well, at least not on all devices - some have still some remnants of WinCE 2.0 which enable it...).
I can't disable the touchscreen. Currently, I just show a fullscreen window, so the presses get to my application (and thus ignored) instead of doing somethiny you don't want. Microsoft does offer some methods to do it, but sadly only to hardware ventors... (That's why TPDisable exists for some devices)
I can't disable the phone buttons on some devices. That's another thing that's far too deeply coded in the system, and additionally highly device dependant, so even a system "hack" would probably screw up some devices.
There's no way to be informed about popup messages, I could only check for them in certain intervals.
Other programs (esp. games) can override the button remappings and draw directly to the screen.
Thus, MortSaver is the best I could do with all this system limitations. Vendors could do far better things...
Originally posted by Mort Well, I'd love to do such things. Or rather, I'd love if they'd be build in. Hardware sliders for "hold" and "phone" would be the best solution imho...
But as it is, there are a lot of limits to me.
I can't detect whether the power button is pressed (well, at least not on all devices - some have still some remnants of WinCE 2.0 which enable it...).
I can't disable the touchscreen. Currently, I just show a fullscreen window, so the presses get to my application (and thus ignored) instead of doing somethiny you don't want. Microsoft does offer some methods to do it, but sadly only to hardware ventors... (That's why TPDisable exists for some devices)
I can't disable the phone buttons on some devices. That's another thing that's far too deeply coded in the system, and additionally highly device dependant, so even a system "hack" would probably screw up some devices.
There's no way to be informed about popup messages, I could only check for them in certain intervals.
Other programs (esp. games) can override the button remappings and draw directly to the screen.
Thus, MortSaver is the best I could do with all this system limitations. Vendors could do far better things...
I do appreciate your awesome application.... I had a question about it. I don't know if this was discussed, but every once in awhile i get numbers on the screen like
410000102002420020001
The one last thing is there is an app called screentoggle by wei. Basically you assign a hardware button to this program and it shuts off the display. It also disables regular hardware buttons, but does not disable phone edition buttons. This would be an easy thing to ask wei to fix, but he does not have a device anymore and has stopped development. Since his apps are free, i don't think he wil mind sharing his source code with you. His app is like 7k.
What ideally would be great is to have an app that disables the display( turns off touchscreen) and locks all hardware buttons except the power button and the one assigned to lock/unlock.
So you would have an app that all though the phone is on, will have the display totally off and hardware keys locked so the phone cannot make calls or get screwed up. I have faith that an app like this can be created and i would be willing to pay for it.
To be honest, i was surprised to see the advanced features that you have put into mortsaver. It works excellent with my ipaq 6315. I do appreciate your time and generocity. Have a happy new year!!!
Originally posted by krad I don't know if this was discussed, but every once in awhile i get numbers on the screen like
410000102002420020001
They're just for debugging. There are some issues with some programs like SmartFilter when a call is done...
Quote:
It also disables regular hardware buttons, but does not disable phone edition buttons. This would be an easy thing to ask wei to fix, but he does not have a device anymore and has stopped development.
I'm afraid it's not an easy thing. I tried to do that myself. On some devices, the game API allows to catch the phone buttons (e.g. on MDA II), on others it doesn't - and that's with the same DLL! On those "other" devices, there's seemingly no way to access the phone buttons - at least nobody in the newsgroups and message boards I know could tell... It seems like the operating system handels them itself before there's a way to interfere.
Quote:
Since his apps are free, i don't think he wil mind sharing his source code with you. His app is like 7k.
I'm afraid he does basically the same as I do...
Maybe he could help with the power button. But I'm afraid that doesn't work on every device, too...
btw: You could combine the system's button lock with MortSaver. That way, only a combination of power and unlock button turns on display and buttons.
Well, and an incoming call. There's the phone button problem again...
Originally posted by Mort They're just for debugging. There are some issues with some programs like SmartFilter when a call is done...
I'm afraid it's not an easy thing. I tried to do that myself. On some devices, the game API allows to catch the phone buttons (e.g. on MDA II), on others it doesn't - and that's with the same DLL! On those "other" devices, there's seemingly no way to access the phone buttons - at least nobody in the newsgroups and message boards I know could tell... It seems like the operating system handels them itself before there's a way to interfere.
I'm afraid he does basically the same as I do...
Maybe he could help with the power button. But I'm afraid that doesn't work on every device, too...
btw: You could combine the system's button lock with MortSaver. That way, only a combination of power and unlock button turns on display and buttons.
Well, and an incoming call. There's the phone button problem again...
Same to you!
my phone buttons are locked properly with mortsaver. My other hardware buttons are the ones that bring the device on to the mortsaver screen. Being that the phone buttons are being blocked properly on the 6315, could you make a special flavor of mort saver, where the display does not come on at all when other hardware buttons are pressed? I don' t know if i am asking for to much.... could the hardware keys be mapped to do nothing... except the one set to turn the display back on?
thanks again for taking the time to make this awesome application.
Originally posted by krad my phone buttons are locked properly with mortsaver.
As said - that's device dependant...
Quote:
Being that the phone buttons are being blocked properly on the 6315, could you make a special flavor of mort saver, where the display does not come on at all when other hardware buttons are pressed?
Not really. When the program is notified that a button was pressed, the device is already powered on (or rather woken up from standby) from the system.
There are only two possible workarounds: You could either use the systems button lock additionally (which leads to a power+unlock button combination) or you shorten the timeout time to one second (I'm not sure whether zero works).
But besides of that, I wanted a visible feedback, because otherwise it's hard to tell whether the device is off or if only the screen was turned off by MortSaver. And on devices that don't turn on with every button, you need some time between power on and unlock button...
Quote:
I don' t know if i am asking for to much.... could the hardware keys be mapped to do nothing... except the one set to turn the display back on?
As said - I can't keep the buttons from waking up the device, that's far too deep in the system. I could only shorten the time until the device or screen is turned off again.
Attached is a new beta of MortSaver. It now features a battery and phone signal display, and some bugfixes (esp. the "emergency exit" by powering on the device twice within 10 seconds now works).
I've also tested the program with SmartFilter. It worked fine for me, but maybe that's only because of a new SmartFilter version or device dependencies...
Originally posted by Mort As said - that's device dependant...
Not really. When the program is notified that a button was pressed, the device is already powered on (or rather woken up from standby) from the system.
There are only two possible workarounds: You could either use the systems button lock additionally (which leads to a power+unlock button combination) or you shorten the timeout time to one second (I'm not sure whether zero works).
But besides of that, I wanted a visible feedback, because otherwise it's hard to tell whether the device is off or if only the screen was turned off by MortSaver. And on devices that don't turn on with every button, you need some time between power on and unlock button...
As said - I can't keep the buttons from waking up the device, that's far too deep in the system. I could only shorten the time until the device or screen is turned off again.
Attached is a new beta of MortSaver. It now features a battery and phone signal display, and some bugfixes (esp. the "emergency exit" by powering on the device twice within 10 seconds now works).
I've also tested the program with SmartFilter. It worked fine for me, but maybe that's only because of a new SmartFilter version or device dependencies...
Once again, i do appreciate your awesome work with this app. It is by far the most valuable app for my ppc phone.
I do understand what you are saying regarding the hardware buttons and the such.
On the hp 6315, i have to keep the device on all the time due to my bluetooth headset.
After installing mortsaver i did as you suggested and made the timer go down to 0.. but that didn't work, so i keep it at 1 second.
One last favor i ask, can you make the choice for the clock to display 1:00pm or 13:00 hours. If this option is in the program, i apologize for not seeing them. thanks again.
Originally posted by krad Once again, i do appreciate your awesome work with this app. It is by far the most valuable app for my ppc phone.
Thanks... Even I didn't expect it to go that far. I just wanted that damn thing to keep the display off...
Quote:
I do understand what you are saying regarding the hardware buttons and the such.
OK. I just wanted to make clear where the problems are located...
Quote:
On the hp 6315, i have to keep the device on all the time due to my bluetooth headset.
Oh, that makes using the system's button lock "a bit" difficult...
Quote:
After installing mortsaver i did as you suggested and made the timer go down to 0.. but that didn't work, so i keep it at 1 second.
One last favor i ask, can you make the choice for the clock to display 1:00pm or 13:00 hours. If this option is in the program, i apologize for not seeing them. thanks again.
I'll add those two next week (i.e. on/after 10th of January). I forgot to copy the latest code of the options program from my office PC (where I do some small modifications during noon break or long builds in the background...) and having vacations until then...
Btw, I'm also planning to add a "custom text" option, so you could show e.g. user informations on the MortSaver screen.
(Btw II: After that's done, I'll probably release V2.0...)
The attached beta fixes some minor display bugs. In certain circumstances, no clock and 100% phone and battery were displayed...
Hey Mort,
I just downloaded that last beta version. I have an ipaq h6315 and when I activate your program, it does exactly what it's supposed to do. The catch is that when I turn it back on, it tells me I have 5 seconds to press any button, pressing any button just resets the timer. (ie: 5,4 [press button] 5, 4, 3, ...).
Last edited by parisbarman : 01-04-2005 at 03:52 PM.
Originally posted by parisbarman The catch is that when I turn it back on, it tells me I have 5 seconds to press any button, pressing any button just resets the timer. (ie: 5,4 [press button] 5, 4, 3, ...).
Oh... I have to check that...
Until then, get the MSOpt program (I think the latest version was in the b6 download) and set the deactivation button to anything but "activation button".
Or simply assign MortSaver to any application button in the system settings' buttons dialog.
I was experiencing the same problem with the latest version so I went in and deleted the file. Now when I turn off the phone and a call comes in the screen shows "Notification Error - Cannot execute\My Documents\mortsaver.
Where can I find the file to delete that send this notification to the screen.
Let me know when you get the other issue fixed and I will reload the program again.
Hi Mort I also would like to say this is a great program. I have one request if possible, I have the latest mortsaver set to activate when i switch my O2 XDAIIs on, is it possible to press once on the power and a subsequent press disable mortsaver and take you direct to the today screen without having to dismiss the notification window? That way i can press once to get the time and batt status and with another press go straight to start using my device.
Another minor request, is it possible to have a separate countdown for the notification popup so you have a better chance of catching text message or other notifications. Thanks for all your hard work
Originally posted by jhensley Where can I find the file to delete that send this notification to the screen.
That's the windows system itself...
You'll have to copy and run MSOpt again, and uncheck the "Run at power on" option. (In later installation programs, I'll remove the notification on uninstall)
The other bug doesn't appear if MortSaver is assigned to an application button or a deactivation button is chosen in MSOpt.
Of course I'll fix it, but until then, it's quite easy to avoid.
Originally posted by efjay I have one request if possible, I have the latest mortsaver set to activate when i switch my O2 XDAIIs on, is it possible to press once on the power and a subsequent press disable mortsaver and take you direct to the today screen without having to dismiss the notification window? That way i can press once to get the time and batt status and with another press go straight to start using my device.
I think you're talking about the "emergency exit", right?
Well, I can't get when the power button is pressed, I only get notified when the system is powered on. I.e., you'll always need to press the power button at least three times (power on, power off, power on) within 10 seconds.
I might offer options for a user defined timespan for the "emergency exit" and to supress the message in later updates.
Quote:
Another minor request, is it possible to have a separate countdown for the notification popup so you have a better chance of catching text message or other notifications.
If you mean the timespan between power on and activation of MortSaver: I'd like MortSaver to be activated as soon as possible, to avoid that other programs are run or other unwanted things happen if the device was powered on by accident (notification, s.th. in the pocket, ...).
OmegaOne 1-Pass
Login
Panel
