Does anybody know of a lock screen that can be configured so that if the device is woken up by a text, or incoming call etc its locked BUT if i wake it up myself with the power button it ISNT locked? I need it to be locked if i receive a call or text when its in my pocket, but it really annoys me to have to 'slide to unlock' if i deliberately turned it on myself - it seems like an unnecessary step (am i asking too much do you think?).
Does anybody know if this is even possible, i.e. can the device tell the difference between how its woken up?
Related
Hi,
I am new to my XDA Orbit and am liking it very much. One annoyance (which is probably due to my ignorance) is that when I receive a text or an alarm goes off, my Orbit the device turns on / comes out of powersave mode and hence the screen is active whilst it is in my pocket (could be dangerous).
Is this the correct behaviour? Surely not, as input can be made from contact with your pocket? Is there a setting to change this behaviour? What does everyone else do?
Thanks in advance for any advice
Gary
Dosn't the XDA version have the screen lock like the mda?
It's a little padlock icon at the bottom of the today screen which says device unlocked, you tap it and the screen is locked from in pocket pressing, all buttons are locked too except the power button. when the device is switched on manually or by an event the screen is only active after using a 2 tap pattern, unlikely to happen by accident.
I must admit, I thought this was part of WM5 and not T-Mobile specific, strange it's not there on the xda.
It is possible to lock the screen before you turn the orbit off but it is a bit of a pain in the arse to have to remember to do that every time you turn off the device.
I was hoping for a program that would allow alarms and text message notifications without the screen becoming active.....
True, or you could re-train yourself to only do the screen lock and have the device auto-off in 3 mins or so, and it would be exactly the same.
Personally I find the screen wake up useful.
I can't say I've tried, but what happens if you go to Start - settings- Sounds & Notifications - Notifications
and go through all the text message received etc and untick "Display message on screen"??
http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
this battery status plug-in works on mda compact iii and it has a setting to lock the device on wake up so all you need to do is switch it off to lock it.
macguffin said:
http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
this battery status plug-in works on mda compact iii and it has a setting to lock the device on wake up so all you need to do is switch it off to lock it.
Click to expand...
Click to collapse
So it does!! I didn't notice. This is an excelent piece of software to have anyway, so this is just a double bonus, unless you are unhappy with the 2 screen taps required to de-activate the lock.
Hitting the lock icon requires the stylus whereas the power button does not - much easier and intuitive.
Will have a look into the alerts settings
Thanks for your help
Can't say I've had any difficulty hitting the lock (and definately not the unlock buttons) with my thumb, one handed, but see above for auto locking option, you 100% don't need to get the stylus to unlock.
i auto lock when the screen goes off and unlock with my thumb one handed, easy and intuitive
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
seraphic8x said:
I've been having an unusual problem with my dash running kavana's 6.1 rom. Occasionally, more often now than usually, upon locking my phone or letting it lock on timer (i haven't tested extensively), it'll be in "locked out" mode but without the button option to unlock it!
The two softkey options are Start and Contacts instead of just "unlock". it's as if the lock program got minimized and the phone's still locked but i can't get it to the foreground to unlock it? that's my theory.
The phone still seems to be running: the clock keeps running, i can wake it up from black screen with any keypress even though it'll still be in locked-out no backlight mode.
Also, it can receive calls and i can answer, talk, and hang up, but nothing else.
It's not that annoying in that i can take out and put the battery back in to fix it, but the problem is that i can see text messages come in while it's locked... then when i put the battery in, they're gone! it's infuriating! i have no idea who sent them!
Click to expand...
Click to collapse
Did you try a hard reset?
i was wondering if i could get sum people to tell me about ehir experiences with their locking/unlocking programs...such as, which ones youve used with success...im interested in knowing which ones use the least about of battery power, least amount of memory/ram...so on and so forth...any input wiould be greatly appreciated
specifically programs being used with the touch pro 2
I'm personally not a big fan of screen lock programs. I just think that for something as simple as locking the screen, the end-user shouldn't have to give up anything in terms of resources/battery life.
That's why I suggest sticking with the default WinMo lock.
I suggest either SmartLock or LockDevice to auto lock your device. Neither uses up any resources.
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).
I would really like to use the app, but there is a dialer conflict when getting incoming calls for boths apps. For example during an incoming call, I initially get HTC dialer. During the middle of the call, I get the original WM dialer. Do you have any suggestions to avoid this problem?
ohyeahar said:
pistou said:
I've perused the threads concerning both the locking apps you cite above, but both appear to have some issues (i.e. not everything working properly after the install). I'm specifically looking for a way to have the screen locked when the device is turned on, mostly because I carry the thing in my pocket (yes, with a screen protector) and want to be sure that if I should inadvertently bump the power button I don't end up calling friends overseas from the inside of my pocket. It doesn't appear to me as if the default locking app can do this (and not simply turn on the lock after a timeout) -- or am I missing something?
Click to expand...
Click to collapse
I've used both of those apps and it works fine for me. I have the exact same concern that you have. I don't want the device to wake because someone called and hung up after a second, thus making the screen susceptible to taps.
In both apps, you can customize how you want the lock mechanism to kick in. You can set it to lock when you screen goes off. My personal preference is to set it to lock on suspend.
Click to expand...
Click to collapse
Thanks: I've loaded lockDevice and so far so good
ohyeahar said:
I'm not really sure what you mean. If your device is locked (with the WinMo default lock), you won't be able to do anything (including making calls) without unlocking it first either via tap & slide (WinMo 6.5) or left soft key & unlock button (WinMo 6.1).
Click to expand...
Click to collapse
What I meant was that my understanding of the default WinMo lock is that it only locks after a specific period of in activity (which I don't want to happen) rather than after a suspend (which is what I do want).
I am currently using Go SMS for my txt application. I have it setup to show a popup of a received txt message over the lock screen so I can quickly reply. If I look at the txt, and reply or close it out right away, everything is fine, but if I let it sit for a few seconds, and the screen turns off, when unlocking the screen, the camera doesn't kick on for face detection. The workaround that I have found to get past the lock screen is to press the Emergency Call button, then the back button, then it allows me to use the pattern lock screen to unlock my phone. Has anyone else experienced this?
Just a little more background, I'm running the stock ROM, and the phone is rooted.
New GSIII user (just got it for Black Friday). 2 questions relating to the lock screen.
1. I read another post sort of related to this, but not really (almost the opposite in fact, he wanted the pattern or pin lock but had other issues). So, I have my lock screen set to unlock with only the swipe. Why are none of the advanced lock screen options available unless you choose a more stringent unlock option (like pattern or PIN)? Even with just plain swipe, I want a delayed lock after the screen shuts off, and and I want to st DISABLE the instant lock with the power button. Is there any way to do this without having to set a more stringent unlock method? And if not, what possible reason would the designers have for now allowing those other options without using a higher unlock method?
2. Not sure if this due to the lock screen, or a bug with Bluetooth, or a combination of both. I actually tried playing with a pattern unlock screen, but when I have that enabled I can't do Bluetooth voice dialing. I press the Bluetooth headset offhook button, and the phone wakes up, but then it just sits at the pattern unlock screeen and won't respond to voice until I unlock the pattern. But if I revert to just a plain swipe unlock, then the Bluetooth voice dialing works just fine (I press the headset button, phone wakes up AND listens for voice). Bluetooth voice dialing is a CRITICAL function for me.
Any help is greatly appreciated! Thank you!
I got hold of a Samsung tech via live chat on their web site and he confirmed that this is how it it works. I suggested these were poor design decisions and asked they pass along my request to ask that these be changed in a future update (of course, no gurantee that there will even be a future update, but I can hope).