yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] jspielberg:
I modified my build.prop in the system directory to have different strings to get around the assert errors.

I believe the entries causing the problems are at the tail of /android/system/device/samsung/epic/full_epic.mk

All that being said... my android system build is behaving very similarly to yours. I will update try another build tonight hopefully.
[Epic 4G Android Development] msponsler:
Nullghost / Dameon87

Maybe a little nudge in the right direction? What steps are we missing and/or we doing incorrectly to get the compiled cm7 build to boot properly?

I'm suspecting that we arnt packaging the zip file correctly. I've tried replacing my compiled system folder (cp -rp to properly preserve file permissions) to the cm7-alpha1.zip file. Even using alpha1's build.prop file. Should I not be compiling this as a standard user? It looks like the alpha1 you guys released was compiled by root.

Thanks!
[Epic 4G Android Development] nullghost:
msponsler:

Well first, make sure your build is actually finishing, with the line about installed-files.txt showing up. Brunch, make bacon, and make otapackage do not work yet, so please don't use them.

As for packaging the zip, try removing the /system folder inside the zip first, then copy out/target/product/epic/system into the zip dir. Then of course, make sure you're zipping the three folders together: kernel, META-INF, and system. Those should be in the top level of the zip, not the folder containing the three.

jspielberg:

Did you use the hotspot fix supplied in the third post? It's causing our current builds to bootloop if not fixed. Once you fix it, it should stop boot looping.
[Epic 4G Android Development] msponsler:
@Nullghost:

It looked like it had finished up. I'll give it another repo sync; make tonight and I'll keep on the lookout for an "installed-files.txt" file showing up.

But really, just drop the /path/to/out/target/product/epic/system folder into the CM7-alpha1 zip? You had no other snaffu's or gotcha's that you had to do? Are you compiling as root, or as an unprivledged user? I'm only wondering because it creates all the system files as owned by user:usergroup and not root:root. And I don't see how that would translate very well to the boot image. At the very least the files would have an unknown UID / GID to the system itself, and with a ownership less than 777 on any of the system files -- your **** is broken! I didn't know if Android does some magic conversion or somehow just doesn't care. I guess I could do a chown -R root:root , but even still the init/rc files should probably be root:bin or root:sys

When I do drop the system folder in to the zip, I got these of errors during flashing :

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

when using the build.prop file that was generated during the build so I was using the one in CM7-Alpha1's system folder. Odd thing is, the generated build.prop file had an empty field for "ro.build.device=". So I wasn't sure where it was pulling that information from.

Thanks for the help! I really appreciate it!
[Epic 4G Android Development] nullghost:
I build as an unprivileged user. The init.rc in the kernel handles file permissions by chown/chmod'ing whatever it needs at boot, so don't worry about any of that. I've not run into the assert issue, so I don't know how to help you fix it.

Worst case scenario, do what I recommended to jspielberg. Run those blocks of code to reset and update your repositories.
[Epic 4G Android Development] msponsler:
Thanks!

I'll hopefully be able to give it a shot tonight.

Stupid Sun Cluster builds keeping me at work late....
[Epic 4G Android Development] deano0714:
Will you post a build?
[Epic 4G Android Development] msponsler:
If I ever get out of work today, and my wife let's me "screw around" on my computer -- and it works. I'll be more than happy to post a build of it.
[Epic 4G Android Development] deano0714:
Thanks man!!! :)
[Epic 4G Android Development] msponsler:
It boots...kind of.

Everything built okay, but I'm still stuck at the samsung screen.

I can `adb shell` into the device, and I can follow what the init.rc is doing.

It's dying here in the init.rc file:

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server

socket zygote stream 666

onrestart write /sys/android_power/request_state wake

onrestart write /sys/power/state on

zygote won't start. if I try to run it manually:

# /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server

link_image[1962]: 2673 could not load needed library 'libandroid_runtime.so' for '/system/bin/app_process' (reloc_library[1311]: 2673 cannot locate 'hotspot_unload_driver'...

)CANNOT LINK EXECUTABLE

And yes, libandroid_runtime.so exists, and it's in the library path.

export LD_LIBRARY_PATH='/system/lib:/system/lib/egl'

/system/xbin # ls -la /system/lib/libandroid_runtime.so

-rw-r--r-- 1 root root 563368 Aug 1 2008 /system/lib/libandroid_runtime.so

It won't attempt to load the GUI or even the boot animation because zygote won't run.

Thoughts? Comments? Help!

I can't crank at this any more tonight....I've got to get to bed.

Thanks!
[Epic 4G Android Development] jspielberg:
***** This may be outdated information pending build test *****

Zygote issues may be solved by:

Will build and test.

Original message below.

------

I can confirm the same results as msponsler..

I am running on Ubuntu server 10.10 64-bit minimal install in a 16GB VM (under vmware player - not sure if that makes a difference, but putting it out there), and have been following the instructions pretty much straight up. One thing I had to do was extract the eb13 files from a different machine... tar up the directory and copy them over, since my VM can't see the epic through adb. Since the build completes successfully, I assume that hasn't been a problem of missing needed files.

Notes on needed changes so far:

For the kernel:

I think we have confirmed that the code sourcery is required... or at least the CM7 included cross compiler is insufficient for kernel building. The package p7zip-full is required to be added (on Ubuntu 10.10) for the build-kernel.sh -z command to complete successfully.

For CM7 android/system:

The best option is to use the CM7-alpha as a directory skeleton. The build.prop file in the produced system directory... needs "SPH-D700" to be added for the ro.build.device field to avoid asserts during the flash.

I wonder if the fact that Nullghost is not seeing the assert errors and we are is key to difference as to why ours is not booting.

Nullghost-

When your make completes in android/system, does your build prop have a blank for the ro.product.board? Does your build.prop have:

If not, maybe we can figure out why and if it is related.
[Epic 4G Android Development] msponsler:
Also, some updates were pushed to the kernel/initramfs (forget which one...i think initramfs) that updates the proprietary kernel modules from Samsung to EC05. Compiling and flashing with last night's updates will allow the system to boot, and get to the home screen. But after it completes it's init cycle (when SD card is prepared), zygote force closes and restarts -- which shoots you back to the boot animation.

I didn't have a chance to look to close at that issue yet, just reporting what I've found out with the latest updates from the git repository.

What I wouldn't give for ldd and truss on android. I'm half tempted to compile them and push them in myself.

I wonder if this is because busybox isn't initializing properly?
[Epic 4G Android Development] Phasma343:
ldd alone would be a huge help in pinpointing issues like this. I am surprised that these weren't put into the set of utilities in the CM project in the first place.

logcat only gets you so far :P
[Epic 4G Android Development] jspielberg:
msponsler -

I think we might be missing a key part of nullghosts updated "gotcha" notes.

I will try this shortly.
[Epic 4G Android Development] msponsler:
*facepalm*

Ugghh....read the instructions twice. <-- mental note.

Let me know how it goes. I won't be able to dive into this into about 9:30 EST tonight.
[Epic 4G Android Development] deano0714:
Will you post a build if it works?
[Epic 4G Android Development] jspielberg:
Hey NullGhost,

Assuming msponsler and I get good builds tonight... do you have a problem with us posting them with the caveat that these are pre-alpha2 and will not be supported by the official CM7 dev team?
[Epic 4G Android Development] msponsler:
The source is open and available, I don't see that there would be any issue with it.

And if there is an issue, I'd be more than happy to ablidge to their requests.
[Epic 4G Android Development] msponsler:
Good news!

It boots!

Bad news!

no network connectivity over the CDMA radio. Not sure why...one small step at a time.

outgoing phone calls work, but the end key doesn't work...odd.
[Epic 4G Android Development] DevinXtreme:
You guys are free to build and post as you like.

We hold off on posting for reasons, though. We have a lot of experimental code flying around. Stuff can (and will) break. As you noted above, the radio isn't totally working.
[Epic 4G Android Development] nullghost:
To expand on DevinXtreme's post a bit:

To get the radio working in Alpha 1, we had to tinker with the telephony frameworks a bit. We're working on adjusting our patch to work with other devices, as we've yet to push said patch to github.
[Epic 4G Android Development] msponsler:
Cool, thats pointing me in the right direction. Thanks.
[Epic 4G Android Development] jspielberg:
msponsler,

Looks like there has been an initramfs change for wifi. Though the comment for the check-in says it is for Alpha2 builds only. I am not sure what an A2 build, but I assume it was are on the tip... then we are on A2.
[Epic 4G Android Development] msponsler:
Not quit. Some of the Alpha 2 stuff hasn't been pushed to the git hub...hopefully they will do that soon. So we can test and help squash current bugs :D
[Epic 4G Android Development] mdleal:
Is there a way to tell when new stuff gets added to the git hub for the epic? I just got done successfully building the update.zip
[Epic 4G Android Development] theandrewgordon:
if you have a successful build, and more stuff works than alpha, can you share it? i tried to build and failed... Thanks!
[Epic 4G Android Development] jspielberg:
Right now... with the latest checked in the functionality is decidedly less than what is in Alpha1.

In my latest build, the phone application force closes continuously preventing any useful interaction with it. This might be something I am doing wrong in my build... probably the zygote fix of commenting out the hotspot blocks.

Hey msponsler -

Did you remove the whole functions when you did the hotspot_ fixes?

Does that look about the same for you?
[Epic 4G Android Development] msponsler:
@ mdleal :

Follow the instructions on the first post for sync information.

If it grabs stuff....new stuff has been added. If it say's "up to date" then...you've got the latest stuff pushed to the git-hub

@jspielberg :

pretty much. I commented out the fields.

I wasn't having the phone application FC on me. But if using the latest kernel source (as of monday) zygote would die and restart when the wifi turned on. The kernel build I have from the 18th does not have this issue.

I couldn't connect to Sprint...I spent some time going through the telephony framework. But since this isn't one of the issues plaguing the CM7 dev's (they have a fix) I ignored it.

@theandrewgordon :

There is less functionality in the current build than in Alpha 1. There is alot of "in transition stuff" going on.

@All:

I'm trying to spend what little time I have trying to debug and test for the CM7 Dev's (unofficially, of course). The hopes of getting a "working" pre-alpha2 build is just a bonus.
[Epic 4G Android Development] mdleal:
Any Ideas? Iv started fresh and still get this error

device/samsung/epic/full_epic.mk:113: *** multiple target patterns. Stop.

** Don't have a product spec for: 'full_epic'

** Do you have the right repo manifest?
[Epic 4G Android Development] jspielberg:
Mdleal -

Does your device directory look like:

If you have an android_samsung_epic_4g directory or something like that... you may left off the "epic" when you ran the 'git clone git://github.com/EpicCM/android_device_samsung_epic.git -b gingerbread epic'

Which would leave an extra directoy with an Android.mk file with full_epic defined. You ight be able to just remove that directory... or just to be sure, delete your ~/android/system directory and start again from the beginning.
[Epic 4G Android Development] jspielberg:
Hey Nullghost -

Do you know if there is going to be a plan to use the newest EC05 proprietary files in the extract?

When I run extract_files.sh on a phone upgraded to EC05, I get the follow missing files.

Looking through adb, the /system/firmware directory is empty.

Are those firmware not required?

- jeff
[Epic 4G Android Development] mdleal:
That's the way I have it.

android/system/device/samsung/epic

It worked for me the 1st time but when I did a re-sync and try to rebuild it again, I received that error. I already tried to start over. Deleted the android folder.

I may just start all over and reinstall ubuntu. This is my 1st time using it and I could use the practice of setting it up again and reinstall android sdk.

One last question. Do we need all the other devices or can I delete those out of the android folder?
[Epic 4G Android Development] msponsler:
I resync'ed and tried to compile late last night / very early this morning (insomnia sucks BTW). I was getting the same thing. I didn't have time to dig into it, though.
[Epic 4G Android Development] jspielberg:
yep... I am seeing the same thing now too.
[Epic 4G Android Development] mdleal:
Good and bad news for me. I'll start looking threw the code at the dir structure.
[Epic 4G Android Development] jspielberg:
Okay... I looked through the recent commits on github and found the problem.

Add a "\" to the end of line 112 in your ~/android/system/device/samsung/epic/full_epic.mk

device/samsung/epic/prebuilt/gps.aries.so:system/lib/hw/gps.default.so

so it looks like

device/samsung/epic/prebuilt/gps.aries.so:system/lib/hw/gps.default.so \

You should be able to build after that. I really need to find out how to commit my changes back into git.
[Epic 4G Android Development] mdleal:
Yep that did it and I also learned how to find the recent changes on github. Thanks. I also comments on the line that was missing the back slash so hopefully Dameon fixes it. Is he compiling the same way we r in this thread?
[Epic 4G Android Development] Phasma343:
You mean by using the "make" command?

sorry I had to.
[Epic 4G Android Development] jspielberg:
I found the answer to this question... it does... It looks like they are in /system/sem and /system/seh in EC05 for some reason. Going to edit my extract to pull from one of these places.. (just incase).
[Epic 4G Android Development] mdleal:
Never mind, my build was not finished. Reading threw all 12 pages helped answer alot of questions.
[Epic 4G Android Development] msponsler:
Building from source still gives me no data service.

CM7 Team:

Has the telephony framework fixes been pushed up to the github?

Thanks!
[Epic 4G Android Development] mdleal:
couple more updates on github. going 2 resync and rebuild. Still need to build the kernal.
[Epic 4G Android Development] nullghost:
RIL patches are now on our github, see:

https://github.com/EpicCM/android_frameworks_base

brunch and cyanogen_epic build stuffs should go up soon, you'll find them at:

https://github.com/EpicCM/android_vendor_cyanogen

And please re-read the updated first post on how to stay in sync with our changes.
[Epic 4G Android Development] msponsler:
Awesome. Thanks!

I won't have time to play with this until tomorrow though.
[Epic 4G Android Development] mdleal:
The latest build I get no signal and wifi does not work. The phone also reboots after a minute or 2
[Epic 4G Android Development] msponsler:
@nullghost

Would the recent RIL patches fix the "no data service" when compiling from source?

I haven't had a chance to play with any of this in a while -- stupid taxes!
[Epic 4G Android Development] wis3m0nkey:
Finally I'm free :)

I'm gonna try my hands on everything in a day or two -- need to do plenty of reading :-/
[Epic 4G Android Development] Phasma343:
Anyone else having issues pulling one of the repos?

@zoidberg:~/android/system/device/samsung/epic$ git remote add epiccm git://github.com/EpicCM/android_device_samsung_epic.git
fatal: Not a git repository (or any of the parent directories): .git

Only one that spits out an error...
[Epic 4G Android Development] shabbypenguin:
so ive been trying to get past this error for a few days now and no such luck...
[Epic 4G Android Development] Decad3nce:
make update-api

and l2read
[Epic 4G Android Development] nullghost:
From the samsung/epic dir, run `git init` then try adding the repo again.
[Epic 4G Android Development] Phasma343:
Worked like a charm
[Epic 4G Android Development] nubecoder:
Same problem as you last night, same fix today as well (seems maybe the OP was updated, or I just plain missed it yesterday).

Now I've run into another problem, and I guess it will take a new CPU for my laptop to fix it.

It seems that only x64 capable systems are supported beyond Froyo. =[

Gives me a reason to buy that $50 CPU upgrade from ebay though I guess..

Unless there is some work-around, maybe this should be added to the OP.

=/
[Epic 4G Android Development] Decad3nce:
I build in a 32 bit environment.

Clearsilver patch:

http://osdir.com/ml/android-porting/2010-12/msg00272.html

http://groups.google.com/group/rowboat/msg/cccbe407ba23dc58
[Epic 4G Android Development] nubecoder:
Well I went to begin applying the aforementioned patch, and noticed this.

In /external/clearsilver/java-jni/Android.mk @ line #36:

And in /build/core/main.mk @ line #73:

So I went ahead and tried to run "make" again, no x64 error this time.

Seems that when you get the error, it sets the "build on 32bit" setting, and the next time you run "make" it works fine.

I did get the crespo error mentioned in post#3, but it was STATIC_LIBRARIES, rather than SHARED_LIBRARIES, no matter, the fix of adding:

to the "/device/samsung/crespo/sec_mm/Android.mk" file worked fine.

I also ran into the error shabbypenguin had, but I know how to read so that wasn't an issue. ;]

Running "make update-api" fixed that as well.

It's still building now, so we'll see if any other errors pop up, but for the moment, things are looking good.

Thanks to everyone for the help.

=]
[Epic 4G Android Development] redsox19asb:
How did you do on your build?
[Epic 4G Android Development] Phasma343:
Still can't get any telephony working from these builds. I am guessing the tweaks you guys have done to the telephony framework aren't in the repos?
[Epic 4G Android Development] nubecoder:
I got it building fine, haven't done anything with it yet, so I'm not sure if it would boot or not, but it did build successfully.

=]
[Epic 4G Android Development] nullghost:
Yeah, we've been toying with how to keep our patches aligned with the frameworks. I'll update the main post when we find a better way.

For now, we're keeping patches in android_device_samsung_epic, just read the patch and apply it in the right directory.

(the ril patch should go in frameworks/base and the cyanogen makefile patch should go in vendor/cyanogen)
[Epic 4G Android Development] Phasma343:
ahhh that's why the patches were failing for me. Thanks!
[Epic 4G Android Development] dreamsforgotten:
I'm working on an AOSP build and working with the cm7 source simultaniously. I'm stuck at this point. In the CM7 device file, overlay, config.xml you have a bool value of usingsamsungRIL. I'm getting a make error that the overlay has a resource that base doesn't. So what I did was open both cm7 and aosp filesystems side by side and nav to the frameworks/base/core/res/res/values/config.xml trying to see where usingsamsungRIL is supposed to match. Nothing is in there defining that resource so my question, where in the base (CM7 code) do I need to edit to accept the resource usingsamsungRIL?
[Epic 4G Android Development] Phasma343:
re-sync the repos. The issue was fixed a couple of hours ago.
[Epic 4G Android Development] dreamsforgotten:
Ok, to make sure we're on the same page before I do, I'm combining the RIL fix to AOSP, I'm actually building AOSP atm not cm7. Resync AOSP and it'll have the usingsamsungRIL resource in it?
[Epic 4G Android Development] Phasma343:
Ah, ok I get what you are doing.

No you will want to remove a line from the overlay/frameworks/base/core/res/res/values/config.xml file.

this line

- <bool name="usingsamsungRIL">true</bool>

After removing that it should allow you to build.
[Epic 4G Android Development] dreamsforgotten:
This is the error I'm getting. Just did a resync

device/samsung/epic/overlay/frameworks/base/core/res/res/values/config.xml:156: error: Resource at usingsamsungRIL appears in overlay but not in the base package; use <add-resource> to add.

Install: out/target/product/epic/system/lib/libOMX.SEC.AVC.Decoder.so

make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Error 1

make: *** Deleting file `out/target/common/obj/APPS/framework-res_intermediates/package-export.apk'

Edit: I thought to do that but will I loose a RIL fix the EpicCM team has worked out by removing the line?
[Epic 4G Android Development] Phasma343:
yes you will lose one of the RIL fixes, but it will not build otherwise.
[Epic 4G Android Development] dreamsforgotten:
Thanks, it just built. Gonna play with it now before looking at more of the code. I appreciate the quick responses!
[Epic 4G Android Development] bricky23:
I would love to have the latest kernel, but I have no idea how to compile kernel. And I just get lost trying. It would be great if someone could upload it. Thanks
[Epic 4G Android Development] dreamsforgotten:
I might have one tonight if so I'll send it to you
[Epic 4G Android Development] deano0714:
Me too please! Thanks
[Epic 4G Android Development] Phasma343:
I have one I compiled earlier I can upload when I get home from dinner.
[Epic 4G Android Development] deano0714:
Does it fix anything?
[Epic 4G Android Development] theandrewgordon:
I would be very interested as well.
[Epic 4G Android Development] Esteway.619:
I would be interested also
[Epic 4G Android Development] Phasma343:
No idea. Haven't tested it yet. It would probably be better coupled with a full rom compilation.
[Epic 4G Android Development] Phasma343:
here is the kernel as promised.

http://dl.dropbox.com/u/27414438/phasma_cm7_kernel.zip
[Epic 4G Android Development] Esteway.619:
Thanks bud ill try it out and report back

Edit: did u add anything to it compared to the other cm7 kernel?
[Epic 4G Android Development] Phasma343:
The kernel was built from the code on github with none of my own changes made to it.
[Epic 4G Android Development] Esteway.619:
Ohh ok. It's running smooth so far. If bugs come out will let u know
[Epic 4G Android Development] bricky23:
Thank you for this. You are truly a gentleman and a scholar!

Sent from bad to the bone Epic
[Epic 4G Android Development] maldito.boss:
how can i make a zip with the last update from github?

i have everything done with ubuntu i just dont know how to make the zip file to be flash!!! sorry but i been tryin to figure myself with no luck
[Epic 4G Android Development] Phasma343:
Easiest way is to use the existing Alpha4 zip file and overwrite everything in it.
[Epic 4G Android Development] maldito.boss:
which commmand? that what i meant but thanks for the repley
[Epic 4G Android Development] Phasma343:
You mean the zip command? :confused:
[Epic 4G Android Development] maldito.boss:
Yes