[ROM][SIRIUS][LP][5.1.1_r6][SM-4.9.x/4.9.x] CyanogenMod 12.1 SaberMod Builds

Status
Not open for further replies.
Search This thread

deepongi

Recognized Developer
Jul 12, 2008
6,097
15,095
41
Portugal
OnePlus 9
Samsung Galaxy Watch 5

CXjdJVo.png


Z2/SIRIUS/D6503 CYANOGENMOD 12.1 SABERMOD BUILDS

LOLLIPOP 5.1.1_r6

DOWNLOAD #1
(main mirror)
DOWNLOAD #2
(backup mirror)

ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150726)
KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150726)

SOURCE: https://github.com/infected-lp/android_kernel_sony_msm8974/tree/saber

[+] -O3 optimized (arm and thumb)
[+] strict-aliasing
[+] frame-pointers
[+] graphite flags
[+] LinkTimeOptimizations (-flto) flags
[+] cpu arch specific flags (armv7-l)
[+] other flags to optimize even more the code.

BUGS REPORT

REPORT BUGS ONLY:

- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM THIRD POST
- NO MODS OF ANY SORT

CHANGELOG:

http://www.cmxlog.com/12.1/sirius/

BUILDBOT:

(intel core i7 3770k, asus p8z77-v, 24gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 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, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)

DISCLAIMER:

These builds are freshly compiled/synced from CyanogenMod Rom open-source code:

https://github.com/CyanogenMod

SPECIAL THANKS

CyanogenMod Dev Team = for the source code.

Zb6j03d.png
CxAw1Uv.png
IKK3tXM.png
xEr9tem.png
LV3r9kI.png
A1bRdbJ.png


XDA:DevDB Information
Z2/Sirius/D6503 Linaro/Sabermod CyanogenMod 12.1 Builds, ROM for the Sony Xperia Z2

Contributors
infected_
Source Code: https://github.com/CyanogenMod

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest TWRP recovery
Based On: CyanogenMod

Version Information
Status: Testing

Created 2015-03-31
Last Updated 2015-08-03
 
Last edited:

deepongi

Recognized Developer
Jul 12, 2008
6,097
15,095
41
Portugal
OnePlus 9
Samsung Galaxy Watch 5

Attachments

  • Screenshot_2015-03-31-06-50-00.png
    Screenshot_2015-03-31-06-50-00.png
    127.2 KB · Views: 16,099
  • Screenshot_2015-03-31-06-59-39.png
    Screenshot_2015-03-31-06-59-39.png
    153.9 KB · Views: 15,798
  • Screenshot_2015-03-31-07-00-26.png
    Screenshot_2015-03-31-07-00-26.png
    102.4 KB · Views: 15,547
  • Screenshot_2015-04-06-09-26-51.png
    Screenshot_2015-04-06-09-26-51.png
    82.6 KB · Views: 14,221
  • Screenshot_2015-04-06-09-27-04.png
    Screenshot_2015-04-06-09-27-04.png
    178.2 KB · Views: 14,508
  • Screenshot_2015-04-06-09-27-42.png
    Screenshot_2015-04-06-09-27-42.png
    133.2 KB · Views: 14,467
  • Screenshot_2015-04-06-09-27-59.png
    Screenshot_2015-04-06-09-27-59.png
    135.3 KB · Views: 13,772
  • Screenshot_2015-04-06-09-28-04.png
    Screenshot_2015-04-06-09-28-04.png
    161.6 KB · Views: 12,778
  • Screenshot_2015-04-06-09-29-14.png
    Screenshot_2015-04-06-09-29-14.png
    90.6 KB · Views: 12,110
  • Screenshot_2015-04-06-09-28-21.png
    Screenshot_2015-04-06-09-28-21.png
    126.4 KB · Views: 11,946
Last edited:

deepongi

Recognized Developer
Jul 12, 2008
6,097
15,095
41
Portugal
OnePlus 9
Samsung Galaxy Watch 5
F.A.Q (Frequently Asked Questions)

What is the difference between these builds and the official builds?

These are unofficial builds of CyanogenMod 12.1 for the Xperia Z2/sirius.

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.4 (kernel code) & sabermod arm-linux-androideabi 4.9.4 (rom code) toolchain compilers
  • May contain some custom cherry-picks. Always see changelog for details.
  • Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM

What is Toolchain?

To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).

The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
Source: http://elinux.org

What is SaberMod?

The term "SaberMod" is coming from:

the SaberMod project. Initially the project was used on SaberMod ROM for the Nexus 7 WiFi model (2013). This continued onto the Nexus 4 and Nexus 5 through help of user donations. The toolchains are based on GNU GCC 4.8, 4.9, and 5.0 with AOSP patches forward ported into GNU GCC. SaberMod also provides extra optimization features unlike Google’s toolchain, which gives options for a few amendments in the ROM itself to add more performance gains, such as graphite loop transformation optimizations. SaberMod tracks other utilities from GNU in the toolchain source components that are generally more up to date than AOSP or Linaro toolchains, and almost always tracks the development branches of GNU GCC for the latest patches and bug fixes. The toolchain ecosystem of SaberMod is very different from AOSP, using complex scripts to provide quick, up to date toolchains. Other toolchain sources like the AOSP based toolchain build repository have been heavily modified to work in favor of the way SaberMod toolchains are produced. I have approached some toolchain developers to ask a few questions.
Source: http://www.xda-developers.com/interview-with-developers-of-sabermod-hyper-toolchains/


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. The Linaro organization was founded in mid 2010 and almost instantly its developers started to work on many projects, including GCC-based toolchains for ARM. Android builds compiled with Linaro started to pop up a few months later. Ever since the Linaro group was founded, users praised it for decent performance improvements and overall snappiness. Linaro uses its own solutions and is constantly updated. You can download the newest version of the toolchain directly from the web page.
Source: http://www.linaro.org/linux-on-arm/


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.

Screenshots of toolchains used and benchmarks.
 
Last edited:

VinBenzin810

Senior Member
Nov 4, 2013
474
95
Mannheim, Germany
What about the issues with loudspeaker is that fixed in and full functionalty in 5.1

And the low call in ringtone is That fixed too ?

Sent from my Xperia Z2 using XDA Free mobile app
 

sbreit

Senior Member
Nov 18, 2014
75
11
Wiped system, cache and dalvik cache, installed CM12.1 20150330 and 5.1.0 gapps from known thread but ended up in a boot loop. Did the same with 5.0.2 gapps. I'm seeing lots of GC and SELinux relabeling messages in the log file.

http://pastebin.com/UVwVKm2t

Do I have to wipe Data too or am I running into another issue here?
 

deepongi

Recognized Developer
Jul 12, 2008
6,097
15,095
41
Portugal
OnePlus 9
Samsung Galaxy Watch 5
Wiped system, cache and dalvik cache, installed CM12.1 20150330 and 5.1.0 gapps from known thread but ended up in a boot loop. Did the same with 5.0.2 gapps. I'm seeing lots of GC and SELinux relabeling messages in the log file.

http://pastebin.com/UVwVKm2t

Do I have to wipe Data too or am I running into another issue here?

yes, you need to wipe /data .. i needed to, or i would be stuck at boot animation.
 

twistedddx

Senior Member
Oct 23, 2010
963
577
I got stuck at boot screen until i wiped data also.

I flashed someones update to pa gapps for 5.1 and found aosp keyboard failed and had to install another ketboard via apk. I am blaming gapps package though for the issue.

keyboard issue aside everything so far seems as good as cm12 by infected.
If anything it maybe slightly more responsive.
 

RyTekk

Senior Member
Aug 17, 2012
1,144
573
Nha Trang
I got stuck at boot screen until i wiped data also.

I flashed someones update to pa gapps for 5.1 and found aosp keyboard failed and had to install another ketboard via apk. I am blaming gapps package though for the issue.

keyboard issue aside everything so far seems as good as cm12 by infected.
If anything it maybe slightly more responsive.

You need to flash addon gg keyboard to kick out the force close issue, or just you the pack 1503 instead of 2903 (another person made it)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 47

    CXjdJVo.png


    Z2/SIRIUS/D6503 CYANOGENMOD 12.1 SABERMOD BUILDS

    LOLLIPOP 5.1.1_r6

    DOWNLOAD #1
    (main mirror)
    DOWNLOAD #2
    (backup mirror)

    ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150726)
    KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150726)

    SOURCE: https://github.com/infected-lp/android_kernel_sony_msm8974/tree/saber

    [+] -O3 optimized (arm and thumb)
    [+] strict-aliasing
    [+] frame-pointers
    [+] graphite flags
    [+] LinkTimeOptimizations (-flto) flags
    [+] cpu arch specific flags (armv7-l)
    [+] other flags to optimize even more the code.

    BUGS REPORT

    REPORT BUGS ONLY:

    - AFTER A CLEAN INSTALL
    - USING STOCK KERNEL
    - USING GAPPS FROM THIRD POST
    - NO MODS OF ANY SORT

    CHANGELOG:

    http://www.cmxlog.com/12.1/sirius/

    BUILDBOT:

    (intel core i7 3770k, asus p8z77-v, 24gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 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, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)

    DISCLAIMER:

    These builds are freshly compiled/synced from CyanogenMod Rom open-source code:

    https://github.com/CyanogenMod

    SPECIAL THANKS

    CyanogenMod Dev Team = for the source code.

    Zb6j03d.png
    CxAw1Uv.png
    IKK3tXM.png
    xEr9tem.png
    LV3r9kI.png
    A1bRdbJ.png


    XDA:DevDB Information
    Z2/Sirius/D6503 Linaro/Sabermod CyanogenMod 12.1 Builds, ROM for the Sony Xperia Z2

    Contributors
    infected_
    Source Code: https://github.com/CyanogenMod

    ROM OS Version: 5.1.x Lollipop
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: Latest TWRP recovery
    Based On: CyanogenMod

    Version Information
    Status: Testing

    Created 2015-03-31
    Last Updated 2015-08-03
    19
    ive compiled and uploaded a new sirius build.

    have a nice weekend everybody!

    regards.
    18
    GAPPS

    http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

    All packages contains backup-script, so you dont have to flash gapps, everytime you flash a new build.

    Many Thanks to @Deltadroid for making these.
    13
    F.A.Q (Frequently Asked Questions)

    What is the difference between these builds and the official builds?

    These are unofficial builds of CyanogenMod 12.1 for the Xperia Z2/sirius.

    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.4 (kernel code) & sabermod arm-linux-androideabi 4.9.4 (rom code) toolchain compilers
    • May contain some custom cherry-picks. Always see changelog for details.
    • Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM

    What is Toolchain?

    To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).

    The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
    Source: http://elinux.org

    What is SaberMod?

    The term "SaberMod" is coming from:

    the SaberMod project. Initially the project was used on SaberMod ROM for the Nexus 7 WiFi model (2013). This continued onto the Nexus 4 and Nexus 5 through help of user donations. The toolchains are based on GNU GCC 4.8, 4.9, and 5.0 with AOSP patches forward ported into GNU GCC. SaberMod also provides extra optimization features unlike Google’s toolchain, which gives options for a few amendments in the ROM itself to add more performance gains, such as graphite loop transformation optimizations. SaberMod tracks other utilities from GNU in the toolchain source components that are generally more up to date than AOSP or Linaro toolchains, and almost always tracks the development branches of GNU GCC for the latest patches and bug fixes. The toolchain ecosystem of SaberMod is very different from AOSP, using complex scripts to provide quick, up to date toolchains. Other toolchain sources like the AOSP based toolchain build repository have been heavily modified to work in favor of the way SaberMod toolchains are produced. I have approached some toolchain developers to ask a few questions.
    Source: http://www.xda-developers.com/interview-with-developers-of-sabermod-hyper-toolchains/


    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. The Linaro organization was founded in mid 2010 and almost instantly its developers started to work on many projects, including GCC-based toolchains for ARM. Android builds compiled with Linaro started to pop up a few months later. Ever since the Linaro group was founded, users praised it for decent performance improvements and overall snappiness. Linaro uses its own solutions and is constantly updated. You can download the newest version of the toolchain directly from the web page.
    Source: http://www.linaro.org/linux-on-arm/


    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.

    Screenshots of toolchains used and benchmarks.
    11
    some may noticed today's build is a bit bigger in size. some new optimizations were introduced, so sirius is smoother, snappier and battery should last longer.

    current optimizations, combined with sabermod toolchain, on both ROM and kernel code:

    -O3 optimized (arm and thumb)
    strict-aliasing
    frame pointers
    graphite flags
    LinkTimeOptimizations (-flto) flags
    cpu arch specific flags (armv7-a-neon)
    other flags to optimize even more the code.

    regards.