I've got a Droid X running the stock OS; haven't rooted it or installed anything except a few apps from the store. Lately, the screen lock hasn't been very reliable.
I work in a lab where we're not allowed to have cell phones, so they all sit in a metal cabinet outside the room. I put it in airplane mode to keep from draining the battery, and I use the screen lock with a 2 min. timer and a PIN in case someone decides they want to fool with it while I'm working. The last couple days, sometimes when I wake the phone up after letting it sit awhile, it'll take me right to the last screen it was on without requiring the PIN to be input. Rebooting the phone doesn't seem to help.
Anyone else seen this?
Did you do a factory reset after upgrading to 2.2? Solves a lot of problems...
I got the phone with 2.2 already installed. You think it would be worth trying anyway?
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
my nexus 4 is behaving abnormally... the lower part of the screen(1 cm) is unresponsive to touch(tested with pointer location) and sometimes out of the blue the touch input for the entire screen stops working and works after a couple of lock/unlock and the sometimes the phone starts pressing anywhere by itself.... I was running pa latest version... it was working fine ... so i restored the phone to the old pa since i need pie because bottom screen not working= no navbar.... it still didnt work and screen with similar problems. have anyone experienced something like this... is it something with the screen or other hardware parts ... help!
i had this issue with the bottom right side and a irresponsive touch screen at times, it was fine at beforehand, i backup and reflashed and it worked, using PA. it depends if the phone was fine for months before or something that has happened when you first used it. try restore to stock rom and kernel
If you've already done a factory reset, it's likely a hardware problem. You'll probably have to have someone repair it. If you're really desperate, I guess you could try putting it in the freezer for a few minutes, and seeing if that fixes any connection problems. That might just make it worse/cause other problems though. It works with hard drives on occasion.
Hello,
ok, I gave up on moving APPs to external SD on ICS 4.0.3...
Here is my new issue in a nutshell....
I updated to ICS 4.0.3 with no problems and everything worked fine for months. Within the last month, the tablet has developed a random problem, usually 30-90 seconds after it boots, where it may or may not freeze up (i.e. the screen is unresponsive) and I have to turn it oss and reboot and hope it doesn't happen again.
Sometimes this happens one or two times in a row and then its fine, sometimes it will happen five times or more, and then the next boot it is fine, sometimes it works fine on the first boot.
I have removed all kinds of apps and media to make sure I have lots of room and curently have about 5G free. but that didn't fix the issue.
I looked into the GPS txt files being left behind and made sure they are removed regularly, but that doesn't help the issue.
I used a Device Info APP to display what is going on when this happens, and while it doesn't show any APP or process I can see as the culprit, the CPU is being maxed at 100%?
It also seems to have "something" to do with the WiFi, as when it "locks up" the WiFi icon in the tray goes away and when I go to settings it seems stuck trying to turn off the WiFi. But at other times then the WiFi is working fine?!
Also, sometimes if I let it go to sleep for too long, when I wake it up this will happen..
SO... anyone got a clue what this could be?!
ALSO, the screen would not turn on when i get on a call and cover the proximity sensor, Only way to come back is to reboot it.I dont know whats going on with my phone but lately the knock on has gotten worse and it's pissing me off. Past week, only way to turn on screen is with the power button and when it wakes up its only for a few seconds, then relocks itself. Knock on will work randomly when it feels like it but really its only worked like 10% of the time the past week. I've checked for any new apps, removed them even though they were official. I dont get it. I have xposed and g2 xposed. Uninstall them. problem still happening. I'm on Rooted Stock 11a.
anybody else experience this?
Amazingly, I googled the phone call screen off problem and found a workaround until it really dies I guess.
Make pressure at the top of the phone by the spaker,sensors area, squeeze it there and poof its working great again. So weird, somehow the inside gets apart from itself? definitely a hardware problem that seems pretty popular with this phone.