Related
Alright my At&t tilt front face buttons started to not work (i could only use the arrow buttons and the ok button) and my keyboard stopped working but the arrow keys would. i upgraded the rom after calling htc for help. that didnt fix a thing and now today none of the buttons work. i keep getting the PTT to come up and ask for installation and edfc keeps typing themselves on the screen. so idk if it is a software problem or if the hard ware is malfunctioning.
Damn, I got the same problem. Does anybody know how to fix this?
the same problem here... :/
same problema here.
i already tried another radio, another SPL, another ROM and nothing.
any idea?
Just updating.
Yesterday my tytn started working perfectly again, but today the same problem is occuring. I did nothing, so probably is really a hardware issue.
I have a similar problem.
Send/End + Soft Keys + Keyboard are not working. The issue is not resolved yet?
Wow, this problem just happened to me as well. I've searched everywhere on the net and couldn't find anything.
So is this a pervasive issue? Anyone with any hint as to what might be the source of the problem?
Originally, I thought it the PTT button was stuck in the PRESSED position because the phone behaves as if this button was constantly being pressed. For example my PTT button was mapped to Voice Recorder if the PTT button was held down. The voice recorder constantly comes on everytime I turn the phone on!!
1234567890
I have the exact same problem.
The only change I recently made (two weeks ago) was installing tom tom navigator.
First I thought it was a virus and I installed bull guard, but with no success.
It opens/closes the start menu every second, no buttons work apart from the directional buttons and it writes "edfc" in my textmessages when I turn on/off the screen with the power button.
Most of the time(!) this irritating opening/closing of the start menu only happens after I first turn off/on the screen (with the power button).
I saw this problem described in a post dating back almost two years ago. Someone ought to know the answer to our problems. What does HTC say about it?
I have been lucky and not had this issue yet; but I would recommend starting by flashing the stock rom from HTC. Then hard reset; that will clear everything back to original. If you still experence this after that, then you have a hardware issue. Good luck
This just happened to me this morning. I cant use any buttons and nothing is popping up. This is soo wierd cause the phone was just sitting there overnight!!
Me too...
I have been going nuts with this issue for a couple months now. Makes the phone unusable half the time. I am so disappointed to find that a ROM reload doesn't fix it!! I remapped the 6 key to none and that sort of helps but it was mapped to Voice record before and it would constantly record memos until all the memory was gone in the phone and then it would all crash from there. So frustrating.
I too get the edfc message after I reboot....
It really seems like a virus the way it acts but I guess if it is a hardware issue then it's not a virus.
Anyone ever figure anything out with this? Nothing has changed on my phone recently.
Still an issue?
Holy Toledo fellow Tilt Users. Have you ditched your half-functioning touchscreen, or have we figured out how to solve this issue.
Recently I FOUND THE SAME PROBLEM!
I am going to do what was suggested (original HTC Rom & hard reset) and will let you know if I get the rest of my keyboard back...
All buttons except for power and... NOT WORKING
Outside "Enter" buttons work but they are mapped to Windows key. ? Weird. For some reason the kaiser thinks it is something else. I do not know how it got this way, but there must be a way to convince the hardware of the existence of all my other buttons. The entire keyboard does not work.
Hard Reset & stock HTC Rom did not help. I was surprised that I could hard reset it at all since the two soft buttons are unresponsive to software.
Anyone figure this out yet?
Hi, I got the same issue today as well - Has anyone got rid of this?
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
three threads above yours.
http://forum.xda-developers.com/showthread.php?t=681723
could be a hardware issue.
Mine does this every few days.. I am still on the stock 2.1 rom.
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
It happens to me as well, but very infrequently. Maybe every few days... so it doesn't bother me enough to worry about it.
I'm on stock ROM btw.
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Hmm, my problem's slightly different. Around half of the time, I have to press the power button twice to turn the screen on. Sometimes, pressing it the first time doesn't turn the screen on, had to press the power button firmly again.
This started only recently. On stock n1 and bought it during feb.
that means that your power button is dying, like many others' (including mine)
this is the first time, it takes 2 clicks to work....than it will increase.
Expect a repair soon...
Well i am having the issue other way around. i am not been able to put my phone in stand by mode by clicking on it and it is do a hard press then i get options to shut off the phone
any suggestions what might be causing it ?
I'm happy I haven't received this problem yet
-------------------------------------
i want my yogurt lol froyo time
negroplasty said:
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
Click to expand...
Click to collapse
I am having the same issue and i wonder if you were able to find the cause for it. I have the same rom as you do on your phone
negroplasty said:
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Click to expand...
Click to collapse
I have a similar problem. When I unplug the N1 from the charger, the screen comes on showing the lock screen, and I can't get it to turn off. If I unlock the phone, however, then the power button works normally. I don't think it was doing this until recently (I bought it in January the first day it was offered and am running the stock update1 ROM).
So here is my theory if the power button is a problem then it needs to act up both ways and not only one way. right now i can put the phone in sleep mode but i can wake it up. i will post the issues on the development forum and might be able to find an asnswer to it
So seems like the issues is because of Cyanogenmod 5.0.6 because since i have flashed another rom it is working just fine. i will be doing some more testing before i can be certain
Another problem I am experiencing is when I long press the power button, it pulls up the phone options menu but also turns off the screen. It's extremely frustrating as it does this quite frequently; right after I power on the screen again and unlock the device it works properly every time - so much so that I am convinced this is a software issue.
I am now running froyo, rooted with Cyan's minor root patch. I can also say for sure I experienced the same problem on CM 5.0.6, but it definitely occurred less frequently.
Am I alone here?
di2356 said:
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
Click to expand...
Click to collapse
I just started having this problem after upgrading to 2.2.
I have this every so often. But sometimes wonder if it is flyscreen doing it
You guys should all just be running the app no lock to take the power autumn out of the equation.
Ahhhhh! I just need trackball wakeup!
I have a similar issue where my screen will turn on but will be unresponsive. When i turn it on and off, the backlight jut comes and goes. If it times out it won't turn back on for a bit(the backlight will come on still).
I just wiped my phone, hoping that'll fix it since it only started happening on a regular basis since I updated to Froyo
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
ok good, me too!
was just looking for this topic.
mine doesnt always turn anything on at all. sometimes the light go on, others nothing. Also trying to turn off the phone is hard as it sleeps straight away with out opening up the power menu.
I have a stock N1, which recently updated to Froyo, with the same problem.
any ideas would be great!
cheers,
lorin.bute said:
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
Click to expand...
Click to collapse
Also happens on CM 5.0.7.1.
i think it may be a hardware button issue.
I have tried turning mine off (had to pull the battery out) and then to turn it on.
It should turn on readily as it has nothing to do with the OS at that point.
any ideas?
No HW button issue described. HW button works - if it didn't, lights wouldn't go on. It's a wrong reaction on the button, at least that's what OP describes (and me too).
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
I've read more than one or two threads on power button issues, and I know what I'm talking about. My power button DOES power up the phone when the battery is taken off the first shot, it DOES wake the phone from standby, it DOES register long presses - there was even one time when a second press was long, and suddenly the screen woke up with power menu, while the first press left it dark with touch button light going on.
Doesn't look even a bit like HW to me. HW would leave the phone dead, non-responsive to touches, or create a loose touch which would translate into several touches - none of those would EVER turn into a phone being on with screen off, and suddenly snapping back to screen on when the SCREEN is touched several times.
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Take your time! As for me, I'm using my N1 for 3 months now for the power button to completely dead with everyday use (I didn't use any app to trackball-wake).
As I said, all the things you are yelling I have been through. And I, too, thought it was software problem.
I tried both MCR and Cya with no hope.
Good luck!
ps: One of my friend just told me about his N1's power button issue right after hearing me telling about mine.
This sucks
anyone know where i can buy a new button??
Corrupt SD Card
I had the same issue. I'd press the power button, the bottom four buttons would light up but no screen wake. Only way to get out of it was to pull the battery. It would happen maybe 30-40% of the time. (Nexus One Froyo FRF72)
I think it was due to a corrupt MicroSD card. I recently installed a 32gb card and put some music on it using songbird and possibly didn't safely remove. That's when I started getting issues. Removed the SD card completely and it worked fine. Changed back to the old card and no issues. Then formatted the 32gb and tried again, worked fine. Then I tried to transfer more music, there was an error and I got the same problem. (Cheap ebay card from Hong Kong, that'll teach me).
Anyway, I'd be interested to know if that solved anyone else's problem, because all I see on forums are that it's a faulty power button, but that didn't seem to be the case in my situation.
Cheers,
Dylan
-Witty esoteric statement about science/technology.
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
jimbobalu said:
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
Click to expand...
Click to collapse
i have almost the same issue, although mine happened twice when i was on EPE54B but it's been far more common on FRF91
the only difference is my power will continue to turn the back light on and off no matter if the screen has already timed out or not
kobecamp2009 said:
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
Click to expand...
Click to collapse
I have exactly the same issue. Over in the general forum, there's another thread on this issue. Many, myself included, are reporting that this problem started after the FRF91 update. Can you confirm?
rtx101 said:
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
Click to expand...
Click to collapse
Read again carefully. Are you sure your hardware problem was identical to what the OP described? I've noticed a lot of people with obvious hardware problems (i.e., the power button is completely unresponsive) posting on threads like this when they actually have a different problem. It's very confusing.
britoso said:
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Click to expand...
Click to collapse
This sounds VERY promising -- thank you britoso!
PS: Are you guys getting the unresponsive unlock slider like britoso describes?
I had this problem when I first flashed CM6 yesterday. Even after wiping and reflashing it was the same. Only way to get out of the black screen was to do a soft reset, power + vol down + trackball. I finally found out that my SD card malfunctioned and was corrupt. I tried reformatting the sd card in an microsd card reader but windows said it could not be reformatted. I finally switched back to another microsd card that was working, wipe and reflashed cm6 and the problem went away. Try backing up all the data on your microsd onto your computer then reformat it and wipe then reflash to see if it works
Edit: ughhhh it just happened again, but not as bad as before, turns back on after second try... maybe i didnt press the trackball hard enough
Hey, recently I was just using my phone and it wouldn't respond to any of my touches / screen presses. I tried doing a factory reset (using CM 7 stable), but it still doesnt work. The menu buttons arent working either, but the trackball works fine. If I press REALLY hard down on the screen it registers my input. Any idea what happened or how I can fix it?
Was playing with a phone just last night with a non-responsive touchscreen. Couldn't get past the "Touch the Android to Begin" screen after reinstalling CM7. I found that if I gently pressed and twisted the bottom of the phone around the trackball, the touchscreen would come back. Give it a shot.
Have you ad trouble with this from before? Try installing another rom with wipe
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)