Database Users

Power button not waking phone up

Every once in a while after not using the phone for a few hours the power button won't wake the phone up and I have to take the battery out or soft reset. Any ideas what is causing this?

Anyone have any ideas?

When I wake my phone up, it seems like it takes two hits of the power button to fully wake it up.
On the first try, I can see the answer and hangup keys light up for a second then go dark. On the second try, the phone wakes up.
Not sure what may be causing this. Can you try to see if hitting the power button a second or a third time will wake it up?

rijc99 said:
When I wake my phone up, it seems like it takes two hits of the power button to fully wake it up.
On the first try, I can see the answer and hangup keys light up for a second then go dark. On the second try, the phone wakes up.
Not sure what may be causing this. Can you try to see if hitting the power button a second or a third time will wake it up?
Click to expand...
Click to collapse
I can hit it 100 times and it won't wake up, needs a soft reset or battery removal to wake up. I've tried it with programs installed and just hard reset it and it's still doing it

my phone has this same issue too. its happened twice since i got my phone a week ago.

i have had the same problem ... let then a week of having the phone and on 2 occasions it has just shut off on me ... i even upgraded to the new rom and that didnt help

I have the same problem.

same problem here, i use soft reset to fix

yes, I had to do a softreset to fix it
xxza said:
I have the same problem.
Click to expand...
Click to collapse

but that doesnt fix the problem in the long run

Just exchanged mine...hopefully it won't do it on the new phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Replacement works perfect

dsotm82 said:
Every once in a while after not using the phone for a few hours the power button won't wake the phone up and I have to take the battery out or soft reset. Any ideas what is causing this?
Click to expand...
Click to collapse
It's a bug in HTC's software and they told me the fix will be included with the EVDO Revision A upgrade. Also the default SIP does not stick between soft resets and THAT bug is supposed to be fixed as well.

ho11ywood45 said:
i have had the same problem ... let then a week of having the phone and on 2 occasions it has just shut off on me ... i even upgraded to the new rom and that didnt help
Click to expand...
Click to collapse
can you inform which ROMs you used that had this problem and which carrier?

It's not a bug with the rom or the phone specifically. It's issues the phone has with certain software, etc.... I experienced the same problem when installing and running some items. After uninstalling the software the problem went away.
I've experienced this with several different applications that weren't intended for the Mogul but i decided to try out anyways.
My suggestion is to figure out when the problem started and then determine what software you had recently installed. This will most likely solve your problem.
Also, in a previous post someone mentioned that the SIP won't stick after a soft reset. This is true, however you can fix it with a free program on xda's site. Look for SIPChange

Someone posted previously that this happened even after a hard reset, and the only fix was having it exchanged for a different unit.
Sounds to me like at least in that case, it wasn't merely a software issue.
I actually had this happen to me today, but its not as often as some people report it to be. I've owned this phone for over a month, and its happened maybe 2-3 times. A little press on the soft reset button fixes it, and I forget it ever happened!

does this problem happens on WM5 & WM6?

did you solved the problem? i have had the same problem and in my case PhoneAlarm was the reason.
http://forum.xda-developers.com/showthread.php?t=329601
\\Yoshi

This just happened to me this morning. I just got the phone last night.

I'm so happy to hear all this! especially since I plan on getting the phone this weekend! I can't wait to run into these problems! Just out of curiousity, where did you guys purchase your phones? City, State? Online? Earth? thanks!

Anyone have Evo that glows in the dark?

a lot of people are reporting this problem when the phone is off
http://androidforums.com/htc-evo-4g/106893-i-just-notied-my-evo-glows-dark.html
JoshHuman said:
Here is the problem on a 002 15 second exposure in complete darkness.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

The way I see ut is that the button panel has its own backlight and is meant to turn on in complete darkness, but some evo's do it when the phone is off given enough power since the panel's software run a separate lower powered chip, but I'm no engineer. It can be fixed with a firmware update, probably.

Mine did this once. I turned it back on and killed a bunch of apps with advanced task killer, and then it quit. Think it was just a fluke because it hasn't happened since.. and that was about a week ago. If it's happening constantly even after reboots, I'd assume you have installed something that is acting retarded in the background.

actually it's not a software problem... I hard reseted and kepted the phone clean and checked at night. still LED problem being lit. I took it to a store and they are willing to replace the phone

Yes this happens to me alot and i have to remove the battery and put it back in i left the phone like that for 10 minutes and i click every button but does not come back on so have to remove the battery

My wife's has been doing that and it will not stop. Ive rebooted cleaned all apps and nothing. I'm trying to return it but am waiting for bestbuy to call me when they get more phones. Any one have a solution?
Sent from my PC36100 using XDA App

I have the opposite problem. Mine never seem to turn on in complete darkness. >_<

I just noticed this for the first time last night. Haven't seen it before or since.
Sent from my PC36100 using XDA App

TheBiles said:
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
Click to expand...
Click to collapse
wish i had that problem. i really have no need for back lights on the menu. the bleed they cause is terrible when looking at dark movies.
on the droid, in froyo at least, the menu buttons dim when watching a movie or you can use LEDsHack to turn off the lights.

I posted this issue a couple days ago and got no replies. I have noticed this issue on my phone. Sometimes pressing volume up/down will cause the lights to come on too.
I wonder if this is the cause of poor battery life. It's almost as if the light sensor is still functioning when the phone is supposed to be sleeping.

I noticed this also on both mine and my girls 0002 models... You can see it during the day too if you cup your hands around the bottom of the screen just over the buttons and look under. Wasn't sure what that was all about. Looks like just another glitch to me.

Is this good enough reason to request exchange? Does this drain battery faster in any way?

apexi350z said:
Is this good enough reason to request exchange? Does this drain battery faster in any way?
Click to expand...
Click to collapse
yes it is a good reason. kills battery

delete please.. double post

I thought the whole time that the "glow in the dark" was a feature. Its something I certainly don't mind, as I have found it rather useful.
But since its not a feature... then... defect? Haha. Well, this EVO is going back to the store anyway.

Waking to a black screen

This started yesterday out of the blue.
When i press the power button to wake up the phone, It wakes to a black screen. The Home,back, menu and search icon light up. I can even slide to unlock. It all works but the screen remands black. Now if i press the power button on/off a few times everything works and the screen will awake.
Once the screen is woke everything runs fines. The only other problem i ever had was the launcher force closing.
Running "Vision_Gingerbread_S_TMOUS_2.13.531.8"
I reflash the rom when this problem first started. I really need to fix this. IDK if it is software or hardware. Has anyone had this problem before? I wasnt planing on buying another phone till income tax time which is about 7-8months from now.
also tried adjusting the brightness, and disabling the animations.

I had the same problem on Vision roms. Now I'm on CM stable, and get it once in a blue moon.

Yea i flashed that rom along with some others. I am thinking its hardware problem.
I took the phone apart and the ribbon cable that runs from the phone to the screen casing has a little dot on it( a rip in the insulation). Im guessing something in my pocketed one day kinda cut into it or just wear and tear.
Im going to try to find that cable and replace it and see if it fixes my problem.
For now i just put a little tape on it to stop the hole from getting bigger. and shorting out with the metal casing.
Anyone know where to start looking for this cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found screens and keyboard stuff but havent found this cable yet

your black screen problem is a known issue for your phonehaving trouble catching up (speed wise) and it does that until you turn the screen on and off again. I suggest upping your minimum clock speed to something like 475mhz. apart from that if you're using something like Virtuous 2.0, then the OC daemon will eliminate that issue. I haven't seen the issue on my phone for the past few months after i switched to using the OC daemon provided by rmk and the virtuous team.

mputtr said:
your black screen problem is a known issue for your phonehaving trouble catching up (speed wise) and it does that until you turn the screen on and off again. I suggest upping your minimum clock speed to something like 475mhz. apart from that if you're using something like Virtuous 2.0, then the OC daemon will eliminate that issue. I haven't seen the issue on my phone for the past few months after i switched to using the OC daemon provided by rmk and the virtuous team.
Click to expand...
Click to collapse
That doesnt explaine y it just started doimg this tho. I unhooked the ribbon and plugwd it back. Also havnet openwd the the phone since and all has been good. So I bwlieve its just hardware. Maybe the cable came lose.

unless you screwed something up hardware wise, it is the minimum speed trying to catch up with the turn on and failing.
I had this problem before and switching to the OC daemon solved it. It's a known fact.
those ribbons usually come with the screen, so search ebay for the screen component, you'll have better luck there.

mputtr said:
unless you screwed something up hardware wise, it is the minimum speed trying to catch up with the turn on and failing.
I had this problem before and switching to the OC daemon solved it. It's a known fact.
those ribbons usually come with the screen, so search ebay for the screen component, you'll have better luck there.
Click to expand...
Click to collapse
Son and wife have knocked it off the desk I put it. Fallen about 2ft onto the carpet. So im welling to bet the cable was just lose. Will give it a week and ser if the problem comes back. Thanx for the help.
It also did the blank screen doing boot up and recovery which has to be hardware since the os hasnt booted yet.

sure. good luck with it then.

I think the minimum clock speed is a good theory. I have mine on 245MHz, will make it higher and see if it helps. Now that I think about it I started having the problem since rooting and playing with SetCPU.
Yep, having it higher there is an increase in how long it takes for the screen to turn on after pressing the button (Yes, I do see in milliseconds ) Now i'm on 768 min and 1516 max.

I had a trackpad wake to black screen on CM 7.1RC1. Upgraded to the latest nightly and it's fine

Well so far problem seems to be gone since I took the phone apart. I didnt change any settimgs or anything.

[Q] Proximity Sensor doesn't work with CyanogenMod-7-11152011-NIGHTLY

Hi,
I have got an white ZTE Blade (Gen1, with normal TFT) bought from Orange Austria in February 2011. I used Swedish Spring RLS5 for almost a year without any problems.
Because I'm a big fan of Cyanogenmod, yesterday I switched to Gen2 and installed CyanogenMod7. Everything is fine except the proximity sensor.
I have already tried
-) wipe cache and wipe dalvik cache
-) disable automatic display brightness
-) calibrate proximity via "settings --> ZTE Blade device settings --> calibrate proximity sensor"
After calibrating it I get the following "Display proximity sensor data":
prox_theshold_hi=1276
prox_theshold_lo=1021
prox_int_time=246
prox_adc_time=255
prox_wait_time=255
prox_intr_filter=0
prox_config=0
prox_pulse_cnt=16
prox_gain=32
When I put my finger on the sensor and calibrate it the following values changes:
prox_theshold_hi=1534
prox_theshold_lo=1227
Due to the change if I keep my finger on it and because it has always worked with Swedish spring, a hardware fault is excludable.
Any hint or help is welcome!
Regards,
Arthur

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i use these and i use CM
i too had the problem but calibrating it in bright sun solved the problem u actually need bright conditions at least for me.

saaransh9 said:
i use these and i use CM
i too had the problem but calibrating it in bright sun solved the problem u actually need bright conditions at least for me.
Click to expand...
Click to collapse
Hi, saaransh9!
Thank you for your hint!
Are you sure that you don't confuse light sensor and proxmity sensor?
I thought that the proximity sensor is light independend!?
Anyway I will give it a try tomorror at midday.
Regards,
Arthur

8200 said:
Hi, saaransh9!
Thank you for your hint!
Are you sure that you don't confuse light sensor and proxmity sensor?
I thought that the proximity sensor is light independend!?
Anyway I will give it a try tomorror at midday.
Regards,
Arthur
Click to expand...
Click to collapse
dont worry what i m saying is right me myself tried 10s of times and atlast was all in sweat to get it working.

saaransh9 said:
dont worry what i m saying is right me myself tried 10s of times and atlast was all in sweat to get it working.
Click to expand...
Click to collapse
Thank you but it didn't work :-(
I recently went out (because the sun was shining beautifully, midday) and tried calibrating proximity.
As soon as I put the phone in the direct sun-light I got the error "Something went wrong. Aborting".
In my shadow it worked but the values are almost ~ the same.
I can't believe that the sensor is defect because it did work with Swedish Spring RLS5.

After I could not solve the problem (and even the light sensor made problems), I switched back to Gen1 and restored my nandroid backup of Swedish Spring RLS5. Instantly both sensor worked just fine!
So there is a bug with the proximity and light sensor in CM 7 for ZTE blade. :-/
8200 said:
I can't believe that the sensor is defect because it did work with Swedish Spring RLS5.
Click to expand...
Click to collapse

I'm using cm7 stable build and both are working just fine.
Try flashing a stable build instead of a nightly
Sent from my Blade using xda premium

proximity sensor
saaransh9 said:
dont worry what i m saying is right me myself tried 10s of times and atlast was all in sweat to get it working.
Click to expand...
Click to collapse
I have a HTC HD2 with Cyanonen mod9 NexusHD2. Android versin 4.0.4 and kernel 2.6.32. And i have a problem. When i call, the proximiti sensor off the screen. But when i need to see the dealer i cant, during the call. Exemple: i call to my voicemail and i need to dill any number to hear. But the screen is out. How to fix it?
Thanks.

Nobi said:
I have a HTC HD2 with Cyanonen mod9 NexusHD2. Android versin 4.0.4 and kernel 2.6.32. And i have a problem. When i call, the proximiti sensor off the screen. But when i need to see the dealer i cant, during the call. Exemple: i call to my voicemail and i need to dill any number to hear. But the screen is out. How to fix it?
Thanks.
Click to expand...
Click to collapse
U can just switch off the sensor u will not press any buttons because with the new dialer the buttons are located at the bottom
Sent from my Blade using xda premium

[q] nexus 4 acting weird (possessed)

Hey guys
I hope you can help me, after 4.3 update my nexus starts working weird, like it has been possessed, suddenly it start playing by itself the screen starts moving and open some applications by itself....it recovers when i press the powen buttom two times, so it get back to normal. But this problem has started continuesly apprearing, sometimes im texting and then the phone press some buttoms by itself....so weird.
At the beginning i though i had a virus so i downloaded avast but the problem was still there, then i though mm it might by the image.
So i unlocked the bootloader and then, flash image 4.3, seems the problem was resolved but after 30 min it was there again.
I though OK maybe 4.3 its the problem, i flashed 4.2 but it was worst.
I was reading another post and it seems some users that has NEXUS 7 are experience the same issue:
http://forums.androidcentral.com/go...g-weird-after-thundershowers.html#post3054272
Well i have a NEXUS 7 2013 and its working good.
However my lovely NEXUS 4 has been possessed, anybody has experienced the same problem ?
I recorded video to explain the problem: http://youtu.be/R4GHnVA7ZHw
Thanks in advance for your help.
BR.

Did you just said possessed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

badboy47 said:
Did you just said possessed?
Click to expand...
Click to collapse
Yeah haha i dont know how to call it ? The screen start moving randomly and never stop moving, if you open the application list, then some of the application start loading without any touch, its like someone is playing with your device while you are using it haha.

joadchob said:
Hey guys
I hope you can help me, after 4.3 update my nexus starts working weird, like it has been possessed, suddenly it start playing by itself the screen starts moving and open some applications by itself....it recovers when i press the powen buttom two times, so it get back to normal. But this problem has started continuesly apprearing, sometimes im texting and then the phone press some buttoms by itself....so weird.
At the beginning i though i had a virus so i downloaded avast but the problem was still there, then i though mm it might by the image.
So i unlocked the bootloader and then, flash image 4.3, seems the problem was resolved but after 30 min it was there again.
I though OK maybe 4.3 its the problem, i flashed 4.2 but it was worst.
I was reading another post and it seems some users that has NEXUS 7 are experience the same issue:
http://forums.androidcentral.com/go...g-weird-after-thundershowers.html#post3054272
Well i have a NEXUS 7 2013 and its working good.
However my lovely NEXUS 4 has been possessed, anybody has experienced the same problem ?
Thanks in advance for your help.
BR.
Click to expand...
Click to collapse
Try an excorcism by doing a data factory reset in settings/accounts/backup and restore. if that doesn`t help reflash the factory image in fastboot.

gee2012 said:
Try an excorcism by doing a data factory reset in settings/accounts/backup and restore. if that doesn`t help reflash the factory image in fastboot.
Click to expand...
Click to collapse
Hi already tried all that.
First factory reset, then flash image 4.3 and 4.2 over fastboot.
Same issue.
Check the video i made http://youtu.be/R4GHnVA7ZHw

joadchob said:
Hi already tried all that.
First factory reset, then flash image 4.3 and 4.2 over fastboot.
Same issue.
Check the video i made http://youtu.be/R4GHnVA7ZHw
Click to expand...
Click to collapse
Your phone looks defective (hardware) and you need to take it in for repair. You can`t fix this bro. Good luck

gee2012 said:
Your phone looks defective and you need to take it in for repair. You can`t fix this bro. Good luck
Click to expand...
Click to collapse
Really, i was hoping someone was experiecing a similar issue, so weird
Thanks for the help.

does this happen only when you are plugged in or when unplugged as well?

simms22 said:
does this happen only when you are plugged in or when unplugged as well?
Click to expand...
Click to collapse
well i have not paid attention on that.
But the problem does not appear everytime, for example right now ive been playing with it for 1 hour no lag so far.
But from time to time it appears, weird.
It really looks possessed haha

Do you have a screen protector on your Nexus? Sometimes some of the cheaper ones can cause interference with touchscreens, making them do that. (Happened to my old Droid Milestone)

Draw a pentagram " anyone will do. A good one is the alchemy circle from full metal alchemist "
Sacrifice two ducks, a rat, and two hundred donkeys and start channeling your thoughts and summon tool guy "aka Satan"
In all seriousness did your phone get wet? And I mean that in a totally non sexual way....

Ouch it's really acts like possessed one, you need to call some priest (kidding) :silly:
If seriously, what version of android are you using? It is got wet, or it's just started suddenly to act like this?

You're not alone, well then again i did get a replacement lcd/digitizer so it could be a problem with that.
But without a doubt i'm getting the same symptoms as you, sometimes my screen touches itself and what not.
Power on/off does solve it too.

If possible enable show touch events under developer options that will help you track down if its touch events.
my N4 has recently started showing these signs without any specific reason, its not possessed but what i can understand is my device has got a horizontal strip in middle of screen which is non responsive to touch and the random touch events are tracked to that specific region only.

I have the same problem. I've got a brand new nexus 4 and its really jumpy and the best possible way to describe it is definitely possessed. Does anyone have any solutions or shall i just send it back and get it replaced?