We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-01-19 00:06:51 +0200

Bug: concurrent alarm and clock event

There seems to be some kind of race condition,when an alarm and a clock event are programmed to happen at the same time: Both alarm sounds and both display screens are racing for the necessary rescources audio and video. On several tests sometimes the calender event wins, on other times the clock event wins. Sometimes they even play both their sounds at the same time.

Most of the times this would not be a problem, as long as - both sounds are loud and penetrant enough to be noticed - both events are displayed. When not displayed in parallel (how could this be possible?), then at least sequencial

Should this be defined? What event is more important - an calender or a clock event?

Bug: concurrent alarm and clock event

There seems to be some kind of race condition,when an alarm and a clock event are programmed to happen at the same time: Both alarm sounds and both display screens are racing for the necessary rescources audio and video. On several tests sometimes the calender event wins, on other times the clock event wins. Sometimes they even play both their sounds at the same time.

Most of the times this would not be a problem, as long as - both sounds are loud and penetrant enough to be noticed - both events are displayed. When not displayed in parallel (how could this be possible?), then at least sequencial

Should this be defined? What event is more important - an calender or a clock event?