Stable Hybrid Release
SHR is one of the many distributions that currently work on the Openmoko phones. You can compare a distribution with an Operating System on normal computers. It gives the phone all the software needed for operating. For more information about the different flavors, see distributions. Template:SHR
The Stable Hybrid Release (SHR) is intended to be a community driven distribution composed of the FSO and some basic applications, that can be configured to use several diffrent graphical toolkits, for example GTK or EFL. SHR is based on the FSO build.
Why SHR exists
At first, SHR was introduced in order to use the Openmoko2007.2 GTK software in combination with the new FSO. Things have changed. SHR is now mainly a community driven distribution, that contains some basic applications which make use of the FSO.
Why not FSO?
FSO is the initiative by Mickey Lauer and crew to create a good D-Bus infrastructure which runs on the neos, among other devices.
FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application, right now.)
FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.
Other people are supposed to put a front end on FSO. So that's what we're doing.
See the Developer Info on the upper right side of the SHR project page.
How to join
- Hang out in #openmoko-cdevel on irc.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau, Ainulindale and quickdev.)
- Send a request to join on the SHR project on the OM projects page.
- Join firstname.lastname@example.org and send an introductory email. The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.
- See SHR Development to find out how to set up your development environment to work on existing SHR packages.
Tasks & status
The list of tasks is available at the SHR Milestone page. Some information is missing this is why the table below is still valid.
|Task||Status||Owner||Helping out||Last update||Comment|
|Run the build host||Have server CPU time and disk space||paulproteus||2008-07-03|
|Test & label good SHR releases||Awaiting builds||Nobody|
|Set up launcher (home) page and document how to add new apps to it||The launcher will be the apps tab of openmoko-today2||2008-07-08|
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR||Done! SHR Project HomePage||2008-07-08|
|fork media player for SHR||Done!||2008-08-07|
- Needs owner! - someone needs to take responsibility for this task
- Not started - someone has taken responsibility, but hasn't done anything yet...
- Started - someone has started work, but there is nothing usable yet
- Alpha - it might work, maybe
- Beta - it probably works most of the time
- Maintained - a stable release is out there, working on oddball bugs & new features
- Done - a stable release is out there, no activity on this task now
List of packages included
- libframeworkd-glib (C bindings for frameworkd dbus interface)
- ophonekitd (daemon that handles frameworkd events, for example showing the UI on an incoming call)
There's a buildhost sponsored by bearstech.com, which builds the shr images:
Installing an image
Download the appropriate uImage and jffs2 from http://shr.bearstech.com/shr-testing/images/neo1973/ and install as normal. Afterwards, run opkg update && opkg upgrade. You may need to edit /etc/resolv.conf and put something like this in it:
Getting the source code
There is no need to download the code independently as it is automatically obtained when setting the development environment described in SHR Development.
Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd. So in order to be able to build and test these applications, you have to build frameworkd and gsm0710muxd.
In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus. libfraemworkd-glib is heavily used by SHR applications and now hosted on http://git.freesmartphone.org/?p=libframeworkd-glib.git;a=summary.
SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/lf.png.