Archived:Custom alarm sounds and categories are ignored on S60 2nd and 3rd Editions (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Custom alarm sounds set using TASShdAlarm::SoundName() are ignored. Also, it is not possible to set custom alarm categories, for example alarms associated with a particular application or application engine.

Article Metadata

---

Compatibility

Platform(s): S60 2nd Edition and FP1, FP2, FP3
S60 3rd Edition and FP1

---

Article

Created: User:Technical writer 1 (10 May 2007)

Last edited: hamishwillee (21 Jun 2012)

Description

S60 alarm implementation ignores the custom alarm sounds set using TASShdAlarm::SoundName():

TASShdAlarm iAlarm;
...
iAlarm.SoundName().Copy("SoundFile");   // ignored

The alarm server is only capable of playing the default clock or calendar alarm sounds.
Also, custom categories, set using TASShdAlarm::Category(), are ignored. Only two categories are supported (KASCliCategoryClock for clock alarms, rest of the category values are interpreted as calendar alarms).

Solution

No known solution.