Amungmiak

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMods build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).

Downloads

Latest build: ROM Download
Google Apps: GApps Download

Installation

- First time flashing CM11 to your Galaxy S (or coming from another ROM)?

    Root your device and install ClockworkMod Recovery.
    Reboot into Recovery using 3-button-combo
    Do a Nandroid backup!
    WIPE (wipe data/factory reset + wipe cache partition)
    Install the ROM from internal sdcard using ClockworkMod Recovery
    Optionally install the Google Addon

- Upgrading from CM7/CM9?

    Do a Nandroid Backup!
    WIPE (wipe data/factory reset + wipe cache partition)
    Install the ROM from internal sdcard using ClockworkMod Recovery
    Optionally install the Google Addon

- Upgrading from CM10/10.1?

    Do a Nandroid Backup!
    Install the ROM from internal sdcard using ClockworkMod Recovery
    You will finally see a "set_metadata_recursive" status 7 error. That is normal.
    Reboot back into recovery (the reboot is required)
    Install the ROM again from internal sdcard using ClockworkMod Recovery
    Optionally restore /data from Nandroid Backup (the update will wipe your /data)
    Optionally install the Google Addon

- Upgrading from CM10.2?

    Do a Nandroid Backup!
    Install the ROM from internal sdcard using ClockworkMod Recovery
    Optionally install the Google Addon

- Upgrading from another build of CM11?

    Do a Nandroid Backup!
    Install the ROM from internal sdcard using ClockworkMod Recovery

Warning: You may get set_metadata_recursive related-errors during install if youre using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.

Known Issues
Please do not report bugs if it is already listen in the list of known issues

    Display issues in Browser & other embedded webviews (Google Chrome works fine)
    No access to TV-Out menu
    Layout issues in lockscreen
    Menu soft-buttons appearing where they shouldnt
    Some CyanogenMod features a missing - please do not file bug reports for those.
    Privacy guard icon not disappearing when exited app
    Broken layout of quick message popup (SMS)
    Cannot set value via custom brightness "Edit" menu
    Vibrate on answer call doesnt work properly
    If back button is pressed during incoming call, you cant answer the call.
    FC when entering file manager settings
    FC when changing image sharpness
    Flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)


Reporting Bugs

You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.

REPORT BUGS IN THIS THREAD ONLY

    Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what youre doing.)
    If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didnt exist, it would greatly help in tracking down what caused it.