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.

how do i factory reset with a dead screen?

my damaged nexus one screen has progressed to the point of a black screen all the time... i didnt think of it before the screen died, but i am a bit stumped as to how i now reset to clear all my data? i cant see anything on the screen, but the phone still has my google account linked to it.
doh! :-(
reason i want it cleared: may send in for repair and i dont want others to get my info, or i may have to send to insurance company for payout (they said to hang on to phone for now) and i dont want them to see my info, or may sell damaged unit if insurance doesnt pay and i dont want those folks to get my info either.... see the problem?

You can try this. Did a google search.
http://www.droidforums.net/forum/droid-general-discussions/28793-how-do-full-adb-wipe-help.html

thanks for the link...would work if id had debugging enabled before the screen died... adb wipes require debugging mode.
any other suggestions?

There's this:
http://code.google.com/p/androidscreencast/
But if you don't have Debugging enabled and can't get it to register when you hit "adb devices" you're probably effed. I don't know much about touch screen engineering, though. Does it still respond to touch as far as you can tell, or is the screen completely dead when the OLED display stops working?
This serves as a good warning for others, though. ALWAYS MAKE SURE USB DEBUGGING IN SETTINGS > APPLICATIONS > DEVELOPMENT IS CHECKED. There's really no good reason I can think of that would ever make you want to leave this unchecked, and this is an example of when it would come in very handy.

cant you use the clear storage function by booting while holding volume down, waiting 5 seconds, then pressing volume down 3 times followed by a press of the power button?

flybyme said:
cant you use the clear storage function by booting while holding volume down, waiting 5 seconds, then pressing volume down 3 times followed by a press of the power button?
Click to expand...
Click to collapse
is this a commonly known sequence ? if so, please link to a list of all the known boot-up key combos. thanks

Kiserai said:
There's this:
http://code.google.com/p/androidscreencast/
But if you don't have Debugging enabled and can't get it to register when you hit "adb devices" you're probably effed. I don't know much about touch screen engineering, though. Does it still respond to touch as far as you can tell, or is the screen completely dead when the OLED display stops working?
This serves as a good warning for others, though. ALWAYS MAKE SURE USB DEBUGGING IN SETTINGS > APPLICATIONS > DEVELOPMENT IS CHECKED. There's really no good reason I can think of that would ever make you want to leave this unchecked, and this is an example of when it would come in very handy.
Click to expand...
Click to collapse
the digitizer still accepted touch input as screen beneath began to fail. colors bled from the cracks and the images began to imprint in the screen... within a few hours, it was completely illegible, and then the next morning, it appeared as a dysfunctional unit with a non working screen.
i will try and methods suggested, but i have no way to verify success... thanks for the sequence.

well when you boot by holding power, your given options FASTBOOT, RECOVERY, CLEAR STORAGE, SIMLOCK
Heres the exact key combination
Boot phone using Volume Dn + Power
Wait 5-10 seconds to be safe
Press Volumn Dn twice
Press Power Btn
Press Volume Up
Phone should reboot after 5 seconds

i will try that... confirmation of success will be the charging LED turning off and then back on again?

nexusonemeover said:
i will try that... confirmation of success will be the charging LED turning off and then back on again?
Click to expand...
Click to collapse
of the reboot? ya. i cant imagine doing this without the screen lol. Sorry i couldnt be more help

You could also probably flash a PASSIMG.zip from the bootloader. That will overwrite all partitions so it should make it 100% stock.
It might be harder to do without the screen than the clear storage function though.

flybyme said:
of the reboot? ya. i cant imagine doing this without the screen lol. Sorry i couldnt be more help
Click to expand...
Click to collapse
tried the method... and i think it worked... i cant verify, but thanks for the help guys.

You can easily verify that by sending yourself an email and see if your phone can get the notification of that new email (by trachball or sound).

Dead within 8 hours of use (dead dead. not battery dead)

ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?

thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
IIRC the Xperia Z1 has a hard reset button under the sim flap, it's a small red button, give it a shot.

remove sim card and sd card and try again, if it's still not responding do an update repair using SUS or PCC
BTW there is a known fault with the XZU and it could also be on the Z1 as they use similar Firmware, what people have found is that the phone will start up eventually and then they go into the display setting and untick the auto backlight option and that fixes it

I also reboot my Z1in this way when it blackout.
Sent from my C6902 using xda app-developers app

Had the same issue called Sony, push hard reset button all is fine in the world. Known issue Sony is working on it
Sent from my C6903 using Tapatalk 4

Managed to hard reset using power and up volume .
Put it on charge overnight but it doesn't see,m to have taken any charge at all....just trying again using diff PSU and cables but it doesn't want to charge. It recognises that I've out a cable in as I played with the smart connect setting. When it is off completely I get a red light (presumably meaning its charging ) but not in android
Any ideas?

Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)

Sometimes phones have issues. I got one once that had no speakers or Mic inside... it happens lol
Try to go exchange it, and see if the next device gives you issues.. if not then you're good, if it does pick a different phone..
Do it soon though, most carriers only have a 14 day exchange period, and then after that will charge you all sorts of fees and try to fix your phone rather than just giving you a new one....
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel

thefunkygibbon said:
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Click to expand...
Click to collapse
sounds like a similar problem I had with my 64gb SD card - as I mentioned above remove all cards then start from there - a reflash of the firmware might help also

thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.

LadFromWales85 said:
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
Click to expand...
Click to collapse
yeah i've been trying to reproduce it and failing to. very odd. maybe its something to do with the first time you use youtube and do something specific?
gunna phone o2 up tomorrow and see what they say about all my issues. seems to have been fine this last 24 hours though and in their eyes that is prob reason enough not to issue a replacement.

I've had mine since Monday and this happened to me yesterday. I was troubleshooting sending MMS with T-Mobile tech support (not a phone issue as it was happening on previous phones too) and had to restart the phone several times. I noticed upon restarting that the backlight seemed to be on but the phone was not booting up. Had to perform several hard resets (both with the red reset button as well as the power/volume up buttons) before it FINALLY rebooted and stayed on. While trying to figure this out I ran a Google search to see if others were having this problem. One solution was to make sure the backlight option is checked. I had been messing with settings the night before and must have unchecked it. Since I rechecked it I haven't had the same issue.

[Q] Bug Report Captured

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.

power button problem

hello friends, today dropped my droid turbo, after that it seems that power button is little bit fell in, so it's harder to press on it, it's no more like volume button (no click effect), but it steel works, so is there some solution to fix it without disassembling whole device? thanks

Niku7a said:
hello friends, today dropped my droid turbo, after that it seems that power button is little bit fell in, so it's harder to press on it, it's no more like volume button (no click effect), but it steel works, so is there some solution to fix it without disassembling whole device? thanks
Click to expand...
Click to collapse
I have a not-quite-so similar issue; I dropped mine a couple of weeks ago, with a Diztronic case on it, and it landed on a brick walkway directly on the power button completely disabling any function whatsoever to the power button. I thought about opening the back of the phone and trying to replace the button with one from a previous busted quark that I still have. But instead, I have gotten by without it by using Lock Screen Widget (free from Google Play, along with other similar apps), which can place a button on the screen, either permanently or on Home screen only, to turn the screen off.
Now, to turn the screen on, Ambient Display has proven to be invaluable, plus in the Button settings of the Bliss (@NepoRood) custom rom I'm using, there is a selection to wake the phone using the volume button and I have it set to wake when it's plugged into a charger / PC. If you're not using Bliss, I'm pretty sure other custom roms have these wake features; if you have unlocked bootloader and root access, the Xposed module Gravity Box may be able to enable this as well. However, if your phone isn't rooted, I'm not sure if this wake feature would be available.
I know this may not directly answer your question, it's just what I've been using to get by. I am curious though if anyone else has had success personally replacing or repairing the power button.

RL_Wells said:
I dropped mine a couple of weeks ago, with a Diztronic case on it, and it landed on a brick walkway directly on the power button completely disabling any function whatsoever to the power button.
Click to expand...
Click to collapse
thanks for reply
so does anyone know i need to buy new button and replace it or need to change whole frame, which holds that power button?

Niku7a said:
thanks for reply
so does anyone know i need to buy new button and replace it or need to change whole frame, which holds that power button?
Click to expand...
Click to collapse
A few months after I got my original Droid Turbo the power button failed. Wouldn't turn it on or off. Physically had a problem. They told me that there is an issue with their power buttons and when it gets like that they have to replace the button.
However, perhaps you do have something as simple as a dented case/cover in the metal by the button which is restricting the button from functioning as normal. If you have something small and thin like an intricate pick tool, you might be able to get down in there a little bit and see if you can go all the way around the button. If it sticks or stops, that might be a dented area.