Database Develop

[ROM][SIRIUS][KK][4.4.4][LINARO/SABERMOD] Paranoid Android 4.6 [BETA 5][DSB]

Z2/SIRIUS/D6503 PARANOID ANDROID 4.6 LINARO/SABERMOD BETA BUILDS
Current build:
BETA 5
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.8.4 2014.08 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 2014.10 toolchain
FEATURES
-O3 global compiler ARM/thumb flags
strict-aliasing (highest level = 3)
pre-selected flags for optimized performance
memory optimizations
graphite
+30 cherry-picks (to be able to compile with all options mentioned, using custom toolchains)
TOOLCHAINS
SaberMod 4.8 (ROM code, self-compiled toolchain)
Linaro 4.8 (Kernel code, custom optimized linaro toolchain)
CHANGELOGS
http://blog.paranoidandroid.co/2014/10/21/4-6-beta-5-release-playful-pitaya/
BUILDBOT
(intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
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, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 x64 "Qiana" 3.13.0-24)
DISCLAIMER:
These builds are freshly compiled/synced from AOSPA Legacy open-source code:
https://github.com/AOSPA-legacy
always latest linaro arm-eabi 4.8 used to compile the kernel code & sabermod arm-linux-androideabi 4.8 toolchains to compile ROM code
SPECIAL THANKS
CyanogenMod Dev Team = for the source code.
@sparksco = sabermod toolchain sources.
{
"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"
}
​
XDA:DevDB Information
Z2/Sirius/D6503 Linaro/Sabermod Paranoid Android 4.x Builds, ROM for the Sony Xperia Z2
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 4.6 BETA 5
Beta Release Date: 2014-10-25
Created 2014-09-11
Last Updated 2014-09-10

Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (bluE led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3s, during this period press vol+
- wipe
- flash rom zip
- flash gapps zip
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942

F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of AOSPA Legacy ROM for the Xperia Z2/Sirius/D6503.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.8.4 (kernel code) & sabermod arm-linux-androideabi 4.8.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always check OP.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
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/
What is graphite?
Graphite has been around for a while in GCC. During this time a lot of people tested Graphite and Sebastian fixed many bugs. As of today the Graphite infrastructure is pretty stable and hosts already specific optimizations such as loop-interchange, blocking and loop-flattening.
However, during the development of Graphite we also found areas where we are still way behind our possibilities. First of all we realized that the use of a rational polyhedral library, even though it provides some functionality for integer polyhedra, is blocking us. Rational rational polyhedra worked OK for some time, but we have now come to a point where the absence of real integer polyhedra is causing problems. We have bugs that cannot be solved, just because rational polyhedra do not represent correctly the set of integer points in the loop iterations. Another deficit in Graphite is the absence of a generic optimizer. Even though classical loop transformations work well for certain problems, one of the major selling points of polyhedral techniques is the possibility to go beyond classical loop transformations and to forget about the corresponding pass ordering issues. Instead it is possible to define a generic cost function for which to optimize. We currently do not take advantage of this possibility and therefore miss possible performance gains. And as a last point, Graphite still does not apply to as much code as it could. We cannot transform a lot of code, not only because of the missing support for casts (for which we need integer polyhedra), but also because of an ad hoc SCoP detection and because some passes in the GCC pass order complicate Graphite's job. Moving these road blocks out of the way should increase the amount of code we can optimize significantly.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse

Benchmarks screenshots

infected_ said:
Benchmarks soon.
Click to expand...
Click to collapse
Antutu Benchmark.

waleedshiekh said:
Antutu Benchmark.
Click to expand...
Click to collapse
try 4.6 beta 2 from today, and see if your score raises.
i got 43k with this latest build.

infected_ said:
try 4.6 beta 1 from today, and see if your score raises.
i got 43k with this latest build.
Click to expand...
Click to collapse
Benchmark for Beta2 V2...

infected_ said:
try 4.6 beta 1 from today, and see if your score raises.
i got 43k with this latest build.
Click to expand...
Click to collapse
waleedshiekh said:
Benchmark for Beta2 V2...
Click to expand...
Click to collapse
dont know what you are doing wrong, but i get 43k...

Hi @infected_ how ru man.. regards from Z1 people.. came here to ask is Camera Broken on Z2 CM build or is it broken on This ROM..? broken as in sense no camera At all? No AOSP camera too?

abbychauhan said:
Hi @infected_ how ru man.. regards from Z1 people.. came here to ask is Camera Broken on Z2 CM build or is it broken on This ROM..? broken as in sense no camera At all? No AOSP camera too?
Click to expand...
Click to collapse
Camera works fine on all aosp builds..

4K camera and everything else working on this? I'm looking for a smooth, highly customizable ROM with 4K camera

ca12bon said:
4K camera and everything else working on this? I'm looking for a smooth, highly customizable ROM with 4K camera
Click to expand...
Click to collapse
4K doesn't work! If you want it, stick to stock ROM
Sent from my Xperia Z2 using XDA Premium 4 mobile app

BETA 5 is up!
- Full working DynamicSystemBars (DSB)
PA Recents is still closed source. soon the code is released, ill compile a build with it.
DSB looks awesome.
You want to have a look info about it and settings: http://blog.paranoidandroid.co/2014/10/21/4-6-beta-5-release-playful-pitaya/
Enjoy your weekend!

Was waiting for an update on this which included DSB. Thank you for your hard work

Thank you infected, I'm unlocking my bootloader tonight, loved your work on xperia z , any one know how camera is on this rom

Camera is OK. Stick ROM has better camera options

NVM, got it from your CM link in signature. I miss PA so much!! I can't use it though because like all non stock roms for me, I get no data after turning off wifi and nobody seems to know anything about why. APN settings same as every other phone and stock on my Z2 yet LTE symbol but no data I'll be back for you someday PA!

infected_ said:
BETA 5 is up!
- Full working DynamicSystemBars (DSB)
PA Recents is still closed source. soon the code is released, ill compile a build with it.
DSB looks awesome.
You want to have a look info about it and settings: http://blog.paranoidandroid.co/2014/10/21/4-6-beta-5-release-playful-pitaya/
Enjoy your weekend!
Click to expand...
Click to collapse
Hi @infected_ , the download link was broken

Is anyone else having problems with the wifi in the latest build? It doesn't turn on, just says 'Turning on Wifi...' even after reboot...

zexl455 said:
Is anyone else having problems with the wifi in the latest build? It doesn't turn on, just says 'Turning on Wifi...' even after reboot...
Click to expand...
Click to collapse
same here , cant connect to wifi at all , have to go back to older build for now untill fix

[ROM][LP][5.1.1_r8][SM-4.9.x] Paranoid Android 5.1 SaberMod Builds [20150806]

{
"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"
}
Z2/SIRIUS/D6503 PARANOID ANDROID 5.1 SABERMOD BUILDS
LOLLIPOP 5.1.1_r8
BUILD 5.1 20150806 IS ONLINE.
DOWNLOAD #1
(main mirror)
DOWNLOAD #2
(backup mirror)
NOT WORKING YET: (?) YOU TELL ME.
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-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 THIRD POST
- NO MODS OF ANY SORT
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 24gb 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
Z2/Sirius/D6503 Linaro/Sabermod Paranoid Android 5.1 Lollipop Builds, ROM for the Sony Xperia Z2
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: AOSP
Version Information
Status: Testing
Created 2014-12-06
Last Updated 2015-08-06

Reserved
GAPPS
http://forum.xda-developers.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.
SUPERSU
http://download.chainfire.eu/supersu
Benchmark Screenshots and Toolchains used.

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 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.
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. 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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse

+1

++1

edit : Its very nice rom, working everything except the camera.
keep up the good work OP.. We love it.
(old post : tested and not impressed.. I think i'll continue with CM12 for now.)

azam426 said:
tested and not impressed.. I think i'll continue with CM12 for now.
Click to expand...
Click to collapse
Is that really why you are here? To write this?
Seing the unimpressive parts of any work is not a talent nor a necessity, leading or helping the way to the solution is.
Sent from my D6503 using XDA Free mobile app

Definitely not stock Paranoid Android. Why the notification pulldown patch and there's no way to turn it off??
The only thing I've added to my build was the kernel msm mach voice routing patch, but I guess I'm not a known developer and that's that...

cheep5k8 said:
Definitely not stock Paranoid Android. Why the notification pulldown patch and there's no way to turn it off??
The only thing I've added to my build was the kernel msm mach voice routing patch, but I guess I'm not a known developer and that's that...
Click to expand...
Click to collapse
The quick pulldown was merged into the main source yesterday, to be clear.
Turning it off will be soon, see their gerrit.

OK thanks for the heads-up.
Well, I'm not really here to compete, seeing as this is the first time I'm working from inside Android (I develop apps as my day job). Krabappel and me are still basically working on getting stock AOSP up.
Just a few heads-ups from myself for this build:
- Mobile data is somehow strange, it shows as HS*PA or LTE but is very slow, sometimes it seems there is no connection at all. Passover from WiFi to mobile seems strange too.
- I couldn't make my media playback app work (it uses libVLC as the backend), however Googe Play Music worked fine
- SDCard seemed not accessible, or at least not fully
I went back to my build for the time being but I guess you guys are more experienced with building this stuff; looking forward to the official AOSPAL Sirius builds!

cheep5k8 said:
Definitely not stock Paranoid Android. Why the notification pulldown patch and there's no way to turn it off??
The only thing I've added to my build was the kernel msm mach voice routing patch, but I guess I'm not a known developer and that's that...
Click to expand...
Click to collapse
"Definitely not stock Paranoid Android" ?
please elaborate..
AOSPA starts always fresh upon a new Android release.. you had kk for ex, and now you have lllpp. basically this alpha build is "pure AOSP", with kernel optimizations...
features will come in time.
regards.
edit: @TheMrcool212, please correct me if i am saying non-sense.

infected_ said:
"Definitely not stock Paranoid Android" ?
please elaborate..
AOSPA starts always fresh upon a new Android release.. you had kk for ex, and now you have lllpp. basically this alpha build is "pure AOSP", with kernel optimizations...
features will come in time.
regards.
edit: @TheMrcool212, please correct me if i am saying non-sense.
Click to expand...
Click to collapse
Chill, both of you are doing good. He just not notified what's going on with the current features, that gives a difference between your build and him for the time being.

_delice_doluca_ said:
Is that really why you are here? To write this?
Seing the unimpressive parts of any work is not a talent nor a necessity, leading or helping the way to the solution is.
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Oh my god.. fighters everywhere..
we dont have freedom to tell what we feel about something?
what kind of world is this?
****ty people.

azam426 said:
Oh my god.. fighters everywhere..
we dont have freedom to tell what we feel about something?
what kind of world is this?
****ty people.
Click to expand...
Click to collapse
Another one here, i'm about to feel the mods will remove our posts now.
Btw, just want to say your previous post sounds a bit negative. Yes, you do have rights to say what you feel about something, but at least say that you appreciate the dev's work, give them support, and most importantly not making them disappointed/unhappy.
Hope this explains.

Just adding an actual ROM related post.
Is this thing still in development? how is it looking so far?
I'm currently running CM12 infected edition and it runs smooth as ****.
Correct me if I'm wrong, this AOSPA 5.0 is based on CM12 so it will have the same bugs and possibly the same look/feel (at least for now).

Do we use the gapps from cm12 Roms for this?
Sent from my Xperia Z2 using XDA Free mobile app

GeekyAndroid said:
Just adding an actual ROM related post.
Is this thing still in development? how is it looking so far?
I'm currently running CM12 infected edition and it runs smooth as ****.
Correct me if I'm wrong, this AOSPA 5.0 is based on CM12 so it will have the same bugs and possibly the same look/feel (at least for now).
Click to expand...
Click to collapse
Development just started.. and Paranoid Android (AOSPA) is AOSP based, not CM.
benjmiester said:
Do we use the gapps from cm12 Roms for this?
Sent from my Xperia Z2 using XDA Free mobile app
Click to expand...
Click to collapse
use the cm12 gapps on basketbuild: https://s.basketbuild.com/gapps
they work fine.
regards.

Thanks, you're the best! One other thing though, is it OK to migrate from your cm ROM with a wipe of course? But will I lose the twrp recovery in recovery partition and have to do fastboot recovery to flash again or anything like that?
Sent from my Xperia Z2 using XDA Free mobile app

Recovery won't get changed. Just wipe the system and install

This ROM is buttery smooth just wondering if this is still in development? Or are you mainly focussing on cm12? Moved to this ROM because of the screen issues on cm12, it was making my phone too hot :/

[ROM][SIRIUS][LP][5.1.1_r10][SM-4.9.x] Slim LP SaberMod Builds [BETA 0.6]

{
"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"
}
Z2/SIRIUS/D6503 SLIM LP SABERMOD BUILDS
BETA v0.6 IS UP!
LOLLIPOP 5.1.1_r10
DOWNLOAD
NOT WORKING YET: (?)
ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150804)
KERNEL COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150804)
SOURCE: https://github.com/infected-lp/kernel_sony_msm8974/tree/saber
[+] -O3 Optimizations
[+] LTO
[+] strict-aliasing
[+] frame-pointers
[+] Graphite
[+] CPU specific flags (armv7-a-neon)
[+] Other GCC flags to optimize the build
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM THIRD POST
- NO MODS OF ANY SORT
CHANGELOG:
https://review.slimroms.eu/#/q/status:merged
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 250gb ssd 850 evo + 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 SlimRoms open-source code:
https://github.com/SlimRoms
SPECIAL THANKS
SlimRom Dev Team = for the source code.
​
XDA:DevDB Information
Z2/Sirius/D6503 Infected Sabermod Slim LP Builds, ROM for the Sony Xperia Z2
Contributors
infected_
Source Code: https://github.com/SlimRoms
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest TWRP recommended
Based On: SlimROMs
Version Information
Status: Beta
Current Beta Version: 0.6
Beta Release Date: 2015-08-24
Created 2015-02-25
Last Updated 2015-08-25

Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash recovery recovery.img (TWRP = http://teamw.in/project/twrp2/232)
- fastboot flash boot boot.img (extract boot.img from latest slimlp build zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- wipe it all..!
- flash rom zip
- flash gapps zip
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them, like on this thread:
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

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

Cool buddy
Thanks for this too

First of all, thanks for all your efforts for keeping development for Z2 alive~! I'm really shocked by the lack of official and common custom roms for Z2.
Q: is this rom only for D6503 model? Or i can flash it for 6502 too with a patch?

Aeonxul said:
First of all, thanks for all your efforts for keeping development for Z2 alive~! I'm really shocked by the lack of official and common custom roms for Z2.
Q: is this rom only for D6503 model? Or i can flash it for 6502 too with a patch?
Click to expand...
Click to collapse
it should work ok on D6502, the sh script it theres on the zip.

Its working fine on D6502!

Is your loudspeaker fix included?

new build is up.
edit: not booting with multirom. someone test with a "normal flash"

infected_ said:
new build is up.
edit: not booting with multirom. someone test with a "normal flash"
Click to expand...
Click to collapse
Boot-looping on Sony logo after flashing according your instructions...

brouwerchris said:
Boot-looping on Sony logo after flashing according your instructions...
Click to expand...
Click to collapse
thanks. already removed it.

Is it as stable as cm12 infected ? Or has some major bugs?
I would test or myself but can't go back and fourth between my current rom
Thanks in advance

New alpha 0.1 is up.

infected_ said:
]
Click to expand...
Click to collapse
Your website or server id down
cant download anything just getting blank white page with
Code:
powered by h5ai 0.26.1

Quick question. With this being a stock Kernel is it flashable on locked Bootloaders?
Sent from my D6503 using XDA Free mobile app

ianrobbie said:
Quick question. With this being a stock Kernel is it flashable on locked Bootloaders?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
no

Only with me on latest build no enter key on sim-pin page ??

Can anyone upload mirror link for downaload

[email protected] said:
Your website or server id down
cant download anything just getting blank white page with
Code:
powered by h5ai 0.26.1
Click to expand...
Click to collapse
you are trying to download from a PC or a mobile device?

infected_ said:
you are trying to download from a PC or a mobile device?
Click to expand...
Click to collapse
Tried on both and tried proxy as well but no luck but thanks anyway

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

{
"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"
}
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.
​
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

GAPPS
http://forum.xda-developers.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.

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.
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. 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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Screenshots of toolchains used and benchmarks.

Woohoo!
We were talking about this yesterday!
Edit: Downloading now.
Will put all issues here!

you may need to wipe for first install, i had to. and 5.0.2 gapps are compatible.

great
:good: thank's @infected_ :good:

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

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?

sbreit said:
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?
Click to expand...
Click to collapse
yes, you need to wipe /data .. i needed to, or i would be stuck at boot animation.

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.

twistedddx said:
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.
Click to expand...
Click to collapse
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)

Can I please get a link to the GApps we suppose to use?
Do we have a recovery on this ROM?

Puffin617 said:
Can I please get a link to the GApps we suppose to use?
Do we have a recovery on this ROM?
Click to expand...
Click to collapse
+1
I would love links to corresponding pico package as well

Here you can find all the gapps you want
http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693

Is this rom will work on D6502?
Sent from my D6502 using XDA Free mobile app

@infected_,
which GApps do you recommend?

hambalos said:
Is this rom will work on D6502?
Sent from my D6502 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the patch.

Puffin617 said:
@infected_,
which GApps do you recommend?
Click to expand...
Click to collapse
The ones from Deltadroid ..
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
i added them to third post.

Does this work ont the D6543 ??

It's amazing to see that everything works as well as cm12. Awesome job! Now if only a custom kernel was available ?

[ROM][LP][5.1.1_r6][SM-4.9.x/4.9.x] OMNI ROM 5.1.1 UNOFFICIAL [20150704]

{
"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"
}
Z2/SIRIUS/D6503 OMNI ROM UNOFFICIAL BUILDS
LOLLIPOP 5.1.1_r6
DOWNLOAD
NOT WORKING YET: Camera
ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150704)
KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150704)
SOURCE: https://github.com/infected-lp/sony_msm_3.10
- Clang Optimized with -O3
- Linker Optimizations
- Graphite Flags
- CPU architecture specific flags
- Other GCC flags to optimize the build
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM THIRD POST
- NO MODS OF ANY SORT
CHANGELOG:
https://changelog.omnirom.org/
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, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from Omni ROM open-source code:
https://github.com/omnirom
SPECIAL THANKS
Omni ROM Dev Team = for the source code.
​

GAPPS
http://forum.xda-developers.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.
SUPERSU
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 LP 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.
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. 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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse

Hi,
Where can I see the feature list?

Testing and report with screens soon
Edit : tab to wake,sleep is missing. 3.10 kernel doesn't have ROW i/o

Kernel 3.10, I'm interested in it, will try this rom as soon as the loudspeaker fixed.

thread re-opened and build 20150704 is up!
regards.

infected_ said:
thread re-opened and build 20150704 is up!
regards.
Click to expand...
Click to collapse
Thanks bro,
do you think to continue the developement? I love "work in progressssss"
sorry for my bad english .....

robby.pgn said:
Thanks bro,
do you think to continue the developement? I love "work in progressssss"
sorry for my bad english .....
Click to expand...
Click to collapse
The development is still in it's early stages. Omni Maintainer Team for the shinano device family (me being one of them) has just started to work on OmniROM based on the Sony AOSP trees recently, hence there are no official releases yet. There still is no working camera, but everything else should work fine.
@infected_ you might want to update the not working list to Camera not working, LoudSpeaker is working fine for me.
Assuming you did not pick any commits from the Omni Gerrit you also want to add Recovery as not working since you can't enter it without these 2 commits:
https://gerrit.omnirom.org/#/c/12817/
https://gerrit.omnirom.org/#/c/12818/
and the removal of these 2 lines:
https://github.com/omnirom/android_...id-5.1/recovery/root/etc/bootrec-device#L3-L4

Myself5 said:
The development is still in it's early stages. Omni Maintainer Team for the shinano device family (me being one of them) has just started to work on OmniROM based on the Sony AOSP trees recently, hence there are no official releases yet. There still is no working camera, but everything else should work fine.
@infected_ you might want to update the not working list to Camera not working, LoudSpeaker is working fine for me.
Assuming you did not pick any commits from the Omni Gerrit you also want to add Recovery as not working since you can't enter it without these 2 commits:
https://gerrit.omnirom.org/#/c/12817/
https://gerrit.omnirom.org/#/c/12818/
and the removal of these 2 lines:
https://github.com/omnirom/android_...id-5.1/recovery/root/etc/bootrec-device#L3-L4
Click to expand...
Click to collapse
thanks, but entering recovery is fine. dont know if you noticed, but the commits you pointed are already merged...
regards.

@Myself5 @infected_
Is cam, headset / calling thru headphones and thermal managment fully working?

Destroyedbeauty said:
@Myself5 @infected_
Is cam, headset / calling thru headphones and thermal managment fully working?
Click to expand...
Click to collapse
AFAIK, only cam is not working, but @Myself5 being the maintainer, should be able to answer better than me.
regards.

Destroyedbeauty said:
@Myself5 @infected_
Is cam, headset / calling thru headphones and thermal managment fully working?
Click to expand...
Click to collapse
infected_ said:
AFAIK, only cam is not working, but @Myself5 being the maintainer, should be able to answer better than me.
regards.
Click to expand...
Click to collapse
cam is not (yet) working, calling trough headphones should work but I have not tested it yet personally. Thermanager is the same as CM uses (as CM uses the AOSP thermanager), you can decide on your own if you call it working or not I personally encounter some issues with the CPU throttle on both, AOSP and CM based ROMs, but one is able to life with them.

Myself5 said:
cam is not (yet) working, calling trough headphones should work but I have not tested it yet personally. Thermanager is the same as CM uses (as CM uses the AOSP thermanager), you can decide on your own if you call it working or not I personally encounter some issues with the CPU throttle on both, AOSP and CM based ROMs, but one is able to life with them.
Click to expand...
Click to collapse
Then - I'll stay on stock ROM..
Needs fully working cam and so so. Sorry :/