First off-- great job on the ROM. I appreciate your hard work as much as anyone. It generally works great on my SDA.
That said, could you please remove Automatic keyLock 3.9 beta 10 from your next revision? It is a nice program, but should probably remain in the Extras package. My company uses Goodlink for pushing exchange email to Windows mobile. Goodlink enforces keylock control on our devices and cannot be disabled. I am having strange issues happen with the keyboard and backlight. I think these are happening due to a conflict between auto keylock and goodlink. In some cases the keyboard just stops working. The only keys that will take input are the left and right soft keys. In addition, the backlight sometimes refuses to come on after, key press, OR it just blanks out while I am in the middle of something. In both cases the only way to get it back, is to reboot the phone. I have tried the adjusting the DisableLightWorkaround key, but it had no effect.
Thanks!
Just delete keylock.lnk from /windows/startup, you can do it even from pc thru AS if your keyboard locks... and then keylock won't matter to you
thanks. that is the 1st thing i tried. unfortunately, it seems like keylock makes reg changes even if the program is not active. i could be wrong, but i haven't had this problem with any other rom (wm5
or wm6). this is the only rom i have tried that had auto keylock pre-loaded.
Related
I recently got a Qtek 8300 (similar to an i-Mate SP5m). It's working pretty well and I'm pleased with it. However, one thing I wish I could correct is that when I have my phone in a case, slightly touching the front of the case causes the locked keyboard to unblank the screen. I have an eBook reader so I have the screen stay on for a longer-than-usual time. The problem is that unblanking the screen for no reason wastes battery power. Half the time when I glance down at the phone case, the screen is on.
Is there any way to get only the left soft key, or any other key, to unblank the screen to unlock the keyboard, and have all the other keys ignored? Thanks.
-Gary-
I'd be very curious to get a solution to this problem too. Even the Automatic Keylock utility seems to end up calling the canned WM5 keylock routine, which turns on the light whenever you touch a locked key...
I really liked the way WM2003SE locked the keys on a PocketPC phone. With that, the light stayed off until I pressed the power button. The beauty of the power button is that it's recessed and won't be pressed by a carrying case. Plus, I always knew where the power button was - even in the dark.
Dave H
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
cinimod1000 said:
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
Click to expand...
Click to collapse
From my Wizard (XDA Mini-S), turning the "lock all keys" option on and off, changes this value:
[HKEY_CURRENT_USER\ControlPanel\Keybd]
"DefaultKeyLock"=dword:00000000 (unlocked)
"DefaultKeyLock"=dword:00000001 (locked)
unfortunately, there is no "Keybd" key on my Tornado (Xda IQ, specifically) so I suspect this won't work. Shame...
Daern
Hi Guys,
There are a couple of things I've not been able to get working in the way I'm used to on my Artemis, just wondered if anyone can help....
1) The require password when device is not used for x minutes, when set to 0 minutes on my Artemis, would only ask me for the password if it was coming out of standby... I'm trying to get the Polaris to behave in the same way. The gotcha with this is that having edited the settings on the Artemis, it doesn't behave like this anymore
What's actually happening is that when set at 0 minutes the device locks right away. I've now set it to 1 hour but now when coming out of standby I don't have to put the password in unless I leave it for an hour... Which is what it sounds like it should do, but not what I want, or what it WAS doing!
2) My backlight doesn't come on until I have fully unlocked the device... So I can't see the keypad or unlock button in daylight. My Artemis doesn't do this, the backlight comes straight on.
Any ideas are welcome
Thanks
LP
Wouldn't mind knowing about a reg tweak for the backlight/lock issue myself...
Screenlock? and backgrond light
I'v managed to get a screenlock function to work really nice. The Polaris is now always locked on start, exept for Answer/Reject soft and hardware buttons, plus that I can shut down the ringing with the volume button. Really nice.
The program that does it is Autolock. You find it att http://www.intelliott.com
The backlight problem was solved via a register hack found on this site.
At
\HKCU\ControlPanle\Backlight\LockLevel
Rename the folder to LockLevelX.
Does work even if the handset is soft resetted.
Thanks peta§,
That reg hack works pretty well
Any chance of a little more detail on the registry tweak. The backlight issue is really starting to annoy me.
Thanks
I followed the instruction in this link. It was quite easy:
http://forum.xda-developers.com/showthread.php?t=351709
peta§,do u know any registry tweak in order to disable key lock permanently?
Cheers Peta,
Worked a treat however, I don't understand why this was not done at the manufacturing stage unless it was purely an oversight.
Thanks
I agree MusicArtist, it should be activated in WM6 from the start. It's very interesting what can happen when you take your phone out of the pocket when a reminder calls for your attention, or a SMS or call is incoming and you by mistake presses some functions on the activated screen.
dene3erw, disabling key lock permanently? I don't follow. Do you mean the Autolock?
If so, ýou can find an icon in the Program folder, just to tap on it. It enables/disables the function.
Hey everyone,
If I have Opera open on my HTC Touch Pro with the hardware keyboard slid out, it still shows the onscreen keyboard (and it's annoying having to keep closing it all the time). Any idea how to fix this?
I too would like to know the solution for this. I have a feeling that this is kind of a feature from Opera and can't be disabled but it's very annoying for users with hardware keyboard.
I have this issue on my kaiser too
Daniel1515 said:
Hey everyone,
If I have Opera open on my HTC Touch Pro with the hardware keyboard slid out, it still shows the onscreen keyboard (and it's annoying having to keep closing it all the time). Any idea how to fix this?
Click to expand...
Click to collapse
HKEY_CURRENT_USER\ControlPanel\Sip>:
Create or change DWORD TurnOffAutoDeploy from 0 to 1
Restart your device!
its a bug with opera...
Brendo said:
its a bug with opera...
Click to expand...
Click to collapse
Actually, it's not Opera. It's Raphael itself. HTC should have made it in such a way that if the keyboard is out, the SIP should not be displayed.
To prove that it is not Opera, try creating a new SMS. Do this in portrait mode first. Try hiding the SIP and change field (To or Message). You'll see that the SIP is displayed every time you change field. Now slide out the keyboard. Try changing field and you'll see that the SIP is also displayed.
As far as I understand (from another post somwhere on the forum) it's not technically a bug...
It's a requirement of Windows mobile that the SIP is deployed whenever text is entered into a field. Seems rather daft when you have a hardware keyboard on your phone though...
I've had that registry tweak above work for me, the same tweak is implemented in Advanced Config 3.3 as well. There's another fix that *should* work throughout Windows Mobile, for text fields.
It's called nullkb, and installs an option into the SIP menu that gives you a null keyboard option, and any attempt to bring up the SIP brings up nothing. I installed it, and it appeared to work, but after a reset, it defaulted back to the normal keybaord, so you have to select the null keyboard everytime you reset the device.
I'd love to find a way to simply disable auto deployment of the SIP in ALL circumstances. NullKB forces you to go into the SIP menu and select another keyboard should you want to use symbols, for example. The registry fix only seems to (sometimes) work for opera.
I just want the SIP to stay hidden until I want it, and a single click on the keyboard icon should bring the selected keyboard up.
I have no idea how to go around getting this working, I'm more of an end user than a developer...
e: there's also this reg key HKEY_CURRENT_USER\ControlPanel\Sip\AllowChange=1
Change that to 0 and it disables the SIP entirely. I'm thinking this fix and judicious use of PQzII (once I figure out how the hell to set it up...) to set up hardware keys for lots of symbols (where the hell is "\" on the keyboard? On a WM phone I would've thought a \ key would be mandatory...) might be the way forward, though it's a fair amount of work to get everything set up.
branko.savic said:
HKEY_CURRENT_USER\ControlPanel\Sip>:
Create or change DWORD TurnOffAutoDeploy from 0 to 1
Restart your device!
Click to expand...
Click to collapse
That doesn't work, at least not on my CDMA Touch Pro.
SquidgyB said:
e: there's also this reg key HKEY_CURRENT_USER\ControlPanel\Sip\AllowChange=1
Click to expand...
Click to collapse
Doesn't work on my CDMA Touch Pro That regedit makes the keyboard appear on screen all the time, with no way to minimize it.
it is a bug in opera...
it is well documented as one
you can see if you disable autodeploy of keybaord (use advanced config) and youll see it still appears in opera. the only work around is to download nullkb and select it as your input while using opera
I had the problem with nullkb that it wouldn't stay as the default SIP after a soft reset. Loading PQzII and setting a link to PQzII in the startup folder fixed this, as within PQzII you can select which SIP should be displayed in portrait *and* landscape individually.
This still means a couple of clicks to get a keyboard up in landscape for entering symbols, but if in portrait the SIP will display normally.
I still can't get the "\" to work properly through PQzII though... it displays odd characters whenever I enter it into any of the PQzII configuration options. I suspect \ is used extensively in the code or something, and this messes up what's going on inside PQzII.
Suddenly on my Opal, the Send (green) button won't launch the keypad (dialer) even after doing many reboots.
WM6.1 user.
please help.
Well my obvious guess would be that the button is physically broken, otherwise, I haven't a clue
but i can still use it to answer calls... and my long press (assigned: rotate screen) is still functional.
after many wasted times of hard resetting and installing apps to trace what might have caused it, finally the keypad is back!
the culprit... Advanced Configuration Tool v3.3.
i'm still testing what setting in Advanced Config 3.3 that affects the green button...
oh well...
Hello everyone,
I have an unlocked Nokia Lumia 710 running a custom ROM and all in all the phone is good. However, the proximity sensor doesn't seem to work properly (I don't know if the problem is from the custom ROM or from the phone itself but it doesn't really matter) - when I'm in a call I keep pressing the Hold and Mute buttons (no matter how I hold the phone) which makes me really irritated. So I was wondering, there should be registries I guess that make the buttons active when pressed during a phone call. Can someone point me to the correct registries that control if the buttons are active or not when pressed so that I will hopefully be able to completely disable these two buttons (so that when pressed nothing happens)? I don't use them anyways, so completely disabling them would certainly fix my problems. I'm posting in the general WP7 section because I guess the location of these registries would most probably be the same for all phones...
Thanks a lot in advance!
There's a registry value that is updated automatically by the proximity sensor and indicates its current status system-wide, but I doubt you'd want to use it. For one thing, it would almost certainly get immediately reset by the sensor, faulty or otherwise. For another, the Phone app isn't the only thing that uses the proximity sensor; you would end up locking out the touchscreen in some other apps too. Finally, this would also prevent you from pressing the End Call button!
I don't know of a registry value that's specific to the Phone app's use of the proximity sensor. However, even if there is, the first and third reasons above still apply.
I instead recommend that you simply tap the power button when putting the phone up to your ear to talk. This will turn off the touchscreen (and incidentally save power) and you can tap the Power button again to access the Phone app or any other app on the phone when you need them, without interfering with the call.
There may also be a tool in some built-in Manufacturer or Diagnostics app that would let you test and adjust the sensitivity of the proximity sensor. This would perhaps be the best option, but I don't know where or if it exists on a Lumia.
What I want to do is not to play with the proximity sensor itself but rather with the buttons on the screen during a call. I guess I didn't make myself clear enough, sorry about that. The idea is that when I'm in a call, the proximity sensor does not work properly and I always press either the Mute or the Hold buttons. So, these buttons can still appear during a call but when you press them, I don't want anything happening. I mean, the idea is even when the phone is not next to your ear and the screen is active during a call, pressing the buttons to do nothing. I'm just following some simple logic, which might of course be incorrect (or too simple), but I'm thinking that there is most probably a separate registry for each button that controls whether this button does some action when pressed or not. I'm also hoping that they'll be separate registries for each button so that I can, for example, disable the actions for the Hold and Mute buttons, but leave the End Call button active. The problem is that I have no idea where to look for this registry since I'm still new to WP OS.
Heck, it would even be OK for me to completely remove the buttons from the screen during a call (or substitute the current buttons with some 1x1 px transparent images), if that's possible, so if someone knows how to do even that, tell me.
I was also considering using the power button when in call but I first want to see if there is any other way to do what I want. And since I'm not using the Mute and Hold functions at all, I just thought about disabling them.
No, I understood you. I was suggesting the "fix your proximity sensor" option because normally, the problem you're experiencing just doesn't happen; that's what the prox sensor is for. Sometimes it's miscalibrated, though, or something is covering it up (some poorly-cut or installed screen protectors do this, for example).
The "Phone" app isn't a Silverlight app like third-party ones; it's a native EXE that we pretty much can't modify without using a custom ROM. That's going to make changing it the ways you suggest (disabling or resizing certain buttons, etc) quite difficult.
I'm pretty sure you don't want to disable all the buttons always, even if that were possible. For one thing, that would prevent you from hanging up, as I mentioned before. It would also prevent you from dialing any numbers, which would make the use of touch-tone automated services impossible.
The Power button option really seems like the best fit for you. It's easy, doesn't require any hacks, doesn't break any other functionality, and should be the next-best solution beyond actually solving the problem.
I see now, makes sense. In my head it sounded simpler than what it really is. I was considering resizing the buttons because I'm also using iOS and I quite enjoy digging in the OS and changing some elements, so it's possible there to, for example, substitute some buttons with transparent 1x1 px images, etc. But that's irrelevant. Looks like WP is different and I still need some time to get in to it. Anyways, thanks for your help.
P.S. The screen protector was the first thing I "accused" but unfortunately it wasn't causing the problem.
On a custom ROM, you could definitely tweak the Phone app if you wanted to. However, the way WinCE (the kernel behind WP7) works, OS files are almost always marked as "in ROM" which means that the filesystem driver will refuse to modify them while the OS is booted. This makes tempering with the stock OS difficult; we have to find ways to modify the behavior of apps and system features without modifying the apps or features themselves.