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

[infected_]

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

 

[infected_]

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.

 

[infected_]

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.

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. 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.

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.

 

[infected_]

+1

 

[infected_]

++1

 

[azam426]

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.)

 

[_delice_doluca_]

tested and not impressed.. I think i'll continue with CM12 for now.

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

 

[cheep5k8]

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...

 

[TheMrcool212]

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...

The quick pulldown was merged into the main source yesterday, to be clear.

Turning it off will be soon, see their gerrit.

 

[cheep5k8]

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!

 

[infected_]

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...

"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.

 

[TheMrcool212]

"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.

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.

 

[azam426]

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

Oh my god.. fighters everywhere..
we dont have freedom to tell what we feel about something?
what kind of world is this?
****ty people.

 

[TheMrcool212]

Oh my god.. fighters everywhere..
we dont have freedom to tell what we feel about something?
what kind of world is this?
****ty people.

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.

 

[GeekyAndroid]

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).

 

[benjmiester]

Do we use the gapps from cm12 Roms for this?

Sent from my Xperia Z2 using XDA Free mobile app

 

[infected_]

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).

Development just started.. and Paranoid Android (AOSPA) is AOSP based, not CM.

Do we use the gapps from cm12 Roms for this?

Sent from my Xperia Z2 using XDA Free mobile app

use the cm12 gapps on basketbuild: https://s.basketbuild.com/gapps

they work fine.

regards.

 

[benjmiester]

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

 

[bluheart]

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

 

[joeliomason]

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 :/