Related
Hi all, please can you help me with this!?
Firstly when my phone boots or is taken out of sleep mode it immediately activates voice record as if this button has been pressed. It then opens the dialler and types ‘EDFC’. If I open pocket word and then wake the phone up it also types ‘EDFC’ before doing the above.
My keyboard is not working and the only hardware buttons that function are the power button (only for a while), the camera button and the silver select button in the middle of the d-pad. The jog wheel and silver directional d-pad buttons occasionally come to life. The others don’t work (green call and red end buttons, ok, windows etc).
When I use the standard keyboard SIP on the screen the directional buttons and delete do not function?!
I’ve reverted to a stock ROM to make sure this isn’t the problem.
It appears as though my Kaiser thinks these buttons are being depressed, but I’ve checked them and they click normally and release when pressed (even though they don’t perform a function) so nothing is stuck down etc….
I’m going to use AE Buttons to try and unhinge the button functions for now, but it would be great if someone has any suggestions!!
Thanks in advance.
Update - AE Button won't unhinge the buttons or change their function to anything else (e.g. nothing). I can't stop this from happening every time the phone boots/wakes up!
Help!
Mine got the same symptoms last week except it opens quick something or other,and then the dialler dials 2547.The screen for my pin then comes up,which I can enter normally.Home screen fires up normally but the keyboard will not work or any buttons except the silver one in the middle.Searched a bit and this problem is very common although I cannot find a solution anywhere.Can someone please help
AE button didn't work?
When mine did that, I reset all the hardware buttons (not the keyboard, just the buttons reachable from the outside. A soft reset and viola!
That's the only solution I have. It's worked for me 2x.
Also try pulling the battery for 20 seconds or so and restarting. That has fixed my touchscreen not working after it gets spashed 3x. Yeah, my phone is old and abused, but keeps working.
Will
wasilvers said:
"I reset all the hardware buttons (not the keyboard, just the buttons reachable from the outside. A soft reset and viola!"
Click to expand...
Click to collapse
Thanks for your replies - I've got Orange sending me another one in the morning now and sods law it's just stopped happening.... Taking the replacement anyway in case it happens again.
For my knowledge, how did you reset the buttons? I deleted some registry keys to completely stop them working (although I couldn't find the registry keys for the red and green buttons).
Searching on Google there are quite a few reports of this, but no one has ever posted the cause!
I am having the same problem... please help. My phone is going crazy. I did a hard reset but still didnt solve the problem....
I am also having this issue. Phone starts typing EDFC and then initiates the voice recorder. I reflashed various ROMs and regardless of what was flashed.. initially they appeared okay, then it started happening again. I also tried hard and soft resets. Nothng has worked so far.
I resorted to disabling the keys and some of the applications which I dont use which appear to be getting started/run (Voice recorder for one). So far I havent had the issue, knock on wood.
I think this is more than likely a hardware error. My tilt is actually pretty old so I wouldnt be surprised. If someone finds either the cause or a workable solution please post. Im trying to hold off until January when my contact expires to get a new HTC.
I searched and searched but found no solution for this and ended up getting the phone replaced.
HTC seemed to know nothing of such a problem....
Have you tried whacking it?!!?
Hope you get it sorted.
brandall said:
Have you tried whacking it?!!?....
Click to expand...
Click to collapse
Hmm, yes, but I don't see how that helped my phone.
lol, all jokes aside, my friends, I ask in this thread as well,
what is causing this problem? I ran into this issue after ALL my buttons stopped working (except for the power).
I installed a new rom (I forget which one), and still nothing works except for power button.
It would be even better if someone knows the solution!
-Calling for Help-I'm still convinced it is a software/registry problem...
Okay, so there's no solution available for this weird problem of ours.
On the bright side, however, it is amazing that we can still use the phone, even after it requires servicing (some way or another). I have accepted this handicap that has been placed on my phone for now, simply hoping it will grow out of it one day.
But something isn't right. When I looked in the registry (trying to follow some directions I found within the wiki for when your keyboard STILL doesn't work properly), there was a discrepancy between what was supposed to be found in the registry and what was actually there. It wasn't that the values were wrong, it was the names of the values that were different. Why could this be?
Or even if you have moment of time, and you have an AT&T Tilt, and it works perfectly, maybe you could write up a run down of what you have hanging around in that section of the registry?
Hey, just so I can be sure, is there some place I can cross check what I have in my HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP with what is supposed to be there in a fully functioning AT&T Tilt?
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
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
Hello everybody,
I was doing a lot of research on this issue and was using the search function of course, however I was not able to find a fix to the problem I am experiencing.
I have a Samsung at&t captivate with cyanogenmod 10.0 installed.
The problem:
Lately I experienced strange touchscreen problems, where it seemed that my phone did what it wants to do. Opening google maps zooming in and out, opening other apps and it even called a friend one time. All that did not seem to follow any pattern, it was more like someone randomly touched on my screen.
What I tried:
After doing some research, I booted to recovery and deleted the cache and dalvik cache. After I rebootet the phone everything seemed alright, except for when writing a message, some keys "p" and "?" where not working.
So I rebootet to recovery again and did a factory reset, and installed cyanogenmod 10.0 again. Everything seemed alright at the beginning, but when I clicked my way through the welcome process, I noticed that the "p" key does not work again, all the other keys though, especially the ones in the bottom right corner, work just fine.
And here comes the problem: On the next screen "Google & location", I can not press the ">" button to proceed in the bottom right corner!
Do you think it is a hardware problem? What is against this is, that the same spot where the ">" button appears, works fine on the other screen, when I enter my Email adress.
Every kind of help is very much appreciated!! Thank you all in advance!
Best,
Moritz
moritz1 said:
Hello everybody,
I was doing a lot of research on this issue and was using the search function of course, however I was not able to find a fix to the problem I am experiencing.
I have a Samsung at&t captivate with cyanogenmod 10.0 installed.
The problem:
Lately I experienced strange touchscreen problems, where it seemed that my phone did what it wants to do. Opening google maps zooming in and out, opening other apps and it even called a friend one time. All that did not seem to follow any pattern, it was more like someone randomly touched on my screen.
What I tried:
After doing some research, I booted to recovery and deleted the cache and dalvik cache. After I rebootet the phone everything seemed alright, except for when writing a message, some keys "p" and "?" where not working.
So I rebootet to recovery again and did a factory reset, and installed cyanogenmod 10.0 again. Everything seemed alright at the beginning, but when I clicked my way through the welcome process, I noticed that the "p" key does not work again, all the other keys though, especially the ones in the bottom right corner, work just fine.
And here comes the problem: On the next screen "Google & location", I can not press the ">" button to proceed in the bottom right corner!
Do you think it is a hardware problem? What is against this is, that the same spot where the ">" button appears, works fine on the other screen, when I enter my Email adress.
Every kind of help is very much appreciated!! Thank you all in advance!
Best,
Moritz
Click to expand...
Click to collapse
I'm thinking you might have to go back to Stock KK4 and start fresh. If that doesn't work, it's most likely a hardware issue (humidity perhaps). If it comes down to that, take apart the phone and put it in a bag of rice for a couple days. Now if that doesn't fix it, you might have to get a new screen
I'd add bad screen protector to the humidity/hardware list. the key is that it keeps recurring in the same place on the screen. if you rotate the keyboard 90 degrees, does the p key work?
Sent from my SGH-I897