|
Posted by Mike K on November 16, 2006, 2:56 pm
Please log in for more thread options Thanks for replying Todd.
Well i dont have any 3rd party software on my SDA and I even removed
everything from the phone (clear storage) which supposedly puts it back
to factory settings (i am assuming this is the same as hard reset).
That didnt work. I had 11 meetings and appointments today and none of
them came up but my older recurring appointment came up just fine. I am
waiting for the refurbished sda to show up tomorrow. I am hoping its
scenario #1.
How do you like your MDA? IF this fails i might have to go that route.
I had the Moto Q from Verizon but i thought it was a little big and i
couldn't use it in Europe so I opted for the Tmobile SDA.
> At 16 Nov 2006 10:08:45 -0800 Mike K wrote:
>
> > Any one???I use an MDA, not an SDA, but I think the advice I'm offering is
generic
> enough to apply.
>
> I've had intermittent alarm issues twice, and a hard boot solved it both
> times. Both times the problem was caused by me, using 3rd party software
> to edit the device's notification queue. (Bad idea!)
>
> IMO, your problem is most likely one of three issues-
>
> 1) Bad hardware- IMHO unlikely, but a replacment from T-Mo would solve it
> if it is. Don't be afraid of refurbs. My brand-new MDA's digitizer died
> after 60 days- the refurb replacement has worked for six months so far
> without a hitch...
>
> 2) A software/OS bug. In this case, any SDA will have the same problem,
> so the replacement will be equally problematic. You'll just have to live
> with it and pray for a new ROM upgrade. This "problem" is unlikely, IMO,
> or everyone with an SDA would be screaming.
>
> 3) Some errant third party app (most likely one that schedules something-
> a replacement clock/calendar app, a scheduled backup app, anything that
> does SOMETHING at a scheduled time) is screwing up the Notification
> Queue. If so, a hard reset followed by NOT installing or using that app
> is the solution. This, IMHO, is the most likely culprit but also the
> hardest to nail down. You'll have to hard reset and run virtually
> nothing but the built-in software long enough to verify the problem isn't
> appearing, and then add your third party apps one at a time, waiting each
> time beore adding the next long enough to ensure the problem hasn't
> returned. Eventually you'll find the app that screws up the notifications,
> and have to decide what's mord important to you: that app, or reliable
> alarms...
>
> Good luck! (You'll need it!)
>
> --
> Posted via a free Usenet account fromhttp://www.teranews.com
| 
XML Sitemap