So yesterday, I turned off the security pattern to unlock the phone. This morning, when I went to unlock it by sliding it, I was asked to draw the pattern again, even though I had turned off the Unlock Pattern.
But here's the interesting part: when asking for the unlock pattern, it'll accept ANY pattern to unlock the phone. Even if it is just a single circle.
I'm gonna upload a video showing this to YouTube soon.
EDIT: http://www.youtube.com/watch?v=JPUY52kb8G8
Nice music in the video!
Interesting flaw there, perhaps it could be a settings glitch? Have you tried toggling the option to ON, then locking the device, unlocking, and then toggling it to OFF, to see if it didn't get interuppted while saving that setting?
Otherwise, have you rebooted after you removed the pattern requirement? If not, that setting could be lingering around in memory...
Actually, after shooting that video, I turned on the unlock pattern and turned it off again. It seemed to be good for a few hours, then the problem reoccured. Even now, the phone switched off due to the battery running out. When I turned it on and asked me for the unlock pattern, it unlocked atfer touching ONE circle.
Hm, interesting. Have you flashed the device at all or are you running stock OS?
As my sig says, stock. If I turn on the Unlock Pattern and turn it off, it'll stay like that for about 8 hours or so, and then it'll come back!
Hm, alright. I was going to suggest a factory reset, but that'll wipe your stuff off your HTC's memory (not the MicroSD Card, though). I haven't run into this problem before, I'll see if it does the same on mine when I get it.
Coburn64 said:
Hm, alright. I was going to suggest a factory reset, but that'll wipe your stuff off your HTC's memory (not the MicroSD Card, though). I haven't run into this problem before, I'll see if it does the same on mine when I get it.
Click to expand...
Click to collapse
I don't mind resetting it. I can backup my data through WaveSecure. I'm pretty sure that will fix the problem. But I'm more interested in finding out WHY it is happening on the first place.
Hello
My HD2 Worked well for a long time, but now everytime I press the "sleep" key it turns off for half a second then turns back on and proudly displays the lockscreen without me pressing anything. There is no way to turn the screen off and go in standby mode anymore.
Obviously the battery drains so much faster from not being able to have the screen off and this silly problem actually makes the phone unusable
I flashed a few roms using HardSPL and now HSPL2. I'm currently running Artemis 11.0, the problem appeared may days after flashing while using Artemis ROM 9.0. A hard reset seemed to fix it but the problem reappeared. Today flashing 11.0 only solved the problem at first boot.
Anyone had that before? Not sure if it's software/rom related or not anymore. HELP
As far as Ive seen, its only you an me who have had this problem so far.
Honestly, Im relieved to see someone else with this problem.
I had exactly as you described, but using Axlor roms.
It worked fine for 1/2months, then all of a suddon the screen backlight wouldnt go off, but a reset fixed it.
But it got worse and worse.
Now nothing will work...
Ive taken everything back to stock, and i mean EVERYTHING! Not a single app installed.
And I still have this problem. I've tried it all.
I think its a warrenty job....
EDIT:
I also noticed the backlight will go off fine when the phone is charging, is that the same for you?
I just sent the phone off to Tmob today, to see if they can fix/replace it.
I'll keep you informed.
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
I experienced this issue when I minimised a game called virtual pool. Closing it in task manager would then allow me to permanently make the phone sleep.
samsamuel said:
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
Click to expand...
Click to collapse
How come Ive still got the problem after reflashing several times and taking everything back to exactly as it came from the box?
flannco said:
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
Click to expand...
Click to collapse
I too have had the navi panel problem.
Im praying they fix mine under warrenty
Yes the problem is exactly what you describe, hard reset and flashing to a stock rom doesn t fix it with no programm running in the background
Navipanel seems to be on randomly sometimes so can I guess it could be related.
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Considering sending it for warranty now.
Thanks for replies! If anybody knows more let us know
Update re standby problem
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
flannco said:
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
Click to expand...
Click to collapse
I have a feeling mines going to come back from tmob in the same state i sent it in...
What other options do with have if they sent it back without fixing it?
any info? I still have not had mine back.
bump... any more infos on this?
CrocMonsieur said:
bump... any more infos on this?
Click to expand...
Click to collapse
Ive noticed allot more people getting this problem. So its not only us.
Tmob are replacing mine, so Im guessing its out of our control now.
did any of you guys try performing a task 29 in between flashing roms? it may help
Audio Oblivion said:
did any of you guys try performing a task 29 in between flashing roms? it may help
Click to expand...
Click to collapse
Actually no, I overlooked it.
Probably would have been a good idea
Prehaps thats worth a try Mr Opr
CrocMonsieur said:
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Click to expand...
Click to collapse
Thanks for this workaround. Now with the urgency gone hopefully somebody finds a lasting solution without the need of sending it in..
I have same problem guys after 4 months using. ...and my HD2 is unusable with no standby. I mean battery gets weak during 2-3 hours. Whats your guess guys is it software problem. Cause Im afraid of this is hardware prob because after reset goes my device in wrong state.
Help!
Sadly I'm running into this same error with my t-mobile hd2....getting serious power drain...can anyone confirm if the task 29 helped at all? Mine won't stay off for more than 30 seconds.
** Found out the google easy sms beta app I was running had a service which was causing the app to come out of standby...uninstalling this app cured the problem.
For me, it was a sd slot problem. When i removed the sd card, phone always waked up after 0.5 seconds, and card was detected as bad.
Now the SD slot was changed (under guarranty) and it work fine, no wake up if sd slot is empty.
Any update on this? My HD2 starting doing this today as well
And I have no usb cable at work to 'trick' it. The only option is to pull the battery which I don't want to do. This is ridiculous. Am I going to have to hard-reset the damn thing to fix it?
FYI I didn't do *ANYTHING* to my phone in a couple of weeks (no new apps, etc.) and it started doing this out of the blue.
You hit the red 'end call' button and it goes black..then comes right back on.
The odd thing is it *thinks* its plugged in because the only screen setting I can get it to acknoweldge is the 'backlight level when charging'. So somehow my phone thinks its plugged in even though my only usb cable is back home.
Grrr. No registry tweaks or temp files I can delete to reset this behavior?
I rebooted my phone earlier today. However, I had a very hard time entering my PIN. Apparently, the touchscreen's calibration was entirely messed up. I don't mean that my selections triggered action at a fixed point relative to my actual finger input, it was just seemingly random. Touching 2 triggered 6 and touching the "Emergency" button triggered 1.
I wanted to see whether it was a ROM problem or whether my actual touchscreen was messed up so I made a nandroid backup and flashed a different ROM. Everything worked flawlessly. Then I reverted back to the nandroid backup and obviously the problem was there again.
After a while I managed to enter the PIN and navigated to the touchscreen calibration tool with the buttons. Now the touchscreen works again but I discovered that the Window Animation setting was altered as well. Additionally, I noticed that the "SIM card changed" notification doesn't appear anymore after I boot up, which used to happen before.
That brings us to my question: is the ROM (stock HTC 1.6, rooted) messed up? Why did the settings randomly change and do you think there are more settings that messed up? Will it keep working in the future or will it happen again?
Any advice would be greatly appreciated, so thanks in advance!
That's strange. It could be a rom problem. But maybe the settings changed while you had the phone in your pocket. If push menu twice in 1 minute the screen turns on and anything can happen then. If it happens again I would flash again stock rom or another.
Thanks for the reply. It hasn't happened anymore, and I hope it never will.
Using Froyo, when setting a PIN lock (now required for exchange) boots take a *very* long time... sometimes 10 minutes or more. Watching the status bar at boot it seems to "restart" at a certain point in the boot process many times. I've captured a log with ADP and I see a number of fatal errors, but nothing I can relate directly to the pin lock.
I confirmed the same problem on my wife's Vibrant (pretty much straight stock w/o a lot of apps).
Pattern lock works fine. (but not allowed by exchange). Password lock behaves the same way.
I posted on the T-Mobile forums and others there confirmed the problem but no solution. I don't think T-Mobile will be fixing this anytime soon... do other ROMs have the same issue? Is there a simple fix?
Robert
I had the same problem using the pin lock. When I rebooted it got stuck in the "media scanner" loop with random vibrating from the phone. I had to format my sd card to get back on, on the third time it did this it forced me to factory reset just so I could use the damn phone again. I got so fed up I decided to look into rooting my phone. I was able to root it and haven't looked back since. If samsung ever decides to send out more updates I'll never do it until team whiskey takes a look at it and makes it better . I went back to 2.1.1 eclair stock, cuz I wasn't able to do it with 2.2 froyo (cuz I'm new). I'm now using bionix v1.2.1, its pretty awesome. I had used the pin lock with this rom and it works just fine, haven't tried the pattern lock or other password lock. I don't use it anymore but it has nothing to do with it being unstable, just personal. Anyway, if you're looking into rooting I highly recommend bionix-v. Good luck with your phone
I am rooted, but you're talking about running a non-stock ROM. I don't feel the need for it (yet).
stock Exchange email forced the use of a pattern or password lock. I've started using touchdown and it just requires the pin lock in the touchdown app, not the whole phone. I'll probably stick with the stock ROM and Touchdown.
I find it strange that something like a screen lock would cause so much trouble.
Robert
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks!:crying: I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet and never had a flip cover or any sort of case so literally don't know why it happened.
Thanks in advance,
Max
Hi
I had the exact same issue with mine, I was on LineageOS and could access the logs so I was able to determine it was an hardware failure.
Went to a repair shop to replace the home button, and Bam it worked again.
If you didn't flash a custom ROM it is likely an hardware issue just like I had.