I did a search of all the forums but didn't see anyone making a cab to enable haptic (vibration) feedback when keying in your PIN in the Security lock screen. For security, I have a 10 digit security code, and sometimes, due to the "lag" of the keypad response, I enter the wrong digits. Having haptic feedback would be great here.
Do a search for Touch Response on here, it's a little app for enabling haptic feeeback for whatever you want!
Thanks for the suggestion. I just downloaded it from here, and installed it in my HD2. After reboot, it had one unfortunate effect of somehow causing my HD2 not to recognize my 10 digit PIN code on startup, and "YES", I'm very sure I entered it correctly, because this isn't something I would forget. No matter how slow I entered the code, it would not let me back into the phone. I also noticed that even with haptic feedback, it was possible to feel the vibration, and yet have no response to the number being entered in the keypad, so this wasn't quite what I was looking for.
I had to do a hard reset..
Luckily, I had JUST backed up my entire phone prior to installing Touch Response, so no harm done.
gregwee said:
due to the "lag" of the keypad response
Click to expand...
Click to collapse
It happens when Windows Mobile is still booting up in the background, kind of how Windows OS is very laggy a few seconds after the desktop screen appears. It is as if the device has finished loading and waiting for your response, but some background processes are still yet to be finished.
Try this, instead of installing haptic feedback (which I don't think is actually the problem), wait for.. lets say.. 5+/- seconds. Then try entering your PIN.
Coming from an Xperia X1, the Leo is blazingly faster. Sometimes I would wait up to 30 seconds on X1 before any input is registered. For my Leo, I usually wait 2 seconds.
btyeh, your probably right. I guess I'll just have to be patient...
Guess this is a lost cause in any case.
gregwee said:
I guess I'll just have to be patient...
Click to expand...
Click to collapse
Its a common annoyance for some people (including me). Maybe not so much with this phone, but mostly desktop OS's.
I have a 4-number PIN code, and can enter it with relative speed. But what happens is that I get to the Sense home screen a little faster, and as a result I get another side-effect of the background-processes-still-finishing-to-load syndrome: the weather animations lag like hell.
Goes accross all OS's really, as the benchmark is to grant the consumer's wishes of a lightning bootup time. From a manufacturer's point-of-view, either you make the process loading more efficient, or you trick the user into thinking the machine load is quick by presenting them with input options (i.e. entering PIN code or displaying of the desktop). The latter is easier to achieve, an I might add, cheaper. But we're getting ripped off at the same time.
Related
Hi,
I'm considering buying a WM5 device but I heard it doesn't allow configuring the Standby screen which is always dead blank. What I need to be shown there is 1) Clock; 2) received texts and 3) missed calls. Like in Nokia/Sony Ericsson mobiles. Any ideas how it can be achieved? By a registry hack or a custom application?
Thanks
Well, in a way WM5 devices do have configurable stand-by screen.
Before I start, do you have experience with a Windows phone before? If not, you may not able to understand something I will be saying. Others members, please leave your comments.
Anyway, for WM5, you can configure your Todayscreen to display everything that you've mentioned below (or more, see some of the Today screen that other posted). Then, you can use this today screen as your 'stand-by screen', of which you need to (screen) lock your phone (using one of the Today's plugins). If you were to unlock your buttons, with screen lock, you can have your phone, press any button to wake the phone up to display the Today screen with all the infor you want. Feasible.
Easier, just wake it and sleep it using your power button. Just a button click away.
Thanks, Hanmin. Well, "Just a button click away" is exactly what I want to avoid. Standby for me means when it's not in use, some screensaver gets invoked. And in some phones, this can be configured to show the details I need (clock, texts and calls), in others it is just dead blank and requires this very "button click" to show the required info. Seems like WM5 devices fall into the second category which is not what I need. But as it has a highly configurable OS, I thought I could find a way to make it show it anyway. So my question is: I have a WM5 phone which I put on the desk and don't use it for, say, 5 or 10 minutes. It is in a silent mode so I don't hear a noise and I don't feel a vibe. But I look at it once in a while to see if there's any news or just to check the time. So how can I do this last thing without actually touching the phone?
p.s.I do have an Axim which isn't really a phone but based on WM5 anyway.
Well.. hmm.. come to think of it.. depends on if you are in ext power. Since you have a Dell PDA with you, you ought to try keeping the unit on while on external power (e.g. on your table), it should gives you the Today screen without the backlight. And you can have a big Today clock whihc you can see without backlight.
If you are on battery, you ought to able to get your notifications via the LEDs (depending on your phone, Charmer doesn't seem to be able to do that). So, you will know if anything happens by looking at the LEDs, but you won't be able to read the clock on it (wear a watch )
Thanks again, Hanmin. Yes, this is what I was originally told. I just thought you folks are experts in mobile Windows so you may know how to tweak it. Like in normal Windows you can do pretty much anything with the OS, I hoped the same is with its younger sibling. I am planning at some stage to get closer involved with this particular version but for now just needed an expert advice. Thanks!
Quite frequently (about 75%+ of boots) my Touch Pro (stock Sprint WM6.1 ROM) tends to lock after I enter my pin and hit unlock. Whenever it locks up it just sits there with the unlock button highlighted. Most of the time that it locks up on the boot my signal indicator has the bolt next to it (it looks like a tower w/ the top view of a flathead screw next to it). I was content for a while just to reboot several times until I got it right, but now it's just becoming a MAJOR annoyance, especially if I need to get booted and into GPS quickly for example. Does anyone have any ideas why this may be happening?
jhw549 said:
Quite frequently (about 75%+ of boots) my Touch Pro (stock Sprint WM6.1 ROM) tends to lock after I enter my pin and hit unlock. Whenever it locks up it just sits there with the unlock button highlighted. Most of the time that it locks up on the boot my signal indicator has the bolt next to it (it looks like a tower w/ the top view of a flathead screw next to it). I was content for a while just to reboot several times until I got it right, but now it's just becoming a MAJOR annoyance, especially if I need to get booted and into GPS quickly for example. Does anyone have any ideas why this may be happening?
Click to expand...
Click to collapse
Have you done a hard reset? Sounds llike some program you installed is interfering with the booting.
I completely agree, my Titan/Mogul did it too. I suppose the question, more accurately, would be is there a way to see all items that are queued to start prior to the log in (I know things like TFD3D, Ariel Battery, and anything else in \windows\startup go after the pin login and WM6.1 logo). Perhaps something similar to msconfig so I can do diagnostic boots and remove items one at a time to see which one is causing it.
Hi there,
Is there anything I can do for a T-Mobile ZTE V768 gingerbread phone that doesn't enter recovery mode(it freezes) or download mode(it reboots),
and can't start because it has a pattern and it is locked for T-Mobile? The phone was sent to a friend here in Honduras from the USA. I have really tried to help this guy but have not met my goal yet.... Any ideas would be totally useful....
Regards and thanks in advance,
freakyhn said:
Hi there,
Is there anything I can do for a T-Mobile ZTE V768 gingerbread phone that doesn't enter recovery mode(it freezes) or download mode(it reboots),
and can't start because it has a pattern and it is locked for T-Mobile? The phone was sent to a friend here in Honduras from the USA. I have really tried to help this guy but have not met my goal yet.... Any ideas would be totally useful....
Regards and thanks in advance,
Click to expand...
Click to collapse
Hey dude hope this will help
A couple of weeks ago, the iPhone world discovered an exploit (not fixed) that allowed anyone to bypass the lockscreen and access the phone, messages, and even pictures.
Well, the bug has been caught in the GS3 world now, too. A few days ago, mobile enthusiast Terence Eden discovered a flaw that also allowed limited access to certain features of your Samsung Galaxy S3, and only in very certain circumstances. And it works no matter what protection you have enabled...Pattern Lock, PIN, Password, or Face Unlock.
Steps to Exploit #1
Lock your phone and turn the screen back on.
Go to Emergency Call.
Select the Emergency Contact icon on the bottom left.
When in the Emergency Contact screen, hit the Home button.
You will see a flash of your Home Screen (no matter what launcher you are using).
In that second when the Home Screen flashes, you can select an app/widget to execute.
The limitations with this exploit are that almost anything you select will run in the background, and you will be back at the lock screen. Where this exploit can be effective is if, let's say, you have a Direct Dial widget on your homescreen. In this case, someone can hit this widget, and the call will go through.
While this is something that should be fixed, it doesn't actually allow you to do much, so really, it's not all that scary. Unfortunately, the fun doesn't end there.
Yesterday, Sean McMillan of Full Disclosure opened up the initial exploit and discovered something much scarier. If successful, not only will this exploit open up the full contents and capabilities of your S3, but it will disable the lock screen completely until the phone is rebooted.
Steps to Exploit #2
Lock your phone and turn the screen back on.
Go to Emergency Call.
Select the Emergency Contact icon on the bottom left.
When in the Emergency Contact screen, hit the Home button.
Immediately after hitting Home, press the Power button.
If you did this correctly, the next time you press Power, your device will go directly to your homescreen.
This is obviously not good. Sean does note that you may need to do this multiple times to get it to work. Also, it doesn't matter what launcher you are using, or whether you are using a lockscreen replacement or not.
In the interest of full disclosure, I tried about 30 times, both with my rooted/modded phone, and with a bone-dry stock phone, and I couldn't replicate it.
But, just because I couldn't do it, doesn't mean it isn't real and dangerous. At this point, there has not been any word out of Samsung regarding this exploit, but I imagine a response and a patch will be on their way shortly.
Atif Naser
Hey everyone, I'm a fairly new OPO user myself here as well; I received mine back in early-mid October, and have had it since then.
But oddly enough, for the past two weeks or so, the following issues have surfaced and has become more frequent, and prominent than ever. For all the fellow OPO-users out there, I was wondering if anyone else has come across the same issue(s) that I've been going through... Unfortunately I really haven't had the time to look up any solution methods and whatnot with two young'uns whom are extremely demanding of my presence... All. The. Time.
So I thought that if I compiled my little list here, hopefully some kind soul will reach out to me with answers (or at least, the direction to where I could find those answers) and make my day just -that- much lighter.
Now just to mention the main points : NO, I have NOT rooted my phone, and YES, I DID install the OTA update, and currently my CM version is the 11.0-XNPH38R.
~~~~~~~~~~~~~~~~~~~~~
a) sometimes, my OPO screen will absolutely REFUSE to turn back on, after I've put the phone to sleep. nothing i do can get the screen to turn back on again - unless it decides it finally wants to. (it's got a mind of its own, this thing... and it's just as stubborn as I am. UGH.) i try double-tapping the screen several times (i've turned that feature on) and i try pressing the power/wake button, or holding it down, ... but zilch. this will usually last up to 10~15 minutes. (after 5~10 minutes of trying to bring it back to life, I just give up and let it be.) when the screen DOES end up turning back on, it's either flashing the "power off/reboot/accessibility" menu several times (probably from me trying to mess with the physical power/wake button) then finally respond to my 'backspace' on-screen keys, or the home icon, returning me back to the proper lockscreen it's supposed to show. ANOTHER way it ends up FINALLY responding, is that the phone will vibrate in short sequences of two, maybe three times and then it will initiate the rebooting process. then everything starts working fine again. i don't recall having ever done anything to trigger something like this to happen, either...
b) the keyboard (the stock Android keyboard) randomly will NOT work; by that I mean, when I am in a messaging app, or any other app that requires a person to TYPE WORDS ON, the keyboard DOES show up, (along with the suggestive bar just above it) and when I try to type, all the usual things will occur; the letter I happen to press will pop-up in response to my tap, and in the suggestive word bar above, it will start showing me the possible word combinations possible based on the sequence of the letters I type, but nowhere do I actually SEE on the SCREEN/message bar/etc. any letters or characters popping up. this issue too, will happen out of nowhere and will last about 15~20 minutes as well. usually what fixes the problem (as annoying as it is) is if I shut down/turn on, then reboot the phone a couple of times to get the keyboard to actually start working again. but there MUST be an easier method to fix this (and all my other issues) !
c) the stock camera app; this issue actually started occurring within days - just under a week of actually getting the shipment of the phone to my place. I was testing out the camera functions, the usual, then suddenly, I would get booted out of the app, and a message saying "The Camera cannot be used at this time" will pop-up as a result. (although, what was even STRANGER, was for a while, (for about 2-3 days) I was receiving a totally different message that didn't even make any SENSE: it said something along the lines of "the camera could not be connected to the device at this time" or "the camera has been disconnected from the device"... i don't even know HOW a camera can "disconnect" itself from the phone, but apparently it CAN.) with this issue, there was absolutely NOTHING I could do to start making it work again. it was non-functional for three, four days straight (no word of a lie) then just for the hell of it, I decided to open the camera app again, and boom, it was working. that didn't last long, though... then suddenly after opening the camera, there would be a prolonged black screen on the phone that wouldn't go away, and I couldn't select any options whatsoever... then when the camera finally started "working", i tried taking a picture - i thought that it would work, since nothing was indicative of it NOT working... but alas, such was not the case. when i went into gallery, to browse through the photos I had taken, they were not there at all, and the photos i had thought were taken weren't actually taken at all.
Asides from that, and some occasional (frequent) crashes while using the phone, I'm not feeling too frustrated by it. (I guess I just have an effin'-load of patience.) Still, I would greatly appreciate any thoughts or suggestions about this dilemma of mine, or providing me the key to all of the answers to these stupid bugs.
Thanks for all those who took the time to read my lengthy post. :fingers-crossed:
-- MK.
I have a S7 from AT&T, non-edge. I have the lock screen setup with the fingerprint reader and a pin code.
95% of the time, the fingerprint scanner works the first time.
4% of the time, it will work the second time.
1% of the time, it does something VERY strange. If it fails the first and second time, it will NOT unlock the screen using the fingerprint reader unless i enter the pin code. It will let me keep trying my fingerprint, but it will says its not valid. I can enter the pin code, unlock the phone, relock, then boom, the fingerprint reader works again. Its like once it fails twice, even though the phone lets you keep trying, it doesn't really read it.
Has anyone else experienced this? It's very annoying and I am wondering if I should RMA, or if this is a software issue.
Finger print scanner indeed suck.. Just make multiple imprints of same finger.. Get every angle possible.
Only time I have to enter my pin is when I reboot the phone. It wants my pin instead of my fingerprint. After that first time though the fingerprint is all I have to do.
when entering a fingerprint each time change the angle of the chosen finger slightly as you press the home key having multiple images at diff angles lessens the chance of not getting a match.
Sent from my SM-G930F using Tapatalk
This has taken some getting used to, coming from the Nexus 5x... its fingerprint scanner is so much better.
On the nexus, you go from a black locked screen straight to the home screen in a split sec with a touch of the scanner that's way more accurate and gets it 99% of the time .
With the S7, I'm having to press the power/home button, then scan, which gets it right more like 65% of the time. And is a 2 step process. Or hold the home button down and try to time it just right- too soon and it doesn't read.. too long and i open google now... haha too complicated. I'm almost thinking there's an issue with mine it's so inaccurate. Or maybe i'm just spoiled to the nexus...
Bottom line= LG & Google implementation= much much better.
Chronzy said:
This has taken some getting used to, coming from the Nexus 5x... its fingerprint scanner is so much better.
On the nexus, you go from a black locked screen straight to the home screen in a split sec with a touch of the scanner that's way more accurate and gets it 99% of the time .
With the S7, I'm having to press the power/home button, then scan, which gets it right more like 65% of the time. And is a 2 step process. Or hold the home button down and try to time it just right- too soon and it doesn't read.. too long and i open google now... haha too complicated. I'm almost thinking there's an issue with mine it's so inaccurate. Or maybe i'm just spoiled to the nexus...
Bottom line= LG & Google implementation= much much better.
Click to expand...
Click to collapse
Press and depress the home button quickly, but instead of taking your finger off the button immediately, keep it on there lightly touching for a split second. It's not that difficult.
It works for me on the first try 95% of the time. The other times it's my fault for not covering the button but instead getting just a corner of it.
I also set it up with both thumbs and both index fingers and it works with all. I'm quite pleased
I've been having aroung 50% success rate on the first time with the fingerprint scanner and about 95% on the second attempt. I don't know if I'm doing anything wrong. I've made the fingerprint profile many times, change position and angles but I still can't get it to work reliably. I wish i could see if theres any gaps, or maybe tone down how "strict" the scanner is.
I've found another flaw in the finger print reader... I'll describe the issue, then upload a vid to show it.
My screen is set to lock/dim/shut off after 30 seconds. At which time you'll have to press the home button OR power button to wake the phone, followed by using your finger print to open the phone.
However, within a few seconds of the screen shutting off you can just press the home button with any finger even ones you've never registered a print for and it will unlock the phone.
https://www.youtube.com/watch?v=Xhb0e01aLuQ
HTCMDA said:
I've found another flaw in the finger print reader... I'll describe the issue, then upload a vid to show it.
My screen is set to lock/dim/shut off after 30 seconds. At which time you'll have to press the home button OR power button to wake the phone, followed by using your finger print to open the phone.
However, within a few seconds of the screen shutting off you can just press the home button with any finger even ones you've never registered a print for and it will unlock the phone.
https://www.youtube.com/watch?v=Xhb0e01aLuQ
Click to expand...
Click to collapse
There is a setting, which by default locks the phone 5 seconds after the screen turns off. During that time you can just push the button and no need to unlock.
But if you push the power button to turn the screen off, if locks immediately. There is a setting for that as well.
Yea...that's not a good thing. Should not be on by default.
Chronzy said:
This has taken some getting used to, coming from the Nexus 5x... its fingerprint scanner is so much better.
On the nexus, you go from a black locked screen straight to the home screen in a split sec with a touch of the scanner that's way more accurate and gets it 99% of the time .
With the S7, I'm having to press the power/home button, then scan, which gets it right more like 65% of the time. And is a 2 step process. Or hold the home button down and try to time it just right- too soon and it doesn't read.. too long and i open google now... haha too complicated. I'm almost thinking there's an issue with mine it's so inaccurate. Or maybe i'm just spoiled to the nexus...
Bottom line= LG & Google implementation= much much better.
Click to expand...
Click to collapse
It works 100% of the time for me if i press the home button and leave my finger on it. Its not even a tiny bit innacurate. Maybe your fingers are greasy.
The reading from screen off sounds a bit better but is essentially the same thing. Just on S7 you have to actually press the button down rather than just press the finger on the sensor. Im not sure why the added pressure makes it that much worse.
HTCMDA said:
Yea...that's not a good thing. Should not be on by default.
Click to expand...
Click to collapse
Forgot to reply to this part.
No it shouldnt be on by default. Its a great feature, if you dont like it you turn it off.
HTCMDA said:
Yea...that's not a good thing. Should not be on by default.
Click to expand...
Click to collapse
That's an android thing. My previous LG and Motorola phones had the same settings by default.
It is convenient because if the screen turns off due to timeout while you are reading something you can quickly turn the screen back on without having to unlock it (password unlock can be very annoying). I gotta tell you if that feature didn't exist, I would have to set a really long screen timeout because I do quite a bit of reading where I don't touch the screen for a while and the constant need to unlock would drive me crazy.
Plus, an extra 5 seconds (added to the screen timeout) is unlikely to make it insecure. If you hit the power button to turn the screen off, it locks immediately. I think it's the best combo of convenience and security.
i'm just saying i feel like that goes against the "security" of having your phone.... your phone could get stolen while unlocked, and all they have to do is set your screen to never time out and now they have access to all your info...
HTCMDA said:
i'm just saying i feel like that goes against the "security" of having your phone.... your phone could get stolen while unlocked, and all they have to do is set your screen to never time out and now they have access to all your info...
Click to expand...
Click to collapse
I someone steals your phone, while it's unlocked, they already have access to all of your data. The 5 second delay isn't going to make a difference.