I've tried several different builds by several different devs, and within about 5-10 minutes of any boot my phone will stop waking up from standby properly.
I hit the power button and everything lights up like it's going to wake, including the backlight on the screen, but 9 times out of 10 it'll just hang like that. Sometimes if I leave it for a minute (literally 60 seconds minimum) it wakes up by itself but usually it just goes back to sleep. The only way to get back into the phone is to pull the battery and go back to winmo.
It's really irritating because I loved my G1, and having Android on my HD2 would make it a serious contender for the best phone I've ever owned.
Has anyone else had anything like this? If it matters my current ROM is the latest build of Energy ROM and my radio is 2.12.50.02_2, I've tried other radios and they don't seem to make any difference.
tarwedge said:
I've tried several different builds by several different devs, and within about 5-10 minutes of any boot my phone will stop waking up from standby properly.
I hit the power button and everything lights up like it's going to wake, including the backlight on the screen, but 9 times out of 10 it'll just hang like that. Sometimes if I leave it for a minute (literally 60 seconds minimum) it wakes up by itself but usually it just goes back to sleep. The only way to get back into the phone is to pull the battery and go back to winmo.
It's really irritating because I loved my G1, and having Android on my HD2 would make it a serious contender for the best phone I've ever owned.
Has anyone else had anything like this? If it matters my current ROM is the latest build of Energy ROM and my radio is 2.12.50.02_2, I've tried other radios and they don't seem to make any difference.
Click to expand...
Click to collapse
Ok i will try to help you as much as i can!
First format you SDcard from withing windows mobile.
Update your radio to 2.15.50; it works better for me (http://www.mediafire.com/?b1je19xg58r06s9)
Install some of MDJ builds, they are fast at wake up!
Finally do not rush the system by pushing the power button many times; only once, and if you feel that it's not waking up keep pressing it like if you will shut it down, sometimes this trick worked for me and let it take some time to wake (usually up to 10 or 15 sec not more)
Good luck
what i do is just press the end call button a **** load of times like 10 times really fast and then it wakes up.
but this only happens like the first day of booting android for the firsst time
can anyone cast anymore light on this issue ( no pun intended)
as in a technical explanation as to why it happens so often and with so many builds and different radio's and WM Roms?
it really plagues me, as the phone would be so awesome if i could find a build that would wake when pressed and not when it feels like it ?
help
I've had success with an app called WidgetLocker Lockscreen and have had almost no problems waking up by pressing the homebutton (problems waking maybe 2x in 2 weeks).
If you dont find any solution...then try testing it with different SDcard.
+1
I have the same issue, tried many roms (winmo and android) - think they are all the same... Also tried a different memory card. Would be good to have a proper solution/reason...
any devs shed any light ???
position your HD2 in front/close to a bright light then press end call/power button.
It should wake up.
I also have the same issue, I'm beginning to think its a H/W Related issue, me and my colleague have the same device, same HSPL, Same radio, same base rom, same android build, same SD card. I have the issues, he does not.
I've also tried endless combinations of SD Cards, builds, radios, and so on, the funky wakeup issue still shows up at least twice a day, annoying as hell.
None of the "Tricks" has solved it for me.
I've found dozens of posts regarding the same issue (Including a thread I started on my own) and still nothing.
Most devs seem to ignore the issue cause apparently Quote: "Only about 1% of the users have the wakeup issue" , so I guess its not considered critical for anybody to worry about.
I never had this problem, then with a new sd card it started happening but only if i tried waking it up just after it had gone off. So looks like its the sd card...
Related
I started noticing a few days ago that when my phone is in stand-by, and I turn it on, pressing the power button, it takes longer than usual to wake up, like 5 seconds.
I don't remember this happening before. Last time I upgraded the ROM was back in November. I have VP3G 3.62.3, and everything was always working fine. I also use Slide2Unlock, and at first I thought this was causing the lag, because of a memory problem, maybe it was taking too much memory to be loaded, or something like that could have changed. But no even if I disable slide2unlock and use it normal, it still happens. I even re-loaded the ROM, without anything else (the lite version), but no matter what, when I turn the phone off (make it sleep), whenever I try to turn it back on, the lag is always there.
Anyone else experiencing this? Do you know of any cause or solution?
Thanks very much.
My phone does the same thing, but it's no big deal. Occassionally I'll hit the button twice thinking I didn't hit it right the first time, but it's really not a big deal.
Sounds normal, but there are some cooked roms that are quicker then others depending on addons (the TNT rom is one of them for me). If you have not already, try using 'startclean', 'hibernate' and 'cleartemp' apps daily to free up memory, cache, etc...
im wondering if its just me..
most times, when the phone comes out of sleep, after i slide to unlock, it just hangs. i dont even get to see the clock, sometimes, it just shows a black screen, and sometimes, all i see is the lock screen..stuck.
i can push the start button, and it would work as normal, but i cant go home.. and everything else related to sense...music, settings, message, ..just crashes.
i always have to reboot phone to get it back to normal.
could there be something making it crash? ..and does it happen to anyone else?
yes it happens to me from time to time. sometime HD2 just lies on my desk and 'fall asleep'... cannot turn on the screen though all the buttons light up.
when this happens i have to call from my HD to turn HD2 on and when it's on, it's unstable, and i have to reboot it.
same problem
I have exactly the same problem. it just crashes for no reason. sometimes when WiFi is on. sometimes after I synchronize. sometimes if only plugged out of the charger.
it was in version 1.48 and kept happening even after I upgraded to 1.66
I hope this has a fix or something or atleast a way to restart sense because the Windows button works, phone works, except the volume, the turn off and the settings in the start menu..
help!
thank you in advance.
Same problem here. Freezes at the lock screen and the lights appear from the buttons. Occurring with worrying frequency now. Twice in the last three days. Any ideas?
folks, do report your issues here .. i have a feeling that this is a known hardware issue by HTC and they are just keeping veru quiet about this.
http://forum.xda-developers.com/showthread.php?t=596484&page=15
mercernathan said:
Same problem here. Freezes at the lock screen and the lights appear from the buttons. Occurring with worrying frequency now. Twice in the last three days. Any ideas?
Click to expand...
Click to collapse
Same thing here, it use to happen 2 time in 2 months since new, but ever since i upgrade to 166 is happening everyday
I am really really disappointed with HTC HD2 he came out with some many bugs that i am after 2 months of hade and love affair really considering divorcing ones for all.
Nice looking screen but no reliable atall enough is enough
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. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
I'm having temporary screen freezes when I want to take out my HTC HD2 with tytung's ICS version. When I press the buttonss they light up but the screen stays black. I can still receive phone calls and connect it to a PC, where the PC recognizes the phone. Sometimes after 20-30 minutes the wakes up like normal when I press a button.
Does anyone know the cause of this and is there a solution?
Thanks in advance.
Has your screen been unresponsive lately ?
read this: http://forum.xda-developers.com/showthread.php?t=993787
I think your end button .. is dying?
It is not just the end button. None of the buttons give a response although they light up when I press them. Sometimes after 10 minutes or half an hour the phone is responding again.
6384erwin said:
It is not just the end button. None of the buttons give a response although they light up when I press them. Sometimes after 10 minutes or half an hour the phone is responding again.
Click to expand...
Click to collapse
Does this happen on every ROM? Also try flashing another kernel. It may be driver or hardware related.
It also happened with the previous ROM from Tytung. I disabled wifi for 2 days now and the problem has not occured yet. Normally it occured every day. Can it have something to do with WIFI?
i have had the same issue, and for me the only solution was to flash a new rom. if you're going to do that: try miui, i think it is very good(as soon as you've fixed all the problems with it it works perfect)
Did you try a clean install with task 29 before?
I only did the task29 the first time I started flashing a rom. After that I only changed the partition size once and updated from the zip file. What will another task29 do?
I have wifi disabled now for 4 days and haven't had the problem again. It seems that other people also have this issue, but is there no solution?