![CyanogenMod 11 [NIGHTLY BUILDS]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyQM8B-MnbHmgAdZwms5frrLLDChKl6AO-KKGSCRdZl9vuf8ulVdxePRYK2fjQIJ-J-gxKGWZTK5b0q5OnBPza0gUDjv4cWtgK3PfyHUOq2Zh8drDS_y8zmkfI5kz1rvGaxVU4DFqB6A4/s400/5557-bd59ca7f_680_400.jpg "CyanogenMod 11 [NIGHTLY BUILDS]")
Nightly Build CM 11 20131219 is ONLINE
Build/Sync Date: Dec 19 2013 01h:09 GMT+00h:00 Lisbon
DOWNLOAD(MediaFire - Main Mirror)
DOWNLOAD(AFH - Backup Mirror)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.7.4 201311 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.3 201311 toolchain
- -O3 optimizations
- strict-aliasing rules
- custom performance flags
- +30 cherry-picks used
- sqlite fsync hack by dorimanx
CHANGELOG
mali: bulk import of r3p2-01rel3 drivers from i9300-update12 |
check the rest on:review.cyanogemod.org
These builds are hosted in my private account at MediaFire (purchased account - 120GB | no ads and really fast downloads!)
(buildbot: intel core i7 3770k@4.6Ghz, asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
2x western wigital wd3200aaks raid 0 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 16 "Petra" x64 3.11.10)
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:https://github.com/CyanogenMod
latest linaro arm-eabi-4.7.4 used to compile the kernel code & linaro arm-linxu-adnroideabi-4.8.2 toolchains to compile ROM code
Special Thanks
CyanogenMod Rom Dev Team
| OFFICIAL CM WIKI |
| OFFICIAL CM INSTRUCTIONS |
- Copy GApps and CM11 ZIPs to your internal/external sdcard SDCard
- Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG. If you're unsure, flash this ClockworkMod-Recoveryusing Odin/Heimdall.
- Make sure you're running a proper working ClockworkMod-Recovery
- Boot into Recovery
- Flash CM 11 zip from internal/external sdcard SDCard
- Flash GApps zip from internal/external sdcard SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
| DOWNLOADS |
MediaFire Download Folder
AndroidFileHosting Folder
Google Apps:
MediaFire Folder
Use this gapps: 11-7_GApps_Core_4.4_signed.zip
CWMR's (KitKat compatible)
Zip - http://www.mediafire.com/download/we...ible-i9100.zip
Tar - http://www.mediafire.com/download/uk...ible-i9100.tar
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 11 for the i9100.
ROM is built using the same source code (github) like the official one but with these following additions:
- Compiled using linaro arm-eabi 4.7.4 13.09 (kernel code) & linaro arm-linux-androideabi 4.8.2 (rom code) toolchain compilers
- Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
Quote:
| In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools. A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product. |
What is SaberMod?
The term "SaberMod" is coming from:
Quote:
| SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM. |
What is Linaro?
Quote:
| Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces. |
About GCC main compiler cflags-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
0 comments:
Post a Comment