Results 1 to 13 of 13
  1.    #1  
    My wife uses her phone alarm every weekday to wake up. However, probably 75% of the time, the alarm doesn't trigger until the screen is turned on via the power button. So if it is set to 6:00AM (yes we've checked AM/PM), and she oversleeps due to it not sounding, then checks her phone by pressing the power button to wake up the screen, it will sound immediately. This can occur 1 minute or even as much as an hour late.

    I have tested this with the stable F102 Kernel which is what she normally runs. I thought it could be a screenstate bug so I removed it and reverted to the stock kernel. However, the same issue remains.

    The phone DOES have some patches. MY phone has the same patches and WAAAY more but works fine. I wanted to check to see if anyone else had experienced this issue. If EPR or doctoring is the only option, I'll go that route. I just wanted to check with the community first.

  2. #2  
    I've had issues with volume settings, but nothing like what you are describing. I have a feeling you will be visiting the doctor soon.
  3. #3  
    kinda talking about this here...may be related?
  4.    #4  
    Thanks...I think this could definately be the issue. I DO notice when the screen is turned on, the displayed time is slow and updates within a second or two.

    I'll look into it. Anyone else have other experiences?
  5. #5  
    Quote Originally Posted by lenmac08 View Post
    kinda talking about this here...may be related?
    Good call. I think this is the thread you are thinking of:
  6.    #6  
    Well last night I changed her Preset Reset to Sync time AND moved the reset time to 3:50am. Her alarm was set to DID NOT go off until she woke up with my phone alarm at 5:30am.

    The DR is coming most likely....but I'm still not sure what's going on. =\
  7. #7  
    Has stuff like this EVER happened to people running a stock kernel?
  8. pk1234's Avatar
    93 Posts
    Global Posts
    94 Global Posts
    This has been happening to me for a while now. I just assumed it was a common problem/bug on all the pres. I would say it the alarm does not go off half the time. I had the same issue with my old pre.

    And whenever its able to go off it will do so a minute before and then at the scheduled time (i.e. alarm set for 4am, will go off at 3:59am and then at 4:00am)

    I have F102 Kernel installed.
  9. #9  
    It might be hard to find, but this was reported and there is a thread somewhere. A possibly related problem that I had and could never solve is that the ringer sound would go down to 0 for no reason and would have to go back into settings and increase the volume each time it happend.
  10. #10  
    Can someone please explain a german why it's called "doesn't go off" when you mean it doesn't goes on?
  11.    #11  
    Quote Originally Posted by somline View Post
    Can someone please explain a german why it's called "doesn't go off" when you mean it doesn't goes on?

    Eh...just bad American jibberish.
  12. #12  
    Yeah, it's just the way some of us say it. Timers/alarms go "off" when they chime. Don't ask why! Lol.

    -- Sent from my Palm Pre using Forums
    I see pandas.
  13. #13  
    I've had the alarms database corrupt a few times - definitely happens when the Pre locks up while playing an alarm and you have to pull the battery to recover. Try deleting all your alarms, reboot (may not be necessary), and set them up as normal. Also I've found that this needs to be done after an OS update. YMMV.
    Palm III > Palm V > Palm Vx > (Sprint) Kyo 6035 > Handspring Treo 300
    > Handspring Treo 600 Oct.'03 > Palm Treo 700P May'06 > Treo 755P Aug.'07 > Pre(-) June'09 + TouchPad July'11 LONG LIVE webOS!!!

Posting Permissions