Hello everyone, sorry for my english I'm using google translate. I was able to compile the toolchain linaro 4.7.4 kernel 3.0.72 is that the whole of the AOSP rom from source Google Samsung Galaxy Nexus.
Kernel + ramdisk:
Kernel updated to: 3.0.72 (compiled with Linaro GCC 4.7.4-2013.06.26)
Compressed zImage – LZO
Disabled ro.adb.secure
Enable adb remount
Available I/O Schedulers: Deadline – CFQ – No-op
Available CPUFreq govenor: performance – powersave – userspace – ondemand – interactive – conservative – hotplug
Enabled CIFS support
Enabled NFS support
Enabled TUN support
Fix shell adb in standard GNU/Linux
Enabled Local Version
Enabled /proc/config.gz
Enabled extract config zImage
System:
AOSP Jelly Bean 4.3 build JWR66V (compiled with Linaro GCC 4.7.4-2013.06.26)
Installed busybox
The rom has no root, also lack the google apps, if you want you can install ClockworkMod recovery, the links at the bottom of the download.
Installation Guide:
Install the ClockworkMod Recovery
Download the rom and copy the zip on sdcard
Reboot into recovery, do wipe data / factory restore and flash it.
Download
- Galaxy-Nexus-4.3-linaro-odexed
- Galaxy-Nexus-4.3-linaro-deodexed
- Root SuperUser 1.51
- gapps-jb-4.3
Galaxy Nexus 4.3 compiled with toolchain linaro 4.7.4 with cflags -O3
Galaxy_Nexus_4.3_linaro_odexed_02
The rom odexed seems much smoother and faster, to increase the speed of the luncher, go to Settings - enabled Developer options - select scale window animation, transition and animator 0.5x.
Credits:
- Google Android Source
- Team Project Linaro
- EstebanSannin
If you like my rom thank me with a Donation
Guide for completing the sources linaro:
- You must have installed ubuntu 10.04 64-bit compilation but also goes with ubuntu 13.04 64-bit tested by me and the oracle java 6
- Download the source AOSP Android 4.3, the Android Developers website explains how to do
- Download the kernel sources of the Galaxy Nexus:
Code:
git clone https://android.googlesource.com/kernel/omap.git
cd omap
git branch -a (This command will list the various kernel versions)
master
* remotes/origin/android-omap-tuna-3.0-jb-mr2
remotes/origin/HEAD -> origin/master
remotes/origin/android-omap-3.0
remotes/origin/android-omap-panda-3.0
remotes/origin/android-omap-steelhead-3.0-ics-aah
remotes/origin/android-omap-tuna-3.0
remotes/origin/android-omap-tuna-3.0-ics-mr1
remotes/origin/android-omap-tuna-3.0-jb-mr0
remotes/origin/android-omap-tuna-3.0-jb-mr1
remotes/origin/android-omap-tuna-3.0-jb-mr1.1
remotes/origin/android-omap-tuna-3.0-jb-mr2
remotes/origin/android-omap-tuna-3.0-jb-pre1
remotes/origin/android-omap-tuna-3.0-mr0
remotes/origin/android-omap-tuna-3.0-mr0.1
remotes/origin/glass-omap-xrr02
remotes/origin/glass-omap-xrr35
remotes/origin/glass-omap-xrr64b
remotes/origin/glass-omap-xrr88
remotes/origin/linux-omap-3.0
remotes/origin/master
remotes/origin/sph-l700-fh05
git checkout remotes/origin/android-omap-tuna-3.0-jb-mr2 (choose the last updated version of the 3.0.72 kernel jelly beans)
git checkout -b remotes/origin/android-omap-tuna-3.0-jb-mr2
- Download the toolchain linaro 4.7-2013.07 (4.7.4) from here
- Set the variables to compile the kernel:
Code:
export ARCH=arm
export CROSS_COMPILE=/home/utente/Scrivania/Galaxy_Nexus/Toolchain-Linaro/arm-linux-gnueabi-linaro_4.7.4/bin/arm-unknown-linux-gnueabi-
make tuna_defconfig (This command will load the config gnexus)
make menuconfig (this command using a graphic interface you can select and load the modules in the kernel and change the configuration)
make (start compilation)
- To compile the source google AOSP, we have to download this toolchain linaro 4.7.4: http://snapshots.linaro.org/android/~linaro-android/toolchain-4.7-bzr/447/android-toolchain-eabi-4.7-daily-linux-x86.tar.bz2
- We extract and copy it in the folder: sorgenti-aosp/prebuilts/gcc/linux-x86/arm/ in this folder are the gcc toolchain to google, I do not to confuse it with the other folders called arm-linaro-4.7, now we just have to edit the file TARGET_linux-arm.mk which is located in the sorgenti-aosp/build/core/combo and let's change the name of the folder on TARGET_TOOLCHAIN_ROOT,
by this way:
Code:
# You can set TARGET_TOOLS_PREFIX to get gcc from somewhere else
ifeq ($(strip $(TARGET_TOOLS_PREFIX)),)
TARGET_TOOLCHAIN_ROOT := prebuilts/gcc/$(HOST_PREBUILT_TAG)/arm/arm-linux-androideabi-$(TARGET_GCC_VERSION)
TARGET_TOOLS_PREFIX := $(TARGET_TOOLCHAIN_ROOT)/bin/arm-linux-androideabi-
endif
in this way:
Code:
# You can set TARGET_TOOLS_PREFIX to get gcc from somewhere else
ifeq ($(strip $(TARGET_TOOLS_PREFIX)),)
TARGET_TOOLCHAIN_ROOT := prebuilts/gcc/$(HOST_PREBUILT_TAG)/arm/arm-linaro-$(TARGET_GCC_VERSION)
TARGET_TOOLS_PREFIX := $(TARGET_TOOLCHAIN_ROOT)/bin/arm-linux-androideabi-
endif
Once this is done you can start filling out the following site guides android source
Command to compile the AOSP rom odexed:
Code:
make DISABLE_DEXPREOPT=false WITH_DEXPREOPT=true
Oh I forgot before he ends up filling in the system you have to copy the folder that is created out of the blob proprietary Galaxy Nexus that you can take from your stock rom 4.3, otherwise the rom will not boot.
News:
I recompiled the rom with the cflags -O3, to set it in the sources I have modified the file TARGET_linux-arm.mk by so:
Code:
TARGET_arm_CFLAGS := -O2 \
-fomit-frame-pointer \
-fstrict-aliasing \
-funswitch-loops
# Modules can choose to compile some source as thumb.
TARGET_thumb_CFLAGS := -mthumb \
-Os \
-fomit-frame-pointer \
-fno-strict-aliasing
in so:
Code:
TARGET_arm_CFLAGS := -O3 \
-fomit-frame-pointer \
-fstrict-aliasing \
-funswitch-loops
# Modules can choose to compile some source as thumb.
TARGET_thumb_CFLAGS := -mthumb \
-O3 \
-fomit-frame-pointer \
-fno-strict-aliasing
I first tried to compile the rom exporting only the variables:
Code:
export CFLAGS="-O3 -pipe"
export CXXFLAGS="-O3 -pipe"
before giving the command make, but I was not sure so compiled with cflags -O3 , the compilation is completed without error but I have not tried the rom.
Compiling with the change to the file TARGET_linux-arm.mk[/ B] is finished without errors, the system.img who created me is 259.1 Mb, instead system.img with the export of cflags is 250 Mb, the same size as the system.img that I compiled without the cflags -O3, so I think that with the changes to the file are able to compile the cflags -O3, I just have to try the rom and take tests benchmark to see if the rom has been optimized and is smoother and faster.
I did some benchmark tests with Antutu on rom compiled with the cflags -O3, with freq to 1200 and governor performance did score of 7830, higher than the rom compiled without cflags -O3 and stock rom.
thanks bro.. i'm limited to 8 thanks per day.. i will thank you tomorrow
:thumbup:
Does this work with Linaro 4.8 ? I tried it and it wouldn't compile !
Shyam
I tried to compile the kernel with only 4.8 linaro but it is unstable and is across reboot
i have galaxy nexus with team win on it (and rooted) today i got the 4.3 jellybean update OTA, but when i click install, the phone restarts and go to team win, from there what are the steps to get the update? TNX
Sent from my Galaxy Nexus using xda app-developers app
homedog said:
i have galaxy nexus with team win on it (and rooted) today i got the 4.3 jellybean update OTA, but when i click install, the phone restarts and go to team win, from there what are the steps to get the update? TNX
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I don't think a rooted GNex can be updated through OTA. You better download the flashable zip of the stock rom and flash it through recovery, or you can download the image file from the source and flash it through fastboot.
XPERIA Z1/HONAMI/C6903 PARANOID ANDROID 4.5 LINARO/SABERMOD WEEKLY BUILDS
4.5 BETA 2 is ONLINE
Build/Sync Date: Ago 13 xxh:xx GMT+1 Lisbon
DOWNLOAD
(infected server)
(md5sum included with all builds)
CHANGELOG
http://forum.xda-developers.com/showthread.php?p=54620455
HOMEPAGE
http://infectedbuilds.net
kernel code compiled with linaro arm-eabi-4.9.1 201407 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 201407 toolchain
FEATURES
-O3 optimizations (ROM and kernel code)
strict-aliasing rules
custom performance flags (ROM and kernel code)
+30 cherry-picks used
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 wigital wd3200aaks raid 10 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 17 x64 "Qiana" 3.13.0-24)
DONATIONS NEEDED
Disclaimer:
These builds are freshly compiled/synced from AOSPA Legacy open-source code:
https://github.com/AOSPA-legacy
latest linaro arm-eabi-4.9.1 toolchain used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchain to compile ROM code
Special Thanks
AOSPA Legacy 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"
}
XDA:DevDB Information
Z1/HONAMI/C6903 Linaro/Sabermod Paranoid Android Legacy (AOSPAL) 4.4x Builds, ROM for the Sony Xperia Z1
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: AOSPAL
Version Information
Status: Stable
Current Stable Version: 4.44
Stable Release Date: 2014-07-24
Created 2014-07-24
Last Updated 2014-08-13
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blue led)
- fastboot flash boot boot.img (extract boot.img from an official AOSPAL honami build zip or these builds)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of AOSPA Legacy for the Xperia Z1/Honami/C6903
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.07 (kernel code) & sabermod arm-linux-androideabi 4.8.4 14.07 (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
first
wow new rom i must try it
---------- Post added at 03:45 PM ---------- Previous post was at 03:15 PM ----------
install finito
start with Rom now i write feedback later
Thx , but is there anything different from the old AOSPAL we have here ?
iiD4x said:
Thx , but is there anything different from the old AOSPAL we have here ?
Click to expand...
Click to collapse
yes. these builds are cross-compiled with custom toolchains, instead of google gcc 4.6 & 4.7 "stock" ones... the gcc toolchains that can be used are linaro, sabermod, and boosted... compiling using latest gcc versions 4.8/4.9, using -O3 optimizations, strict-aliasing, and other performance/optimization flags, results in the advantages described on the third OP.. smoother, faster, and more battery friendly builds...
try it, and them give feedback...
any doubt, feel free to ask.
regards.
infected_ said:
yes. these builds are cross-compiled with custom toolchains, instead of google gcc 4.6 & 4.7 "stock" ones... the gcc toolchains that can be used are linaro, sabermod, and boosted... compiling using latest gcc versions 4.8/4.9, using -O3 optimizations, strict-aliasing, and other performance/optimization flags, results in the advantages described on the third OP.. smoother, faster, and more battery friendly builds...
try it, and them give feedback...
any doubt, feel free to ask.
regards.
Click to expand...
Click to collapse
Lol, Official AOSPAL we have here using latest SaberMod toolchain also..
OPTIMIZATION:
Offical SaberMod toolchain (GCC 4.8 for ROM , 4.9 for Kernel)
Strict-aliasing enabled
Memory optimization flags
Graphite
Click to expand...
Click to collapse
i dont mean anything, but we already have it OFFICIAL for honami.
iiD4x said:
Lol, Official AOSPAL we have here using latest SaberMod toolchain also..
i dont mean anything, but we already have it OFFICIAL for honami.
Click to expand...
Click to collapse
you must be mixing things up... Paranoid Android (AOSPA) uses google toolchains.. just check manifests.
Paranoid Android Legacy (AOSPAL) also uses google toolchains... check manifests.
Paranoid Saberdroid (AOSPAL also), i dont give a dime what they use...
i told to try ROM first...
regards.
Been waiting for this Thread.. Superlike
Sent from my Xperia Z1 using Tapatalk
Is there any disadvantage of this over the official one?
Blegh said:
Is there any disadvantage of this over the official one?
Click to expand...
Click to collapse
This will be faster
Blegh said:
Is there any disadvantage of this over the official one?
Click to expand...
Click to collapse
quite the opposite.. run for half a day with stock PA, then run the other half of the day with a PA linaro/sabermod build.
you can flash each on top of another and vice-versa.
You'll see the differences..
When I've flashed the boot.img from CM11 and try to access my sdcard from recovery I get the following error:
E: Can't mount /storage/sdcard1
Any idea on how to solve this?
Thanks
siwan05 said:
when i've flashed the boot.img from cm11 and try to access my sdcard from recovery i get the following error:
E: Can't mount /storage/sdcard1
any idea on how to solve this?
Thanks
Click to expand...
Click to collapse
Try flashing the boot.img from this rom zip
abbychauhan said:
Try flashing the boot.img from this rom zip
Click to expand...
Click to collapse
yeah.. i need to change 2nd post instructions according to AOSPAL..
You might want to change the tag to AOSPA as AOSPAL is the name for Paranoid SaberDroid. It is kinda misleading IMO.
There's new build 26 July
Sent from my Xperia Z1 using Tapatalk
if @infected_ would be kind enough to give changelogs then it would be batter
Though new build working Superb
7sen said:
There's new build 26 July
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
abbychauhan said:
if @infected_ would be kind enough to give changelogs then it would be batter
Though new build working Superb
Click to expand...
Click to collapse
there isn’t any.. its same 4.44 build, but i only added extra cpu governors and i/o schedulers... sure there were things merged, you can check gerrit ..
its an untested build. don’t have time to do it atm...
infected_ said:
there isn’t any.. its same 4.44 build, but i only added extra cpu governors and i/o schedulers... sure there were things merged, you can check gerrit ..
its an untested build. don’t have time to do it atm...
Click to expand...
Click to collapse
it's perfect build i installed with fresh install :good: and now it's good with all cpu governors :angel: