Cross posting my question from PPCGeeks, since there doesn't seem to be a well known fix in the wild, or at least not that I can find with extensive searching anyway.
Is there a CAB or registry hack to disable the keyboard from breaking the WM 6.5 lockscreen? The device unlocks, even if the kb is slid just half an inch. This causes few, but unexpected unlocks while in my pocket.
I'm using Smart Lock 1.9b with the WM 6.5 lock screen option, but this may happen even without Smart Lock, I'm not sure. Smart Lock is broken after this happens until I manually relock the phone, though. Maybe it gets confused about what the current state of the lock is?
I have tried the registry-based HKLM\HARDWARE\DEVICEMAP\KEYBD\SlideWakeup solution from the Touch Pro, but my TP2 already had this and set to 0. Is there a solution for us Rhodium users yet?
I have also tried the imnuts Disable Slide Keyboard Wakeup.cab that someone recommended over at PPCG and it had seemingly no effect.
Thanks!
There is a cab called disable slide wake up. It prevents the keyboard, or more commonly magnets in holder making the phone think the keyboard has slid out, from waking up the phone and undoing the lock.
OR:
[HKEY_LOCAL_MACHINE\Hardware\DeviceMap\Keybd]
Create a new dword "SlideWakeup" with a decimal value of 0 and soft reset
jonto said:
OR:
[HKEY_LOCAL_MACHINE\Hardware\DeviceMap\Keybd]
Create a new dword "SlideWakeup" with a decimal value of 0 and soft reset
Click to expand...
Click to collapse
lol someone didn't read my original post, did they?
aguenter said:
I have tried the registry-based HKLM\HARDWARE\DEVICEMAP\KEYBD\SlideWakeup solution from the Touch Pro, but my TP2 already had this and set to 0. Is there a solution for us Rhodium users yet?
Click to expand...
Click to collapse
aguenter said:
Cross posting my question from PPCGeeks, since there doesn't seem to be a well known fix in the wild, or at least not that I can find with extensive searching anyway.
Is there a CAB or registry hack to disable the keyboard from breaking the WM 6.5 lockscreen? The device unlocks, even if the kb is slid just half an inch. This causes few, but unexpected unlocks while in my pocket.
I'm using Smart Lock 1.9b with the WM 6.5 lock screen option, but this may happen even without Smart Lock, I'm not sure. Smart Lock is broken after this happens until I manually relock the phone, though. Maybe it gets confused about what the current state of the lock is?
I have tried the registry-based HKLM\HARDWARE\DEVICEMAP\KEYBD\SlideWakeup solution from the Touch Pro, but my TP2 already had this and set to 0. Is there a solution for us Rhodium users yet?
I have also tried the imnuts Disable Slide Keyboard Wakeup.cab that someone recommended over at PPCG and it had seemingly no effect.
Thanks!
Click to expand...
Click to collapse
So...do you have the Verizon/CDMA version? And you're saying that the well-known registry fix doesn't work for the Verizon version?
Because...this registry fix is the solution for Rhodium users -- the one that works for most people...most GSM people, anyway. I've been running 6.5 on my GSM TP2 for a long time and this registry fix has always worked for me.
But maybe not for CDMA?
The above registry edit fixed the slide (magnet) unlock issue in my Sprint TP2 just fine, but I'm still running WM6.1 if that makes a dif.
For me, the SlideWakeup entry did not exist prior to the change.
MCbrian said:
So...do you have the Verizon/CDMA version? And you're saying that the well-known registry fix doesn't work for the Verizon version?
Because...this registry fix is the solution for Rhodium users -- the one that works for most people...most GSM people, anyway. I've been running 6.5 on my GSM TP2 for a long time and this registry fix has always worked for me.
But maybe not for CDMA?
Click to expand...
Click to collapse
Yes, I have the Verizon CDMA Worldphone RHOD500, and i'm running a WM 6.5 cooked ROM (EnergyROM Leo) which I'm assuming added the SlideWakeup key which does not work.
If you enable a 4 digit pin, the lock screen doesn't unlock when the keyboard is opened. The Rhodium's touch screen is so much better than Wizard and Kaiser's, it's really easy to enter the 4 numbers with the quickness...
Disable stylus removal from unlocking device?
Hi - I've tried this fix, but my phone unlocks/wakes when it is gently bumped, and I've narrowed it down to a gfaulty stylus mechanism. The phone only wakes up/unlocks incorrectly when the stylus is in – I believe the phone mistakenly thinks the stylus has been removed so it wakes up. It doesn't happen when the stylus is already out.
Does anyone know how to stop the phone waking/unlocking when the stylus is removed. I've searched the registry but can't find anything.
Related
Argh!!!!
I'm desperate guys!
Ok - I have tried various flavours of WM6 and various radio roms as well but here is my problem:
I use a keyboard/screen lock (the one that comes with the OS) so that if it gets nicked i've got some idiot time to phone t-mobile and cancel the sim. (yes, I also use a sim lock)
However, on rare occasions I get this same problem:
I set the keyboard lock code, in this example 1234. I then lock the keyboard and try it and its fine. I reboot the phone and the code no longer works and the ONLY way to get into the phone is by hard-reset and rebuild the phone again! I've tried everything i can think of including:
Using the keyboard
Using the onscreen keyboard
lots of soft resets
diferent builds of WM6
I know im typing in the correct pass number yet it refuses to use it. Now, remember this happens one out of every three reboots.... the ONLY way I have found round this is as i've said, hold those magic buttons down and poke the stick in the magic hole.
Any ideas whats causing it to lose the numbers I give it?
Any ideas what it wants me to type when it does lose them?
How can I stop it??????
Thanks for your help!
gets better!
Now, after a couple of soft reboots it wont even "click" the unlock option. I can type any numbers I like but, as soon as I click "unlock" at the bottom, it highlights - so it knows its being hit - and does nothing.
I'm so very confused.
Monty Burns said:
gets better!
Now, after a couple of soft reboots it wont even "click" the unlock option. I can type any numbers I like but, as soon as I click "unlock" at the bottom, it highlights - so it knows its being hit - and does nothing.
I'm so very confused.
Click to expand...
Click to collapse
sometimes 2 + 2 dons't be 4 ... as we say here in Spain, this is Informagica
eh? what????
Monty Burns said:
eh? what????
Click to expand...
Click to collapse
Sorry, mate, only a joke.... can't help you, is so strange...
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
I'm not sure if this has been addressed in a thread before, but I've noticed that sometimes when I'm texting in HTC Messaging on my physical hardware keyboard, there's lag in the blinking cursor and it somewhat jumps slowly among my last letters when I'm typing.
Is there already a fix for this?
Sometimes I get the same thing. My last phone was the original Tilt, and there was a fix for it in the Kaiser forums (HWKeyboardSpeedup.cab, or some very similar name, cant miss it). I dont know for sure, but its possibly just a reg edit in cab form for some keyboard delay setting or sensitivity or something. I havent tried it on this device cause its not nearly as bad on my Tilt2, dont know if it would work on this device, but it might be worth a shot for ya. If it doesnt work, you can just uninstall it and do a soft-reset.
Edit: Let me know if you try it and it works so I can do it on my phone too!
If you have XT9 on while using the keyboard, your typing will lag and possibly might not recognize the space bar when you hit it and all your words can be one long word. Make sure XT9 is off when using the hardware keyboard.
AngelDeath said:
If you have XT9 on while using the keyboard, your typing will lag and possibly might not recognize the space bar when you hit it and all your words can be one long word. Make sure XT9 is off when using the hardware keyboard.
Click to expand...
Click to collapse
At first, that's what I thought, but I found that regardless of being in ABC or XT9 mode, there's the same constant lag.
huggs said:
Sometimes I get the same thing. My last phone was the original Tilt, and there was a fix for it in the Kaiser forums (HWKeyboardSpeedup.cab, or some very similar name, cant miss it). I dont know for sure, but its possibly just a reg edit in cab form for some keyboard delay setting or sensitivity or something. I havent tried it on this device cause its not nearly as bad on my Tilt2, dont know if it would work on this device, but it might be worth a shot for ya. If it doesnt work, you can just uninstall it and do a soft-reset.
Edit: Let me know if you try it and it works so I can do it on my phone too!
Click to expand...
Click to collapse
I did some research and found the thread for it, but the TP2 users who have tried it seemed to have issues already. I didn't want to get caught up in it either.
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
BY default I thought in all roms the proximity sensor would turn the screen off when its pressed against our heads so buttons wouldnt get pushed?
If that doesnt work you can always just push the power button... which I sort of do by default for some reason anyway. But... yeah there is a way so the screen turns off when its close to your face. Someone else will chime in with it I'm sure.
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
I'm using the Titanium version without TouchFlo or Sense, and my screen turns off.
This is absolutely a feature of all versions of the TP2, and works regardless of whether TF is used of not. Have you tried a hard reset? Also, does flipping the phone onto its face during a call activate the speaker phone? This involves the proximity sensor (along with G-Sensor), so it might give you a clue if your proximity sensor is somehow disabled, etc.
I dug around the registry for a second, and found the following values under:
HKLM\Software\HTC\Proximity
Name: ProximityDetectStatus
Value: 0
Base: Decimel
Name: ProximitySensorOn
Value: 0
Base: Decimel
Name: PSensorDebounceTime
Value: 300
Base: Decimel
Name: UnexpectedWakeup
Value: 0
Base: Decimel
Some of the values seem counterintuitive (I would think the "ProximitySensorOn" would be 1, not 0). But in any case, it might help to check your registry settings.
Many thanks for your response.
To answer your questions: I've recently upgraded to WM6.1, but didn't like that and so flashed 6.1 back again, and in fact re-flashed that again the other day, so the machine has been through quite a series of hard resets of late, however to the best of my knowledge I have never had a working during-calls-screen-protect other than the brief period during which I was trying out TouchFlo when I first had the phone.
Yes, flipping the phone to activate the speaker works flawlessly, I use it often.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
AidanBell said:
Many thanks for your response.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
Click to expand...
Click to collapse
If you are using Total Commander, go to the appropriate location on the registry, and the first entry is "Add value". Select that, then pick "DWORD", type the name of the value (UnexpectedWakeup). Hit OK, then enter 0 for the value and select OK again.
If you are using another editor besides Total Commander, the process should be the same. I use TC, so I only know that exact process.
Are you flashing to an "official" 6.1 ROM, or a cooked ROM?
Did you run Task29 before flashing the new ROM? This will wipe/format the memory completely, and will sometimes clear up random problems. Its recommended to do this before flashing a cooked ROM, but I don't know if using an "official" ROM is a problem with Task29 or not.
http://forum.xda-developers.com/showthread.php?t=649191
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone, but secondly it seems the reg tweak has done the trick; the screen now Blanks when in call, as it should do. So all is well.
Many thanks indeed for that.
No problem. Happy to help.
But it was the "UnexpectedWakeup" entry that fixed it? That name/description doesn't really seem to fit. In fact, I can't even imagine what that description even refers to, lol!
AidanBell said:
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone,
Click to expand...
Click to collapse
I don't know if there are any potential issues with using Task29 and official ROMs, I've only used it with cooked ROMs. Although, it seems like it would work and serve the exact same purpose. Task29 just guarantees that no fragments of the remaining ROM will interfere with the new ROM. It seems to help prevent random issues with cooked ROMs.
They say honesty is the best policy, so let me share with you what I have embarresingly discovered was actually the reason for my problem - especially remembering what this forum is for and that it might perhaps help anyone else with a similar issue:
I was told that a good way of testing the proximity sensor is to press your thumb against the loudspeaker during a call while looking at the screen. This did not work ... until I removed the plastic protection case! I have always had my phone protected by a two-piece plastic\silicon casing, and I've only now discovered that when this is on the phone the proximity sensor fails, but when removed it works perfectly! Thinking back that makes sense because when I first got the phone and was using TouchFlo the phone had no protective casing.
As it happens I've just bought an expensive cradle for the phone for my new car, which requires that I remove the plastic casing in order for it to fit, therefore the timing is good as it means I can now use the phone with a fully-working proximity sensor.
However, having dropped the phone only once in the year that I've owned it, don't you just know that the moment I start using it without the protective casing .... !
Can anyone help me with a way of stopping the virtual keyboard from appearing whenever I open text programs in portrait mode? Very often I only want to read a file, not edit, however the virtual keyboard constantly and irritatingly appears every time I open such a file. It's there any way of stopping this, please?
Or alternatively, would there be a way of switching off the virtual keyboard altogether? I almost never use it, preferring always to use the hardware keyboard.
I was wondering about this too. I almost always use the hardware (that is sorta the point of getting a TP2) and it is really annoying how the virtual keyboard always pops up on its own, and 90% of the time I have to close it right away. I could see how it would be nice on a all touch screen phone, but for the TP2 it's a really annoying feature.
I'm hoping for a solve for this annoying problem also!
Trying to resolve this too
This is the closest solve so far:
defaultdotxbe said:
i use fakesip
although its an all-or-nothing solution, it completely replaces the soft keyboard, supposedly you can switch back by selecting a different soft keyboard, but that doesnt work for me and i have to uninstall to get the soft keyboard back (which is fine for me since i never use the soft keyboard)
Click to expand...
Click to collapse
Use diamond tweak, and then go to point 20.1 and set the keyboard automatic display to disable and this will stop it from popping up everytime you open your email or sms. Not sure what the registry settings are, but diamond tweak is quite helpful for some of these issues.
Anyone found a registry setting for this yet?
Since this was an annoyance I got used to, I never really thought about it till I saw this thread. Although I do tend to use the on screen keyboard a fair bit.
Anywho, you can go into advancedconfig and under the "Input" tab set "Auto deploy SIP" to disabled. Tried it and it seems to do the trick so far.
Surprised no one noticed this before as I got the impression most people use advancedconfig.
oops, just checked and noticed this doesnt work in opera. hopefully this doesnt apply to anything else!
I've never used advancedconfig, but I might have to check that out if it provides a solution.
...thanks for the reply
By God it seems to work!
Fade2black101 you are a genius!
Many thanks for the fix
This works for me on my Sprint Touch Pro 2 to keep the soft keyboard from popping up automatically:
[HKEY_CURRENT_USER\ControlPanel\Sip]
"TurnOffAutoDeploy"=dword:00000001
HD2Tweak works as well.
Does anyone know of a way to ONLY have SIP deploy in Portrait, NEVER when the keyboard is open? That would be my ideal setting, because I do use both, but I hate having to constantly close the SIP in Landscape mode
JimSmith94 said:
This works for me on my Sprint Touch Pro 2 to keep the soft keyboard from popping up automatically:
[HKEY_CURRENT_USER\ControlPanel\Sip]
"TurnOffAutoDeploy"=dword:00000001
Click to expand...
Click to collapse
Am I supposed to create this entry? I don't see it on my Tilt 2. The extent of my registry editing has only been changing values to existing entries. Do I make the entry name TurnOffAutoDeploy without the quotes right? Case sensitive?
Sorry if I'm missing something obvious...
kiint said:
Does anyone know of a way to ONLY have SIP deploy in Portrait, NEVER when the keyboard is open? That would be my ideal setting, because I do use both, but I hate having to constantly close the SIP in Landscape mode
Click to expand...
Click to collapse
Oh how I wish something like this exists. Unfortunately I'm currently clueless on how to achieve this though.
JVogler said:
Am I supposed to create this entry? I don't see it on my Tilt 2. The extent of my registry editing has only been changing values to existing entries. Do I make the entry name TurnOffAutoDeploy without the quotes right? Case sensitive?
Sorry if I'm missing something obvious...
Click to expand...
Click to collapse
Basically just create a DWord in the appropriate place which is within the "Sip" folder. Then click on it and make sure the base is set to "Dec." Then under "DWord Data" put the value as "00000001" Mine is set to "1" though so maybe you can set it to that and it'll still work?? Don't really know the process behind all this to be honest
Was using Resco Registry so hopefully whatever you're using is of a similar layout and format.
fade2black101 said:
Oh how I wish something like this exists. Unfortunately I'm currently clueless on how to achieve this though.
Basically just create a DWord in the appropriate place which is within the "Sip" folder. Then click on it and make sure the base is set to "Dec." Then under "DWord Data" put the value as "00000001" Mine is set to "1" though so maybe you can set it to that and it'll still work?? Don't really know the process behind all this to be honest
Was using Resco Registry so hopefully whatever you're using is of a similar layout and format.
Click to expand...
Click to collapse
Oops! forgot to say enter the "TurnOffAutoDeploy" exactly how you see it
fade2black101 said:
Oops! forgot to say enter the "TurnOffAutoDeploy" exactly how you see it
Click to expand...
Click to collapse
without the quotes!
Thanks for walking me through that...I didn't think it worked at first, but it's been working fine after my device froze, and I had to reset it. I did a reset after I added the value but I guess it didn't stick or something...FINALLY, no more keyboard popping out!
It seems like I spend more time trying to get my phone to do what I want...than actually using it! One step closer though...
JVogler said:
Thanks for walking me through that...I didn't think it worked at first, but it's been working fine after my device froze, and I had to reset it. I did a reset after I added the value but I guess it didn't stick or something...FINALLY, no more keyboard popping out!
It seems like I spend more time trying to get my phone to do what I want...than actually using it! One step closer though...
Click to expand...
Click to collapse
I know exactly what you mean.. I've had the Wizard and Kaiser before this phone, but because I was at uni I didnt really give a crap bout customising them too much and just got used to how crap the interface was. (especially when drunk!) That's why I had no hesitation bout getting the Touch Pro 2 once it came out. Wish I'd researched it a bit more though as I would have got the HD 2 which came out very soon after (wasn't ready to switch to android at that point). I've been trying to get the Touch Pro 2 perfect tho so haven't really been able to enjoy it properly! Constantly flashing new roms and hard resetting, etc!
On a two year contract and still got a year left, but as soon as it runs out I'm switching to android. I'd get the HTC Desire right now if I could afford it.
On a related issue: Does anyone know a tweak or fix to prevent the display, when the keyboard is closed, from automatically switching to landscape mode when the phone is tilted at a certain angle? I never need this feature and it infuriates me when I'm lying in bed trying to read the phone in portrait mode, and whenever I hit a certain angle it automatically flips over to landscape. I'd love to be able to stop that from happening.
AidanBell said:
On a related issue: Does anyone know a tweak or fix to prevent the display, when the keyboard is closed, from automatically switching to landscape mode when the phone is tilted at a certain angle? I never need this feature and it infuriates me when I'm lying in bed trying to read the phone in portrait mode, and whenever I hit a certain angle it automatically flips over to landscape. I'd love to be able to stop that from happening.
Click to expand...
Click to collapse
Lol yeah I get this aswell.. I usually just switch hands!
Try downloading an app called "G-Config" which allows you to add apps to auto rotate. I think theres sum preset ones that you can remove too.
I'm sure there's registry entries that you can delete which would achieve this, but I don't know where. Hopefully someone else can help?