[ROM][C5303][LP][5.1.1_r8][SM-4.9.x] AOSPAL 5.1 Unofficial SaberMod [20151008] - Xperia SP Android Development

{
"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"
}
XPERIA SP/HUASHAN/C5303 PARANOID ANDROID 5.1 UNOFFICIAL SABERMOD BUILDS
LOLLIPOP 5.1.1_r8
BUILD 5.1 20151008 IS ONLINE.
DOWNLOAD
NOT WORKING YET: (?) YOU TELL ME.
ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150926)
KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150926)
SOURCES:
kernel - https://github.com/infected-lp/android_kernel_sony_msm8x60/tree/saber
rom - https://github.com/infected-lp/android_device_sony_huashan/tree/pa_saber
[+] -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.
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM SECOND POST
- NO MODS OF ANY SORT
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl9, msi gtx 970, 1x samsung 850 evo 256gb + 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 AOSPA Legacy open-source code:
https://github.com/AOSPA-L
SPECIAL THANKS
AOSPA Dev Team = for the source code.​
​
XDA:DevDB Information
XSP/C5303/Huashan/ Paranoid Android 5.1 Unofficial Sabermod Builds, ROM for the Sony Xperia SP
Contributors
infected_
Source Code: https://github.com/AOSPA-L
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest TWRP recovery
Based On: Paranoid Android
Version Information
Status: Nightly
Created 2015-10-07
Last Updated 2015-10-07

---

Reserved
HOW-TO:
* wipe/format /system /data /cache /dalvik.
* flash latest available build, and flash gapps.
* reboot and you're done.
ps: theres no need to flash SuperSU, ive integrated it on the builds.
GAPPS:
OpenGapps - http://opengapps.org/
Modular Gapps - http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

---

Reserved
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of Paranoid Android 5.1 for the Xperia SP
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.
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/
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

---

Another reskined cm12.1
They even have the same exact bugs like lockscreen shows when locking the screen

---

DahakePL said:
Another reskined cm12.1
They even have the same exact bugs like lockscreen shows when locking the screen
Click to expand...
Click to collapse
the device sources are the same, and the github link is in OP... do you see any official SlimRom or AOSPA huashan official github repos anywhere?
and is also OP the purpose of these builds. and.. no one is forcing you to use them.
regards.

---

If you don't mind me asking, who's sources are you using to build this, Slim and the unofficial CM?

---

TheAvengingTITAN said:
If you don't mind me asking, who's sources are you using to build this, Slim and the unofficial CM?
Click to expand...
Click to collapse
Link is in OP.
regards.

---

Slimrom without sabermod (made by different user) feels different and it doesn't have lockscreen bug for example
So what's the matter?

---

DahakePL said:
Slimrom without sabermod (made by different user) feels different and it doesn't have lockscreen bug for example
So what's the matter?
Click to expand...
Click to collapse
what lockscreen bug? seems ok to me.

---

infected_ said:
what lockscreen bug? seems ok to me.
Click to expand...
Click to collapse
You can see the lockscreen for a second if you want to turn off the screen (old cm bug)

---

DahakePL said:
You can see the lockscreen for a second if you want to turn off the screen (old cm bug)
Click to expand...
Click to collapse
hm.. thats such a major bug, that i didnt even noticed until you said now.
regards.
ps: if you had the bug i have on leo with CM trees, while taking pictures, that you could really complain about.

---

@infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards.

---

flash- said:
@infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards.
Click to expand...
Click to collapse
That's what I'm talking about

---

flash- said:
@[HIDE]infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards[/HIDE].
Click to expand...
Click to collapse
i asked permission at @darioj98 if i could use his kernel tree to make my sabermod builds. if i get a positive reply, ill continue with these builds.
regards.

---

infected_ said:
i asked permission at @darioj98 if i could use his kernel tree to make my sabermod builds. if i get a positive reply, ill continue with these builds.
regards.
Click to expand...
Click to collapse
That would be awesome because I love PA

---

allright, i got a reply from @darioj98
i have permission from @Adrian DC to use is m8x60 kernel, so expect updates and bug fixes soon on the saber builds.

---

i'll just wait for nxt build
Sent from my Xperia SP using XDA Free mobile app

---

alright.
new build is up, 20151008
new device and kernel trees used.
regards.

---

Hello, I want to know about performance. This Rom is suitable for daily use?

---

aumAP said:
Hello, I want to know about performance. This Rom is suitable for daily use?
Click to expand...
Click to collapse
its suitable for daily use.
performance is good, smoothness if awesome, and battery great. try it and report please
regards.