Database Develop

Power button just does not work !!

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.

Screen won't timeout

Very odd...
My screen won't timeout anymore, unless I manually press the power button. It doesn't matter whether the phone is plugged in or not, and it isn't dependent on the screen I am on either. The screen just stays on forever.
Is there a way I can see if a certain program is preventing the screen from sleeping? Has anyone encountered this type of thing before?
Thanks!

yakkamut said:
Very odd...
My screen won't timeout anymore, unless I manually press the power button. It doesn't matter whether the phone is plugged in or not, and it isn't dependent on the screen I am on either. The screen just stays on forever.
Is there a way I can see if a certain program is preventing the screen from sleeping? Has anyone encountered this type of thing before?
Thanks!
Click to expand...
Click to collapse
Did you check the screen time out settings, maybe you got it at 30mins ?

Yeah, it's set to 30 seconds. It must be some program that tells my phone not to sleep?

Even more odd...
It fixed itself!
Rebooting the phone for the last couple days had no effect on the timeout issue I was having, but doing it this afternoon somehow resolved the issue.
Add this to the list of idiosyncrasies that my SGS has.

I'm having this annoying problem with my SGS (JPY) at the moment. Sometimes it'll go to sleep and turn off the screen by itself, but 9 times out of 10 I have to manually turn it off with the power button.
Has anyone else experienced this with JPY? I'm reluctant to wipe and start again, but it's really starting to piss me off now...

might be an old topic, but i am experiencing this right now
i just installed gingerreal guerilla version yesterday and it works fine
however when i connected my phone to usb for charging this morning, it wont turn off the screen unless i do it manually by pressing the power button
weird thing is as far as i remember there's a setting on USB debug mode to turn off the screen when connected to usb. i think it might be related to the rom or is it always like that on gingerbread? i assume that is the root cause,
although i couldn't post the issue directly on the gingerreal thread due to minimum post count.

N1: Screen issues (Stops working)

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.

[Q] Amzer TPU case laggy unlock

Hey guys i bought a amzer tpu case and its nice but i've noticed that everytime I unlock the phone with the case on the phone vibrates and gets EXTREMELY laggy for a couple minutes before vibrating again and returning to normal. I also randomly get a prompt asking me to send something via gmail/email/etc after the second vibrate. any idea on whats going on?

I don't see a case causing anything like this.... unless its pushing the buttons.
Sent from my Nexus S using XDA App

shahravi94 said:
Hey guys i bought a amzer tpu case and its nice but i've noticed that everytime I unlock the phone with the case on the phone vibrates and gets EXTREMELY laggy for a couple minutes before vibrating again and returning to normal. I also randomly get a prompt asking me to send something via gmail/email/etc after the second vibrate. any idea on whats going on?
Click to expand...
Click to collapse
i have the exact same problem! i thought it was just a bug with my build of ICS

shahravi94 said:
Hey guys i bought a amzer tpu case and its nice but i've noticed that everytime I unlock the phone with the case on the phone vibrates and gets EXTREMELY laggy for a couple minutes before vibrating again and returning to normal. I also randomly get a prompt asking me to send something via gmail/email/etc after the second vibrate. any idea on whats going on?
Click to expand...
Click to collapse
I suspect this may be related to an android feature which dumps logcat when you hold vol up + power button. This only occurs if USB debugging is turned on. I encountered this when I use my nexus S with my nexus one pouch, and I would hit the two buttons whilst I was pulling it of the case.
The first vibration indicates the start of the log taking, the second indicates the end and when it writes it to file. If I'm correct, there'll be a largish folder full of logcat like text files in a folder located in /sdcard/.
Only fix for this is avoiding pressing both buttons at once when waking the phone, OR turning off USB debugging.

ringer13 said:
i have the exact same problem! i thought it was just a bug with my build of ICS
Click to expand...
Click to collapse
no its been happening to me since the days of gingerbread :/
Uni7 said:
I suspect this may be related to an android feature which dumps logcat when you hold vol up + power button. This only occurs if USB debugging is turned on. I encountered this when I use my nexus S with my nexus one pouch, and I would hit the two buttons whilst I was pulling it of the case.
The first vibration indicates the start of the log taking, the second indicates the end and when it writes it to file. If I'm correct, there'll be a largish folder full of logcat like text files in a folder located in /sdcard/.
Only fix for this is avoiding pressing both buttons at once when waking the phone, OR turning off USB debugging.
Click to expand...
Click to collapse
oh i guess that makes sense! thank you. i think im just going to stop using the case. ive passed that overprotective period so ill live without a case on my baby lol

Uni7 said:
I suspect this may be related to an android feature which dumps logcat when you hold vol up + power button. This only occurs if USB debugging is turned on. I encountered this when I use my nexus S with my nexus one pouch, and I would hit the two buttons whilst I was pulling it of the case.
The first vibration indicates the start of the log taking, the second indicates the end and when it writes it to file. If I'm correct, there'll be a largish folder full of logcat like text files in a folder located in /sdcard/.
Only fix for this is avoiding pressing both buttons at once when waking the phone, OR turning off USB debugging.
Click to expand...
Click to collapse
hmm couldnt find any folders containg log files. do you know which one it is? could this be related to the ridiculous amount of radiodump.bin files i have appearing on my sdcard?

Proximity Sensor Issue with Lollipop

I can't tell if this issue is with the specific ROM I'm using, or if it's just a Lollipop issue in general. During phone calls, the screen goes black (as it should) when I bring the phone to my ear, but now with Lollipop ROMs, most of the time when I pull the phone away, the screen stays black instead of coming back on. Normally, the screen would illuminate when I pull the phone away, but now it doesn't always work correctly. This is particularly annoying at the end of a call when I would normally touch 'end call', but now I have to wait for the caller on the other end to hang up before the screen comes on. Anybody else notice this?

I'm running gruesomewolf's GPE version 1 and I noticed it. I can usually just press the power button and the screen comes back on though.

A workaround
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.

Abdou.rk said:
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Click to expand...
Click to collapse
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:

One more solution
coal686 said:
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
Click to expand...
Click to collapse
You can also enable DoubleTap2Wake by using a custom kernel.

Same problem on TMo m7
Last week I upgraded to Android 5.0.2 on my TMo HTC One m7.
Since then when I remove the device from next to my head during a phone call the screen stays black.
This means I cannot use a keypad to navigate a phone menu or to enter a PIN.
I can tap the power button to re-awaken the screen but it takes several seconds to come back - and sometimes stays dark.
This is a mild nuisance if simply trying to end a call but is a major issue if I'm trying to use an IVR (this device is, after all, a PHONE!)
I have run the HTC Function test on the phone and the P-Sensor test runs fine.