Issues waking the phone?Support


Last Updated:

  1. Sgroh87

    Sgroh87 Active Member This Topic's Starter

    Joined:
    Jul 12, 2010
    Messages:
    35
    Likes Received:
    4
    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.
     

    Advertisement
  2. aquaitious

    aquaitious Well-Known Member

    Joined:
    Jul 22, 2010
    Messages:
    263
    Likes Received:
    43
    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.
     
  3. Teknologic

    Teknologic Well-Known Member

    Joined:
    Mar 23, 2010
    Messages:
    969
    Likes Received:
    93
    Yeah man, lockscreen overlays can cause slowdown in waking the phone. I've had this problem with bTunes once and gentle alarm.
     
  4. macprv

    macprv Well-Known Member

    Joined:
    Mar 16, 2010
    Messages:
    337
    Likes Received:
    47
    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??
     
  5. diazamet

    diazamet Member

    Joined:
    Nov 17, 2009
    Messages:
    13
    Likes Received:
    0
    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:
    Code (Text):
    1. D/KeyguardViewMediator(   85): wakeWhenReadyLocked(26)
    2. D/KeyguardViewMediator(   85): handleWakeWhenReady(26)
    3. D/KeyguardViewMediator(   85): pokeWakelock(5000)
    4. I/power   (   85): *** set_screen_state 1
    5. D/AK8973  (   64): Compass Start
    6. D/AK8973  (   64): Compass CLOSE
    7. D/AK8973  (   64): Compass Start
    8. W/ActivityManager(   85): Timeout of broadcast BroadcastRecord{44e03ab8 com.levelup.beautifulwidgets.ACTION_UPDATECLOCK} - receiver=null
    9. W/ActivityManager(   85): Receiver during timeout: ResolveInfo{44e1ea28 com.levelup.beautifulwidgets.HomeWidget p=0 o=0 m=0x0}
    10. W/ActivityManager(   85): finishReceiver called but none active
    11. I/Process (   85): Sending signal. PID: 8151 SIG: 3
    12. I/dalvikvm( 8151): threadid=3: reacting to signal 3
    13. I/dalvikvm( 8151): Wrote stack traces to '/data/anr/traces.txt'
    14. I/Process (   85): Sending signal. PID: 85 SIG: 3
    15. I/dalvikvm(   85): threadid=3: reacting to signal 3
    16. I/dalvikvm(   85): Wrote stack traces to '/data/anr/traces.txt'
    17. I/Process (   85): Sending signal. PID: 3514 SIG: 3
    18. I/dalvikvm( 3514): threadid=3: reacting to signal 3
    19. I/dalvikvm( 3514): Wrote stack traces to '/data/anr/traces.txt'
    20. I/Process (   85): Sending signal. PID: 155 SIG: 3
    21. I/dalvikvm(  155): threadid=3: reacting to signal 3
    22. I/dalvikvm(  155): Wrote stack traces to '/data/anr/traces.txt'
    23. I/Process (   85): Sending signal. PID: 153 SIG: 3
    24. I/dalvikvm(  153): threadid=3: reacting to signal 3
    25. I/dalvikvm(  153): Wrote stack traces to '/data/anr/traces.txt'
    26. I/Process (   85): Sending signal. PID: 166 SIG: 3
    27. I/dalvikvm(  166): threadid=3: reacting to signal 3
    28. I/dalvikvm(  166): Wrote stack traces to '/data/anr/traces.txt'
    29. I/Process (   85): Sending signal. PID: 167 SIG: 3
    30. I/dalvikvm(  167): threadid=3: reacting to signal 3
    31. I/dalvikvm(  167): Wrote stack traces to '/data/anr/traces.txt'
    32. I/Process (   85): Sending signal. PID: 7419 SIG: 3
    33. I/Process (   85): Sending signal. PID: 7737 SIG: 3
    34. I/Process (   85): Sending signal. PID: 7726 SIG: 3
    35. I/Process (   85): Sending signal. PID: 6685 SIG: 3
    36. I/dalvikvm( 6685): threadid=3: reacting to signal 3
    37. I/dalvikvm( 6685): Wrote stack traces to '/data/anr/traces.txt'
    38. I/Process (   85): Sending signal. PID: 6063 SIG: 3
    39. I/dalvikvm( 6063): threadid=3: reacting to signal 3
    40. I/dalvikvm( 6063): Wrote stack traces to '/data/anr/traces.txt'
    41. I/Process (   85): Sending signal. PID: 6397 SIG: 3
    42. I/dalvikvm( 6397): threadid=3: reacting to signal 3
    43. I/dalvikvm( 6397): Wrote stack traces to '/data/anr/traces.txt'
    44. I/Process (   85): Sending signal. PID: 7591 SIG: 3
    45. I/Process (   85): Sending signal. PID: 7292 SIG: 3
    46. I/dalvikvm( 7292): threadid=3: reacting to signal 3
    47. I/dalvikvm( 7292): Wrote stack traces to '/data/anr/traces.txt'
    48. I/Process (   85): Sending signal. PID: 6755 SIG: 3
    49. I/dalvikvm( 6755): threadid=3: reacting to signal 3
    50. I/dalvikvm( 6755): Wrote stack traces to '/data/anr/traces.txt'
    51. I/Process (   85): Sending signal. PID: 7534 SIG: 3
    52. I/dalvikvm( 7534): threadid=3: reacting to signal 3
    53. I/dalvikvm( 7534): Wrote stack traces to '/data/anr/traces.txt'
    54. I/Process (   85): Sending signal. PID: 6587 SIG: 3
    55. I/dalvikvm( 6587): threadid=3: reacting to signal 3
    56. I/dalvikvm( 6587): Wrote stack traces to '/data/anr/traces.txt'
    57. I/Process (   85): Sending signal. PID: 7402 SIG: 3
    58. I/dalvikvm( 7402): threadid=3: reacting to signal 3
    59. I/dalvikvm( 7402): Wrote stack traces to '/data/anr/traces.txt'
    60. I/Process (   85): Sending signal. PID: 7390 SIG: 3
    61. I/dalvikvm( 7390): threadid=3: reacting to signal 3
    62. I/dalvikvm( 7390): Wrote stack traces to '/data/anr/traces.txt'
    63. I/Process (   85): Sending signal. PID: 472 SIG: 3
    64. I/dalvikvm(  472): threadid=3: reacting to signal 3
    65. I/dalvikvm(  472): Wrote stack traces to '/data/anr/traces.txt'
    66. I/Process (   85): Sending signal. PID: 8151 SIG: 9
    67. E/ActivityManager(   85): ANR in com.levelup.beautifulwidgets
    68. E/ActivityManager(   85): Reason: Broadcast of Intent { act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4 cmp=com.levelup.beautifulwidgets/.HomeWidget (has extras) }
    69. E/ActivityManager(   85): Load: 6.08 / 6.09 / 6.01
    70. E/ActivityManager(   85): CPU usage from 60369ms to 50ms ago:
    71. E/ActivityManager(   85):   system_server: 0% = 0% user + 0% kernel / faults: 62 minor
    72. E/ActivityManager(   85):   events/0: 0% = 0% user + 0% kernel
    73. E/ActivityManager(   85):   akmd: 0% = 0% user + 0% kernel / faults: 61 minor
    74. E/ActivityManager(   85):   oid.voicesearch: 0% = 0% user + 0% kernel / faults: 24 minor
    75. E/ActivityManager(   85):   zygote: 0% = 0% user + 0% kernel / faults: 8 minor
    76. E/ActivityManager(   85):   adbd: 0% = 0% user + 0% kernel
    77. E/ActivityManager(   85):   putmethod.latin: 0% = 0% user + 0% kernel / faults: 13 minor
    78. E/ActivityManager(   85):   m.android.phone: 0% = 0% user + 0% kernel / faults: 26 minor
    79. E/ActivityManager(   85):   ounter:phonelog: 0% = 0% user + 0% kernel / faults: 8 minor
    80. E/ActivityManager(   85):   d.process.acore: 0% = 0% user + 0% kernel / faults: 20 minor
    81. E/ActivityManager(   85):   viders.calendar: 0% = 0% user + 0% kernel / faults: 20 minor
    82. E/ActivityManager(   85):   ogle.android.gm: 0% = 0% user + 0% kernel / faults: 22 minor
    83. E/ActivityManager(   85):   com.twidroid: 0% = 0% user + 0% kernel / faults: 12 minor
    84. E/ActivityManager(   85):   com.amazon.mp3: 0% = 0% user + 0% kernel / faults: 7 minor
    85. E/ActivityManager(   85):   om.drivesafe.ly: 0% = 0% user + 0% kernel / faults: 14 minor
    86. E/ActivityManager(   85):   ectricsheep.asi: 0% = 0% user + 0% kernel / faults: 22 minor
    87. E/ActivityManager(   85):  +flush-31:0: 0% = 0% user + 0% kernel
    88. E/ActivityManager(   85):  +logcat: 0% = 0% user + 0% kernel
    89. E/ActivityManager(   85):  +re-initialized>: 0% = 0% user + 0% kernel
    90. E/ActivityManager(   85):  +re-initialized>: 0% = 0% user + 0% kernel
    91. E/ActivityManager(   85):  -flush-31:0: 0% = 0% user + 0% kernel
    92. E/ActivityManager(   85):  -logcat: 0% = 0% user + 0% kernel
    93. E/ActivityManager(   85): TOTAL: 100% = 0% user + 0% kernel + 98% iowait
    94. I/Process (   85): Sending signal. PID: 8151 SIG: 9
    95. W/ActivityManager(   85): Process ProcessRecord{44e7ac08 8151:com.levelup.beautifulwidgets/10046} failed to attach
    96. I/power   (   85): *** set_screen_state 0
    97. W/ActivityManager(   85): Activity pause timeout for HistoryRecord{44d71e40 com.android.launcher2/.Launcher}
    98. D/AK8973  (   64): Compass CLOSE
    99. W/ActivityManager(   85): Activity idle timeout for HistoryRecord{44d71e40 com.android.launcher2/.Launcher}
    100.  
    101.  
    Does this mean anything to anybody? I see lots of references to 'BeautifulWidgets' could this be causing the problem?
     
  6. Teknologic

    Teknologic Well-Known Member

    Joined:
    Mar 23, 2010
    Messages:
    969
    Likes Received:
    93
    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
     

Share This Page

Loading...