Z2/SIRIUS/D6503 CYANOGENMOD 11 SABERMOD NIGHTLY BUILDS
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with sabermod arm-eabi-4.9.2 2014.08 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 2014.08 toolchain
FEATURES
- -O3 global compiler ARM/thumb flags
- strict-aliasing (highest level = 3)
- pre-selected flags for optimized performance
- memory optimizations
- graphite
- +30 cherry-picks (to be able to compile with all options mentioned, using custom toolchains)
TOOLCHAINS
SaberMod 4.8 (ROM code, self-compiled toolchain)
SaberMod 4.9 (Kernel code, self-compiled toolchain)
CHANGELOGS
http://www.cmxlog.com/11/sirius/
BUILDBOT
(intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, 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 17 x64 "Qiana" 3.13.0-24)
DISCLAIMER:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
always latest sabermod arm-eabi 4.9 used to compile the kernel code & sabermod arm-linux-androideabi 4.8 toolchains to compile ROM code
SPECIAL THANKS
CyanogenMod Dev Team = for the source code.
@sparksco = sabermod toolchain sources.
@thomas1991_12 = helping me fix some stuff.
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (bluE led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3s, during this period press vol+
- wipe
- flash rom zip
- flash gapps zip
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-dev...d.php?t=2397942
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod ROM for the Xperia Z2/Sirius/D6503.
ROM is built using the same source code (github) like the official one but with these following additions:
- Compiled using sabermod arm-eabi 4.9.2 (kernel code) & sabermod arm-linux-androideabi 4.8.4 (rom code) toolchain compilers
- May contain some custom cherry-picks. Always check OP.
- Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
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.
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
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.
Source: http://forum.xda-dev.....php?t=2158698
What is Linaro?
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.
Source: http://www.linaro.org/linux-on-arm/
What is graphite?
Graphite has been around for a while in GCC. During this time a lot of people tested Graphite and Sebastian fixed many bugs. As of today the Graphite infrastructure is pretty stable and hosts already specific optimizations such as loop-interchange, blocking and loop-flattening.
However, during the development of Graphite we also found areas where we are still way behind our possibilities. First of all we realized that the use of a rational polyhedral library, even though it provides some functionality for integer polyhedra, is blocking us. Rational rational polyhedra worked OK for some time, but we have now come to a point where the absence of real integer polyhedra is causing problems. We have bugs that cannot be solved, just because rational polyhedra do not represent correctly the set of integer points in the loop iterations. Another deficit in Graphite is the absence of a generic optimizer. Even though classical loop transformations work well for certain problems, one of the major selling points of polyhedral techniques is the possibility to go beyond classical loop transformations and to forget about the corresponding pass ordering issues. Instead it is possible to define a generic cost function for which to optimize. We currently do not take advantage of this possibility and therefore miss possible performance gains. And as a last point, Graphite still does not apply to as much code as it could. We cannot transform a lot of code, not only because of the missing support for casts (for which we need integer polyhedra), but also because of an ad hoc SCoP detection and because some passes in the GCC pass order complicate Graphite's job. Moving these road blocks out of the way should increase the amount of code we can optimize significantly.
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.
Info:
Decidi partilhar na comunidade Android Portuguesa, a CyanogenMod 11 ROM para o Z2/Sirius/D6503, extremamente optimizada por mim.
Todos os créditos e sources estão mencionados.
Benchmarks Screenshots: http://forum.xda-dev...543&postcount=4
link para a thread original na XDA: http://forum.xda-dev...d-11-0-t2866055
Editado por infected_, 09 September 2014 - 10:09.
