tl;dr: lock function no longer working after upgrade from official 1.6 to 2.1
I know this is a duplicate post from two others, but they never got any replies, I'm just trying my luck here.
New phone, preloaded with 1.6, no third party apps other than carriers bloat. Lock screen functions just fine on 1.6 and I have never attempted any "rooting" to this device.
Once I perform the official update with Samsung Kies Mini, the lock screen never shows up. It boots right to the home screen and the lock button now only turns off the back-light.
Tried enabling pattern lock, but it never shows. Performed system reset back to 1.6 and the lock screen returns. My carrier, Rogers (Canada), has never heard of this and is going to exchange my phone. However I want to find out if anyone else has a cure for this weird bug before my replacement arrives Friday (Nov 5).
Try changing backlight timeout in settings- on 2.1 screen is locked when light goes off. Maybe somehow system is set to "never"
Related
Hi everyone, I just purchased 2 HTC HD2 phones from T-mobile 5 days ago and every thing was fine until 2 days ago. The phone that is mine started to freeze on the unlock screen / slide button, will not unlock all the time, sometimes it does sometime it doesn't. I have to remove the battery and reset to unlock. Both phones came with the same firmware version 2.13.531.1 but only my phone freezes and not my wifes. I read in the T-Mobile forums that, the latest update would fix my issue. So I update my firmware to the latest version (actually reinstalled latest version as it was already installed on phone, to see if that would fix issue) 2.13.531.1, to fix unlocking issues in the lock screen. But after updating several times and trying almost every thing I have read about in this forum and HTC's forum, like disabling sensing and cleaning the RAM removing locations from weather app and permanently deleting all text messages and emails, and disable autolock with cab file, Nothing has worked. I have 2 HTC HD2 but only 1 freezes. They both have the same firmware version 2.13.531.1. The only work around I have found is to deactivate automatic shut down in the settings menu to keep the phone from locking automatically sense it only freeze at the unlock screen/slide button.How ever this drains my battery alot faster because the screen only dims but never shuts off and its not a real fix to the issue. If anyone knows of a real fix please post here will I check again for any knew posts......................Thank you .
It might just be a defective phone.
I for one started on the (i believe its 2.10) firmware & then upgrade to the 2.13....HATED IT. They 2.13 which was supposed to "fix" certain bugs seemed to make mines worst so i reinstalled the original 2.10.
Im not sure if they do handset trade where you are, you could call the store and find out, if not, you could always downgrade the software to see if it works, or just flash a custom ROM....
Or wait on hole for a TMO rep and see if they can just send you a replacement (once you got through a bunch of troubleshooting that most likely wont work).
Good LUCK!
mine also freezes on the lock screen, is there a way to deactivate the lock screen during standby?
spikegotti said:
mine also freezes on the lock screen, is there a way to deactivate the lock screen during standby?
Click to expand...
Click to collapse
Go to google and type in "deactivate lockscreen on hd2"
Choose the second result...
Didnt want to get in trouble for posting the link to another site so i decided to play it safe....
I have hadthis problem since I upgradedfrom at&t 1.6.. this problem manifests regardless of what rom iam running..
Basically, it happens after I use (either receive or make a call) the phone... if you bring the phone close to your face to activate the proximity sensor and turn off the screen,the screen never comes back on. No matter what I do, can't use the device after that... I know the device itself is NOT frozen because if the other part hangs up... I can still hear the notifications for email or other events and even hear the ringtone if someone calls... I just can't do anything about it because the screen stays dark and in responsive..
I went from at&t 1.6 with 31 baseband and firmware to 305 using QDL from sreakdroid..I immediately noticed the issue so thought I would upgrade to the official 318 but still had the same issue... I then went to Steve's 1.5.1 but still the same behavior... I have done data wipes and repeated the 305-318-1.5.1 upgrades with the issue present in all roms. . At this point Iam frustrated as the device cannot be used past the first phonecall..
Any ideas or help will be appreciated.
Try to recalibrate your screen bro.
Just did thescreen calibration... didn't solve the problemm... the fact that the problem happens only after/during a phone call leads me to blueberry somethingelse is causing it... there are no other issues with the screen prior to a phone call... plus I would think that I should be able to wake up the screen with the power button and even that doesn't work???
Is there a way to go back to US ATT 31 rom?
Not Android Development
Moving to General
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
I have my Nexus 4 for about 2 months now, and lately I have noticed a very annoying thing.
Whenever I lock my screen and then trying to quickly unlock it (using the power button), the screen lights up a little bit in a dark blue, stays like that for about 15-20 seconds, and only after that the lock screen shows up, allowing me to unlock the phone. This happens every time I try to unlock it after, let's say, less than 10 seconds after I locked it. If I unlock it after a longer period of sleep, no problem at all.
I have stock Android 4.2.2 and the phone is not rooted.
I have had installed GO Locker, and thought that it might cause the problem, but I uninstalled it. Unfortunately the problem persists.
I also had apps like Screen on / off, GO Switch, that were device administrators to allow them to lock the screen. I have unistalled them all, the same situation.
Can anybody tell me what is the cause and how could I fix this? It's really annoying when I need some quick information and I have to wait 20 second for the screen to unlock.
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.