Not sure if im the only one with this problem but no matter what rom I put on it seems to have an unlocking problem....after hittting the power button to bring up the device...nothing will happen...the screen will "turn on" but will not come up with the slide to unlock screen, its just blacked out...another problem is that the slide to unlock screen will come up but the screen is unresponsive......right now I just keep hard resetting to get back into the device...is there something that can fix this or what.....I'm currently on the hashcode ics beta rom but I also tried miui and it also did the same thing
I occasionally have the same issue and I am running CM7 so I don't think its ROM specific. If you do a search I am certain there is a ton of info available. People on the forum are calling it SOD or sleep of death. You may want to try searching for that.
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....
Froyo 2.2
After putting the phone in stand-by by pressing the "end" key, the phone wakes up fine within 1 minute, 2 minutes or even within 5 minutes.
However, if the phone is left for about 10 minutes or longer, the phone resumes back with the "black screen" or "dead black screen" - as referred to in many threads all across.
Solution found:
Pulling the battery out and restarting the phone resolves the issue.
This solution is quite troublesome and long process to go through.
Any advice?
Phone
HTC HD 2 by TMobile
Android Version
2.2
Baseband Version
15.39.50.07U_2.10.50.26
Kernel Version
2.6.32.9-28169-g26C6697-dirty [email protected] #3
Build Number
2.09.405.8.CL218634 release-keys
Software Number
FroyoStone Sense V2
~~~~~hope the information helps~~~~~
That is SOD(silent of death), but it solved few weeks ago by newer zimage
Where is this zimage found?
foxcheng said:
That is SOD(silent of death), but it solved few weeks ago by newer zimage
Click to expand...
Click to collapse
I thought it was Screen Of Death?
Hmm, Anyways it was also solved earlier by changing your radio.
The radio is in my sig hasent given me on SOD in about 3 weeks of using it all day every day
.BetaBoy said:
I thought it was Screen Of Death?
Hmm, Anyways it was also solved earlier by changing your radio.
The radio is in my sig hasent given me on SOD in about 3 weeks of using it all day every day
Click to expand...
Click to collapse
Can you explain how I update the radio to this one and where I can find it? Sorry for noob questions. Someone upgraded this phone to froyo 2.2 not me.
yes please, help in regards to upgrading the radio would definitely be appreciated!
It seems like I found the solution to my problem. I had to remove the dual boot application by JMZ in order to resolve the "dead black screen" or "screen of death" issue.
I hate to not have dual boot capability, however, would upgrading the radio resolve the issue with continuous use of JMZ?
talha984 said:
Froyo 2.2
After putting the phone in stand-by by pressing the "end" key, the phone wakes up fine within 1 minute, 2 minutes or even within 5 minutes.
However, if the phone is left for about 10 minutes or longer, the phone resumes back with the "black screen" or "dead black screen" - as referred to in many threads all across.
Solution found:
Pulling the battery out and restarting the phone resolves the issue.
This solution is quite troublesome and long process to go through.
Any advice?
Click to expand...
Click to collapse
It did not fix it for me - I went through 7 battery-outs / reboots and then booting into Android - every single time (7 times) I got Screen of death... I deleted the whole thing all together and will test out V2 of FroyoStone Series ...
Forgot to mention my SODs occurred on FroyoStone Series V1...
Quite interesting enough, my V1 FroyoStone worked for about 10-14 days easily without a single SOD (!!???!!) - go figure.
three things to try when you have a black / blank unlock screen / sod :
1) You know where the unlock swipe is. Just swipe with your finger on the black screen and screen turns on. (even if you can't see it)
2) Try waking up the phone by yes/send/call button instead of no/end/hangup button.
3) enable menu button unlock from cyanogen mode (if you have it) and unlock with the menu button.
Please provide feedback if any of this works for you in the long term.
memin1857 said:
three things to try when you have a black / blank unlock screen / sod :
1) You know where the unlock swipe is. Just swipe with your finger on the black screen and screen turns on. (even if you can't see it)
2) Try waking up the phone by yes/send/call button instead of no/end/hangup button.
3) enable menu button unlock from cyanogen mode (if you have it) and unlock with the menu button.
Please provide feedback if any of this works for you in the long term.
Click to expand...
Click to collapse
I loaded the JMZ dual boot application and the SOD appeared again. I tried doing what you suggested but it didn't work either. Uninstalling the JMZ dual application resolved the issue and the HD2 works like a charm with Froyo2.2 by Darkstone.
talha984 said:
I loaded the JMZ dual boot application and the SOD appeared again. I tried doing what you suggested but it didn't work either. Uninstalling the JMZ dual application resolved the issue and the HD2 works like a charm with Froyo2.2 by Darkstone.
Click to expand...
Click to collapse
Can you explain how to uninstall the JMZ dual application? Sorry. T__T!
I'll share my experiences:
The SODs have been my main problem with the builds. Everything else works just fine. I have also formatted and re-formatted the sd card and so on... nothing helps.
I tried Finger Lock screen from the market... after installing it I have not had a single SOD or reboot during charging. If I disable it, it is just a matter of time when the next SOD will happen.
And another good thing: it never gets stuck waiting after button press like the regular one, instant response.
But god I hate that lock screen... hope to find some other that makes my phone work like this one.
I have mentioned this in another thread but hopefully someone capable of understanding what is the difference between these screens can also figure out how to fix it .
.BetaBoy: My HD2 is setup pretty much in the same way as yours (in your sig) however I am running 2.11 radio and get the "blackness," as I call it often. I am updating my radio to match your's from your sig and hope it works. If it doesn't, any other suggestions you might have would be greatly appreciated.
thanks.
****monkey said:
I'll share my experiences:
The SODs have been my main problem with the builds. Everything else works just fine. I have also formatted and re-formatted the sd card and so on... nothing helps.
I tried Finger Lock screen from the market... after installing it I have not had a single SOD or reboot during charging. If I disable it, it is just a matter of time when the next SOD will happen.
And another good thing: it never gets stuck waiting after button press like the regular one, instant response.
But god I hate that lock screen... hope to find some other that makes my phone work like this one.
I have mentioned this in another thread but hopefully someone capable of understanding what is the difference between these screens can also figure out how to fix it .
Click to expand...
Click to collapse
What finger lock screen are you talking about>? i need it
First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...
Hey guys, I seem to have a problem with my A4g.
Basically, once in a while, the screen starts to press on its own. Usually towards the middle of the screen, so if i go to text message, keys such as "F" and "S" get rapidly hit on their own! Turning off and on the screen helps fix it, but sometimes i need to restart the phone altogether.
Anyone else having this issue?
I'm on Gingerbread with Unlocked bootloader and rooted but this problem has been around since i got the phone.
we'll need to know a little bit of information on your phone.
are you running stock software? (for instance, i'm using Ninja Speed Freak 0.4.5 and Faux's custom OC kernel)
have you dropped your phone recently?
has your phone gotten any contact with water recently?
do you have any suspicious third party apps installed?
bigdog_nick said:
Basically, once in a while, the screen starts to press on its own. Usually towards the middle of the screen, so if i go to text message, keys such as "F" and "S" get rapidly hit on their own!
.
Click to expand...
Click to collapse
OMG! its like a spirited game!!!
Sometime it happens to me, the screen to become unresponsive..
And i turn of the screen and on and its gone.
The thing happened at you it happens only with raindrops.
And rarely FP sensor dont work, so i reboot..
Are you stock? Or on a custom rom probably ?
As i wrote in OP, i'm running on the AT&T Unlocked bootloader 2.3.4 found here:
http://forum.xda-developers.com/showthread.php?t=1182526
This problem isn't due to the rom, it happened to me before the update too.
Ive only dropped this phone once since May and it was on carpet.
have you tried doing a factory reset? quick google search brought this up for me, but i'm not having the problem so i can't test it out myself for ya =\
http://www.atrixforums.com/forum/motorola-atrix-general-discussion/889-screen-issues.html
That was the first method i tried 3-4 months ago with no luck.
I can't do that anymore because of the unlocked bootloader
Im using the miui-ndt development v34.0 by langthang.
everythign has been working flawlessly for a month until a few days ago when i noticed that my phone will not respond once i get to the lockscreen to access my phone again. In the beginning it would work after couple of times of me pressing on the end button to turn the screen off and on but now the problem has become more serious when i have to try almost a minute for the lockscreen to unlock.
the funny thing is once i get the lockscreen to respond and unlock the phone works flawlessly. soon as i press the power/end button again and put it in my pocket and take it back out to use my phone, the phone fail to unlock the lockscreen. I know that the process of the phone is working because i can see the time chance and battery percentage and reception work. can anyone shine light to this situation?
Anyone ?
Sent from my HTC HD2 using XDA App
ive not used a MIUI rom but disabling Compatibility Mode in Spare Parts has helped myself and others with very similar/exact problem.
good luck