yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I'm confused. Which source are you using? Isn't the shooter kernel android_kernel_htc_msm8660 on CM? If so, it's at llinux kernel version 3.0.53 on the jellybean branch already.

In order to answer your question, we'd need to know the source you're using as the base and the source of the patch. The patch is just a text file of the diff output between the the base and the update. If your base is not the same as the base used to generate the patch, that could be the cause of the errors.

Also, if the source you are wanting to update to has the repo available (which I assume it does) you could alternatively add that repo as a remote tracking branch to your kernel source. Lets say you had just a local repo and wanted to add CM's repo:

cd /kernel/htc/msm8660
git remote add upstream git://github.com/CyanogenMod/android_kernel_htc_msm8660.git

Then, if the CM repo gets updated you can just pull in the updates from that repo and merge them into yours. For this example, I'll assume the local repo you're working with is on a branch named jellybean:

git fetch upstream
git merge upstream/jellybean
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
You my friend are a rocket scientist!(skyrocket get it lol) If I could get you to help me build Slim4.2 that would be great! I can't get a good build for nothing. Slim don't support the hercules or skyrocket any more. But I'm sure with cm's great work I can build but I'm just not doing something right.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Have you tried building Slim4.2 using CM's repos for they kernel, qcom_display-caf, qcom_audio-caf, and the device repos (skyrocket, celox-common, qcom--common, and msm8660-common), and TheMuppets repo for the proprietary vendor blobs? In the current setup on CM, our device repos use display-caf and audio-caf. Slim does not have the caf variants in their repos, which is weird given that their qcom-common repo still has the flag to use the caf variants.

What is the error you get when you build?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
When I have built Slim, I always had a successful, bootable build, only with no wifi. Could never figure it out. Would trying it this way help with that? If I remember correctly, my steps were similar, but without TheMuppets proprietaries. I believe theirs hadn't updated at that point, or something.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Here is a copy of my error:

ls: cannot access device/*/hercules/slim.mk: No such file or directory

build/core/product_config.mk:232: *** Cannot locate config makefile for product "slim_hercules". Stop.

Device hercules not found. Attempting to retrieve device repository from SlimRoms Github (http://github.com/SlimRoms).

Found repository: device_samsung_hercules

Traceback (most recent call last):

File "build/tools/roomservice.py", line 225, in <module>

add_to_manifest([{'repository':repo_name,'target_path':repo_path}])

File "build/tools/roomservice.py", line 156, in add_to_manifest

if existing_project.attrib['revision'] == repository['branch']:

KeyError: 'branch'

ls: cannot access device/*/hercules/slim.mk: No such file or directory

build/core/product_config.mk:232: *** Cannot locate config makefile for product "slim_hercules". Stop.

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

** Do you have the right repo manifest?

here is a copy of my local_manifest:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="SlimRoms/device_samsung_hercules" path="device_samsung_hercules" remote="github" revision="jb" />

<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.1" />

<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />

</manifest>

By the way sorry,I got called out of town again and couldn't reply. I don't know if any of ya'll have been in east Tx. but cell coverage such's there!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I believe slim has a different revision for 4.2

jb4.2 is the branch
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
That would explain why I had issues, if the update came so recently. Thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Also, I was incorrect about this. At one point this was true, but a few days ago or so, around the time when Mr. CM updated our kernel again he switched back from the display-caf variant to the default hardware/qcom/display

I noticed this from one of his comments on gerrit for a change to device_samsung_qcom-common:

http://review.cyanogenmod.org/#/c/31734/

And then realized I was dumb when I looked back at BoardConfigCommon.mk in that repo:

ifneq ($(TARGET_BOARD_PLATFORM),msm8660)
TARGET_QCOM_DISPLAY_VARIANT := caf
endif

I glazed over that part thinking it said ifeq not ifneq.

For anyone not familiar with what that means, it's a conditional statement in GNU Make similar to the IF function in MS Excel. ("If 'whatever' = 'stuff', then do 'something', otherwise do 'something else'" or "If 'whatever' = true, then do 'something', otherwise do 'something else'" ) You can think of ifeq vs ifneq as "if equal to" vs "if not equal to".

As an example, let's say you have the following conditional statement in a make file:

conditional-directive
text-if-true
else
text-if-false
endif

If you use ifeq as the conditional-directive it can take any of the followng 5 forms:

[FONT=Courier New]ifeq (arg1, arg2)
ifeq 'arg1' 'arg2'
ifeq "arg1" "arg2"
ifeq "arg1" 'arg2'
ifeq 'arg1' "arg2"[/FONT]

This will expand all the variable references in arg1 and arg2 and compare them. If they are

identical

, the text-if-true is used; otherwise, the text-if-false, if any, is used.

If you use ifneq as the conditional-directive, it can take the same 5 forms:

[FONT=Courier New]ifneq (arg1, arg2)
ifneq 'arg1' 'arg2'
ifneq "arg1" "arg2"
ifneq "arg1" 'arg2'
ifneq 'arg1' "arg2"[/FONT]

This will expand all the variable references in arg1 and arg2 and compare them. If they are

different

, the text-if-true is used; otherwise, the text-if-false, if any, is used.

And that concludes today's Random Facts From M4570D0N.

:)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Huh, I too always had successful slim builds for 4.1.2. Including wifi. :)

As for 4.2.1, is there anybody around to modify the OP/SlimBean to reflect simply what m4570d0n said? lol

Also, I'm loving 10.1. Daydream is cool and I really noticed the kernel updates the other day.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
4.2.2! woohoo!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Broke my damn kernel ... lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'll get the OP fixed shortly. :cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
echo...echo....echo.... =-) What's everybody up to?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You're still using the jb branch for device_samsung_skyrocket from slim and not the cm-10.1 branch from CM and modifying it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Cripes! That sounds major. Is it a matter of swapping out the *.mk files?

---------- Post added at 09:57 PM ---------- Previous post was at 09:28 PM ----------

I tried but it keeps on fetching "jb4.2" from slimroms, adding it to the local_manifest

build/core/product_config.mk:251: *** No matches for product "slim_skyrocket". Stop.
Device skyrocket not found. Attempting to retrieve device repository from SlimRoms Github (http://github.com/SlimRoms).
Found repository: device_samsung_skyrocket
Adding dependency: SlimRoms/device_samsung_skyrocket -> device/samsung/skyrocket
Syncing repository to retrieve project.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
Fetching projects: 100% (1/1), done.
warning: local_manifest.xml is deprecated; put local manifests in local_manifests instead
error: revision jb4.2 in SlimRoms/device_samsung_skyrocket not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:251: *** No matches for product "slim_skyrocket". Stop.

** Don't have a product spec for: 'slim_skyrocket'
** Do you have the right repo manifest?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Hey guys,

i haven't forgotten about updating the OP for Slim. Could someone PM me or lay it out here, so I know exactly what to change and what not to? I need a set of changes that have been successful and I'll take care of it today. Also, if there are any other updates that require a change in the OP, let me know. :cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

That would be so cool. Seems slim is the only thing not building 4.2 for SR. I'm just sorry the tut won't be coming from me. I've been trying a little every day.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I would figure out all the changes on my own, but had to dump my rocket files to make space to build for the N4 and 7.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Pwning my son and all his little buddies on Black Ops II :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Pft! I know what you've been up to.....Kernally goodness. ;)

So, I just synced cm-10.1 and it was all SR stuff.....just say'n

---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------

Too bad you know. You're missing 'Moretz'. Nice to see you pop'n in tho...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yeah, I miss my old crowd. Almost makes me wish that the N4 wasn't Google.

ALMOST. :cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
check my post a few posts up:

http://xdaforums.com/showpost.php?p=37946103&postcount=3055

Also I'm not sure what you still have there in your build tree that's creating that slim dependency but there is no jb4.2 branch for the skyrocket. It's fetching the jb branch (android 4.1) for that repo.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Anyone get a successful slim build??

Should I give it a try??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
wantowan2,

Here's what you need to do.

Delete your /device/samsung/skyrocket repo, and make sure in your local manifest it is pointing to the cm-10.1 branch from CM's github (not Slim).

run repo sync.

Make sure you make the changes I mentioned here:

http://xdaforums.com/showpost.php?p=37946103&postcount=3055

The reason you got that error and it tried to automatically retrieve the skyrocket repo from Slim is because you did not change the PRODUCT_NAME in /device/samsung/skyrocket/slim.mk from cm_skyrocket to slim_skyrocket.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Hey guys I don't know if this is related but I was having trouble syncing slim and by accident put the local manifest in the local manifest folder and it synced everything up without issues

I'm building for the epic 4g touch but my issues were with other things I was pulling in FYI hope it helps

From what I gather the new git has an add and remove feature that remove projects from the default manifest that are on you're local manifest

Well my build is finished but it errored out at the ota zip part don't know exactly which part but from what my wife read to me something about a global define append assert my build was For the sprint s2.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Yes! Please.... If you work it out, could you help out with the OP update for slim?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I'll see what I can do.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
You can't add the same git repo to manifest and local manifest. Rule of thumb it if all devices don't use it keep it off manifest. Also you need to update the device folder. I had to start fresh with cm's skyrocket and msm8660-common. I pushed some initial work to our github, however that doesn't compile. The working source is in our Gerrit waiting for review. I'm looking for testers for the rom. Keep in mind I don't own this device so I don't know if it boots. Kernel size and vendor folder looks good so it should boot . Anyone that knows how to use adb logcat and adb shell and want to test pm me please.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Something is up over there @ slim cuz even my seperarate jb(4.1.2) build doesn't sync right. Same errors for the most part. It fetches but the folders don't resolve.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Nope you broke something on your end. We haven't touched jb branch (4.1) since our last release for 4.1.2.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MHousos:
Any help would be appreciated =P

Hey guys! I'm trying to build Carbon Rom for the Epic 4g Touch but I keep getting this error....does anyone have any suggestions? Thanks in advance!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Here's my build of CM10.1 from today if anyone wants to play around with it. I included a few extras:

framework: Battery bar (1/2)

Settings: Battery bar (2/2)

Camera: Add storage selection (1/2)

Gallery2: Add storage selection (2/2)

Calculator: New Features Part 3

Code reformat

fix user-defined backlight scaling

vibetonz: fix get_time_for_vibetonz

Also ported the center clock status bar settings, and it also includes TitaniumBackup, SuperSU, ADW Laucher and Root Explorer.

Download Link

:

http://d-h.st/qbv
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Gotta say actually, that is usually the case. lol Not sure what seeing as it was perfect (sync/build) up untill I started with cm10.1/4.2.1. I haven't, I don't think, changed anything in that folder....

Anyhoo, I saw your comits to the jb -4.2 slim git. I think anyway. Simular handle as here. I was under the impression that slim was dropping the SR. So does this mean you are taking it over? You have a build together but I haven't been getting a clear picture as to what mods are required. If your goal is to have the git fully updated the I will maybe ask you for the manifest and re init a fresh repo.:D

Right now it seems to be my fav rom to build/use. Perfect mix of cm and aokp I think.

Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I'm the DM for i897 and T959 and I help out with Mako ad I own the device. On top of that I do low level work on the site and I'm pretty much the only guy using the teams social media, beside g+ where a we all help out. I'm just trying to get it up to date best I can however I'm not so sure it's worth the time. But I'll try to iron out the bugs best I can, I don't own this device. FYI since the kernel is CM I'm don't have to post any sources, though I should link to it (will do that later tonight). My pushes for a working source are in our Gerrit awaiting review ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
It's worth it!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Is the Slim gerrit still https://review.slimroms.net:8443? When I go there, there are no open/merged submissions and no projects listed. Just an empty gerrit page.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

You need to log in to access it. For the time being we are keeping it private. I'm interested to know how you know the port #.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

A good magician never reveals his secrets
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Is anyone working on the ubuntu release? This looks like its going to be very easy to build, they are using cm10.1 as there Android code and its very easy to port to our devices! All of the ubuntu stuff stays the same on all devices and hardware stuff is based on cm10.1 for your device. I am syncing now as I type but so is a LOT of others so its going slow. I will keep everyone posted and do a tut. if I get everything going well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Yep I already started but look like I need 12.4 to enable the ppa. Let's see if I can work around it I already repo synd but held back by the ppa stuff.

EDIT: disregard my ppa comment I'm tired and misread.

Roger_n
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I can build a 12.4 VM and give you shell access to it if you want ... :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I'm working on ubuntu12.10 on this partition, All my android stuff is on another partition with ubuntu12.04. I figure since I'm going to be building 12.10 I might as well be running 12.10.

As far as trying to do a tut., things are changing to fast even on the ubuntu porting page:https://wiki.ubuntu.com/Touch/Porting This has changed twice so far today!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I redid my build machine a few weeks ago w 12.10 and has been fine too. There HAVE been alot of updates.

---------- Post added at 09:50 PM ---------- Previous post was at 09:47 PM ----------

I've been keeping my eye on the slim git and working with prbassplayer a bit. Anybody know why, if the info is clearly on the git and downloadable, that I can't sync to it?

wantowan2@TITTYSNATCH:~/sb$ repo sync -j16
fatal: remote error:
Repository not found.
fatal: remote error:
Repository not found.
Fetching projects: 12% (41/336) fatal: remote error:
Repository not found.
Fetching projects: 16% (54/336) fatal: remote error:
Repository not found.
remote: Counting objects: 354, done
remote: Finding sources: 100% (12/12)
remote: Getting sizes: 100% (9/9)
remote: Total 12 (delta 1), reused 12 (delta 1)
Unpacking objects: 100% (12/12), done.
From https://android.googlesource.com/platform/system/extras
f070d34..554ed4f master -> aosp/master
Fetching projects: 59% (199/336) error: Cannot fetch SlimRoms/android_device_samsung_msm8660-common
Fetching projects: 64% (216/336) error: Cannot fetch SlimRoms/android_device_samsung_qcom-common

error: Exited sync due to fetch errors

EDIT:

This is my local_manifest...

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jb-4.2" />
<project name="SlimRoms/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb-4.2" />
<project name="SlimRoms/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="jb-4.2" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="SlimRoms/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jb-4.2" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" />
</manifest>
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Did you repo init? Our manifest changed today. Second can you post what's on your local manifest? Or link it here with paste bin or something?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I must have been adding it as you posted...lol

Heres my default file:

EDIT:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remote name="aosp"
fetch="https://android.googlesource.com/" />

<remote name="github"
fetch="git://github.com/"
review="https://review.slimroms.net:8443/"/>

<default revision="refs/tags/android-4.2.2_r1"
remote="aosp"
sync-j="4" />

<project path="build" name="SlimRoms/android_build" remote="github" revision="jb4.2" >
<copyfile src="core/root.mk" dest="Makefile" />

---------- Post added at 10:11 PM ---------- Previous post was at 09:58 PM ----------

My prob is that I would prefer the other way around. I would far prefer Android on my desktop PC...lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Ok a few things. One if this is the only thing in your manifest its missing a lot. So Repo init to our manifest. Second your local manifest has its branches wrong. Our branches are jb4.2 not jb-4.2 and Celox-c0mmon is missing its branch. If I wheree you I'd delete your local manifest do

repo init -u git://github.com/SlimRoms/platform_manifest.git -b jb4.2

repo sync

First command should add the correct manifest and since you deleted your local manifest it shouldn't have any conflics. This way you don't blow your whloe source just device and vendor folder.