• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][X][6.0.1_r74][SM-4.9.x] AOSP SABERMOD [20161114]

Search This thread

infected_

Recognized Developer
Jul 12, 2008
5,856
14,129
OnePlus 8

Android_Open_Source_Project_710x277_transparent.png


X/SUZU/F5121 AOSP SABERMOD BUILDS

MARSHMALLOW 6.0.1_r74

Current Build: 20161114

DOWNLOAD

CURRENT ISSUES:

1. Adaptive brightness (sensor HAL)
2. Audio InCall volume change (audio HAL)
3. Incell Panel: on wakeup no touch, suspend|resume with
power button as workaround for panel type 8 (kernel)

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 (20160726)

BUILDS ALREADY HAVE GAPPS INCLUDED.

KERNEL SOURCE: https://github.com/SonyAosp/kernel/tree/mm-6.0

BUGS REPORT

REPORT BUGS ONLY:

- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- NO MODS OF ANY SORT

CHANGELOG:
(check the download folder for the build corresponding changelog)

BUILDBOT:

(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 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 with open-source code from SonyAosp repos.
Many thanks to @davidteri91 for letting me use his sources. all credits goes to him.

file_5f93f983524def3dca464469d2cf9f3e_black_whit.png
Zb6j03d.png
CxAw1Uv.png
image00.png
mint_debian_logo2_scaled.png
A1bRdbJ.png

 
Last edited:

infected_

Recognized Developer
Jul 12, 2008
5,856
14,129
OnePlus 8
Coming from stock sony:

- download build, and extract boot.img
- download twrp from here
- fastboot flash recovery recovery_suzu.img
- fastboot flash boot boot.img
- enter recovery, wipe and flash build.
- reboot and you are done!

Coming from an aosp based rom:
- enter recovery, wipe and flash build.
- you are done!

ROOT:

TWRP / FlashFire installable ZIP:
Stable: http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu

BUILDS ALREADY HAVE GAPPS. PLEASE DONT BREAK IT BY FLASHING THEM.
 

infected_

Recognized Developer
Jul 12, 2008
5,856
14,129
OnePlus 8
F.A.Q (Frequently Asked Questions)

These are AOSP builds for the Xperia X (F5121)

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?

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.

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


Optimization Flags in GCC
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
 

Nicolae-Daniel

Senior Member
Dec 22, 2011
768
150
Hei @infected_ , just flashed your build but on start it requires a password. Some help?

// seems like a factory reset solved the problem

Some bugs i found are related to google camera, and audio playback via play music. Flashed back stock rom.
 
Last edited:

El Brillantinas

Senior Member
Sep 3, 2011
479
105
110
Vanaheim
Trying to flash the last build for november, but it won't do it.

"updater process ended with signal: 7
Error installing zip file name-of-the-file.zip"

Also, TWRP is asking for a password. I'm trying to install the zip from the SD Card.
 

infected_

Recognized Developer
Jul 12, 2008
5,856
14,129
OnePlus 8
Trying to flash the last build for november, but it won't do it.

"updater process ended with signal: 7
Error installing zip file name-of-the-file.zip"

Also, TWRP is asking for a password. I'm trying to install the zip from the SD Card.
Temporary Workaround: download a X omnirom build. Extract boot I'm and flash it. Enter recovery, cancel when it ask for a password, flash aosp build and boot.

Sent from my F5121 using XDA-Developers mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    Android_Open_Source_Project_710x277_transparent.png


    X/SUZU/F5121 AOSP SABERMOD BUILDS

    MARSHMALLOW 6.0.1_r74

    Current Build: 20161114

    DOWNLOAD

    CURRENT ISSUES:

    1. Adaptive brightness (sensor HAL)
    2. Audio InCall volume change (audio HAL)
    3. Incell Panel: on wakeup no touch, suspend|resume with
    power button as workaround for panel type 8 (kernel)

    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 (20160726)

    BUILDS ALREADY HAVE GAPPS INCLUDED.

    KERNEL SOURCE: https://github.com/SonyAosp/kernel/tree/mm-6.0

    BUGS REPORT

    REPORT BUGS ONLY:

    - AFTER A CLEAN INSTALL
    - USING STOCK KERNEL
    - NO MODS OF ANY SORT

    CHANGELOG:
    (check the download folder for the build corresponding changelog)

    BUILDBOT:

    (intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 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 with open-source code from SonyAosp repos.
    Many thanks to @davidteri91 for letting me use his sources. all credits goes to him.

    file_5f93f983524def3dca464469d2cf9f3e_black_whit.png
    Zb6j03d.png
    CxAw1Uv.png
    image00.png
    mint_debian_logo2_scaled.png
    A1bRdbJ.png

    3
    Coming from stock sony:

    - download build, and extract boot.img
    - download twrp from here
    - fastboot flash recovery recovery_suzu.img
    - fastboot flash boot boot.img
    - enter recovery, wipe and flash build.
    - reboot and you are done!

    Coming from an aosp based rom:
    - enter recovery, wipe and flash build.
    - you are done!

    ROOT:

    TWRP / FlashFire installable ZIP:
    Stable: http://download.chainfire.eu/supersu-stable
    Beta: http://download.chainfire.eu/supersu-beta
    Latest: http://download.chainfire.eu/supersu

    BUILDS ALREADY HAVE GAPPS. PLEASE DONT BREAK IT BY FLASHING THEM.
    3
    F.A.Q (Frequently Asked Questions)

    These are AOSP builds for the Xperia X (F5121)

    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?

    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.

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


    Optimization Flags in GCC
    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
    3
    new build is up.

    regards.
    1
    Nice work! Good to see some dev love for our X!

    ps) this twrp is also working for stock roms or only for AOSP based roms?
    Only for AOSP based ROMs.

    Sent from my E6653 using XDA-Developers mobile app