Ugh... I'm having no end to issues trying to get the right unlock setup that I need.
I'm using the default lock program because I need something that prevents powering down when the end key is long pressed. But now it's unlocking whenever I open the keyboard. This is a problem because the keyboard often get bumped a bit when I take it out the case.
Anyone know how to make it so it doesn't unlock when I open the keyboard.
After a lot of searching and a bit of luck I found the solution... It wasn't that the keyboard was opening, but rather that the Magnets of my belt holster were moving against the sensors enough to simulate a keyboard open, which was unlocking the phone. Either way it was still a problem, but the solution was to make a small change in the registry to not unlock on a keyboard open.
If anyone else is experiencing the same problem you may want to follow that line of thinking.
RedRamage said:
After a lot of searching and a bit of luck I found the solution... It wasn't that the keyboard was opening, but rather that the Magnets of my belt holster were moving against the sensors enough to simulate a keyboard open, which was unlocking the phone. Either way it was still a problem, but the solution was to make a small change in the registry to not unlock on a keyboard open.
If anyone else is experiencing the same problem you may want to follow that line of thinking.
Click to expand...
Click to collapse
can u please tell me which registery value/key u changed to disable unlock when keyboard is opened?
thanks
Couldn't one simply put a pattern or PIN lock on the device?
Related
I'm looking for a solution for a hermes, but assume it would be the same for wizard, kaiser, etc.
I'm often browsing the internet on my phone, and want to type just a few words without losing any screen estate to an onscreen keyboard, and without causing the screen to reprocess to landscape. I especially want to do this as I often have ms reader in the background, and it locks up the whole device while it repaginates the book.
Searching the obvious terms is just leading to people who want to rotate the screen without opening the keyboard - not want I want to do.
Any tips would be appreciated. I either want a way to lock the screen to portrait, or a way to make the device ignore the light sensor which tells it the keyboard is out (but if the keys could still light up, that would be a bonus.)
I`m using Opera, in portrait mode and I get keyboard to write -> the screen of my Kaiser flips in the opposite direction of my keyboard ._.
So yeah, this would be great.
if it works from a light sensor just cover it up with something maybe?
edit: it doesn't work lol, i also have this problem. my phone is too slow to handle this. i bet there's a registry setting for it. if i find anything out ill let you know
Okay, after further searching I found that someone had answered this question.
http://forum.xda-developers.com/showthread.php?t=349760
I now have rotate mapped to a button, (using spb pocket plus, rather than the program in the thread), so I rotate the screen manually when I want.
Lokioki - this solution will probably suit you for your opera problem.
I tryed the sensor lock and I was at first impressed with it but as soon as I had to soft reset the Pro, Sensorlock starting to vibrate alot!
I couldn't unlock the phone at all, not even enter my pin. The only way I could get in to my phone was by putting in the USB cabel, and uninstall the sensorlock. So I won't try that again. Stylus lock looks neat but having to remove the stylus from the phone just to be able to answer a call aint what I'm looking for.
I'm hoping that someone here can rip out the locking function from the Kaiser and make it useable on the Pro. That program was really good and simple.
hope someone can help me find what I want.
you should read the readme or use the search engine in this forum. i guess some devices are just not compatible at this time with the vibrate function. wating for 0.3, it should be fixed.
Emmoth said:
I tryed the sensor lock and I was at first impressed with it but as soon as I had to soft reset the Pro, Sensorlock starting to vibrate alot!
I couldn't unlock the phone at all, not even enter my pin. The only way I could get in to my phone was by putting in the USB cabel, and uninstall the sensorlock. So I won't try that again. Stylus lock looks neat but having to remove the stylus from the phone just to be able to answer a call aint what I'm looking for.
I'm hoping that someone here can rip out the locking function from the Kaiser and make it useable on the Pro. That program was really good and simple.
hope someone can help me find what I want.
Click to expand...
Click to collapse
Yeah I had the same problem!
My touch pro was spaaacing. He was vibrating the whole time....
So the uninstall was very quick with this one
oh seems 0.3.1 is out, bug is gone for me.
for your information ahorn I did use the search function and I did read the readme file..
But sensorlock wasn't my question... I was mearly wondering if someone could make the screen/button lock from kaiser to work in the Raphael... since I had problems with the other.
I had SensorLock installed since yesterday and had no problem at all. In fact I am liking it over another product. Maybe you need change your settings.
My only qualms is that it does not have a unique gesture.
I still got problems with sensorlock, so I'm not gonna use that.
I would like a more simple locking program like the one on Kaiser. Easy and fully functional.
Phone Lock
Sensor Lock would be great for me if I shouldn’t have to rotate the phone like a weird maniac pretending a magician or something - looks extremely funny when it doesn’t unlock and you’re in a meeting with business partners. Like I’m really desperate to impress the party this way …
Would be lovely if instead of rotating the thing we could use a sequence combination of pressing hard buttons. Like “Power, + Back” toggling “Lock Everything”, though this diminishes its name “SensorLock”, I would be gratefully thankful if this option would be kindly implemented by the developer.
i use vjdevice lock and remaped it to the left soft key, works great, one touch screen lock and power off. Big thanks to Vjay555 for this one.
http://www.vijay555.com/?Releases:VJDeviceLock
Security lock from the Tornado smartphone is another good one. I hope someone will be able to rip it off for the TouchPro.
If you are looking to disable the on-screen answer keys only, the answerkeys disabler works perfectly for me...
i remember a while back a fake video of a guy using a thumb print to unlock his phone.
Is there a modification that can be done so that somebody could just touch a location on the screen to unlock it? I wouldnt mind putting a fake thumb print background and having that as the unlock
I don't know of any answer to this, but a cool looking method would be that you have to hold your thumb on there for 1.5 - 2 seconds while a 'scanning bar' moves down the thumb like a photocopier.
Requiring a thumb to be held on would make it more secure against accidental unlockings in the pocket.
Calling any bored developers...
jez83uk said:
I don't know of any answer to this, but a cool looking method would be that you have to hold your thumb on there for 1.5 - 2 seconds while a 'scanning bar' moves down the thumb like a photocopier.
Requiring a thumb to be held on would make it more secure against accidental unlockings in the pocket.
Calling any bored developers...
Click to expand...
Click to collapse
good idea..anybody want to attempt this?
i would be keen in using this! nice idea guys.
The purpose of S2U2 is to make people do a sliding gesture in order to unlock the phone, so that it cannot be unlocked using a simple "touch", even a long one on the screen.
So your request is just the contrary of what everybody wants S2U2 to do...
With your method, what would prevent a long un-wanted touch to be performed while the phone is in your pocket ?
Please also remember that Windows Mobile devices have, for the time being, resistive screens, unable to detect "a thumb touch"... They only can detect "one pixel at a time".
mysterd said:
The purpose of S2U2 is to make people do a sliding gesture in order to unlock the phone, so that it cannot be unlocked using a simple "touch", even a long one on the screen.
So your request is just the contrary of what everybody wants S2U2 to do...
With your method, what would prevent a long un-wanted touch to be performed while the phone is in your pocket ?
Please also remember that Windows Mobile devices have, for the time being, resistive screens, unable to detect "a thumb touch"... They only can detect "one pixel at a time".
Click to expand...
Click to collapse
not sure what everybody wants S2U2 to do, if you mean what it was intended for isnt the purpose of this forum to build apps and change existing apps to further everyone's knowledge and pleasure of their phone? If you dont like the idea, no big deal dont comment.
What your saying is that something would have to press the power button on the phone and then touch a certain location for a set amount of time. I think this is highly unlikely, even more so for the people that carry their phone in a case or by itself in a empty pocket.
Im not sure what you mean by one pixel at a time, my sbp keyboard recognizes when I hold down a certain letter, so not sure how te WM would prevent this from working
You might be able to do something like this with wisbar desktop. I made something like this for a star wars image but nothing that scrolls down like you said. If any software could do it i bet on wisbar desktop. Great idea.
ls6tt said:
not sure what everybody wants S2U2 to do, if you mean what it was intended for isnt the purpose of this forum to build apps and change existing apps to further everyone's knowledge and pleasure of their phone? If you dont like the idea, no big deal dont comment.
What your saying is that something would have to press the power button on the phone and then touch a certain location for a set amount of time. I think this is highly unlikely, even more so for the people that carry their phone in a case or by itself in a empty pocket.
Im not sure what you mean by one pixel at a time, my sbp keyboard recognizes when I hold down a certain letter, so not sure how te WM would prevent this from working
Click to expand...
Click to collapse
By "one pixel at a time", i mean "one pixel at a time"... When you press a resistive screen, even with your whole thumb, in the end WinMo retrieves the coordinates of a single pixel that was "clicked". Actually the screen returns the coordinates of the pixel at the center of the pressed area (or something like that).
As for my comment, please be free to tell me i'm wrong, but please let me free to comment also
And finally, concerning the situation i describe to be likely, you're right, S2U2 was made because the situation is very likely : even with a case, it's very easy to answer a phone call or to click everywhere on an app when the phone is in the pocket.
So, no offense meant, let's all keep cool.
Have a nice day.
mysterd said:
By "one pixel at a time", i mean "one pixel at a time"... When you press a resistive screen, even with your whole thumb, in the end WinMo retrieves the coordinates of a single pixel that was "clicked". Actually the screen returns the coordinates of the pixel at the center of the pressed area (or something like that).
As for my comment, please be free to tell me i'm wrong, but please let me free to comment also
And finally, concerning the situation i describe to be likely, you're right, S2U2 was made because the situation is very likely : even with a case, it's very easy to answer a phone call or to click everywhere on an app when the phone is in the pocket.
So, no offense meant, let's all keep cool.
Have a nice day.
Click to expand...
Click to collapse
thanks for the explanation. Wasn't sure what you meant.
If it recognizes one pixel at a time and you set a block of pixels as the touch point wouldn't this work.
thanks for the advice, anybody else?
You could make it look like it was scanning your thumb, but you couldn't make it really scan it. If you open up one of these touch screens it is just some metal dots on two sheets of clear plastic. They register when they are pressed together and touch. Nothing more.
I believe that Sunscape is an app that will appeal to alot of you guys.http://forum.xda-developers.com/showthread.php?t=416843 I never tried it but I hear it has a rub to unlock feature...as well as using possible pressure points on the screen to unlock.
I've been doing alot of research about unlockers because I want to build one that like an unlocker combined with an applauncher, when you slide to unlock you basically just slide the icon you want to launch after the unlock and once the screen unlocks it opens to that program. I think it seems logical and keeps people from having to delve into the UI just to unlock and send an SMS or whatever...
I get another idea . In this version i Slide to right , who can change this for slide to left becouse i have SE Xperia X1. And slide to right it's uncomfortable for me becouse slider it's moving. If someone have this motive, please place this
anyone have this problem or a fix? lately my keyboard keys are difficult to press... i mean i press a key and it feels like a click or the key goes down but the letter isnt inputted.
so i have to press really hard and then it works....to use the keyboard now is too difficult to type sms, etc.
....or maybe ive lost strength in my fingers?
any ideas?
treo 750
just do a hard reset on your treo 750...
Yes, I've had this with my old Treo 750. I put up with it, but I remember reading about some people who had opened up their device and removed the membrane behind the keyboard. They reported that this sorted out their problem, but I haven't tried this myself.
junglemonkey said:
anyone have this problem or a fix? lately my keyboard keys are difficult to press... i mean i press a key and it feels like a click or the key goes down but the letter isnt inputted.
so i have to press really hard and then it works....to use the keyboard now is too difficult to type sms, etc.
....or maybe ive lost strength in my fingers?
any ideas?
Click to expand...
Click to collapse
I have same problem with my treo, anyone can give solution for this?
monomer888 said:
Yes, I've had this with my old Treo 750. I put up with it, but I remember reading about some people who had opened up their device and removed the membrane behind the keyboard. They reported that this sorted out their problem, but I haven't tried this myself.
Click to expand...
Click to collapse
Just a reference for my previous post: http://discussion.treocentral.com/treo-750/167703-some-keys-not-very-responsive-anymore.html
http://www.treo8.com/bbs/thread-130931-1-2.html
some picture guides to open the device and solve the keyboard problem, sorry it's in chinese, but with photo, somehow it is understandable.
The key press issue has deteriorated to the point that I'm willing to take apart my Treo 750 to deal with it now (also I'm a bit braver partly because it's now my secondary device). When the down key on the D-Pad starts to not register, it can get very annoying
I found this video on YouTube of a Palm Treo 755p, which apparently most resembles the Treo 750. Hope it helps:
http://www.youtube.com/watch?v=j9p1CqviqW4
Just to report back: I've completed the 'operation' and having removed the membrane, the keyboard is a lot better!
thanks
thanks for your replies...i will take a look at the links and videos and try out that tip about taking out the membrane
seems like it worked for another reader so i hope it works for me
First, just want to say thanks for the development on the Note Pro. CM on this thing is awesome. That said, I still have a couple of lingering issues, hoping someone may have found some work arounds/solutions. Inevitably there will be someone that will reply with "USE THE SEARCH!". For those that do, I will offer you my sincere admiration. Your search foo is only exceeded by your wit. For those that are still willing to read on and assist, know that I've come up empty in my search attempts. Believe me, I'd rather have found a simple search result than to have typed all this up... In any case:
1. Hardware keys and navbar -
CM has a setting for "Enable on-screen navigation bar and disable hardware buttons". Checking this box enables the navbar, but fails to actually disable the capacitive and physical buttons. This causes me some grief when using the tablet in portrait mode. I've tried hacking around in the build.prop and the Generic.kl files, but haven't found that magical combination of new lines/commented out lines. Maybe CM does this differently than other roms? (I've not observed a difference in these files when toggling back and forth in the settings, so there must be something else I'm missing.) Any pointers?
2. Key Mapping -
I have the Logitech Pro Keyboard Case. Seems to work well, for the most part. (I'm typing on it now...) However, not all of the keys work. Example - there are keys on the top left row for "back", "menu" and "task switching". Nothing appears to happen when pressing these now. Again, probably something in a .kl file somewhere, but I'm coming up empty. There doesn't appear to be a Vendor-Specific.kl file, but Generic.kl doesn't seem to cut it either.
3. On-Screen keyboard still displays when using bluetooth keyboard.
Well, that about says it all really. I've tried using both the Google keybard, and SwiftKey. Both continue to show up on-screen, even though I'm typing on the bluetooth keyboard. Swiftkey even tells me that it cannot detect a physcial keyboard. Probably related to the key mapping issue from above, but...
Again, thanks for all the work on this. Having CM saved my tablet from it's date with eBay.
Thanks!
- Bri
1. i thought about it but now i haven't spare time to implement. next week maybe.. but i dont promise
2. and 3. try this programm https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
171
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
bribash said:
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
Click to expand...
Click to collapse
Hey, try going with Null Keyboard, enable all your keyboards, and switch between them depending on whether the device is connected or not