Develop Bugs

[MOD] SHW-M110S Development (with lagfix/root/voodoo sound kernel)

For SHW-M110s development/discussion. (Korean Anycall SGS ONLY yes for any who don't know, we are officially part of the I9000 forum.
Koe1974 suggested this thread and will I think act as a co-OP on this discussion. Look for front page updates, links, whatever from him 3 posts down, (below the lost guy from China) in the future too.
Version 4 released
Version 4.0r1 released to fix Odin flashing problem
link to kernel
with tegrak_voodoo sound (v2) module, tegrak ext4 module, root (superuser.apk) and busybox 1.17.1 optional, safe mount option overides by default, auto detect lag fixed partitions (improves upgradeability and interchageability) [/B][/size] Compatible with previously z4modded ext2 setups. All ROM versions, SK05 through TA13 tested and released (link is below).
안녕하세요 to any of the Korean developers who find this. Please update us in English about what you are doing. Your English is probably MUCH better than my korean, and I live in Korea.. There are some people in China, Iran, Philippines, etc using this device who might be helped.
-------------------------------------------------------------------------------------------------------------------------
Ext4 (tegrak modules) z4build rooted voodoo sounds kernel link
A stock z4moded kernel with added ext4 support ( presently by "stealing" tegrak kernel modules.) and many tweaks to make it actually work.
This is now working with z4control to get an easy to apply ext4 lag fix!
------------------------------------------------------------------------------------------------------------------------------------
Bug discussion here please, usage discussion (how do get the file into odin?) .. maybe the general thread is better.
For now, our rooting guide is linked from my sig also, although the above linked kernel can also be made to provide root with no effort.
This type of initramfs modification can be done by unpacking a stock kernel making customizations and then applying z4build to it. But I used a z4modded kernel and then applied customizations and repacked. I did this because I set up to repack by hand anyway before knowing I wanted to use z4mod and even then, when I thought I needed to pack into a tegrak kernel (which z4build can't do). It turned out to cause complications, but also taught me a good bit about the process and about z4mod, and probably helped me find bugs.
Some other related useful links for Reference:
kernel extraction (commented by me specifically for tegrak lzma compressed initramfs and z4build split initramfs)
http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
kernel repacking
http://forum.xda-developers.com/showthread.php?t=789712
It needs the initramfs to be cpio'd already something like this:
Code:
cd $initram
find ./ | cpio -H newc -o > $repackdir/newramfs.cpio
It also needs the editor.sh script modified to point to the cross-compiler.
By default it can only pack you initramfs into an image which previously had an uncompressed initramfs. This can be modified though easily.
kernel compiling
This old thread probably isn't too useful now..
http://forum.xda-developers.com/showthread.php?t=740740&page=2
We have much better info 3 posts down by koe1974.
Kernel sources here:
http://opensource.samsung.com/
search SHW-M110S.
The first froyo update has a nice readme with a link to the compiler (I don't have the link right this moment)
Not sure if we need to figure/find .configs, or if the ones included are ok to start. Just need to compile one once and see.
I got my compiler toolchain here:
http://www.codesourcery.com/sgpp/li...1-188-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
I thought it's the one recommended is the original froyo source from samsung, but Koe says they point to 2009 version, so I don't know now.
............
I flashed the korean voodoo sk22 kernel just to boot it into recovery. It has CW mod recovery. Might be useful. (BTW I don't recommend flashing unfamiliar kernels haphazardly, ex: this one injected a file into my ROM that interefered with z4mod until I realized it ) Mine BTW injects only one empty directory (/etc/init.d) and nothing else. Remove the kernel and all other changes dissappear. (z4control adds a tad more, but very little, most of its additions self destruct after use.)

Post reserved.

Post Removed, as requested.
Sent from my GT-I9000 using XDA App

Links:
Korea's equivalent to XDA
Lilinser's GitHub - kernel repack, deodexer, etc.
Project-Voodoo - initramfs (SK05)
Just for hobbies - Voodoo for SL28
Tegrak Kernel
SHW-M110S intramfs Requires further research.
Older M110S from someone at MIT working on the M110S potential resource
bml7 & initramfs possible resource
more initramfs
initramfs SK05 Tested .. OK
How-Tos:
Basic How-To Build Environment with built kernel test

First this diff is from a z4modded stock SL28 image to the custom kernel image. It's not against stock. So it includes tegrak files and scripts I changed. Also note the -N option. It pretends like files that don't exist do.. Any binary files that "differ" are actually added from tegrak.
Code:
diff -rbpN z4mod_sl28/initramfs/init.rc z4grak-construction-sl28/initramfs/init.rc
*** z4mod_sl28/initramfs/init.rc 2011-01-13 02:20:12.000000000 -0500
--- z4grak-construction-sl28/initramfs/init.rc 2011-01-11 07:43:34.000000000 -0500
*************** loglevel 3
*** 58,63 ****
--- 58,72 ----
mount j4fs /dev/block/stl6 /mnt/.lfs
insmod /lib/modules/param.ko
+ #ext4 modules by woo
+ insmod /tegrak/lib/modules/mbcache.ko
+ insmod /tegrak/lib/modules/jbd2.ko
+ insmod /tegrak/lib/modules/ext4.ko
+
+ # tegrak system lagfix by woo
+ #
+ insmod /tegrak/lib/modules/tegrak_module.ko
+
# Backwards Compat - XXX: Going away in G*
symlink /mnt/sdcard /sdcard
*************** service vt /system/bin/vtserver
*** 728,734 ****
#user system
#group system
-
service dumpstate /system/bin/dumpstate -s
socket dumpstate stream 0660 shell log
disabled
--- 737,742 ----
*************** service dumpstate /system/bin/dumpstate
*** 739,747 ****
# oneshot
-
# Added by z4mod
service z4postinit /init
oneshot
--- 747,761 ----
# oneshot
# Added by z4mod
service z4postinit /init
oneshot
+ #install root ingore the mount type, it doesn't matter
+ # syntax looks a little strange to me.. we'll see if it works
+ mount rfs /dev/block/stl9 /system rw remount
+ cat /sbin/su > /system/bin/su
+ chown root /system/bin/su
+ chmod 4755 /system/bin/su
+ mount rfs /dev/block/stl9 /system ro remount
\ No newline at end of file
diff -rbpN z4mod_sl28/initramfs/lpm.rc z4grak-construction-sl28/initramfs/lpm.rc
*** z4mod_sl28/initramfs/lpm.rc 2011-01-13 02:20:12.000000000 -0500
--- z4grak-construction-sl28/initramfs/lpm.rc 2011-01-11 06:37:28.000000000 -0500
*************** on init
*** 16,21 ****
--- 16,26 ----
insmod /lib/modules/param.ko
insmod /lib/modules/vibrator.ko
+ #ext4 modules by woo
+ insmod /tegrak/lib/modules/mbcache.ko
+ insmod /tegrak/lib/modules/jbd2.ko
+ insmod /tegrak/lib/modules/ext4.ko
+
mount rfs /dev/block/stl9 /system check=no
mount rfs /dev/block/mmcblk0p2 /data nosuid nodev check=no
Binary files z4mod_sl28/initramfs/sbin/sslvpn and z4grak-construction-sl28/initramfs/sbin/sslvpn differ
Binary files z4mod_sl28/initramfs/tegrak/bin/mkfs.ext4 and z4grak-construction-sl28/initramfs/tegrak/bin/mkfs.ext4 differ
Binary files z4mod_sl28/initramfs/tegrak/bin/tune2fs and z4grak-construction-sl28/initramfs/tegrak/bin/tune2fs differ
Binary files z4mod_sl28/initramfs/tegrak/lib/modules/ext4.ko and z4grak-construction-sl28/initramfs/tegrak/lib/modules/ext4.ko differ
Binary files z4mod_sl28/initramfs/tegrak/lib/modules/jbd2.ko and z4grak-construction-sl28/initramfs/tegrak/lib/modules/jbd2.ko differ
Binary files z4mod_sl28/initramfs/tegrak/lib/modules/mbcache.ko and z4grak-construction-sl28/initramfs/tegrak/lib/modules/mbcache.ko differ
Binary files z4mod_sl28/initramfs/tegrak/lib/modules/tegrak_module.ko and z4grak-construction-sl28/initramfs/tegrak/lib/modules/tegrak_module.ko differ
I'm a bit confused about sslvpn It's in my SL28 , it's not in my z4moded SL28. everything else diff as expected. Maybe I just lost it, maybe z4mod removed it. It's a small unimportant mystery.
BTW it looks like what I believe are the recovery keys have changed from SK22 to SL28, so maybe using the wrong kernel breaks something.
and my slightly modified version of the extraction script with commented lines to deal with lzma.
it's much faster (well.. why not), and it handles direcories a little better. It need a "/" somewhere in the file name though so use "./zImage".
Code:
#!/bin/bash
#MUCH faster than dd bs=1 skip=blah
#
# syntas is fastdd file skip <length_in_bytes_optional>
# skip is NOT optional and should be set to 0 read from begining.
#
fastdd () {
#dd with a skip is crazy slower cause it forces bs=1
#credit goes to somebody on the internet.
local bs=1024
local file=$1
local skip=$2
local count=$3
(
dd bs=1 skip=$skip count=0 2>/dev/null
if [[ "$count" != "" ]]; then
dd bs=$bs count=$(($count / $bs))
dd bs=$(($count % $bs)) count=1
else
dd bs=1024 2> /dev/null
fi
) < "$file"
}
zImage=$1
basedir=${1%/*}
echo working directory $basedir
mkdir $basedir/initramfs
outdir=$basedir/initramfs/
#========================================================
# find start of gziped kernel object in the zImage file:
#========================================================
pos=`grep -P -a -b -m 1 --only-matching $'\x1F\x8B\x08' $zImage | cut -f 1 -d :`
echo "-I- Extracting kernel image from $zImage (start = $pos)"
echo
echo "*** Start of compressed kernel image:" $pos
#========================================================================
# the cpio archive might be gzipped too, so two gunzips could be needed:
#========================================================================
fastdd $zImage $pos | gunzip > /tmp/kernel.img
pos=`grep -P -a -b -m 1 --only-matching $'\x1F\x8B\x08' /tmp/kernel.img | cut -f 1 -d :`
#
# Use next one for tegrak secuere 11 SL28
# It's an lzma header
# It's found by looking for 5D 00 in the exact same place as cpio (070701) is found in stock.
# The long string of FF's is the real give away since 5D 00 is too vague.
# pos=`grep -P -a -b -m 1 --only-matching '\x{5D}\x{00}\x..\x{FF}\x{FF}\x{FF}\x{FF}\x{FF}\x{FF}' /tmp/kernel.img| cut -f 1 -d :`
echo
echo "*** gzip position in kernel.img :" $pos "(start of gzipped cpio)"
#===========================================================================
# find start and end of the "cpio" initramfs image inside the kernel object:
# ASCII cpio header starts with '070701'
# The end of the cpio archive is marked with an empty file named TRAILER!!!
#===========================================================================
if [ ! $pos = "" ]; then
echo "-I- Extracting compressed cpio image from kernel image (start = $pos)"
# use either one of the next two lines for gzip
# dd if=/tmp/kernel.img bs=1 skip=$pos | gunzip > /tmp/cpio.img
fastdd /tmp/kernel.img $pos |gunzip > /tmp/cpio.img
# comment above and uncomment one of next two lines for lzma, if decompressing tegrak image.
# dd if=/tmp/kernel.img bs=1 skip=$pos | unlzma > /tmp/cpio.img
# fastdd /tmp/kernel.img $pos | unlzma > /tmp/cpio.img
start=`grep -a -b -m 1 --only-matching '070701' /tmp/cpio.img | head -1 | cut -f 1 -d :`
end=`grep -a -b -m 1 --only-matching 'TRAILER!!!' /tmp/cpio.img | head -1 | cut -f 1 -d :`
inputfile=/tmp/cpio.img
else
echo "-I- Already uncompressed cpio.img, not decompressing"
start=`grep -a -b -m 1 --only-matching '070701' /tmp/kernel.img | head -1 | cut -f 1 -d :`
echo start $start
end=`grep -a -b -m 1 --only-matching 'TRAILER!!!' /tmp/kernel.img | head -1 | cut -f 1 -d :`
echo end $end
inputfile=/tmp/kernel.img
fi
end=$((end + 10))
count=$((end - start))
if (($count < 0)); then
echo "-E- Couldn't match start/end of the initramfs image."
exit
fi
echo "-I- Extracting initramfs image from $inputfile (start = $start, end = $end)"
echo inputfile: $inputfile
echo start $start
echo count $count
echo outdir $outdir
# dd if=$inputfile bs=1 skip=$start count=$count > $outdir/initramfs.cpio
fastdd $inputfile $start $count > $basedir/initramfs.cpio
cd $basedir
basedir=`pwd`
cd $outdir; cpio -v -i --no-absolute-filenames < $basedir/initramfs.cpio
cp /tmp/kernel.img $basedir/
More to come.

I like the way this is going, appagom, please put [MOD] in the title.

GL on the new thread, if you hope to have Koreans stumbled upon the thread it might be good to add more phrases like:
루팅
갤럭시s
안드로이드
프로요
업그레이드
업데이트
I never really fully utilized it myself. I hope you get more done here or I'll just take the move personally. Actually, now that you guys were moving into compiling and building I thought this would come. Also, you should look to get some Soju out of this with some donate links or something, even if you aren't looking to take in any cash perhaps you could use it as a seed pot for bounties.
Most importantly, I need to know what "the lost guy from China" said...ㅋㅋㅋ
@Koe, don't waste your time on Gingerbread, get us Honeycomb

Compile a Kernel in 13 Lucky Steps
If you are not familiar with Linux, you might have a hard time following this. Just as I am writing how to do get setup to compile a kernel and compile Android apps, others have written how to setup VirtualBox, Ubuntu, AndroidSDK, etc. Please see documentation provided by Oracle, Google, Ubuntu, etc. before you ask for help about VirtualBox, Ubuntu and the SDK. Thanks.
This is written for people who have used Linux but have not compiled much. Or for the brave at heart who are looking for a nice weekend project. This will tell/guide you through getting a system setup that will not destroy your existing OS.
My host OS is Ubuntu 10.10 64-bit. I wanted had to make an Ubuntu 10.04 32-bit 64-bit system for development because I didn't want to deal with 64-bit vs. 32-bit issues but since Gingerbread requires a 64-bit compiler, I had to. Might as well just use my host system, but since we're here let's keep going!
So you're about to begin. Let's just get one thing straight. No! This will not result in a kernel you can flash. “Then why do this?, you ask. Ask yourself that!
1. Install VirtualBox and the Oracle VM VirtualBox Extension Pack (Currently 4.0.0 r69151)
http://www.virtualbox.org/wiki/Downloads
2. Download an Ubuntu ISO (I suggest Ubuntu Desktop 10.04 64-bit)
http://www.ubuntu.com/desktop/get-ubuntu/download
3. Create a new VM in VirtualBox (You may/have to modify the settings)
Operating System: Linux
Version: Ubuntu64
Extended Features: IO APIC
Processors: 2
RAM: 2048MB
Video Mem: 128MB
HDD: 32GB
Enable PAE/NX
Shared Drive: (I use a shared folder, more detail later)
Click to expand...
Click to collapse
4. Install VirtualBox Guest Additions
5. Install Ubuntu and Update Ubuntu
TIP: Mount your Shared Folder with fstab (Optional but helpful)
If you chose to use a shared folder you can auto-mount it via /etc/fstab.
NOTE: I use a shared folder named andDEV and I mount it on my desktop (~/Desktop). Below is what I add to my /etc/fstab (You may/have to change it)
Code:
andDev /home/koe/Desktop/andDev vboxsf uid=1000,gid=1000 0 0
Click to expand...
Click to collapse
6. Enable multiverse and partner "Software Sources"
7. Install additional software: NOTE: I would also recommend installing preload, but it is not required.
Code:
sudo apt-get install qt3-dev-tools texinfo git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk eclipse ia32-libs
8. Get and Setup the AndroidSDK (Everything you need to know is there or just Google for help)
http://developer.android.com/sdk/index.html
NOTE: Ubuntu 10.04 does not have Java 5 in it's repositories. Follow this link to setup to Java 5
9. Get and Setup ADT Plugin for Eclipse (Everything you need to know is there or just Google for help)
http://developer.android.com/sdk/eclipse-adt.html#installing
TIP: At this point you might want to try Google's “Hello, Android” tutorial.
Click to expand...
Click to collapse
10. Download and Install the Sourcery G++ Lite for ARM EABI Toolchain (Currently arm-2010.09)
http://www.codesourcery.com/sgpp/lite/arm/portal/subscription3053
Look for and click the link for Recommended Release
Look for and click the link for IA32 GNU/Linux TAR
Extract the archive. You will have a folder named arm-2010.09
Make a directory in your home directory named CodeSourcery
Ex. mkdir ~/CodeSourcery
copy the entire arm-2010.09 folder into CodeSourcery
Click to expand...
Click to collapse
11. Update your $PATH
You should be familiar with this because you had to do it to setup the AndroidSDK
Append the following to your PATH in .bashrc
Code:
~/CodeSourcery/arm-2010.09/bin
12 Download and Prepare the Samsung Source Code (Currently SHW-M110S_Opensource_Froyo_update2.zip)
http://opensource.samsung.com/
Click Mobile - Mobile Phones
Look for and download SHW-M110S_Opensource_Froyo_update2.zip
Extract the archive. Inside the new folder are two more archives.
Extract SHW-M110S_Kernel.tar.gz Inside there is a new folder Kernel
You can copy this to a more convenient location. I copy it to my desktop.
In the Kernel folder is a file named Makefile. Open it with your editor of choice.
Go to line 184. You will see ...
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-
You have to change it to something like below, but see the koe? That is my username so you have to change it to your username.
CROSS_COMPILE ?= /home/koe/CodeSourcery/arm-2010.09/bin/arm-none-eabi-
Save Makefile.
Click to expand...
Click to collapse
13. Compile a Kernel
NOTES:
1. Do not try to compile the code in your Shared Folder. It will fail.
2. When issuing these commands you will see lots of output during this part, most of which is not useful to you at this point.
3. The amount of time it takes for the final make command to run will depend on your computer.
Click to expand...
Click to collapse
Open a terminal window and move into the Kernel directory. Issue the following commands.
Code:
$ make shw-m110s_defconfig
$ make menuconfig
When the config editor opens do the following:
DOWN ARROW to Userspace binary formats and press ENTER
DOWN ARROW to Kernel support for a.out and ECOFF binaries and press SPACE
RIGHT ARROW to Exit and press ENTER
RIGHT ARROW to Exit and press ENTER
Press ENTER again and it will exit back to the command line
NOTE: If you have a powerful computer and you want to speed up the build time, make can be run as, make -j# The # represents how much it will try to do at once. $ make does 1 operation, make -j3 tries to do 3. I have a 2.66 Ghz dual-core CPU and I allow the VirtualBox guest OS access to both cores, so I use make -j3 The compile finishes in about 12 minutes and allows me to still use my host OS. For now, you might just want to run make without the -j option to get a full understanding of how long it takes. Later you can test with values.
Click to expand...
Click to collapse
WARNING: Time is relative. This will take some time ... go make a sandwich or maybe even watch a movie.
Code:
$ make
When you see $ again check the last couple of lines of output. You want to see …
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Click to expand...
Click to collapse
Congratulation! You just built a kernel for the m110s!

good write up.. Glad to see you hit the same a.out snag as me. Just makes me think it's not configured right and so I have low hopes. Will be fun to see what happens when you put an initramfs in it. I'd just unpack the stock one and try that first.
As for z4control.. I'm pretty interested in getting this working as something like this was the real reason I started messing with this. It seems there may be some issue with the z4mod's init wrapper not doing things it should but anyway.. just now seeing issues. flashed one kernel where I added some debug output added.. trying to understand it (not understanding it yet). I'm optimistic that I can track it down. edit:... definitely making progress, not quite there yet but getting closer.

appagom said:
good write up.. Glad to see you hit the same a.out snag as me. Just makes me think it's not configured right and so I have low hopes. Will be fun to see what happens when you put an initramfs in it. I'd just unpack the stock one and try that first.
Click to expand...
Click to collapse
Strictly to see if it would build completely and to get more info on how to do it, I did do an initramfs & kernel test build.
used the update2 kernel source
used the initramfs linked above (SHW-M110S intramfs Requires further research.)
ran find ./ | cpio -H newc -o > ~/Desktop/newramfs.cpio
added the cpio via menuconfig with no compression
It did build successfully and I ended up with a 7mb zImage vs. a 2.5mb.
There is no way in hell I am going to flash it because I do not know which initramfs (maybe from sk05) it is or what it contains but it did complete.

Now isn't this a kick in the nuts!
Since I got the toolchain all set I decided to focus on the Android source code. Following these directions .. http://source.android.com/source/download.html I got to "Building the code"
Code:
[email protected]:~/Desktop/myAnd$ source build/envsetup.sh
including device/htc/passion/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
[email protected]:~/Desktop/myAnd$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. simulator
4. full_passion-userdebug
5. full_crespo-userdebug
Which would you like? [full-eng] 1
============================================
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=AOSP
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv5te
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
============================================
[email protected]:~/Desktop/myAnd$ make
============================================
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=AOSP
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv5te
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
============================================
Checking build tools versions...
build/core/main.mk:76: ************************************************************
build/core/main.mk:77: You are attempting to build on a 32-bit system.
build/core/main.mk:78: Only 64-bit build environments are supported beyond froyo/2.2.
build/core/main.mk:79: ************************************************************
build/core/main.mk:80: *** stop. Stop.
Well, 32-bit will do for now seeing how ::cough:: I'm not the one building gingerbread.
I guess my next how-to is going to be how to go out and buy a PC and setup a 64-bit development environment.

Well, 32-bit will do fro now see how ::cough:: I'm not the one building gingerbread.
I guess my next how-to is going to be how to go out and buy a PC and setup a 64-bit development environment.
Click to expand...
Click to collapse
Could try the gnu cross compiler I suppose maybe it's clever enough to work around it. Your computer really isn't 64 bit though? You could just install a 64 bit VM assuming it is.

koe1974 said:
added the cpio via menuconfig with no compression
Click to expand...
Click to collapse
Ok, that procedure is easier than it used to be, or than what I read it used to be. I'm not afraid to add one and flash it. Just busy with making one I like right now though.. then again.. sounds like a 10 minute interruption.. so.. we'll see... oh and I don't remember what was stopping xconfig from working, but something annoying.. it's quite a bit nicer than menuconfig. I need to learn how that works though.. cause really you should add modules from the compilation itself right.. so you cant have the initramfs already before you compile, unless make opens it and add the modules and re-cpio's it. Anyway.. I'll shoot first, ask later.
edit: just flashed.. it gave about 1 tenth of a blue bar and froze. Ok, that was fun, back to fixing and ext4 kernel up.

appagom said:
Could try the gnu cross compiler I suppose maybe it's clever enough to work around it. Your computer really isn't 64 bit though? You could just install a 64 bit VM assuming it is.
Click to expand...
Click to collapse
The VM I setup was 32bit, but it's 64bit now. I will just modify the How-To for a 64bit system.

4 bugs related z4control issues solved(ok 2 were probably the same as well as a fifth, so really 3)..
one, it's failing to create a directory it needs (/system/etc/init.d), reported, work around create by hand.
2) It's rfs formatting wrapper script which checked for voodoo, failed. Strange bug in sh actually.. workaround in script found and reported
bugs 3 and 4 details unimportant, were related to the mystery of where sslvpn went. z4build was splitting the initramfs by tacking it some of it brute force on to the end of the zImage. The init script found it again and unpacked the files before continuing. Oddly, it seems an uneeded because I fit the only big displaced file in just fine without splitting and I didn't even use heavy compression. Anyway, needed or not it caused two files to go missing, this one, and a small text file that reported the version of z4mod. this file prevented z4control from working.
I will not fix this tonight, but I mostly understand it (altough not in exact detail of precisely understanding some of the odd symptoms, but I think dealing with this will likely solve it all) My diffs could never find the version file, cuase I never unpacked it to know it even existed in the first place. Waaaah.. bug tracking is tiring. We should have this all running very shortly.
update: my first attempt at fixing the repacking bug.. resulted (I already feared this but hoped it would just go away) in a kernel that seems totaly complete, but where it seems something in the init wrapper isn't working... getting closer to finding it.
update: LAST BUG FIXED
The last bug(which I previously assumed was part of the repack bug) was actually aslo part of z4build, now documented here:
http://forum.xda-developers.com/showpost.php?p=10638535&postcount=1062
I'm pretty sure that one should really get it all going now. there are no lines of code left to break. I've tested almost every line now. I'll get a new kernel out, but will need to wait for an updated z4control. z4ziggy seems busy right now maybe (no complaint obviously).
I can fix this last bug in my roll out of the kernel. The other remaining ones can be worked around pretty easily, but not pretty for user instructions, better to wait probably.

SK05 Rebuild test (PASS)
We have doubts about if the shw-m110s_defconfig is what is used by samsung so I decided to try to make a working kernel from an initramfs and froyo_update source code.
General idea of what I did...
sk05 source code froyo_update (from samsung)
sk05 initramfs (link in post 4 "initramfs SK05 Tested .. OK")
cd initramfs_dir
find . -print0 | cpio -o0 -H newc | gzip -9 -f > some/path/initramfs.cpio.gz
cd kernel source code root directory
modify Makefile ln. 184
make aries_android_rfs_defconfig
make menuconfig
disable a.out
add path to initramfs archive
compression gzip
make
tar --format=ustar SK05rebuilt.tar zImage
Click to expand...
Click to collapse
Results in a zImage the same size (4.6mb) as samsung's, and it boots.

awesome..
I GOT IT
That was big fat B to solve. Debugging self destructing scripts that run in a startup environment with different mounts and different PATH variable is no fun and requires some imagination. I had to work around 2 more bugs in z4build but now I have user transparent workarounds to all of them.. plug and play. Unfortunately I have about 30 minutes more free time today so I probably wont post it today. I should clean up some comments and such in it first probably. We'll see.

appagom said:
awesome..
I GOT IT
Click to expand...
Click to collapse
Very nice!
Sent from my SHW-M110S using XDA App

the "awesome" comment was referring to you. Should be able to take the grak of z4grak with some compiling , but I'm happy with it in too.. doesn't matter.
Anyway.. I updated the kernel page (from the link on OP). The new kernel is there, but I pushed it out very fast. Didn't flash last repack myself yet after changing comments.. but I only changed comments. (I am running the posted copy now) It needs testing since my system has gotten a been used and non-pristine. Get z4control, you can use it to flash it if you want. the rest is all push button I hope.

Oh and default settings are less safe than Tegrak, not much if any better than ext2 actually. I think.. can't confirm right now. I recommend modifying etc/fstab to data=ordered,barrier=1 personally.. but that's what I like about z4.. you can decide for yourself.
Sent from my SHW-M110S using XDA App

[TUTORIAL]Setting up and compiling CM9/CM10 from source

Since I’ve seen many questions on how to build cyanogenmod 9 (CM9) from source for the Galaxy Nexus, but there isn’t a proper guide, I will attempt to write a small how-to. There already is a very good guide how to build ICS from source, but there are a few extra things you’ll have to do for CM9. I hope it will be useful, and if not, well, at least I’ve tried
LATEST UPDATE: August 20th - also added CM10
SETTING UP THE BUILD ENVIRONMENT
I highly recommend Ubuntu 12.04 64 bit for development or Linux Mint 13. It is possible to build on different linux distro’s, but I cannot cover all exceptions. (If you don’t have linux installed or are afraid to set up a dual boot, it is possible to build in a virtual environment –e.g. virtualbox-. Building in a virtual environment however, can be very slow. Also, 64 bit is recommended.)
Make sure java is installed! At the end of this post, I have written a small guide how to install java.
Set up adb and create proper udev rules
I will not write these steps down, but rather point you to some very nice and easy guides. It would be best to do this first, however, it is not completely necessary if you just want to build a fully functioning rom.
1) set up adb (follow this excellent guide)
2) set up udev rules which allow you to start adb without having to use sudo (follow this terrific tutorial)
Installing all necessary packages and set up repo (source)
Open a terminal and copy the following code:
Code:
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 tofrodos python-markdown \
libxml2-utils xsltproc zlib1g-dev:i386
WARNING: run the following commands as user (NOT as root) unless stated otherwise (e.g., when it explicitly shows ‘sudo’ before a command)!!!
Next, you’ll have to install repo to download the source. First we’re going to create a bin folder (1) in our home directory and include it in our path (2). Also, download the repo script (3) and make it executable (4). All from the command line:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Okay, we’re done with the first part. So far it’s been similar to building pure AOSP.For CM, there will be some additional things you’ll have to do.
DOWNLOADING THE CM SOURCE
Create a directory (CM9 -or CM10-) for your working files:
Code:
mkdir CM9
cd CM9
and then initialize the main CM repo (For CM10, just replace ics with jellybean):
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
Good, now you’re ready to download the source. This can take a couple of hours!! Run the following command from the terminal (Run the following commands in the terminal from the root of the directory that contains the source, e.g., ~/CM9/):
Code:
repo sync
Okay, the majority of the files needed to build CM are now on your computer. However, device specific files are needed. To get them, issue the following command in your terminal:
Code:
source build/envsetup.sh
lunch
After the lunch command, choose your device. If you have a GSM version, choose cm_maguro, if you have the CDMA version, choose cm_toro. Additional files needed for your device are being downloaded right now.
Before you can actually build the rom, you’ll need to run two more commands to get some proprietary files.
1) Open a terminal and go to CM9/vendor/cm/. Run the following command:
Code:
./get-prebuilts
This will download term.apk and rommanager.apk. You will need these files otherwise you’ll get an error while building.
2) Now we need to grab some files from your phone. Make sure you have a working build cyanogenmod version (just install a nightly) on your phone. Make sure adb is setup properly (see beginning of this post)!
Connect your phone to the pc. Open a terminal and go to CM9/device/samsung/(Maguro OR Toro)/. Run the following command:
Code:
sh extract-files.sh
BUILDING CM9/CM10
The building part is very easy. It just requires two simple commands:
Code:
source build/envsetup.sh
brunch
After the brunch command, choose your device. Again, if you have a GSM version, choose cm_maguro, if you have the CDMA version, choose cm_toro. Depending on your computer, hopefully you’ll have a fully functioning CM9 or CM10 in 30minutes-2hours (or even longer) . You can find the rom in: /out/target/product/(Maguro OR Toro)/
Next time you build, first clean your working directory. Enter the following command in the terminal:
Code:
make clobber
This will completely remove your output directory!
To update the source, before each build just run:
Code:
repo sync
ADDITIONAL INFO
Install Java
Installing java is very easy in Ubuntu 12.04. Java 6 is recommended. To install it in Ubuntu 12.04 or Linux Mint 13, download the most recent Java 6 SDK from HERE. To install, open a terminal and run the following commands:
Code:
$ chmod +x jdk-6u34-linux-x64.bin
$ sudo ./jdk-6u34-linux-x64.bin
$ sudo mv jdk1.6.0_34 /usr/lib/jvm/
$sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_34/bin/java 1
$ sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_34/bin/javac 1
$ sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_34/bin/javaws 1
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config javaws
NOTE: after each 'update-alternative'-command, choose the correct (new) java version!
To check if you have the correct java version, type in a terminal:
Code:
java –version
I also added JAVA_HOME to my path; I don’t know if it is still necessary, but it doesn’t hurt either. First, check where java is located. In a terminal type:
Code:
which java
In my case the output shows /usr/bin/java, but it could be located somewhere else. Write down the path minus '/java'. Then open /home/USERNAME/.bashrc and add the following line to the bottom of the file:
Code:
export JAVA_HOME=/usr/bin
Of course replace /usr/bin with your path. Then save and close, and in a terminal run:
Code:
source ~/.bashrc
Odexed version
Some people like their rom to be odexed. There are multiple ways to achieve this (special thanks to Planet X for helping me with this):
1)Instead of ‘brunch’ do the following (if you are building for toro, replace maguro with toro):
Code:
source /build/envsetup.sh
lunch cm_maguro-user
make –j4
(Note:
taken from source.android.com: GNU make can handle parallel tasks with a -jN argument, and it's common to use a number of tasks N that's between 1 and 2 times the number of hardware threads on the computer being used for the build. E.g. on a dual-E5520 machine (2 CPUs, 4 cores per CPU, 2 threads per core), the fastest builds are made with commands between make -j16 and make -j32.)
2)If you want to build an odexed version every time and just want to use the brunch command, do the following:
-Open build/core/main.mk
-Comment out (place a # at the beginning of the line) lines 240, 241, 245, and 246. Thus, replace:
ifneq (true,$(DISABLE_DEXPREOPT))
ifeq ($(user_variant),user)
Ifeq ($(HOST_OS),linux)
WITH_DEXPREOPT := true
Endif
endif
endif
Click to expand...
Click to collapse
# ifneq (true,$(DISABLE_DEXPREOPT))
# ifeq ($(user_variant),user)
Ifeq ($(HOST_OS),linux)
WITH_DEXPREOPT := true
Endif
# endif
# endif
Click to expand...
Click to collapse
Now you can use the brunch command to build an odexed version with insecure boot image.
Hopefully this guide will benefit some people, if not, it kept me busy for a while. Enjoy building!!
(btw, I'm not a native english speaker, so excuse me if I made errors in grammar )

Wow great work. These tutorials keep getting better making it so easy to compile your own rom!

So what does that "brunch" command actually do?
Is it just a script that does the make otapackage commands and stuff?

Infra said:
So what does that "brunch" command actually do?
Is it just a script that does the make otapackage commands and stuff?
Click to expand...
Click to collapse
Indeed! Brunch is actually a combination of 'lunch' and 'make'. Using the 'lunch-part' you choose your build (in our case the maguro or toro). Next, the 'make-part' actually gets things going. The nice thing using brunch is that it automatically detects the maximum number of threads it can use so that it will run at maximum speed.

Finally set my computer up to compile CM9 last night for the first time and after a few tries I finally got it going. The only problem is that I am now getting an error very close to this one.
http://forum.xda-developers.com/showpost.php?p=25452343&postcount=3093
That poster says that it has been happening for a few days now. Is this a known issue with compiling CM9 or is this just user error? I have tried twice compiling now and have had no luck. Is it working for anyone else?
---------- Post added at 02:05 PM ---------- Previous post was at 01:19 PM ----------
Here is the exact error that Im getting. I tried it again today just to see if it anything had changed.
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/mark/CM9/kernel/samsung/tuna'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

Thanks for this guide. I just built my first CM9 kang. Getting ready to flash it. Now to find a guide on what I can and can't change and recompile or do I just remove stuff and use 7-zip to zip it back up?

housry23 said:
Thanks for this guide. I just built my first CM9 kang. Getting ready to flash it. Now to find a guide on what I can and can't change and recompile or do I just remove stuff and use 7-zip to zip it back up?
Click to expand...
Click to collapse
Glad to hear you succeeded building your first kang. I don't really understand what you want to do next? If you want to remove stuff from the zip, you can. I for instance always remove stk.apk. But you can also modify the build files so that only things you want will be built. You can play around with the source code and things like that. Anyway, most of the answers you will find using google. I also very much like the development board on Rootzwiki; people are really helpful and friendly there. So if you have any specific questions, i recommend that forum as well!

mbroeders said:
Glad to hear you succeeded building your first kang. I don't really understand what you want to do next? If you want to remove stuff from the zip, you can. I for instance always remove stk.apk. But you can also modify the build files so that only things you want will be built. You can play around with the source code and things like that. Anyway, most of the answers you will find using google. I also very much like the development board on Rootzwiki; people are really helpful and friendly there. So if you have any specific questions, i recommend that forum as well!
Click to expand...
Click to collapse
Okay thanks. I was asking just what you answered. I want to be able to remove and/or add stuff to the zip for starters. I found the answer through Google, but I do appreciate you taking the time to answer. I'll definitely be visiting the Rootzwiki dev board. Thanks for the suggestion.

I have successfully compiled cm9 from source but have never tried to cherry pick or Kang anything yet. Could you quickly explain how you cherry pick with cm9?
Sent from my Galaxy Nexus using Tapatalk 2

SupWiz17 said:
I have successfully compiled cm9 from source but have never tried to cherry pick or Kang anything yet. Could you quickly explain how you cherry pick with cm9?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Check out this link it may be helpful
http://rootzwiki.com/index.php?/topic/13189-[TUTORIAL]-Everything-you-ever-wanted-to-know-about-GIT#entry322735
Sent from my GT-S5360 using Tapatalk 2

That's a very useful link, thanks! In addition, if you want to cherry pick commits that haven't been merged yet -specific CM commits, such as navbar customization-, have a look here: http://review.cyanogenmod.com/#/q/branch:ics,n,z
Now let's say you see something interesting that you want to add. Then look at that commit and you'll see a 'download' command, such as "git fetch http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/06/13306/15 && git checkout FETCH_HEAD". Just run that command and if everything works, you have succesfully cherry picked a commit. -of course, because these are not yet merged, there is the chance that no everything will work as it should-

There are also some GUI programs to manage git. I'm just about to try gitgui by all accounts it is very good.
Sent from my GT-S5360 using Tapatalk 2

Maybe it is a noobish question, but does this line:
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > /bin/repo
miss a ~?
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

UncleDan said:
Maybe it is a noobish question, but does this line:
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > /bin/repo
miss a ~?
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Click to expand...
Click to collapse
Not noobish at all! You're absolutely right. It's not necessary when you're already in your home folder, but to be sure I've changed it in the guide. Thanks for letting me know!

Sticky!!!!!
Thanks dude
Sent from my Galaxy Nexus using Tapatalk 2

im sorry for noobish...at this step
1) Create an empty file in ~/CM9/.repo
in home i have dir CM9 but its empty...i havent a folder call .repo
java its installed and adb work perfectly
this is my terminal output:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 20774 100 20774 0 0 35679 0 --:--:-- --:--:-- --:--:-- 56604
[email protected]:~$ chmod a+x ~/bin/repo
[email protected]:~$ cd CM9
[email protected]:~/CM9$ repo init -u git://github.com/CyanogenMod/android.git -b ics
Your Name [loris]: loris
Your Email : my email
Your identity is: loris
is this correct [y/N]? y
repo initialized in /home/llo/CM9
[email protected]:~/CM9$
and nothing...
SOLVED

Hey mate any idea why my camera never works after a build... I know I'm missing something but I'm not sure what. I have all the proprietary files for my maguro etc but I just can't get camera to work... everytime
Sent from my Galaxy Nexus using Tapatalk 2

CdTDroiD said:
Hey mate any idea why my camera never works after a build... I know I'm missing something but I'm not sure what. I have all the proprietary files for my maguro etc but I just can't get camera to work... everytime
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
And you flash gapps everytime?
Sent from my GT-I9300 using Tapatalk 2

Infra said:
And you flash gapps everytime?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Sorted it out was just missing a few important files under /system/vendor thanks
Sent from my Galaxy Nexus using Tapatalk 2

CdTDroiD said:
Sorted it out was just missing a few important files under /system/vendor thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Glad it worked out! Seems there have been a few changes lately, so I will add some more info soon.
Sent from my SGS3

Building cm9 for the Kindle Fire

BUILDING CM9 FROM SOURCE FOR THE KINDLE-FIRE
This is a guide to help with building a rom from Hashcodes source for the kindle fire.
I am no Dev so please go easy, and if you see any mistakes let me know and I will amend them, It took me a week of reading and asking numerous questions (to proper :angelev's:angel with lot's of mistakes to build my first rom.
Below is what worked for me in the end, (but from what I have learnt, every setup is different).
I'm posting this guide hoping it may help in someway, but please read and research as much as possible before starting
Please follow this guide at your own risk.
Please don't blame me if anything in this thread messes with your system.
I tried lot's of things and in the end I installed a new ubuntu 11.10 x64bit on a external 500gb hdd, (the nice thing now is that all my building etc is all done on a external hdd so I can not mess up my pc AGAIN
I tried 32 bit (but java didn't like that)
I tried ubuntu 12.04 (which is what I dual boot on my laptop)
and the one that worked for the following info was ubuntu 11.10 x64bit.
So here goes.
First you need the following installed.
sun-java6-jdk
android sdk (adb etc) (setup as normal for the kindle fire).
eclipse classic.
Then you set up extra build-essentials
Install the Build Packages
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 sun-java6-jdk pngcrush schedtool
sudo apt-get install*g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib
Install the repo
mkdir -p $HOME/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > $HOME/bin/repo
Then add the following to your path (e.g. in $HOME/.bashrc)
export PATH=$HOME/bin:$PATH
Then onto the build setup.
mkdir -p $HOME/otter/cm9
cd $HOME/otter/cm9
repo init -u https://github.com/CyanogenMod/android.git -b ics
download the local_manifest to .repo
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/ics/local_manifest.xml
at this point you should have a folder called otter inside your home folder and inside this a folder called cm9.
If you show hidden folders in cm9 you should also find a folder called .repo, inside you should have your local manifest, open with a text editor (ie. gedit) and make sure it looks like this.
(hashcodes manifest as of 07/03/2012)
**
****
****
****
****
****
****
****
**
Then sync your repo
repo sync -j4 (duel core)
(this can take a while (mine took 6 hours) (I have a laptop with dual core but only 1.3ghz).
this script uses ccache which will make subsequent builds at least two times faster.
Code:
#!/bin/bash
if [ -z "$1" ]; then
echo "usage: build.sh "
exit 1
fi
device=$1
# ensure ccache is in the path
export PATH="$PATH:$PWD/prebuilt/$(uname|awk '{print tolower($0)}')-x86/ccache"
setup()
{
USE_CCACHE=1
CCACHE=ccache
CCACHE_BASEDIR="$PWD"
CCACHE_DIR="$PWD/.ccache"
#export CCACHE_COMPRESS=1
export USE_CCACHE CCACHE_DIR CCACHE_BASEDIR
if [ ! "$(ccache -s|grep -E 'max cache size'|awk '{print $4}')" = "10.0" ]; then
ccache -M 10G
fi
source build/envsetup.sh
#lunch cm_$1-userdebug
}
setup $device
LOGFILE=build_${device}_$(date +%Y%m%d_%H%M).log
START=$(date +%s)
#make -j`cat /proc/cpuinfo| grep processor | wc -l` bacon 2>&1 | tee $LOGFILE
brunch $device 2>&1 | tee $LOGFILE
END=$(date +%s)
ELAPSED=$((END - START))
E_MIN=$((ELAPSED / 60))
E_SEC=$((ELAPSED - E_MIN * 60))
printf "Time to compile: " >> $LOGFILE
[ $E_MIN != 0 ] && printf "%d min(s) " $E_MIN >> $LOGFILE
printf "%d sec(s)\n" $E_SEC >> $LOGFILE
grep "Time to compile" $LOGFILE
copy/paste the text in a file called $HOME/build.sh, make it executable (chmod 775 build.sh). The script also saves the build output to a file called build_otter_.log.
then onto the build.
cd vendor/cm
./get-prebuilts
cd ../../
then onto buiding
source build/envsetup.sh
then this is the build command
brunch otter (this starts build)
Enjoy
To start over and wipe "out" folder
(from within /otter/cm9)
make clobber
or
rm -rf out/target
build.sh otter
(this can take awhile (mine took another 6 hours)
I had a few things missing and at various times throughout the setup/build I had to download some missing libs. etc (I was prompted all the way through, it would tell me I had so & so file missing and I just used the software centre to dl the missing files).
By all means ask me questions but don't be offended if I answer back “sorry I don't know” as I've already mentioned I am learning myself.
Cheers
Steve
:good:Thanks to Twa_priv & Hashcode with helping me with my rom and this guide:good:
If there are any mistakes/updates to change/modify please let me know.
PLEASE PRESS THE THANKS BUTTON IF YOU FOUND THIS THREAD HELPFULL AND HAPPY ROM BUILDING

helpful links (if you want to add a different guide let me know)
Ubuntu usb install
[B]http://www.ubuntu.com/download/help/create-a-usb-stick-on-ubuntu[/B]
Ubuntu iso
[B]http://releases.ubuntu.com/11.10/[/B]
another build guide (ubuntu 12.04) Thank SBlood86 for this one https://github.com/KFire-Android/and..._manifest/wiki

I can only find the Ubuntu 12.4 on their website, I am running windows 7. If it's not too much can you put links to where the software is downloaded from. Thanks Lovejoy.

TahrirSquare said:
I can only find the Ubuntu 12.4 on their website, I am running windows 7. If it's not too much can you put links to where the software is downloaded from. Thanks Lovejoy.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=ubuntu+11.10+download

Links added ^^^^^^^^^^^^^^^

I think you should add downloading the repo script:
mkdir -p $HOME/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > $HOME/bin/repo
Then add the following to your path (e.g. in $HOME/.bashrc)
export PATH=$HOME/bin:$PATH

twa_priv said:
http://lmgtfy.com/?q=ubuntu+11.10+download
Click to expand...
Click to collapse
Wow what was that, First time I see such a link. cool. Thanks

Thanks Twa_priv (info added to op)
(would not get very far without that
what does this bit do? cd ../../

You should add the build.sh script in there that twa-priv provided us with when we made our builds
Other than that looks great
Sent from my Amazon Kindle Fire using xda app-developers app

lovejoy777 said:
Thanks Twa_priv (info added to op)
(would not get very far without that
what does this bit do? cd ../../
Click to expand...
Click to collapse
This gets you back to the base directory so that "source build/envsetup.sh" works.

all above notes added to op
Thanks guy's

Incidentally the build instructions for Ubuntu 12.04 are here...
https://github.com/KFire-Android/android_local_manifest/wiki
I never put the instructions for older versions on there because they were on the Google and CM pages... Either way, very nice write up

SBlood can I put your guide in the op as well
Sent from my Galaxy Nexus using xda premium

lovejoy777 said:
SBlood can I put your guide in the op as well
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Go for it; if you'd like to see anything added to the wiki shoot me an email.

Please change editor to gedit not gimp
Thanks

thanks, oops
Sent from my Galaxy Nexus using xda premium

Just wondering, does it have to be Sun JDK 6? Will it work with Sun JDK 7 or OpenJDK?
I did a clean install of Ubuntu and the PPA I used to download JDK 6 doesn't work anymore

Only JDK 6 .
Envoyé depuis mon GT-I9000 avec Tapatalk

Trojan38 said:
Only JDK 6 .
Envoyé depuis mon GT-I9000 avec Tapatalk
Click to expand...
Click to collapse
Dang ok. Now I have to figure out how to install JDK 6. lol :silly:
Sorry I can't thank you. I ran out of thanks
---------- Post added at 07:02 PM ---------- Previous post was at 06:21 PM ----------
It's not letting me install JDK 6 at all. What do I do...?
EDIT: Found a way to install. Thanks for the help. http://www.devsniper.com/ubuntu-12-04-install-sun-jdk-6-7/

veeman did you not have it before?
Sent from my Galaxy Nexus using xda premium

[PORT] [ROM] WebOS Port - Build Setup

Overview
The following steps will help you to setup a complete build environment for the webos-ports project.
WE DO NOT CURRENTLY SUPPORT webos-image PLEASE BUILD webos-dev-image
Setup the build environment
Code:
$ sudo apt-get install gawk
$ sudo apt-get install diffstat
$ sudo apt-get install chrpath
$ sudo apt-get install texinfo (if not on Ubuntu or Debian it will be makinfo instead of texinfo)
$ cd into-your-build-directory
$ mkdir webos-ports && cd webos-ports
$ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh
$ sudo sh prerequisites.sh
$ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
$ make setup-webos-ports
Before you can build, you will need some tools. If you try to build without them, bitbake will fail a sanity check and tell you about what's missing, but not really how to get the missing pieces.
This has been tested on Gentoo (shr-chroot) and Ubuntu-12.04 amd64 and should work almost everywhere where valid toolchain is provided.
You need a lot of RAM to link webkit-webos, make sure you have at least 6GB (it's OK when some of that is swap, because it's used only for short part of build).
Webkit needs so much ram to link because it's linking with debug symbols (huge files) which are stripped later in do_package after creating -dbg packages.
You can add extra 2GB of swap file like this:
Code:
$ dd if=/dev/zero of=swap_2gb.img bs=1024k count=2048
$ mkswap swap_2gb.img
$ sudo swapon swap_2gb.img
If you want it permanently add it to your /etc/fstab.
Building
To configure to build for tuna (notice '.' which is actually bash 'source' command):
Code:
$ cd into-your-build-directory/webos-ports/webos-ports
$ . ./setup-env
To update metadata
Code:
$ make update
# or if it shows warning about different bblayers.conf or layers.txt
$ make update-conffiles && make update
# you can also add UPDATE_CONFFILES_ENABLED = 1 to config.mk
# if you never want to have any uncommited changes in your checkouts RESET_ENABLED = 1 in config.mk
To build the webos-image for the gnex device:
Code:
$ MACHINE=tuna bb webos-ports-image
# or for the webos development image
$ MACHINE=tuna bb webos-ports-dev-image
If you get an error about missing qmake-palm, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f qt4-webos
If you get an error about missing QtWebKit #261, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f webkit-webos
If you get an error "The BBPATH variable is not set", then you forgot to call:
Code:
$ . setup-env
After the build completes, you will find your image in <build env>/tmp-eglibc/deploy/images/tuna/
==Speeding up the build==
You can tune bitbake to use more of your processor. Edit webos-ports/conf/local.conf and uncomment the PARALLEL_MAKE and BB_NUMBER_THREADS lines. PARALLEL_MAKE should be set to the number of processor cores you have (or the number you have made available to the VM in the case of a VM) and BB_NUMBER_THREADS can be set from one to two times that, depending upon RAM, processor speed, other tasks running and Hyper-threading support. Example values:
Code:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
I'm not in charge of this port. This thread is just here to help you, and discuss about this port made by team WEBOS-PORT.
Thanks for their work.
Installing and running the image
Once you have built the image, you'll likely want to install it and run it on your Nexus. See Testing Gnex for further details on that process.
Source and updates : http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup

Videos
Pictures
More Pictures : http://webos-ports.org/wiki/Galaxy_Nexus

Thanks for this, just having a go at this now
Edit: Damn it seems it doesn't like Ubuntu 10.10
Suppose I needed an excuse to update........

It would be pretty cool to have web os as a port for the Nexus. Wish you all the best
Sent from my Galaxy Nexus using Tapatalk 2

Nice, I hope webOS will be a succes on our Galaxy Nexuses!
Good luck!

nice work there ...

Really excited about this. Can't wait for a relatively stable port of the WebOS

So awesome, can't wait to see how this progresses.
Sent from my Galaxy Nexus using Tapatalk 2

The source was specified for Gnex, wasn't it?
Sent from my Galaxy Nexus using xda app-developers app

woot woot. niceeeee

Sound good....
Sent from my Galaxy Nexus using xda app-developers app

Awesome dude! Can't wait for a release. Hopefully in the future we can get this to dual boot with android, that would be awesome!

possibly to get instructions for toro?

waiting this on my gnex

New video added to post #2

exciiting stuff

Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.

#1 updated with Latest revision as of 23:58, 10 October 2012

sounds interesting.. cant wait for build that i can flash

Bread Pitta said:
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
Click to expand...
Click to collapse
Same here. Finally got it to build without errors, but no clue what to do next. My best Google sleuthing couldn't find any hints either

[GUIDE] Compiling your own AOKP (ICS Branch) from Source

Hi! Here's a complete guide for people who want to develop AOKP from source. I havent compiled any ROM from source because my internet connection is too slow. This guide will work, as far as I know. So lets start off by seeing the requirements.
Requirements :
Code:
1. A 64-bit environment. (64-bit is necessary for android 4.0 and plus builds)
2. Ubuntu 12.04 or 12.10 (with 64-bit architecture)
3. 2Ghz Dual Core Processor
4. 2GB Minimum ram
5. 50GB File Space (For only one rom source)
The device tree can be found here : Link. (thanks to whitexp for the device tree and percy_g2 to provide the correct links in the replies.
Now Open the terminal (CRTL+ALT+T) and go ahead as follows :
1. Update your OS
Code:
$ sudo apt-get update
$ sudo apt-get upgrade
2. Download the required packages :
2A. Installing JDK:
Code:
$ sudo add-apt-repository ppa:webupd8team/java
$ sudo apt-get update
$ sudo apt-get install oracle-java6-installer
Once its installed check weather its installed properly or not.
Code:
$ java -version
The output should be like this :
Code:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
2B. Installing required packages.
Code:
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 xsltproc pngcrush gcc-multilib lib32z1 schedtool
2C. LibGL shortcut issue solver:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3. Setup installing repo
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
4. Create the working folder
Code:
$ mkdir aokp_ics
$ cd aokp_ics
5A. Making the directory for downloading the source
Code:
mkdir -p ~/rom/android/system
Now go into that folder by :
Code:
cd ~/rom/android/system
PATH=~/bin:$PATH
5B. Downloading the AOKP source:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b ics
6. Sync repository:
Code:
$ repo sync
** Please note that this will take a long time. You need fast connection because the size repositories is 8 ~ 12 GB.
7. Setting up the source folder
Once the sync finishes without breaking all the folders will appear in rom/android/system folder, Execute :
Code:
mkdir -p ~/rom/android/system/device/samsung/totoro
and then for vendor, execute this :
Code:
mkdir -p ~/rom/android/system/vendor/samsung/totoro
8. Compiling
Code:
. build/envsetup.sh
lunch cm_totoro-eng
brunch cm_totoro-eng
** Your build will be located at /rom/android/system/out
All the best.. ​

And how will this work again?
Without proper source implementations from the device?
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]
---------- Post added at 12:23 AM ---------- Previous post was at 12:19 AM ----------
Hmmm,
We can't even compile a stable ics build.
I'm not sure how well this works.
Can any senior GY devs verify this?
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]

Good thread

deathnotice01 said:
And how will this work again?
Without proper source implementations from the device?
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]
---------- Post added at 12:23 AM ---------- Previous post was at 12:19 AM ----------
Hmmm,
We can't even compile a stable ics build.
I'm not sure how well this works.
Can any senior GY devs verify this?
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]
Click to expand...
Click to collapse
i am not an expert in this so I have said that this will work "as far as i know". I have gone till the step in which you have to sync repo. So I thought that this will surely work even ahead of that step.
Ya sure. Some senior GY dev must verify this.
There is a file called default.xml in repo/manifests. You have to change it according to your needs.

LoLz... Let CM9 get stable! AOKP and other ICS based source compiled roms come after!!
Also PPA no longer exists! Java won't install with the method given in the guide!
EDIT:
Also, If you haven't tried on your own you can't say it works -_-
And you didn't mention which device config to be used -_- People aren't pros like you #LOL
@prototype-U @percy_g2 @Deadly
EDIT:
Also the source is not 8-12GB its less than 8GB :silly:
EDIT 3:
More people need to see this :v
@gadgetroid

Arnav.G said:
LoLz... Let CM9 get stable! AOKP and other ICS based source compiled roms come after!!
Also PPA no longer exists! Java won't install with the method given in the guide!
EDIT:
Also, If you haven't tried on your own you can't say it works -_-
And you didn't mention which device config to be used -_- People aren't pros like you #LOL
@prototype-U @percy_g2 @Deadly
EDIT:
Also the source is not 8-12GB its less than 8GB :silly:
EDIT 3:
More people need to see this :v
@gadgetroid
Click to expand...
Click to collapse
Exactly.
The device tree is of most importance
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]

deathnotice01 said:
Exactly.
The device tree is of most importance
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]
Click to expand...
Click to collapse
Yeah, CM is AOSP with Major Modifications in Google AOSP Source for Performance!
Also instead of compiling ICS based roms you should first compile CM7/GingerBread roms! Coz if you directly start off with CM9/ICS I am sure you are going to get frustrated of the big big errors you are going to face!
This thread ironic! lol

deathnotice01 said:
Exactly.
The device tree is of most importance
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]
Click to expand...
Click to collapse
AOKP or any aosp builds based on cm9 can be compiled but it will have same bugs like CM 9 and device tree can be found https://github.com/Whitexp/android_device_samsung_totoro/tree/ICS here for SGY .
Its useless until RIL is fixed

Also compiling isn't that tough!
But writing proper HAL's and fixing the bugs is tough!!

hmm thread is not a bit useful in this forum
aokp on galaxy y5360
make me laugh
we can dream for cm7.2 aosp is a milestone that cant be achieve

I am new here and not a professional.
I have tried this. But i didnt make the final build because my internet is too slow(256K modem). but i have reached the sync repo step successfully and so i thought i would share it. But now i see that sharing it was waste.
And yes, @Arnav.G its not a rule that CM must be maintained first and AOKP after that. Anyone can start the work of AOKP simultaneously. I was seeing your profile and i saw that you also have posted a guide on compiling CM, AOKP and all. I sincerely think that the guide is not so noob friendly, you should make it more simpler by separating the commands which you have pressed into one.
greetings.

robowarrior1377 said:
I am new here and not a professional.
I have tried this. But i didnt make the final build because my internet is too slow(256K modem). but i have reached the sync repo step successfully and so i thought i would share it. But now i see that sharing it was waste.
And yes, @Arnav.G its not a rule that CM must be maintained first and AOKP after that. Anyone can start the work of AOKP simultaneously. I was seeing your profile and i saw that you also have posted a guide on compiling CM, AOKP and all. I sincerely think that the guide is not so noob friendly, you should make it more simpler by separating the commands which you have pressed into one.
greetings.
Click to expand...
Click to collapse
Why bringing my guide here? lol
Also do you want to kang my guide!?

Ok.
So OP what device tree did you use to be exact?
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]

AOKP and Galaxy Y look so funny together!
Btw you missed the major steps:
Setting up vendor
Setting up device tree
Setting up kernel source
And obtaining cm_totoro.mk
Anyways, its worth the try.. atleast you guys would be able to see AOKP

Subscribed to thread xD
Lets see what is his next reply

robowarrior1377 said:
I havent compiled any ROM from source because my internet connection is too slow.
Click to expand...
Click to collapse
makes a guide for something he doesn't know or has never done
robowarrior1377 said:
Requirements :
2. Ubuntu 12.04 or 12.10 (with 64-bit architecture)
Click to expand...
Click to collapse
I'm sure I built it on 11.10
robowarrior1377 said:
3. 2Ghz Dual Core Processor
Click to expand...
Click to collapse
1ghz single core
robowarrior1377 said:
4. 2GB Minimum ram
Click to expand...
Click to collapse
yawn. 512mb with a bit of swap
robowarrior1377 said:
5. 50GB File Space (For only one rom source)
Click to expand...
Click to collapse
20gb
robowarrior1377 said:
Now Open the terminal (CRTL+ALT+T) and go ahead as follows :
Click to expand...
Click to collapse
isn't working on debian. had to map my own shortcut
robowarrior1377 said:
1. Update your OS
Code:
$ sudo apt-get update
$ sudo apt-get upgrade
Click to expand...
Click to collapse
Isn't necessary
2. Download the required packages :
robowarrior1377 said:
2A. Installing JDK:
Code:
$ sudo add-apt-repository ppa:webupd8team/java
$ sudo apt-get update
$ sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
can be problems for new distros. please use my method
cybojenix said:
first we download the required binary:
Code:
wget --no-check-certificate --no-cookies --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com" "http://download.oracle.com/otn-pub/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin"
then we need to run the binary, and move it to a shared location
Code:
chmod +x jdk-6u45-linux-x64.bin
sudo ./jdk-6u45-linux-x64.bin
sudo mv jdk1.6.0_45 /usr/lib/jvm/
finally, all the needed java binaries need to be installed, and given the highest priority. This will override any other java versions you have
Code:
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk1.6.0_45/bin/jar 1
sudo update-alternatives --install /usr/bin/javadoc javadoc /usr/lib/jvm/jdk1.6.0_45/bin/javadoc 1
now check that jdk1.6.0_45 is selected on these
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws
sudo update-alternatives --config jar
sudo update-alternatives --config javadoc
Click to expand...
Click to collapse
robowarrior1377 said:
5A. Making the directory for downloading the source
Code:
mkdir -p ~/rom/android/system
Click to expand...
Click to collapse
no comment.
robowarrior1377 said:
Code:
PATH=~/bin:$PATH
Click to expand...
Click to collapse
you'd be better off adding this to ~/bash.rc
robowarrior1377 said:
7. Setting up the source folder
Once the sync finishes without breaking all the folders will appear in rom/android/system folder, Execute :
Code:
mkdir -p ~/rom/android/system/device/samsung/totoro
and then for vendor, execute this :
Code:
mkdir -p ~/rom/android/system/vendor/samsung/totoro
Click to expand...
Click to collapse
WOOOOTTTT building with empty device folders. you must be a genius
robowarrior1377 said:
8. Compiling
Code:
brunch cm_totoro-eng
Click to expand...
Click to collapse
hmm. brunch totoro
robowarrior1377 said:
** Your build will be located at /rom/android/system/out
Click to expand...
Click to collapse
LOOOL
~/aokp-ics/rom/android/system/out/target/product/toroto
that's if you insist on using your directory.
I hope this helped you. trollojenix

cybojenix said:
makes a guide for something he doesn't know or has never done
I'm sure I built it on 11.10
1ghz single core
yawn. 512mb with a bit of swap
20gb
isn't working on debian. had to map my own shortcut
Isn't necessary
2. Download the required packages :
can be problems for new distros. please use my method
no comment.
you'd be better off adding this to ~/bash.rc
WOOOOTTTT building with empty device folders. you must be a genius
hmm. brunch totoro
LOOOL
~/aokp-ics/rom/android/system/out/target/product/toroto
that's if you insist on using your directory.
I hope this helped you. trollojenix
Click to expand...
Click to collapse
Ahahahhahahahahahhahahahahahha... xD Can't stop laughing
Trololololjenix xD