Related
So I pretty much would like to start building my own kernels and Roms from AOSP, but not sure where to start. I have downloaded the SDK already, and started downloaded some file with git and these commands:
git clone https://android.googlesource.com/kernel/omap
cd omap
git checkout origin/android-omap-tuna-3.0-mr0
but the guides I've been reading don't offer much more help. And then there is a toolchain of some sort? I can get my way around linux fairly well and have built my own kernels about a year and a half ago for my Vibrant, but took a completely different course.
Was wondering if someone could point me in the right direction, thanks!
You're on the right track. Use Linux ubuntu, install all the packages, the Android tool chain, then just clone the aokp kernel like you showed. But you had the wrong repo link. Go to team kangs github page, go to the nexus kernel, then at the top will be their git link in a box.
Git clone "link"
Then just run the make command in terminal. Make sure you navigated yo the downloaded kernel folder.
RogerPodacter said:
You're on the right track. Use Linux ubuntu, install all the packages, the Android tool chain, then just clone the aokp kernel like you showed. But you had the wrong repo link. Go to team kangs github page, go to the nexus kernel, then at the top will be their git link in a box.
Git clone "link"
Then just run the make command in terminal. Make sure you navigated yo the downloaded kernel folder.
Click to expand...
Click to collapse
Thanks a lot, will try that. The link on their page is AOSP?
Sent from my Galaxy Nexus using XDA
The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250
bk201doesntexist said:
The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250
Click to expand...
Click to collapse
Sweet will continue with these steps and look onto the merge
Sent from my Galaxy Nexus using XDA
bk201doesntexist said:
The guy is asking us on how to clone AOSP tuna kernel tree, and you tell him to clone teamKang kernel project?
@op, no, you dont have the incorrect url. Clone from there, then checkout branch android-omap-3.0.
Type:
'make tuna_defconfig'
'make -j4'
You'll then have a zimage in arch/arm/boot, which you'll need to merge with a compatible ramdisk (either by fastboot or manually).
sent from my i9250
Click to expand...
Click to collapse
Oh holy crap haha I completely thought he asked about aokp kernel, my bad I didn't read.
AOSP kernel for HTC Explorer/Pico
Can you tell me how to build aosp kernel for htc explorer?
monishvster said:
Can you tell me how to build aosp kernel for htc explorer?
Click to expand...
Click to collapse
Just do the same thing, but instead sync the htc kernel rather than the nexus. Go search and find out if source code has been released for that phone.
Then just run the make command.
Somebody call 911, we've been hijacked
Note: 'make tuna_defconfig' is for maguro, i dont know what is the name of default config file for the htc, why should we? User should refer to htc explorer subforum @xda or to kernel documentation.
Sent from my i9250
so, already compiled some times GB kernel, easy, just command make and everything works fine
but i'm interested in compiling jb kernel.
already git clone kernel 2.3.6, git checkout jb 2.3.6
but i cant compile, already sudo sh extract-files and setup-makefile, the only thing that it does is pushing the files from adb to a dir.
also, itt new guide for compile kernel
any help in compiling the kernel from source.
any help would be appreciated
regards
zezadas said:
so, already compiled some times GB kernel, easy, just command make and everything works fine
but i'm interested in compiling jb kernel.
already git clone kernel 2.3.6, git checkout jb 2.3.6
but i cant compile, already sudo sh extract-files and setup-makefile, the only thing that it does is pushing the files from adb to a dir.
also, itt new guide for compile kernel
any help in compiling the kernel from source.
any help would be appreciated
regards
Click to expand...
Click to collapse
i use thishttp://forum.xda-developers.com/showthread.php?t=1966751 as my guide for building the kernel also this one http://forum.xda-developers.com/showthread.php?t=
Sent from my GT-I8150
This is DIY
If you are just looking for a well done and stable PA download, you are probably the wrong place. Then go and grab xzzz9097s build, it's good!
If you are impatient and know what to do, just leave and do the init/sync/build.
For anyone wanting to build her/his own PA without any "extras", go ahead and read on.
We already have a very easy full guide to compile CM10 for HOX. I was looking for the same for ParanoidAndroid, but did not find a 100% guide, meaning I had to do it myself.
To be fair, I only needed to do 1% as you will see after the usual disclaimer. I hope this little guide will be enough to make anyone complile their own PA for the HOX.
The usual disclaimer:
I am no developer!
I just happen to be able to read and understand instructions. I am persistent and know how to search for answers.
With luck and patience I ended up with a 184MB zip, that installs and runs just fine on my HOX.
I pass this guide as it is now, no guarantee no returns. I will probably not be able to help much here, time is very limited, so no commitments for support from me.
If it breaks you device, you broke it all by yourself
I am no developer!
gokussjx made the general guide, explaining how to port Paranoid Android 3.xx to different devices.
It works 99% for Endeavoru. The last 1% takes some effort to get right.
For me, not knowing what I am doing, it took a lot of trial and error, but eventually, - I made it and might as well pass it on here.
I'm in debt to all the people helping out in that thread. Huge thanks!
To get started, just follow a few simple steps:
You need a linux setup.
Install as your main system or run it in windows with VirtualBox.
Most guides are expecting Ubuntu. I use Mint Debian 64, which is just perfect for this job (and everything else ).
For VirtualBox you need at least a 50GB virtual-drive. Add 16GB if you will use ccache. I have build PA with a 52GB VBox in Win7.
It was just enough to compile, but had no room for ccache!
Compile time (VBox) on EliteBook 8540w (i7) was 120min. Not too bad, considering my old DeskTop need close to 4 hours on pure Linux.
Expect to download 8GB of source. Add 18GB for building to the "out" folder.
Enough statistics now, let's get started.
Follow gokussjx guide to setup linux for PA compiling.
Follow only these steps:
# Install OpenSSL, for Python
# Install Dependencies
# Configure USB
# JAVA JDK Installation
# Python Installation (just pick option 1)
# Android SDK
Click to expand...
Click to collapse
Exit gokussjx guide and continue here:
Download your favorite arm toolchain:
I found mine here.
Just extract the archive to any folder with user access, later you will point the build system to the /bin folder of the toolchain.
Install CCACHE:
Code:
$ sudo apt-get install ccache
Activate it in .bashrc:
Code:
# use ccache
export USE_CCACHE=1
You can change max-cache size, 16G should be enough for this build.
From terminal:
Code:
$ ccache -M 16G
Install Repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Download the build manifest:
Code:
$ mkdir -p padroid/system
$ cd padroid/system
$ repo init -u git://github.com/teemodk/manifest.git -b padroid
Get the source!
Code:
$ repo sync -j16
Find this section in "build/envsetup.sh" update with your favorite arm toolchain:
Code:
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=[B]~/toolchain/linaro4.8/bin[/B]
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
Go!
Code:
$ ./rom-build.sh endeavoru
Thats all. If it went well, get your new ROM in "out/target/product/endeavoru"
Don't forget the gApps.
Credits go to
PA:molesarecoming, D4rKn3sSyS for the awesome hybrid magic. All PA contributors. gokussjx for the mother of all PA guides. All the helpful people here, that use their time to help.
CM(aosp):thöemy,gorbi16,tbalden,(pabx) and all the unknown soldiers contributing to CM
Everyone I forgot.
Differencies from the official guide.
The official PA manifest is put together in a way, so you can easily build and maintain multiple devices with only one manifest.
It works by adding and removing device specific code with local manifests under the "vendor/pa" folder.
However, I am only compiling for OneX, so I found it easier to add/remove stuff directly in the main manifest.
The downside to this is, that you have to manually maintain the manifest everytime you want to sync with PA. Place for improvement
All changes in STEP 2 of the official guide, is already done if using my guide with padroid manifest.
In vendor/pa these steps are done:
Code:
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.adds"]/manifest/<device>.adds[][/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/manifests/endeavoru.removes"]/manifest/<device>.removes[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/prebuilt/pa_endeavoru.conf"]/prebuilt/pa_<device>.conf[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/pa_endeavoru.mk"]/products/pa_<device>.mk[/URL]
* Add device makefile entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/products/AndroidProducts.mk"]/products/AndroidProducts.mk[/URL]
* Create [URL="https://github.com/teemodk/padroid_vendor_pa/tree/padroid/vendorprops"]/vendorprops/<device>.proprietaries[/URL]
* Add device lunch menu entry to [URL="https://github.com/teemodk/padroid_vendor_pa/blob/padroid/vendorsetup.sh"]/vendorsetup.sh[/URL]
Furthermore, I temporarily moved the CM adds/removes from "vendor/pa/manifests" to .repo/manifest.xml.
I am sure there are better ways to handle git/repo/manifest etc., but this works well for me for now. Open for suggestions though.
Problem Solving
If (when) you run into problems, go to the official guide and find the answer. Most, if not all, errors is already answered there. If not, ask.
But first make a serious effort to find the error yourself. Read some good advice about finding the error.
As a rule of thumb: The build system tells you where to find the error! Something is missing, something is duplicated or somthing is just wrong. It's all in the log, running up your screen when compiling.
Build 25.Oct.2013
http://d-h.st/XRt
Nice, I'm always eager to learn this stuff .
Thanks!
ROM uploaded to post 3.
teemo said:
ROM uploaded to post 3.
Click to expand...
Click to collapse
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Mat08.cc said:
Thank you so much Teemo, for providing the guide and the rom.
Just a Q: is this stock ParanoidAndroid rom (stock kernel?) ?
Thanks again for your work :good:
Click to expand...
Click to collapse
The ROM is as close to stock as it get for OneX. It is really a mix of CyanogenMod and ParanoidAndroid. I follow the official build guide from PA-team.
The kernel is from same source as CM.
You can see everything in the manifest.
@teemo
your build is running fast and stable, congratulations! maybe you can keep updating this .. I appreciate it and I'm sure many other people would be of the same opinion
Sry,wrong threat....
Gesendet von meinem EndeavorU mit Tapatalk
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Mat08.cc said:
Hi @teemo I was trying to build my own rom using a different source.
I'm pretty sure I've done things right except that when i start my build it ends up after few seconds saying: "Kernel source found, but no configuration was defined. Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file"
I checked my BoardConfig.mk file and what I've got is TARGET_KERNEL_CONFIG := cyanogenmod_endeavoru_defconfig
I thought you may know how to help me with this!
Other infos: I'm tryn to build paranoidandroid 4.0 and i'm using cyanogenmod files for the endeavoru since i know aospa is cyanogenmod based right?
Hope you can help me :fingers-crossed:
Click to expand...
Click to collapse
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
teemo said:
Hi, I don't know what it takes to build ParanoidAndroid 4
But maybe you can ask in the Paranoid guide.
Or you can ask here for all other builds.
EDIT: Btw, to build PA4 or any other KitKat, you need the new sources for OneX (device+vendor+kernel). This guide will not work for KitKat.
Click to expand...
Click to collapse
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Mat08.cc said:
I used the new sources but that was the result! I'll start from zero again to see if I missed something Thanks for the reply always really kind!
Click to expand...
Click to collapse
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
One-X-master said:
the aospa dev build the aospa kitkat version...so a few days waiting and it will be there
Click to expand...
Click to collapse
Yeah I thought so! But I would love to learn! I have always looked to devs as to extraordinary people, understanding what makes them such would be great
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
LuisDias said:
Hey @teemo , sorry to bother you, but could you make an update build of PA? I don't have a stable connection, can't make a build of the new PA.. :/
Thanks man, take care
Click to expand...
Click to collapse
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
bosas200 said:
All credits to @audahadi https://drive.google.com/folderview?id=0B-KjFDQ914F4dVdQLU9nT3VkMGc&usp=sharing
Click to expand...
Click to collapse
Thanks brotha
teemo said:
Build 25.Oct.2013
http://d-h.st/XRt
Click to expand...
Click to collapse
Any chance helping me build AOSB with newer cm 11 base?
As no instructions anywhere on building AOSB from source. Source is
https://github.com/AOSB?page=1
Many thanks
I am wanting to build AOSB from source with newer CM 11 as base
How do I build it repo is https://github.com/AOSB?page=1
Many thanks hope someone can help please
anttaz said:
I am wanting to build AOSB from source with newer CM 11 as base
How do I build it repo is https://github.com/AOSB?page=1
Many thanks hope someone can help please
Click to expand...
Click to collapse
Assume you have setup build environment.
1. Repo init AOSB source
2. [email protected] device/htc/endeavoru, device/htc/tegra3-common, vendor/htc, kernel/htc to appropriate path.
3. Modify .mk file in device/htc/endeavoru per AOSB
Hint : maybe you also need more missing repo in AOSB from CM..especially wifi stuff
yes ubuntu build environment set up just need to know how to build. I am a bit of a newbie to Android, Many thanks for the response
audahadi said:
Assume you have setup build environment.
1. Repo init AOSB source
2. [email protected] device/htc/endeavoru, device/htc/tegra3-common, vendor/htc, kernel/htc to appropriate path.
3. Modify .mk file in device/htc/endeavoru per AOSB
Hint : maybe you also need more missing repo in AOSB from CM..especially wifi stuff
Click to expand...
Click to collapse
yes ubuntu build environment set up just need to know how to build. I am a bit of a newbie to Android, Many thanks for the response
Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru
audahadi said:
Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru
Click to expand...
Click to collapse
404 this is not the page you are looking for?
audahadi said:
Read some guide to understand a bit about build process.XDA university @ CM wiki have lot of resources.
repo init -u https://github.com/AOSB/android.git -b cm-11.0
They have crap commit for newbie to build..hope that link work.
After you have all device tree setup properly.
.build/envsetup.sh && brunch endeavoru
Click to expand...
Click to collapse
Read up I just don't get the device tree part of it now?
anttaz said:
Read up I just don't get the device tree part of it now?
Click to expand...
Click to collapse
Compare with other AOSB devices..what they change @ needed to compile for AOSB.
audahadi said:
Compare with other AOSB devices..what they change @ needed to compile for AOSB.
Click to expand...
Click to collapse
Well no luck as no other devices have a guide on building and asking the chefs of the ROMs on xda and on official asob site no response other than yourself. So still none the wiser
audahadi said:
Compare with other AOSB devices..what they change @ needed to compile for AOSB.
Click to expand...
Click to collapse
I have the manifest xml now will this help in the building process?
anttaz said:
I have the manifest xml now will this help in the building process?
Click to expand...
Click to collapse
Should be similar to this
http://wiki.cyanogenmod.org/w/Endeavoru_Info
Honestly..their source is crap..can't find much information to help you with. Just use another rom..
audahadi said:
Should be similar to this
http://wiki.cyanogenmod.org/w/Endeavoru_Info
Honestly..their source is crap..can't find much information to help you with. Just use another rom..
Click to expand...
Click to collapse
Many thanks for all your help anyways. Much appreciated
Hello Fellow developer and programmer, I'm building a custom by using Ressurection Remix as a base, While I'm initializing the repo an error occurred, How to solve that. The Error is repo is not reccoginzsed as an internal or external command, I have installed the repo, thanks for the reading the post
LMGTFY - Let Me Google That For You
For all those people who find it more convenient to bother you with their question rather than to Google it for themselves.
bfy.tw
Deadshot0x7 said:
Hello Fellow developer and programmer, I'm building a custom by using Ressurection Remix as a base, While I'm initializing the repo an error occurred, How to solve that. The Error is repo is not reccoginzsed as an internal or external command, I have installed the repo, thanks for the reading the post
Click to expand...
Click to collapse
Download repo and make executable. Basic stuff man. Google as suggested above.
William.trem said:
Download repo and make executable. Basic stuff man. Google as suggested above.
Click to expand...
Click to collapse
thanks btw I'm new to custom rom
Deadshot0x7 said:
thanks btw I'm new to custom rom
Click to expand...
Click to collapse
I'm working on porting one myself. Repo is available within the Ubuntu apt-get repository. That can be a simpler way to install. However I'd suggest the curl & chmod method method for the latest binary as well as getting good experience.
Source control tools | Android Open Source Project
source.android.com
Downloading the Source | Android Open Source Project
source.android.com
2 sec to google
Follow the instructions to add the repository, then do an initial repo sync, I hope you have plenty of drive space cos some roms can take up many GB
The manifest instructions even link you to the guide for setting up git and repo
Ubuntu is usually the best platform for this, it might work in Windows subsystem for Linux but I've never tried so couldn't tell you.
Haven't built a rom for a while but you used to add device tree urls in .repo/local_manifests/roomservice.xml, it's probably still done the same way. (.repo is a hidden folder by default so, in Ubuntu, you would press CTRL+H to get it to show up)
If you don't know how to install repo then you will likely need to do a LOT of reading before you can even think of firing off a build.
djsubterrain said:
Follow the instructions to add the repository, then do an initial repo sync, I hope you have plenty of drive space cos some roms can take up many GB
The manifest instructions even link you to the guide for setting up git and repo
Ubuntu is usually the best platform for this, it might work in Windows subsystem for Linux but I've never tried so couldn't tell you.
Haven't built a rom for a while but you used to add device tree urls in .repo/local_manifests/roomservice.xml, it's probably still done the same way. (.repo is a hidden folder by default so, in Ubuntu, you would press CTRL+H to get it to show up)
If you don't know how to install repo then you will likely need to do a LOT of reading before you can even think of firing off a build.
Click to expand...
Click to collapse
Currently having success within WSL v1 Ubuntu.