Related
{
"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
{
"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"
}
LG G PAD 8.3"/awifi/v500 SLIMROM LP SABERMOD BUILDS
BETA 0.14 is up.
LOLLIPOP 5.1.1_r33
DOWNLOAD
NOT WORKING YET: (?)
ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.x (20151224)
KERNEL COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.x (20151224)
KERNEL SOURCE: https://github.com/infected-lp/android_kernel_lge_awifi/tree/saber
[+] -O3 optimized (arm and thumb)
[+] strict-aliasing
[+] frame-pointers
[+] graphite flags
[+] LinkTimeOptimizations (-flto) flags
[+] cpu arch specific flags (armv7-a)
[+] 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:
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 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 crossflow 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
@fefifofum for letting me use his device trees.
SlimRom Dev Team = for the source code.
XDA:DevDB Information
LG G PAD 8.3, ROM for the LG G Pad 8.3
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.14
Beta Release Date: 2016-01-08
Created 2015-06-01
Last Updated 2016-01-08
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 LG G Pad 8.3"
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod arm-eabi 5.2.x (kernel code) & sabermod arm-linux-androideabi 4.9.x (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
Flashing Instructions
First time installing:
Flash CWM recovery or TWPR recovery.
Place build zip + gapps on internal/external memory
reboot into recovery
wipe /system /data /cache
flash build + gapps
reboot
you're done, enjoy!
Coming from previous build version:
Flash build, wipe cache.
you're done, enjoy!
SLIM GAPPS
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
WoW !! Thx for this. Try it later
Its working fine!!!
nice to see slim back on this tab
found one issue: dt2w doesn't work, but the rest seems to work fine even layers <3
Darkmasterhk said:
nice to see slim back on this tab
found one issue: dt2w doesn't work, but the rest seems to work fine even layers <3
Click to expand...
Click to collapse
Layers work? I applied a later and the settings screen was messed up. All the text was invisible.
@infected_
Thank you for bringing back Slim to our V500. As you are working on the ROM, can you add Layers related commits to the ROM. Slim Team is still undecided whether to go for rro layers in their official builds. But there is a SlimSaber build for one p!us one by a dev called fusionjack. And he has fully integrated layers in his build of SlimLP. If you plan to add layers you can check with him.
Once again,
Thanks.
indian84 said:
Layers work? I applied a later and the settings screen was messed up. All the text was invisible.
@infected_
Thank you for bringing back Slim to our V500. As you are working on the ROM, can you add Layers related commits to the ROM. Slim Team is still undecided whether to go for rro layers in their official builds. But there is a SlimSaber build for one p!us one by a dev called fusionjack. And he has fully integrated layers in his build of SlimLP. If you plan to add layers you can check with him.
Once again,
Thanks.
Click to expand...
Click to collapse
i know who @fusionjack is .. we were building ROMs at the same time, a couple years back for the i9100 .. right FJ ?!
ill talk to him if i decide for the layers or not.
infected_ said:
i know who @fusionjack is .. we were building ROMs at the same time, a couple years back for the i9100 .. right FJ ?!
ill talk to him if i decide for the layers or not.
Click to expand...
Click to collapse
Correct. He is from i9100. @fusionjack. Hopefully we will have 100% layers support.
indian84 said:
Layers work? I applied a later and the settings screen was messed up. All the text was invisible.
@infected_
Thank you for bringing back Slim to our V500. As you are working on the ROM, can you add Layers related commits to the ROM. Slim Team is still undecided whether to go for rro layers in their official builds. But there is a SlimSaber build for one p!us one by a dev called fusionjack. And he has fully integrated layers in his build of SlimLP. If you plan to add layers you can check with him.
Once again,
Thanks.
Click to expand...
Click to collapse
at least a few Elixium UI layer e.g. works fine with default dpi.
Darkmasterhk said:
at least a few Elixium UI layer e.g. works fine with default dpi.
Click to expand...
Click to collapse
Correct. Even element theme worked for me.
Hey @infected_
Wanted to report back about layers. The earlier report of some layers working is only partially correct.
Only light themes work and that too only partial items get themed.
Are you still planning to implement full layers support?
And if you are OK with it, how frequently you planning to update the ROM?
Not asking for ETA.
indian84 said:
Correct. Even element theme worked for me.
Hey @infected_
Wanted to report back about layers. The earlier report of some layers working is only partially correct.
Only light themes work and that too only partial items get themed.
Are you still planning to implement full layers support?
And if you are OK with it, how frequently you planning to update the ROM?
Not asking for ETA.
Click to expand...
Click to collapse
ill leave the layers support for later.
these was supposed to be weekly builds, same has always. but slim is still at version 0.3, hasnt been bumped, thats why i havent build it yet.
infected_ said:
ill leave the layers support for later.
these was supposed to be weekly builds, same has always. but slim is still at version 0.3, hasnt been bumped, thats why i havent build it yet.
Click to expand...
Click to collapse
Thanks for the info. And you are correct about 0.3 isn't been bumped yet.
Cheers dude..
Works fine for me after more 6 days
Amazing, Smooth, Fast. @infected_ You should become a part of Slim Team.. ?
alpha v0.4 is up!
regards.
infected_ said:
alpha v0.4 is up!
regards.
Click to expand...
Click to collapse
Thanks...
Hi guys, I'm having the backlight problem, how do I solve it? Flashing bootloader? Wich one?
Thanks in advanced
bokoy said:
Hi guys, I'm having the backlight problem, how do I solve it? Flashing bootloader? Wich one?
Thanks in advanced
Click to expand...
Click to collapse
happened to me last week, after flashing stock lollipop for v500..
i had to flash stock kdz 4.2.2 and then flash CM12.1/Slim, but i am sure theres easiest ways.
regards.
Many thanks infected, at least finally I'm able to try your job, wich is excellent.
Edit: finally there is no backlight problem, only while booting, once booted works perfect. Again thanks infected, best rom i have ever tryed for this device, no doubt?
{
"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"
}
Z5/SUMIRE/E6653 OMNIROM UNOFFICIAL SABERMOD BUILDS
MARSHMALLOW 6.0.1_r74
Current Build: 20161110
DOWNLOAD
CURRENT ISSUES:
- you tell me!
ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.x (20160726)
KERNEL SOURCE: https://github.com/deepongi/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 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 4x western digital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from Omni ROM open-source code.
XDA:DevDB Information
OMNIROM FOR Z5/SUMIRE/E6653, ROM for the Sony Xperia Z5
Contributors
infected_
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Beta
Created 2016-04-20
Last Updated 2016-11-10
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
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 Omni Rom for the Xperia Z5 (E6653)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 4.9.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
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
Sweet !
Whoaah @infected_ good to see u around here! I remember u from Yuga
Sent from my E6653 using XDA-Developers mobile app
Great! AOSP 4dawin =D
Great ! Thanks
Sent from my E6653 using XDA-Developers mobile app
@infected_ is that you from the i9100 days?[emoji14]recognise your name.
Sent from my E6653 using Tapatalk
Fingerprint works ?
Sent from my E6653 using XDA-Developers mobile app
Dockyy said:
Fingerprint works ?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not yet.
regards.
Ha ha! infected_ strikes back!
A long while ago I had your Cyanogen on my Z2. Good work.
Excellent. When all is functional this will be my new ROM for sure. Please let me know when anything needs to be tested. Thanks
new build is up!
- brightness is fixed.
- in sync with aosp and omni device trees
please report bugs with logs attached.
regards.
@infected_ Just curious to know why you are linking to 32bit GAPPS. I know the phone is 64bit architecture, so is there something different with your ROM config? Or does it not really matter when using CM/AOSP base?
wickedmx said:
@infected_ Just curious to know why you are linking to 32bit GAPPS. I know the phone is 64bit architecture, so is there something different with your ROM config? Or does it not really matter when using CM/AOSP base?
Click to expand...
Click to collapse
the only part of the ROM that is compiled with arm64 toolchains is the kernel.. the other ROM code is compiled with arm. So basically you have a 64bits device running a 32bits rom.
i never had any issue with them, and been using them since they were launched... thats why i recommend it.
maybe you can ask @Deltadroid for further enlightenment.
regards.
infected_ said:
the only part of the ROM that is compiled with arm64 toolchains is the kernel.. the other ROM code is compiled with arm. So basically you have a 64bits device running a 32bits rom.
Click to expand...
Click to collapse
Sweet, thanks for the quick reply. So it's basically the same principle as running 32 bit programs on a 64 bit desktop OS.
Hello, this ROM is also compatible with the version Xperia Z5 Dual (E6683 / E6633)?
pickmod said:
Hello, this ROM is also compatible with the version Xperia Z5 Dual (E6683 / E6633)?
Click to expand...
Click to collapse
maybe. flash and see. the worst thing that can happen is you need to flash a dual sim patch thats around in the forum somewhere.
regards.
Will this work on E6683?
pickmod said:
Hello, this ROM is also compatible with the version Xperia Z5 Dual (E6683 / E6633)?
Click to expand...
Click to collapse
thetitanium said:
Will this work on E6683?
Click to expand...
Click to collapse
infected_ said:
maybe. flash and see. the worst thing that can happen is you need to flash a dual sim patch thats around in the forum somewhere.
regards.
Click to expand...
Click to collapse
above ^
regards.
{
"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"
}
Z5/SUMIRE/E6653 SLIMROM SLIM6 SABERMOD BUILDS
v1.5 IS UP!
MARSHMALLOW 6.0.1_r72
DOWNLOAD
NOT WORKING YET: NFC
ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.X (20160726)
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
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
Z5/SUMIRE/E6653 SlimRom Slim6 Sabermod Builds, ROM for the Sony Xperia Z5
Contributors
infected_
Source Code: https://github.com/SlimRoms
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest TWRP recommended
Based On: SlimROMs
Version Information
Status: Stable
Created 2016-06-18
Last Updated 2016-10-13
Reserved
Coming from stock sony:
- download build, and extract boot.img
- download twrp from here, and as alternative cm recovery from here (note that cyanogenmod recovery doesnt support busybox)
- fastboot flash recovery twrp_recovery_20160607.img
- enter recovery, wipe and flash build, plus gapps.
- reboot and you are done!
Coming from an aosp based rom:
- enter recovery, wipe and flash build, and gapps
- you are done!
ROOT:
enable it on developer settings.
Reserved
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of SlimRom Slim6 for the Xperia Z5 (E6653)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 4.9.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
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
alpha v0.3 is up.
also ive updated the kernel code toolchain.
regards.
Wish I could help beyond adding some encouragement - but at the moment as camera isn't working properly I can't flash any custom ROM (although I'm itching to get rid of Sony's offering) because my Z5 is my only device.
building with these updated binaries fixed the screen flickering in aosp for me i was unable to boot with them in cm13 though.
http://developer.sonymobile.com/downloads/tool/software-binaries-for-experimental-aosp-marshmallow/
SW_binaries_for_Xperia_AOSP_M_v01b_exp.zip
celderic said:
building with these updated binaries fixed the screen flickering in aosp for me i was unable to boot with them in cm13 though.
http://developer.sonymobile.com/downloads/tool/software-binaries-for-experimental-aosp-marshmallow/
SW_binaries_for_Xperia_AOSP_M_v01b_exp.zip
Click to expand...
Click to collapse
Screen flickering was solved a while back, on the 1.2.2 kernel branch, and using superbenevolant blobs repo, which also work on cm13.0
github.com/deepongi
Have a peek there.
Regards.
Sent from my E6653 using XDA-Developers mobile app
celderic said:
building with these updated binaries fixed the screen flickering in aosp for me i was unable to boot with them in cm13 though.
http://developer.sonymobile.com/downloads/tool/software-binaries-for-experimental-aosp-marshmallow/
SW_binaries_for_Xperia_AOSP_M_v01b_exp.zip
Click to expand...
Click to collapse
Those are for the new, WIP, 1.3.3 kernel branch only, no ?
zacharias.maladroit said:
Those are for the new, WIP, 1.3.3 kernel branch only, no ?
Click to expand...
Click to collapse
Yes i think so, just playing around with it trying to get the kernel to boot cm13
Hi, sorry for asking, but will this rom get updated?Because v0.8 relased, but this rom is still stuck at 0.4
I've had another cleanup here and I'd prefer not to have to return for more of the same.
Please refrain from engaging with trolls here... you're not helping anything.
Just press the report button and let a moderator deal with it.
Certainly do not respond with profanities like you have been or I will be dealing with your XDA account also.
Sometimes when i turn on the phone the screen is like an old TV showing no channel, or half the screen does it, really weird anyway to fix this? graphics bug?
shaunm1989 said:
Sometimes when i turn on the phone the screen is like an old TV showing no channel, or half the screen does it, really weird anyway to fix this? graphics bug?
Click to expand...
Click to collapse
Reboot the phone, and get a dmesg.
I assume you're on a JDI Novatek panel. The issue is known, but nobody is up for fixing it yet. I'm having the same issue btw, so don't worry [emoji14] Just turn off the screen and turn it on again.
Sent from my D6603 using Tapatalk
Bug:
Screen always stays in portrait mode, no matter which way the phone is held. Screen rotation is enabled in quick settings.
SlimROM v1. 5
Is it possible to change kernel parameters? Any app recommended?
husky69 said:
Is it possible to change kernel parameters? Any app recommended?
Click to expand...
Click to collapse
Kernel auditur
Hmmmm. Anyone work on this Rom for Feature?
Hi, the rom can't detect my external memory. Is it just me or is it bug?
{
"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"
}
Z5/SUMIRE/E6653 PARANOID ANDROID/AOSPA UNOFFICIAL SABERMOD BUILDS
MARSHMALLOW 6.0.1_r72
Current Build: 20161011
DOWNLOAD
CURRENT ISSUES:
- you tell me!
ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.x (20160726)
KERNEL SOURCE: https://github.com/deepongi/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.aospa.co/#/q/status:merged
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung 850 evo + 1x samsung 128gb ssd 840 pro, 4x western digital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from Paranoid Android/AOSPA open-source code.
XDA:DevDB Information
Paranoid Android For Z5/SUMIRE/E6653, ROM for the Sony Xperia Z5
Contributors
infected_
Source Code: https://github.com/aospa
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Created 2016-06-29
Last Updated 2016-10-11
INSTRUCTIONS:
- download the latest build zip, and extract boot.img
- place the build, gapps and supersu somewhere on external/internal memory.
- download twrp recovery - http://www.infectedbuilds.net/downloads/sumire/pa_mm/twrp/recovery.img
- fastboot flash the boot img and recovery 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
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 Paranoid Android/AOSPA Rom for the Xperia Z5 (E6653)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 4.9.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
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
Hi so thanks for rom
My devıce ıs E6603
Can ı use thıs rom ın my devıce?
Lptrex9 said:
Hi so thanks for rom
My devıce ıs E6603
Can ı use thıs rom ın my devıce?
Click to expand...
Click to collapse
yes you can.
regards.
My most favorite ROM, thank you but, I can't taste it since I'm owning a dsds device, hope you would be easier to build a ROM for devices that you don't own.
RyTekk said:
My most favorite ROM, thank you but, I can't taste it since I'm owning a dsds device, hope you would be easier to build a ROM for devices that you don't own.
Click to expand...
Click to collapse
+1 for this. I'm really waiting for this ROM on my E6683. I wish you could make it support our Dual Sim Variant
Thank you very much for that rom!
Waiting for that one too! My Z is still running PA! Thank you so much!
Sent from my E6653 using XDA-Developers mobile app
Used it for a day. Surprisingly usable as a whole.
Several cons to consider:
Speakers sound distorted near full volume.
Camera is functional, but not very usable.
Display artifacts occasionally on lock screen when being woken up.
No indication of charging other than Led (perhaps this is by design?)
Besides these few things the ROM was snappy and fluid.
would pay for dsds support
Is it just me or are the essential things like pie an peek missing from this ROM for a reason? I can't seem to find anything
Baltiweed said:
Is it just me or are the essential things like pie an peek missing from this ROM for a reason? I can't seem to find anything
Click to expand...
Click to collapse
A lot of PA key features have been abandoned from Lollipop.
RyTekk said:
A lot of PA key features have been abandoned from Lollipop.
Click to expand...
Click to collapse
Why are these features still presented on the official website as if they are active?
Baltiweed said:
Why are these features still presented on the official website as if they are active?
Click to expand...
Click to collapse
Most likely because PA hasn't updated their website yet. They can be slow to do so
Thanks for your great work, rom works fine on my Z5 E6603
Enviado desde mi Xperia Z5 (AOSPA) mediante Tapatalk
new build is up using new updated kernel.
regards.
Thank you very much!
Anyone tried PA with Multirom? Last time I tried it didn't boot.
Thanks in advance
Sent from my E6653 using XDA-Developers mobile app
Panaroma said:
Thank you very much!
Anyone tried PA with Multirom? Last time I tried it didn't boot.
Thanks in advance
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
It boots.
@infected_ is exfat not supported?
Sent from my E6653 using XDA-Developers mobile app
new build is up, using sony aosp v2 marshmallow blobs, along with new kernel.
camera is working!
video recording is still broken, but being fixed.
enjoy!
regards.
ps:
stock camera after taking the pic it crashes, you need to use a 3rd party one.
i advise the use of "snap hdr camera", google cam, htc cam, or snapdragon cam.
langeveld024 said:
It boots.
@infected_ is exfat not supported?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not sure. give it a spin to latest build, and check it out.