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!
Er, which settings do you have?
Esp. the power off options and which button do you use for deactivation?
I just replaced my iPaq h6315 with a imate PDA2K. I can't even begin to speak of how much better this device is.
I installed your latest beta and it works great. I can not find any bugs.
I have a slight problem, the PDA2K has an issue when the bluetooth headset is linked to the device. For some reason the device turns itself on periodically.
This is where mortsaver could come in. Mortsaver works properly and catches when it turns on, but it does not display the count down screen. It displays a screen very similar but it does not count down. It is the same screen that comes on if the power button is pressed when mortsaver is activated.
So I think this is why you made the "disable screen off check" under the power menu. With this checked it now turns off the device when the power button is pressed and when the device automatically turns itself on. But it now causes problems when a call comes in. The screen flashes and it is difficult to answer the call. Basically I have to repeadedly press the deactivate key in order to catch it at the right time to deactivate it.
It looks like with the "Disable screen off check" causes the device to watch itself and turn back off. But the problem is it turns itself back off too quickly. Can this time be extended so it doesnt turn itself off so fast? Maybe extend it to 10 or 15 seconds?
This would allow enough time to deactivate mortsaver and catch the call. Do you think this could work?
Originally posted by IronMan805 This is where mortsaver could come in. Mortsaver works properly and catches when it turns on, but it does not display the count down screen. It displays a screen very similar but it does not count down. It is the same screen that comes on if the power button is pressed when mortsaver is activated.
It seems like the device is not turned off, but only the display.
Quote:
So I think this is why you made the "disable screen off check" under the power menu.
Kind of...
A lot of devices support routines to get the current display state (i.e. if it's on or off). For those, it's quite easy: If I detect an active display, I show the countdown, and afterwards switch off the display or device.
The problem with the others is: I don't have a chance to detect whether the display was turned on by the power button or a notification. So, if "disable screen off check" is active, I just turn off the display about every second, even if it was already off.
Quote:
But it now causes problems when a call comes in. The screen flashes and it is difficult to answer the call.
Yes, incoming calls are a really pain in the a...
There seems to be a conflict: Both the call window and MortSaver want to be "always on top" and both want to be the active window. So they both activate themself repeatetly.
Currently, it seems to be the only solution to "allow incoming call popups" (latest beta, phone settings in the options). With this, MortSaver will not activate itself as long as there's a call.
Drawback: the buttons and (unless you have TPDisable/Enable and activated them) the touchscreen will be active.
The only way to disable that, would be to replace the incoming call popup completely, but I'd like to avoid that...
Oh, and btw: On some devices the phone buttons will be active even if MortSaver is running (on some only if pressed a while, e.g. flight mode by pressing the red button). I tried to replace the phone application temporarily with MortSaver, but it seems like this only works after a soft reset, and I don't want to replace it permanently...
@ironMan
welcome to the PDA2K Users ... (well, mine's an Orange SPV, but taht's all the same)
the phone-keys on the pda2k do work even when mortsaver is active. an the latest betas (several). Earyler, they did still work, but the timeout to turn off the device after a button (which doesn't show the count-down screen) has been pressed, was much shorter. if this timeout is shorter, the phone-buttons, in order to make a call accidentially have to be double-klicked very quickly, which almost never happenes. (first click turns on the device, second click redials the last number, or if the phonepad isn't activated yet, it will first launch it and then the third click (or second double-klicK) will place the call).
the reason for giving it a longer timeout was, that sometimes the device totally freaked out and turned it self on and off all the time, which caused a strange flickering of all the buttons and stuff.. this all of a certain stopped and everything was okay agan... i have not really figured out, on what condition this happenes.. but it just happenes sometimes...
@Mort
allthough this freaking out of my device isn't probably a good thing, i still prefer it to the greater chance of repeating my last call, because with the longer timeout this often happenes. so that's why i am still using a very very old beta you've sent me earlyer (the first you uploaded here, IIRC). so if i may place a "feature request": could you please give us the choice of setting a long or short timeout (maybe just use a text field for the acutal timeout length to be entered, so everybody can experiment with it and try what suits their needs themselves.. ) this would make the newer betas more useful for all the PDA2K and similar devices.
There's a new beta version...
Changes:
- Activation on every power on
- Selectable timeouts
- Turns only off screen (instead of power) when ActiveSync is active
- Should keep on device/screen during call (maybe still buggy...)
- 2nd button option is working
- Removed "Action/fire button" for button 1, because there's a higher risk it's send to another window
- "Turn off device on activation" only switched off screen on some devices
This time there's no installation program, just copy the contained files directly to the device.
Be sure to deactivate "Activate MortSaver every time the device is switched on" before uninstall or downgrade, otherwise there'll be annoying messages on every power on...
i've tried version 1.1 and found out that it doesn't work too good with the phone edition. i contacted the autor and he wrote me that he doesn't have time at the moment but will somewhen update it..
i just realized it is now up to version 1.2.. so maybe thatone's better?
After testing the latest beta I think it works very well. Just for reference I have a PDA2K. I had a minor issue where the phone locked up when starting mortsaver, but only happened once and it was most likely related to something else.
For everyone else watching this thread, mortsaver works to combat the bluetooth power on problem. I have the latest patches from imate installed and use a Sony Ericsson HBH-300. With mortsaver activated, a call comes in I can via the headset without having to touch the phone. When I am finished with the call all I have to do is hit the multifunction key on the headset and the phone hangs up and mortsaver locks the phone again.
Originally posted by IronMan805 I had a minor issue where the phone locked up when starting mortsaver, but only happened once and it was most likely related to something else.
Well, there are problems with applications that access screen and buttons at low level, like some games.
I've implemented an "emergency exit" if you power on the device two times within three seconds.
But currently I can't think of an solution for an activated screensaver with disabled check: In that case, the power button only turns on the screen on some devices (which I can't detect), and there's no way (well, a hard one...) to turn off the device because the screensaver reactivates within a second.
Well, maybe I could do the countdown all the time (i.e. the screen is switched off every 5 seconds - or whatever you set), while the "put in foreground" still works (or not, with concurring applications) every 100ms. That way, there's at least a chance to turn off the device within those 5 seconds, and after the first power on, the countdown restarts anyway...
Oh, and there's a problem with SmartFilter (and maybe some other phone apps). It seems to modify/catch some phone notifications, so MortSaver won't be deactivated. I'm trying to work around that, thus the debug messages in the current beta.
Quote:
For everyone else watching this thread, mortsaver works to combat the bluetooth power on problem.
Well, not completely...
If bluetooth is active, the device can't be turned off. Only the display is turned off - even if you press the power button.
(At least with my device, but I think there's not much difference on others)
I had an idea that would make it easier for me to catch notifications. Can you make the countdown appear after the notification has come up? Currently when a notification comes in I hear the tone, pull out the phone and get to see the notification for probably a couple seconds. This is too short for me. I can not respond to snooze or dismiss in that short amount of time. Is the countdown active in the back ground, and this is why it turns off again? I have changed the powerdown time to 10 seconds, I should be able to see if this makes a change. If this is the case can you make a separate option that allows the countdown to be adjusted just for notification popups?
Quote:
Originally posted by Mort
Well, not completely...
If bluetooth is active, the device can't be turned off. Only the display is turned off - even if you press the power button.
(At least with my device, but I think there's not much difference on others)
This is not the case with the PDA2K. The power off (suspend) button can be pressed and keep bluetooth active. It stays active only if there was an device connected via bluetooth (ie Headset). If there is not active connection bluetooth is turned off. So in fact your program does help us PDA2K owners combat this problem. As I was typing this post I could see my PDA2K turn on, mortsaver was active so the countdown screen was active, and mortsaver turned it back off again.
This how ever was not the case for my iPaq h6315. Bluetooth would turn off when ever the device would turned off (be suspended). Needless to say I was not very impressed with that phone. The PDA2K is ten times better.
Originally posted by IronMan805 If this is the case can you make a separate option that allows the countdown to be adjusted just for notification popups?
Sorry, no chance. I can't find out whether there's been a notification (except for calls, because there's an extra telephone API). I only get informed that the device was powered on. If this was done by a button or a notification makes no difference.
(The "enable popus" option only supresses the "always on top")
Quote:
This is not the case with the PDA2K. The power off (suspend) button can be pressed and keep bluetooth active.
I wouldn't bet on it... The MDAc seems off, too. But if I use the remote screen utility from Microsoft via bluetooth, I still can use the device...
Quote:
If there is not active connection bluetooth is turned off.
OK, that might be... I don't know how it is if a headset is paired but not active...
Quote:
This how ever was not the case for my iPaq h6315. Bluetooth would turn off when ever the device would turned off (be suspended).
Well, maybe this is what some users expect. I mean, some might think it's obvious that "off" is really off... I don't expect my PC to keep a connection if it's in standby...
I think an option would have been the better solution...
has anyone tried mortsaver on a sx66? i have tried it but can't really figure out the key thing or it may not be compatible. the os only allows 5 buttons to be mapped. any thoughts?
Originally posted by krussell has anyone tried mortsaver on a sx66? i have tried it but can't really figure out the key thing or it may not be compatible. the os only allows 5 buttons to be mapped. any thoughts?
I don't know about the sx66.
Just assign the MortSaver to a button in the system dialog. If you didn't use the installation programm, you have to create a link in the start menu, otherwise it's not listed.
has anyone tried mortsaver on a sx66? i have tried it but can't really figure out the key thing or it may not be compatible. the os only allows 5 buttons to be mapped. any thoughts?
thanks.
Works perfectly on a PDA2k, which should be hardware-identical to the SX66. I mapped the OK button to enable and disable MortSaver and it works great on my PDA2k!
The PDA2K is ten times better.
Login
Panel
