Community SSU

m (Installation: Whitespace)
Line 13: Line 13:
</div><div style="float: right">
</div><div style="float: right">
Image:Bugsquad-logo-wazd-small.png|84px|center|thumb|Report bug
Image:Bugsquad-logo-wazd-small.png|84px|center|thumb|Report a bug
desc none
desc none
default []
default []

Revision as of 19:47, 11 April 2011

Report a bug



What is it?

Seamless Software Update (SSU), is the term Nokia formerly used for over-the-air updates of Maemo (generally marketed as Maemo Update as of Maemo 5).

The Community Seamless Software Update (CSSU) is being developed by the Maemo community as a continuation of, and expansion on, Nokia's update support. It aims to deliver fixes which would be difficult to deliver through Extras (like core Maemo packages). It won't, however, bundle software which can be installed through the Extras repositories.

There are two such efforts for the Maemo platform. This page describes the one for Fremantle (Maemo 5, as used in the Nokia N900). The Diablo Community Project is doing the same for Diablo (Maemo 4.1, as used in the Nokia N800, N810 and N810 WiMAX Edition).

Who is it for?

Long-term: all N900 users/owners.

For now: power-users, developers, Nokia/Maemo/MeeGo engineers, testers, documentation writers and those willing to risk a re-flash in order to help.


  1. Upgrade to PR1.3, Nokia's last official Maemo 5 update. If you're unsure if you have, Settings > About product should show Version beginning with 20.2010.36.
  2. Click on the Install testing button above. ( for a quick link to this page from your N900)
  3. Hildon Application Manager (HAM) will launch and begin processing (be patient). There are a series of installations for which it will prompt you with messages and warnings. Click "Accept" and "Done" for each to install.
  4. Once this is completed, close HAM and go into the applications menu. Tap the Community SSU icon. This will run through a series of scripts to ensure the community repository are set up.
  5. HAM will re-open and present a system upgrade called Maemo 5 Community SSU. Once installed, your device will reboot.

Problems? Check the Installation FAQ


Main article: Community SSU/Features

How to use new features such as Thomas Perl's hildon-desktop improvements and the status of applications in Portrait Mode with forcerotation.


Main article: Community SSU/Changelog

Changes in the SSU between PR1.3 and various SSU releases.


Get involved on IRC (#maemo-ssu), Talk, Bugzilla and Gitorious.

Can you write documentation? If so, it'd be great to flesh out the wiki page with installation instructions (to make it easy for users to install without worrying about missing a step or getting it wrong); explain more about the SSU and generally spruce up the wiki page and maintain things like the changelogs etc.

Were you involved in developing Maemo? If so, with Nokia now looking to Harmattan and MeeGo, we'd love to see your itches addressed in the Community SSU (CSSU). Have you always wanted to implement something in hildon-desktop, but Management stood in your way? We'd love to have it!

Have you written a patch for Maemo? Raise a bug and let's get it in the CSSU.

Are you a developer? There are numerous patches floating around for hildon-desktop; but they can't be included in the CSSU until they are configurable (via gconf) and default to off.

Want to test? Not only testing this release, but writing test scripts so that each release of the CSSU can get sanity checked before unleashing it into a "stable" repo for end-users. How do we do it? What should be tested? How is it organised?

Want to organise? There's still lots of process left to organise; hopefully there'll be bugs and features to triage and manage in as well as communication of the testing, releases and end-user readiness of the CSSU.

For more information: contact MohammadAG on #maemo-ssu on FreeNode IRC or

QA and bugs

Main article: Community SSU/QA

Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: testing and stable. Changes are carefully tested, with an extensive set of tests, before things are made "stable".

If you have found a bug, in either the testing or stable releases, please raise a bug. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation!


Main article: Community SSU/Development

The Community SSU is developed and managed through Gitorious. Bugs are tracked in Bugzilla. Collaboration largely happens on IRC. Getting involved through development, bug triaging and managing developers is a good way to get involved.