Page 2 of 4 FirstFirst 1234 LastLast
Results 21 to 40 of 80
  1. #21  
    Demerol will do the trick !!! im sure !
    ĦṔ-Ḷṫ-Ŧḯη
    Here is a direct link to webOS Doc for all carriers
    http://www.webos-internals.org/wiki/...octor_Versions
    P.S. if i have helped you and you are thankful please hit the thanks button to the right---->
  2.    #22  
    Doctor'd I'm still losing at a rate of about 10% every 30 minutes. 10:07 had 56% and at 11:27 had 30% insert many curse words here

    I don't have any PreWare stuff put back on the phone yet. And Doctor for 1.4.5 doesn't give a clean system, hence I don't know if something was left lying around that is still messing with the phone going to sleep.

    This is completely and totally messed up. It comes down to the powerd-suspend message ...

    POWERD-SUSPEND: POWERD-WOKE after 0s : 0 days, 0h-0m-0s
    POWERD-SUSPEND: Wakeup Source: GPIO (RINGER_SWITCH)
    POWERD-SUSPEND: Wakeup Source: BUTTON (POWER_BUTTON)


    ... but no such button was hit AND the phone isn't acting like it was hit. It just keeps going sleep-wake-sleep-wake-sleep-wake until I actually hit the button to wake it up or charge it.

    Anyone know how to doctor 1.4.5 in such a way the it is a CLEAN install? Nothing left over and getting the phone to a "new from the store" state?
  3. #23  
    Quote Originally Posted by arrasmith View Post
    Anyone know how to doctor 1.4.5 in such a way the it is a CLEAN install? Nothing left over and getting the phone to a "new from the store" state?
    I read somewhere that an old doctor (can't remember the version) will clean everything to stock (even /media/internal). Maybe you can search for that info and if you don't have someone can send the doctor to you.
    Or it's a hardware failure?
    You may also try take out battery and hold the power button for at least 15 seconds and insert battery again. I've heard this will do some kind of reset.
  4.    #24  
    Any doctor before 1.3.1 will do a full erase, but I can't find any online for that. Right now I'm trying the Full Erase option from the Device Info application and I'm now at the restoring the Palm Profile part. Battery out and holding power button didn't do a reset.

    As far as hardware goes I'm hoping someone here with the same problem can actually confirm the PowerD messages in their log files as well. If you do, then I'm sure it isn't specific to my hardware.
  5. #25  
    If I installed the minimal logging patch, am I pretty much screwed for checking for this issue now? :O
  6.    #26  
    Well after another doctoring, a full erase, and then much waiting. The phone still will not sleep and 4 hours runtime is just not cutting it. This makes my Pre worthless. Absolutely worthless.

    I just don't see what is going on. The power daemon keeps getting a wakeup source of the power button. Every two seconds. But, it doesn't actually REALLY wake up. The screen stays black. It REALLY wakes up only if I open the slider or hit the power button for real. WTH. If it was a bad button you would think that it would fully wake or act like the button is being constantly hit (try and power off, etc).

    For anyone else who has access to a terminal or novaterm please type ...

    grep POWER_BUTTON /var/log/messages


    and tell me what you get.
    Last edited by arrasmith; 09/28/2010 at 04:54 PM. Reason: typos
  7.    #27  
    Looks like this powerd bug is old.

    From Wizzums Drain battery 11% per hour.

    When the power button is pressed it event gets handled by "hidd: KeypadEventReader" and it then wakes up. But many people are also seeing the bug which is waking powerd as ...

    Wakeup Source: BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)

    So the question I need to figure out is why. So far I haven't found the event code, but still looking. Wizzums "fixed" his problem by installing a new kernel. My problem started while using UberKernel and has stayed though a doctor of my Pre. I'm going to finally steal my daughter's Pre and root around a working system to see the message difference.

    It would be interesting on how to get powerd it ignore that event. And where it really is coming from.
  8. #28  
    I only get this entry by actual pressing the button.
    Logfile started at 01:00.
    Code:
    2010-09-29T01:36:42.957824Z [2148] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2147.920000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:36:48.837799Z [2150] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2149.880000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:40:35.847686Z [2377] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2376.890000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:42:35.196594Z [2379] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2379.320000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:48:10.573455Z [2403] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2403.770000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:48:10.573883Z [2403] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2403.810000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:49:34.573181Z [2484] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2483.890000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T01:49:36.363616Z [2485] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [ 2485.710000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
  9. #29  
    i got about 7 hours with everything on. Everything, meaning GPS, google services,mode switcher and so on. i also have the issue with the power.
    If you want to buy a Palm Pre is great condition. Here's your chance.

    http://forums.precentral.net/showthr...91#post2782191
  10. #30  
    I just checked and the problem seems to be gone now that i dont have nodoze anymore.
    If you want to buy a Palm Pre is great condition. Here's your chance.

    http://forums.precentral.net/showthr...91#post2782191
  11. philbw's Avatar
    Posts
    310 Posts
    Global Posts
    352 Global Posts
    #31  
    EDIT: Somehow I missed your final post saying it was fixed. Ignore the following.

    Just out of curiosity are you using a Pre battery or an old Centro battery? I know little of the probs with using Centro batteries but was always warned that the Centro battery "doesn't allow the system to sleep correctly" so I figured I'd check.

    - Phil -
  12. #32  
    Hahaha...I just read the wizzum post and I also had uberkernel when I was having this issue. I installed F105 and it stopped.
  13.    #33  
    @somline ...

    Can you (or anyone else for that matter) run:

    grep POWER_BUTTON -A 10 -B 5 /var/log/messages


    ... after you put your phone to sleep and then wake it after 5 minutes. Then post the results here along with the times you put the phone to sleep and woke it up.
  14. #34  
    Sorry was "on the road"
    Code:
    2010-09-29T18:11:26.865417Z [14586] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [14586.830000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T18:12:35.004455Z [14610] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [14610.790000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T18:16:28.263427Z [14613] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [14613.130000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    2010-09-29T18:16:28.263824Z [14613] palm-webos-device user.info powerd: {powerd}: POWERD-SUSPEND: Wakeup Source: [14613.170000] BUTTON (POWER_BUTTON) omap3_wakeup_sources_save+0x114/0x144 (a004962c)
    EDIT: switched to sleep by pressing the power button at 18:11 and waked up at 18:16
  15.    #35  
    @somline ...

    Did that include the " -A 10 -B 5 " switched on the grep? It should have printed 10 lines after and 5 lines before each of the ones you gave me. I'm looking to see what happened around the 18:12 time frame in particular. Because I doubt you hit the power switch then.
  16. #36  
    Sorry. Rename it to *.rtf
    Attached Files Attached Files
  17. #37  
    Hi... I have uberkernal and govnah installed and fully up to date... I can confirm a single set of powerd sleep messages coming from terminal. One for sleep, the other for wake... replicated this three times. Its still possible I suppose... what govnah settings are you folks using?
  18.    #38  
    @somline ...

    That helps a lot. Now I know that the "omap3_wakeup_sources_save" stuff isn't needed information. And the POWER_BUTTON and RINGER_SWITCH are always there for a wake up event.

    The big difference between our phones is that all of yours had normal wake up events (alarm, wifi, and modem) outside of one. Only at 18:11:26 did you have a wakeup event that had no reason listed. That I'm assuming is the bug.

    For me, I never see an alarm, wifi, or modem wake event. It is all just repetitive info that doesn't actually give any useful information. But I might not be seeing those wake events because my log files rotate out so quickly due to them filling up.

    For me
  19. #39  
    Just for your info. I use stock palm kernel.
  20.    #40  
    @bluewanders ...

    I've tried pretty much everything. UberKernel, SBromwichKernel, 105 Kernel, Stock Kernel, Govnah in fixed and screenstate modes, and doctoring my phone to a clean 1.4.5. Still will not sleep.

    Now I'm a goin' beggin' to rwhitby to try and get a handle on where powerd gets its events and how to make it ignore this bug. It would be nice if Palm posted who maintains powerd.
Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions