Help Issues waking the phone?

[Sgroh87]

I've been having a problem with the physical buttons on my phone. At first I thought I had a defective power button, because I was having issues with waking the screen. I sent it in to HTC for repairs, and they sent it back saying it was fixed.

Now I'm using WidgetLocker, and sometimes I have issues getting the screen to wake, even using the volume rocker or the trackball. I have to do a battery pull to get the phone to restart.

Should I just get HTC to do a device swap, or is there something I can do to fix this? I'm running the latest official patch from Google, and I'm not rooted, if that makes any difference.

 

[Member196159]

I've been having a problem with the physical buttons on my phone. At first I thought I had a defective power button, because I was having issues with waking the screen. I sent it in to HTC for repairs, and they sent it back saying it was fixed.

Now I'm using WidgetLocker, and sometimes I have issues getting the screen to wake, even using the volume rocker or the trackball. I have to do a battery pull to get the phone to restart.

Should I just get HTC to do a device swap, or is there something I can do to fix this? I'm running the latest official patch from Google, and I'm not rooted, if that makes any difference.

Could it be WidgetLocker that's preventing it from waking? Try the default one for a few days, see if there's a difference...

Or try to remove the locker completely for a few days to see what gives.

 

[Teknologic]

Yeah man, lockscreen overlays can cause slowdown in waking the phone. I've had this problem with bTunes once and gentle alarm.

 

[macprv]

i dont think is the widget.. i to have this problem, randomly, when i pick up the device and try to wake it up via the power button, the touch buttons light up but the screen stays off.. i even received a call once and the ringtone would play but the screen wouldnt turn on.. and that started when i had no special wake up widget.

now i i just installed the no lock widget, and even when i try to wake up the device with the track ball, the screen wouldnt turn on.

this happens randomly, and not very often, but when ever it does hapen, i always have to remove the battery, and now my 16gb card is getting corrupted =/

i dont know but i have my suspicious that maybe the apps to sd is what is causing this problem.. or perhaps the sd card??

 

[diazamet]

I have a problem waking my phone from time to time. The phone is still working to a certain degree because if I hold the volume down button, it will vibrate after a short period.
Because it has been happening every few days, I turned on the debug via usb functionality. Today the screen refused to wake, so I plugged it into my laptop via usb. I am able to start a shell on the phone so it is not locking up completely. I poked around and found the 'logcat' utility. Here is the output when I press the power button to wake the phone:

D/KeyguardViewMediator(   85): wakeWhenReadyLocked(26)
D/KeyguardViewMediator(   85): handleWakeWhenReady(26)
D/KeyguardViewMediator(   85): pokeWakelock(5000)
I/power   (   85): *** set_screen_state 1
D/AK8973  (   64): Compass Start
D/AK8973  (   64): Compass CLOSE 
D/AK8973  (   64): Compass Start
W/ActivityManager(   85): Timeout of broadcast BroadcastRecord{44e03ab8 com.levelup.beautifulwidgets.ACTION_UPDATECLOCK} - receiver=null
W/ActivityManager(   85): Receiver during timeout: ResolveInfo{44e1ea28 com.levelup.beautifulwidgets.HomeWidget p=0 o=0 m=0x0}
W/ActivityManager(   85): finishReceiver called but none active
I/Process (   85): Sending signal. PID: 8151 SIG: 3
I/dalvikvm( 8151): threadid=3: reacting to signal 3
I/dalvikvm( 8151): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 85 SIG: 3
I/dalvikvm(   85): threadid=3: reacting to signal 3
I/dalvikvm(   85): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 3514 SIG: 3
I/dalvikvm( 3514): threadid=3: reacting to signal 3
I/dalvikvm( 3514): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 155 SIG: 3
I/dalvikvm(  155): threadid=3: reacting to signal 3
I/dalvikvm(  155): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 153 SIG: 3
I/dalvikvm(  153): threadid=3: reacting to signal 3
I/dalvikvm(  153): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 166 SIG: 3
I/dalvikvm(  166): threadid=3: reacting to signal 3
I/dalvikvm(  166): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 167 SIG: 3
I/dalvikvm(  167): threadid=3: reacting to signal 3
I/dalvikvm(  167): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 7419 SIG: 3
I/Process (   85): Sending signal. PID: 7737 SIG: 3
I/Process (   85): Sending signal. PID: 7726 SIG: 3
I/Process (   85): Sending signal. PID: 6685 SIG: 3
I/dalvikvm( 6685): threadid=3: reacting to signal 3
I/dalvikvm( 6685): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 6063 SIG: 3
I/dalvikvm( 6063): threadid=3: reacting to signal 3
I/dalvikvm( 6063): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 6397 SIG: 3
I/dalvikvm( 6397): threadid=3: reacting to signal 3
I/dalvikvm( 6397): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 7591 SIG: 3
I/Process (   85): Sending signal. PID: 7292 SIG: 3
I/dalvikvm( 7292): threadid=3: reacting to signal 3
I/dalvikvm( 7292): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 6755 SIG: 3
I/dalvikvm( 6755): threadid=3: reacting to signal 3
I/dalvikvm( 6755): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 7534 SIG: 3
I/dalvikvm( 7534): threadid=3: reacting to signal 3
I/dalvikvm( 7534): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 6587 SIG: 3
I/dalvikvm( 6587): threadid=3: reacting to signal 3
I/dalvikvm( 6587): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 7402 SIG: 3
I/dalvikvm( 7402): threadid=3: reacting to signal 3
I/dalvikvm( 7402): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 7390 SIG: 3
I/dalvikvm( 7390): threadid=3: reacting to signal 3
I/dalvikvm( 7390): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 472 SIG: 3
I/dalvikvm(  472): threadid=3: reacting to signal 3
I/dalvikvm(  472): Wrote stack traces to '/data/anr/traces.txt'
I/Process (   85): Sending signal. PID: 8151 SIG: 9
E/ActivityManager(   85): ANR in com.levelup.beautifulwidgets
E/ActivityManager(   85): Reason: Broadcast of Intent { act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4 cmp=com.levelup.beautifulwidgets/.HomeWidget (has extras) }
E/ActivityManager(   85): Load: 6.08 / 6.09 / 6.01
E/ActivityManager(   85): CPU usage from 60369ms to 50ms ago:
E/ActivityManager(   85):   system_server: 0% = 0% user + 0% kernel / faults: 62 minor
E/ActivityManager(   85):   events/0: 0% = 0% user + 0% kernel
E/ActivityManager(   85):   akmd: 0% = 0% user + 0% kernel / faults: 61 minor
E/ActivityManager(   85):   oid.voicesearch: 0% = 0% user + 0% kernel / faults: 24 minor
E/ActivityManager(   85):   zygote: 0% = 0% user + 0% kernel / faults: 8 minor
E/ActivityManager(   85):   adbd: 0% = 0% user + 0% kernel
E/ActivityManager(   85):   putmethod.latin: 0% = 0% user + 0% kernel / faults: 13 minor
E/ActivityManager(   85):   m.android.phone: 0% = 0% user + 0% kernel / faults: 26 minor
E/ActivityManager(   85):   ounter:phonelog: 0% = 0% user + 0% kernel / faults: 8 minor
E/ActivityManager(   85):   d.process.acore: 0% = 0% user + 0% kernel / faults: 20 minor
E/ActivityManager(   85):   viders.calendar: 0% = 0% user + 0% kernel / faults: 20 minor
E/ActivityManager(   85):   ogle.android.gm: 0% = 0% user + 0% kernel / faults: 22 minor
E/ActivityManager(   85):   com.twidroid: 0% = 0% user + 0% kernel / faults: 12 minor
E/ActivityManager(   85):   com.amazon.mp3: 0% = 0% user + 0% kernel / faults: 7 minor
E/ActivityManager(   85):   om.drivesafe.ly: 0% = 0% user + 0% kernel / faults: 14 minor
E/ActivityManager(   85):   ectricsheep.asi: 0% = 0% user + 0% kernel / faults: 22 minor
E/ActivityManager(   85):  +flush-31:0: 0% = 0% user + 0% kernel
E/ActivityManager(   85):  +logcat: 0% = 0% user + 0% kernel
E/ActivityManager(   85):  +re-initialized>: 0% = 0% user + 0% kernel
E/ActivityManager(   85):  +re-initialized>: 0% = 0% user + 0% kernel
E/ActivityManager(   85):  -flush-31:0: 0% = 0% user + 0% kernel
E/ActivityManager(   85):  -logcat: 0% = 0% user + 0% kernel
E/ActivityManager(   85): TOTAL: 100% = 0% user + 0% kernel + 98% iowait
I/Process (   85): Sending signal. PID: 8151 SIG: 9
W/ActivityManager(   85): Process ProcessRecord{44e7ac08 8151:com.levelup.beautifulwidgets/10046} failed to attach
I/power   (   85): *** set_screen_state 0
W/ActivityManager(   85): Activity pause timeout for HistoryRecord{44d71e40 com.android.launcher2/.Launcher}
D/AK8973  (   64): Compass CLOSE 
W/ActivityManager(   85): Activity idle timeout for HistoryRecord{44d71e40 com.android.launcher2/.Launcher}

Does this mean anything to anybody? I see lots of references to 'BeautifulWidgets' could this be causing the problem?

 

[Teknologic]

Diaza, from your description I think your problem is strictly hardware related. I can't see much wrong with the logcat (but I'm no expert) and if anything it shows that your screen is getting switched on software-wise. Contact HTC support, they should be very good with fixing hardware problems. Good luck