I hestitate to start a new thread to ask this, but I just spent 5 hours reading the Wizard forums and didn't find anything useful. So here goes . . .
I recently upgraded to Cingular_RUU_WIZARD_217_AKU22_Basic
(thanks, summiter). I'm happy with everything except the behavior of the password protection.
With the original ROM, I had it set (and don't remember what setting did it) so that I would only be prompted for a password when the device was coming out of standby mode (i.e. when I press the power button to turn the screen back on). Most of the time, I would put the device in "protected mode" by manually pressing the power button, but I also had "turn off after 5 minutes when running on battery" set, so if I left it sitting somewhere, it would go into "protected mode" in a few minutes.
With the new ROM, I've tried setting the "prompt if device unused for" setting to "0 minutes" (the setting I seem to recall I had used with the old ROM), which DOES cause the device to prompt for a password whenever I turn it on, but it also causes the password prompt to appear after 1 minute of idle time. If I use a longer setting, then I don't get the password prompt while the device is on, but when I turned off, and back on again, it doesn't prompt for a password.
I'm not dealing with a high security situation here. I just want a simple way to keep my kids and other prying eyes from accessing the PDA function, with a way for me to force it into locked mode, and some kind of time out for when I set the phone down and forget to lock it.
Is there a way to change my current ROM to get the old behavior? Is there some other program I should use instead of the one built-in to the OS?
Thanks.
Seconding this request. I've been looking for a solution to the same problem.
The password behaviour in the AKU2 ROMs are a real PITA - especially if you use SatNav without first switching off the password protection.
Unfortunately this is down to the implemenation by Microsoft so don't hold your breath for this to be "fixed".
Here's my solution so far:
I bought a copy of Pocket Secure 3.0 for $14
Website: http://www.TotalPocketPC.com
Support: http://www.4winmobile.com/-pocket-secure-support-vf25.html
I associated the progam with the Press and Hold voice button (I don't use voice recording), so when I want to force lock the phone, I just press and hold the button.
Using this program, I've left Media Player and/or TCPMP running in the background, "locked" the phone, and then carried it around in my case without any problems.
The "lock screen" displays battery level and a nice big clock. Since I don't wear a watch, 50% or more of the time, when I'm turning my phone "on" (i.e. switch out of standby mode), it's just to see what time it is.
Related
Hello all,
I just got my AT&T Tilt and love it so far, except for one major annoyance. When I press the power button, the device will turn the screen back on after a few seconds to a few minutes. The problem is when it's in my pocket, it can accidentally call people. My 8125 and 8525 did not experience this issue.
Any suggestions?
Thanks!
Button lock
It sounds as though the phone isn't set to lock all buttons except the power button when it is in standby. This happened to me last time I re-flashed my Wizard, and I couldn't figure out for ages why my battery was draining so quickly as well!
Settings > Buttons > Lock
Hmm, not seeing any option under Buttons or Lock. I do remember this setting from WM5. It does appear, however, that the buttons are not turning the phone on, it's just waking up even if I leave it on a desk.
You can add lock to the home screen
first press and hold the hang-up button so that it locks. Then just push the power button once. This puts it in standby.
There is a idle timeout for going on standby mode, but I can't find a setting to auto-lock.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
Are you paired to a Bluetooth device? I see similar behavior in my 8525 when in my car - the BT car kit does stuff which "wakes" the 8525
Richard
Try this leaving Google Maps On the Screen
Hi Guys,
I get this behavior when I have Google Maps running. It will even cycle the screen on and off a couple times.
nope and nope. just sitting on the today screen.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
I have the very same problem.
However, my girlfriend whom I also bought a Tilt for, her's doesn't do it.
We've installed all the same software too, so I'm a little puzzled.
start>settings>system> key lock. set it to lock all buttons except power.
rzanology said:
start>settings>system> key lock. set it to lock all buttons except power.
Click to expand...
Click to collapse
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
JonRick said:
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
Click to expand...
Click to collapse
Any number of applications might be starting the device, from weather apps to calendar, diary, time sync etc etc. For example, HTCs weather app will do it depending on how often you have it set to another example I came across from someone was TREO ALERTS that contains a script "refresh.mscr" and it was set up refresh time 30 seconds (this was turning his TyTn II on by itself).
Mike
hard reset and try again.
i'm betting that none of these suggestions were helpful (except the one about some application generating a wakeup event without any other visual notifications).
i was having the same problem, but i just tried to narrow down which running program was causing the events. it's one of:
* wireless manager
* messaging
* IM
my guess is IM; i'm going to test that out in a second.
well, it's none of the above. still seems to wake up randomly anywhere from 15 seconds to several minutes.
seems to happen more frequently when it's just been turned off.
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
dscline said:
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
Click to expand...
Click to collapse
i'm fine with using the lock function, but it still turns on randomly, using battery, and eventually unnecessarily yellowing the screen from backlight aging. my next approach is to check out the notification queue, using a notification cleaner app.
So i am having a similar problem. When i press the power button, the phone's screen turns off but when the keyboard slides, it turns back on... is there a way to make it so the keyboard sliding does not turn on the device? I think the keyboard slides around a little when in my pocket and i hate pushing 3 buttons to unlock my phone... thanks
I was having the same problem.
This is an issue with the ATT rom. Flash over HTC rom and you will be all set.
I have been having the same problem as well. I just installed this DeviceLock program:
http://forum.xda-developers.com/showthread.php?t=305402
If you enable the "Lock on Wake" option, the device will be locked when it wakes up, so the backlight stays off and you won't call anyone by accidentally hitting buttons.
Also, I ran across this related thread you might want to check out (basically talking about the same thing, but for the TyTn II):
http://forum.xda-developers.com/showthread.php?t=341419
Is there an application that turns the phone off via software rather than holding the power button down?
Ideally, with a small battery, it would be cool to have the phone auto power off at say 11:00pm time and then come back on at say 06:00am.
There are various apps than can power off the device (amongst other functions) - they are usually a secondary function of what its primary purpose is. One such example is SPB Pocket Plus - it includes various little tools, one of which is PowerOff which can be run from a shortcut, or scheduler etc.
I'm sure you'd have no problem getting the device turned off automatically at 8pm, but back on in the morning will be rather tricky given that the device is off hence unable to tell itself to turn back on!
Perhaps if you elaborate on what your ultimate goal is (i.e. why you want it turning off at night) then there may be another, better, way of achieving it.
Mathew
Thanks Mathew.
I dont take calls at night so its best to turn the phone off. With the battery not lasting that long it would be great.
I know that Sony Ericsson phones can turn on and display a reminder even when they are off. And I used to have a Siemens phone which had an auto-off function whereby I was able to set a time at which it would go off. A minute before the scheduled off time, a dialogue would appear on screen to say that the phone would turn off in 59 seconds. Then it would proceed to countdown the seconds. I had the opportunity to overide the auto power off if required otherwise when the countdown got to 0 seconds the phone would turn off. Cant remember if the siemens had an auto on function!
I think theres two ways of looking at this thread...
phone off - physically like a blackberry can do at a set time each day etc
or phone off as in the actual phone function. I think this is more suited to your needs and I really can;t think it would be that difficult to do for the average programmer.
You are in theory making something to switch "phone" on or off as you would in the communication manager
And then tie this in to an alarm style program
Okay, I'm having an odd one and searching around here for about three hours yielded me nothing, so I'm going to lay it down here:
The keylock on my Diamond fails to function at all. I've got the New SwiftBL Diamond ROM 6.0 installed since yesterday, and I think that is also when this started. I will also post this in the ROM's topic.
I checked the following settings:
- Settings, Long Press End Key is set to Automatically Execute: Lock Devie
- Settings, Key Lock is set to Lock all buttons except Power button.
I get no error messages, the only thing I see when holding the End Key is a short flicker of the screen, after which the Home Screen comes up. Do note that the keys are not appropriately locked.
I do not wish to use S2U2, and I am wondering why locking my device does not work. Anyone having any ideas?
you get this is you put a pin or password to protect your diamond and use one of the cooked roms, most roms have this bug now and i'm yet to find a fix other then to remove the password/pin completly
yeah, i have had this issue, its the rom. just let swiftblade know and wait for the next release
Able to lock (with issue)
Hi, I agree this is a bug. I configured my exchange account and have the lock policy enforced by my server. With the stock ROM there was no problem at all. But after the upgrade to the RUU_Diamond_HTC_WWE_2.03.405.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship ROM, the Long Press End Key no longer works to lock the device (the screen flicks).
I found a **workaround** (but not solution ). Long press the end key (as you normally would) and wait for the screen flick, press the power button (it have to be the first key touched after the screen flick). That's all, the device should be locked now.
Hi there,
Wondering if this is happening for all Diamond2 users or whether my playing around and initial configuration setup for the phone has somehow caused this situation.
When I hold down the Hang-Up/Home key it locks the screen. To enable the screen again I press the first Unlock button on the bottom left and then the Unlock button that pops up to re-enable use of the phone. This is of course normal.
However as my company forces Password protection as part of our Exchange Email policy, a Password is now enabled on the phone. Now holding down the Hang-Up/Home button locks the phone and instantly displays the Password screen (and not the Home screen with any information).
Being a previous Touch Cruise, then Touch Diamond user this has always driven me mad so I install SPB Mobile Shell so whenever I lock the phone it still shows the Home screen with all the information I want to see.
However on the Diamond2 this does not work and any locking of the phone simply displays the Password screen and no information. All I can do is enter the Password to enable phone use again.
I've installed registered versions of SPB Mobile Shell 3, and PocketShield but neither of them get around this problem.
Is anyone else having this problem? I'm trying to work out whether it's something I've done or whether it is all Diamond2's that demonstrate this frustrating behaviour? I've done a number of hard resets and gone back to scratch trying to see if I could get a combination that worked with this...
Appreciate any help so I can get this phone configured to my liking and actually start 'using' it. I know WM6.5 fixes this poor design in the OS.
Cheers.
Its an exchange thing...
The new version of Exchange 2007 forces all information to be hidden. As far as I am aware, there is no way anymore to show this info, especially as TF3D is so tightly integrated now.
Its pretty pointless having Exchange mobile policy on a device designed to protect the mobile information, and then being able to deactivate it, and show all that information you are supposed to be protecting when the device is locked.
BTW, the "versions" of wimo 6.5 that are floating around have been tampered with to remove this limitation. The official versions of ANY 6.1 rom will always hide that info when using exchnage mobile, if the group policy has restricted it.
You could always ask your sysadmin to disable it for your device.
Thanks for the reply and the info here.
I'm not trying to remove the password screen and that's fine with how it is intended to work.
But on my HTC Touch Cruise and my Diamond (both running 6.1 Pro) if I hold down the hang-up key it 'locks' the keys and dims the screen but still shows the home screen. Then after 15mins timeout I'm required to enter the password to access the phone again. During this the screen is always still displaying the home screen with the time, calendar etc.
But on the Diamond2 when I hold down the Hang-up key it locks the phone keys and displays the Password logon screen instantly. To use the phone again for anything, or to see the Home screen - I need to enter the Password.
This can't be the right way the phone is meant to work...?
Basically the 15mins timeout requiring password is 'instant' if I hold the hang-up key.
On my Samsung i600 which runs WM 6.1 I also have Exchange Sync with group policy enforcement of the password protection, but I can just chose "Unlock => Menu => Cancel" and the home menu shows.
But I can write back when my TD2 arrives and see if mine also does the same or if it is only yours.
mine does exactly the same
elmalote said:
On my Samsung i600 which runs WM 6.1 I also have Exchange Sync with group policy enforcement of the password protection, but I can just chose "Unlock => Menu => Cancel" and the home menu shows.
But I can write back when my TD2 arrives and see if mine also does the same or if it is only yours.
Click to expand...
Click to collapse
The rom did this out of box. I just flashed the HTC latest diamond rom onto my original diamond as well, and it doesn't show any info either.
thats interesting.
madstyle69 said:
Thanks for the reply and the info here.
I'm not trying to remove the password screen and that's fine with how it is intended to work.
But on my HTC Touch Cruise and my Diamond (both running 6.1 Pro) if I hold down the hang-up key it 'locks' the keys and dims the screen but still shows the home screen. Then after 15mins timeout I'm required to enter the password to access the phone again. During this the screen is always still displaying the home screen with the time, calendar etc.
But on the Diamond2 when I hold down the Hang-up key it locks the phone keys and displays the Password logon screen instantly. To use the phone again for anything, or to see the Home screen - I need to enter the Password.
This can't be the right way the phone is meant to work...?
Basically the 15mins timeout requiring password is 'instant' if I hold the hang-up key.
Click to expand...
Click to collapse
The answer there lies with the GPO triggering the simple pin lock from WIMO, rather than a 3rd party lock program.
A little progress...
Think I may have worked something out with this after a bit more playing around.
If I disable TouchFlo 3D and enable just the Device Lock option to show on the standard Today screen, then when I press Device Lock it locks the phone keys and dims the display (but still displays the Today screen info).
So the Device Lock can actually function on the phone as desired - however it appears that the ROM by default has the long press End key mapped to display the password logon screen (and not mapped to the Device Lock function).
Now it comes down to whether the long press End key can be re-mapped in the registry somehow to point to the standard Device Lock function and not the password screen.
I thought I had a way around it by mapping the long press Send key to Device Lock - however this button can only be mapped to installed applications (and not functions) from what I can see.
So any registry experts know of the key I'd need to modify to either re-map the long press End, or map the long press Send to the Device Lock function?
Resolved
Just closing the loop on this thread.
Zenyee Stay Unlock tool can be downloaded which resolves this problem.
It removes the need for a Password prompt for Exchange Group Policy (whilst not affecting the functionality of Exchange email working on the phone).
be VERY carefull!
madstyle69 said:
Just closing the loop on this thread.
Zenyee Stay Unlock tool can be downloaded which resolves this problem.
It removes the need for a Password prompt for Exchange Group Policy (whilst not affecting the functionality of Exchange email working on the phone).
Click to expand...
Click to collapse
Modifying the GPO at all on the phone causes a send home signal and can trigger the remote wipe! TRUST me on this.. i triggered the remote wipe and wiped my diamond and the storage card playing around with a few settings in the registry...
Juggles said:
Modifying the GPO at all on the phone causes a send home signal and can trigger the remote wipe! TRUST me on this.. i triggered the remote wipe and wiped my diamond and the storage card playing around with a few settings in the registry...
Click to expand...
Click to collapse
I've read countless messages from people using this tool on XDA and on other WM sites I've not yet read anything negative.
But thanks for the info in case I notice something unusual happen with the phone...
Hey everyone,
I encrypted my phone and installed MobileIron to get work email and calendar. Ended up removing it all and decrypting phone after a few weeks. Since then, my phone isn't locking when the screen times out. If can be sitting with a black screen, but soon as I touch the home button it's awake and ready for action. It seems to lock eventually after sitting for an indeterminate amount of time.
Where the heck is the setting to control how long the phone waits before locking (requiring swipe or pin, not just turning off screen)? I know when I had the phone encrypted I found it and changed it to like 15 minutes so I didn't have to enter my 8 digit pin every couple of minutes, but now that its decrypted I am either blind or that setting is gone....
Thanks in advance.
UnexplainedBacon said:
Hey everyone,
I encrypted my phone and installed MobileIron to get work email and calendar. Ended up removing it all and decrypting phone after a few weeks. Since then, my phone isn't locking when the screen times out. If can be sitting with a black screen, but soon as I touch the home button it's awake and ready for action. It seems to lock eventually after sitting for an indeterminate amount of time.
Where the heck is the setting to control how long the phone waits before locking (requiring swipe or pin, not just turning off screen)? I know when I had the phone encrypted I found it and changed it to like 15 minutes so I didn't have to enter my 8 digit pin every couple of minutes, but now that its decrypted I am either blind or that setting is gone....
Thanks in advance.
Click to expand...
Click to collapse
First thing is to go to settings > lockscreen > screen lock and change it to pin or swipe or something other than swipe until your device recognizes when you've locked it. If it starts locking with the pin engaged go back and turn it to swipe and see if it locks on its own again. Second I imagine that it locks when you press the power button to turn the screen off? Set your screen timeout to an obscenely high number so that you remember and get in the habit of locking the device by pressing the power button. This is just for habit because Android (the base system) engages the lockscreen when the power button is pressed and the screen is on. If you are running a custom ROM you could dirty flash to put system settings back to default and if you are on stock out of the box you may have to factory reset to get settings back to their default state. I know that last one is less than optimal, but if the first two options (changing the lockscreen type and locking manually) are not a good work around then you will either have to do the encryption routine again to see if it fixes it and if it doesn't then you may have to factory reset.