Related
Is it possible to activate your lock screen by clicking on the sleep button? (Just like S2U2) At this moment I've got it the original way by holding the end call button. I hope there is a simple way to do that, maybe a cab. file?
I'm using a stock win 6.5 ROM.
Here, this should work. its better to install in main memory. once installed, it will appear in your start menu, which u can then configure to suit your needs.
Hope it helps, let me know!
rumz82 said:
Here, this should work. its better to install in main memory. once installed, it will appear in your start menu, which u can then configure to suit your needs.
Hope it helps, let me know!
Click to expand...
Click to collapse
I've got it running. Please tell me how to configure it to my needs. I want everything stock except that I want to auto lock my phone when I hit the sleep button or when it goes automatic to sleep.
Search for HKCU/ControlPanel/Backlight/ set Autodevicelockenabled to 1.
It's one of the first options, lock on standby. The problem with the reg edit is that it locks on backlight dim and uses the winmo call lock.
tried this but when i am using the camera or video, or playing a video it locks.
how can i avoid this.
There is a field that says 'DO Not Lock if runing' what do i write in this field?
Thanks
yasinism said:
tried this but when i am using the camera or video, or playing a video it locks.
how can i avoid this.
There is a field that says 'DO Not Lock if runing' what do i write in this field?
Thanks
Click to expand...
Click to collapse
Hi. Im not sure as i didnt use that option. but i think u may need to put the path of the programs or the name of the programme exe. Try it.
zimmicz said:
Search for HKCU/ControlPanel/Backlight/ set Autodevicelockenabled to 1.
Click to expand...
Click to collapse
All of that I can find in this program?
Ciedric said:
All of that I can find in this program?
Click to expand...
Click to collapse
For that you need a registry editor like total commandar or resco registry, also, SK tools comes with a registry editor.
I use Lock Device....Works very nice
http://forum.xda-developers.com/showthread.php?t=542482
Try this
I'm using something called AutoLock Screen v 1.7E. It just works, no reg tweakes or anything like that. It lockes the device when it goes to sleep, when you press the power button to turn off the screen, it even does in call lock... but I admit it would be nice if it actualy turned off the screen when in call rather then just locking it...
I recomed you use this version because the newest ones have the tendancy to double lock your device...
rumz82 said:
For that you need a registry editor like total commandar or resco registry, also, SK tools comes with a registry editor.
Click to expand...
Click to collapse
No change to do it with out Total Commander? Btw where can I get Total commander
smielek00 said:
I use Lock Device....Works very nice
http://forum.xda-developers.com/showthread.php?t=542482
Click to expand...
Click to collapse
Thnx, I'll have a look.
clutch16b said:
I'm using something called AutoLock Screen v 1.7E. It just works, no reg tweakes or anything like that. It lockes the device when it goes to sleep, when you press the power button to turn off the screen, it even does in call lock... but I admit it would be nice if it actualy turned off the screen when in call rather then just locking it...
I recomed you use this version because the newest ones have the tendancy to double lock your device...
Click to expand...
Click to collapse
I'll try, it sound great in my ears
TOTAL COMMANDER CAB FOR "Ciedric"
rumz82 said:
TOTAL COMMANDER CAB FOR "Ciedric"
Click to expand...
Click to collapse
Thnx
Btw I've choosen for AutoLock Screen v 1.7E it works just the way I want it. Thnx for the help!
Autolock worked great but after testing it sometime it went nuts time by time. Now I'm testing LockDevice and it is still running great
Here is an application to make specific programs(like ebook reader,SatNav etc) prevent standby when they are running. It will watch them even when they are in background, so be careful, if you just forget them running in the background, your phone will not go into standby. (v1.1 change: now you can disable background watch by checking "monitor active window only")
Installation:
1- Just install the latest cab file onto Device Memory and NOT Storage Memory.
2- You need .NETCF 3.5, if you don't have it, install it.
Usage:
1- If you will use background watching, find the executable name from Task Manager/Processes, drop .exe part, type it into textbox and click add. (AdobeReaderLE.exe -> AdobeReaderLE)
1a- If you want to watch only the active window (so that your battery doesn't drain if you minimize the whitelist app) Find the window title of the application (Either task manager/applications or just look at the title if it is not hidden) and insert it as above. (Adobe Reader LE this time) you can have both versions live together. There is one limitation to active application watching though, if the application doesn't report a window title in task manager, you can only background watch it. (e.g. htcreader)
2- if you want to remove a certain app, select its name and click remove button.
3- if you want to have KeepAwake open but still not active (to force into standby) click stop.
4- this app autostarts with each boot, if you don't like it, delete the shortcut under \Windows\Startup\KeepAwake.lnk
5- this app starts minimized. if you want to configure settings, select the icon one more time or switch to it using a task manager.
6- if you click quit, obviously the software quits and no more monitoring is done, so click X after configuring if you want it to monitor your apps.
7- if you want to turn off screen and lock keys (for listening to music maybe) you can click the lock button. If your app is running, the phone will still stay awake.
Tips:
1- You can map KeepAwake to a hardware button for easy access and screen locking.
Credits:
Thanks goes to Frank T. van de Ven for ProcessCE library.
Thanks a lot to DaveShaw for letting me use xdaShutdown application.
I'm pretty excited about this... I've been looking for something exactly like this to prevent specific standby times.
I hope it works with most of the applications I have in mind.
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
espaleena said:
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Click to expand...
Click to collapse
I haven't specifically tried MSN app, but I see no reason it shouldn't work.
Raadius said:
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
Click to expand...
Click to collapse
I think you need a task manager so that you can close apps. This one is for making certain apps prevent the phone go standby.
ozkaya said:
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Click to expand...
Click to collapse
I haven't given this a try yet, but any more additions are welcomed! This is something I've been looking for. I think it might be nice to give a way to put settings per application for standby perhaps (like some applications don't let the device go to stand by for 3 minutes, others are like 30 miuntes, etc). I think having't the screen off is a good addition, but keeping the device working is good, so things like voice recorder can work without having the screen on.
Seems to work well for IM services.
I haven't tested it completely for Opera and internet-browsing programs.
Nevertheless, this is a great idea.
new version is up..
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Zepiii said:
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
Click to expand...
Click to collapse
I thought about that but later decided that not many people would find it useful. if enough request comes, I will add it. In the meantime, you might just add an always running app like device or cprog into list manually when you want to keep it on always. or just minimize an app in the whitelist
Quider said:
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Click to expand...
Click to collapse
that's odd. I just tried and Youtube keeps itself open while playing a video for me even without this app. (Locks on the search screen) But still, KeepAwake seems to detect it when it is running. After installing have you clicked on the icon to run KeepAwake? Then minimized it by clicking on X? Have you tried another app, like Adobe Reader for instance? Is youtube minimized or active?
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
mdzepinajr said:
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
Click to expand...
Click to collapse
as long as you don't lock it yourself, yes, it won't be locked.
Very nice app...much thanks!
The app works for eReader on my Omni II running 6.3 One word of caution I have the x= app closed option turned on so the x shuts down keepAwake. It took me some time to figure out I was closing the app not minimizing it.
How would I go about disabling the standby while in a call? What's the name of the application I need to put in there? I'd like to use it so the sleep during call doesn't stop the call recording utility from working, but I still would like the screen turning off when keeping the phone at the ear.
Doesn't work on touch pro2
The software breaks error when we try to add software to the list, only with the program in background it goes to sleep anyways. It's a good idea, but not there yet...
Hi there!
I'm looking for an app that have the ability to prevent screen wake up when notifications arrive, but I also want the option to select which app that are allowed to wake the screen (like Hello or incoming call).
Does such app exist?
kartongsaft said:
Hi there!
I'm looking for an app that have the ability to prevent screen wake up when notifications arrive, but I also want the option to select which app that are allowed to wake the screen (like Hello or incoming call).
Does such app exist?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.lukekorth.screennotifications
I tested this app, but the screen still turn on. I thought it was Light Flow that caused this behavior, so I deactivated it and rebooted the device. Same problem.
kartongsaft said:
I tested this app, but the screen still turn on. I thought it was Light Flow that caused this behavior, so I deactivated it and rebooted the device. Same problem.
Click to expand...
Click to collapse
I dont know :/
Hmm, strange.
kartongsaft said:
I tested this app, but the screen still turn on. I thought it was Light Flow that caused this behavior, so I deactivated it and rebooted the device. Same problem.
Click to expand...
Click to collapse
Then,check the notification history and deactivate.
Even if you experienced same problem,I don't know too
Delete.
packyy said:
Then,check the notification history and deactivate.
Even if you experienced same problem,I don't know too
Click to expand...
Click to collapse
Check notification history? Deactivate?
kartongsaft said:
Hi there!
I'm looking for an app that have the ability to prevent screen wake up when notifications arrive, but I also want the option to select which app that are allowed to wake the screen (like Hello or incoming call).
Does such app exist?
Click to expand...
Click to collapse
if your device use 4.0+ android, then you go to settings, and manage apps, then click on aplication that you want to disable notification, and disable it. :/ I dont know any other way.
Paget96 said:
if your device use 4.0+ android, then you go to settings, and manage apps, then click on aplication that you want to disable notification, and disable it. :/ I dont know any other way.
Click to expand...
Click to collapse
But if I disable notification for an app, it will not push the notification in any form.
Thanks anyways!
Is there a way to prevent screen from waking up for an incoming call while in pocket?
My phone's screen wakes up inside my pocket and registers touches inside and receives calls without me even knowing. This problem is getting out of hands. Already tried the app 'Gravity Screen' and the closest setting I could get to is, screen WILL wake for an incoming call whether the proximity sensor is covered or not (phone's in pocket or not) and will only turn off screen if I uncover the sensor and cover it again.
Please help, experts.
N.b.: my device of rooted so any rooted method will also be appreciated
TIA
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
It hasn't been updated since January so I imagine its just an incompatibility
ragnarokx said:
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
Click to expand...
Click to collapse
I'm on stock rooted Lollipop and I'm running into a similar issue, but with face unlock instead of trusted device.
I have double-tap on Nova Launcher set to system lock using Tasker, and when I lock my phone using that, face unlock doesn't activate, and won't until I put in my PIN password and then re-lock using the power button.
chronostorm said:
I'm on stock rooted Lollipop and I'm running into a similar issue, but with face unlock instead of trusted device.
I have double-tap on Nova Launcher set to system lock using Tasker, and when I lock my phone using that, face unlock doesn't activate, and won't until I put in my PIN password and then re-lock using the power button.
Click to expand...
Click to collapse
I also tried locking my phone using Greenify instead of Screen Off & Lock, sam result. Perhaps there is a way to implement locking the phone that won't trigger the PIN to unlock? Or - and I hope this isn't the case - maybe there is no way to do this in 5.0?
ragnarokx said:
I also tried locking my phone using Greenify instead of Screen Off & Lock, sam result. Perhaps there is a way to implement locking the phone that won't trigger the PIN to unlock? Or - and I hope this isn't the case - maybe there is no way to do this in 5.0?
Click to expand...
Click to collapse
I tried messing around with screen timeout in Tasker, but it doesn't let me set it to 0 seconds (for obvious reasons, I guess haha), since I noticed that letting my screen time out seems to work just fine for triggering face unlock. The lowest I can set it to is 7 seconds though, if I remember right, which is a bit too high for a screen off function.
ragnarokx said:
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
Click to expand...
Click to collapse
Have the same issue, wait for developer to fix it.
Sent from my Nexus 5 using Tapatalk
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
I attached a pic of trying to do what you said in Tasker. When I run the task, nothing happens.
ragnarokx said:
I attached a pic of trying to do what you said in Tasker. When I run the task, nothing happens.
Click to expand...
Click to collapse
Have you installed the latest superSU beta? The previous versions had problems with the new security features introduced by lollipop. If you're not using this latest version my solution won't work.
spiderflash said:
Have you installed the latest superSU beta? The previous versions had problems with the new security features introduced by lollipop. If you're not using this latest version my solution won't work.
Click to expand...
Click to collapse
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Nothing against Screen Off and Lock as it's just doing what it's designed to do (and Lock after all) but this is a useful work around, thanks.
ragnarokx said:
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Click to expand...
Click to collapse
Oh yeah I forgot about that. First I tried it that way, but for some reason it didn't work, so thats why I use an external app But I'm glad it works for you!
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
Thanks you guys. Now I feel more at home with Lollipop with my old habit. I couldn't stand that smart lock was disabled when I used other screen off apps (then again those haven't gotten an update for a while too).
ragnarokx said:
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Click to expand...
Click to collapse
Yeah, there is no update yet from screen lock app developer regarding this issue ..
guess i have to use tasker trick ..
nsg86 said:
Yeah, there is no update yet from screen lock app developer regarding this issue ..
guess i have to use tasker trick ..
Click to expand...
Click to collapse
There probably won't be. The app is called "... And Lock". Technically, it's doing what its supposed to.
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
Was searching for a solution and i found this thread! Thanks a lot!
So no hope for people like me who don't use trusted devices/places but use trusted face? Because I think even tasker can't do that with trusted face unlock.
Also looking for a solution to this with trusted faces on lollipop.
Edit: If you're interested, you can follow the defect here: https://code.google.com/p/android/issues/detail?id=79735
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
m0d hipp¥ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow
Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!