yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

That priv.h file just for giggles try removing it from that CPP file that calls it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Okay you are gonna have to chill out with posting full files inside the html tags. haha. All of the files are on github, (assuming one doesn't already have the files locally on their computer already). A link to the file is sufficient.

Also, this line of your build error:

hardware/qcom/media/mm-video/vidc/vdec/inc/omx_vdec.h:92:26: fatal error: gralloc_priv.h: No such file or directory

Tells you the file name, location of the file, and the line number in that file causing the error.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

omxvdec.h take out the priv.h under include I think its line 96 let me look.. Sorry I was doing paperwork and driving home

Line 92
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Well, thanks for that. From where I sit. I had somebody that had more knowledge then I, giving me a ton of help, while they were at work to solve a problem that a lot of people are waiting for. My mode was to get it all to them when there were questions. MY mods and OUTPUTS are unique and not on any git/other persons computer.

While your tip is good to know. Tells me nothing about how to solve the problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Actually it did tell you.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jahrule:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I think he just meant to say that pastebin is a lot easier to scroll through then pasting to forum, especially on phone lol. We all appreciate your time and work as well all those who are helping.
[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 agree pastebin might be a better option ;). Also you can always upload to your github.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I guess my point is this. Say you are talking to somebody that doesn't speak English. Repeating something LOUDER & s l o w e r will not make them understand any better. This answer, while appreciated, won't work. Not for me at least. Saying "Look, there, the error says that file. You have to find that file!" ".... and the line number in that file causing the error."

ok...

"92:26"

92, 26 , both?

Now, what in that error message is SO obvious to you as to what I am supposed to do about it.

Do I:

-Delete that line?

-Change it to something else?

-Delete the file and resync?

-Look for that same file in my CM build folder?

".....that file causing the error." Is there some cryptic meaning of "that"? Is there some standard yet unstated thing you do with "that" files? Cuz a Guide/tut/"ask any question" thread is no place to be keeping secrets. Considering you felt it was worth your time answering at all. A worthwhile reply is one that is effective. Not one that's ambiguous at best and raises 10 questions and a ton of frustration.

Now this is, of course, assuming you know the answer and how to solve it and not just trying to make yourself look smart.

---------- Post added at 05:54 PM ---------- Previous post was at 05:28 PM ----------

When this thread works, there is no better. However, there are times when a question can sit for 3-4 days or more. So when you get a quick response ya kinda want to do your part, as the asker, to follow up. If/when somebody helping asks for more info and you feel that if you don't get it fast enough and catch them giving a free moment, you might loose the chance at that quick answer.

I did try minimal. The forum provides scroll boxes, I was asked for more. I had at least 2 peeps asking for info. This isn't a build thread. Anybody has to keep in mind that there WILL be somebody trying to do and coming across the same issues I had. While, a little verbose, following what was happening was made better by making it clear with information. So, with that in mind it isn't a stretch to assume that some other person trying to build the same thing, isn't going to be following the thread on a phone.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Easy killer. And i thought i was frustrated. I know that not getting a straight answer can be one of the biggest hassles of learning this stuff in this way. I am still trying to come up with a successful build on the N4 and although some devs were helpful, some of the help was like pulling teeth. I had a dev help me with one part of my build problem and when i had another that i attributed to the local manifest being wrong, i was given the reply ' yep, thats most likely the problem'. Seriously? I had already asked that dev and another to share their manifest with me and youd think i asked em what their old lady's phone number was! Anyway my point is this: since I've 'left' this forum the only one to always offer help for a device he doesn't even use is M45. Not defending him, I'm not the type to jump in on anybody else's beef, just saying that he is probably thinking that it can be figured out on your own with some research. Then again maybe not. But maybe a pm would get a more detailed answer. Not my business really but then again it is my thread. My penny and a half for what its worth. Yukyuk:D. I miss you guys. Its not as much fun building for a device that doesn't really have any kinks. All the ROMs are already in production so coming up with something that stands out is twice as difficult. Maybe i just suck at it.:(
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Basically, yes. That. I couldn't seem to find a way to say that wouldn't possibly come off as sounding rude, so I gave up and decided to come back to the post later but then I got busy with stuff.

@ wantwowan2

I took another look at it, and gralloc_priv.h is found in hardware/qcom/display/libgralloc/

If I had to guess, I would say the reason you are getting the error is due to the fact that you are using CM's repo, but you're using the display-caf variant while we are currently setup on CM to use the regular display repo. In the dependencies file you posted, at the bottom is this:

"repository": "CyanogenMod/android_hardware_qcom_display-caf",
"target_path": "hardware/qcom/display-caf",

From what I recall, Steve (CM) said he couldn't get our phone to play nice with that repo so we don't use it. We use "CyanogenMod/android_hardware_qcom_display" (no caf).

edit: I forgot, I made a post about that in this thread last month :) here:

http://xdaforums.com/showthread.php?p=37947947#post37947947
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That makes sense. I swear somebody was saying up and down awhile back that we have to use -caf hmmm, my cm10.1 hardware/qcom folder has both in it...

I was stuck on -caf cuz slims local_manifest actually has both of them in there.

Thanks, that really colored the picture for me.

---------- Post added at 06:39 AM ---------- Previous post was at 06:12 AM ----------

http://www.slimroms.net/index.php/new-addons-menu
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Ok so I have been following this and am doing some of the the same things only with the hercules. I am back to stock build now. What do ya'll think the next step should be? I get a good solid build with everything working great except no camera. Is everything working minus camera in skyrocket build?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Thing is I believe it needs both display and display-caf. Also If it isn't needed it shouldn't call for it at all (this might be my fault I'd need to check my commits) because hardware/qcom/ folders are there by default regardless of what device you are compiling. CM makes you download them regardless when you sync.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
:o Yeah, that was probably me too. If you look at the link in my previous post I was quoting myself where I previously said that we were using the dispay-caf repo, and noting that this was not the case anymore and that we were now using the regular display repo.

I know both display variants are synced to the local build tree, but I don't think there are any files related to any msm8660 device that call on the display-caf repo. It's basically only there for the 4-layer composition stuffs for the msm8960 and newer hardware.

Based on his error message, there must be a line that is pointing to the -display-caf somewhere, because it's complaining that gralloc_priv.h does not exist, and that's true for the display-caf repo, but it's there in the default display repo.

edit: well, actually, I only see the display-caf in his local manifest. He said he had both in his /hardware/qcom folder, but unless he edited the default manifest, that would mean he is syncing CM's android_hardware_qcom_display-caf repo, and Slim's hardware_qcom_display repo. I haven't looked at the difference between CM's default display repo and Slim's display repo in detail yet, though.

Also, I just saw this commit from sk8erwitskil on Slim's qcom-common repo a couple weeks ago (02/17):

https://github.com/SlimRoms/device_...mmit/84e022e74451a5b5f774c3a1a3c27bd0f1558c81

He switched it back to using the display-caf repo for msm8660 devices for some reason.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Thats from CM and Cyanogen also has a caf commit in msm8660-common here. So CM skyrocket & Hercules (and Gnote LTE?) use display-caf.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That said and ONLY for those following this thread and are aware of the trouble we have been having building SlimBean.

Here is

"

FrankenSlim

" :eek:

This rom has not been Git Synced. I had to put it together with my most recent build material and downloaded chunks from here and there. A huge thanks to ktempleton for putting up with my slow approach to learning and mistakes. We are taking HOURS of chat, very good guy.

If you are:

- a bit crazy

-have flashed more then 30 roms with success

-really HAVE to have a new slim to try

-willing to provide the short & skinny on how it turned out ie: Cam, gps, browser, wifi

-a bit more crazy

~~~~~~~~~~~~~~~~~~~~~~~

ZERO-MOD-SLIM-ROM

: Tester

-NANDROID PLEASE!

-FACTORY WIPE

-WIPE CACHE

-FORMAT SYSTEM FOLDER

-WIPE DALVIK CACHE

-FLASH ROM+GAPPS

-Slim-4.2.2.build.1.2-i727-20130308-0433-UNOFFICIAL.zip - 85.07 MB

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

I want to try this but am afraid. The last time I flashed slim bean it bricked.

Aw, what the hay, I'm going in.

Installed fine using TWRP. Booted (nice boot ani), letting it settle for a few minutes, then reboot, sign in to google and advise..

SGH-I727 - Peace
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Hmm. I had not noticed that. Well now I'm at a loss again. There must be something missing from one of theupstream merges from CM to one of Slim's repos (not sure which repo anymore now) if it's using display-caf, but when it's building the hardware_qcom_media stuff it's looking for gralloc_priv.h when it gets to the hardware/qcom/media/mm-video/vidc/vdec/inc/omx_vdec.h file. In CM's version of that omx.vdec.h file, it still has that ifdef for it on line 92:

#if defined (_ANDROID_ICS_)
#include <gralloc_priv.h>
#include <IQService.h>
#endif

As does's Slim's version. The only difference between CM's version and Slim's for that file is 5 additional lines starting on line 171, but I'm fairly sure it's not related to the issue:

//BitMask Management logic for U32
#define BITMASK_CLEAR_U32(mArray,mIndex) ((mArray) & (~(BITMASK_FLAG(mIndex))))
#define BITMASK_SET_U32(mArray,mIndex) ((mArray) | BITMASK_FLAG(mIndex))
#define BITMASK_PRESENT_U32(mArray,mIndex) ((mArray) & BITMASK_FLAG(mIndex))
#define BITMASK_ABSENT_U32(mArray,mIndex) (((mArray) & BITMASK_FLAG(mIndex)) == 0x0)

(That came from this commit a little over a week ago: https://github.com/CyanogenMod/andr...mmit/dbe5573b17afe64c74d3ae55cbda5225b29968e9)

I don't have the Slim repos on my computer locally to do a more in depth comparison. If no one else can figure out the issue, I'll see if I have room to add slim repos on my linux partition.

**edit: Apologies, it's been a long week and I'm sick. Somehow either yesterday or today I got it in my head that the gralloc_priv.h file was only in the default display repo and not the display-caf repo, however, it is indeed in both display variants so there's no reason one should get a "no such file or directory" error. Are you getting that error or is it just wantwowan2? If it's just him, then it's most likely a user error, and not an issue with the repos. The camera still not working is a separate issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] berniesteven:
Ok, restoring nand. Flashed using TWRP, let it settle, reboot, and bootloop when I hit start. Reflashed, and same thing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

And he did sync yesterday lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I did a fresh build for skyrocket, can someone test this and see if it is as stable as my same build for hercules? There should be no camera, but everything else works fine on my hercules build. I do not have this device and it could brick your phone etc etc. My hercules build is very stable and I don't think there is much if any risk. http://d-h.st/Wl6

Please be sure and check the MD5 Sum.

EDIT: gps don't seem to work
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Got my phone back! They put stock 4.2.1 on it and it has features I've never seen before. ++++ It isn't a Rogers version. Has 0 bloat and has GAPPS. First thing--->make a rom out of it! hahaha

---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------

If you still have it on there, you could try a diff kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Where did your phone go and who put what on it, now? Official JB 4.2 from AT&T?? Does that even exist?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hechoen:
How about a screenie of about phone?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Ok, build question for the experts here ... I'm adding a new sysfs interface to the Moretz kernel to all users to manage the GPU frequencies (since I overclocked both 3d & 2d).

Problem I'm running into is that my build won't pull in the gpu_freq.c file during compile.

Here's what I've done:

created gpu_freq.c that houses the code for the sysfs interface:

https://github.com/carvsdriver/msm8...2ab9e8c402e2a70d/arch/arm/mach-msm/gpu_freq.c

I added the config to my defconfig files (relevant commit, has a bunch of other stuff, but defconfigs are at the top):

https://github.com/carvsdriver/msm8660-common_moretz/commit/4a90fe5d4a1ef71205325082a514e457311a1cf3

Then, I updated my Makefile in mach-msm to use the config (can be seen in the above commit).

What am I missing here? I even went as far as adding this to the Kconfig file a little while ago and it's still a no go during build ...

https://github.com/carvsdriver/msm8660-common_moretz/commit/71a803f79197962e1559415b0c4d89942721c0c8

I noticed the same problem when I added USB fast charge, so I just hijacked the CONFIG_ARCH_MSM8X60 setting in Makefile to include it.

I'd prefer to fix this properly ... any help would be appreciated. I'm sure it's something completely silly that I'm missing. Once I get the sysfs interface in the build and working, I can write the code to actually use the settings :)

Edit:

You can see all the related commits for this in my gpu-test branch of Moretz - they start on March 8th.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ayysir:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Tried forcing the the file to compile using obj-y += gpu_freq.o into makefile ?
[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]

Oops .. Meant to hit reply, not thanks ...

Anywho, it was a Kconfig issue. All set now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ayysir:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Lol cool, figured that way wouldn't make it user controlled since you need kconfig for sysfs interface
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
Sorry but kinda lost is there anthing that supposed to be in the AOKP step (2)?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I don't know why the local manifest contents there are empty now in those instructions, but that was from AOKP-jb (Android 4.1). The process would likely be similar for 4.2, however, I haven't tried to build AOKP in many months so I haven't looked at which xml files might need to be modified or removed from the skyrocket device repo overlays (device/samsung/skyrocket/overlay).

try this as the local manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="AOKP/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb-mr1" />
<project name="AOKP/device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jb-mr1" />
<project name="AOKP/device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="jb-mr1" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>

You could also change those 3 AOKP repos to CM's repos instead.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" 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" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>

You can look at AOKP's skyrocket device repo from ICS here for comparison to help you figure out what you might need to add/remove. You could also take a look at their repo for the Hercules, as that one actually has a jb-mr1 branch:

https://github.com/AOKP/device_samsung_hercules
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
Thanks how i create the local_manifest.xml or should i copy another and than edit, so i noctice there are many vendorsetup.sh file dont know which to add it too.

---------- Post added at 10:19 AM ---------- Previous post was at 10:07 AM ----------

I see my problem i believe there is no device/samsung/skyrocket?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ..Cory..:
Can anyone help figure out what my problem is here? I've been trying to build CM10.1 for days now and I'm officially stumped. This is my latest error/problem.

This is during the build process. It just stops after that line. Any solutions?

Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
ccache

How do I setup ccache to use with an external drive? Or would it even be benificial to do so? The reason I ask is because I'm limited to small SSD space.
[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]

As long as its mounted, same way as normal just change the path to the cache to wherever you want.

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

How much ram do you have? I've seen that happen when you run out of available memory.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ..Cory..:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

8GB, never had a problem with RAM before. I also used to build CM10 ROMs on a nightly basis... I'm just so stuck right now.

I thinks it's more of a problem with some sort of rule? Because it says it doesn't have a rule or whatever for that file.

Sent from my very expensive paperweight!
[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]

Oh duh, I totally missed the error message.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
When our server maintainer was setting up our build server was testing setups to get the most out of it he found out that having SSD didn't show a huge difference compared to HDD (as long as they where 7200rpm+ on Raid) however having CCache on a different drive (as in different to where the source is at) shows much better compile times in general. On my laptop I have source in my SSD and CCache on HDD, though I rarely compile anything on my PC except kernels lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ..Cory..:
So do you know what it is...? :p
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You create the local manifest yourself. Just open a text editor (like gedit) and paste the lines I posted in my previous reply into the blank document, save it as roomservice.xml at /.repo/local_manifests/roomservice.xml. (You will probably need to create the "local_manifests" folder. This is a recent change, along with the change in the file name from local_manifest.xml to roomservice.xml). After you have this set up and run the repo sync command, then it will download all the many GBs of source code from the default manifest and the local manifest you created ( along with the skyrocket device repo)

Since you are new to building, I would recommend that you start off with CM10.1 as our device has official support with that source. It's significantly easier and more straight forward. Once you have a better understanding of the process for setting up the environment and the general mechanics of the build process, then you could branch out into building ROMs that don't have official support (which require more tweaking/modifying prior to building).

---------- Post added at 06:10 PM ---------- Previous post was at 06:00 PM ----------

From teh Androidz:

http://source.android.com/source/initializing.html
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I love this thread and all the help you guys give! Sometimes the answer stares you right in the face and you just simply forget to wear your helmet like Your supposed to :p

Thanks guys. I got the note 2 and I'm having to start all over.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
haha whoops. I think I quoted the wrong post in my reply. It was meant to be a reply to your question about ccache.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
So I just noticed that you already have a thread with your AOKP builds. You seem to already have it covered before your post in this thread, so now I'm quite confused.