FORUMS
Remove All Ads from XDA

[ROM][Z5][MM][6.0.1_r46][SM-4.9.x] CyanogenMod 13.0 SaberMod Builds [20160613]

5,813 posts
Thanks Meter: 14,120
 
Thread Closed Email Thread
Announcement from infected_: CyanogenMod like you never seen before!



Z5/SUMIRE/E6653 CYANOGENMOD 13.0 UNOFFICIAL SABERMOD BUILDS

CURRENT BUILD: 20160613

MARSHMALLOW 6.0.1_r46

DOWNLOAD

ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.x (20160520)

SOURCE: https://github.com/infected-mm/android_kernel_sony_msm - 3.10.x

CURRENT ISSUES: - camera not at 100%, but usable.

BUGS REPORT

REPORT BUGS ONLY:

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

CHANGELOG:

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

BUILDBOT:

(intel core i7 [email protected] (1.22v), asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11 (1.5v), msi nvidia gtx 970, 1x samsung 850 evo 250gb + 1x samsung ssd 840 pro 128gb, 4x western digital 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.
@davidteri91 = for the device trees.



XDA:DevDB Information
Z5/SUMIRE/E6653 CyanogenMod 13.0 Sabermod Builds, ROM for the Sony Xperia Z5

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

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest TWRP recovery and Unlocked Bootloader
Based On: CyanogenMod

Version Information
Status: Nightly

Created 2016-06-13
Last Updated 2016-06-13
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20160613-100458.png
Views:	1904
Size:	126.7 KB
ID:	3781348   Click image for larger version

Name:	Screenshot_20160613-100740.png
Views:	1866
Size:	112.0 KB
ID:	3781349   Click image for larger version

Name:	Screenshot_20160613-104009.png
Views:	1890
Size:	130.2 KB
ID:	3781350  
The Following 11 Users Say Thank You to infected_ For This Useful Post: [ View ]
 
 
13th June 2016, 10:20 AM |#2  
infected_'s Avatar
OP Recognized Developer
Flag Portugal
Thanks Meter: 14,120
 
Donate to Me
More
How-To
Coming from stock sony:
- download build, and extract boot.img
- fastboot flash boot boot.img
- download twrp from here, and as alternative cm recovery from here (note that cyanogenmod recovery doesnt support busybox)
- fastboot flash recovery twrp_recovery_20160607.img
- enter recovery, wipe and flash build, plus gapps.
- reboot and you are done!

Coming from an aosp based rom:
- enter recovery, wipe and flash build, and gapps
- you are done!
The Following 4 Users Say Thank You to infected_ For This Useful Post: [ View ]
13th June 2016, 10:20 AM |#3  
infected_'s Avatar
OP Recognized Developer
Flag Portugal
Thanks Meter: 14,120
 
Donate to Me
More
Reserved
F.A.Q (Frequently Asked Questions)

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

These are unofficial builds of CyanogenMod 13.0 for the Xperia Z5 (E6653)

ROM is built using the same source code (github) like the official one but with these following additions:
  • Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 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?

Quote:

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:

Quote:

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/interv...er-toolchains/

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.

Source: http://www.linaro.org/linux-on-arm/


Optimization Flags in GCC
Quote:

What are flags?
For compilers such as GCC, flags are essentially options. A flag can enable or disable an option or feature that is used when compiling (building) code.

What are optimizations?
Optimizations, in the context of compiler flags, are flags that improve some aspect of the code, whether it be size, speed, memory use, and debugging, among other possibilities.

General Optimizations
These optimizations are basic flags in GCC, typically implemented into projects to improve an aspect of the final compiled code.

-O1: Optimization level 1, very basic optimizations, rarely used.
-O2: Optimization level 2, basic optimizations, most commonly used.
-O3: Optimization level 3, basic + experimental optimizations. Large performance boost, but can produce bugs.
-Os: Optimize for size. Most of the optimizations from levels 1 and 2, with extras added to decrease the size of code.
-Ofast: All Optimizations from levels 1, 2, and 3, with extra fast math optimizations.
Typically produces the most bugs, with a large performance gain.
-Og: No performance boost, optimizes the debugging experience, making errors and
warnings more informative to help developers.
-g0: Disables all extra debugging, usually makes code faster.
-fomit-frame-pointer: Removes frame pointers when they aren’t needed, streamlining the code.
-fipa-sra: Removes unused parameters/variables and replaces parameters with the called value, streamlining the code.
-fkeep-inline-functions: Emits static inline functions, even after they’ve been called.
-fmodulo-sched: Reorders instructions in loops in the most optimal way.
-fmodulo-sched-allow-regmoves: a more aggressive -fmodulo-sched, optimizing loops further by allowing register moves
-fgcse-sm: Moves stores out of loops to decrease the workload of loops.
-fgcse-las: Removes redundant loads after a store to reduce the workload.
-fgcse-after-reload: Removes redundant loads after a reload.
-funsafe-loop-optimizations: Optimize more by making assumptions, can create bugs from loops overflowing.
-fira-hoist-pressure: Decreases size of the code by evaluating register pressure for hoist expressions.
-fira-loop-pressure: Makes code smaller and faster by evaluating the register pressure of loops.
-DNDEBUG: Passes the variable for no debugging.
-flto: Enables link time optimizations (LTO) for improved library and executable performance.

Graphite Optimizations
Graphite is a project within gcc that uses the integer set library (ISL) and the chunky loop generator (CLooG) to improve memory use and optimize loops.

-fgraphite: Performs basic graphite loop and memory optimizations.
-floop-interchange: Switches two nested loops.
-floop-strip-mine: Splits a complex loop into a set nested loops.
-floop-block: Splits a loop into nested loops so that the memory fits into caches.
-fgraphite-identity: Creates a visual polyhedral representation of certain graphite optimizations. with some optimizations from ISL such as dead code removal.
-floop-nest-optimize: Optimizes the order of nested loops for data-locality and parallelism. This flag is experimental
-floop-unroll-and-jam: Enable unroll and jam for the ISL loop optimizer.
-floop-parallelize-all: Use graphite data to find and parallelize loops that can be.

Multithreading optimizations
Make code run in multiple jobs (threads) to use a multicore cpu to its fullest potential.

-ftree-parallelize-loops=n: Run parallelized loops is n number of threads.
-pthread: Use the posix thread system for multi-threading.
-fopenmp: Use the OpenMP thread system for multithreading. Tends to use less ram than posix.

Sanitizer Flags
These flags use libsanitizer for memory optimizations.

-fsanitize=leak: Sanitize memory leaks to reduce memory use
-fsanitize=address: Sanitize memory addresses to reduce memory use
-fsanitize=thread: Sanitize excess threads to reduce memory/cpu use. Only for 64bit.

Hardware Optimizations
These optimizations optimize code for the targets cpu, gpu, or ram.

-marm: Uses the ARM instruction set for executable code, improving performance.
-mthumb: Uses the Thumb2 instruction set, improving compatibility.
-mthumb-interwork: Improves compatibility between Thumb and ARM code.
-march=X: Optimizes code for your CPU’s arch, such as armv6, armv7-a, etc
-mcpu=X: Optimizes code for your specific CPU such as cortex-a15, cortex-a53, etc.
-mtune=X: Refer to -mcpu
-mfpu=X: Optimizes code for your CPU’s FPU such as vfpv3. vfpv4, neon, etc.
-mabi=X: Optimizes code ABI for your CPU, such as 32 or 64

The Following 5 Users Say Thank You to infected_ For This Useful Post: [ View ]
13th June 2016, 11:52 AM |#4  
Abaddon's Avatar
Senior Member
House Avernus
Thanks Meter: 950
 
Donate to Me
More
woot. finally it's own thread. thank you
been using this since the first build as DD tho wish camera was as good as stock but it's sony's fault
anyway hoping we could see more builds and more new roms from you?
The Following User Says Thank You to Abaddon For This Useful Post: [ View ] Gift Abaddon Ad-Free
13th June 2016, 02:39 PM |#5  
zhangyang_haha's Avatar
Senior Member
Flag jiangsu wuxi
Thanks Meter: 418
 
More
Finally its here. Thanks for your incredible work!
The Following User Says Thank You to zhangyang_haha For This Useful Post: [ View ] Gift zhangyang_haha Ad-Free
13th June 2016, 08:11 PM |#6  
Junior Member
Thanks Meter: 2
 
More
Oh so thanks for thıs
Thank you

Sent from my E6603 using XDA-Developers mobile app
13th June 2016, 10:01 PM |#7  
Senior Member
Thanks Meter: 177
 
More
Thanks for your work! So everything is working except camera? Fingerprint reader for example?
14th June 2016, 05:25 AM |#8  
Abaddon's Avatar
Senior Member
House Avernus
Thanks Meter: 950
 
Donate to Me
More
Quote:
Originally Posted by diemadedrei

Thanks for your work! So everything is working except camera? Fingerprint reader for example?

yes. better than stock in my end 😁
camera works but not 100% sadly. go try it.

Sent from my Nexus 6p using Tapatalk
The Following 2 Users Say Thank You to Abaddon For This Useful Post: [ View ] Gift Abaddon Ad-Free
14th June 2016, 06:31 AM |#9  
Senior Member
Thanks Meter: 177
 
More
Thanks, I will later this week.
14th June 2016, 07:26 AM |#10  
Junior Member
Thanks Meter: 0
 
More
@infected_ I tried the 0613 ver but it's not charging. when plugged in. the batt icon indicates it's charging but it's not. checked via ampere and I get -500. plus the led indicator just blinks red saying the batt is low.
is it kernel related? how can I fix this? tried flashing 2x clean install
14th June 2016, 07:34 AM |#11  
infected_'s Avatar
OP Recognized Developer
Flag Portugal
Thanks Meter: 14,120
 
Donate to Me
More
Quote:
Originally Posted by LegionCommander

@infected_ I tried the 0613 ver but it's not charging. when plugged in. the batt icon indicates it's charging but it's not. checked via ampere and I get -500. plus the led indicator just blinks red saying the batt is low.
is it kernel related? how can I fix this? tried flashing 2x clean install

its charging.. i think LED has a small bug, yet to be fixed, during charging.

just leave it pluged for one hour or whatever time, and youll see that it charges.

regards.
The Following User Says Thank You to infected_ For This Useful Post: [ View ]
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes