v500/G Pad 8.3" SLIMKAT LINARO/SABERMOD WEEKLY BUILDS
Final Build 9.0 is ONLINE
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.7.4 201406 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.5 201412 toolchain
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
graphite
(buildbot: intel core i7 [email protected], asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11, nvidia gtx 970, 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.1 x64 "Rebecca" 3.13.0-39)
Disclaimer:
These builds are freshly compiled/synced from SlimRoms open-source code:
https://github.com/SlimRoms
latest linaro arm-eabi-4.7.4 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.5 toolchains to compile ROM code
Special Thanks
SlimRoms Dev Team
Flashing Instructions
First time installing:
Flash CWM recovery or TWPR recovery.
Option #1 = http://forum.xda-developers.com/showthread.php?t=2588671
Option #2 = http://forum.xda-developers.com/showthread.php?t=2641409
Place build zip + gapps on internal/external memory
reboot into recovery
wipe /system /data /cache
flash build + gapps
wipe cache
reboot
you're done, enjoy!
Coming from previous build version:
Flash build, flash gapps
you're done, enjoy!
Gapps = SlimRom Gapps
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of SlimKat 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 linaro arm-eabi 4.7.4 14.04 (kernel code) & sabermod arm-linux-androideabi 4.8.3 14.04 (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?
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/
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
Wow.. Thanks Again..
Removed.
I must have picked the right time to root etc my Pad as yet another superb ROM is now here to try.
Having just nandroid the CM 11 build I have now wiped and flashed this. It looks every bit as good as it does on my Nexus 5. I love the built in DPI as well as the inverted GAPPS, when the darker Slim is selected.
All seems well so far.
Thanks for sharing
Seems to work well, thanks!
Am I the only one who is having a problem with the screen being way too dim? Setting up the tablet after the first reboot was a pain. Could it be tied to the recovery version on my device? I am running TWRP 2.7.
Running fine. Swapped over from Demetris' build to see if any different. Did have a sound glitch when on Spotify that I don't notice here. Might be smoother as well or could be placebo effect.
new linaro/sabermod SlimKat build 4.9 is up!
regards.
Love the Rom, best I've tried. Can't seem to see 4.9 on the download server? Sorry if I'm being blind
Sent from my LG-V500 using Tapatalk
joegrant said:
Love the Rom, best I've tried. Can't seem to see 4.9 on the download server? Sorry if I'm being blind
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
It's on the Slim website. Download section, weekly, and V500 device.
thanks, I was looking at the infected server from the Op. maybe that can be changed to the slimkat website if the infected server is not being updated. cheers
Sent from my MI 2S using Tapatalk
sorry, but i wasnt aware the upload failed.
i re-uploaded build 4.9
regards.
@infected_ Could you build the v5.PCFR release?
Thanks
Demetris said:
@infected_ Could you build the v5.PCFR release?
Thanks
Click to expand...
Click to collapse
yes.
Code:
SLIM_VERSION=Slim-4.4.2.build.5.PCFR-INFECTED-20140510-1607
i'll upload as soon has it finishes.
build 5 PCFR is up!
Ok I'll bite
What is PCFR...?
BTW excellent work yet again for the continuing support
vimesUK said:
Ok I'll bite
What is PCFR...?
BTW excellent work yet again for the continuing support
Click to expand...
Click to collapse
Whatever it is I lost root after flashing it
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
Whatever it is I lost root after flashing it
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
go to developer settings and enable it...
Is it possible to install SuperSU from Chainfire on this after you enable root? It just feels a little faster.
infected_ said:
go to developer settings and enable it...
Click to expand...
Click to collapse
Infected Thanks for the GREAT effort you are putting into these ROMs, really appriciated.
You will be the first I will donate some beer to!!!
Related
i9100 CYANOGENMOD 10.2 LINARO/SABERMOD BUILDS
Build 10.2.1 Final is ONLINE
Build/Sync Date: Feb 01 2014 --h:-- GMT+00h:00 Lisbon
DOWNLOAD
(MediaFire - Main Mirror)
DOWNLOAD
(AndroidFileHost - Backup Mirror)
(md5sum included with all builds)
DONATIONS NEEDED
ok... here's the deal..
i don't like asking for donations, because i am doing this almost for fun, and learning new stuff. but this time its really needed...
i trying to expand the linaro/sabermod builds "business".. for this, we should start to have our own website for starters, where i can publish our builds.
websites requires work, knowledge, and money above all.
the website is already a WIP, and almost complete:
http://pierun.tk/white/
http://pierun.tk/dark/
thanks @Pumpernikiell for the work he had.
it will have two versions. one white, the one i gave the link, and a dark one.
i am asking if to you all, that every day download and use the builds i compile, if all of you give just even $1/1€, it will be enough money to buy a domain, a hosting server, and maybe if theres enough donations, even a VPS...
so, please donate what you can, so this project goes forward, and keeps getting better, and better.
you can donate, using this link: DONATE
thank you all,
infected_
Click to expand...
Click to collapse
(cross-compiled with sabermod arm-linux-androideabi-4.9.0 201307, and linaro arm-eabi-4.7.4 201312 toolchains)
-O3 building optimizations;
custom performance flags;
strict-aliasing rules;
cortex string routines handling;
sqlite fsync hack (by dorimanx);
over +30 cherry-picked commits/patches;
CHANGELOG 10.2
http://review.cyanogenmod.org/#/q/status:merged+branch:cm-10.2,n,z
(always compare build/sync date (settings -> about phone) with changelogs)
STATS
CM 10.1 PROJECT STATS @ 20130922 14h:20 GMT+00h:00 Lisbon (+1h Summer Time)
Builds = 57
Downloads TOTAL = 7843
CM 10.2 PROJECT STATS @ 20130922 14h:28 GMT+00h:00 Lisbon (+1h Summer Time)
Builds = 32
Downloads Total = 10169
Click to expand...
Click to collapse
These builds are hosted in my private account at MediaFire (purchased account - 120GB | no ads and really fast downloads!)
(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,
2x western wigital wd3200aaks raid 0 array, samsung f1 1tb, 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 16 "Petra" x64 3.13.1)
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod open-source code:
https://github.com/CyanogenMod
When its necessary, it can be cherry-picked a commit and integrate it on the build
sabermod arm-linux-androideabi-4.9.0 201307, and linaro arm-eabi-4.7.4 201310 toolchains used to cross-compile.
If you have any doubt or question, post it in the main thread, so we can help out.
You can check Officials CM 10.1 & CM 10.2 threads for support also, since the source code is the same.
Special Thanks
IAmTheOneTheyCallNeo, DJLamontagneIII, fusionjack and bluefa1con - for the tips, and some of the commits/patches on the ROM building.
Karpfenhai - user support.
Click to expand...
Click to collapse
{
"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"
}
Instructions/Download Links
OFFICIAL CM WIKI
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/I9100_Info
OFFICIAL CM INSTRUCTIONS
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy S II, or coming from another ROM:
- Copy GApps and CM10.2 ZIPs to your internal SDCard
- Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG. If you're unsure, flash this ClockworkMod-Recovery using Odin/Heimdall.
- Make sure you're running a proper working ClockworkMod-Recovery
- Boot into Recovery
- Flash CM10.2 zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.2:
- Copy CM10.2 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM10.2 zip from internal SDCard
- Reboot
Upgrading from CyanogenMod 10.1:
- Copy 4.3 GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- Reboot
DOWNLOADS
Click to expand...
Click to collapse
i9100 LINARO/SABERMOD CM 10.1 & 10.2 Nightly Builds:
MediaFire Download Folder
AndroidFileHosting Folder
Google Apps:
http://goo.im/gapps
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 10.2 for the i9100.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.7.4 13.09 (kernel code) & linaro arm-linux-androideabi 4.8.2 13.09 (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?
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/
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
Raise the flasholism! Is linaro 4.8 stable for android ? https://github.com/dorimanx/Doriman...mmit/7a3fbb792919c406e146f6bb29c0c9054cfda61a
But let's flash and see
Btw what distro do u build on?
Verstuurd van mijn GT-I9100 met Tapatalk
Unexist6969 said:
Raise the flasholism! Is linaro 4.8 stable for android ? https://github.com/dorimanx/Doriman...mmit/7a3fbb792919c406e146f6bb29c0c9054cfda61a
But let's flash and see
Btw what distro do u build on?
Verstuurd van mijn GT-I9100 met Tapatalk
Click to expand...
Click to collapse
i'm using gcc linaro arm compiler 13.06/4.8 201306 at almost a month... NEVER gave me problems on my builds, and seems more smooth and battery friendly than the compiler that CM Jenkins buildbot uses.
running ubuntu 13.04 x64 / kernel 3.8.0-26
regards.
Any idea why Bluetooth audio routing to Mono devices (BT Mono for example) doesn't work on CM10.1? It used to work on CM10.
kokesh said:
Any idea why Bluetooth audio routing to Mono devices (BT Mono for example) doesn't work on CM10.1? It used to work on CM10.
Click to expand...
Click to collapse
no. sorry..
but, have you tried these:
Mono Bluetooh Router
&
Super BT Mono
give it a try.
What does this offer more than official cm?
Sent from my GT-I9100
lowrider82 said:
What does this offer more than official cm?
Sent from my GT-I9100
Click to expand...
Click to collapse
The main difference between these builds and the official ones, is that these builds are compiled using the GCC Linaro 4.8 201306 toolchain. Has been stated by users (and by myself) that this results in a smoother UI, and better battery usage..
also, check these two links:
http://www.linaro.org/linux-on-arm
http://en.wikipedia.org/wiki/Linaro
regards.
Giving this a try! I'll give you feedback =)
thanks for posting this, i'll use your build for the moment
but i have some questions for trying linaro on my own.
am i right, that one can follow these instructions?
https://wiki.linaro.org/Platform/Android/BuildSource
i'm asking, because they say it's linaro 4.4.X while you use 4.8
following this guide http://forum.xda-developers.com/showthread.php?t=1988315 we have to choose a specific toolchain and "use" it.
does this replace the official instruction
"Install Linaro tools
sudo apt-get install linaro-image-tools"
thank you for your help =)
PS: i'm also running latest (k)ubuntu 13.04.
its easy... try to follow this little tutorial i made.
open a shell and navigate to you root folder of your source tree, and then "prebuilts/gcc/linux-x86/arm/"
run: "wget http://releases.linaro.org/13.06/components/toolchain/gcc-linaro/4.8/gcc-linaro-4.8-2013.06.tar.bz2"
Run: "bunzip2 *.tar.bz2"
Run: "tar -xvf *.tar"
Open you file manager and navigate to the root folder of your source tree again.
Navigate To "/build", in your root folder.
run: gksudo gedit envsetup.sh
change the line in bold, got to look equal:
Code:
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-4.6/bin
;;
[B] arm) toolchaindir=arm/gcc-linaro-4.8-2013.06[/B]
;;
mips) toolchaindir=mips/mipsel-linux-android-4.6/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
save the file and reboot, you are done!
regards.
PS: Forget about apt package linaro-image-tools ... !
infected_ said:
The main difference between these builds and the official ones, is that these builds are compiled using the GCC Linaro 4.8 201306 toolchain. Has been stated by users (and by myself) that this results in a smoother UI, and better battery usage..
also, check these two links:
http://www.linaro.org/linux-on-arm
http://en.wikipedia.org/wiki/Linaro
regards.
Click to expand...
Click to collapse
Nice! I'll try this ROM later!
Would you recommend to flash another kernel? I'm using CM10.1 + custom Siyah kernel based
Strokesws said:
Nice! I'll try this ROM later!
Would you recommend to flash another kernel? I'm using CM10.1 + custom Siyah kernel based
Click to expand...
Click to collapse
yeah you can use a custom kernel. you have good options now:
Dorimanx 8.32/9.32 http://forum.xda-developers.com/showthread.php?t=1617219
KangBang 1.3 http://forum.xda-developers.com/showthread.php?t=2311448
Gustavo_S Siyah_CM based kernel build 0605 http://forum.xda-developers.com/showthread.php?t=2222843
My current favourite is KangBang 1.3, with "zzmove" governor, and "zen" scheduler ..
Regards.
Whats the difference between infected and unofficial from the 26nd?
Gesendet von meinem GT-I9100 mit Tapatalk 4
infected_ said:
yeah you can use a custom kernel. you have good options now:
Dorimanx 8.32/9.32 http://forum.xda-developers.com/showthread.php?t=1617219
KangBang 1.3 http://forum.xda-developers.com/showthread.php?t=2311448&highlight=aokp
Gustavo_S Siyah_CM based kernel build 0605 http://forum.xda-developers.com/showthread.php?t=2222843
My current favourite is KangBang 1.3, with "zzmove" governor, and "zen" scheduler ..
Regards.
Click to expand...
Click to collapse
I'm using Gustavo_S Siyah_CM based kernel build 0605. I prefer long battery life. Which is the best?
ArnomaF said:
Whats the difference between infected and unofficial from the 26nd?
Gesendet von meinem GT-I9100 mit Tapatalk 4
Click to expand...
Click to collapse
they are the same build, but because i changed buid.prop from "UNOFFICIAL" to "INFECTED", it was giving error on the md5sums, and some users asked me to upload "untouched" build, so the md5sum match up ..
Strokesws said:
I'm using Gustavo_S Siyah_CM based kernel build 0605. I prefer long battery life. Which is the best?
Click to expand...
Click to collapse
Like i said on my previous post, my current favourite is KangBang 1.3 + init.d scripts.. Gustavo_S kernel is also good, but its a bit outdated, now even more with new release of mali drivers.
Rom performs as good as any other nightly before, no issues, battery seems slighty better, I'll report at the end of my cycle, I'm curious about the usual ril crash after two days uptime, (memleak) b/c I hate reboots...
Well done @iNFECTED.:thumbup:
Tapatalked from my Galaxy SII
What's the difference between Your builds and Kalpik's build? Just asking.,
I asked Kalpik also.. hehe
i9100 OMNI ROM 4.4.2 LINARO/SABERMOD WEEKLY BUILDS
Nightly Build 4.4.2 20140213 is ONLINE
Build/Sync Date: Feb 13 2014 07h:xx GMT+00h:00 Lisbon
DOWNLOAD
(Goo.im - Main Mirror)
DOWNLOAD
(AFH - Backup Mirror)
(md5sum included with all builds)
HOMEPAGE
http://infectedbuilds.com
Kernel code compiled with linaro arm-eabi-4.7.4 201404 toolchain
ROM code compiled with sabermod arm-linux-androideabi-4.8.3 201404 toolchain
ROM FEATURES
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
sqlite fsync hack by dorimanx
white UI (following kitkat design)
Click to expand...
Click to collapse
CHANGELOG
https://changelog.omnirom.org/
https://gerrit.omnirom.org/#/q/status:merged+branch:android-4.4,n,z
Click to expand...
Click to collapse
These builds are hosted in my private account at MediaFire (purchased account - 120GB | no ads and really fast downloads!)
(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,
2x western wigital wd3200aaks raid 0 array, samsung f1 1tb, 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 16 "Petra" x64 3.13.1)
DONATIONS
Please consider helping with this project development and hosting, by giving a small donation...
http://infectedbuilds.com is almost complete. i will try to get it up and running at full throttle by the end of this week.
i will need to buy a new dedicated hosting service... looking into the ones users suggested.
you can check the progress made by webdev @Jflima at his github: https://github.com/Jflima92/Omni
so, please donate what you can, so this project goes forward, and keeps getting better, and better.
you can donate, using this link: DONATE
thank you all,
regards.
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from Omni Rom open-source code:
https://github.com/omnirom
latest linaro arm-eabi-4.7.4 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.3 to compile ROM code
Special Thanks
nims11, herna Omni Rom Dev Team
{
"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"
}
What is Omni ROM ?
Omni Rom Introduction
Omni Rom Homepage
Omni Rom Wiki
Omni Github
Omni Gerrit Code Review
Omni Bugtracker
Disclaimer
As you all know, every human being is responsible for their own action and reactions, so you are flashing this ROM on your own risk. I am not responsible for anything unexpected that happens to your device.
Downloads
i9100 Linaro/SaberMod Omni ROM NIGHTLY BUILDS
Gapps
Root Access
SuperSu
Installation Instructions
First Time User of Omni Rom
1. First of all download all 3 zip files and place them in your SD-card (Internal or external)
2. Backup of your current ROM
3. Wipe data/factory reset, wipe dalvik cache, wipe cache
4. Install zips from sd card, Omni ROM, Gapps and Super SU.
5. Reboot your device and wait until it boots, it might take some time to boot
- Already On Omni ROM
1. First of all download all 3 zip and put it in your SD-card (Internal or external)
2. Backup of your current ROM
3. Wipe system, wipe dalvik cache, wipe cache
4. Install zip from SD-card, Flash Omni ROM, Gapps and Super SU.
5. Reboot your device and you are good to go.
Working/Not Working
This are early nightly builds, so don't expect that everything will work as a stable release or have all the functions/options.
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of Omni Rom 4.4 for the i9100.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using latest linaro arm-eabi 4.7.4 (kernel code) & sabermod arm-linux-androideabi 4.8.3 (rom code) toolchain compilers
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/
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
I will trie. Can you add toggles to change?
Sent from my GT-I9100 using Tapatalk
Infected thanks for your build.
I wil try this rom and report
Sent from my GT-I9100 using xda app-developers app
Please add 'Known Bug List' (guess atm same as nims11 builds) - thanks.
Downloading... Seems to take its time.
Slim-4.3.1||i9100¬Tapa2
Antutu scores please (detailed)
How to install cm10.2 on this? When trying to flash, error appears
Mate, add gapps in the OP, and a little how to...
A lot of people are changing from Dalvik to ART, it would be good some info and problems about this...
rsimas said:
I will trie. Can you add toggles to change?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
code will be compiled as it is, from omni git. if they add toggles, then this builds will have toggles.
the only change for now, until i patch the build to compile the ROM code with linaro/sabermod, is the kernel code that's compiled with linaro arm-eabi 4.7.4 201310
Following thread. Hope OP gets updated with more details especially with what gapps to use. Or is anyone so kind there to spoonfeed me? Haha. And also guide me to be able to get ART working. Well, thanks a lot guys.
Sent from my GT-I9100 using xda app-developers app
./delete.sh
http://forum.xda-developers.com/showthread.php?t=2397942
infected_ said:
Just did a fast thread opening, and have to leave now. when i get home again, i'll arrange things better, and provably make a new build..
PS: gapps are the same used on nims11 builds, but i'll spoon-feed you guys..
GAPPS 4.4 (PA)
http://www.mediafire.com/folder/e68x4lsotd6xh/4.4
Info on pa's gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Ok, let's try.
Nice job, mate.
thanks man but for me i will wait for more feature merging in rom and then update to 4.4 ....:good:
some screenshots plz
Thanks. Working great for the moment.
ammarsg said:
thanks man but for me i will wait for more feature merging in rom and then update to 4.4 ....:good:
Click to expand...
Click to collapse
I'm also waiting for more features, particularly the toggles in notification drawer.
Sent from my GT-I9100 using Tapatalk 4
sidrocks89 said:
I'm also waiting for more features, particularly the toggles in notification drawer.
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
yes at least feature in 4.3.1 ....we look forward not backword
Mobile data didn't worked :what: but @nims11 build worked fine. I've tested both
Sent from my GT-I9100 using XDA Premium 4 mobile app
OP, 2nd post and 3rd post updated..
build 4.4 20131120 is compiling, i'll upload soon.
v500/G Pad 8.3" CYANOGENMOD 11 LINARO/SABERMOD NIGHTLY BUILDS
DOWNLOAD
(infected server)
(md5sum included with all builds)
CHANGELOG
http://www.cmxlog.com/11/v500/
kernel code compiled with linaro arm-eabi-4.7.4 201406 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201411 toolchain (self-compiled)
FEATURES
-O3 optimizations
strict-aliasing rules
custom performance flags
+30 cherry-picks used
original google kk ui (holo)
graphite
(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 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)
(Linux Mint 17 x64 "Qiana" 3.13.0-24)
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
latest linaro arm-eabi-4.7.x toolchain used to compile the kernel code & sabermod arm-linux-androideabi-4.8.x toolchains to compile ROM code
Special Thanks
CyanogenMod Dev Team = for the code sources.
Linaro Dev Team = for the arm-eabi toolchain
@sparksco = official 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"
}
[/CENTER]
XDA:DevDB Information
v500/G Pad 8.3 Linaro/Sabermod CyanogeMod 11 Builds, ROM for the LG G Pad 8.3
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP recovery
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-02-25
Last Updated 2014-07-28
Flashing Instructions
First time installing:
Flash CWM recovery or TWPR recovery.
Option #1 = http://forum.xda-developers.com/showthread.php?t=2588671
Option #2 = http://forum.xda-developers.com/showthread.php?t=2641409
Place build zip + gapps on internal/external memory
reboot into recovery
wipe /system /data /cache
flash build + gapps
wipe cache
reboot
you're done, enjoy!
Coming from previous build version:
Flash build, flash gapps
you're done, enjoy!
Small video with installation instructions (thanks to @Tomsgt)
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 11 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 boosted-tc arm-eabi 4.7.4 14.03 (kernel code) & boosted-tc arm-linux-androideabi 4.8.3 14.03 (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?
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/
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
Picking my G pad up tomorrow can't wait to get KitKat on it. Thanks so much to the devs that make all this happen. Would love to see some great kernels released (if there aren't already). Loving Franco linaro kernel on my N5. Does this ROM have any known bugs etc?
Sent from my Nexus 5 using XDA Premium 4 mobile app
alsheron said:
Picking my G pad up tomorrow can't wait to get KitKat on it. Thanks so much to the devs that make all this happen. Would love to see some great kernels released (if there aren't already). Loving Franco linaro kernel on my N5. Does this ROM have any known bugs etc?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
has far as i can tell, very few. same has original cm code. good for daily driver..
regards.
Removed.
Interesting. Signing in. I won't hop on the train just yet, though. Maybe next week
Removed.
can i update from cm11 offcial without data wipe if i have ART enabled ?
Nice to see some love from Portugal!!!
Uberzone said:
can i update from cm11 offcial without data wipe if i have ART enabled ?
Click to expand...
Click to collapse
yes, you should be ok, this was merged already. wipe caches, and has always, nandroid backup first, just in case.
regards.
Looping and timed out downloads...a,m on attempt no 10 now...any mirrors please?
Moe5508 said:
Looping and timed out downloads...a,m on attempt no 10 now...any mirrors please?
Click to expand...
Click to collapse
mirror added to OP.
regards.
Just got all set up all seems well, clean + snappy. About to enable art. Thank you for this build, it's only been a few min and I can see the performance difference from the official. :thumbup:
Sent from my LG-V500 using Tapatalk
build 20140226 is up on AFH, uploading to Goo.im..
regards.
Read from SD-Card
Does this build make it possible for 3 program to read from the sd-card (komix, pdf-reader, music, movieplayer). I think kitkat has a problem with it...
Booting the current build now (takes a while for art to optimize), one thing that's driving me crazy is the slow cm boot animation. Was that done on purpose? The circle spins faster on all other devices.
-VZW LG G2 VS980
annoyingduck said:
Booting the current build now (takes a while for art to optimize), one thing that's driving me crazy is the slow cm boot animation. Was that done on purpose? The circle spins faster on all other devices.
-VZW LG G2 VS980
Click to expand...
Click to collapse
Might this be the nerdiest feedback ever? The boot animation spinning too slow??
I tried mahdi for a very short while, I was satisfied with beanstalk, then I found this rom. Thank you.
android404 said:
Might this be the nerdiest feedback ever? The boot animation spinning too slow??
I tried mahdi for a very short while, I was satisfied with beanstalk, then I found this rom. Thank you.
Click to expand...
Click to collapse
Well, I gotta come up with something to complain about! I mention it because on my gs3 if the cm boot animation spun slow (like here) something bad was about to happen, like an unrecoverable sod.... It makes me anxious watching it!
Sent from my LG-V500 using Tapatalk
I lost root when I flashed this rom. Any idea why and if the normal root method will work again now that I'm on cm11?
Sent from my LG-V500 using xda app-developers app
{
"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"
}
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
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.
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 in attachment.
GAPPS
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
All gapps packages on the previous link, contain a backup script, so you dont need to flash them everytime you flash a new build.
Many thanks to @Deltadroid for these.
Sweet. Going to install in a bit.
Sent from my SM-N900V using Tapatalk
you may need to wipe /data for first install, i had to. and 5.0.2 gapps are compatible.
infected_ said:
you may need to wipe for first install, i had to. and 5.0.2 gapps are compatible.
Click to expand...
Click to collapse
Is this 5.1 r3?? Base on 4.2.2 or 4.4???
infected_ said:
you may need to wipe for first install, i had to. and 5.0.2 gapps are compatible.
Click to expand...
Click to collapse
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?
darksidesh007 said:
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?
Click to expand...
Click to collapse
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.
Works OK so far. I do get a Settings crash when pressing Sounds. Also noticed minor issue of AM/PM option for clock greyed out.
@infected_
This commit fixes the settings crash.
https://github.com/Euphoria-OS/andr...mmit/6285ecbfbf3ff95b33e02549d6defc00ede727d9
Deltadroid said:
@infected_
This commit fixes the settings crash.
https://github.com/Euphoria-OS/andr...mmit/6285ecbfbf3ff95b33e02549d6defc00ede727d9
Click to expand...
Click to collapse
thanks! will add it on next build.
infected_ said:
thanks! will add it on next build.
Click to expand...
Click to collapse
@Rick Roll deserves most (all) of the credit. He posted the link.
20150331 is up.
Downloading now. Just a suggestion, but maybe the download link in the OP go directly to the 12.1 folder.
Also, which boot is this based, 4.2.2 or 4.4.2? I'm on 4.2.2 and all seems fine.
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.
Cal said:
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.
Click to expand...
Click to collapse
How can dimming when booting to Recovery be relevant to any ROM you are using?
uzi2 said:
How can dimming when booting to Recovery be relevant to any ROM you are using?
Click to expand...
Click to collapse
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.
Another (minor) issue - While they fixed the FC for Sounds, the selections made do not stick with a reboot.
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?
I've been running it since the first nightly. I think it's great...Just very small issues which were resolved fast.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XPERIA SP/HUASHAN/C5303 PARANOID ANDROID 5.1 UNOFFICIAL SABERMOD BUILDS
LOLLIPOP 5.1.1_r8
BUILD 5.1 20151008 IS ONLINE.
DOWNLOAD
NOT WORKING YET: (?) YOU TELL ME.
ROM CODE COMPILED WITH LATEST SABERMOD ARM-LINUX-ANDROIDEABI 4.9.4 (20150926)
KERNEL CODE COMPILED WITH LATEST SABERMOD ARM-EABI 4.9.4 (20150926)
SOURCES:
kernel - https://github.com/infected-lp/android_kernel_sony_msm8x60/tree/saber
rom - https://github.com/infected-lp/android_device_sony_huashan/tree/pa_saber
[+] -O3 optimized (arm and thumb)
[+] strict-aliasing
[+] frame-pointers
[+] graphite flags
[+] LinkTimeOptimizations (-flto) flags
[+] cpu arch specific flags (armv7-a-neon)
[+] other flags to optimize even more the code.
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM SECOND POST
- NO MODS OF ANY SORT
BUILDBOT:
(intel core i7 3770k, asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl9, msi gtx 970, 1x samsung 850 evo 256gb + 1x samsung 128gb ssd 840 pro, 4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from AOSPA Legacy open-source code:
https://github.com/AOSPA-L
SPECIAL THANKS
AOSPA Dev Team = for the source code.
XDA:DevDB Information
XSP/C5303/Huashan/ Paranoid Android 5.1 Unofficial Sabermod Builds, ROM for the Sony Xperia SP
Contributors
infected_
Source Code: https://github.com/AOSPA-L
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest TWRP recovery
Based On: Paranoid Android
Version Information
Status: Nightly
Created 2015-10-07
Last Updated 2015-10-07
Reserved
HOW-TO:
* wipe/format /system /data /cache /dalvik.
* flash latest available build, and flash gapps.
* reboot and you're done.
ps: theres no need to flash SuperSU, ive integrated it on the builds.
GAPPS:
OpenGapps - http://opengapps.org/
Modular Gapps - http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Reserved
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of Paranoid Android 5.1 for the Xperia SP
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod arm-eabi 4.9.4 (kernel code) & sabermod arm-linux-androideabi 4.9.4 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
Click to expand...
Click to collapse
Source: http://elinux.org
What is SaberMod?
The term "SaberMod" is coming from:
the SaberMod project. Initially the project was used on SaberMod ROM for the Nexus 7 WiFi model (2013). This continued onto the Nexus 4 and Nexus 5 through help of user donations. The toolchains are based on GNU GCC 4.8, 4.9, and 5.0 with AOSP patches forward ported into GNU GCC. SaberMod also provides extra optimization features unlike Google’s toolchain, which gives options for a few amendments in the ROM itself to add more performance gains, such as graphite loop transformation optimizations. SaberMod tracks other utilities from GNU in the toolchain source components that are generally more up to date than AOSP or Linaro toolchains, and almost always tracks the development branches of GNU GCC for the latest patches and bug fixes. The toolchain ecosystem of SaberMod is very different from AOSP, using complex scripts to provide quick, up to date toolchains. Other toolchain sources like the AOSP based toolchain build repository have been heavily modified to work in favor of the way SaberMod toolchains are produced. I have approached some toolchain developers to ask a few questions.
Click to expand...
Click to collapse
Source: http://www.xda-developers.com/interview-with-developers-of-sabermod-hyper-toolchains/
Optimization Flags in GCC
What are flags?
For compilers such as GCC, flags are essentially options. A flag can enable or disable an option or feature that is used when compiling (building) code.
What are optimizations?
Optimizations, in the context of compiler flags, are flags that improve some aspect of the code, whether it be size, speed, memory use, and debugging, among other possibilities.
General Optimizations
These optimizations are basic flags in GCC, typically implemented into projects to improve an aspect of the final compiled code.
-O1: Optimization level 1, very basic optimizations, rarely used.
-O2: Optimization level 2, basic optimizations, most commonly used.
-O3: Optimization level 3, basic + experimental optimizations. Large performance boost, but can produce bugs.
-Os: Optimize for size. Most of the optimizations from levels 1 and 2, with extras added to decrease the size of code.
-Ofast: All Optimizations from levels 1, 2, and 3, with extra fast math optimizations.
Typically produces the most bugs, with a large performance gain.
-Og: No performance boost, optimizes the debugging experience, making errors and
warnings more informative to help developers.
-g0: Disables all extra debugging, usually makes code faster.
-fomit-frame-pointer: Removes frame pointers when they aren’t needed, streamlining the code.
-fipa-sra: Removes unused parameters/variables and replaces parameters with the called value, streamlining the code.
-fkeep-inline-functions: Emits static inline functions, even after they’ve been called.
-fmodulo-sched: Reorders instructions in loops in the most optimal way.
-fmodulo-sched-allow-regmoves: a more aggressive -fmodulo-sched, optimizing loops further by allowing register moves
-fgcse-sm: Moves stores out of loops to decrease the workload of loops.
-fgcse-las: Removes redundant loads after a store to reduce the workload.
-fgcse-after-reload: Removes redundant loads after a reload.
-funsafe-loop-optimizations: Optimize more by making assumptions, can create bugs from loops overflowing.
-fira-hoist-pressure: Decreases size of the code by evaluating register pressure for hoist expressions.
-fira-loop-pressure: Makes code smaller and faster by evaluating the register pressure of loops.
-DNDEBUG: Passes the variable for no debugging.
-flto: Enables link time optimizations (LTO) for improved library and executable performance.
Graphite Optimizations
Graphite is a project within gcc that uses the integer set library (ISL) and the chunky loop generator (CLooG) to improve memory use and optimize loops.
-fgraphite: Performs basic graphite loop and memory optimizations.
-floop-interchange: Switches two nested loops.
-floop-strip-mine: Splits a complex loop into a set nested loops.
-floop-block: Splits a loop into nested loops so that the memory fits into caches.
-fgraphite-identity: Creates a visual polyhedral representation of certain graphite optimizations. with some optimizations from ISL such as dead code removal.
-floop-nest-optimize: Optimizes the order of nested loops for data-locality and parallelism. This flag is experimental
-floop-unroll-and-jam: Enable unroll and jam for the ISL loop optimizer.
-floop-parallelize-all: Use graphite data to find and parallelize loops that can be.
Multithreading optimizations
Make code run in multiple jobs (threads) to use a multicore cpu to its fullest potential.
-ftree-parallelize-loops=n: Run parallelized loops is n number of threads.
-pthread: Use the posix thread system for multi-threading.
-fopenmp: Use the OpenMP thread system for multithreading. Tends to use less ram than posix.
Sanitizer Flags
These flags use libsanitizer for memory optimizations.
-fsanitize=leak: Sanitize memory leaks to reduce memory use
-fsanitize=address: Sanitize memory addresses to reduce memory use
-fsanitize=thread: Sanitize excess threads to reduce memory/cpu use. Only for 64bit.
Hardware Optimizations
These optimizations optimize code for the targets cpu, gpu, or ram.
-marm: Uses the ARM instruction set for executable code, improving performance.
-mthumb: Uses the Thumb2 instruction set, improving compatibility.
-mthumb-interwork: Improves compatibility between Thumb and ARM code.
-march=X: Optimizes code for your CPU’s arch, such as armv6, armv7-a, etc
-mcpu=X: Optimizes code for your specific CPU such as cortex-a15, cortex-a53, etc.
-mtune=X: Refer to -mcpu
-mfpu=X: Optimizes code for your CPU’s FPU such as vfpv3. vfpv4, neon, etc.
-mabi=X: Optimizes code ABI for your CPU, such as 32 or 64
Click to expand...
Click to collapse
Another reskined cm12.1
They even have the same exact bugs like lockscreen shows when locking the screen
DahakePL said:
Another reskined cm12.1
They even have the same exact bugs like lockscreen shows when locking the screen
Click to expand...
Click to collapse
the device sources are the same, and the github link is in OP... do you see any official SlimRom or AOSPA huashan official github repos anywhere?
and is also OP the purpose of these builds. and.. no one is forcing you to use them.
regards.
If you don't mind me asking, who's sources are you using to build this, Slim and the unofficial CM?
TheAvengingTITAN said:
If you don't mind me asking, who's sources are you using to build this, Slim and the unofficial CM?
Click to expand...
Click to collapse
Link is in OP.
regards.
Slimrom without sabermod (made by different user) feels different and it doesn't have lockscreen bug for example
So what's the matter?
DahakePL said:
Slimrom without sabermod (made by different user) feels different and it doesn't have lockscreen bug for example
So what's the matter?
Click to expand...
Click to collapse
what lockscreen bug? seems ok to me.
infected_ said:
what lockscreen bug? seems ok to me.
Click to expand...
Click to collapse
You can see the lockscreen for a second if you want to turn off the screen (old cm bug)
DahakePL said:
You can see the lockscreen for a second if you want to turn off the screen (old cm bug)
Click to expand...
Click to collapse
hm.. thats such a major bug, that i didnt even noticed until you said now.
regards.
ps: if you had the bug i have on leo with CM trees, while taking pictures, that you could really complain about.
@infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards.
flash- said:
@infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards.
Click to expand...
Click to collapse
That's what I'm talking about
flash- said:
@[HIDE]infected_ glad to see another one working on xsp ..but ur late a little bit to the party ...the thing that i can see is that ur source tree is from cm which is very old imo ...we had deves such as marcelo and adrian who worked on the device tree to fix a lot of problems and to make the source cleaner ...another member from this community made the slim lp with the developers kernel and source tree that i mentioned before ....as for cm and if i guessed right u should move to fixed source tree instead of cm poor one (for cm and slim lp ...idk if this applies to aospal) (if I'm not wrong )...useful links : 1...2...3
regards[/HIDE].
Click to expand...
Click to collapse
i asked permission at @darioj98 if i could use his kernel tree to make my sabermod builds. if i get a positive reply, ill continue with these builds.
regards.
infected_ said:
i asked permission at @darioj98 if i could use his kernel tree to make my sabermod builds. if i get a positive reply, ill continue with these builds.
regards.
Click to expand...
Click to collapse
That would be awesome because I love PA
allright, i got a reply from @darioj98
i have permission from @Adrian DC to use is m8x60 kernel, so expect updates and bug fixes soon on the saber builds.
i'll just wait for nxt build
Sent from my Xperia SP using XDA Free mobile app
alright.
new build is up, 20151008
new device and kernel trees used.
regards.
Hello, I want to know about performance. This Rom is suitable for daily use?
aumAP said:
Hello, I want to know about performance. This Rom is suitable for daily use?
Click to expand...
Click to collapse
its suitable for daily use.
performance is good, smoothness if awesome, and battery great. try it and report please
regards.