yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] numberoneoppa:
This is a legitimate question. No changes in github since late may.

Sent from my Vibrant using the XDA for Android app.
[Epic 4G Android Development] dreamsforgotten:
I'm sure they are devoted to the kernel now and possibly awaiting source to finish the official kernel the rest of the sgs cyanogen are running plus in another thread nullghost noted two of the devs in the process of moving so patience is best now it gets discouraging to devs when people start accusing them of abandoning a project even if it weren't meant that way. This is extremely difficult on the epic both from the os itself and our phones boot partitions differ from the other sgs cousins.
[Epic 4G Android Development] Esteway.619:
My friend has a vibrant and he said that on there cm7 builds the use nexus s bootloaders that's how they got theres working good with there nexus s kernel (gsm) do u think he's right?
[Epic 4G Android Development] willverduzco:
Keep it clean in here, guys. Don't make me start issuing bans.
[Epic 4G Android Development] xboxfanj:
Any progress? I know that there's a CM7 thread, but that's a froyo kernel.
[Epic 4G Android Development] rulyskull:
+1

sent from my epic with the 4 g and the leaked ginger bread
[Epic 4G Android Development] Esteway.619:
There won't be an update till gb source gets release.
[Epic 4G Android Development] viper2g1:
This may be slightly off topic here but...

I am trying to build an AOSP rom from source with only pieces of CM code such as skip music with the volume rocker, and widgets buttons in the status bar.. Can anyone point me to a guide that can show me how to do that?

I am currently trying to sync with androids source but I hear its down now. After I get that synced up I want to pull commits from CM so please help if you know how.

Thanks for anyone who chooses to help me!!

Oh my build will be on a Nexus S. I am just here following the search button.
[Epic 4G Android Development] ugothakd:
How would we do this now with Decad3nce's sources?
[Epic 4G Android Development] nullghost:
If I find the time, I will update this post. School and work has me quite busy throughout the week. Until then, just remember: if and when I update this, you'll see the thread title updated as well as a post from me saying what I changed.
[Epic 4G Android Development] TexasLTE:
Okie Dokie :)
[Epic 4G Android Development] wis3m0nkey:
Hi,

Please follow http://xdaforums.com/showthread.php?t=974308 for current cm7 state for epic.

In this thread we r mainly discussing how to get it done.
[Epic 4G Android Development] jspielberg:
Hey wis3m0nkey...

What did you do to get past the "samsung-kernel-epic/scripts/mksysmap: line 44: arm-none-eabi-nm: No such file or directory" error?

I currently am in the same place with building the kernel.

CHK include/linux/version.h
SYMLINK include/asm -> include/asm-arm
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
SKIPPED include/linux/compile.h
LD vmlinux
SYSMAP System.map
~/samsung-kernel-epic/scripts/mksysmap: line 44: ~/arm-2010.09/bin/arm-none-eabi-nm: No such file or directory
make: *** [vmlinux] Error 1

At first I tried using the built in cross-compiler with cm7 source, but when I had issues with 4.4.3, I decided instead to go with option 1... using the latest codeSourcery toolchain.

I am still working on getting the cm7 source to compile too.
[Epic 4G Android Development] wis3m0nkey:
Hi,

After applying patches from 3rd post u need to do

And then try make
[Epic 4G Android Development] jspielberg:
Thanks wis3m0nkey... I was just working on kernel first. I think I figured out the problem I was having. I was specifying the path for my CROSS_COMPILE string as ~/android/system...., once I changed that to /home/<userid>/android/system kernel build completed...

LD [M] drivers/net/wireless/bcm4329/victory/dhd.ko
LD [M] drivers/net/wireless/wimax/cmc7xx_sdio.ko
LD [M] drivers/net/wireless/wimaxgpio/wimax_gpio.ko
LD [M] drivers/onedram/dpram_recovery/dpram_recovery.ko
LD [M] drivers/onedram/victory/dpram.ko
LD [M] drivers/onedram_svn/victory/modemctl/modemctl.ko
LD [M] drivers/onedram_svn/victory/onedram/onedram.ko
LD [M] drivers/onedram_svn/victory/svnet/svnet.ko
LD [M] drivers/samsung/fm_si4709/Si4709_driver.ko
LD [M] drivers/samsung/vibetonz/vibrator.ko
LD [M] drivers/scsi/scsi_wait_scan.ko
LD [M] net/netfilter/xt_TCPMSS.ko
CC arch/arm/boot/compressed/misc.o
AS arch/arm/boot/compressed/piggy.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready

Compilation took 903 seconds.

Now onto the CM7 build...
[Epic 4G Android Development] wis3m0nkey:
That is same as saying ~/android/.....

Ohh well but I've my development environment on another drive so I had to change it anyways so I never noticed it :)

Anyways if u figure out how to make flashable zip out of compiled source please do share :) I'm stuck there (even though nullghost gave me some pointers I couldn't follow them)

One more thing I couldn't yet figure -- if we can use fastboot utility with epic
[Epic 4G Android Development] jspielberg:
Okay... I have both the kernel and android/system all built

Now what :D

I went looking on the cyanogenmod forum, but I didn't see anything obvious about how to package these up and get them installed on the phone.

I feel like I am getting close.
[Epic 4G Android Development] wis3m0nkey:
To create package:

after make

or

instead of lunch

but for now both these methods fail

Third one is write an update-script and use content of system folder, but I couldn't wrap my head around it

Here are tips nullghost told me:

Get Quantum rom zip, unzip it and use its structure to build rom out of compiled cm7.

I'm not sure if I need to sign the zip or not, thats why I looked up at fastboot utility but its not for epic I suppose
[Epic 4G Android Development] jspielberg:
Well... the make otapackage did something.

The produced zip looks promising...

and the updater-script at the end of the META-INF directory structure looks promising as well:

Any idea about what was broken with the "make otapackage" output?

I would just test it, but unfortunately I seem to have hard bricked my epic trying to get the kernel on using ODIN and a tar file.

Hopefully the Sprint techs can reset it.
[Epic 4G Android Development] wis3m0nkey:
I don't know wats wrong with my build but I get following error for make otapackage.

Please let me know if you can understand what is wrong with this build:

And did u try odin to stock? or Frozen Syndicate? -- I'm not sure state of your phone just trying to give my opinion..

Did it brick because of CM7 zip? (blank screen can be fixed I have been there -- just use odin)
[Epic 4G Android Development] wis3m0nkey:
These particular lines

My build:

jspielberg's build:

I guess there is the problem if anyone can shed some more light on it :)
[Epic 4G Android Development] jspielberg:
Well... Sprint went above and beyond. Now that I have working Epic again... I am a little skittish about bricking it again... At least for 24 hours. :)
[Epic 4G Android Development] wis3m0nkey:
hehe yea understandable,

Let me know how to get otapackage done I'll try it :)
[Epic 4G Android Development] nullghost:
Kernel build issue relating to a.out should be fixed, go ahead and sync your repos.

The build_kernel.sh will now generate a flashable update.zip if you pass it the switch '-z' (Just for the kernel, not for CM7).
[Epic 4G Android Development] wis3m0nkey:
Awesome, Thanks :D

Can I flash it and use instead of EB13 (for other roms and not for CM7)?

And

How can I change

this particular line shows up while compiling (make otapackage)
[Epic 4G Android Development] nullghost:
That wouldn't be wise, monkey. The init.rc is different, who knows what would go wrong. Most likely it just wouldn't boot. Plus we're having an issue where the phone reboots when the screen times out.
[Epic 4G Android Development] wis3m0nkey:
hmm too bad :( and yea I know wouldn't be useful was just trying to test it :)
[Epic 4G Android Development] nullghost:
Reboot issue is resolved. Initramfs now uses eb13 modules.

If you wish to test, both the kernel and initramfs WILL boot on eb13.

It is a DualFS kernel, so no need to worry about your filesystem.
[Epic 4G Android Development] jwhisl:
Bit of a strange question here. I know Android is based off of a Linux kernal. I have several Linux programing guides at my disposal and I also have some light visual basic experience (which I'm sure will be useless here). What version of Linux is Android based off of and will Redhat/Fedora knowledge be of any use?
[Epic 4G Android Development] nullghost:
Not a strange question at all. Android is more or less its own distribution. It brings up just enough of a linux system to get Dalvik (a java-esque virtual machine) off the ground. From there, Dalvik runs your UI, apps, and so forth. In short, the underlying linux system is very limited.

General linux knowledge is handy if you plan on porting Android to a new device, but I would say Java, and Android-specific Java knowledge is more useful.
[Epic 4G Android Development] jwhisl:
Thanks for the info! I never thought about it being mostly java. Looks like I need to do some further reading. I'm currently downloading the sdk and so forth. I'll see what I can figure out from there
[Epic 4G Android Development] wis3m0nkey:
Awesome thanks again :)

I got kernel and CM7 compiled and zipped may give it a shot tonight.
[Epic 4G Android Development] jspielberg:
Maybe I am a glutton for punishment, but my attempt to load the results of the "make otapackage" and "kernel_build.sh -z" weren't so hot.

From a starting point of EB13 Extended with CW3, it was giving assert error on the "epic" stirngs. Telling recovery to ignore asserts didn't get much farther.

Also I noticed that my kernel zip (11 MB) and my ota package (74 MB) combined are quite a bit smaller than the CM7 Alpha1. Is make ota package and the build_kernel.sh -z not the best options?

My next test is going to be flashing on the Alpha but then applying the ota package and see if I get any better luck.

Anyone else having any luck getting the source builds flashed on their epics?
[Epic 4G Android Development] jspielberg:
Well... no dice flashing the zip built from source with the CM7 Alpha1 starting point (which looks real nice btw :))

Still getting

Still no love on getting this build flashed.

Any advice?
[Epic 4G Android Development] nullghost:
Yeah, we moved the initramfs into a subfolder so .git wouldn't get packed into your zImage. What I neglected to do was change the guide to reflect this.

In your kernel config, change CONFIG_INITRAMFS_SOURCE from "~/samsung-initramfs-epic/" to "~/samsung-initramfs-epic/initramfs/"

Sorry for the inconvenience.
[Epic 4G Android Development] nullghost:
Update your kernel source. I'm a jerk that forgot EXT4 support. The defconfig is updated to fix my dumbness.
[Epic 4G Android Development] jspielberg:
Thanks Nullghost...

I just updated everthing (initramfs, kernel and android/system) and I am rebuilding.

I am going to look over the alpha zip and the ota zip to see what the differences are... Looks like the ota zip contains a 6MB boot.img and the alpha has a kernel directory and a zImage. The System Apps directory contains a bit more apps like ADWLauncher and the stock build contains Launcher2 which seems more of theming thing so... not really concerned about the apps..

So... the initramfs issue was preventing the gingerbread otapackage to fail its asserts during clockwork recovery flashing?

Am I missing a step where the samsung kernel build gets intergrated into the build of the android system?

I am afraid I am at the stage where I am doing more question asking than being useful/helpful.
[Epic 4G Android Development] jspielberg:
Hmm... no luck on the rebuild... still the same asserts errors. I feel like I am missing a step merging the samsung kernel build product with the android system build product.

Googling the getprop assert errors, it looks like it is expecting a different radio (or an old CWM but I am on 3.0.0.6, so I think I am good to go there). I am going to try pulling the proprietary files from the alpha rather than from EB13 and see if that makes any difference.
[Epic 4G Android Development] wis3m0nkey:
Ok this is very simple just want to make sure u r going through it :

Have u wiped data, cache and dalvik cache? If yes then wipe them and try after restart.

And do we need to sign these zips? What's the use of signing?
[Epic 4G Android Development] jspielberg:
All flash attempts were after multiple wipes.

Any luck flashing your builds Wis3?
[Epic 4G Android Development] wis3m0nkey:
Not really quite busy with work for last 2/3 days lets see if I find time tonight I'll update u guys :-)
[Epic 4G Android Development] nullghost:
We are now using `lunch full_epic-userdebug`

Hotspot driver causing zygote crashes has been added to the list of issues.

I recommend using our CM7-Alpha1 update.zip to aid in the creation of your own flashable.

As always, sync your repo, and update device/samsung/epic with sources from our github.
[Epic 4G Android Development] wis3m0nkey:
Thanks nullghost :)

Yup I'm using cm7 released through progress page (the one by daemon) only. However trying to learn so I can be helpful in future or maybe so I can tinker around.
[Epic 4G Android Development] wis3m0nkey:
Hey nullghost,

Have a look at http://xdaforums.com/showthread.php?t=902051 for wimax drivers.

I know you guys must be working hard and I don't want to sound pushy but thought I would point it.

I would like to work myself but not sure if I can help rather than causing damage (taking time) :P
[Epic 4G Android Development] dustinmatthews87:


I'm pretty sure its not that easy, it took team win like 5 month to even have am alpha of wimax out. Also the evo and the epic use different radios from what I understand but hey who knows. Also what they did to get the evos wimax working is completely wroth the code from scratch.
[Epic 4G Android Development] MДЯCЦSДИT:
How much space does this take up so I know how big to make my vm hard drive?
[Epic 4G Android Development] wis3m0nkey:
Ouch my bad :-/ I assumed they r talking about wimax generically, and didn't even think of radios.

I would say use anything beyond 30 gigs but if u r going to use it only for cm compilation then even 15 gigs would be enough. Moreover u can put cm source code and sdk on other drive (windows drive) in that case u don't need so much space.
[Epic 4G Android Development] MДЯCЦSДИT:
Thanks. You have to download 10gb? Jeez.
[Epic 4G Android Development] msponsler:
After I built cm7 and the kernel, packed it up and flashed it...it won't boot. Just sits there at the samsung logo. Its the same spot I was at a while ago when I was trying to build aosp gingerbread. What am I doing wrong?

And idle curiosity...what about the gps isn't supposed to work? Mine works without issue with the cm7
[Epic 4G Android Development] msponsler:
Stupid enter key....

My gps works with cm7 alpha 1. Maps, latitude, weather app, everything.

I'm building cm7 with ubuntu 10.10 x64 on amd 6 core 1090. Java 6 jdk update 24.
[Epic 4G Android Development] wis3m0nkey:
Nice if gps works then daemon worked it out or will update the rom page

And download is not 10 gigs but compiled code takes space
[Epic 4G Android Development] drizek:
Yup. I have an 8gb drive so I never managed to get it to work properly. Make sure to use a dynamically expanding virtual drive and you can set it to whatever you like.

I think the actual download is around 5.2GB, but you need room to compile. I also had WebOS SDK running on the same VM and that took up some space too.

As for 4G, I think the Evo code won't be very useful. IIRC, the Evo doesn't use a "real" wimax radio like the Epic does. The Evo one only works in the US whereas the Epic should work on any wimax network. I'm assuming that that means there are some pretty substantial differences between them, though hopefully the Nexus S 4G will save us.
[Epic 4G Android Development] MДЯCЦSДИT:
I get permission denied for doing curl to bin/repo
[Epic 4G Android Development] MДЯCЦSДИT:
Nvm. Sudo su got it to work
[Epic 4G Android Development] nullghost:
A note about this:

In the directions, I simply stated to put it in ~/bin/repo, which is your home directory. i.e. /home/<username/bin/repo.

It's perfectly ok that you put it in /bin/repo (I did too), I just recommend putting it in your home dir for other users due to permissions, etc.
[Epic 4G Android Development] jspielberg:
Msponsler -

I have been having the same results. Can't seem to boot past the samsung screen using the kernel in samsung-kernel-epic/arch/arm/boot/zImage. Both the kernel and the produced ~/android/system/out/target/product/epic/system build just fine. That said I can't figure out how to best to use them - i.e. get the phone to boot past the samsung logo.

Marcusant -

I have CM7 build environment running in a 16GB VM. I installed Ubuntu 10.10 server as a minimal VM appliance, and I have just enough space to build both the kernel and the android system. I have about 400 MB free which feels pretty tight. If I weren't actually running it off of a spare sdcard I had lying around I would spurge for 18 to 20 GB of space.

General build/flash notes:

I am using the cross compiler in the android source for arm rather than codesourcery's cross compiler (when compiling the samsung kernel).

Using the cm7 source arm compiler saves me 100M which as I said before am running with a 16GB VM which is cutting it very close.

When I try to flash the otapackage (outside of the CM7 skeleton zip), CMW give assert errors. I believe them to be the issues with the build.prop file in system, but can't confirm. Transplanting the built system directory and zImage into the CM7 Alpha zip does allow for install from CWM recovery... but doesn't properly boot... Same thing if I just copy in the system folder.

Also, I can't transplant the files on a windows box for some reason. CWM recovery doesn't like the zip windows makes and it aborts. So far I have been using

on my ubuntu box and clockwork will flash that. I may next try using the 7-zip package on windows to see if I can do that manipulation there (again trying to save space).

Anyway... that is where I am at... no love yet on the booting.
[Epic 4G Android Development] nullghost:
jspielberg: try this for me please. (change dirs as needed, I'm just assuming)

cd ~/samsung-initramfs-epic/
git reset --hard HEAD
git pull origin master
cd ~/samsung-kernel-epic/
make mrproper
git reset --hard HEAD
git pull origin master
grep CONFIG_INITRAMFS_SOURCE arch/arm/configs/victory_03_defconfig

Make sure this points to the proper directory, the subdir initramfs/

Make sure the build_kernel.sh has the right cross_compile string, since we reset everything.

Then:

./build_kernel.sh -z

It'll produce a flashable zip in the current directory.

Let me know how that turns out.
[Epic 4G Android Development] theandrewgordon:
Can someone post their update.zip? My computer is having issues with the g++ part.... I have a 64bit build of Ubuntu
[Epic 4G Android Development] msponsler:
When I flash the files, it still sits on the Samsung logo.

@jspielberg

Did you do anything special or different this time?

How are you packaging your .zip file?

I get an error about my build.prop file in CWM. ro.product.board= is blank. I just put in SPH-D700 and it doesn't complain about it any more.

All my build are successfull...except I get one error, see below:

cd ~/android/system

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

repo sync -j16

. build/envsetup.sh

lunch full_epic-eng

make otaupdate -j7

brunch full_epic-eng

Running brunch gives me this at the end:

find: `/home/spoony/android/system/out/target/product/epic/repack.d/ota/system/lib/modules': No such file or directory

Usage: arm-eabi-strip <option(s)> in-file(s)

Removes symbols and sections from files

The options are:

-I --input-target=<bfdname> Assume input file is in format <bfdname>

-O --output-target=<bfdname> Create an output file in format <bfdname>

-F --target=<bfdname> Set both input and output format to <bfdname>

-p --preserve-dates Copy modified/access timestamps to the output

-R --remove-section=<name> Remove section <name> from the output

-s --strip-all Remove all symbol and relocation information

-g -S -d --strip-debug Remove all debugging symbols & sections

--strip-unneeded Remove all symbols not needed by relocations

--only-keep-debug Strip everything but the debug information

-N --strip-symbol=<name> Do not copy symbol <name>

-K --keep-symbol=<name> Do not strip symbol <name>

--keep-file-symbols Do not strip file symbol(s)

-w --wildcard Permit wildcard in symbol comparison

-x --discard-all Remove all non-global symbols

-X --discard-locals Remove any compiler-generated symbols

-v --verbose List all object files modified

-V --version Display this program's version number

-h --help Display this output

--info List object formats & architectures supported

-o <file> Place stripped output into <file>

arm-eabi-strip: supported targets: elf32-littlearm elf32-bigarm elf32-little elf32-big srec symbolsrec tekhex binary ihex

Zipping package...

Signing package...

Cleaning up...

Package complete: /home/spoony/android/system/out/target/product/epic/update-cm-nightly-signed.zip

95f9c69b4f431b738918d0acb6be1c4f update-cm-nightly-signed.zip

spoony@spoonylnxubuntu:~/android/system$

It gives me:

full_epic-ota-eng.spoony.zip

update-cm-nightly-signed.zip

The kernel compiles, and is flashable. I flashed CM7-Alpha1 then flashed the kernel and it boots successfully.

Since brunch is making calls to arm-eabi, is it trying to compile the kernel and package that up?

I'm pushing my zip'ed files up to githup ( https://github.com/msponsler/CM7-Builds ), including compiled kernels. victory_03-03182011.zip works. I haven't tested victory_03-03202011.zip yet. If anyone was interested.

Even just dumping my system file into the CM7-alpha1 .zip file doesn't work. What step am I missing....it's damn frustrating!

The only thing I did do different, is I pulled the files from extract-files.sh from a stock EB13 image.
[Epic 4G Android Development] jspielberg:
Hey Msponsler -

I don't believe the otapackage and brunch are supposed to be working yet --- are you using code sourcery's cross compiler or the one from the android source? I have been using the one out of the android source, but since my kernel doesn't build, I may switch this over.

I have been dumping my files (including the kernel) into the cm7 alpha1 file structure and rezipping it back up. I found if I tried doing this on windows, cwm recovery would abort...

Then again, I think you are currently farther along than I am.
[Epic 4G Android Development] jspielberg:
Well for those wanting to build their own kernels... I can confirm that if you follow the instructions here ... AND... use the Code Sourcery cross compiler, (not the one in the android code drop), you will get a bootable kernel.

Thanks Msponsler for proving it was possible -- and thanks nullghost for the steps to hard reset the git branch locally.

Now onto the android system.
[Epic 4G Android Development] msponsler:
I'm using code sourcery's tool chain for the kernel.

I also keep getting this when I try to flash using the compiled build.prop file:

assert failed: getprop ("ro.product.device") =="epic" || getprop("ro.buid.product")=="epic" || getprop ("ro.product.device")=="epic"

I don't know if I'm farther along or not! Your compiled CM7 does *something* lol!
[Epic 4G Android Development] msponsler:
Here: https://github.com/msponsler/CM7-Builds

The kernels (victory_****.zip) work, and are flashable with CM7.

The builds don't work yet....not sure why. It just sits there on the samsung boot screen. Very frustrating...