Maemo Wiki Mirror - User contributions [en]

Kernel Power

2016-07-03T01:38:29Z

122.57.34.193: /* Installing kernel-power */

The enhanced kernel "kernel-power" is compatible with [[Maemo_5/PR1.2|PR1.2]] and [[Maemo_5/PR1.3|PR1.3]], contain lots of additional features (IPv6, NAT etc) and bugfixes.
The kernel can be installed via Application manager from the System section. Installation of the customization package Kernel-Power-Settings is sufficient, as it depends on the kernel page.

The custom kernel contains additional modules for IPv6, packet filtering, QoS, NAT, tunneling, kernel configuration, Wifi mesh networking, builtin ext3 for booting from other media, ext4, XFS, reiserfs, NTFS read support, ISO9660, UDF, CIFS, automounter, squashfs, unionfs, device mapper and dm-loop, cryptography, cryptoloop, EFI partitions, UTF8 codepages, mouse+joystick input, PPP, PPTP, serial support, USB hostmode (h-e-n), USB/IP and generic USB device drivers, battery info, overclocking and kexec support.

'''Note: This page is under construction and based on the [[Overclocking|overclocking/undervolting instructions]]. Hence the heavy bias to overclocking.''' For overclocking it includes a large set of possible frequencies (125 MHz-1.15 GHz) which you manually set and try out without flashing a new kernel. The defaults are set to the standard 250-600 MHz range. You can also fine tune the voltages for your device for power-saving. Every device is different.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanced kernel]
[http://talk.maemo.org/showthread.php?t=71879: Discussion of the enhanced kernel beginning with version 47]

Changes between versions are announced on the [https://garage.maemo.org/news/?group_id=1528 garage page].

==Installing kernel-power==

'''Note:''' All commands on this page must be [[root access|run as root]] in [[terminal|X Terminal]] (install rootsh package and enter "root")

'''Note: The power kernel may not be compatible with the currently-installed fcam-drivers package.''' Should you lose camera functionality, you can update them by running as root:<pre>apt-get install fcam-drivers</pre>

'''Note:''' This probably won't work and you'll probably need to install fcam-drivers-1.0.7-2 from extras-devel:
http://repository.maemo.org/extras-devel/pool/fremantle/free/f/fcam-drivers/fcam-drivers_1.0.7-2_armel.deb
install with ''dpkg -i'' command

===Installing the [http://maemo.org/downloads/product/Maemo5/kernel-power-flasher/ Stable Kernel]===

With this kernel you can change the frequency limits, the voltages and DSP frequencies online. It requires firmware [[Maemo 5/PR1.1|PR1.1]] or newer.
# Install the package <code>[http://maemo.org/downloads/product/Maemo5/kernel-power-settings/ kernel-power-settings]</code> (section system in Application manager). It will automatically also install <code>kernel-power-flasher</code>.
# Shutdown the device, and boot it up again.
# The kernel is now installed.

===Installing the Unstable Kernels===
This kernel version contains additional experimental features and patches.

Just enable the [[Extras-testing]] or [[Extras-devel]] catalogue and install according to [[#Installing the Stable Kernel|these instructions]].

Please follow the [[Help_testing_software|QA checklist]] and vote for the package to allow promotion to Extras.

=== Verifying Proper Installation ===
First verify, that the kernel is actually running:<pre>uname -r</pre>
should return "2.6.28.10power<version>".
If it does not, you should reboot or try to [[#Installing kernel-power|install the kernel again]].

=== Upgrade from older versions (< maemo24) ===
The kernel package was previously called <code>kernel-flasher-maemo</code>. Unfortunately, Application Manager does not support package transitions, i.e. installation of the new version leads to conflicts with <code>kernel-maemo</code> and <code>kernel-modules-maemo</code>.
If you have one of the older packages installed it you need to upgrade in X Terminal.
<pre>root
apt-get install -y kernel-power-flasher
apt-get remove kernel-flasher-maemo
</pre>
If the new kernel still doesn't boot up, try
<pre>apt-get install --reinstall -y kernel-power kernel-power-flasher</pre>
Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for uninstalling the old package.

Make sure you reset <code>/etc/pmconfig</code> to the defaults:
<pre>
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 0
sr_vdd2_autocomp 0
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1
</pre>

===Uninstalling kernel-power===
Do not try to uninstall the "kernel-power" package in Application Manager!
This does not remove the kernel, as it is installed in the device's NAND.

'''You never want to uninstall a kernel''', as your device can't work without a kernel.
====Installing the Nokia Kernel with X Terminal====
The standard process for replacing the kernel is as follows:

# Ensure that you have a working Internet connection.
# Install the package '''rootsh'''. (available in the System section of the Application Manager)
# Close the Application Manager.
# Gain root permissions<pre>sudo gainroot</pre>
# Reinstall the stock Nokia kernel<pre>apt-get install --reinstall -y kernel kernel-flasher</pre>
# Should it complete successfully (with "SIGTERM received" and "Image flashed successfully" messages), then you can continue with <pre>apt-get remove -y kernel-power kernel-power-modules</pre>
# After uninstallation, the command <pre>ls -l /lib/modules/current</pre>should show: <pre>... /lib/modules/current -> 2.6.28-omap1</pre>
# Shutdown the device (without any USB cable connected) and boot again.
# The stock kernel should now be installed.

====Installing the Nokia Kernel (Graphical Method)====
If you have a recent kernel (>v27), there is a "Deinstall kernel" application in your menu.
This application is however, still '''experimental''' (for >v27 it is more stable). Only use if have can fall back to reflashing the kernel using the flasher (see below) in case of problems.
Read the instructions carefully when you start the deinstall application!

====Installing the Nokia Kernel with flasher-3.5====
If the device fails to boot or you have other problems, perform the uninstallation from a PC with USB cable and the flasher-3.5 utility:
'''NOTE''': This only works for kernel-power v28 and later. Versions prior to 28 interfere with system files, and may not work properly with the stock Nokia kernel.
# Make sure your battery is properly charged (if it fails, charge your battery)
# Execute the following on your PC (see [[Updating the firmware|this]] for more details)<pre>flasher-3.5 -f --flash-only=kernel -R -F <firmware-image></pre>
*The firmware image file could be, for example, <code>RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin</code>. This is only way of deinstallation with leaked release 1.2 firmware.

=== Upgrading to a new PR ===

Before upgrading, always make a backup. There are two ways of upgrading the firmware to a new Nokia public release (PR):
# [[Updating the firmware|reflashing the complete firmware]] via flasher or NSU. This is safest way (especially for PR1.2). In this case you simply reinstall the kernel after the upgrade. The settings should be restored by the backup application.
# Over The Air (OTA) upgrade: this upgrades only system components of your device so that you don't need to restore your settings or reinstall applications. see below

OTA upgrade:
Disable extras-devel and extras-testing. DIsable autodisconnect if is installed. Perform the upgrade. If the PR does not deliver a new kernel (PR1.1.1) then you're done. If it provides a new kernel (PR1.1 and PR1.2) then you need to reinstall the enhanced kernel with the following commands:
root
apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher

=== Holding a specific kernel version ===
If your manually installed kernel should be not upgraded to the one in extras* try [http://talk.maemo.org/showpost.php?p=603915&postcount=2063 this]:

<pre>
echo kernel-power-flasher hold | dpkg --set-selections
echo kernel-power hold | dpkg --set-selections
echo kernel-power-modules hold | dpkg --set-selections
</pre>
to unlock the version:

<pre>
echo kernel-power-flasher install | dpkg --set-selections
echo kernel-power install | dpkg --set-selections
echo kernel-power-modules install | dpkg --set-selections
</pre>

=== Issues after multiboot or Nitdroid installation ===

Multiboot changes the boot process and might not load kernel-power properly. This is not a kernel-power problem. Please read the multiboot threads or Nitdroid forums. For versions >=v39 typically,
<pre>apt-get install kernel-power-bootimg
apt-get install --reinstall multiboot-kernel-power</pre>
adds kernel-power to your boot menu.

== Features ==

=== Configuring the kernel speed/voltage settings ===

The instructions on the [[Overclocking]] page require the <code>kernel-power-flasher >=v27</code> and <code>kernel-power-settings >=0.8</code>.

If you upgraded from the old stable version the old settings should still work and be loaded during boot.

'''NOTE''': The kernel settings are not loaded after a crash. In that case the file <code>/etc/kernel-power/.notloaded</code> is created
and a notification will be shown after booting. The settings will be loaded at the next boot again unless it crashes again.

=== Battery ===
'''bq27200.ko module conflicts with bme battery charging! A "fix" temporarily added to I2C driver broke system completely and thus got reverted'''
In kernels version >=maemo20 you can read out the current battery info:

<pre>
modprobe bq27x00_battery
cat /sys/class/power_supply/bq27200-0/capacity
cat /sys/class/power_supply/bq27200-0/voltage_now
cat /sys/class/power_supply/bq27200-0/current_now
cat /sys/class/power_supply/bq27200-0/temp
cat /sys/class/power_supply/bq27200-0/charge_full
cat /sys/class/power_supply/bq27200-0/charge_full_design
cat /sys/class/power_supply/bq27200-0/charge_now
cat /sys/class/power_supply/bq27200-0/time_to_empty_avg
cat /sys/class/power_supply/bq27200-0/time_to_empty_now
cat /sys/class/power_supply/bq27200-0/time_to_full_now
</pre>

*'capacity' value in percentage of battery level.
*'voltage_now' value in mV of battery voltage level.
*'current_now' value in microA of battery current consumption.
*'temp' value in degrees C of battery temperature. (>= v47: in tenths of degree Celsius)

In kernel version >= v47 is additional info:
*'charge_full' value in µAh - last remembered value of charge when battery became full
*'charge_full_design' value in µAh - design charge value, when battery considered full
*'charge_now' value in µAh - actual charge value
*'time_to_empty_avg' averaged value - seconds left for battery to be considered empty (i.e. while battery powers a load)
*'time_to_empty_now' seconds left for battery to be considered empty (i.e. while battery powers a load)
*'time_to_full_now' seconds left for battery to be considered full (i.e. while battery is charging)

To remove this kernel module use:

rmmod bq27x00_battery

or reboot.

With kernel-power-settings >=0.6 the module can be loaded on boot. Just execute this once:
<pre>root
echo bq27x00_battery >> /etc/modules</pre>

With kernel version >= v47 the bq module is automatically loaded on boot. To disable, blacklist bq27x00_battery module:
<pre>root
echo bq27x00_battery >> /etc/modprobe.d/blacklist</pre>

===Mobile Hotspot===

all necessary modules are included. read [http://mobilehotspot.garage.maemo.org/ this] for more details.

===JoikuSpot===
seems to work. read [http://talk.maemo.org/showpost.php?p=653966&postcount=3592 this post].

Update: it doesn't work for me (recent version of Joikuspot and Maemo), ICMP and DNS resolving work OK, but TCP connections are completely freezed...If it works for you, let us know.

===CIFS Support===
You can now mount a network drive using Microsoft's CIFS protocol. To do so you need to do the following:

# Share a folder on your Windows PC, with the latest versions of Windows you will have to create a user account with a password to share a specific folder that is not the Public Library.

# Create a folder for the mount, pressumably on your /home/users/MyDocs folder, so that you could access your network drive through the file manager.

# Mount the folder on your device by typing the following into xterm under root:
<pre>mount -t cifs //netbiosname/sharename /media/sharename -o user=winusername,pass=winpassword,ip=destip,direct</pre>

===kexec===

All necessary kexec patches are included. read [http://wiki.meego.com/ARM/N900/Install/kexec] and [http://lists.meego.com/pipermail/meego-dev/2010-May/002277.html this post]
for MeeGo support.

===Boot Options===

There is a separate file /etc/default/kernel-boot for extra boot options.
It requires kernel-power-settings >= 0.11 and is disabled by default.
These two options are experimental and may brick your device!
Just install the template with the following commands and edit it (by default the options are disabled)
root
cp /usr/share/kernel-power-settings/boot /etc/default/kernel-boot

The default template looks like this
<pre># start USB networking and sshd early during boot
EARLY_SSH=0
# fsck of /home partition before mounting?
# 1=if necessary, force=always check
FSCK_HOME=0</pre>

====Filesystem Checking and Repair, and pre-mount Scripts====

See above for enabling this feature.
The following operations are performed before mounting /home:

# If you have a script (e.g. for repartitiong) called /etc/kernel-power/pre-mount.once it will be executed once and then moved away.
# if FSCK_HOME is enabled the /home partition (first ext3 on eMMC) will be fscked on boot.
Alternatively,
<pre>root
echo 1 > /etc/kernel-power/force_fsck</pre>
should check it only during next boot.
<pre>root
echo 0 > /etc/kernel-power/force_fsck</pre>
disables it only for the next boot.
If you reset or reboot the device during fsck, it will not fsck (only) during the next boot. All messages are logged to <code>/etc/kernel-power/pre-mount.log</code>

===IPv6===

IPv6 support is enabled and many users are successfully using it.
Note however, not all applications are IPv6 compatible.

So far, it has been successfully used with Chromium and Firefox out of the box. To run with the MicroB browser, you need to change one of the settings.

The setting is 'network.dns.disableIPv6' in about:config. When set to false, IPv6 just works when the phone has IPv6 connectivity.

IPv6 has also been used successfully with ssh and sshd.

Please share additional experiences here.

===PPTP===
[http://talk.maemo.org/showthread.php?t=36172 tutorial]

===Kismet===
[http://david.gnedt.eu/blog/2010/05/11/kismet-fully-functional-monitor-mode-for-the-n900/ tutorial] and
[http://talk.maemo.org/showthread.php?t=52393 TMO thread]

===Other Filesystems===
The kernel includes support for many alternative filesystems, including ext4 bugfixes and large file support.
You might want to repartition your eMMC or SD card with [[Repartitioning_the_flash]].

==Notes==

# even if 125 Mhz is disabled, the telephone app will always try to set the minimum freq. to 125 Mhz after a phone call, but it is ignored unless you enable 125 Mhz.
# if you enable 125 MHz also set "<code>echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load</code>" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]
# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125 MHz issue]
# Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
# The kernel supports 125 MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default] in avoid_frequencies. In version <25, it is enabled by specifying "124999", in later versions it is disabled in ''<code>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</code>'' and can be enabled with: <pre>echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</pre>similarily, individual frequencies can be disabled in >=v25:<pre>echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</pre>

[[Category:Power users]]
[[Category:N900]]

Community SSU

2016-07-02T21:41:25Z

122.57.34.193: /* Installation */

<div style="float: right">
<imagemap>
Image:Bugsquad-logo-wazd-small.png|84px|center|thumb|Report bug
desc none
default [https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU]
</imagemap>
</div>
<div style="float:right">
<imagemap>
Image:Cssu_testing_5.png|center|thumb|Testing_one-click-install
desc none
default [http://repository.maemo.org/community-testing/community-testing-fremantle.install Install testing]
</imagemap>
</div><div style="float:right">
<imagemap>
Image:Cssu_stable_5.png|center|thumb|Stable_one-click-install
desc none
default [http://repository.maemo.org/community/community-fremantle.install Install stable]
</imagemap>
</div><div style="float: right">
[[Image:Cssu_both_5.png‎]]
</div>

==What is it?==
Seamless Software Update ([[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 (or could) 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).
<br clear="all">

So this CSSU is the recommended '''update method''' for '''Maemo 5 Fremantle'''. It's not a new version of maemo distribution.

==Whom is it for?==

===Everyone===
Since the release of the stable branch CSSU-S is meant to be the LongTermSupport hotspot for all N900 users/owners.

Maximum compatibility for all N900 owners is CSSU primary guidance.

===Testers===
Power-users, developers, Nokia/Maemo/MeeGo engineers, testers, documentation writers and those willing to risk a re-flash in order to help can still install the testing version and stay as bleeding edge as possible inside CSSU universe, not implying CSSU will be the bleeding edge and pacemaker of development away from maemo5 towards something above and beyond (that's not what CSSU is meant to be and never will be, see above note about maximum compatibility).

===Thumbers===
Tired of the [[N900]]'s memory bottleneck, look no further.
CSSU-Thumb is reducing code size by compiling packages with Thumb2 ISA.

CSSU-Thumb is based on CSSU-Testing flavor, but uses a very low level patch to '''kernel''' to overcome the bugs in OMAP chip related to thumb/ARM mixed code. Thus the binaries from CSSU-Thumb will '''not work''' in a "normal system", and several things like uBoot or flashing --flash-only=kernel stop working the way they used to, and you need to take special care regarding the changed behaviour of those. If you don't, our system might start segfaulting like mad and probably not even boot up anymore. Thus to go back from thumb-enabled kernel to stock- or any other non-thumb-kernel is not an option for CSSU-Thumb users. Generally this solution is deprecated for you if you don't feel familiar with kernel installation stuff.

{{main|Community SSU/Thumb}}
[http://talk.maemo.org/showthread.php?t=84829 CSSU-Thumb talk.maemo.org Thread]

==Installation==

"Newbie" Video Tutorial: http://www.youtube.com/watch?v=uMHxo1ALXNE

Another nice one (I (jr/docS) prefer it better): http://www.youtube.com/watch?feature=fvwp&NR=1&v=DPVHOpGVzZY

Nevertheless read this full page as well, before starting CSSU installation, so you understand what it's all about.

Note that both videos show installation (and features) of CSSU-T - for (on first glance missing) features of CSSU-S see http://wiki.maemo.org/Community_SSU#Features

'''THIS IS THE ONE AND ONLY SUPPORTED AND TESTED WAY TO INSTALL CSSU''', please follow instructions faithfully!

'''There's no way to "uninstall" CSSU!''' Although you hardly ever want to do that. So:

# '''[NEW]:''' ''Since original Nokia system repositories vanished together with Nokia, please see http://wiki.maemo.org/Repository#Mirrors_of_standard_Nokia_repos_.28using_Application_manager.29 to get working source of core system components. You'll need that to satisfy dependencies of packages you're going to install during the process.''
# Install [http://maemo.org/packages/view/backupmenu/ backupmenu] . Do a full backup of your system. Get your battery charged up to state "green". All this is not mandatory but highly recommended, as usual. Plug in wallcharger. Get a softdrink of your choice :-)
# If you haven't done yet (unlikely): Upgrade to at least [[Maemo 5/PR1.3|PR1.3]], Nokia's last official major Maemo 5 update. PR1.3.1 is fine as well. If you're unsure if you have, ''Settings > About product'' should show ''Version'' beginning with '''20.2010.36'''(PR1.3) or '''21.2011.38'''(PR1.3.1). Make sure you have no too weird catalog settings in Application manager, esp it's recommended you never disable the core Nokia SSU repositories.
# In case you have modified hildon-desktop installed (you will know when you did that) remove it before taking further steps, all your settings will work since cssu does include all m-h-d changes. Rebooting the N900 prior to next step is probably a good idea, to make sure no memory hogs or anything is running. Make sure your device has a working connection to internet prior to next step, preferably via WLAN or a high bandwidth 3G data connection.
# Open this page in N900 webbrowser. Think a minute if you want to be a tester supporting CSSU bleeding edge, or you rather need a rock solid CSSU, then click on the according Install [http://repository.maemo.org/community/community-fremantle.install stable] or [http://repository.maemo.org/community-testing/community-testing-fremantle.install testing] icon at top of this page, or directly on the links in this very sentence.
# Hildon Application Manager (HAM) will launch and begin processing (be patient as nothing seems to happen for some minutes). There are a series of installations for which it will prompt you with messages and warnings. Click "Accept" and "Done" for each to install.
# 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.
# HAM will re-open and present you '''the real thing''': a system upgrade called '''Maemo 5 Community SSU''' - probably you want to install it ;-D. This will take a while. Once installed, your device will reboot "into" CSSU.
# If you installed the stable version and have edited your ''transitions.ini'' before installing, then you'll find your old settings in the file ''/usr/share/hildon-desktop/transitions.ini.precssu''. You can either just copy it over the new one and miss out on the new features, or incorporate your changes.

Problems? Check the [[Community_SSU/Installation_FAQ|Installation FAQ]]

==Features==
{{main|Community SSU/Features}}
{{main|Community SSU/FeaturesStable}}

You find there how to use new features such as [http://thpmaemo.blogspot.com/2011/02/community-ssu-features-to-look-forward.html Thomas Perl's hildon-desktop improvements] and the status of applications in [[Portrait Mode]] with <code>forcerotation</code>.

==Changelog==
{{main|Community SSU/Changelog}}
{{main|Community SSU/ChangelogStable}}

lists all changes from stock PR1.3 to CSSU and between various CSSU releases.

==Contributing==
{| style="background: #e8d8c8; border: 1px solid #666; width: 100%; text-align: center"
| Get involved on [[IRC]] (<code>#maemo-ssu</code>), [http://talk.maemo.org/showthread.php?t=67905 Talk], [https://bugs.maemo.org/buglist.cgi?resolution=FIXED&resolution=WONTFIX&resolution=---&classification=Extras&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&product=Maemo%205%20Community%20SSU Bugzilla] and [https://github.com/community-ssu Github].
|}

'''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 [[Community_SSU/QA#Test scripts|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 bugs.maemo.org as well as communication of the testing, releases and end-user readiness of the CSSU.

'''Have great ideas?''' If you have suggestions that you think could be picked up by the CSSU developers, please add them here: [[CSSU Requests]]. However see the notice above about CSSU not going to include anything that better gets implemented as a normal app. Nonetheless CSSU actually will host apps that are specific to CSSU core system, the orientation-lock applet being first of a possibly ever increasing number.

For more information: contact MohammadAG on #maemo-ssu on FreeNode IRC or [mailto:council@maemo.org council@maemo.org].

== QA and bugs ==
{{main|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". Packages in cssu-testing are supposed to be crafted and tested to be in a shape where the contributor and cssu maintainers expect them to pass those tests for "stable".

If you have found a bug, in either the ''testing'' or ''stable'' releases, please [https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU 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!

== Development ==

{{main|Community SSU/Development}}

The Community SSU is developed and managed through [https://github.com/community-ssu Github]. Bugs are tracked in [https://bugs.maemo.org/buglist.cgi?resolution=FIXED&resolution=WONTFIX&resolution=---&classification=Extras&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&product=Maemo%205%20Community%20SSU Bugzilla]. Collaboration largely [http://mg.pov.lt/maemo-ssu-irclog/ happens on IRC]. Getting involved through development, bug triaging and managing developers is a good way to get involved.

[[Category:Community]]
[[Category:Fremantle]]