Related
I know there are hundreds of threads and articles posted about HD2s freezing with the lock screen but this issue seems different to me. My problem is that whenever I lock the phone the touch screen will freeze entirely. I thought a work around may be to install a different lock screen. After installing that I can get past the lock screen but the touch screen still is not responsive. I have no idea what to do. I already did a hard reset and it still does it. I would like to add that it is completely consistent. It happens every time without fail. In order to even use the phone I have to pull the battery and I get one use out of it before it locks and I have to pull the battery again. Does anyone have any suggestions? I would really appreciate it..
Update: I flashed the original ROM to my phone and the freezing problem still exists.. I have no idea what to do at this point.
Update 2: Narrowed down the problem to being the physical "power/end/lock" button. If I slightly press it but not fully it will go to the honeycomb style menu with all the apps. If I press it fully the screen will go out like normal but then if I restore it, the entire screen is locked up. Nothing will work after that until I pull the battery.
I've directly linked the issue with the power button. I dont know why all of a sudden the power button would have a different function. The work around I found is while the phone is locked and the screen is off I can press the green button to unlock the phone and the touch screen will then function. If I use the power button it will remain frozen. Any ideas what happened?
Hello,
I got some bad news for you, this issue is actually related to the digitizer (hardware) not software. What i would recommend is called HTC for a repair and send it in, it is covered by warranty, hopefully you have warranty.
A lot of people are having this issue, no-one yet has been able to pinpoint the cause, but here is the link a thread with similar problem:
http://forum.xda-developers.com/showthread.php?t=854165
Luckych
Thanks for the reply. I do not think I have a warranty on this phone considering I bought it privately. Ill talk to Tmo and HTC and see what I can do. Just a theory, I may be wrong. But I live in PA and its been getting below 20 here lately. I noticed today that my work around didnt work when I was outside working on my car. Then I went inside and used a blow dryer to heat up the phone and it started working again. The end button didn't function properly but I could unlock the phone with the green send button. Perhaps the cold weather is shorting out people's digitizers? I don't really know how they work so that's why i said its only a theory. I bought this phone in the spring and didnt have an issue until now when it started getting really cold.
Hey guys, per Dalingrin's posts in the CM7 Dev or General thread, he's been unable to reproduce Sleep of Death. A lot of folks have seen it but it's hard to pin down a pattern in forum posts, so I created a google spreadsheet form to track builds and configuration people are using.
Dal has looked over the form and gives his thumbs up, so let's fill it out! The idea here is to fill out for EVERY SOD you have, filling out the latest information. If you remember the details, feel free to fill out recent SOD info.
If anyone sees anything I should update/modify or add, let me know. Also, if anyone wants an Excel file from either or both forms for analysis, please let me know and I'll send it. One thing to note here is it's impossible to see folks who are saying No on the Results form vs their answers, so the raw data could be useful.
Anywho, link is here, please fill it out guys! This form is to query you on what build you're using and how you have some things set up. Please fill it out every time you have SOD, and folks who do NOT have SOD are also encouraged to fill it out!
https://spreadsheets.google.com/spr...ormkey=dFZrS0tOdTVwZ0pnaWpqSTQwaDFmcmc6MQ&ifq
And here's a summary page of the responses so far:
https://spreadsheets.google.com/viewanalytics?formkey=dFZrS0tOdTVwZ0pnaWpqSTQwaDFmcmc6MQ
New Form!
And there's also a second form to track some answers to Widgets and Apps that sync/run all the time below. I did set the answers as No/Yes so you should just be able to click the ones you have installed/use and the rest you can just skip over and it'll default to No. Probably only fill out this second form once, as this is just to query the apps/widgets folks are running.
I am looking for feedback on additional apps, but since I have SOD on this set of "stuff" I figure it's good enough to start with. Honestly my confidence that this will be what figures out SOD is fairly low, but it should just take a few minutes, unless you're really aligned with me and have a bunch of the same stuff
Like the previous form, folks who have and have not experienced SOD are encouraged to submit their data.
Appreciate it guys, hopefully it continues to help out the CM7 gang understand why we're seeing SOD.
https://spreadsheets.google.com/spr...US&formkey=dHRMVklTSTgzT1htRkZRYWFfTmQ5WHc6MQ
And here's the direct link to the results so far..
https://spreadsheets.google.com/viewanalytics?formkey=dHRMVklTSTgzT1htRkZRYWFfTmQ5WHc6MQ
Semi-informative form changelog for Form 1 (Build and Settings)
Added Nightly 83, 84. Added non-default OC kernel for folks using 1100 or such, added eMMC vs SD Install, and added SOD Yes/No so folks NOT having the issue can provide their data too
Added N/A to battery questions for folks NOT having SOD, added Never to frequency of SOD question for No SOD folks. Also modified existing questions to say SOD or Normal Sleep.
Semi-informative form changelog for Form 2 (Widgets and Apps)
TBD
thanks khaytsus, great idea. I hope this will help us all with SOD and no deep sleep
May I also suggest that people who are experiencing SODs:
1) Press the power button once to turn the device on.
2) If the screen does not turn on, DO NOT PRESS THE POWER BUTTON AGAIN... just let the device sit for a while -- at least several minutes
3) After about 5 minutes, try pressing the power button again.
There is evidence to suggest that at least some subset to of SODs are actually the device just taking an extraordinarily long time to wake -- long enough for people to assume it's dead and reboot.
Normally I can wake the device by pressing power or "n", but in my most recent apparent SOD, the power button did not wake the device, nor did the "n" button. After about 5 minutes, the power button worked. Once, it woke about 3 minutes after pressing the power button.
sinanju said:
May I also suggest that people who are experiencing SODs:
1) Press the power button once to turn the device on.
2) If the screen does not turn on, DO NOT PRESS THE POWER BUTTON AGAIN... just let the device sit for a while -- at least several minutes
3) After about 5 minutes, try pressing the power button again.
There is evidence to suggest that at least some subset to of SODs are actually the device just taking an extraordinarily long time to wake -- long enough for people to assume it's dead and reboot.
Normally I can wake the device by pressing power or "n", but in my most recent apparent SOD, the power button did not wake the device, nor did the "n" button. After about 5 minutes, the power button worked. Once, it woke about 3 minutes after pressing the power button.
Click to expand...
Click to collapse
thanks sinanju, but I have read this somewhere before to, but my nook is set to go back to sleep in one minute. so how does this work? does the back to sleep clock setting only start after a full wake. but this is still a bug. a 5 min wake up is just as bad as a true SOD
maybe we should call it "SO5MW" sleep of 5 min wake
at the risk of cluttering a dev thread,
Hey khaytsus, nice job!
Hopefully this will help clear up sod or sod-a-like or sod assumed issues. Lol
A couple of things:
1. Need to add all builds that are compatible with kernel .32 like N83 and N84. I'm on N83 and I just got my first confirmed SOD.
2. Not everyone maxes out their clock with the OC kernel. I keep mellow at 1100.
Sent from my NookColor using XDA App
You might want to accommodate those of us that aren't having the problem as another data point. I am running what I perceive as the same exact same setup as those with the problem and I don't have it.
Just a suggestion.
Moxie3000 said:
A couple of things:
1. Need to add all builds that are compatible with kernel .32 like N83 and N84. I'm on N83 and I just got my first confirmed SOD.
2. Not everyone maxes out their clock with the OC kernel. I keep mellow at 1100.
Click to expand...
Click to collapse
Added 83 and 84.. For the kernel OC I didn't want to put TOO many choices, but I've added one for OC Kernel, not-default speed. Hopefully people put it in the notes, but I have a feeling it's more around OC/not OC vs frequencies. Good info either way!
Awats said:
You might want to accommodate those of us that aren't having the problem as another data point. I am running what I perceive as the same exact same setup as those with the problem and I don't have it.
Just a suggestion.
Click to expand...
Click to collapse
Good suggestion, only problem is that the numbers wouldn't mean much. So if I had daily SOD's (I don't, like 2-3 a week) and you never have SOD, you'd have one "No" against my 7 "Yes". However I think you're right that if you have the same config as most other people have and yet you never have SOD there's some other variable to consider. I've added a column for SOD Yes/No. Thanks for the suggestion!
I've also added a question about eMMC or SD, although I don't think it matters, but regardless it's one more thing to capture. You suggested it too, by your signature
Thanks for doing this, it's interesting to read the results so far to see what people have been experiencing.
I think you were right (in an earlier post in PBD thread) and I was possibly not waiting long enough between power button presses to see if my Nook would wake up by itself -- while I was trying for several minutes, I may have been inadvertently turning it off/confusing it during an SOD by trying to hard boot it too soon after previous hard boot attempts.
My nightly 85 install isn't SODorPDBing until ~20% so it'll be a while till I can add information to your OP, I'm afraid. (at 89% now).
Yesterday I had a SoD too. I'm on nightly 87 with dalingrin 5/23 at 1.1ghz. Just one thought from my side, couldn't it be an overheating problem due to overclocking? I wasnt able to turn it back on unless I waited some time....
Sent from my Nexus S using Tapatalk
TubeShaped said:
Yesterday I had a SoD too. I'm on nightly 87 with dalingrin 5/23 at 1.1ghz. Just one thought from my side, couldn't it be an overheating problem due to overclocking? I wasnt able to turn it back on unless I waited some time....
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I don't think having to wait is the norm with SOD. I don't ever have to wait. Just hold the button until it powers all the way down, and then turn it right back on. Also, my temp doesn't seem to fluctuate much. It's always between 80 - 89 degrees Fahrenheit, and I've been overclocked since January.
philburkhardt said:
I don't think having to wait is the norm with SOD. I don't ever have to wait. Just hold the button until it powers all the way down, and then turn it right back on. Also, my temp doesn't seem to fluctuate much. It's always between 80 - 89 degrees Fahrenheit, and I've been overclocked since January.
Click to expand...
Click to collapse
set wifi to turn off when the screen is off, or manually turn it off when you put it to sleep and see if you can get it to happen then.
chisleu said:
set wifi to turn off when the screen is off, or manually turn it off when you put it to sleep and see if you can get it to happen then.
Click to expand...
Click to collapse
My wifi is set to turn off when the screen is off. I have had it set like that for about a week. I still get SOD.
EDIT: n91 is up! Lets see if it changes anything.
I updated to 91 and last night. I shut it off at 58% and it was at 7% this morning. Before with 86, it's might lose 1%. I do notice that wifi is on now when I hit the button whereas before it would take 10-15 seconds to come on. Hmmm, maybe it's set to keep the wifi-on during sleep. Not sure why it would have changed.
I need to play with it more but if it continues I will drop back to 86.
EDIT: And now I don't. Dunno ...
I was not suffering with SOD on any nightly. I flashed n91 yesterday and reflashed dal's 1.2 emmc kernel. Today I had three SOD's.
Normally I use the power button to wake up my nook, each of the three SOD's I had today I pressed the N button.
I have tested a little since the three SOD's and if I press the power button the nook comes to life. If I hit the N button nothing, subsequently hitting the power button does nothing. Could be nothing but thought I would report it.
Leaving the Nook sit for 5 minutes after an SOD did nothing but kill 5 minutes.
update:
I reflashed the rom and kernel and it seems fine now.
painter_ said:
I was not suffering with SOD on any nightly. I flashed n91 yesterday and reflashed dal's 1.2 emmc kernel. Today I had three SOD's.
Normally I use the power button to wake up my nook, each of the three SOD's I had today I pressed the N button.
I have tested a little since the three SOD's and if I press the power button the nook comes to life. If I hit the N button nothing, subsequently hitting the power button does nothing. Could be nothing but thought I would report it.
Leaving the Nook sit for 5 minutes after an SOD did nothing but kill 5 minutes.
Click to expand...
Click to collapse
Hmm, I'll try waking mine with Power button, I always wake it with the N.
I've never experienced one and I only wake using the power button. Using nightlies and Dal's latest.
Sent from my NookColor using Tapatalk
SOD is still alive
how is the SOD and deep sleep issues with everyone on n91 or higher? Im on n93 and is still getting SOD and no deep sleep.
n94 I see "Wifi: Minor change in SDIO release behavior" in the change log. does anyone know if this is something to do with SOD. does the SDIO release behavior have something with the nook waking up?
Im starting to think SOD has something to do with the recovery of the screen after a sleep. I mean the system is up and running I can hear the beep sound when I press the volume buttons and I the hear the notification sound so I know the system is up and running it only the screen that is not. the waking up of the screen may have some kind of conflict with the wifi or something else waking up at the same time. just my guess. not sure.
cm7 stock n93
boxcar8028 said:
how is the SOD and deep sleep issues with everyone on n91 or higher? Im on n93 and is still getting SOD and no deep sleep.
Click to expand...
Click to collapse
91 and 94, deep sleep is fine for me...
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Pig Vomit said:
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Click to expand...
Click to collapse
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
ECOTOX said:
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
Click to expand...
Click to collapse
No mods whatsoever. Completely stock, not rooted.
Hi guys,
the previous days, I've been having a weird problem where sometimes, the back button would be less responsive for some time.
Since I've never experienced this before, and couldn't find relevant information on this forum about this, I thought I'd ask if anyone else has experienced it.
It took me several tries to activate the 'back' capacitative button, and in a couple of instances I just mashed the 'home' button to get out of there instead.
Now whether this was due to high processor usage or malfunctioning hardware is hard to say... BetterBatteryStats didn't show anything weird even though the previous couple days battery duration was slightly less than expected.
I didn't install any new software, just some updates of existing programs.
So, questions:
- for those who know about the hardware of cap. buttons: what could this problem be due to?
- has anyone experienced the same? If so, what did you do?
thanks
Yes I have had this same problem with it, because i gave my phone for service,whenever i got it back its working perfect.Man who was serviceing it said there was some dirt inside like metal filings so he just clean it.
hey bro check this thread.
http://forum.xda-developers.com/showthread.php?t=1272663 same problem although different situations. hope it helps!
dryhte said:
Hi guys,
the previous days, I've been having a weird problem where sometimes, the back button would be less responsive for some time.
Since I've never experienced this before, and couldn't find relevant information on this forum about this, I thought I'd ask if anyone else has experienced it.
It took me several tries to activate the 'back' capacitative button, and in a couple of instances I just mashed the 'home' button to get out of there instead.
Now whether this was due to high processor usage or malfunctioning hardware is hard to say... BetterBatteryStats didn't show anything weird even though the previous couple days battery duration was slightly less than expected.
I didn't install any new software, just some updates of existing programs.
So, questions:
- for those who know about the hardware of cap. buttons: what could this problem be due to?
- has anyone experienced the same? If so, what did you do?
thanks
Click to expand...
Click to collapse
I have an unresponsive menu button. it has always been like this but I don't really mind it. a problem with the back button would be much more annoying though.
Everytime I go to use the on/of button for anything, I barely press it and sometimes it doesn't work, other times I quickly press it and it thinks I held it for the menu to come up to reboot or power down. But most of the time... It just reboots on its own if I use the switch. Any way to by pass it? The switch itself I think is just super sensitive, I barely have to even touch it. I've taken phone apart and cleaned around the switch. I'm trying to hold out till the Galaxy S 4 comes out... Hopefully soon!!
Sent from my SGH-I777 using xda app-developers app
Although I can't offer a fix... The galaxy s4 goes for preorder for at&t on the 16th of this month for $250 I believe. And T-Mobile is releasing it for $99 on may 1. I think that is all that is currently known about any galaxy s4 release dates. Hope I kinda helped in any roundabout way.
Galaxy S3 T999 rooted and flashed more than daily.
Brand new off contract nexus 4. 250 dollars. If you can deal with the limited internal sd card space and don't have to have your entire music collection with you at all times like some people here lol.
Free Apps to Help
I have the same issue, can't touch the power button. I smack the button a few times to get it to behave. I have installed the following two free apps so I do not have to touch the power button again.
Auto Screen On.
Button Savior(Root)
I am not allowed to post links to the apps, but they can both be found on Google Play.
You have to have root and you have to read the instructions for each app.:good:
Thanks to everyone, I am rooted and running CM9, so that shouldn't be an issue and I'll check into those apps. Just need to make til I can upgrade to the GS4. Thanks for the dates cuz now I have an idea of how long and I'll go order it that day. If that's the preorder, then when is the release date I wonder?
Sent from my SGH-I777 using xda app-developers app
I tried and am using "auto screen on" works prefect!! Using the proximity sensor instead of on off button. Thanks again guys, always seem to find help on XDA!
Sent from my SGH-I777 using xda app-developers app
I think it's absolutely fascinating how we both seemed to develop the problem at the same time. Could be that many others will soon suffer the same problem. Although I'm definitely going to look into those apps now, I found a temporary fix myself (and it could just be coincidental anyway). I pulled the battery out, pressed my power button repeatedly about 100 times, and now I'm able to use the power button again without it sticking and causing this problem.
The weird part is, that physically, the external button wasn't stuck at all. I could still click the button as many times as I wanted even while "stuck" symptoms appeared on my phone, like the power menu coming up, or a reboot. My guess is that the hardware problem lies somewhere between the physical button and the electronic circuitry within, but I haven't actually stripped down the phone and looked inside. But perhaps jamming the button a hundred times helped decrease the chance of the internal "signal relayer" getting stuck.
I had a similar issue with some keys on my laptop after a little kid played with it and got my keys messed up. Outside button was ok, something beyond that was not (so pressing "s" once would lead to 40 s's appearing on my document). Repeatedly pressing ended up helping out quite a lot.
Nonetheless, this may end up being a very useful thread for others later on.
My GF i777 was having the same issue reported here. I just sent it into mobiletechvideos.com and had the power button on the mother board replaced for 40-50 bucks and it works perfectly now. I would suggest using them if you want to keep your i777 working
bhatbhai said:
I think it's absolutely fascinating how we both seemed to develop the problem at the same time. Could be that many others will soon suffer the same problem. Although I'm definitely going to look into those apps now, I found a temporary fix myself (and it could just be coincidental anyway). I pulled the battery out, pressed my power button repeatedly about 100 times, and now I'm able to use the power button again without it sticking and causing this problem.
The weird part is, that physically, the external button wasn't stuck at all. I could still click the button as many times as I wanted even while "stuck" symptoms appeared on my phone, like the power menu coming up, or a reboot. My guess is that the hardware problem lies somewhere between the physical button and the electronic circuitry within, but I haven't actually stripped down the phone and looked inside. But perhaps jamming the button a hundred times helped decrease the chance of the internal "signal relayer" getting stuck.
I had a similar issue with some keys on my laptop after a little kid played with it and got my keys messed up. Outside button was ok, something beyond that was not (so pressing "s" once would lead to 40 s's appearing on my document). Repeatedly pressing ended up helping out quite a lot.
Nonetheless, this may end up being a very useful thread for others later on.
Click to expand...
Click to collapse
I am having this same problem. I started a different thread a few days ago about power button issues that at the time I attributed to the recent software update. But it was apparently just very coincidental, and after some tinkering I was able to get the button working using similar methods described in this thread already. After I got it working again, I rooted and successfully installed AOKP 4.2.2, but now when I manage to get the power button to send a signal it pulls up the shut down options screen and then restarts about ten seconds after that. I assume it is still the same hardware issue, but since the restarts only began occurring after flashing the custom rom I can't entirely rule out the possibility that it is some how related.
jmeas said:
I am having this same problem. I started a different thread a few days ago about power button issues that at the time I attributed to the recent software update. But it was apparently just very coincidental, and after some tinkering I was able to get the button working using similar methods described in this thread already. After I got it working again, I rooted and successfully installed AOKP 4.2.2, but now when I manage to get the power button to send a signal it pulls up the shut down options screen and then restarts about ten seconds after that. I assume it is still the same hardware issue, but since the restarts only began occurring after flashing the custom rom I can't entirely rule out the possibility that it is some how related.
Click to expand...
Click to collapse
If you flash back to stock and you still have the button problem, then it is almost certainly hardware. Did you do that yet?
I actually just flashed AOKP a few days ago. Instead of using one of the applications above, which either drained my battery (auto screen on) or wasn't entirely convenient (button savior), I've got a different set up.
In rom control, activate "volume rocker to wake." It's not a hundred percent, oddly, but it gets the job done. This will help with screen on.
For screen off and power menu, I added a navbar with the second smallest height (30 dpi?), with the power button on it. Now I permanently have a the ability to turn off my screen, from whatever I'm doing, with just one click. Long pressing it gets you the power menu.
As a side note, I added screenshot to the power menu so I wouldn't have to hold my power button for that either. But no, I haven't tried using the nav bar power button with volume down for screenshot, because I'm an idiot and just thought of that now.
Sent from my Nexus 10 using Tapatalk HD
creepyncrawly said:
If you flash back to stock and you still have the button problem, then it is almost certainly hardware. Did you do that yet?
Click to expand...
Click to collapse
I haven't had the opportunity to do that yet. The restart issues may have begun when I flashed the Siyah 4.3.3 kernel before installing the rom, but I probably won't have the chance to tinker with it until the weekend.
Edit: I have also noticed that I can only reliably use the volume buttons to wake my phone up from sleep when it is plugged in.
Weird, I just started getting this problem today, too. Kinda weird how this all happened to us in the same month
Add me to the list of those whose power button suddenly and mysteriously died. Opened up an email Sunday 4/14, the phone rebooted on its own, and when it restarted the power button no longer worked. My suspicious is it's somehow software/rom related. I'm running Task's AOKP 4.2.2 (4.1.13), for what its worth. If everyone with the issue posts their experience maybe we can figure out what's going on...
Mine started doing the same back in March. Pressing the power button would cause it to reboot and sometimes bring up the power menu, as if I was long pressing it. Then the power button didn't want to work at all, sometimes. I tried everything I could think of, even reverting back to stock, but the problem persisted. Then I finally found that pulling the battery and pressing the power button a few times fixed the problem, for a while anyways. If I don't do it every 2-3 days, it starts happening again. I've actually seen something similar happen with notebooks before. A charge manages to build in the motherboard and the system won't power on. Removing the power supply, pulling the battery, and holding the power button for 30 seconds to allow the charge to dissipate actually fixed the notebooks. That's where I got the idea to do it with my phone. Just wish I didn't have to do it every couple days.
My power button stopped working a couple of days ago and I tried this solution http://forum.xda-developers.com/showthread.php?t=1193057&page=2 post #17. Just take the phone apart, spray the power button with the electrical cleaner, and continuously pushing the button for a while (2 or 3 min). Keep the button wet while pushing it. Let it dry, put the phone back together, and start it back up. You should be able to tell whether it worked because when you put the battery back in it will not immediately start back up.