• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][v500][LP][5.1.1_r6][SM-4.8.x/4.8.x] CyanogenMod 12.1 SaberMod Builds

Status
Not open for further replies.

infected_

Recognized Developer
Jul 12, 2008
5,830
14,118
113
Portugal
infectedbuilds.net



v500/G Pad 8.3" CYANOGENMOD 12.1 SABERMOD BUILDS

Android Lollipop 5.1.1_r6

DOWNLOAD #1
(main server)

DOWNLOAD #2
(backup server)

(md5sum included with all builds)

ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.8.x (20150704)
KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.8.x (20150704)

SOURCE: https://github.com/infected-lp/android_kernel_lge_v500/tree/infected

- -O3 Optimization (thumb & arm)
- strict-aliasing
- frame-pointers
- Linker Optimizations
- Graphite Flags
- CPU Arch specific flags
- Other GCC flags to optimize the build

CHANGELOG

http://www.cmxlog.com/12.1/v500/

(buildbot: intel core i7 3770k, asus p8z77-v, 24gb corsair vengeance pro 2133mhz cl11, msi gtx 970, 1x samsung ssd 850 evo + 1x samsung 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, 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 CyanogenMod Rom open-source code:

https://github.com/CyanogenMod

Special Thanks

CyanogenMod Dev Team = for the code sources.



XDA:DevDB Information
v500/G Pad 8.3 SaberMod CyanogeMod 12.1 Unofficial Builds, ROM for the LG G Pad 8.3

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-30
Last Updated 2015-07-12
 
Last edited:

infected_

Recognized Developer
Jul 12, 2008
5,830
14,118
113
Portugal
infectedbuilds.net
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 v500/LG G Pad.
ROM is built using the same source code (github) like the official one but with these following additions:
  • Compiled using sabermod arm-eabi 4.8.5 (kernel code) & sabermod arm-linux-androideabi 4.8.5 (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.

screenshots in attachment.
 

Attachments

Last edited:

uzi2

Elite Member
Jun 6, 2008
2,528
638
113
When you say a wipe are you talking about a Factory Reset, or something more specific? If more specific, what do I need to wipe?
A Factory Reset (standard wipe in TWRP)
There is a report of success with a dity flash over CM12, but I had to do a Factory Reset in order to get it to boot, as did the OP.
 
  • Like
Reactions: infected_

Cal

Senior Member
Dec 25, 2013
366
152
0
Under this one (Infected's 12.1) the recent downloads are located here.
One *has* to do a factory reset & be using Deltandroid's 5.0.2 gapps. One thing, I had by using Red's 16 kernel was getting a 'orange' tint on blue icons, so reverted to Red's 15 & all is great!! Using Infected's 2015-3-31 ROM. :good:

*Edit:* Using 4.4.2 bootloader. Get a vague dimming when booting to recovery, but only a second & then recovery is bright.
 
Last edited:

uzi2

Elite Member
Jun 6, 2008
2,528
638
113
Under this one (Infected's 12.1) the recent downloads are located here.
One *has* to do a factory reset & be using Deltandroid's 5.0.2 gapps. One thing, I had by using Red's 16 kernel was getting a 'orange' tint on blue icons, so reverted to Red's 15 & all is great!! Using Infected's 2015-3-31 ROM. :good:

*Edit:* Using 4.4.2 bootloader. Get a vague dimming when booting to recovery, but only a second & then recovery is bright.
How can dimming when booting to Recovery be relevant to any ROM you are using?
 

Cal

Senior Member
Dec 25, 2013
366
152
0
How can dimming when booting to Recovery be relevant to any ROM you are using?
It was really not relevant to the ROM - only that recovery latest TWRP could dim if using a 4.4.2 bootloader.
Was stated with the latest TWRP recovery - best to use a 4.2.2 Base.
 
Last edited:

Cal

Senior Member
Dec 25, 2013
366
152
0
I'm using this one instead of CM 12...can't understand the seemingly lack of interest in this version. Anyone have a comment? It runs solid and smooth and just upgraded to the latest version and all seems fine.
Comments regarding this version?
 
Status
Not open for further replies.