Database Develop

[GUIDE] Rolling your own CM7

Here's a short tutorial on how to build your own version of CM7.
Requirements:
- Linux distro such as Ubuntu.
- 30 GB of space.
- Fast internet.
Instructions:
1. Open terminal and install these packages through the commands:
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
If you are on a 64-bit system, install these also:
Code:
sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.4-multilib g++-4.4-multilib
2. Create directories.
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
3. Fetch files from CM.
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
~/bin/repo sync
This will take some hours.
4. Download this git: https://github.com/koush/proprietary_vendor_lge - then extract to /vendor/lge/ (so you have /vendor/lge/p970/...).
5. Build.
Code:
~/android/system/vendor/cyanogen/get-rommanager
. build/envsetup.sh && brunch p970
You'll have the .zip in ~/android/system/out/target/product/p970/.
6. Flash the kang!
That's it.

Only a remark:
- Trying to build my own ROM, I've found that the .zip were 15MB smaller than the same nightly because it doesn't include proprietary files into the ROM. Then arcee told me that before build it, you have to run ./setup-makefiles.sh inside the device's dir.

Huexxx said:
Only a remark:
- Trying to build my own ROM, I've found that the .zip were 15MB smaller than the same nightly because it doesn't include proprietary files into the ROM. Then arcee told me that before build it, you have to run ./setup-makefiles.sh inside the device's dir.
Click to expand...
Click to collapse
No need, check point 4.

thank you very much manuel, very kind of you to share your knowledge with those of us who want to continue your work!

When I tried, I ran ./extract-files.sh in order to get proprietary files from phone itself.
Getting it from the indicated git, you get also the needed .mk files, and then there's no need to run ./setup-makefiles.sh
Forget what I've said...

I hope this guide may inspire some members to give a hand cooking own rom, and we can see this development section filled with different roms. What an optimistic scenario it would be ! .
Thanks again all devs.

knzo said:
Here's a short tutorial on how to build your own version of CM7.
Code:
curl http://android.git.kernel.org/repo > ~/bin/repo
chmod a+x ~/bin/repo
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
~/bin/repo sync
Click to expand...
Click to collapse
in case anyone else faces this, could not run repo init and was going crazy, finally realized repo was not taking the exec flag, opened it up and saw the url was moved, but the link it provided did not work either. remembered the original setup i did for the full android development on another machine and tried this instead -
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
worked like a charm! now, on to the rest...

i am happy to say that i have successfully built and am running my first homegrown KANG, thanks to this tutorial! give it a try, it isn't as hard as you might think (but it does take a VERY long time!)

Hi.
I am a completely n00b here and on the Android environment in general.
So, I was watching the Knzo's instructions and I noted this:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [/bold]gingerbread[/bold]
So I changed it to:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [/bold]isc[/bold]
And it worked!
But, trying to build here:
Code:
~/android/system/vendor/cyanogen/get-rommanager
. build/envsetup.sh && brunch p970
My system says:
Code:
bash: /home/said/android/system/vendor/cyanogen/get-rommanager: No such file or directory
Then I tough, "It's ok, I can get the rom-manager from the market. And skipped to:
Code:
. build/envsetup.sh && brunch p970
But then my system said:
Code:
[email protected]:~/android/system$ . build/envsetup.sh && brunch p970
including device/samsung/maguro/vendorsetup.sh
including device/samsung/tuna/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
Device p970 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_p970
Duplicate device 'CyanogenMod/android_device_lge_p970' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_p970'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Then I tried:
Code:
. build/envsetup.sh && breakfast p970
And this is the output:
Code:
including device/samsung/maguro/vendorsetup.sh
including device/samsung/tuna/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
Device p970 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_p970
Duplicate device 'CyanogenMod/android_device_lge_p970' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_p970'
** Do you have the right repo manifest?
So I went to:
Code:
/android/system/build/envsetup.sh
But couldn't find anything resembling the repo manifest. So that's why I'm here... any help?
Thanks in advanced.
EDIT: Maybe I'm just naïve...

saidhabla said:
I am a completely n00b here and on the Android environment in general.
So I changed it to:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [b]isc[/b]
And it worked!
Click to expand...
Click to collapse
What is isc? Do you mean ics stands for Ice Cream Sandwich?
ICS from CyanogenMod isn't even completed yet, then what are you trying to do?
If you really want to hacking the Android system, I suggest that you synchronize the original android source for ICS to build your own ROM:
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
PS: I don't know yet the size of ICS source would be.. It says ~6 GB, but I'm not getting into it yet...
.CMIIW.

The first part is easy, rom-manager is in vendor/cm folder instead. The second part is a bit more difficult - there are only device branches for a few models, you need to look at those makefiles and figure out how to recreate them for our device. I'm at the same point myself. Don't be discouraged by negatives, it certainly can be done (arcee is running it) but we should probably discuss it elsewhere and not hijack this thread. Good luck, and PM me of you get anywhere, I'll do the same.
Sent from my LG-P970 using XDA App

redy2006 said:
What is isc? Do you mean ics stands for Ice Cream Sandwich?
ICS from CyanogenMod isn't even completed yet, then what are you trying to do?
If you really want to hacking the Android system, I suggest that you synchronize the original android source for ICS to build your own ROM:
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
PS: I don't know yet the size of ICS source would be.. It says ~6 GB, but I'm not getting into it yet...
.CMIIW.
Click to expand...
Click to collapse
Thanks!
So, just in case some lost soul come here and watch your post, the command has to be like this:
Code:
~/bin/repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
Thanks again...
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
dharmabm said:
The first part is easy, rom-manager is in vendor/cm folder instead. The second part is a bit more difficult - there are only device branches for a few models, you need to look at those makefiles and figure out how to recreate them for our device. I'm at the same point myself. Don't be discouraged by negatives, it certainly can be done (arcee is running it) but we should probably discuss it elsewhere and not hijack this thread. Good luck, and PM me of you get anywhere, I'll do the same.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Agree!
And if someone knows how to open a new thread, please let us know. Over for now.

saidhabla said:
And if someone knows how to open a new thread, please let us know. Over for now.
Click to expand...
Click to collapse
"How to open a new thread" ?
Just on the thread list of General/Android Development section, you will notice a yellow box on the top saying in capital : "NEW THREAD". Just click it..

saidhabla said:
Thanks!
So, just in case some lost soul come here and watch your post, the command has to be like this:
Code:
~/bin/repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
Click to expand...
Click to collapse
If you've read the main Android documentation, before we can run just "repo" command, we should set the path:
Code:
$ PATH=~/bin:$PATH
If the path didn't set, then it should run the command:
Code:
$ ~/bin/repo
.CMIIW.

Why would I build my own CM7
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário

offcourse said:
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário
Click to expand...
Click to collapse
i'm sorry,but how long have you been in mars ? lol
the nightlies had stopped at v #20 because of the buildbot was down, and no more update till now
that's why all of us (i don't know if it's just me) are so desperated

offcourse said:
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário
Click to expand...
Click to collapse
Well you can build your own ROM if you having the source code, for example this CM source. And yes, you can do everything you want (change the packages, framework, anything). AFAIK there's no tutorial how to do it, but you should have basically programming skill, especially with C++ and Java, since it's based from those programming language. If you don't have that, then you can just using any launcher out there
CMIIW

redy2006 said:
Well you can build your own ROM if you having the source code, for example this CM source. And yes, you can do everything you want (change the packages, framework, anything). AFAIK there's no tutorial how to do it, but you should have basically programming skill, especially with C++ and Java, since it's based from those programming language. If you don't have that, then you can just using any launcher out there
CMIIW
Click to expand...
Click to collapse
OK, thanks. Clearly not for me coz' we, Martians, don't have programming skills. Just wanted a gingerbread rom without all the crap, neither LG's, Vodafone or even Cyanogen.
Also, because LG's gingerbread update, when it comes, will probably not have the VPN and I can't get any vpn software to work currently, except in Cyanogen (which is buggy in some apps).

I am sorry but vendor lge have 404 error can you get another link ?

Compiling from AOSP source for ATRIX (OLYMPUS) [TUT] [GUIDE]

Hi Guys,
This is for US version with ATT
I am starting an attempt to build from AOSP source and I will post as much as possible the complete process for people who wish to do the same. I have never compiled for ATRIX before, and I am sure I will need a lot of help from the community.
I have started my process by first Installing a fresh copy of linux mint 12,
I will give the list of packages install and the directory setup, I will keep my folder in the home directory so the commands I use are portable and probably help make a script in the end , for compile from scratch to the *.img files ready for installation via fast boot.
I am open to suggestions and criticism

Reserved for the main TUT
Lets start by installing all tools that may be needed to build the source including apps
Install an good IDE which also supports android-sdk
Code:
sudo apt-get install eclipse-cdt
1) Install SDK
Install the SDK with api for 2.3.3 and 4.0 if you wish to update to ice cream sandwich, which I plan to soon try after first sucessful compile for 2.3.3
follow instructions here
http://developer.android.com/sdk/eclipse-adt.html#installing
2)Initialize Build Environment
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev \
libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown \
libxml2-utils libsdl-dev libesd0-dev libwxgtk2.6-dev
3)Install CodeSoucery compiler for arm-linux-eabi
Download the IA32-GNU/Linux installer from here
go to the download folder in command prompt and set executable permissions for it
Code:
chmod +x arm-2011.03-41-arm-none-linux-gnueabi.bin
Install it with all default options
4) Get Kernel Source for ATRIX from
here
Unzip code in a folder in home directory , a folder named kernel-tegra is created
5) Get config file from an ATT atrix with stock kernel
Connet phone switch on debugging from settings
Assuming android sdk installed under home folder.
Code:
cd ~/android-sdk-linux/platform-tools/
./adb pull /proc/config.gz
mv config.gz ~/kernel-tegra/
cd ~/kernel-tegra/
gunzip config.gz
cp -a config .config
6) Lets Compile the Kernel
Start with setting the compiler flags
Code:
cd ~/kernel-tegra
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-gnueabi-
make oldconfig
make zImage
make modules
and we have a compiled kernel, now we need to packit and upload it to the phone! Working on it now

Is this the right forum mate..?

whats an atria? herp a derp

So where do I start this, do I go to main android developement thread in the forum?
Sorry atrix, auto correction sucks
Sent from my MB860 using xda premium

I'm 15 with only.visual basic programming ... if I can help please shoot me a pm
Sent from my MB860 using xda premium

lol..take a look at the cm wiki if you need help compiling. There's plenty of guides and tutorials out there

I tried reading those guides but they are highly customized about CM7 code and rely on scripts. M y aim here is to start with google source apply motorola patches update to a working repo on google code and update to ICS. To be generic so anyone can use it for any platform as a guide and know what files are to be modified, I am going to mention in detail about all files modified, all drivers that were added and if possible explain changes in each file , reason and what needs to be changed. If I could find that documentation it would be great but I couldn't!
Also cm7 doesn't have a official repo for ATRIX.

I'm interested for this tutorial. So be kind to continue please. Its nice to gain more knowledge and if it is step by step its even better !
Thank you !

This certainly looks interesting, I think might get linux running in a virtual machine and try it myself. Ice cream sandwich would be a very good thing to get working from this, but to build it from source, you need the source for tegra from nvidia for sure, and maybe code from motorola, I am right?
Even if that's not possible, a guide for building a android aosp rom for the atrix sounds awesome, keep posting.

Ya you do need source from motorola for the kernel, but any device running ICS on tegra2 should help with the kernel, and I don't think the kernel version has changed in ICS it is still 2.6.xx, cause I haven't read anywhere about the change. Also if kernel is the same the drivers are almost the same, so I am guessing main framework and UI changes are a big part, which happen to be quite independent of hardware!

aditya_g8 said:
Ya you do need source from motorola for the kernel, but any device running ICS on tegra2 should help with the kernel, and I don't think the kernel version has changed in ICS it is still 2.6.xx, cause I haven't read anywhere about the change. Also if kernel is the same the drivers are almost the same, so I am guessing main framework and UI changes are a big part, which happen to be quite independent of hardware!
Click to expand...
Click to collapse
I read somewhere that they were going to start using 3.x kernel, but the sdk says its running 2.6.29, and the kernel might not be updated for some time since its not part of the main linux kernel repository anymore.
Is Spotify really necessary???

WTF is this? I hope you prove me wrong but you have noob written all over you. First you misspell Atrix then you misspell Olympus. You write a guide on how to install Spotify. You don't even specify what you're trying to compile. Kernel? AOSP? CM7?

yeahmann said:
WTF is this? I hope you prove me wrong but you have noob written all over you. First you misspell Atrix then you misspell Olympus. You write a guide on how to install Spotify. You don't even specify what you're trying to compile. Kernel? AOSP? CM7?
Click to expand...
Click to collapse
Hey I am new to this, but I am trying to work thing out. I am hardware guy with very less programming experience. I want to write a guide from a noob perspective, which is which is why I started. More than a guide this is a log of things I am doing to get my AOSP and kernel compiled. I wish to then start with ICS, I know it is a long shot but worth a try!
When I am done with it completely say 2.3.3 I will clean up my posts and make sure no errors exists

Guys let the dude try at least ...everyone is a n00b at sometime or the other ...he is trying to learn so motivate him ...

lol..install spotify..sdk..eclipse ide..
lol
Neither 3 of those have anything to do with building..you obviously haven't read the cm wiki yet. theres nothing about scripts there...It gives you the commands to run to get all the tools necessary, & Instructions on how to build.
Jussayin..the way you're going, is headed in the wrong direction even for a noob

jasonyump said:
Jussayin..the way you're going, is headed in the wrong direction even for a noob
Click to expand...
Click to collapse
I agree with that , guess some dev needs to point him to the right direction ...
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
Dont know if this will help, but a long time ago, i compiled a kernel for my spica and here are the steps ...
http://forum.samdroid.net/f28/setup-kernel-build-environment-using-virtualbox-windows-7-64-bit-4007/
---------- Post added at 07:37 PM ---------- Previous post was at 07:19 PM ----------
here is another link which might help
http://forum.xda-developers.com/showthread.php?t=1188298

munchy_cool said:
I agree with that , guess some dev needs to point him to the right direction ...
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
Dont know if this will help, but a long time ago, i compiled a kernel for my spica and here are the steps ...
http://forum.samdroid.net/f28/setup-kernel-build-environment-using-virtualbox-windows-7-64-bit-4007/
---------- Post added at 07:37 PM ---------- Previous post was at 07:19 PM ----------
here is another link which might help
http://forum.xda-developers.com/showthread.php?t=1188298
Click to expand...
Click to collapse
Thanks guys, I will read through them links and will learn. I am open to learning and sorry for the script part , I read a forum where CM7 compile was done with a automated script file which said official and I thought that was it.

Hi guys I have compiled the kernel and have a zImage, I wish to pack and upload it and test it before I can confirm it is working. Thanks for the help again guys! And I got rid of spotify I see people are much more critical than I thought! I was hoping for a little more help as a friendly forum!
Thanks a lot munchy_cool

aditya_g8 said:
Hi guys I have compiled the kernel and have a zImage, I wish to pack and upload it and test it before I can confirm it is working. Thanks for the help again guys! And I got rid of spotify I see people are much more critical than I thought! I was hoping for a little more help as a friendly forum!
Thanks a lot munchy_cool
Click to expand...
Click to collapse
I wasn't trying to be critical, I was just wondering why you had it on there.

Development! Project JellyBeanSwift - Open Source Project!

I will teach you build ROM.
Lets get some ROCK!!!
Operating System
First step is having a fully functional linux distro. You can choose what you prefer, I'm using ubuntu and I write commands for it. You can use OSX too, as I know, but I've completely no idea how, I never had a Mac.
Well, talking about linux, you need a 64bit distribution, so if you have an old 32 bit processor youn cannot go ahead.
To check which version do you have, type in a shell
uname -a
If the results include "x86_64" you're ok.
Required Packages
You need to install some little packages, to be able to proceed, you can do this with your favorite package manager:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Some systems need some trick to install all this package, is your care to check this process completed correctly and fix eventually problems.
Install "repo"
Repo is the program that handles synchronization between our pc and the repository, in this case Cyanogen's one. To install do:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
So we have downloaded and added executables flag to it. Now we need a folder to store locally the sources, you can put it everywhere, but to be coherent with other guides, I do:
mkdir -p ~/CM10/
Repository initialization
Well, now it's time to initialize our source folder to correctly sync with repository:
cd CM10
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Nota: Maybe the repo command is not recognized. In this case you can restart the shell or te machine.
Download
Now is download time! Write this command and get a fresh beer, you have to download several GB of data, please wait.
repo sync -j16
The "-j16" switch may be modified as you want, is the number of concurrent thread downloading from repo. 16 is my value, for a 100Mbit connection, maybe you can decrease a little to match your line speed. Someone uses 8 threads for an 8Mbit ADSL line.
Download precompiled files.
There are some others files needed, like the toolchain, including GCC, to compile code.
~/CM10/vendor/cm/get-prebuilts
Another small wait time and we're ready!
Add sources code for GT540
Copy sources from https://github.com/mmxtrem/device_lge_swift to ~/CM10/device/lge/swift
Or extract this archive http://depositfiles.com/files/1chflk58r to ~/CM10/device/lge/swift
Build
Great, we're ready to build!
The build process takes some hours, so be patient. My notebook, takes more than 10 hours!
cd CM10
source build/envsetup.sh && brunch swift
Install
When is ready, we can find the result here:
~/CM10/system/out/target/product/swift/cm-10-XXXXX-JellyBeanSwift-XXXX.zip
This is the package to be flashed in recovery mode.
There are Gapps included.
Update
If you want to update your build, you have to do only this:
cd CM10
repo sync
and build again!
P.S. Dont forget write Credit my name, when will be publish your ROM. Good Luck!
[Guide] How to use Github
http://forum.xda-developers.com/showthread.php?t=1877040

Wow I always wanted to try this out! Thanks for the surprise tutorial!

Wow wow wow.. forget my post in the other thread. This thing miro, this thing here is possible your best contribution to this community.. I'm getting my old gt540 back from my brother and trying these right tomorrow..
I actually thought about asking you for such a tutorial but scratched it as I didn't believe you would do it. But thank you again and again.. I was so wrong

I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob

Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8

-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
+1
Sent from my LG-P990 using Tapatalk 2

smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
Yes, gt540 is msm7x27

smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Please dont write stupid massages like "smiles" or +1 or other, make it clean! Devs only, if you want build ROM real, if no go spaming into other thread!

XiproX said:
Yes, gt540 is msm7x27
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Click to expand...
Click to collapse
damn

-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
^ This, make a guide for this, or is just all "lets google it"?

thanks for that tut miroslav !!
i would be happy if you can make example of bug fixing/driver porting (something simple as example).

Oh, nice post Miro
But one thing, why don't you post how to make device files. It would be of more use as people will try to make their own sources and a good chance that they could make their own device in collaboration. :good:

i've ear i can do a build in a 32bits processor too! but you know xD do what was said up please!!

Could someone try to build this because I can't cause I have 32bit system in my PC.
We need JB for daily use!

Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?

aaa801 said:
Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?
Click to expand...
Click to collapse
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.

Niquel97 said:
We need JB for daily use!
Click to expand...
Click to collapse
Just do it! (c. Nike)
P.S. Dreams-dreams-dreams.... :laugh:

miroslav_mm said:
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.
Click to expand...
Click to collapse
So should work fine if set to hard yes?

i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])

al3000 said:
i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])
Click to expand...
Click to collapse
Yes, me too, the build comes so big that it fails the size checks on the default partition layout.
To avoid that change the contents in device/lge/swift/BoardConfig.mk, I've used these values:
Code:
# PARTITIONS
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00900000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0010B07600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x007478A00
BOARD_FLASH_BLOCK_SIZE := 131072
I believe you can still zip up the right files in out/target/product/swift/ to have a signable update zip, the command "make otapackage" which I found somewhere didn't seem to work.

Porting AOSP from source

ok, i'm trying to port and boot the AOSP source from google for 4.1.2 JB x86, first of all, i follow the next guide to build my own compiling machine http://forum.xda-developers.com/showthread.php?t=2762390 but i download in the step 12 the repo of google AOSP (repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r2.1 & repo sync)
Start the enviroment with: . build/envsetup.sh
and download download the source from motorola to get some propertary files http://sourceforge.net/projects/razr-i.motorola/files/LATAM/9.8.2I-50_SML-29/
now, the git have some instructions like you see in the README file inside the source, this say:
1. Create a workspace containing "vanilla" JB release from Google.
Done
Click to expand...
Click to collapse
ou may need to apply the following change in build repo to prevent the build from aborting when unexpected user tag is found on some modules:
[SOURCE] diff --git a/core/base_rules.mk b/core/base_rules.mk
index 3c11673..ecf611d 100644
--- a/core/base_rules.mk
+++ b/core/base_rules.mk
@@ -99,7 +99,7 @@ ifneq ($(filter $(LOCAL_MODULE_TAGS),user),)
$(warning * PRODUCT_PACKAGES section of)
$(warning * build/target/product/core.mk)
$(warning * )
- $(error user tag detected on new module - user tags are only supported on legacy modules)
+ $(warning user tag detected on new module - user tags are only supported on legacy modules)
endif
endif [/SOURCE]
i'm trying to do this step, but nothings seems happen...
The second step says that all we need is overlaying the Motorola repos on top of the AOSP repos, but in the Terminal i don't know some commands ('cause always i work on Windows ).
i need just a little help in here, i'm tryin to compare both sources, but in windows i've a tool called WINMERGE, in linux i don't know if we have something like that. I don't wanna overlay the repos, i want to compare the files and re-write the AOSP source with some parts of the motosource and get AOSP software with motorola hardware working.
thks to all, sorry for my bad english, i don't use translator

I always used meld. Meld is an 2to3 way comparing tool, that compares folders (date), files (versions) and text. It is almost like winmerge, just a little bit different. U can look it up in the app store of whatever ubuntu/linux version you have.
As for the defferences between aosp and moto. There are a number of differences. The most can be located in the system/core where moto has changed the behavior of how init works and some x86 implementations (especially pixelflinger). The next BIG thing is the bionic (libc). It has many x86 implementations and i am not sure if u can overlay them without trouble into aosp source.
Good luck!

Hazou said:
I always used meld. Meld is an 2to3 way comparing tool, that compares folders (date), files (versions) and text. It is almost like winmerge, just a little bit different. U can look it up in the app store of whatever ubuntu/linux version you have.
Click to expand...
Click to collapse
yeah, i'm using meld, it's amazig 'cause i can copy the files from one to another place, by the way, i'm using Ubuntu 14.04, with JVM 1.70 but 've some errors in the moment to build ...
As for the defferences between aosp and moto. There are a number of differences. The most can be located in the system/core where moto has changed the behavior of how init works and some x86 implementations (especially pixelflinger). The next BIG thing is the bionic (libc). It has many x86 implementations and i am not sure if u can overlay them without trouble into aosp source.
Good luck!
Click to expand...
Click to collapse
yeah, i see the both codes and check the changes, in some lines the works of moto it's amazing, but whe need more dev's to check all the changes to implement for porting ROMS
Lenovo has recently provided a software update which upgrades Android to version 4.3 for the k900, so i'm going to download the repo AOSP from google and later try to port 4.3

Calling all [DEVELOPERS], make yourselves be known....

Calling all Developers.... (Hi everyone),
Today, we received sad news.... One of our most popular and committed Developers @chasmodo has informed us that he is moving on to pastures new.... (and with that, we wish he well and are thankful for all he has offered us during this time).
Of course, as time goes on, so do people, as they progress to bigger and better devices... As we have seen with, @beerbong, @herna and others.... Like above, we are grateful for all you have given us over these years....
I'm not sure if @victorator is still on the scene...???
[edit]Sorry, forgot that @jackeagle... of SpiritRom fame is still on the scene.
So basically, this is just a call out to see who else is out there, who is still making roms for our beloved N7000.... What with Android L(ollipop) just around the corner.....
ROM's we have lost...
PAC-MAN Rom (no maintainer)
Dirty Unicorn (no maintainer)
LiquidSmooth (no maintainer)
Paranoid Android / Legacy (no maintainer)
C-ROM (abandoned, all devices)
SOKP (closed down, all devices)
(second wave of culls, due to Lollipop)
CyanogenMod (No longer getting any official CM12 support)
OMNI rom (No longer getting any official CM12 support)
Spirit Rom (abandoned, all devices)
AICP (No longer getting any official CM12 support)
ReVolt (unsure future?)
NamelessROM (No longer getting any official CM12 support)
GiggleRom (abandoned, all devices, moved over to Blissrom... However no support for N7000 yet)
ROM's we still have...
CyanogenMod (progress kept alive thanks to wonders of BAUNER, CM11 nightlies seem to be on autopilot)
SlimKat (unsure, will need to check)
CarbonRom (unsure, will need to check)
* there maybe others??
Cheers, Lister

You don't lose those, just setup Linux and compile them. I'm running my own customized LiquidSmooth right now, but I've also compiled others. Even if they don't officially support a device, they all mostly use the same underlying framework, so it's easy enough to make them compile for the n7000.
Here's what I did:
1. Download http://elementaryos.org/ and install
2. sudo apt-get install openjdk-7-jdk git gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i38 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386; sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so; echo "export USE_CCACHE=1" >> ~/.bashrc; mkdir ~/bin; mkdir ~/android/distroname; curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo; chmod a+x ~/bin/repo; cd ~/android/distroname
3. Then find the repo init command for the distro you want. For CM11 do "repo init -u https://github.com/CyanogenMod/android.git -b cm-11.0". For LiquidSmooth it's "repo init -u git://github.com/LiquidSmooth/android.git -b kitkat". For SlimKat "repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4".
4. repo sync; source build/envsetup.sh
5. breakfast n7000; brunch n7000
That last part might be a little different for each distro. But all you need to do is get the n7000 files into the directory. There's some proprietary blobs in ./vendor, and the device tree in ./device, and kernel config is in ./kernel/samsung/smdk4412/arch/arm/configs. Just edit the ./device/samsung/n7000/*.mk files to point to your kernel config.
I would start with CyanogenMod by making ~/android/cyanogenmod and repo init in there. That is because they all use the CyanogenMod device files for building for the n7000. Follow this http://wiki.cyanogenmod.org/w/Build_for_n7000. Once you get that running, you have all the files necessary. Then make a new directory for another distro, like ~/android/liquidsmooth, and repo init in there. Then copy over the samsung folders from the CM11 device, vendor, and kernel config areas into the other distro. That is how I got LiquidSmooth to compile for n7000, since they don't provide those files in their repo.
Then it compiles everything for you and you don't need to understand how it works. You just get an auto-generated .zip file you can flash like any other you download. It isn't difficult, and you don't need to rely on anyone to do it for you.

Lister Of Smeg said:
Calling all Developers.... (Hi everyone),
Today, we received sad news.... One of our most popular and committed Developers @chasmodo has informed us that he is moving on to pastures new.... (and with that, we wish he well and are thankful for all he has offered us during this time).
Of course, as time goes on, so do people, as they progress to bigger and better devices... As we have seen with, @beerbong, @herna and others.... Like above, we are grateful for all you have given us over these years....
I'm not sure if @victorator is still on the scene...???
[edit]Sorry, forgot that @jackeagle... of SpiritRom fame is still on the scene.
So basically, this is just a call out to see who else is out there, who is still making roms for our beloved N7000.... What with Android L(ollipop) just around the corner.....
ROM's we have lost...
PAC-MAN Rom (no maintainer)
Dirty Unicorn (no maintainer)
LiquidSmooth(no maintainer)
C-ROM (abandoned, all devices)
SOKP (closed down, all devices)
ROM's we still have...
CyanogenMod
OMNI rom
Spirit Rom
Paranoid Android / Legacy
SlimKat
CarbonRom
AICP
ReVolt
NamelessROM
GiggleRom (maybe coming to us)
* there maybe others??
Cheers, Lister
Click to expand...
Click to collapse
Even sokp and du leave us note user alone
Sent from my GT-N7000 using XDA Free mobile app

noterio said:
You don't lose those, just setup Linux and compile them. I'm running my own customized LiquidSmooth right now, but I've also compiled others. Even if they don't officially support a device, they all mostly use the same underlying framework, so it's easy enough to make them compile for the n7000.
Here's what I did:
1. Download http://elementaryos.org/ and install
2. sudo apt-get install openjdk-7-jdk git gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i38 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386; sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so; echo "export USE_CCACHE=1" >> ~/.bashrc; mkdir ~/bin; mkdir ~/android/distroname; curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo; chmod a+x ~/bin/repo; cd ~/android/distroname
3. Then find the repo init command for the distro you want. For CM11 do "repo init -u https://github.com/CyanogenMod/android.git -b cm-11.0". For LiquidSmooth it's "repo init -u git://github.com/LiquidSmooth/android.git -b kitkat". For SlimKat "repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4".
4. repo sync; source build/envsetup.sh
5. breakfast n7000; brunch n7000
That last part might be a little different for each distro. But all you need to do is get the n7000 files into the directory. There's some proprietary blobs in ./vendor, and the device tree in ./device, and kernel config is in ./kernel/samsung/smdk4412/arch/arm/configs. Just edit the ./device/samsung/n7000/*.mk files to point to your kernel config.
I would start with CyanogenMod by making ~/android/cyanogenmod and repo init in there. That is because they all use the CyanogenMod device files for building for the n7000. Follow this http://wiki.cyanogenmod.org/w/Build_for_n7000. Once you get that running, you have all the files necessary. Then make a new directory for another distro, like ~/android/liquidsmooth, and repo init in there. Then copy over the samsung folders from the CM11 device, vendor, and kernel config areas into the other distro. That is how I got LiquidSmooth to compile for n7000, since they don't provide those files in their repo.
Then it compiles everything for you and you don't need to understand how it works. You just get an auto-generated .zip file you can flash like any other you download. It isn't difficult, and you don't need to rely on anyone to do it for you.
Click to expand...
Click to collapse
wow bro this full guide should has its own thread
Lister Of Smeg said:
Calling all Developers.... (Hi everyone),
Today, we received sad news.... One of our most popular and committed Developers @chasmodo has informed us that he is moving on to pastures new.... (and with that, we wish he well and are thankful for all he has offered us during this time).
Of course, as time goes on, so do people, as they progress to bigger and better devices... As we have seen with, @beerbong, @herna and others.... Like above, we are grateful for all you have given us over these years....
I'm not sure if @victorator is still on the scene...???
[edit]Sorry, forgot that @jackeagle... of SpiritRom fame is still on the scene.
So basically, this is just a call out to see who else is out there, who is still making roms for our beloved N7000.... What with Android L(ollipop) just around the corner.....
ROM's we have lost...
PAC-MAN Rom (no maintainer)
Dirty Unicorn (no maintainer)
LiquidSmooth(no maintainer)
C-ROM (abandoned, all devices)
SOKP (closed down, all devices)
ROM's we still have...
CyanogenMod
OMNI rom
Spirit Rom
Paranoid Android / Legacy
SlimKat
CarbonRom
AICP
ReVolt
NamelessROM
GiggleRom (maybe coming to us)
* there maybe others??
Cheers, Lister
Click to expand...
Click to collapse
never mind bro, the community is big enough to make everyone happy
And for those who have moved to play with other devices... we really appreciate their work and contribution for the whole comminuty their names are immortals don't you think?!

We DESPERATELY NEED Device Maintainers....
Hi All,
Guys, we are in desperate need of seeking new Device Maintainers, if we are ever to see Android L on our Galaxy Notes...
As my OP highlights, we've lost a lot of ROMs as sadly Device Maintainers move on, or the project(s) get abandoned.... However, I read today that we may not even see Android Lollipop on our Note, as even the main BASE builds (Omni) look set to drop us too.... We can only hope CyanogenMod keep us.... Otherwise we're doomed....
So, if you have the skills, the knowledge and the time.... (or know someone who can, please ask) and make yourselves known.... WE NEED YOU!!! :good::good::good:
Be a shame to see this device drop off all existance, as I'm sure despite it's age, its still a darn fine platform.... Be great to keep it going that bit longer....
Thanks, Lister

Hi All,
Just thought I'd update this list, as we've lost another rom, sadly....
Paranoid Android will no longer be supporting us...
https://plus.google.com/106020481530876935386/posts/iU8TBAAA4w2
Cheers, Lister