Glide users; try the following.
First off, turn on your lock screen. Now, open the keyboard to make the lock screen appear. Use the keyboard to mash in your unlock code.. Except, wait a sec!
The numbers don't match! I can't even hold down alt and use the top row keys for numbers.. this is the numbers to letters match-up:
Code:
1 2 3 4 5 6 7 8 9
W E R S D F X C V
And I haven't found the key that correlates to 0
Running Osimod so I am almost sure that the keyboard driver is goofed up somehow but I'd like to see if anyone besides me is having the issue that isn't running Osimod.
txterron said:
Glide users; try the following.
First off, turn on your lock screen. Now, open the keyboard to make the lock screen appear. Use the keyboard to mash in your unlock code.. Except, wait a sec!
The numbers don't match! I can't even hold down alt and use the top row keys for numbers.. this is the numbers to letters match-up:
Code:
1 2 3 4 5 6 7 8 9
W E R S D F X C V
And I haven't found the key that correlates to 0
Running Osimod so I am almost sure that the keyboard driver is goofed up somehow but I'd like to see if anyone besides me is having the issue that isn't running Osimod.
Click to expand...
Click to collapse
No problem with Rogers ROM. All the numbers are where they are expected to be.
Tried..working normally..
you have any idea why you are not able to use alt and use top row..
What is your default language input..
Sent from my SAMSUNG-SGH-I927R using XDA App
This issue is not present on my phone either, and I am running stock AT&T rom.
Really have no idea why, need to hear from some OsiMod users.. will xpost into their thread
Sent from my SAMSUNG-SGH-I927R using Tapatalk
Related
Hi,
Does anybody know whether it's possible to put a lnk to device lock using the HTC TrayApplet so it appears in the taskbar.
After upgrading to T-Mob WM6 on the Hermes, and poking about in the registry it only seems that you can only link to .exe files using the HTC TrayApplet (device lock does'nt appear to have a visible .exe file?? to link too)
(HKLM/Software/HTC/TrayApplet)
cheers
chalky
i have had the same requirement. did not find a solution.
i am using vijay's devicelock instead.
www.vijay555.com
the correct command will be:
VJDeviceLock.exe -pwroff
egoist6 said:
i have had the same requirement. did not find a solution.
i am using vijay's devicelock instead.
www.vijay555.com
the correct command will be:
VJDeviceLock.exe -pwroff
Click to expand...
Click to collapse
Egoist6,
Did you use the HTC Trayapplet with Vijays devicelock program or did you just map vijays devicelock program to hardware button.
I attempted creating a registry link to Vijays Devicelock program using HTC Trayapplet, but I could'nt get the link to work?
Anyway I have mapped vijays devicelock program to the Hardware [record] button which works well. So now it's just one buton-click to lock & power off, as well as freeing up one row in the Today Screen.
cheers
chalky
i do not use the htc home screen. i use vjdevicelock in combination with an icon on my "iphone-skin launcher".
it works perfect although it is quite annoying to press three buttons to unlock the device...
One button to both lock and switch off then... one button (fixed) to switch on, followed by two screen taps to unlock.
hmmmm ... it might be posssible to try and reduce the 3 actions required to unlock. Maybe a script (mort Script or Skchema) could be used which runs on device wakeup (via notifcation queue)which checks to see if the device is locked or unlocked and then either unlocks the device by emulating screen taps or by doing nothing, since its already unlocked?
I might look into this?
Cheers
Chalky
that should do it:
http://forum.xda-developers.com/showthread.php?t=305402
can't try it now as i am @work.
http://www.vijay555.com/?Releases:VJDeviceLock
and use the VJDevicePowerOff App. it locks the device and poweroff at the same time.
chiekh said:
http://www.vijay555.com/?Releases:VJDeviceLock
and use the VJDevicePowerOff App. it locks the device and poweroff at the same time.
Click to expand...
Click to collapse
??? isn't that the one we are talking about (see my post #2)?
Chalky said:
One button to both lock and switch off then... one button (fixed) to switch on, followed by two screen taps to unlock.
hmmmm ... it might be posssible to try and reduce the 3 actions required to unlock. Maybe a script (mort Script or Skchema) could be used which runs on device wakeup (via notifcation queue)which checks to see if the device is locked or unlocked and then either unlocks the device by emulating screen taps or by doing nothing, since its already unlocked?
I might look into this?
Cheers
Chalky
Click to expand...
Click to collapse
I have done a bit more digging in the registry.
HKLM\Security\Phone\L with dword = 2 for lock ON and dword = 0 for lock OFF.
Instantly changing the value for string associated to L fom 0 to 2 and then saving the value in the registry will cause the phone to instantly lock.
So this will come in useful for checking to see if the phone is locked or not.
Also knowing that this registry key controls the device lock and unlock function of the phone means it should be possible if required to set a script to do automatic locking simply by changing the registry key from 2 or 0!
chalky
probably armstrong's device lock worls that way.
try it - it gives you what you need.
i have replaced vjdevicelock with armstrong's devicelock
Chalky said:
I have done a bit more digging in the registry.
HKLM\Security\Phone\L with dword = 2 for lock ON and dword = 0 for lock OFF.
Instantly changing the value for string associated to L fom 0 to 2 and then saving the value in the registry will cause the phone to instantly lock.
Click to expand...
Click to collapse
Apparently not. I've tested it and while that key may report on a phones lock status it does not effect it (on a HTC Dual Touch, WM6). Which is a shame because such a simple API for turning key locking on and off would be wonderful to have.
I have the ATT Tilt 2, Stock ROM. The keyboard backlight does not seem to stay on the whole time I am using it, or sometimes it does not even come on.
Is anybody else experiencing this? Any ideas/solutions?
if youre in the light then itll turn off the keyboard backlights. you cant see what the keys say if the text lights up white on silver keys. if you wait 10 seconds it will also turn off. that can be changed in hkcu\control panel\backlight\qkeyledtimeout.
The Jack of Clubs said:
if youre in the light then itll turn off the keyboard backlights. you cant see what the keys say if the text lights up white on silver keys. if you wait 10 seconds it will also turn off. that can be changed in hkcu\control panel\backlight\qkeyledtimeout.
Click to expand...
Click to collapse
This registry change doesn't work (at least not on all models and not on mine). See earlier thread (http://forum.xda-developers.com/showthread.php?t=556131). It seems that no-one has found out how to adjust this setting.
that setting works fine on all models, touch pro and touch pro 2. try it out.
sorry brother, tried it, as have many others, only to find that on OUR Touch Pro2s it doesn't work for some reason. No idea why though!
you rebooted after setting that right?
The Jack of Clubs said:
you rebooted after setting that right?
Click to expand...
Click to collapse
Yes, I did. What value did you use there? I've tried many, the latest was 6000 decimal.
i like mine at 25. why dont you set a smaller number to try, just incase it cant read a number that large.
The Jack of Clubs said:
i like mine at 25. why dont you set a smaller number to try, just incase it cant read a number that large.
Click to expand...
Click to collapse
Just tried that. No change. Tried 1, tried 0, tried many numbers. The keyboard backlight always goes out after 6 to 7 seconds. Any ideas anyone?
My phone was in my pocket, a reminder went off, I left it, thinking I would just let the phone go back to sleep and dismiss the reminder later.
When I got out my phone, the sliding lock screen was gone, and now when I lock the phone by holding the end call button, the Old WM unlock appears as a soft key in the bottom right corner. After pressing it you get the gray screen asking if you want to unlock.
How do I get the Sliding Unlock Screen back?!
been trying to get it back for hours now....
(phone has stock Tilt2 Rom)
no one sure what happened...
Ditto!
This happened to me today! Cannot seem to change it back to the slide lock. Does anyone know how to fix this issue? Please help!
I installed HD mini lock. Not bad...
msteenwordpower said:
This happened to me today! Cannot seem to change it back to the slide lock. Does anyone know how to fix this issue? Please help!
Click to expand...
Click to collapse
I ended up doing a Hard eset to get it back...cause no one responded...annoying but it works.
I then installed the trial version or PocketShield...and it happened again...but pocketshield is working great to keep away accidental pressing of stuff in my pocket.
I tried Pocketshield, but just kept getting error messages. I want the end call button to turn on a slide lock... and I'd prefer to not do a hard reset...
msteenwordpower said:
I tried Pocketshield, but just kept getting error messages. I want the end call button to turn on a slide lock... and I'd prefer to not do a hard reset...
Click to expand...
Click to collapse
try anista endkey:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=709124
or else smabergs action screen, which give a similar set of options to anistas end key only you access it by holding down the power button. Both of these should lock with your default lock application.
If you're looking for an alternative program to the default, try s2u. you can find a link in the continuoulsly updated apps worth installing on the tp2 thread.
Edit: OK, smabergs action screen doesn't have a lock option on it... but whatever it was based on did. There is a link to that application in the smabergs thread, i think.
I know the OP has hard reset his phone to fix the issue, but just in case anyone else is having this problem, the following reg key is probably to blame:
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\LockScreen\Enable
Default Value: 1 (for Sliding lock screen)
Changed Value: 0 (for soft key lock a la wm6.1)
I found this because I actually WANTED to disable the default WM6.5 lockscreen as I prefer the soft key unlock, partly because of the memory the sliding lock uses, and also because I want to be able to see the gorgeous sense 2.5 interface when I turn my phone on to see the time
There's also a "ShowLockScreenPicker" value on my phone that is set to 0, not entirely sure what that does though.
Bit late I know, sorry! :/
jamiemckee said:
I know the OP has hard reset his phone to fix the issue, but just in case anyone else is having this problem, the following reg key is probably to blame:
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\LockScreen\Enable
Default Value: 1 (for Sliding lock screen)
Changed Value: 0 (for soft key lock a la wm6.1)
I found this because I actually WANTED to disable the default WM6.5 lockscreen as I prefer the soft key unlock, partly because of the memory the sliding lock uses, and also because I want to be able to see the gorgeous sense 2.5 interface when I turn my phone on to see the time
There's also a "ShowLockScreenPicker" value on my phone that is set to 0, not entirely sure what that does though.
Bit late I know, sorry! :/
Click to expand...
Click to collapse
Tried this & I still haven't gotten my slide to unlock back, any other possible solutions? Besides a hard rest that is.
It is related to pocketshield, everytime I install an update I have to go into the system lock settings display tab and switch it from windows classic to default.
I'm using a swedish version of desire-z and sometimes (too often) the phone decides that i'm trying to write capital letters when i'm using the swedish letters Å Ä and Ö. This even happens in the middle of words and the only way to type small letters is by using the software kwyboard. The shift button does nothing.
This is really starting to bug me! Does anyone have a solution?
If so please let me know.
Thanks!
Sent from my HTC Vision using XDA App
I think those letters can only be used in upper case with the keyboard. There is some info in the dev section.
Sent from my T-Mobile G2 using XDA App
ddotpatel said:
I think those letters can only be used in upper case with the keyboard. There is some info in the dev section.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That is not true. I have the nordic version myself, but I am not experiencing the same issue as lugiber Mine works both in upper case at the beginning of words, and in the middle of a text in lower case
Edit: Lugiber: Does it happen with all the extra letters, or just some of them?
Yes, my mistake. I have re-read the thread in the dev section myself.
Looks like it is a bug at the moment, but shutting and re-opening the keyboard helps??
Sent from my T-Mobile G2 using XDA App
Ah, didn't know that opening and closing the hardware keyboard fixed the issue. Thanks for the tip! It's still annoying that i have to do this just for the simplest functionality on my phone! Hope the fix will come soon.
(Btw if someone is thinking of buying swiftkey don't do it until a fix has been released becase it will cause åä and ö to constantly be capital letters.)
Crap! I really love this phone, too bad htc didn't have sense enough to beta test the phone enough before the release.
But if they did i guess the wait would have been even longer. And that wouldn't have been fun!
Sent from my HTC Vision using XDA App
Porcelina said:
Edit: Lugiber: Does it happen with all the extra letters, or just some of them?
Click to expand...
Click to collapse
I have no idea. I never write in Danish or Norwegan so those button pretty much stay untouched. Sorry!
Sent from my HTC Vision using XDA App
I had the same problem with my DZ in the beginning, and traced the problem down to language selection of the keyboard!
Try to slide out the keyboard and watch two letters pop up in the notification bar - for mine it was EN, and figurated out that it was set to english! After I changed it to Danish, the problem went away! Soo kool...
Enur said:
Try to slide out the keyboard and watch two letters pop up in the notification bar - for mine it was EN, and figurated out that it was set to english! After I changed it to Danish, the problem went away! Soo kool...
Click to expand...
Click to collapse
I noticed that the first day I used the DZ, and changed it... maybe thats why I havent experienced the same problem as TS
Strange - I have a nordic Z also and my danish letters is upper case also sometimes..
I have set my keyboard to danish and T9 (guessing words..).
Either we need to play around more with the language settings or there is a bug...
Hmm, strange. I have set my keyboard to swedish and still experience the issue. Hope there is a bug fix for this soon. I don't want to wear out my keyboard hinges just yet.
Sent from my HTC Vision using XDA App
One solution is select STOCK virtual QWERTY as default input method. That way the bug goes away. Installing any 3rd party virtual keyboard will cause the bug.
Enur said:
Try to slide out the keyboard and watch two letters pop up in the notification bar - for mine it was EN, and figurated out that it was set to english! After I changed it to Danish, the problem went away! Soo kool...
Click to expand...
Click to collapse
I have the same problem, and unfortunately this didn't solve it. :-(
Anja
works on touch
mine works fine if i use the default "Touch input" keyboard, but doesn't work on any other keyboard i have tried. So far only tested "Scandinavian keyboard" and "Smart Keyboard pro".
The fact that it does work consistently (without having to open/close the hardware keyboard) with the default keyboard but not in any other, makes me think that the keyboard sends the code for a capital letter and probably sends some correction info along that the default keyboard listens to but the others ignore... just my guess, i really have no experience with how the keyboards work in android...
I have investigated this CAPS nordic problem too. I have found few ways to generate the situation. It appears to generate caps when you haven't activated textfield by tapping it. For example when you write two sms messages in a row. At the first message you tap the textfield to active it and write the message. After sending the first message the text field is allready "active" (cursor blinking there). And if you start to write immediately without closing keyboard or tapping text field it generates only capital nordic letters. Then if you tap the textfield to really activate it again then the capital nordic letters are gone.
I'm not sure if this is the only problem with this CAPS thing but that is easy way to generate it. I think there might be few other situations where CAPS problem exists because sometimes pressing menu -key twice (open and close menu) caps problem disappears but sometimes not. Then sometimes it disappears when closing and opening the keyboard sometimes not. Best results I have had with tapping text field from screen to activate it.
I have informed HTC Support for this matter but all I have got back is: Hard reset your device. I have once done that but it doesn't help either.
Vexix said:
I have investigated this CAPS nordic problem too. I have found few ways to generate the situation. It appears to generate caps when you haven't activated textfield by tapping it. For example when you write two sms messages in a row. At the first message you tap the textfield to active it and write the message. After sending the first message the text field is allready "active" (cursor blinking there). And if you start to write immediately without closing keyboard or tapping text field it generates only capital nordic letters. Then if you tap the textfield to really activate it again then the capital nordic letters are gone.
I'm not sure if this is the only problem with this CAPS thing but that is easy way to generate it. I think there might be few other situations where CAPS problem exists because sometimes pressing menu -key twice (open and close menu) caps problem disappears but sometimes not. Then sometimes it disappears when closing and opening the keyboard sometimes not. Best results I have had with tapping text field from screen to activate it.
I have informed HTC Support for this matter but all I have got back is: Hard reset your device. I have once done that but it doesn't help either.
Click to expand...
Click to collapse
My experience is slighty different from this one.. But if i write a SMS with HW keyboard, send it and exit the sms thread iam in and go to a new one and write there, the cap letters will be there.. This is if i use the HW keyboard during this .. If i then close the HW keyboard and pull it out again they are gone!
Da9L said:
My experience is slighty different from this one.. But if i write a SMS with HW keyboard, send it and exit the sms thread iam in and go to a new one and write there, the cap letters will be there.. This is if i use the HW keyboard during this .. If i then close the HW keyboard and pull it out again they are gone!
Click to expand...
Click to collapse
I think it is the same situation. When you don't close the HW keyboard and you go to writing text without activating text box by tapping screen you get capital nordic letters.
I got reply from HTC Support from England that they are not aware of that problem (after few replys where I explained the situation) and they gave me Norwegian support phone number, but because of costs to phone there I'll asked if they could give me an email address. Plus I can then get some documentation about what have been discussed even if support person changes. I hope we soon get official fix for this.
well i have one small issue i found and its killing me. i have always used go sms pro and use a PIN style lock for the security lock. when trying to add the PIN style lock to go sms pro, it brings up the keypad but will not let me type a pin password. the keypad it brings up is totally not responsive. now if i try to add the pattern lock, that works just fine but it will not let me add the pin style? any tips or is it just me thats got a weird one.
anyone?
Sent from my Galaxy Nexus using Tapatalk
can anyone using go sms pro atleast test this issue for me to see if its just me?
Yep I get the same thing on my go sms. The keypad buttons register but no numbers show in the display.
Luckyman79uk said:
Yep I get the same thing on my go sms. The keypad buttons register but no numbers show in the display.
Click to expand...
Click to collapse
thank you for confirming. it's driving me crazy lol. hate the pattern style. hope they roll out an update
Sent from my Galaxy Nexus using Tapatalk