Reply
Thread Tools
Posts: 7 | Thanked: 5 times | Joined on Dec 2009
#1
Hi everybody,
Some component of my "Alarms" functionality seems to have been hosed in the last major update: every time I try to access the Alarm Settings dialog, the entire Alarm/Clock application quits, with the delightfully vague complaint that there was some sort of "Internal Error." I'm hoping this is just a simple matter of a corrupt config file (since the alarms still work - I just can't configure them). Consequently, I'm wondering if anyone knows where the clock/alarm application stores its config files, and how I might restore them to factory defaults. Alternatively, if anyone can think of an alternative approach to fixing this problem (short of reflashing), I'd love to hear it.
Thanks!

Last edited by technosopher; 2010-07-06 at 06:47.
 

The Following User Says Thank You to technosopher For This Useful Post:
nicolai's Avatar
Posts: 1,637 | Thanked: 4,424 times | Joined on Apr 2009 @ Germany
#2
Originally Posted by technosopher View Post
Hi everybody,
Some component of my "Alarms" functionality seems to have been hosed in the last major update: every time I try to access the Alarm Settings dialog, the entire Alarm/Clock application quits, with the delightfully vague complaint that there was some sort of "Internal Error." I'm hoping this is just a simple matter of a corrupt config file (since the alarms still work - I just can't configure them). Consequently, I'm wondering if anyone knows where the clock/alarm application stores its config files, and how I might restore them to factory defaults. Alternatively, if anyone can think of an alternative approach to fixing this problem (short of reflashing), I'd love to hear it.
Thanks!
One config file is:
/var/cache/alarmd/alarm_queue.ini

Maybe the alarmd framework documentation has some additional useful information.

regards
nicolai
 

The Following User Says Thank You to nicolai For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 23:11.