TX "Alarm from standby crash" - My fix

[Felekar]

This crash is thus:
An alarm is set to go off at whatever time.
The palm goes into standby mode, by whatever means.
The alarm goes off, the palm locks up, and a soft reset is required to fix it.

My solution:
Set system default clock back to 312.
-little update-
I've been able to bring the clock back down to 156 with no ill effects now, though your mileage may vary.

I had played around with a number of programs already, and I finally set out to fix this last issue I was having with the palm. I found that if I disabled all my third party apps, it went away. After that it was a simple task to torn on each one, and have an alarm go off after each to see what the problem was.
It turned out to be the over/underclocking software I had installed.
Switched to a different one, same issue.

So, rather than live without the wonderful benefits of a longer battery life, I tried just resetting the clock setting back to default. Success! no more crash. After that it was just a simple matter to set the clock speed of each individual program to what I wanted it to be. Sure, it takes a bit of work, but I like my alarms! :D

Also, apologies if this had been posted at one point in the past. I did my best to search for a solution, but the only one I found was something about removing FrameTX. This did nothing for me though.

[technical1]

Felekar,

Sounds like you isolated the problem in a good, analytical fashion, & solved it the same way.

I see no problem here. I've had to do the same kind of thing - changing individual app's clock speeds to make it work (better).

Enjoy,

[_Em]

My reliable clock rate on the TX on software wake from sleep is between 156 and 416. Outside that range it's hit & miss.

[Mickets]

This crash is thus:
An alarm is set to go off at whatever time.
The palm goes into standby mode, by whatever means.
The alarm goes off, the palm locks up, and a soft reset is required to fix it.

My solution:
Set system default clock back to 312.
-little update-
I've been able to bring the clock back down to 156 with no ill effects now, though your mileage may vary.

I had played around with a number of programs already, and I finally set out to fix this last issue I was having with the palm. I found that if I disabled all my third party apps, it went away. After that it was a simple task to torn on each one, and have an alarm go off after each to see what the problem was.
It turned out to be the over/underclocking software I had installed.
Switched to a different one, same issue.

So, rather than live without the wonderful benefits of a longer battery life, I tried just resetting the clock setting back to default. Success! no more crash. After that it was just a simple matter to set the clock speed of each individual program to what I wanted it to be. Sure, it takes a bit of work, but I like my alarms! :D

Also, apologies if this had been posted at one point in the past. I did my best to search for a solution, but the only one I found was something about removing FrameTX. This did nothing for me though.

A-Ha... this may mean a lot of things. I have the same problem. I have some apps running at speeds lower than 100 (I use Warp Speed), and am using Bell Time and Watchmaker.

Did you have to increase the speed of just the alarm program, or any other apps as well? What alarm program were you using?

I began lowering the speed of the alarm software ever since I found that the old Big Clock seemed to drain down the battery on my TX, and since I didn't need a fast alarm program...

[Mickets]

All,

I seemed to have solved the problem I had with the Palm locking when some alarms came during standby. It's at this post here (http://www.1src.com/forums/showthread.php?p=1060381#post1060381).