[ROM][X][MM][6.0.1_r74][SM-4.9/5.3] OmniROM SaberMod [20170128] - Sony Xperia X ROMs, Kernels, Recoveries, & Other D

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
X/SUZU/F5121 OmniROM UNOFFICIAL SABERMOD BUILDS
MARSHMALLOW 6.0.1_r74
Current Build: 20170128
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 LINARO AARCH64-LINUX-GNU 5.3.1 (20160412)
KERNEL SOURCE: https://github.com/infectedmushi/android_kernel_sony_msm
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM SECOND POST
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 1070, 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 from OmniROM open-source code.
​

---

INSTRUCTIONS:
- download the latest build zip, and extract boot.img
- place the build, gapps and supersu somewhere on external/internal memory.
- flash the boot.img you extracted: fastboot flash boot boot.img
- enter recovery after powering the phone, by pressing volume up at the yellow led.
- wipe /system /cache and /data, flash latest build, gapps and supersu.
- reboot, and you are done.
MODULAR GAPPS:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
OPENGAPPS
http://opengapps.org/
SUPERSU:
TWRP / FlashFire installable ZIP:
Stable: http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu

---

F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of OmniROM 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 linaro aarch64-linux-gnu 5.3.1 (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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse

---

I finally found a reason to unlock my bootloader. Thanks, gotta test this ASAP.

---

I am waiting for your feed back

---

first feedback after 12 hours using omnirom on my X:
overall: runs very smooth and fast
found bugs:
- sd card not detected (yes,tried another card) by system and twrp
- touchscreen doesnt react sometimes while waking up,turn off and on again and it works
actually the same problems (for me) as on the aosp rom

---

mstrack said:
first feedback after 12 hours using omnirom on my X:
overall: runs very smooth and fast
found bugs:
- sd card not detected (yes,tried another card) by system and twrp
- touchscreen doesnt react sometimes while waking up,turn off and on again and it works
actually the same problems (for me) as on the aosp rom
Click to expand...
Click to collapse
what sdcard is it? an user have similar issue with sdcard not being detected, but its a 256GB card.

---

infected_ said:
what sdcard is it? an user have similar issue with sdcard not being detected, but its a 256GB card.
Click to expand...
Click to collapse
Its a 64gb card

---

First of all i installed the Rom its realy small with apps that are preinstalled
The only Bug i have is that my charging Animation dont close even After a restart its still there and showing a "charging" battery

---

mstrack said:
Its a 64gb card
Click to expand...
Click to collapse
it is fine here, ss in attachment. backup your stuff and wipe it.

---

infected_ said:
it is fine here, ss in attachment. backup your stuff and wipe it.
Click to expand...
Click to collapse
Ok, will try tomorrow.

---

infected_ said:
it is fine here, ss in attachment. backup your stuff and wipe it.
Click to expand...
Click to collapse
mstrack said:
Ok, will try tomorrow.
Click to expand...
Click to collapse
wiped, still no sd card.
also not in recovery (maybe its important).
---------- Post added at 06:15 PM ---------- Previous post was at 06:02 PM ----------
infected_ said:
it is fine here, ss in attachment. backup your stuff and wipe it.
Click to expand...
Click to collapse
ok, tried another card (which i also tried yesterday) and now it works...of course

---

another bug: no bluetooth telephone calls. cant hear the called,the called doesnt hear me.
tested with a bluetooth headset and car bluetooth.

---

Fingerprint Working but i need to press harder then in original Firmware
Second bug no speaker at phonecalls (normal calls sure are working but not loud

---

Cam isnt working sometimes, getting a force close

---

new build is up.
- android updated to 6.0.1_r74
- device/kernel updates from upstream (omni/aosp)
- twrp full functional
regards.

---

Cant get xposed to work with this rom, everytime after flashing fraamework rom ends up bootlooping.

---

xCorkyy said:
Cant get xposed to work with this rom, everytime after flashing fraamework rom ends up bootlooping.
Click to expand...
Click to collapse
quoting OP...
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM SECOND POST
- NO MODS OF ANY SORT
Click to expand...
Click to collapse
regards.

---

infected_ said:
quoting OP...
regards.
Click to expand...
Click to collapse
Thanks for answering! do you know if it is possible to have xposed with omnirom?

---

new build is up.
- device/kernel updates from upstream (omni/aosp)
- kernel compiled with linaro aarch64 gcc 5.3.1
regards.