Develop Bugs

[GUIDE] Compiling AOSP with gcc4.6

The move to gcc4.6 in many new Linux distros broke compilation of AOSP 4.0.3 and earlier. These branches were frozen with support for only gcc4.4, and the official word from Google is that only the master branch contains the fixes that enables it to build with gcc4.6, and to build 4.0.3_r1 we have to go all the way back to for example Ubuntu 10.04. But I found that it only takes a few minor fixes to get the non-master branches of AOSP to compile with gcc4.6. I made a few changes that let me compile AOSP 4.0.3_r1 on 64-bit Ubuntu 11.10, which I'm attaching in case anyone else was having the same problems I was. Note that this patch will only work with a fresh clone of AOSP 4.0.3_r1.

Chirality said:
The move to gcc4.6 in many new Linux distros broke compilation of AOSP 4.0.3 and earlier. These branches were frozen with support for only gcc4.4, and the official word from Google is that only the master branch contains the fixes that enables it to build with gcc4.6, and to build 4.0.3_r1 we have to go all the way back to for example Ubuntu 10.04. But I found that it only takes a few minor fixes to get the non-master branches of AOSP to compile with gcc4.6. I made a few changes that let me compile AOSP 4.0.3_r1 on 64-bit Ubuntu 11.10, which I'm attaching in case anyone else was having the same problems I was. Note that this patch will only work with a fresh clone of AOSP 4.0.3_r1.
Click to expand...
Click to collapse
I haven't tried your fix yet, but if it works like you said, thanks a lot for putting this out !

[kernel][For CM7 only][LAZY,TUN,CIFS,ondemand tweaks]Adam's kernel[02/10/2012]

Hi guys.
I'm a newbie about compiling kernel,and this is my personal compiled kernel based on Hashcode's git source( stock branch),also with some tweaks which I think can improve the responsiveness without bringing extra power consumption( or as little as possible).
This kernel will also be my testing platform to do some MOD porting from Ezekeel's GLaDOS kernel.
Thanks to all great developers in XDA , especially:
-Hashcode & intersectRaven : for their git repo alone with a working .config. alone
-Ezekeel : for his so many great MODs on Nexus S(my phone) and Galaxy Nexus(will be my next phone)
-whistlestop : For his improvement on CM7 (I'm completely unfamiliar with the user land things about android, without him I'll be still using the stock ROM)
Features:
-LAZY cpufreq governor ported from GLaDOS(http://forum.xda-developers.com/showthread.php?t=1276092) with some tweaks.
-TUN compiled into kernel (especially important for people living in regions with strict network censorship like CHINA! F*ck the GreatFireWall)
-CIFS compiled into kernel along with NLS-utf8 for non-ASCII characters.( Now who cares the size of the internal flash?)
-Minor tweaks on ondemand governor to improve responsiveness.
ToDo:
-BLX porting from GLaDOS(http://forum.xda-developers.com/showthread.php?t=1257497)
-TouchWake porting from GLaDOS(http://forum.xda-developers.com/showthread.php?t=1239240)
Because I'm a newbie on kernel development and the MODs above both have some code in hardware drivers, so it will be a long time before accomplish.
The kernel source code seems to work on both CM9 and stock ROM.
So later I'll upload the flashable kernel zip for CM9 and stock ROM after some test.
Download:
CM7:http://www.mediafire.com/?2nsm9lb7ylm3gnl
In next post,I'll post the procedure for compiling the kernel and the wifi driver.

In this post I'll post the detailed procedure of compile the kernel.
1.Get the kernel source and wifi driver:
If you want to compile the kernel based on my tweak,
you can use my repo (fork from hashcode's source):https://github.com/adam900710/kernel_omap(branch stock)
Or you can just start from scratch without my tweak:https://github.com/KFire-Android/kernel_omap(only branch stock is tested)
If you are unfamiliar with git,you can learn it on the GitHub's help page:
http://help.github.com/
Tiwlan drivers from neither omapzoom nor CM7 works due the lack of given functions.
ONLY the wifi driver from Amazon seems work. So you need to download the whole zip from Amazon:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
The wifi driver locates in mydroid/hardware/ti/wlan/wl1283
2.Get the cross compile toolchain:
Yes,you can build from scratch according to CLFS(http://trac.cross-lfs.org/),but a newbie like me is glad to use the pre-compiled toolchain like sourcery G++. Omappedia recommanded 2010q1-202(https://sourcery.mentor.com/sgpp/lite/arm/portal/release1293), so I use it as the toolchain and it works well.
The self-extrated installation program will install the toolchian without any problem.
Also other toolchain is available like linaro , but according to the post by Ezekeel (http://rootzwiki.com/topic/10855-researchmythbuster-optimized-compiler-toolchains/) , there seems no obvious difference. So the out-of-box sourcery G++ is a good choice.
3.Compile the kernel.
Code:
cd kernel_omap #cd into your kernel
make mrproper #clean the source tree( normally you can skip)
make otter_android_defconfig #get the default .config (also you can copy it manually)
make ARCH=arm menuconfig #if you want,you can tweak the config of the kernel.This needs headers of ncurse
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi -j4 #you should make sure that the toolchain is in you PATH
After some CPU time, the kernel is built, in arch/arm/boot/zImage. Also the modules is built in other places.
Since I built all TUN/CIFS and so on into kernel,so there is no need to install the modules.
4.Compile the wifi driver:
Code:
cd mydroid/hardware/ti/wlan/wl1283/platforms/os/linux/ #cd into the building folder
make ARCH=arm KERNEL_DIR=/home/adam/kernel_omap CROSS_COMPILE=arm-none-linux-gnueabi- TNETW=1273 -j4 #you need to change the path of KERNEL_DIR
CAUTION: DO NOT add DEBUG=n OR DELETE TNETW=1273....
I don't know why,but if you do so,the wifi driver won't work properly.
5. Package the kernel into boot.img with ramdisk.
Thanks to DooMLord , in his git repo , you can download the tools needed.
https://github.com/DooMLoRD/Kindle-Fire-Kernel/tree/master/final_files
Only minor changes are needed for the path ,every thing elso works fine.
You can use the ramdisk extracted from any CM7 boot.img using the perl script.
Then just ./make_bootimg will do everythin for you.

Great i will test it
Sent from my GT-P1000 using xda premium

Best kernel.
I'm running on CM7 with this kernel and get super-perfomance and perfect power consump (Using Lazy governor).

It's not support OC??
Sent from my GT-P1000 using xda premium

acax456 said:
It's not support OC??
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Sorry, not support yet.
Maybe I'll add OC in next release.But I don't recommend OC because the power consumption...

can you able otg usb support ???
is this possible

Please add .zip for CM9!

Can I flash this from the recovery? or do I have to use adb??

please.update your kernel.since its been two months from last.update
Sent from my GT-P1000 using xda premium

[KERNEL][SOURCE][android_kernel_lge_msm7x27-3.0.x (3.0.8)]

I waited to post this over here until it was debugged and all the hardware works.
Even though this forum's been kinda dead quiet for a while, xda gets searched and I want this source code out there.
Derived from androidarmv6 project and tweaked over to thunderc from the p500 developers' awesome work getting it running on the Optimus One.
source:
https://github.com/bigsupersquid/and...7x27-3.0.x.git
(branch squid, for lack of imagination.)
make thunderc-test_defconfig
you'll want to change or remove the toolchain path in the config. it is highly unlikely that your cross toolchain is in the same path as mine.
I set it in the config to avoid having to add "CROSS_COMPILE=/blah/blah/etc" to the make command every time I rebuild the kernel.
it is for jellybean and kitkat roms.
use on older android versions messes up various things. Especially USB.
it conflicts with /sbin/chargerlogo or /sbin/charger for offline charging and bootloops unless that file is removed.
Use the attached removecharger.zip in recovery with signature verification off for that if you don't want to edit the ramdisk yourself.
md5sum b1a9f21285e09e06dc94422a8578dc98
enjoy

@bigsupersquid Know if anyone's willing to have a stab at building Firefox OS, now with the 3.x kernel?
EDIT: Well apparently there's no full ArmV6 support in it so, I guess not...

[ROM][KK][4.4.4][LINARO/SABERMOD] CyanogenMod 11 [NIGHTLY BUILDS]

Z1/HONAMI/C6903 CYANOGENMOD 11 LINARO/SABERMOD NIGTHLY BUILDS
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.9.1 2014.07 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 2014.07 toolchain
FEATURES
-O3 optimizations (ROM & Kernel code)
strict-aliasing rules
custom performance flags (ROM & Kernel code)
+30 cherry-picks used
Original Android KitKat UI (holo)
graphite
extra governors and schedulers
CHANGELOGS
(check build/sync date and compare)
http://www.cmxlog.com/11/honami/
http://changelog.bbqdroid.org/#/honami/next
(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)
HOMEPAGE
http://infectedbuilds.net
DONATIONS
if you can, please make a small donation... it will help with my work on these builds, keep website and dedicated server up and running, so i can deliver fast and unlimited downloads, and host the builds.
many thanks,
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
latest linaro arm-eabi-4.9.1 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchains to compile ROM code
Special Thanks
CyanogenMod Dev Team = for the source code
Linaro Dev Team = for the fresh linaro toolchains
Linaro Dev Team = linaro toolchain
@kecinzer = sabermod toolchains
@Cl3Kener = for the fresh linaro/sabermod toolchains
@aznrice2k4 = for the always fresh boosted toolchain​
XDA:DevDB Information
Z1/Honami/C6903 Linaro/Sabermod CyanogeMod 11 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
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-07-05
Last Updated 2014-07-24

Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- 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 CyanogenMod ROM 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.05 (kernel code) & sabermod arm-linux-androideabi 4.8.3 14.05 (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/
What is graphite?
Graphite has been around for a while in GCC. During this time a lot of people tested Graphite and Sebastian fixed many bugs. As of today the Graphite infrastructure is pretty stable and hosts already specific optimizations such as loop-interchange, blocking and loop-flattening.
However, during the development of Graphite we also found areas where we are still way behind our possibilities. First of all we realized that the use of a rational polyhedral library, even though it provides some functionality for integer polyhedra, is blocking us. Rational rational polyhedra worked OK for some time, but we have now come to a point where the absence of real integer polyhedra is causing problems. We have bugs that cannot be solved, just because rational polyhedra do not represent correctly the set of integer points in the loop iterations. Another deficit in Graphite is the absence of a generic optimizer. Even though classical loop transformations work well for certain problems, one of the major selling points of polyhedral techniques is the possibility to go beyond classical loop transformations and to forget about the corresponding pass ordering issues. Instead it is possible to define a generic cost function for which to optimize. We currently do not take advantage of this possibility and therefore miss possible performance gains. And as a last point, Graphite still does not apply to as much code as it could. We cannot transform a lot of code, not only because of the missing support for casts (for which we need integer polyhedra), but also because of an ad hoc SCoP detection and because some passes in the GCC pass order complicate Graphite's job. Moving these road blocks out of the way should increase the amount of code we can optimize significantly.
Click to expand...
Click to collapse
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

Downloading. Will install later. Loved infected builds on i9100

this what i need for my phone :angel:
download and install now

One more great rom, will download it and try it when im on pc ^_^, thks dev.
Sent from my C6903

Another awesome Dev from i9100!, gonna try this rom soon
Sent from my C6903 using XDA Free mobile app

screens showing toolchains used on the build, are in attachment.
regards.

install finito
Screen flow like mercury
smooth and fast as F hell :laugh:
love the heads up :angel:
keep up man :good:

check this out better camera app
http://forum.xda-developers.com/goo...ps/app-cameranext-one-plus-one-cm11s-t2730715

The update check in settings is from CM or from your server? In other words to update and stay infected we must check in the settings or we have to check manually from the link? Really fast rom by the way!

if possible, please let me know about the battery life , im really curious
I would test it myself but I have too much crap on my phone that needs to be saved and cleared out
regards

ilmorga said:
The update check in settings is from CM or from your server? In other words to update and stay infected we must check in the settings or we have to check manually from the link? Really fast rom by the way!
Click to expand...
Click to collapse
If you use the in-built CM Updater, you will end up with official CM nightly, and not linaro/sabermod build.
hassanman1997 said:
if possible, please let me know about the battery life , im really curious
I would test it myself but I have too much crap on my phone that needs to be saved and cleared out
regards
Click to expand...
Click to collapse
battery is good.
i will try to fix a commit merge error, and add some extra governors and schedulers from a hammerhead kernel, so we can play a bit with them..

battery is good
19% for= 4 hours 1 hour sccren on wifi on 2g
it's really good

Thank you, ill try this rom ASAP :laugh:

Finally, Infected_ builds for Honami

Thanks for the awesome work..

e30luismi said:
pimped kernel work?
Click to expand...
Click to collapse
tried the latest regular and light version, both of them dont work.

e30luismi said:
pimped kernel work?
Click to expand...
Click to collapse
infected_ said:
tried the latest regular and light version, both of them dont work.
Click to expand...
Click to collapse
Actually not a ROM problem.. Pimped kernel needs updation

abbychauhan said:
Actually not a ROM problem.. Pimped kernel needs updation
Click to expand...
Click to collapse
yeah... i know its not a ROM problem...

[Toolchain] UberTC optimized for A8 & A9 [GCC 4.9 to 6.0]

UberTC optimized for A8 & A9​
This is basically UberTC toolchain built for A8 and A9 CPUs.
If you don't know what a toolchain is made for don't post here please
Note that i haven't tested A9 builds. If you find any bug, feel free to post it here.
Downloads: https://bitbucket.org/Coldwindofnowhere/
All credits goes to @Cl3Kener
Contributors
 @Cl3Kener
Source: https://github.com/UBERTC/
Version Information
Status: Stable
Created 2015-11-09
Last Updated 2015-11-09

Which version should i choose ? ​
- Use A8 version if you want to build for any Cortex-A8 based device : i9000 (and all of it's variants), i9001, ...
- User A9 version if you want to build for any Cortex-A9 based device : i9100, i9300, i9305, ...
How to use this toolchain for your builds ?​
Add this to your local manifest (for arm-eabi 4.9 with A8 optimisations)
Code:
<remote fetch="https://bitbucket.org/" name="bitbucket" />
<project name="Coldwindofnowhere/arm-eabi-4.9-cortex-a8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" remote="bitbucket" revision="master" />
(I will add more stuff later)

Reserved

Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?

gsstudios said:
Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?
Click to expand...
Click to collapse
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.

Coldwindofnowhere said:
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.
Click to expand...
Click to collapse
Sure, I'll try building with your toolchain builds on the s2. I'm pretty sure that the differences will be minor, considering how great the toolchain is even without any tuning at all.
thanks, gsstudios
Edit: Please disregard what I've just said. Don't have time due to commitments to exams. Maybe sometime later this week I will be free.

I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.

Coldwindofnowhere said:
I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.
Click to expand...
Click to collapse
Yup i'd like to try the A9 ones for eabi 6.0 if possible

aaz03 said:
Yup i'd like to try the A9 ones for eabi 6.0 if possible
Click to expand...
Click to collapse
Sure, i'll build it in a bit.
Edit : uploaded, tell me if you face any issues.

Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?

djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.

Coldwindofnowhere said:
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.
Click to expand...
Click to collapse
Thanks! The same error is also in UberTC from https://bitbucket.org/UBERTC
What build system do you use? Standard Omni build system or some other?

djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Umm, what compiler flags are you using ?

Coldwindofnowhere said:
Umm, what compiler flags are you using ?
Click to expand...
Click to collapse
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .

djkoloda said:
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .
Click to expand...
Click to collapse
Compiling without these flags has not given results. I tried to arm-linux-androideabi-4.8 UberTC instead of that of the Omni and everything compiled.