Develop Bugs

NEW ROM - Password screen keeps appearing

I've installed the new ROM - so far mostly positive.
There is one thing driving me mad (no not the time on the today screen )
I leave the Jasjar switched on and connected / charging via USB. It stays on OK but keeps going back to the password screen.
What I want is to enter the password when ever it switches on. If the device stays on then I don't want to have to enter a password.
Anyone got any ideas???

do you have push mail setup?? if so it could be exchange policy enforcing it.

Carnivor said:
do you have push mail setup?? if so it could be exchange policy enforcing it.
Click to expand...
Click to collapse
No.

bjashton
If im correct in what im reading u want to turn off the normal password screen (1 with the big buttons) but just have a password as to say when you switch the phone on like a sim password

scotjen1 said:
If im correct in what im reading u want to turn off the normal password screen (1 with the big buttons) but just have a password as to say when you switch the phone on like a sim password
Click to expand...
Click to collapse
More information...
The problem is with the device password - NOT the SIM password which works as expected.
Under...
Settings -> Lock
I have ticked "Prompt if device is unused for" and set the time to 0 minutes.
In the previous ROM this meant that when-ever the device is switched off / on it would prompt for the password. However if the device stays on, for example when it's connected to external power then it just stays on - the password screen never appears.
In the new ROM after 1 minute without being used it reverts to the password screen. If you change the "Prompt if device is unused for" time as above then you can make this longer but then you lose the benefit of the switch-on password for this ammount of time.
What I want...
If you turn the device off it prompts for password when you turn it back on.
If the device stays on it never prompts for a password.
I suspect this is a side effect of the new security features that allow IT administrators to set a password timeout. They probably wouldn't want the user bypassing this by leaving the device on. However they have chosen what to me is a strange behavior for "0 minutes" with a timeout of 1 minute when the device is on.

bjashton said:
Carnivor said:
do you have push mail setup?? if so it could be exchange policy enforcing it.
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
even without push email ... once your administrator decides to install Exchange SP2 the e-mail sync won't work without password setup unless he manaully disable it (the default is simple PIN and time is 5 minutes).

Has anyone found a solution to this problem?
It's driving me nuts so I've had to turn the password feature off, but I'd really like to be able to turn it back on.
Thanks guys.

Hello everybody,
still no solution for this password problem.
I'm having the same problem since upgrading the rom on the tek 9000.
Even if you are using the TOM TOM the pda after about a minute it reverts back to the password screen.
Anybody??????????????????????
Ciao
Gigino

try the new orange or jasjar rom.

ks2k said:
try the new orange or jasjar rom.
Click to expand...
Click to collapse
I can confirm the Orange UK 1.30.90 WWE ROM contains the same behaviour :-(

gigino said:
Hello everybody,
still no solution for this password problem.
I'm having the same problem since upgrading the rom on the tek 9000.
Even if you are using the TOM TOM the pda after about a minute it reverts back to the password screen.
Anybody??????????????????????
Ciao
Gigino
Click to expand...
Click to collapse
yes, with tomtom it makes very hard to keep writing the password when you are driving.. There must be a solution!!

Hello everybody,
looks like nobody has find a solution to this problem yet.
Lets try to keep this thread open to see if anybody while come up with an idea.
Have a Good Easter everyone.
Ciao
Gigino

Not a complete fix but you could set the timeout to something like an hour.
I've got the password set on mine and don't find it too intruative with a decent timeout set.
I'd guess that it doesn't activate with certain apps as I've not noticed it locking with TCPMP though I may just end up pausing it before the timeout occurs and resetting the countdown.

Ok, after being extremely peeved about this bug I just found a solution that works fine, at least on my Universal:
http://www.pdagold.com/software/detail.asp?s=221
This official M$ password utility from the stone age of Pocket PCs works as it should. (Just remember to turn off the WM5-password lock before turning on the old password utility.)

Hello every1
after a lot of searching for the past month after I did the Rom upgrade on my Qtek 9000 I've find the solution to stop the Password screen to appear when you are using TOM TOM Navigator 5.
Go to this URL and you well find the instraction on how to do it.
http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=51293
Hope this well be helpful to someone.
I've been using it for a month now and it works fine.
Ciao
Gigino

That fix is too complicated for me.
Anyone else got a simpler solution?
This password reset is driving me nuts too!
If Windows Mobile 5 is supposed to be more secure, this just makes me want to turn the password option off - making it less secure!!

NEW ROM - £$%$^ Password screen keeps appearing
I have a fix! (I think)
1. Get a registry editor (I used minied of sourecforge.net, because its opensource, but there are many others available)
2. Go to the following key:
HKEY_LOCAL_MACHINE\Comm\Security\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}
- The value called AEFrequencyType will be 1. Change it to 2.
- Ensure the value called AEFrequencyValue is 0
Exit the editor and reset the device.
From now the device should only lock to the password screen when the power shuts off, as per pre-AUK2 behaviour.
Note that if you go in to the lock settings screen, it will try to change the AEFrequencyType value back to 1. Also, this will *not* work if you have an Exchange 2003 enforced policy for this setting active. The policy will overwrite it.

Mine says ASFrequencyType\0 (0x0)
Is this what I edit?
When I click to edit, I have options of 'New DWORD' or 'New String'
Not sure what to do now.
Any idea please?

Which registry editor are you using? It sounds like when you're clicking, it's trying to create a new value, possibly the default value for the key, rather than edit the existing AEFrequencyType value. Most registry editors have a tree structure of the keys in the left hand or upper pane, and the list of values in the right or lower pane. Make sure you have the value highlighted in the right or lower pane before you click edit.
First though, my apologies, one step I missed: Before you do the registry edit part, make sure you have set a password and set the device to prompt if device unused for 0 minutes in Settings -> Lock.
Lastly, can you clarify - is the ASFrequencyType or AEFrequencyType you've got in your registry?

hey "Mutant"....I just tried your method by changing the registry AEFrequencyType from 1 to 2, and it seems to be working fine, thanks a lot. Have you up to now, found any other problems?

HELP- Phone has changed autolock password

I have an XDA IIs recently upgraded to WM6.
I set it up so that after a few mins the password prompt pops up. This stops it from being knocked in my bag etc.
But a few days later and it has decided to change the pass for some reason? And I have no idea what it has set it to.
Is there anyway I can bypass the password screen?
Thanks!
EDIT: If it makes any difference, I guess the battery must've been low, because before the problem happened it had to do a full boot rather than just coming out of standby.

viewtiful said:
I have an XDA IIs recently upgraded to WM6.
I set it up so that after a few mins the password prompt pops up. This stops it from being knocked in my bag etc.
But a few days later and it has decided to change the pass for some reason? And I have no idea what it has set it to.
Is there anyway I can bypass the password screen?
Thanks!
EDIT: If it makes any difference, I guess the battery must've been low, because before the problem happened it had to do a full boot rather than just coming out of standby.
Click to expand...
Click to collapse
This is a known flaw in WM6. The only solution is to delete the hive. Soft-reset, hold the 2 buttons next to the volume slider until a menu comes up and select yes for the delete hive option. You do not need to format storage, but your registry (hive) will not know about the installed programs so you might choose to format storage as well. If you do both it will just like when you first flashed the ROM and you will have to re-install everything. After doing this do NOT use the built-in password option WM6 gives you, this will happen everytime you remove your battery or it goes dead. There are other locking programs out there that wok instead.
I use S2U2 as do many others to keep the phone "locked" when not in use, it does not use a password, but requires you to slide your finger across the screen to "unlock" it.

Thanks!
That seems to have done the trick.
Bit strange that microsoft haven't bothered patching WM6 to fix this...?
Oh well its sorted now anyways, so thats a relief

viewtiful said:
Thanks!
That seems to have done the trick.
Bit strange that microsoft haven't bothered patching WM6 to fix this...?
Oh well its sorted now anyways, so thats a relief
Click to expand...
Click to collapse
It's not been patched by microsoft because it's really not a WM6 problem, it's a 'running a massisvely hack version of WM6 on an old, unsupported device' issue.
Remember, the angel was released some time ago when WM2003 was the latest. These devices were never even considered as an option to run wm6. The fact that Helmi was able to make it run at all is amazing, and really shows just how good he is (I'm assuming Helmi is a male, I've actually never seen anything stating if Helmi has boy or girl wibbly bits ).

yeah...
WM6 really is not made for our BA, there's a thread here regarding your problem.
no sense of saying search first. but im glad someone helped you.
WM6 on our BA? Helmi did miracles to make that happen.
P.S.
actually it's Helmi not Hemli (pardon the correction)
and now that you said that it made me curious too. hmm.... ahaha...

SilverSamurai said:
P.S.
actually it's Helmi not Hemli (pardon the correction)
and now that you said that it made me curious too. hmm.... ahaha...
Click to expand...
Click to collapse
Bah. Thanks for noticing that. Post corrected.

Handsfree Dialing while phone locked

Hi Guys,
I've just ordered 17 touch pro 2's for work and I'm very impressed with them so far. Absolutely awesome phone. We've just got one issue which is the fact that when the phone is locked (we used centralised policies with exchange) you can't dial from our Parrots. The phone says you must unlock the device to allow bluetooth connection.
Does anyone know a way around this without taking the locks off of the phone which is a big no no. Tested it with a collegue's Omnia and it works fine.
You can replicate this issue by using the Bluesoleil dialer which is what I've been doing for testing.
The parrot receives calls fine, just can't make them he the phone is locked.
TIA.

Same problem
Hi there,
I'm having the same issue for dialling out via bluetooth whilst the phone is locked. The TP2 says it needs to be unlocked before answering the call.
There MUST be some registry key to change to prevent this "feature" ... none of the previous HTC phones I have had have had this problem.
Thanks in advance for any help!

i have the same problem, i installed s2u2, which solves the not being able to dial out when its locked, but it's not the most reliable solution.
i'd rather have it working like it did on my kaiser before this phone.
hope someone helps us out.

I tried out S2U2, but the problem is it's only a keypad lock, so plug the phone in USB for example and you still have full access to the device.
S2U2 also does not stop you sliding out the keyboard and pressing the mail button to read the emails on the phone, so this isn't a solution we can use, it's not even a compromise
Haven't had much luck with HTC support either. They are very quick to respond but don't respond with anything of value.

I just wanted to bump this thread -- I picked up a Tilt2 and have the same problem -- really annoying when trying to dial from the car and having to unlock (didn't have this issue on my Fuze).

Yeah this is the most annoying thing I have ever seen. There must be a way to turn it off. I use Ford Sync and really don't want to have to worry about my phone being locked or unlocked. Seems like this goes against all those phone laws. You are making me look at my phone first to make sure it isn't locked before I can safely dial.

Wish I had found this thread before I went ahead with getting a Tilt 2. Didn't have this problem with my Tilt.
Is this a WM6.5 limitation? Hopefully there is an obscure setting that I'm too stupid to find.
Cheers

... and I was just about to ask on this thread whether or not this was still a problem in WM6.5 but I guess I have my answer now.
It's definitely an issue in WM6.0

I contacted AT&T and they said to contact HTC.
HTC gave me this answer:
Thank you for contacting HTC Technical Assistance Center. I apologize for the length of time it took me to respond to your email. I understand how important it can be to use Bluetooth from your device when your device is locked. I will be happy to address the concern for you.
There is not a setting on your ATT Tilt 2 for enabling Bluetooth when your device is locked. When pairing Bluetooth with your vehicle your device must remain unlocked to use the correct functionality. I would suggest placing your device into hibernation mode and keeping your device in a carrying case.

Hi,
I have upgraded by TP2 with the offical HTC rom for 6.5 and installed my blackberry connect 1.06 client. Now, even with the BB lock enforced, as it was with the TP2 using 6.0 and it is working perfectly handsfree in my CAR, locked or not. Previously the TP2 with the stock 6.0 ROM wouldn't make calls when locked.
If people are reporting here that is didn't work in 6.5, then there must be a registry setting somewhere to enable or disable it.
I am just happy that I can make a call in the car, without having to pull over and unlock my phone.
If someone can give me a hint as to where in the registry to look I can compare some settings?

I have a stock AT&T Tilt-2, I loaded loaded "smartlock 1.7" to autolock the phone at power off and also when "in-call" to avoid random dialing. I don't use the PIN for locking.
I can dial hands free BT in my car and with headsets with no issues, power on/off whatever.
Maybe it'd disabled when locked with the PIN?

I am seeing the same issue with two of my users:
One is using a Verizon Wireless TP2 with MW6.1 stock ROM
The other is using an Unlocked HTC touch Pro 2, on the AT&T wireless network (not a Tilt2) with the HTC WM6.5 ROM upgrade.
The Verizon users is using Sync on his Ford Vehical. The other is using whatever system is in his BMW.
Both can pair with the car's system, but if the phone is locked with a PIN the user is not able to place a call without first unlocking the phone.
Has anyone found any information on this?

If MSVC is an option then it has the ability to dial while password protected.

Just noticed this has been bumped. I upgraded all of our phones to the standard Windows Mobile 6.5 from Vodafone when it came out a month ago and this problem is now resolved you'll be glad to know.
I've got 25 handsets currently working fine with no real issues. All the niggles that I had have gone away with 6.5 so it's definately worth the upgrade.
6.1 was screwed and no use with handsfree dialing if you use windows lock which we enforce on our exchange server.

Seems like every provider is a little different.
I have the AT&T Tilt 2 which came with WM6.5, AT&T support claims its a Microsoft and HTC problem. HTC claims its a Microsoft problem.
Anyone have a good support link to Microsoft to get this problem resolved?

Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.

Registry
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014

black88mx6 said:
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Click to expand...
Click to collapse
erenken said:
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
Click to expand...
Click to collapse
erenken,
Thanks for the info. The only item different on my 6.5 Tilt2 is that I also have a key "DontAskHfpCallFailOnDeviceLock"=1. Sounded very promising.
Unfortunately, changing this key to 0 and even deleting it doesn't make a difference: I still cannot dial via bluetooth while the phone is locked with a pin. I tried these changes both with and without a soft reset between.

mnunes:
Were you able to find a fix for this? I am in the same boat.

DaBody1 said:
mnunes:
Were you able to find a fix for this? I am in the same boat.
Click to expand...
Click to collapse
No, so far no luck. I can't say I've been looking very hard, though. It's one of those things I've started to learn to live with, as annoying as it is.

Tilt2 - Can't Bluetooth dial when device is locked

On the Tilt2 I can't Bluetooth dial the phone when it is locked. This was not the case with prior Windows Mobile phones. Is this a 6.5 thing? or a AT&T bloat thing? Is there a workaround?
Thanks,
Mike

I don't think it's a 6.5 thing. I think the ATT ROM has some strange Bluetooth program in it. It's a great deal different than the cooked 6.5 ROMs that I had on my Kaiser. I'm having some Bluetooth file transfer issues that I never had with the other 6.5 ROMs I've used...

I think its in the new Bluetooth-Stack of TP2, got the same issue with my german T-Mobile MDA V.
In Germany it's against the law to touch your phone while driving... Very anoying issue!

Here is another thread started back in July with the same issue.
http://forum.xda-developers.com/showthread.php?t=540502

I have sprint with the stock 6.1 rom. I also think that there should be registry key that allows this to work. It seems that some of the newer 6.5 roms allow this to work.
This only happens when locking with the built in Windows Screen Lock.
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.

On my Verizon HTC Touch Pro 2 with Windows Mobile 6.5 (Build 21874.5.0.83), I just stumbled on a solution that seems to work: Go to Settings:All Settingsersonal:Voice Command, uncheck Password Protected. After doing this, I was able to Bluetooth dial when the phone was locked.
On my phone, after I had unchecked Password Protected and Bluetooth dialed successfully with the phone locked, I was able to check Password Protected again and it keep on Bluetooth dialing with the phone locked. However, when I did a soft reset, I could no longer Bluetooth dial on the locked phone until I unchecked Password Protected again.

Big problem-phone lock problem.

I have a very big problem on my XDA IIs, i cannot unlock the phonelock even though i input the correct password.
-on my way home, my phone got emptied(battery empty). and then when i opened it, the problem began. please help me. what should i do?
-i have read articles stating that it is a common problem when the battery got emptied.
-my phone is an O2 xda IIs WM 6.5, serial 2.7.
-ty for the reply....

as i told you via pm already, there is no way to unlock the phone, once you set a password. the phone "forgets" the right password and would say, any password you put in, is wrong. that is why the only way to get rid of the problem is to re-flash the phone. a hard reset won't work, since that would be a terrible theft protection and also there is no way to backup any data, since even connected to the pc you are not given any access to the phone. that is why, in several threads here, and in several positions in my tutorial, i warn people, not to set a password in a cooked rom. you can do it in the stock wm2003 rom though, it works perfectly fine.
if you feel the need to protect your phone using a password, you need to look for 3rd party software to do that. i think spb has a nice app for that.