I pasted this in Google's official forum but no reply. Can anyone one here please reply to this?
******************************
Here it goes:
The phone is perfect. Works very well. With a small annoying issue.
Sometimes after calling some someone when I hang up and keep it aside, the screen times out (which is normal).
But later when i try to wake the phone by pressing power button it does not do anything. No matter which button i press the phone lies dead.
Take out the battery and the phone starts working great as if nothing happened.
I have experienced this issue atleast 5 times. I tried factory reset just to make sure any random application is not doing this. But, after couple of weeks the issue came again.
I am not sure if HTC is the only one that can help because I am basically scared that they might screw other areas of phone which are working just fine.
Can this be solved by Froyo? Should I wait for it come OTA?
Also, there can be an application which wakes up phone via trackball but would that help?if no button is responding.
Please help guys!!
Always include:
Carrier:Singtel
Country / Language:Singapore
OS / Browser / build number (if applicable):2.1-update 1 (Unrooted, waiting for Froyo OTA)
Try calling your phone from another line first. That would happen to me on my HD2 (a really awesome phone if it didn't suck ass so bad) and, sometimes calling it from another line would cause it to wake up.
OK
Will try to call from another phone once the issue re-occurs.
Should get Froyo by this week as per google so lets see if that can eliminate the issue.
Just now this issue reappeared. I tried calling my phone with other phone but it just kept ringing, no response on N1.
I tried connecting charger and usb but again phone lies dead.
Pull-push battery and now I am typing this message with same phone.
Still wating for froyo ota.
Guys, pls suggest if someone is facing same issue.
I know Leo Laporte had this problem with his N1. Because the power botton is used for unlocking the phone it is more prone to having issues. Everything on his phone was fine, then the power/wake button stopped working. He pulled the battery and could never get it to boot up again, since the power button didn't work. He called up HTC customer service and they sent him out a new phone minus the battery and back cover. That may be the easiest solution to your problem.
I had that problem at one point, although not so severely. Froyo put an end to it but I have a strong feeling the problem will return since I am starting to notice a ~1/2 second lag between pressing the button and the phone waking up.
I think the problem lies in the hardware/software interaction for the button. Can you try something:
-Plug in your phone to your computer
-Start logCat* on your computer
-Keep messing around with your phone while its still connected (logCat will keep scrolling by itself, displaying the system log - if it doesn't, scroll to the bottom of the log and it should begin auto-scroll)
-Wait for the problem to come back
-Press the power button ONCE and see if ANYTHING shows up in logCat that coincides with you pressing the button.
The reason I say this is that I tried this with my phone (i'm a dev so I had it plugged in at the time already) and when I clicked the power button, although the screen would not turn on, logCat would indicate that the Android system registered the click.
Post the results for everyone, if you would be so kind.
*logCat is part of Android-SDK and can be downloaded from the Android Developer's Resources.
it's most likely a hardware issue with the button itself. 3 weeks ago I had a very similar problem where the button was working 1 out maybe 5 times. I called up HTC and they sent me a new one (well technically they're refurbished but I honestly couldn't tell the difference). I was rooted and everything, but they still didn't charge me for it. New phone is still working just fine.
So give them a try.
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
MSigler said:
It sounds like a hardware issue to me too, but like someone already said logcat will tell us for sure. You can use alogcat from the market on your phone if you don't have the sdk installed (and I'm guessing you don't if you're waiting for an OTA for froyo).
Click to expand...
Click to collapse
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
maniacx21 said:
How will the OP view alogcat (installed on the phone) if the sleep/wake button is what's in question?
Click to expand...
Click to collapse
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
musashiken said:
Well everytime android acknowledges a wake from the power button, it will be indicated in the logcat. I think it's something like "I/power: set screen_state 1"
So maybe that is an indication that the power press is being registered. And if the OP is certain that he really did press 5 times and only one time works, then there should only be one line that indicates that.
If the logcat reads 5 power presses, then it may be the display problem.
Then again this is just my speculation. I have no idea how to read logcats.
Click to expand...
Click to collapse
Ahh. I believe you misunderstand my intention;
The logcat output won't explicitly say that the sleep/wake button was pressed, rather you would see some indication of background [system] activities reacting to the press (you would see 'x many' log entries appear RIGHT when you clicked the power button). There would be no way to tell for sure if you see it after the fact. You would essentially be clicking the button with your finger while staring at the logcat output on your computer. You could not do that with alogcat (from the market) as the [device's] display would be off at the time.
*I bolded alogcat to differentiate it from logcat.
For those unfamiliar, the Android system (and activities spawned by applications) send 'messages' to a sub-system in the Android-OS called logcat. The logcat is used by developers to find out at what part of the program an error occurred while debugging as they can output detailed error logs to it from their app. Logcat also outputs things such as results from OTA checkins so Google can debug the OTA system to make sure it is pulling the correct download paths, ect. This was put in place by Google devs (and led to the public finding out the google server addresses of the Froyo 'test' builds).
On average, there are 2-3 logcat entries added per second when the device is being used, and about 0.1 logcat entries per second when the device is in standby mode. What we are looking for in this case is whether there is a sudden surge of entries when the button is pressed, indicating that SOME part of the Android system recognized the press. The entries wouldn't have anything to do with the button itself, but if the same [few] entries come up EVERY time you press the power button and nothing happens visually, you know something was triggered.
Logcat is a software that runs on your computer (what we want in this case) that lets you view log entries in real time. Alogcat on the other hand, is a software that RUNS ON YOUR PHONE that allows you view log entries in real time.
Let me know if you have any questions!
Do you use a taskiller? Ever since I got burned by a taskiller, I've been wary about them. Not wary enough to uninstall them though.
Not a fix:
But a workaround would be using Trackball Wake to circumvent having to use the power button to wake your device. Especially since you are not running on Froyo.
Related
Hi, I cleaned the screen of my HTC Diamond with a bit of alcohol and a pice of tissue and it seems that the alcohol got inside of the Power button. Now, every time I try to turn the screen on by touching the power button, it turns the screen on but it dispays a message that says: "Warning: Power will be turned off and you may lose data if you have not saved them. Do you want to continue?"
If I click YES, it reboots the phone, If I click NO, then its ok. That is fine, but the problem is when I want to turn the phone off. It's impossible. It will keep trying to reboot.
Does anybody know what can I do? I am really worried.
One solution could be to make some other button from the phone to act as the power button (like the Home button that is rarely used). How can I do that?
Please help!!!!
Thank you
Hi,
I have the same problem.
Did you already find an answer ?
No, I didnt find the solution. I tried to fix the hardware but didnt succeed. So, I created a dummy file to emulate the poweroffwarning.exe that pops up when you long press the power button.
Solution
Hello, I have one AT&T TITL 8925 that upgraded to Windows Mobile 6.5
After the new software was loaded I saw same behavior on my phone.
When the phone is ON and I pressed the power button sometimes it do not respond, and others I received the warning message "power will be turned off and you may lose data if you have not saved them..." My first tought was that it is because the processor is slow to this new software release, or maybe my phone is damaged. I was working perfectly with previous (light version) release so my final guess is that this sw requires more uses of the processos.
Anyways what I have been doing is before turing it off I press the red button or hang up button, and after this if I press the power button it works fine (No more warnings). I have some theories but I will keep doing the same
Hope this partial solution helps you as it does for me.
Regards
Jerry
this is not working for me :| the problem is i can't use my power button not even to open my display when it goes to sleep :|:| i don't know what to do guys please help me
You can use the Stylus to awake the phone, instead of using the power button. You can also use TouchLockPro, to suspend the device, so you do not need the power button for that too.
Also you can set the phone to awake on pressing any key (Windows Mobile Setting), but be sure to have a good locking tool, which makes sure you do not have bogus calls and it goes to sleep again fast enough, otherwise it will drain battery.
I have the same problem.
Anyone solved this one?
I have the same issue and this is not a hardware problem. Strange since even updates/changes of the rom do not correct the issue. Did anybody find a solution for this...?
Well.. ive had this problem just ones.. I was walking downtown with my diamond in the frontpocket of my jeans (face down), after about 3min. of walk, it started to rain (big drops), and my clothes got completely wet, i turned around emidietly, to walk back to home. When i got home after 3 more min. i layed the phone on the table, and then i could hear there were somethibg wrong.. The "turn off" sound came, and the notification kept on coming up, even though i pressed No, as if i were just holding the power button down.. Then i began to press the power button continuesly for about a 100 times, and to my surprise then it stopped and have functioned perfectly for about 2 month now.. Something tells me theres some serius promlem with the smallest kind of moisture near the power button on this phone..
Yes this is hardware related.
If you take a look at the inside of the powerbutton, there are 2 points making contact when you press the button.
If you press it, the software will recognize this and the screen will turn off.
If you press it long enough you'll get the "Do you want to turn off your device" message.
But, if water gets underneath the button, the 2 points may be making contact, because water/alcohol conducts.
In this way you'll get that message.
The button is very weak. Due to this, it may not properly work if you have used it for a long time.
I think that could also be a reason why you constantly get that message.
[ElCondor] said:
Yes this is hardware related.
If you take a look at the inside of the powerbutton, there are 2 points making contact when you press the button.
If you press it, the software will recognize this and the screen will turn off.
If you press it long enough you'll get the "Do you want to turn off your device" message.
But, if water gets underneath the button, the 2 points may be making contact, because water/alcohol conducts.
In this way you'll get that message.
The button is very weak. Due to this, it may not properly work if you have used it for a long time.
I think that could also be a reason why you constantly get that message.
Click to expand...
Click to collapse
Hi! on one of my diamond, the power button off from the board. So the black little board with the button itself is not part of the complete circuit anymore... if someone know the hw testpoint for that it would great please.... i see a few TP around, but if i just start sorting them i just going to kill it...I use to flash phones with TP so is not new for me , but i find nothing for diamond.
I have a similar issue. Mine seems like it is almost stuck on, so it wakes its self up all the time, meaning a full charge lasts an hour or two. Then when it runs out of battery it tries to switch itself back on, so goes through a continuous cycle of vibrating and beeping until the battery is removed. The gf finds it very annoying at 3am lol.
Don't recall mine getting wet, but it's possible it could have got damp at some point, but it's been doing this now for about 3 weeks.
Tried a hard reset with no luck.
[ElCondor] said:
Yes this is hardware related.
If you take a look at the inside of the powerbutton, there are 2 points making contact when you press the button.
If you press it, the software will recognize this and the screen will turn off.
If you press it long enough you'll get the "Do you want to turn off your device" message.
But, if water gets underneath the button, the 2 points may be making contact, because water/alcohol conducts.
In this way you'll get that message.
The button is very weak. Due to this, it may not properly work if you have used it for a long time.
I think that could also be a reason why you constantly get that message.
Click to expand...
Click to collapse
I can see that how to remove the power button from the video showing how to replace the screen. Any idea if once removed the button can be fixed, if not can you get replacements?
2004mark said:
I can see that how to remove the power button from the video showing how to replace the screen. Any idea if once removed the button can be fixed, if not can you get replacements?
Click to expand...
Click to collapse
I think I should send it to HTC, and ask them to do it. Or go to a repair centre. But I should not try it myself, because it can be dangerous for the diamond.
Also try searching on ebay, there might be the parts you could use.
Good luck!
is there a way to remap the power button?
my diamond face same problem since this afternoon, arrrrgghhhh!!!
- blocking hwbutton1, hwbutton2, hwbutton3, hwbutton4, hwbutton5, hwbutton6, hwbutton7 >>>> NO LUCK
- hard reset >>> NO LUCK
guys, any of you solved the problem yet
youtube.com/watch?v=Q4SEQ6AUFOI
My Sony X1 have some strange problems with the power button. When it goes into sleep mode, I can not wake it up with the power button, all I can do is to soft reset. Sometimes it does not go into sleep mode either , it just "wake up" all the time. I don't know what's wrong with it, tried Hard reset but no use .
ANyone had this problems before?
@
The only way to solve this is to leave the phone near your laptop heat vent ( fan) . hot air from it might help you to get the power button up and running. But if that to doesn't work then i'm afraid thats bad.
Current sol :
1. download SU2U ( search threads )
2. go to the settings and make the " lock when stylus inserted" option ON
3. Change the screen turn off time to 5 secs..
So , to unlock , remove stylus , to lock -> insert it back ( its turns off the back light within 5 sec )
Less annoying
elektros said:
youtube.com/watch?v=Q4SEQ6AUFOI
Click to expand...
Click to collapse
thanks for this link, i accidentally tear off my power button flex. now i could turn it on again. Thanks elektros
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.
I have searched this exact title and came up with 10 pages and I never saw anyone else with this problem. Surely I cannot be the only one.
After the Gingerbread upgrade I was getting the tethering message/force close, during that time my phone started to randomly shut off ( settle down Beavis, this isn't the same question thats been asked a thousand times ) and reboot. I lived with the tethering message problem for as long as I could but my phone became more ignorant day by day. I finally found a fix for the tethering issue and haven't had a return problem with that but now my phone either stays in standby mode ( dark screen ) and refuses to respond to the hard button to wake it up OR once on it refuses to go into standby mode and stays on until I pop the battery or I go into settings and time the screen out in 15 seconds ( often times this doesn't shut it down either ). Sometimes I can get it to come on by multiple pressing the power button ( this can't be healthy ) and the lock screen will flash momentarily just long enough for me to unlock the screen. Other times it will go to the lock screen while I'm in the middle of something.
Every day at some point while it's on and I'm using it, the power button option screen pops up ( silent mode, flight mode, power off ). When I'm done with a call I try to go into standby and it just sets there...ON.
The thought has crossed my mind that the button doesn't work or has a short but I really think it's something else ( I hope ). Can somebody help me? I am not very techie although I have updated the phone three times myself. It is unrooted and 2.3.5
Thank you in advance
I would go with the power button. It's a known issue on captivate.
mrhaley30705 said:
I would go with the power button. It's a known issue on captivate.
Click to expand...
Click to collapse
I stopped by the AT&T store the other day to check on insurance (ends up I didn't have it) and told them about my button not working properly and how the Captivate was notorious for this problem and they all said "We've never heard that". So the gadget gal is in there so she offers to take it apart and check it. She claims there isn't anything wrong with it and that it has the same amount of spring as the volume buttons. She then noticed that when she put the battery back in the phone came on automatically, I said it's not supposed to do that and she agreed but fortunate for me since I cannot turn it on. She then says I'm eligible for an upgrade and try's to sell me a new phone. I don't want a new contract.
So should I try and buy a new button and change it or could it be something else? Thank you in advance.
Are you using a case for your phone by any chance? If yes, is it too tight? Maybe the power button gets stuck because of that sometimes? Just a long shot! You stated that power menu pops up once in awhile when you're using it, is it possible that the way you grip the phone causes that? (Just trying to help and not trying to offend you btw.)
You might want to try flashing UCKK4 with bootloader(use it from the one click master collection of stock rom's) just to make sure that there is no issue with the firmware. It is not likely to fix your problem but it's good to have a clean start. At least that's what I would do to begin with.
Since you're willing to change the power button, why not do an experiment? Remove the power button and see if there is any change? If it works fine then it's the power button that's faulty else it's a hardware problem.
I continuously get the notification "Bug Report Captured"
Happens when my phone is screen off just sitting around. Had it start happening last week. When I click it it gives me a few options and I finally decided to email it to myself. It attached an 8.9 MB file of text about my phone as well as a picture of my home screen which I can only assume is where the "bug" occurred.
Anyone else encounter this?
I keep getting it and I have no idea what to do with it
This occurs with some delay after you push and hold lock and volume up at the same time. Try avoiding the volume up button when locking your phone.
Ekkoria said:
This occurs with some delay after you push and hold lock and volume up at the same time. Try avoiding the volume up button when locking your phone.
Click to expand...
Click to collapse
I've had it when my is sitting on my desk. With active display, I don't actually need my power button for almost anything.
It's still doing it with me without me touching it. It'll be on my desk and next thing there's a bug report
If you have USB Debugging turned on under Developer Options, the phone will generate Bug Reports. Not sure exactly what triggers one. You can also manually create a Bug Report by touching Take Bug Report.
The text file that is created contains a lot of information about your phone. Mine was 8.2 MB.
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
SlightlyOpaque said:
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
Click to expand...
Click to collapse
You can try to reload (sideload) FireOS via the stock recovery menu to rule out a software glitch. However, based on symptoms I suspect the board holding the buttons and/or associate ribbon cable is the culprit. Not much you can do about either unless willing to crack open the case.
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
SlightlyOpaque said:
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
Click to expand...
Click to collapse
You can view the internals on a self-repair site such as iFixIT or by searching YouTube. The delay prior to acting up suggest heat may play a role. Not necessarily overheating, just the normal warming that electronics emit with use. Good luck.