[DarkMoS]

Yep there has been 2 pages of merges since yesterday, time to cleanup my setup ^^
I guess we now have to run roomservice before each build in order to keep the kernel up to date?

repo sync
build/tools/roomservice.py cm_tenderloin
. build/envsetup.sh
brunch tenderloin

[eyeballer (OP)]

DarkMoS, on 16 April 2012 - 10:36 AM, said:

Yep there has been 2 pages of merges since yesterday, time to cleanup my setup ^^
I guess we now have to run roomservice before each build in order to keep the kernel up to date?

repo sync
build/tools/roomservice.py cm_tenderloin
. build/envsetup.sh
brunch tenderloin

No, just the first time. After that it's added to local_manifest and will be sync'd with repo sync.

[Redflea]

eyeballer, on 16 April 2012 - 11:44 AM, said:

No, just the first time. After that it's added to local_manifest and will be sync'd with repo sync.

Cool...thanks for all the info. I'll update the guide shortly.

[Redflea]

Built, used the new command to add the kernel build from source, flashed, starting boot now...stuck on Cyanogenmod logo (no boot animation) for a long time (minutes)...gonna wait a bit longer and if it doesn't complete boot I'll use power/home to restart and try again.

Wiped cache and dalvik cache and looks like it's still not booting.

Awwww...

Next trying a wipe data/factory reset. Yup - goin' nuclear! :)

That didn't work...restored my kernel from my last backup and it's booting...so something obviously either w/the compiled kernel, or a screw-up on my part. What should be the contents of the local_manifest file at this point? Mine just has stock content (http://pastebin.com/b3bdaQdr).

Anyone else getting it to boot w/the changes to build the kernel integrated?

Edited by Redflea, 16 April 2012 - 02:29 PM.

[lonewulf]

my build just stopped about 2hrs in (takes me about 3hrs total to complete a build after a make clean ect)

http://pastie.org/3800998

Im thinking my problem is something to do with my local_manifest.xml (didnt think I had anything kernel related in there, but appears I do)

http://pastie.org/3801262

any help would be greatly appreciated, thanks everyone.

[eyeballer (OP)]

Redflea, on 16 April 2012 - 01:24 PM, said:

Built, used the new command to add the kernel build from source, flashed, starting boot now...stuck on Cyanogenmod logo (no boot animation) for a long time (minutes)...gonna wait a bit longer and if it doesn't complete boot I'll use power/home to restart and try again.

Wiped cache and dalvik cache and looks like it's still not booting.

Awwww...

Next trying a wipe data/factory reset. Yup - goin' nuclear! :)

That didn't work...restored my kernel from my last backup and it's booting...so something obviously either w/the compiled kernel, or a screw-up on my part. What should be the contents of the local_manifest file at this point? Mine just has stock content (http://pastebin.com/b3bdaQdr).

Anyone else getting it to boot w/the changes to build the kernel integrated?

Seems like the kernel source didn't get pulled down. Re-sync and run room service again. You should see it say "looking for dependencies... not found.. " then it should dl the kernel source and add a line to your manifest. If that doesn't clear it then clean out the local_manifest completely, rm -rf device/hp then "lunch tenderloin" should pull back in the device and kernel repos.

lonewulf, on 16 April 2012 - 04:02 PM, said:

my build just stopped about 2hrs in (takes me about 3hrs total to complete a build after a make clean ect)

http://pastie.org/3800998

Im thinking my problem is something to do with my local_manifest.xml (didnt think I had anything kernel related in there, but appears I do)

http://pastie.org/3801262

any help would be greatly appreciated, thanks everyone.

Hm.. kernel build failed? Didn't it work for you last night in the IRC chan?? Join us again :)

[lafester]

damn I had put off building for awhile since we had some nightlies rolling in.
ugh. now I want to check out all these changes.

maybe later tonight i'll have to dive in and see what i can do.

Edited by lafester, 16 April 2012 - 04:45 PM.

[eyeballer (OP)]

Actually looks like the build may have been broken for a short time.. So if you sync'd between 2.45pm and 5.10pm EST that might be why. Re-sync and try again :)

[drmarble]

I did a build at Mon Apr 16 16:23:55 CDT 2012, (I keep track of build start and stop times). This was with a full, belt and suspenders:
repo forall -c git reset --hard && make clean && repo sync && make clobber && reposync
It worked fine for me. I have a new kernel now (time is just a bit later than build start).
I did have to remove kernel syncing from local_manifests.xml and apply roomservice.py. Lots or repo syncing. Now it all seems golden.

I still think Trebuchet looks terrible unless you hard code in cellCountX=8, and cellCountY=7. I'm trying to figure out how to get them from the settings.
Thanks for the recommendations on alternate launchers. I just want to make Trebuchet work right.

[Redflea]

Repo sync'd again just now and rebuilding. I mis-spoke above, I didn't mean my manifest was still stock, but that i had started w/it stock. The manifest file was updated w/the kernel info successfully.

Sounds like a re-repo and build will fix things.