Develop Bugs

5/6 <DEV> [WIP] {ROM} 'AOSEP' Community Development "Build your own cm7/cm9/?"

5/6 <DEV> [WIP] {ROM} 'AOSEP' Community Development "Build your own cm7/cm9/?"
AOSEP V2.5​
Android Open Source Education Project​See post #191 for updated scripts
By following these instructions and/or using this set of files, you
proceed at your own risk. Under no circumstances would you hold
dizgustipated or anyone, except yourself, responsible for any negative consequences.[/COLOR][/I][/B]
################
***********************
################
I came across a "new" way of thinking over on a different thread, and have decided to adopt it.
I will still be developing and releasing roms,
but
Basically, I want to get you more involved in developing.
Allow you the chance to learn, contribute, and take pride in your accomplishments.
Possibly further the development of android, and see a whole new world open up to you.
That's why and how I got into developing. In was very curious, and unhappy with current rooms and update frequency. Or just with features available.
see post 2 for more info on the philosophy
I'd like to share a little script I found, and modified (with permission, and is still a work in progress) to automate the sync/build/package cycle, and to push the XDA community to get involved on a deeper level.
This whole process is designed for the latest stable Ubuntu (10.04/11.10), though it might work with Debian as well (or even other distros, if you have all the prerequisites already installed).
Alternatively, on tbe last post, you will find a handy script that gives a good shot at automating the whole prerequisites ordeal.
Place it in your root directory, navigate to it in terminal and type
Code:
Code:
sudo ~/installer.sh
Any brave souls willing to try?
I know you're impatient to get started, this script also contains a little guide, so check it out. I haven't had much opportunity to test this script because it takes so much time to start from scratch, so please help me out!
As of now, I have made many full builds this way, as well as a few incremental updates. Feel free to modify the MIT-licensed script. There are two time-consuming steps (4 and 6), so I'd recommend planning accordingly. Also make sure you have plenty of space on your disk; my working directory currently contains about 23GB.
0. I prefer you to start from scratch, (we want a clean start) as follows:
1. Make a folder for all your Android-building needs.
In your home directory, make a folder called "android"
Code:
Code:
mkdir android
and drop the text file in there, (in the new "android" directory, named Makefile (with no extension).
(Alternatively, you can open the make file, and edit the repo init to your preferred sgt7 repo sourcecode. Also, if you change repo address, you will need to make Bacon, instead of make package.)
Then open your favorite terminal app and navigate to that folder.
Code:
Code:
cd android
2. If you don't have any of the tools installed yet, and you're on Ubuntu, do this:
Code:
Code:
sudo apt-get install build-essential
sudo make apt
3. Initialize your working directory:
Code:
Code:
make init
4. Fetch the source code:
Code:
Code:
make sync
nb: It might take a while to fetch ~5.7GB of code off the Internet, depending on your connection. It might also hang, in which case you gotta stop the process, and retry (make sync) until you have everything. When you retry, you might want to do `make sync J=4` to reduce the concurrency. If it then complains about corrupt repositories ("not a repository"), you must delete the corrupt repositories and retry. You'd know it's frozen if "Fetching projects" does not progress for a minute or so.
(after a sync, seeing:
if ! grep -q "<stddef.h>" /home/diz/android/system/external/mesa3d/src/glsl/linker.cpp; then \
sed -i '1i #include <stddef.h>' /home/diz/android/system/external/mesa3d/src/glsl/linker.cpp; \
fi
is normal, it is patching so you can build)
5. (This step is done for you in the sync)
Alternatively, if you are looking to get deeper into dev-ing, you can back up the files, boot into CM7 and do the following to start making your own device files.
Plug in your SGT7 via USB, boot into CM7/BOCA RC1, and make sure debugging is enabled... to get some vendor-specific files (proprietary bits from Samsung and prebuilt bits from CyanogenMod):
Code:*
Code:
make vendor
*This will overwrite my device files, if you do not wish to do so, move on to the next step.
6
Build that stuff:
Code:
Code:
make build
This takes a while, depending on your hardware... perhaps a few hours. It's best to do this step overnight.
*if you error out in the build on: android_reboot.c, download THIS and replace the file already in android/system/system/core/licutils(android_reboot.c)
7. Save a snapshot for later:
Code:
Code:
make snapshot
This is actually required for the next step. But don't worry: snapshots are incremental, so they don't use too much space; and it's safe to remove any snapshot except "current".
8a. Package it up:
Code:
Code:
make package CLEAN=1
Check the snapshots directory for your shiny new update.zip
8b.Or simply make Bacon.
Code:
make bacon
9. It's even easier to keep your source up-to-date:
Code:
Code:
make sync
make build
make snapshot
make package CLEAN=1
(unsigned)
or
Code:
make package CLEAN=1 SIGN=1
(signed)
Or
Code:
make bacon
This makes a GSM P-1000 flashable zip, you can easily exchange the zImage for a L or N kernel, in the zip, & then flash in recovery after clearing user data, dalvic cache and cache then flash ICS gapps
10.
Be joy full and post a screen shot or a build.
11.
Continue developing/contributing to the android community
... and don't forget to thank FatTire and inportb for allowing me to alter and post this script, which made this possible

5/6
Reserved for instructions on how to use different sourcecodes
And things of that nature.

What works if you start building here:
The beginnings of the stuff that makes it BOCA, which include:
auto beagleboard patch
auto cherry pick of cyanogen vold that allows the use of the 4th vold partition (this has been merged)
A bit more HW accel
better video playback in YouTube and your movie files.
better quadrant score
better linpack score
address space layout randomization, as part of the install
WIFI (but takes a long time for the first connection)
Bluetooth
GPS
Accelerometer
Gyroscope
Light
Magnetic field
Orientation
Battery stats
Sound and sound recording
root
a bit of HW acceloration
better video playback (encode/decode)
recent apps button
Auto rotation (for launcher rotation, enable it in CM launcher)
Gallery
Flash
DSP Manager!!!
USB pc trickle charge
Market
Voodoo Sound
sdcard mounts are: internal (sdcard) and emmc (external sd)
USB PC mounting
NOT WORKING SO FAR:
Phone?
Things may/may not be added at some point in the future. You should have no expectations that they will. Anyone who asks for an ETA for something or other gets collectively stoned by the crowd.
Hopefully this project will push some to help fix a few things, as all that is on the NOT WORKING list is NOT WORKING in all and any SGT7 CM9 ports
DO NOT POST BUGS!!!!
ONLY POST "FIXES, OR THINGS THAT HELP FURTHER DEVELOPMENT
THANKS:
JT1134
Fattire
inportb
Spacemoose1
Teknomancer
Github
AOSP
Google (both its search engine and os)
Especially all the sgt7 tab developers
& all android Developers
This list could go on forever!​

Diz, you did it again. Cheers.
Sent from my GT-P1000 using xda premium

massive thread update
REMEMBER, this is still a WIP

We are so lucky to have you here diz. I will send my fourth donation to you at the end of this month! Thank you for educating us so we can learn how to contribute. I would not be surprised if this will be adopted by the whole XDA-community.
EDIT: Happy birthday!
EDIT 2: Is this related to the repo problem at the top of post #1? http://pastebin.com/Hb5rAUFr
Sent from my GT-P1000 using xda premium

stekarson said:
EDIT 2: Is this related to the repo problem at the top of post #1? http://pastebin.com/Hb5rAUFr
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
EDIT
open the makefile
look for these lines:
Code:
else
cd ${SYSTEM}; repo init -u git://github.com/CyanogenMod/android.git -b ics
endif
curl http://pastebin.com/raw.php?i=AGP6wn42 > ${SYSTEM}/.repo/local_manifest.xml
## removes old files and allows init to start from scratch
change it to:
Code:
cd ${SYSTEM}; repo init -u git://github.com/CyanogenMod/android.git -b ics
endif
## removes old files and allows init to start from scratch
then go to android folder, press Ctrl H (to see all the files) and delete everything except the make file.
Then:
in your terminal, in the android directory:
Code:
make init
make sync
Now get the needed files, from the location on the top of the OP.
Place them.
THEN:
Code:
make build
make snapshot
make package CLEAN=1
As soon as its second party verified, I'll update op
From http://review.cyanogenmod.com/p/CyanogenMod/android_system_vold
* branch refs/changes/77/11277/1 -> FETCH_HEAD
# Not currently on any branch.
nothing to commit (working directory clean)
make: *** [sync] Error 1
That just means it has been merged, there is no longer a need to cherry pick it.
Ill take the code out.
This does not ruin your sync.
simple proceed to make build

http://
www.teamovercome.net/common/xDA-Badge-ProudUser.png[/
IMG][/URL]
[B][url]www.teamovercome.net[/
url][/B]: [I][COLOR="Red"]Home of The Overcome ROM
Overcome Kernel ![/COLOR][/I][/LEFT]​

op updated with new directions and a new makefile.
this way we can sync pure cm9 source, and add the vendor and device files of our choice.
And we also don't ever have to worry about "make sync" conflicting with any of the device specific files and causing a sync error.
Although, at this time, I do recommend the files listed in the instructions to get the results implied in post #3

update 1/9
uploaded new makefile:
removed cherry pick vold, it was merged, so no need to clutter the script and get empty repo errors.

First of all thanks for your great work. Im trying to use your guide but got stuck at the "make init" command. If I use this command I get the following error:
Code:
rm /home/lesley/android/sign.tgz /home/lesley/android/update-lite.tgz
if ! grep -q "0x2080" /home/lesley/android/.android/adb_usb.ini; then echo 0x2080 >> /home/lesley/android/.android/adb_usb.ini; fi
cd /home/lesley/android/system; repo init -u git://github.com/CyanogenMod/android.git -b ics
/bin/sh: repo: Permission denied
make: *** [init] Error 126
Nevermind deleted all the folders in the android folder except the make file. After that I did "make init" and it run great.

The make file chmods the bin folder,
Sometimes a reboot is needed for it to take effect.
But sometimes you will still get an issue with bin permissions or paths
Then try this in terminal in the same directory you use the make init command.
Code:
PATH="$HOME/bin:$PATH"
Then
Make build as usual

dizgustipated said:
The make file chmods the bin folder,
Sometimes a reboot is needed for it to take effect.
But sometimes you will still get an issue with bin permissions or paths
Try his in terminal in the same directory you use the make init command.
Code:
PATH="$HOME/bin:$PATH"
Click to expand...
Click to collapse
Thanks, I deleted the folders/files in the android directory except the make file. After that it worked great it's now syncing.

Thank you so much diz !
Making my own CM9 is so damn exciting !!
looking at the instructions , looks easy
Thanks again .
To do list on 15th Jan ( after exam )
Make my own CM9
Diz you are the best !!
Oh btw sorry for this useless post !

I'm stuck at step 5.. how can I download these files....
And what files should be in these folders
Sent from my LG-P999 using Tapatalk
---------- Post added at 05:44 PM ---------- Previous post was at 05:29 PM ----------
tried to follow from step 5 and got this....
http://pastebin.com/vRw7U0Zq
Edit: downloaded whole commit from your git. Included is android folder, device_Samsung_galaxytab folder and Samsung/galaxytab folder
Using cdesi cm9 folder as reference, copied contents in device_Samsung_galaxytab folder. Into Samsung/galaxytab folder then.put that into device folder under android/system then ran step 6b and now it seems to be building since.I have a out folder atm
Edit 2: got same error again. Can you be more specific in your instructions?

Just for p1000 tabs, right? Or for p1010 too?

samcortez said:
Just for p1000 tabs, right? Or for p1010 too?
Click to expand...
Click to collapse
There wont.be support for wifi only.tab......
Sent from my LG-P999 using Tapatalk

samcortez said:
Just for p1000 tabs, right? Or for p1010 too?
Click to expand...
Click to collapse
as the title states, GSM/CDMA?
your device is basically a different device, altogether.
Does your device have cm7 yet?
ayysir said:
tried to follow from step 5 and got this....
http://pastebin.com/vRw7U0Zq
Click to expand...
Click to collapse
yeah thats all part of the original repo error, that i will be fixing today.
But in the mean-time,
navigate to android/system/vendor/cm
open: vendorsetup.sh
add:
add_lunch_combo cm_galaxytab-userdebug
close and save
now make build again

dizgustipated said:
as the title states, GSM/CDMA?
your device is basically a different device, altogether.
Does your device have cm7 yet?
yeah thats all part of the original repo error, that i will be fixing today.
But in the mean-time,
navigate to android/system/vendor/cm
open: vendorsetup.sh
add:
add_lunch_combo cm_galaxytab-userdebug
close and save
now make build again
Click to expand...
Click to collapse
What about galaxytab folder
Sent from my LG-P999 using Tapatalk

The links at step 5 is 404.

[Guide] Building from sources [Kernel only for now]

Hello everyone.
This guide will help you in building a kernel from source for your Nexus 10
Later, when 4.2 hits AOSP, i'll add a guide for building that too
You will need a computer running Linux / OSX to build the kernel, natively, or via a VM.
This guide assumes you’re running any Linux distro.
Getting a toolchain:
You need a toolchain to build the kernel.
The preferred one is Google’s toolchain, the same they use to build AOSP.
In a terminal, type:
Code:
git clone [url]https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/[/url]
export PATH=$PATH:$(pwd)/arm-linux-androideabi-4.6/bin
export CROSS_COMPILE=arm-linux-androideabi-
TIp: paste the export statements in your ~/.bashrc to have them exported each login.
Getting the kernel source:
The kernel source for Nexus devices is available from Google’s servers.
Source : https://android.googlesource.com/kernel/exynos
Github Mirror: https://github.com/chirayudesai/android_kernel_exynos
Open the terminal, and type the below commands to get the kernel source on your computer.
Code:
mkdir -p android/kernel
cd android/kernel
For Nexus 10, we get the exynos kernel sources.
Code:
git clone [url]https://android.googlesource.com/kernel/exynos[/url]
Next, we change our directory to the newly fetched source.
Type
Code:
cd exynos
Figuring out what to build:
Now, we need to figure out which revision to build.
You need to be exactly sure about this, otherwise there are chances that the compiled kernel won’t work.
The commit to build upon can be found by a few ways.
To get the kernel sources matching the device tree, type the below in the device tree.
Code:
git log kernel
Then type the below in the kernel tree
Code:
git checkout <commit>
The commit of the version running on the current review units is 52f6ab1 (probably), which is same as branch android-exynos-manta-3.4-jb-mr1-fr .
Compiling:
Name of defconfig: manta_defconfig
cd to the directory of the kernel source, then type the below in a terminal.
Code:
export ARCH=arm
export SUBARCH=arm
Code:
make <name_of_defconfig>
make
The kernel image will be ready at arch/arm/boot/zImage
To flash it, you need to make it into a boot.img, more on that later. when we have more sources.

Nice work, it's been nice to see some instructions on building additional kernel modules too.
Sent from my GT-I9300 using Tapatalk 2

Great guide! I look forward to seeing your tutorial on compiling 4.2 from source .
Sent from my SCH-I535 using xda premium

Super awesome! I'm currently thoroughly:good: learning the rom building process with my nexus... ill get to this!

looking forward towards the development

Great! This is very helpful and useful

hey man, i got stuck at this point
Code:
git log kernel
it gives me this error
Code:
fatal: ambiguous argument 'kernel': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
didn't really get that point... thanks :good:

matt95 said:
hey man, i got stuck at this point
Code:
git log kernel
it gives me this error
Code:
fatal: ambiguous argument 'kernel': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
didn't really get that point... thanks :good:
Click to expand...
Click to collapse
It has to be typed in the device tree, which hasn't hit AOSP yet, but should soon.
Sent from my GT-P1000

cdesai said:
It has to be typed in the device tree, which hasn't hit AOSP yet, but should soon.
Sent from my GT-P1000
Click to expand...
Click to collapse
oh, now i get this :good:

i was able to make a build tonight from aosp, waiting for my device to arrive & then ill be able to test. but as far as i could tell the output sizes were pretty on compared to the factory image files i extracted http://renzy.me/aoi
...just realized i didnt extract proprietary binaries.

Hello, Cdesai.
Thanks for your guide!
I will do my best to learn it.

so you say that you need to make the zImage into a boot.img (being a noob about this...) on my SGSII, I can flash zImages and boot.img, so I'm confused, lol

jrod091 said:
so you say that you need to make the zImage into a boot.img (being a noob about this...) on my SGSII, I can flash zImages and boot.img, so I'm confused, lol
Click to expand...
Click to collapse
i think it depends on how youre flashing. with the sgsii youre prob using odin/heimdall & it might just overwrite the kernel. flashing with fastboot might require the boot.img cause it contains a ramdisk image after the kernel & is writing a partition. thats just my guess at least, someone else might have a better/more accurate answer for ya

renzyyy said:
i think it depends on how youre flashing. with the sgsii youre prob using odin/heimdall & it might just overwrite the kernel. flashing with fastboot might require the boot.img cause it contains a ramdisk image after the kernel & is writing a partition. thats just my guess at least, someone else might have a better/more accurate answer for ya
Click to expand...
Click to collapse
yeah that's true, but for instance with HTC S-OFFed devices you don't even need to flash the boot.img....

cdesai said:
... To flash it, you need to make it into a boot.img, more on that later. when we have more sources.
Click to expand...
Click to collapse
you can extract the contents from the factory image & use getramdisk.py to get the ramdisk.img out of the current boot.img (or use this ramdisk.img)
then once youve compiled the kernel successfully, use mkbootimg from android_bootimg_tools.tar.gz to repack your boot.img.
if you want to just test...
fastboot boot [new-boot.img]
and flash if satisfied...
fastboot flash boot [new-boot.img]
just tested out if anyone wants some verification... screenshot

@cdesai, shouldn't we be using arm-eabi- instead of arm-linux-androideabi- as CROSS_COMPILE
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
export PATH=$PATH:$(pwd)/arm-eabi-4.6/bin
export CROSS_COMPILE=arm-eabi-
Building with arm-linux-androideabi- causes issues with kernel modules... here's an example of such an issue https://groups.google.com/forum/?fromgroups=#!topic/android-kernel/dzEIOVuxtEo
And the most updated kernel branch is android-exynos-manta-3.4-jb-mr1 not android-exynos-manta-3.4-jb-mr1-fr

Is there any chance of this becoming an OC kernel in the future?

craigacgomez said:
@cdesai, shouldn't we be using arm-eabi- instead of arm-linux-androideabi- as CROSS_COMPILE
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
export PATH=$PATH:$(pwd)/arm-eabi-4.6/bin
export CROSS_COMPILE=arm-eabi-
Building with arm-linux-androideabi- causes issues with kernel modules... here's an example of such an issue https://groups.google.com/forum/?fromgroups=#!topic/android-kernel/dzEIOVuxtEo
And the most updated kernel branch is android-exynos-manta-3.4-jb-mr1 not android-exynos-manta-3.4-jb-mr1-fr
Click to expand...
Click to collapse
Yes, I couldn't get md4 and cifs modules to load with arm-linux-androideabi-4.6:
<3>[ 1250.492203] md4: unknown relocation: 27
<4>[ 1260.230901] cifs: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
However, with this:
git clone https://android.googlesource.com/platform/prebuilt
export PATH=$PATH:$PWD/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
export CROSS_COMPILE=arm-eabi-
The modules load okay:
[email protected]:/mnt/shell/emulated/0 # lsmod
cifs 269223 0 - Live 0x00000000
md4 3442 0 - Live 0x00000000
(Now I have to work out why neither mount nor cifsmanager are working as expected...)

sam3000 said:
Yes, I couldn't get md4 and cifs modules to load with arm-linux-androideabi-4.6:
<3>[ 1250.492203] md4: unknown relocation: 27
<4>[ 1260.230901] cifs: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
However, with this:
git clone https://android.googlesource.com/platform/prebuilt
export PATH=$PATH:$PWD/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
export CROSS_COMPILE=arm-eabi-
The modules load okay:
[email protected]:/mnt/shell/emulated/0 # lsmod
cifs 269223 0 - Live 0x00000000
md4 3442 0 - Live 0x00000000
(Now I have to work out why neither mount nor cifsmanager are working as expected...)
Click to expand...
Click to collapse
I know the reason... busybox needs to be patched... i guess it's something new in 3.4.5 kernel... I haven't done the patch yet
https://github.com/OpenELEC/OpenELEC.tv/commit/f66041febdb07d13a158dab5da901d208cf4fff9

craigacgomez said:
I know the reason... busybox needs to be patched... i guess it's something new in 3.4.5 kernel... I haven't done the patch yet
https://github.com/OpenELEC/OpenELEC.tv/commit/f66041febdb07d13a158dab5da901d208cf4fff9
Click to expand...
Click to collapse
I had actually just got to the point of realising I could make it work by explicitly setting the unc path in mount command options. The missing patch would explain it.

Kernel Compiling Problem

Hello!
I need to say this first : i'm a newbie at development but i want to learn.
I succesfully managed to compile CM9 from CyanogenMod sources but i have some problems trying to compile mike's cm10.1 kernel.I followed his tutorial changing smultron to zeus in terminal,it gave me something about trying dependecies only and then moved on(tried with smultron too and same message) .It compiles for about half hour and then it says :
Code:
host StaticLib: libLLVMCore (/home/filip/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/libLLVMCore.a)
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/filip/android/system/kernel/semc/msm7x30'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
[email protected]:~/android/system$
The changes I have made to the kernel where to change the input drivers from him with the input drivers from DoomLord 3.4 kernel for msm7x30 zeus branch , but I don't think this is the main reason of this error.
EDIT: Compiled succesfully with the input folder from mike's sources.Any idea how to resolve the problem with the input folder from DoomLord ? in his git he says the the touchscreen problem is resolved.
EDIT 2: New error:
Code:
scripts/kconfig/conf --silentoldconfig Kconfig
GEN /home/filip/android/system/out/target/product/zeus/obj/KERNEL_OBJ/Makefile
CHK include/linux/version.h
Using /home/filip/android/system/kernel/semc/msm7x30 as source for kernel
CHK include/generated/utsrelease.h
make[3]: `include/generated/mach-types.h' is up to date.
CALL /home/filip/android/system/kernel/semc/msm7x30/scripts/checksyscalls.sh
CHK include/generated/compile.h
GZIP kernel/config_data.gz
CHK kernel/config_data.h
UPD kernel/config_data.h
CC kernel/configs.o
CC drivers/input/touchscreen/cy8ctma300_touch.o
LD kernel/built-in.o
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:185:28: error: expected ')' before 'int'
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:186:32: error: expected ')' before string constant
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c: In function 'perform_reset':
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:488:2: error: implicit declaration of function 'gpio_set_value' [-Werror=implicit-function-declaration]
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:492:2: error: implicit declaration of function 'gpio_get_value' [-Werror=implicit-function-declaration]
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c: At top level:
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1104:13: error: 'THIS_MODULE' undeclared here (not in a function)
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1106:2: error: unknown field 'ioctl' specified in initializer
/home/filip/android/system/kernel/semc/msm7x30/drivers/input/touchscreen/cy8ctma300_touch.c:1106:2: warning: initialization from incompatible pointer type [enabled by default]
error, forbidden warning: cy8ctma300_touch.c:1106
make[5]: *** [drivers/input/touchscreen/cy8ctma300_touch.o] Error 1
make[4]: *** [drivers/input/touchscreen] Error 2
make[3]: *** [drivers/input] Error 2
make[2]: *** [drivers] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/filip/android/system/kernel/semc/msm7x30'
make: *** [TARGET_KERNEL_BINARIES] Error 2
I attached cy8ctma300_touch.c

sorry.. of topic.. but thanks.. thanks for Trying .. for yourself and Us.. .. I hope someone can answer that.

I tried to compile kernel with cy8ctma300_touch.c from Wedgess's 2.6 kernel from
[DEV][WIP][PLAY] cm 10.1 & pac 4.2 [ROM][KERNEL][4.2.2][UPDATED 21-03-13] and i got exactly same error
As you said, CM10.1 compile without errors with it's own cy8ctma300_touch.c
I'll look into it as much my limited knowledge about linux/kernel things alow me (noob here also, this was my very first rom/kernel compiled from source )

Bakisha said:
I tried to compile kernel with cy8ctma300_touch.c from Wedgess's 2.6 kernel from
[DEV][WIP][PLAY] cm 10.1 & pac 4.2 [ROM][KERNEL][4.2.2][UPDATED 21-03-13] and i got exactly same error
As you said, CM10.1 compile without errors with it's own cy8ctma300_touch.c
I'll look into it as much my limited knowledge about linux/kernel things alow me (noob here also, this was my very first rom/kernel compiled from source )
Click to expand...
Click to collapse
I also want to get into Kernel Compiling.. and ROM compiling of course.. can anyone suggest me is my computer specs enough for compiling and Dual Booting Windows 8 and Ubuntu.. (should I even use Ubuntu ?? or any other distro.. plz recommend) .
My Computer Specs are
4GB Ram
Intel Core 2 Duo CPU T9300 @ 2.50 Ghz
650gb HD
Windows 8 Pro 64 Bit.

yes , it's enough . I don't know if you could resolve anything but you can try . there are a lots of guides on the net about how to do this.

Bakisha said:
I tried to compile kernel with cy8ctma300_touch.c from Wedgess's 2.6 kernel from
[DEV][WIP][PLAY] cm 10.1 & pac 4.2 [ROM][KERNEL][4.2.2][UPDATED 21-03-13] and i got exactly same error
As you said, CM10.1 compile without errors with it's own cy8ctma300_touch.c
I'll look into it as much my limited knowledge about linux/kernel things alow me (noob here also, this was my very first rom/kernel compiled from source )
Click to expand...
Click to collapse
ChunkFlip said:
yes , it's enough . I don't know if you could resolve anything but you can try . there are a lots of guides on the net about how to do this.
Click to expand...
Click to collapse
what distro to use.. lubuntu,, xubuntu.. Ubuntu.. ? which is most stable for android compiling.. and I might start using it as daily driver besides Windows as well.. (don't think so., but maybe.. hehe)

saqibkhan said:
what distro to use.. lubuntu,, xubuntu.. Ubuntu.. ? which is most stable for android compiling.. and I might start using it as daily driver besides Windows as well.. (don't think so., but maybe.. hehe)
Click to expand...
Click to collapse
I'm using Ubuntu 13.10 x64 in Virtualbox. I firstly tried 12.04 LTS but it gave me nothing but trouble in virtualbox.
As in OP, i followed Mike's guide to build from source
As for initial setting up ubuntu i followed this guide and lot of "googling" (basicly, whatever error i get, i copy that text and paste it to google search).
But be warned, source is at least 15GB, it can take some time to download. Plus, compiling time (at least for me) is 3 or 4 hours (if building only kernel, it's shorter, about half an hour)
My progress is very slow, don't have much time for testing, but so far i found that maybe error is not in Mike's cy8ctma300_touch.c but rather difference in kernel between 2.6 and 3.4 . For example, it compile ok if in line 1106 in wedgess cy8ctma300_touch.c i enter ".unlocked_ioctl" instead of just ".ioctl" but touchscreen don't work still. In Mike's kernel there is already line with ".unlocked_ioctl" so it don't give error when compiling.
I still have to try something i found on web, but i don't know will i be able to do it this weekend...

Bakisha said:
I'm using Ubuntu 13.10 x64 in Virtualbox. I firstly tried 12.04 LTS but it gave me nothing but trouble in virtualbox.
As in OP, i followed Mike's guide to build from source
As for initial setting up ubuntu i followed this guide and lot of "googling" (basicly, whatever error i get, i copy that text and paste it to google search).
But be warned, source is at least 15GB, it can take some time to download. Plus, compiling time (at least for me) is 3 or 4 hours (if building only kernel, it's shorter, about half an hour)
My progress is very slow, don't have much time for testing, but so far i found that maybe error is not in Mike's cy8ctma300_touch.c but rather difference in kernel between 2.6 and 3.4 . For example, it compile ok if in line 1106 in wedgess cy8ctma300_touch.c i enter ".unlocked_ioctl" instead of just ".ioctl" but touchscreen don't work still. In Mike's kernel there is already line with ".unlocked_ioctl" so it don't give error when compiling.
I still have to try something i found on web, but i don't know will i be able to do it this weekend...
Click to expand...
Click to collapse
I think if Ubuntu is installed as a separate Operating system.. it would take less time to build.. 3-4 hours is tooo long.. anyways.. I am going to install it DUal boot it with Windows 8.. and start compiling then.

CM12.1 building thread for Moto X Pure devs

Let's get a ROM building thread working for the devs working on the project.
Using my source, you can compile a booting CM12.1 ROM
Working so far:
Boots
Audio
Camera/Camcorder
Video playback
Phone
4G LTE
Sensors
Not working:
Everything else (probably)
Device: https://github.com/JackpotClavin/android_device_moto_clark
Vendor: https://github.com/JackpotClavin/android_vendor_motorola_clark
Kernel: https://github.com/MotorolaMobilityLLC/kernel-msm, branch lollipop-5.1.1-release-clark
Things that I know are missing/broken,
1. I'm missing a bunch of /etc/firmware files relating to audio. As far as I know it has no effect on in call audio as it doesn't work if they are all pushed there or not.
2. Bluetooth will continuously force close, so when you extract the zip you build in recovery, you will have to rename /system/app/Bluetooth/Bluetooth.apk to Bluetooth.bak
3. You will have to set your preferred network type to LTE to get a radio signal

Finally something dropping for the PURE. Thank you

Slim running also. In call audio is working here as well
Sent from my XT1575 using Tapatalk

They're beautiful, keep up the good work, gents!

I can't wait!!
Sent from my XT1575 using Tapatalk

Absolutely amazing, I've been waiting for something to come out. Hopefully a kernel is soon to follow!

Mind pm'ing me on hangouts?
Sent from my XT1575 using Tapatalk

JackpotClavin said:
Let's get a ROM building thread working for the devs working on the project.
Using my source, you can compile a booting CM12.1 ROM
Click to expand...
Click to collapse
JackpotClavin,
Really excited to see that you're developing for the Moto X! I ran your roms on my vs980 for a long time and it was fantastic.
Great work!
Sent from my XT1575 using Tapatalk

After being on a locked down phone for the last four months, I am so looking forward to flashing ROMs again. You guys can't get these out fast enough.

I spent tonight setting up a build environment, I want to at least get CM12.1 booting on my device so I can judge it's performance vs stock Android, bugs or not.
Haven't built a ROM in years, so i'm a bit rusty, right now the build is breaking on:
Code:
/android/clark/roms/cm/kernel/moto/clark/scripts/kconfig/Makefile:108: recipe for target 'msm8994-perf_defconfig' failed
make[3]: *** [msm8994-perf_defconfig] Error 1
/android/clark/roms/cm/kernel/moto/clark/Makefile:512: recipe for target 'msm8994-perf_defconfig' failed
make[2]: *** [msm8994-perf_defconfig] Error 2
Makefile:135: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
I'll tinker with it tomorrow, probably missed a step while tweaking the kernel source to match the device.

breakingspell said:
I spent tonight setting up a build environment, I want to at least get CM12.1 booting on my device so I can judge it's performance vs stock Android, bugs or not.
Haven't built a ROM in years, so i'm a bit rusty, right now the build is breaking on:
Code:
/android/clark/roms/cm/kernel/moto/clark/scripts/kconfig/Makefile:108: recipe for target 'msm8994-perf_defconfig' failed
make[3]: *** [msm8994-perf_defconfig] Error 1
/android/clark/roms/cm/kernel/moto/clark/Makefile:512: recipe for target 'msm8994-perf_defconfig' failed
make[2]: *** [msm8994-perf_defconfig] Error 2
Makefile:135: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
I'll tinker with it tomorrow, probably missed a step while tweaking the kernel source to match the device.
Click to expand...
Click to collapse
Well the kernel source @JackpotClavin linked is not really cm/custom rom friendly.
Use this kernel source https://github.com/Thecrazyskull/kernel-msm (branch cm-12.1) and change msm8994-perf_defconfig in BoardConfig.mk (in your device tree) to clark_defconfig and build again

Thecrazyskull said:
Well the kernel source @JackpotClavin linked is not really cm/custom rom friendly.
Use this kernel source https://github.com/Thecrazyskull/kernel-msm (branch cm-12.1) and change msm8994-perf_defconfig in BoardConfig.mk (in your device tree) to clark_defconfig and build again
Click to expand...
Click to collapse
Thanks much! It's been building for about 45 minutes now without any issues, probably won't have much longer to go.
Edit: Build broke again after an hour and a half, but looks like it was a Java library i'd missed during the initial environment setup. Got a 50GB cache ready too, hopefully it'll speed up each build attempt. This is a learning experience, hopefully i'll be able to cook up my own nightlies once the official branch goes live Infinite kudos to everyone that's put in this work so far!

Beautiful. I can't wait to see a somewhat stable build. Very exciting ?
Sent from my XT1575 using XDA Free mobile app

now I can't wait even more! omg thank you devs
this excites me already! overlay Enable VoLTE in config. 4 days ago

I gave up on building the ROM from source, a bit daunting for my skill level. Something kept making it hang near the end of the build process (2 hours or so each try), and I've got no problem waiting a while longer for a more stable build rather than trying to find out what's broken on my own. Doesn't keep me from checking back in 3 or 4 times a day though, hah.

breakingspell said:
I gave up on building the ROM from source, a bit daunting for my skill level. Something kept making it hang near the end of the build process (2 hours or so each try), and I've got no problem waiting a while longer for a more stable build rather than trying to find out what's broken on my own. Doesn't keep me from checking back in 3 or 4 times a day though, hah.
Click to expand...
Click to collapse
Mind posting the actual error?

Thecrazyskull said:
Mind posting the actual error?
Click to expand...
Click to collapse
The process would hang up on
Code:
make: *** Waiting for unfinished jobs....
I'm building it on my Debian server, i'm certain I have all of the dependencies and repos set right, it'll compile for roughly 2 hours and then hang on the make command for 2+ hours. Went ahead and made a new project folder so I can re-sync everything, I'll give it a try again tomorrow.

breakingspell said:
The process would hang up on
Code:
make: *** Waiting for unfinished jobs....
I'm building it on my Debian server, i'm certain I have all of the dependencies and repos set right, it'll compile for roughly 2 hours and then hang on the make command for 2+ hours. Went ahead and made a new project folder so I can re-sync everything, I'll give it a try again tomorrow.
Click to expand...
Click to collapse
You didnt post the actual error

Thecrazyskull said:
You didnt post the actual error
Click to expand...
Click to collapse
I'll keep an eye out next time I try and build it, hadn't caught any errors in the actions leading up to that line, it might have been much earlier in the process

Hi,
A quick post to let you know guys I successfully made a "blind" PAC build for clark with device tree & kernel provided here. I don't have the device for now (maybe later), so can't test it. Dunno if it's working or not.

Building Unlegacy Android

Hi all,
not sure if this is the correct place to post, please move it in case this should be in another forum.
Im planning on start building my own rom based on Unlegacy for my maguro. Havent found anything specific to this project so once im done i will document how to get it done so that others can use it as a reference.
Have been reading over the weekend and i think im quite clear how this works even if it would be the first time i do sth. like this in android world. So please bear with me !
I have contributed several times to the linux kernel and gentoo linux and developed for some other (closed source) projects many years ago which means im an old school guy and im completely disonnected from "modern" development.
I know how to build, patch, debug c and so on but i have almost zero knowledge about git and some of the other tools that are used nowadays. Furthermore i have almost no idea about android itself, im planning on reading more about it to at least know what im doing before getting messy.
Here my first questions, more to come im sure :
- first things first : is there documentation available somewhere specific to this project ?
- im syncing right now. So far it has downloaded 36 GB and repo says it is at 93 % ... is this normal ??? I know android projects are huge but this sounds to me like im doing sth. wrong. Isnt there a way to just sync what i need for tuna ? Am i supposed to tune the manifests to just sync what i need ?
- toolchain : i have seen while it synced several toolchains already. IIRC there were some problems with modern toolchains and gcc-4.7 should be used to avoid some problems with the buggy mmc. Is this still correct or can i just give gcc 5.x a go ? Im asking because thats the toolchain im using right now.
- kernel source : are there other more updated sources available apart from the ones in this tree ?
- build times : im used to long build times. Years ago when we built some huge c++ projects it took days to finish even with the huge buildfarm we had at our dispossal. What build times can i expect with a regular android build like this one ? I have a i7 with 8 cores at 3,5 MhZ and 16 GB Ram available and could even use another similar box with distcc if necessary.
Would really appreciate if someone could sched some light over this and let me have some tips / tricks to avoid further problems.
I have the feeling that some guides im reading are pointless because they are outdated.
Thanks !

Unlegacy Android follows and combines the OMAP4- and Grouper Android OpenSource Project which were created in late 2015 in order to maintain a clean, organized place for pure AOSP support for various OMAP4 and Grouper devices.
The goal is to provide stable and optimized releases of the recent Android versions for the supported devices.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt our changes.
The source is combined power from multiple devs, you won't find a newer kernel or device source for it.
Why there's no official thread yet? We are still preparing our source and some stuff around for best user experience. The source compiles as it is, no need to change anything for tuna.
You should be patient and wait until the stuff is "official official" available, our freetime is limited and we do our best to get things running.

Android-Andi said:
Unlegacy Android follows and combines the OMAP4- and Grouper Android OpenSource Project which were created in late 2015 in order to maintain a clean, organized place for pure AOSP support for various OMAP4 and Grouper devices.
The goal is to provide stable and optimized releases of the recent Android versions for the supported devices.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt our changes.
The source is combined power from multiple devs, you won't find a newer kernel or device source for it.
Why there's no official thread yet? We are still preparing our source and some stuff around for best user experience. The source compiles as it is, no need to change anything for tuna.
You should be patient and wait until the stuff is "official official" available, our freetime is limited and we do our best to get things running.
Click to expand...
Click to collapse
thanks, wasnt actually pushing to know how the current state of thing is, was more about knowing if im doing things correctly.
I have built succesfully a couple of N roms for my maguro and im learning how to cherrypick and reading more about the android frameworks.
thanks !

have just synced and got this when trying to build :
Code:
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
make[1]: *** No hay ninguna regla para construir el objetivo 'dtbs'. Alto.
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
make[1]: *** [/usr/src/droid/kernel/samsung/tuna/Makefile:1144: modules] Error 1
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
make: se entra en el directorio '/usr/src/droid/kernel/samsung/tuna'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
make[1]: *** [/usr/src/droid/kernel/samsung/tuna/Makefile:1144: modules_install] Error 1
make: *** [Makefile:130: sub-make] Error 2
make: se sale del directorio '/usr/src/droid/kernel/samsung/tuna'
[ 33% 9805/29540] target thumb C++: libLLVMCore <= external/llvm/lib/IR/LLVMContext.cpp^Cmake: *** [build/core/ninja.mk:149: ninja_wrapper]
no idea why it complains about dtbs or module support being disabled.
where is the kernel .config file stored by the way ?
any ideas ?
thanks !

thagringo said:
- im syncing right now. So far it has downloaded 36 GB and repo says it is at 93 % ... is this normal ??? I know android projects are huge but this sounds to me like im doing sth. wrong. Isnt there a way to just sync what i need for tuna ? Am i supposed to tune the manifests to just sync what i need ?
Click to expand...
Click to collapse
When building cyanogenmod I can reduce it to about 5GB with this repo init:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0 --depth=1 --groups=all,-notdefault,-device,-darwin,-x86,-mips,-exynos5,-intel,-eclipse,-device
b specifies the branch you want and means you don't get the whole tree.
The --groups excludes a bunch of stuff you don't want/need (mostly different platforms).
The depth command means that only the last version is checked out and not the whole history.
However, if you are creating a new ROM with this a base you might want the history.
Since this is a Developers forum, it would be nice if ROM posters actually put the build instructions in their posts and didn't just link to github and force you to search through 10s of different repos looking for info though.

opticyclic said:
When building cyanogenmod I can reduce it to about 5GB with this repo init:
b specifies the branch you want and means you don't get the whole tree.
The --groups excludes a bunch of stuff you don't want/need (mostly different platforms).
The depth command means that only the last version is checked out and not the whole history.
However, if you are creating a new ROM with this a base you might want the history.
Since this is a Developers forum, it would be nice if ROM posters actually put the build instructions in their posts and didn't just link to github and force you to search through 10s of different repos looking for info though.
Click to expand...
Click to collapse
Nice, thanks a lot !!
For now I have given up and I'm waiting for things to settle down.
Cheers mate !

I'm taking the same W&S Attitude about Building
thagringo said:
Nice, thanks a lot !!
For now I have given up and I'm waiting for things to settle down.
Cheers mate !
Click to expand...
Click to collapse
That is why I am taking the same wait and see attitude about building (though I AM actually running this on my toro-variant GNex on Tracfone; because it's unified, this same ROM will run on maguro).
Since then, I have grabbed AOSP 8.0 (latest branch) and I'm trying to compile (with new branch in place) and I'm running into a headache post-breakfast (breakfast is fine). Where things fall down is between brunch and lunch (in fact, it is during brunch where things fall down). I'm thinking that the falldown is because things are still fluid, so I'll keep the eyes peeled.

PGHammer said:
That is why I am taking the same wait and see attitude about building (though I AM actually running this on my toro-variant GNex on Tracfone; because it's unified, this same ROM will run on maguro).
Steps to take (from stock via Skipsoft Unified Toolkit):
1. Unlock and root (reboot following this step)
2. Flash TWRP 2.7.1.0 and reboot.
3. Upgrade TWRP to 2.8.7.0 and reboot.
4. Download both the firmware and GApps 7.1 pico (as is the case with GApps 6.0, nano is too large for any GNex) and push them to your phone, then force a reboot to recovery (which SHOULD be TWRP 2.8.7.0).
5. Install (in order) aosp_7.1_tuna2016-10-21 (latest as I type this) and open_gapps-arm-7.1-pico.zip. Wipe cache and reboot after the last install.
Click to expand...
Click to collapse
well, yes, i have been using 7.1 for a couple of months already but i was actually trying to build my own with the gcore stuff patches included.
cheers