Notices

I will test it and tell you how it goes.

alephito: Thanks! You have a knack for crashing it, it seems

Yes, it was in Chinook while using Modest. Now with Diablo I would expect ALL to have the same problem, but that is not the case, isn't it?

Diablo uses modest as the default client (called Email), so as long as you set up your accounts it should be doing the same alarmd activity. Some people have not had problems with desktop resets using lsbc and modest, some have had problem without using modest. It is frustratingly hard to pin down.

I have enabled alarms and had two go off so far with no problems. If I can make it through the weekend without a reset (and I don't reboot) I will be happy. Let me know your progress with the test as well, and if it is positive I will be prepared to consider the problem tentatively closed.

Well, I just set an alarm one minute ahead. When it sounded, the screen went white. I could only see the alarm popup. When I closed it, the desktop reseted.

Now I will test the app without setting any alarm, but with alarms enabled (this was enough to crash in Chinook).

Thanks.

I am sorry, fiferboy, but I just had my usual reset. I disabled alarms.

Hmm, at least we are better off than version 0.7-5! The frustrating thing is that there are only about a dozen lines that get bypassed with the alarm disable, so it must be something in there that is mucking it up!

Oh well, back to looking...

EDIT: I had a crash over the weekend too. I will try to get this issue fixed, but I am running out of ideas. I'll try to look at the code from another open source app that uses alarmd and see what I am doing wrong.

fiferboy. From previous posts this may be an issue you are still working on but FWIW, the LSBC is 'crashing' the desktop at least daily. By crashing I mean all desktop objects are removed and the ststusbar resets to default icons. (I know the quick way to restore them so nothing is permanently lost). I have 2 colleagues at work with an N810, one has not loaded the LSBC and has no crashes. The other was having crashes and removed LSBC and has not crashed since. For me it almost always crashes overnight with no activity (alarms etc) and often during the day when not being used.
I have version 0.7-6 and have not enabled alarms. If I can provide any other data let me know.

This is a great app and I rely on it so much that despite the crashes I don't want to remove it. Thanks for all your effort in getting this where it is today and continuing to improve it.
Cheers!

Is it possible that this app could be disabling the sounding of alarms? I have two N800s, one that has a custom kernel, multiboot, etc, etc, and another which is a fairly clean Diablo install. Both have LSBC installed, and both no longer sound alarms that are set. The alarms appear to be set, but then they never actually sound.

This caused me some embarrassment in Berlin when I slept through my expected wake-up time, only to discover that the alarms don't work anymore.

WFM. (And just tested)

...however I've learned to not trust the alarm function on the tablets anyway, unless it's fully charged.