maemo.org Bugzilla – Bug 3635
Publish sources of alarm framework
Last modified: 2010-01-14 12:27:55 UTC
You need to
before you can comment on or make changes to this bug.
It would be great to have an open source implementation of the alarm framework.
The main reason for this is portability: It would enable people wo want to use
the HAF on other devices than the Nokia tablets to make use of this framework
too. The same applies for applications that run both in Maemo and in other GUI
environments. For these applictions it would be very useful to use the same API
Can you define "alarm" a bit better and describe some usecases? It makes it
easier to convince people...
I see, the name is not consistent in the documentation.
I'm not sure if other components are affected, but the alarm framework consists
of libalarm and alarmd at least.
(In reply to comment #1)
> Can you define "alarm" a bit better and describe some usecases?
Especially as I think that e.g. "cron" from Debian provides most of the alarm
functionality except the device wakeup when the device is powered off
(which should be uncommon use-case)...
That's true - atd can do the same job, but that's not my point. Developing
applications you want to use the same API on all devices. libalarm offers a
nice highlevel api independent from the machanism that is used, but the
motivation to use it is very limited since it is not portable in any way.
In principle the request sounds reasonable. I will organize a request
internally so at least we will know if there is any obstacle.
The first thing to do is define the package/s that belong to this framework and
need to be opensourced: libalarm and alarmd. Anything else?
From what I know only these two components are affected, but maybe these rely
on something that is not known publicly.
Just a note: I will work on this after the Maemo Summit.
As a followup to the discussions at Maemo Summit I have these additional
- garage has a project 'alarmd'
- the project hasn't released any file
- trying to check out the sources returnes an error (403, forbidden)
So it seems the fact that alarm framework sources are not available is a bug
and was not intended.
David told me that the Alarm framework *is* open source. Apparently the sources
are lost/missing, though.
Changing summary and reassigning to him.
At least intended to be, yes.
David, any news here in making the code available to public?
Any news in making the code of libalarm and alarmd available for public?
https://garage.maemo.org/projects/alarmd/ is still empty.
Still nothing in https://garage.maemo.org/projects/alarmd/ .
exists (and .tar.gz also existed in Diablo).
I wonder if the existence of the tar archive would be sufficient to close the
bug. In fact I get a 404 error for this link. The direcory contains deb
That tarball was pulled just because it had not a proper licensing text. We are
working (finally, trust me) on moving alarmd to open development and I expect
to have not only sources but also the code repository out before the Fremantle
beta (or at the same time, latest).
(In reply to comment #15)
> I expect to have not only sources but also the code repository out before the
> Fremantle beta (or at the same time, latest).
Just to warn you: According to the internal ticket things unexpectedly have
become more complicated, so this might not be ready for beta SDK ("to be
released between March-May" as per
The garage svn is still closed, but source tarballs are currently available in
both beta & beta2 repositories, under LGPL 2.1.
It's coming... but the team is extremely busy with the Maemo 5 final release.
Just a quick follow up to this report after reading
http://talk.maemo.org/showthread.php?t=33653 and wondering about the source for
I can see a Debian source package now at this URL:
The SVN repo @ https://garage.maemo.org/projects/alarmd/ is still not
alarmd-1.1.13 has now been copied to
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update