[APP]LockDevice [2009-08-26]. Ultralight app to lock after wakeup - Windows Mobile Apps and Games
change's log
V1.6 2009-09-11
Phone doesnt lock if there is a call in progress
V1.5 2009-08-26
1) Added an option to lock the device when a player (HTC player, WM Player, HTC FM Radio, etc) turns the screen off...
V1.4 2009-08-14
1) Added command argument. "lock". this will lock the device.
2) Added a link called "Lock Now" to lock now....
3) All the links are located in a folder called "Lock Device". (because there are 4 links and I dont want to fill the directory \windows\start menu (in your language) with many links
V1.3 2009-08-04
1) Commands support. The program LockDeviceGUI.exe supports 4 commands.
enabled -> Enable LockDevice
disabled -> Disable LockDevice
wakeup -> Run Mode: Lock on wakeup
screenoff -> Run Mode: Lock on screen off
Your can set one or two parameters. For example:
61#"\Archivos de programa\LockDevice\LockDeviceGUI.exe" disabled -> Disable LockDevice
61#"\Archivos de programa\LockDevice\LockDeviceGUI.exe" enabled screenoff -> Enable LockDevie and run mode set to "lock on screen off"
The installer creates out of the box two links in the system programs folder: EnableLock.lnk and DisableLock.lnk (The first with "enabled" parameter and the second one with "disabled" parameter).
V1.2 2009-08-03
1) The installer includes a little GUI program.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With this program you can configure how LockDevice must behave.
View attachment 211920
1) Enabled / Disabled
2) Work Mode:
2.1) Lock on wakeup. This is how works previous version. Pros: The program doesnt stay resident. Cons: The device must be "off" some seconds before windows really suspend the device. This time is longer with wifi active. So if you press power off and then power on quickly probably the device wont lock (because windows never suspended the device)
2.2) Lock on Screen off. Pros: The device is locked when the screen goes off so always works correctly. Cons: The program stays resident. Anyway the program is "paused" all the time so no CPU is used. the program stays sleeping until windows notifies it the screen is off. Then LockDevice lock the device and goes to sleep again
Please report any bug, suggestion, etc...
Dani
V1.1 2009-07-31
1) The device is locked directly using keybd_event. No sendkey.exe call . So smaller, quicker and no dependence of sendkey.exe configuration.
Initial post
Hi
Today I ve been searching for a very little program, not resident in memory to lock my device on wakeup. There are other ones but I didnt find one that isnt resident in memory.
So I ve done quickly a very small program that is notified by windows when the device is woken up, so no resident, and executes \windows\endkey.exe. So if you ve configured your end key long press to lock the device then your device will be locked.
I ve tested it in my Touch Pro 2 and works.
I really needed it and maybe other people are in the same situation.
Dani
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
EDIT: Oh ok... It doesn't work if you just turn it off then on immediately (which is a good thing). It had to be off for at least 3 seconds. Although there is a second delay before it locks after turning it on, which is ok I guess. Nonetheless, this is good stuff! Since it's the first one I've seen that is not memory resident (which makes me wonder.. how does it work??).
DaVince said:
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
Click to expand...
Click to collapse
I ve reuploaded it to avoid to hang a call
Do you ve \windows\endkey.exe ?
Is it configured to lock the device?
If you suspend the device and quickly press the power button then the device really isnt suspended so It doesnt work. The device must be screen off several seconds (5-10) to consider itself suspended.....
DaVince said:
It doesn't seem to do anything on my Touch HD. I tried turning off and on, nothing. Tried soft resetting, tried again. Nothing. I even tried running it from File Explorer on the LockDevice folder (Maybe it needs to instantiated or something), then tried turning off and on again. Nothing.
EDIT: Oh ok... It doesn't work if you just turn it off then on immediately (which is a good thing). It had to be off for at least 3 seconds. Although there is a second delay before it locks after turning it on, which is ok I guess. Nonetheless, this is good stuff! Since it's the first one I've seen that is not memory resident (which makes me wonder.. how does it work??).
Click to expand...
Click to collapse
Remember to install the new one or the program will hang a incomming call if the device is suspended
When the program starts the first time it register itself to windows to be notified when the device wakes up.
So when the device wakes up Windows execute the LockDevice.exe with an argument "AppRunAfterWakeup". Then the program check if there isnt a call in progress and then execute \windows\endkey.exe. Simple
could some people with other device than mine (tp2) to try if it works ok?
By now all works perfectly without a process spending ram/cpu
Tried the new cab on my Touch HD (Running WM6.1). Everything works ok so far.
Thanks a lot for this! I prefer this solution since this the simplest most efficient one that makes use of the built in Lock.
Nice. I thought about write an small resident process that monitors changes of power state to be more efficient but I prefer a process that only runs for a few ms when the device wakes up and then dies...
awesome app dude. well done. i was wondering though, since its possible to run an app on device wake up...is there a way to call upon an app when the device is set into suspend? cause even though the device's screen isnt on, stuff is still running, so what if a reg entry like the "on device wake up" is used as a "device suspend". that would get rid of the 1 sec wait on wake up and also still not be resident. i actually dont know if there is a way to do that, i dont fully comprehend it but it was an idea. cause it would be sick to be able to get rid of the 1 sec wait.
chronodrago said:
awesome app dude. well done. i was wondering though, since its possible to run an app on device wake up...is there a way to call upon an app when the device is set into suspend? cause even though the device's screen isnt on, stuff is still running, so what if a reg entry like the "on device wake up" is used as a "device suspend". that would get rid of the 1 sec wait on wake up and also still not be resident. i actually dont know if there is a way to do that, i dont fully comprehend it but it was an idea. cause it would be sick to be able to get rid of the 1 sec wait.
Click to expand...
Click to collapse
Hi¡
You can, but using a resident process. The feature I used in the "wake up" process isnt avaible in that way for "before going to sleep". A process can register itself to get notifications about changes in power state (From On state to suspended state)(RequestPowerNotifications api). So you could do some stuff when the device goes to idle state (screen off) but It requires the process to stay running in memory. Really It would be "paused" waiting for a queue event but spending one of the 32 available process in WinMo. Later I will upload a little process doing that. Just for try and play
Dani
Hi
I ve uploaded in first post a more optimized version. Now the program can lock the device by itself instead of rely on call sendkey.exe. So smaller and more efficient. To avoid the 2-3 seconds needed to be suspended to make it work correctly I ve done other version that monitors the power state. It locks the device when the screen goes off (instead of when the device wakes up) but it spend one process (WinMo only can run 32 process at same time). Question of tastes...
The reason about 3-4 seconds needed to wait between power off / power on is this:
When you press power off, the screen goes off (power idle state) but the system needs some seconds to really be suspended. Its in this way because windows notifies drivers about the power event and they must adjust their power levels....So if you press power off and quickly power on then the device really didt was suspended so It isnt really being woken up and the program isnt called by windows
Dani
I'm testing it on a Vogue tomorrow. Looks cool. I'll let ya know how it goes.
Thank you very much
Works well on the Vogue, though sometimes there seems to be a huge delay before the lock screen launches. It seems random though.
Just dropping in to say it works on original Touch Pro and Diamond.
Thanks!
Can't seem to get it to work on the HTC Snap. Anything I am missing here?
Once the screen is off you must wait 3 or 4 seconds before press power on to make it works. Only after that amount of time windows really suspend the device and triggers the wake up event when power on. This time is bigger if wifi is enabled. Tomorrow I will upload a version that locks the device when the screen goes off. It will be even smaller. But it has an inconvenient:will be resident....
Dani
does this lock also have a password lock to it?
Works great on my HTC ATT FUZE running the latest chrome rom 6.5 Thank you very much.
hi.
Tomorrow I will post a new version with 3 options.
1)work mode: lock on wake up (no resident but you ve to wait some seconds between power off / on to lock or lock when screen goes off.(works always but resident)
2)Lock or unlock when suspended and the phone rings. If the device is locked you can pick up/hang the call but you cant activate speakers, for example
3)Enabled / Disabled
Dani
tried it on my toshiba tg01 and it doesn't work,
just wanted to let you know.
cheers
Related
MY Wallaby screen keeps turning on... plz help
i don't know why but everytime i toggle the screen or push the power button to turn off the screen it automatically turns back on... does anyone know how to fix this... because it's wasting power....
start/settings "system" tab and iether "backlight" or "power" and mess with the settings. Also, make sure no programs are running in the backround. I use pocketnav burnt into my rom for managing running programs.... otherwise start/settings/system/memmory/running programs. Hope this helps!
I have the same problem This appears to be a bug in the WM2003 update. The PPC Phone turns itself on when it finds a new radio signal from a microwave tower. There are several work-arounds. The one that I use is called PowerCount. I use it to shut down my PDA and it locks up the device and when the device wakes up, it turns itself off again in 5 seconds unless you tap two pads on the screen. I found it at http://www.freefiles.dk/modules/myd...orderby=titleD. It lets phone calls through no problem. I hope this helps.
[Q] HD2 goes to suspend mode when keying pin at phonelock LockScreen after 13sec
Hi I seem to experience this problem on all HD2s. I activated the phonelock on HD2 and used a simple PIN for unlocking it. When I'm in the LockScreen, keying my PIN, the phone goes to suspend mode (or it seems like it, since the screen just blacks out and i need to press the power button again to see the lockscreen) after about 13 sec, everytime. This phenomenon happens only when phone is using battery power. It works fine when running on external power. Is there a way disable this issue, or extend the time it blacks out. I'm using the default WM6.5 rom 1.66.707.1 Please help, Thank you.
same problem with me ! any solutions ???
settings menu all settings system power backlight try increasing the timeout. also settings menu all settings lock see what options are in there. (mine won't start so i can't test it.)
I have tried all the settings i can find on the phone. I even tried changing Registry values that might be related to the timeouts. but still the same. The screen will black out even while you are typing, so this rules out all the timers that will suspend the phone when idle for too long. Please help, as this is a big issue for me. Thanks.
Getting rid of the Auto-Lock feature?
Is there any way to change a setting or something so that the phone never locks by itself? I hate when I leave my phone sitting for a moment and then it locks by itself. Also, when the phone is locked and then you press the home button, the screen stays on for ages - is there any way to change it so that it only stays on for 5 or 10 seconds (like an iPhone)? Cheers
You should be able to go into settings/personal password (or similar) & set "screen unlock security" to none/disable personal password security. Yes. Get an iPhone (You walked into that one). In all seriousness, it's been a while since I've run stock on my phone, but from memory you *should* (not 100% sure tho) set the screen timeout in the display settings to 15 seconds or similar.
Hmm there was no setting there... I've already got lock screen turned off but that doesn't make a difference.. Is there a way to do it with a custom ROM? I need to get a deodexed ROM anyway so I can run Jkay's theme.. any suggestions of which ROM to run?
In hyperdroid there is an option to change how soon the lockscreen activates after the screen turns itself off via screen timeout, as apposed to when you turn the screen off via pressing the power button. This may also be the case in newer stock roms, I am not sure. Its in Settings > Timeout (Under "Screen unlock settings") Also in Settings > Display you can change the scree timeout delay (aka how fast it auto turns off)
just put a long cooldown on the lock? swiping of an image is not that bad is it?
S3 Lock Screen Issues - Getting Stuck
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue? rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device. In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang. If the lock screen is hanging, pressing power will: (a) sometimes make the phone sleep again (b) make the phone screen kind of glitch/blip and then it takes input again (c) does nothing and the screen remains on and hung/frozen Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu). Now - I think this could be an app, but not sure. When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo. I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly. I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app. Other apps I have installed/running: Swiftkey X 3G watchdog Dolphin Browser HD ES File Explorer Winamp (locks without this running or running at all in lock screen mode, so that is not the issue) Real Calc Google Drive Facebook Alarm Clock Xtreme It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period. Thoughts?
So others may try to help or identify the possible cause / fix ....... What is your firmware version? Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9. But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us. Facebook 3G watchdog Dolphin Browser HD --i never use Google Drive
a fix that worked for me Steps to the solution that worked for me (so far) were to uninstall: 1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway) 2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3. I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though. I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings. While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems. Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer". It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy. LOOOL
Actually... My WIFI problem was not solved.... but I found a solution on another forum , which you can read below: I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around.... It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking. Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said: My WIFI problem was not solved.... but I found a solution on another forum , which you can read below: I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since. Click to expand... Click to collapse Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good.. This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said: weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue? rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks. Click to expand... Click to collapse This looks like a bug from wifi, i had the same problem and i found a fix: On the dialer type: *#0011# Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF. let me know if it solves ur problem
It worked!! douglasurbano said: This looks like a bug from wifi, i had the same problem and i found a fix: On the dialer type: *#0011# Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF. let me know if it solves ur problem Click to expand... Click to collapse This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said: I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this? Click to expand... Click to collapse Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings. Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?
[Help!] Device froze up, screen won't turn on and can't force a reboot. Please help!
Currently, my phone is coming across as useless other than as a torch. I am trying to turn on the screen of my phone, although nothing at all happens. Sometimes, if I'm lucky, it turns on and shows me my home screen background, however it takes so long to load that the screen goes back off again. I think this problem is due to an XPosed module in Sense Toolbox 6 that I enabled, that allows you to turn on the torch by long-pressing on the power button, however I am really not sure. Another likely possibility is a lag issue from the high amount of apps I'm running. At the moment I am considering restoring one of my backups because the problem is so bad (If I can get it to turn off, that is). Please help me!
falseascension said: Currently, my phone is coming across as useless other than as a torch. I am trying to turn on the screen of my phone, although nothing at all happens. Sometimes, if I'm lucky, it turns on and shows me my home screen background, however it takes so long to load that the screen goes back off again. I think this problem is due to an XPosed module in Sense Toolbox 6 that I enabled, that allows you to turn on the torch by long-pressing on the power button, however I am really not sure. Another likely possibility is a lag issue from the high amount of apps I'm running. At the moment I am considering restoring one of my backups because the problem is so bad (If I can get it to turn off, that is). Please help me! Click to expand... Click to collapse As long as you have ADB enabled you should be able to connect it to you pc via ADB and type "adb reboot recovery" this will reboot you straight to recovery where you can restore your backup or disable Xposed framework see link here https://seo-michael.co.uk/how-to-disable-xposed-installer/ for howto . I think you can even disable certain modules via ADB then "adb reboot" but I can't remember the detail you would have to google it. MiniBlu
i can feel the vibration and hear it turn on but i cant see whats on my screen