Originally Posted by XGX5309

If I build on a HDD it usually takes ~120-135 minutes on an i5-2520. Mainly because I'm always building from scratch (make clean). If you have prebuilts it shouldn't take that long.

That just made my day. I thought my HP G7 laptop w/ i3 and 4gb was a pile for taking 120 min for fresh.

although halfway through I lost my touchpad, and was so unresponsive. So i guess it still is.


And also for the status 7 error, couldnt they just format system in recovery, heard it somewhere, never seen an answer.

Originally Posted by MotoMudder77

That just made my day. I thought my HP G7 laptop w/ i3 and 4gb was a pile for taking 120 min for fresh.

although halfway through I lost my touchpad, and was so unresponsive. So i guess it still is.


And also for the status 7 error, couldnt they just format system in recovery, heard it somewhere, never seen an answer.

LOL. Anything Core 2 Duo (Penryn) or newer should be relatively fine. Any i-series will be well more than ok for compiling.

When you lose responsiveness, I guarantee it's because you have a HDD. Look at the HDD activity light when it's unresponsive... probably on constantly.

As for "status 7" problems, those are so well documented in this forum...

Can't seem to get the 5ghz WiFi fix working for my build. When I modify the two nvram files with ccode=US and reboot, WiFi hangs on trying to turn on. Interestingly when I revert the files and reboot again, WiFi remains hung. Has anyone else run across this?

Sent from my Nexus 7

So I had a little idea, please comment on this, and the idea is an automated build script that we would put on our computers and everyday at, for example, 10 P.M., and it would do the repo sync command and if there was anything new it would automatically build the new rom. How could you be able to do this?

Originally Posted by Tjsherod

So I had a little idea, please comment on this, and the idea is an automated build script that we would put on our computers and everyday at, for example, 10 P.M., and it would do the repo sync command and if there was anything new it would automatically build the new rom. How could you be able to do this?

i hate to burst your bubble.. but its called jenkins and the CM team already has it covered haha. but i suppose if you wanted to do it yourself it wouldnt be very difficult at all. and the only reason to have this is if you are submitting changes to your own personal branch and at that point... just build it yourself... also you wouldnt need to sync bc all the changes originate form your pc.

jenkins.cyanogenmod.com

but if you were so inclined... I would use cron since it has a tidy daemon running and then have it call a script which runs the 2-3 commands. and since scripts run sequentially you wont have a problem.

I have a question I tried to ask in irc but my router decided to tank before I got an answer. If I want to cherry pick a few commits, do I just use the git command on the gerrit page and that's it or do I need to be in a certain directory first or what ? I have gotten to where I can build cm10 in Ubuntu with no problem but I want to learn more and thought I would start there.

Sent from my SGH-I777 using xda premium

Originally Posted by zas0006

I have a question I tried to ask in irc but my router decided to tank before I got an answer. If I want to cherry pick a few commits, do I just use the git command on the gerrit page and that's it or do I need to be in a certain directory first or what ? I have gotten to where I can build cm10 in Ubuntu with no problem but I want to learn more and thought I would start there.

Sent from my SGH-I777 using xda premium

You need to use repo start to begin a new branch on whatever project you're messing with, then run that git command within the project

e.g.
repo start blah kernel/samsung/smdk4210
cd kernel/samsung/smdk4210
<paste git command from gerrit here>

Should we use the smdk4210 or the smdk4210_new kernel source from the team Hacksung github?

Originally Posted by ddominator

Should we use the smdk4210 or the smdk4210_new kernel source from the team Hacksung github?

_new is not ready yet - especially for N7000 and I777 because I have been busy with tethering.

It's also missing a whole bunch of common patches - _new is the future, but right now it's behind the old until we finish patching it up

Build Issue

---

deleted.