yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
Check to make sure your device and vendor trees are complete for your device. I was getting these errors when I didn't have the right files in my vendor branch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Having a case resolution issue with eBay about a skyrocket I sold to a guy in the Ukraine. DON"T EVER DO AN INTERNATIONAL SALE ON EBAY! It is more trouble than its worth, and those f****** will side with the buyer no matter what. But, I did complete a second build last night, to make sure it wasn't just dumb luck. Good to go, did some research on gits and commands. Almost ready to do a real build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'll be the first to admit that I am a total novice, but these are the steps I take:

cd ~/cm10

. build/envsetup.sh

vendor/cm/get-prebuilts

repo sync -j16 <--- I have also used -j4 on occasion, because I read that -j16 is the highest speed settings for high speed computers(multiple cores on multiple cpus)

CM_EXTRAVERSION=-yourname CM_SNAPSHOT=1 brunch cm_skyrocket-userdebug

After that, its just a matter of sitting back and watching it fly. You may need to start over on your set up, or delete some unneccessary files. Once again, I am a total novice, and my steps may be up for argument. Regardless, I have had 2 successful builds and am now learning how to interact with the process, i.e.add changes.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
i can confirmed this did NOT work for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aSquard:
I'm not entirely sure, but it came with Windows Vista so it's not ancient. Alright - I'll give it a whirl today after work :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
Would love to know the steps you took to get it going. :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
1. Well first I synced the source and device dependencies.

2. After that then I had to create a few files in device/samsung/skyrocket -- Android.mk, AndroidProducts.mk, custom_skyrocket.mk and edit the vendorsetup.sh

3. Also I removed the cm.mk and cm.dependicies files.

4. I then started the build but had some bionic errors so I made the proper changes to get past that. (TARGET_CPU_VARIANT problems)

5. I then had issues with selinux, sepol and sepolicy so I copied the files from my AOKP source

6. So far it is still building....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
I so wouldn't be mad if I got a PM and a tester link!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
If you would do me a solid and lay out your steps after compiling; I'd like to get it in my HTC ONE Project Rookie thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
So, I got a build of omnirom but it failed to flash. Now they decided to change everything named custom to omni... back to it again to see if I can figure this out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
I've heard the same from other devs working on that project. Just an FYI.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Fixed it. It looks like it was a TWRP-related issue. I removed TWRP from my build tree and restored the default bootable/recovery repo from CM. After running a clean build and flashing the build on my phone, the battery charging images/ animation while powered off is back to normal.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
THATS IT!!! I had forgotten. Yeah, the reason I never experienced it is because I went with PhilzTouch. I had TWRP problems as soon as I got the ONE forum, so I switched. Glad you got it worked out. Wish I could have been more help.

What would it take to get M4570MOD on my device? I miss that little '**** off' in my top corner. Do you even work on that anymore?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I haven't updated the thread for that theme in a (long) while but I still add some changes to it here and there and throw in whatever the latest version is into my ROM builds. Here's the most recent one I have (uploaded just for you ;)).

http://d-h.st/Ygd

Also, it's difficult to keep up with all of the app icons, especially for apps I don't use personally, so if you see an app that used to have an icon themed, but doesn't anymore, let me know.

Also, let me know if there are any obvious UI bugs you happen to see. I don't know if everything for xhdpi is up to date with what I have for hdpi stuffs, so it's possible I've missed something for xhdpi.

---------- Post added at 06:39 PM ---------- Previous post was at 06:17 PM ----------

btw, I decided to make an updated version of gapps last night/this morning. It's exactly the same as the official gapps-jb-20130813.zip but I updated for apps that have newer versions available: Play Store, Gmail, GmsCore (Google Play Services), GoogleNow, TalkBack, and Google Plus.

gapps-jb-20131018-signed.zip - 88.41 MB
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
That theme is pretty awesome! Really dig it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Yeah, it's strange. I have been building 4.3 and I synced my repo today then all of a sudden I'm building 4.3.1. I did get it to finally compile, but am not sure that it is working correctly. I had it lock up on me while it was turning offs the screen automatically. The screen off beam fizzled out strangely and the capacitative buttons stuck on. I had to hard boot it.

I found a commit in another repo for the Google msm kernel which contained a definition for 'MDP_YCBYCR_H2V1' which I added to my working source, but only added the definition. I did not add the rest of the commit. This allowed me to finish compiling.

https://github.com/MoKee/android_kernel_google_msm/commit/c53fb6d134fab3e3d7a022ba857d9cad4fcfa59a

Does anyone know if this commit is related to this issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I'm using Linux mint Olivia and have not recently upgraded. The repo seemed to update though when I synced my repos today. I'm using jdk 1.6 though instead of 1.7.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I just ran into this error as well. I noticed that when I synced up it said

hardware/qcom/display-caf: discarding 41 commits

which means CM did some significant changes to that repo (likely reverted it a long way back and then added some changes back on top of it or something like that). Not sure yet what the resolution to this issue is though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Yeah, when I look at the github for display-caf, there are a lot of commits recently, but I haven't been able to make any sense of it.

I assume there is a way to set the repo back in time, I just don't know how to do it. I know how to do it with a normal git repo, but android seems to be a beast that way.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ThdDude:
I was having same issue with Hellybean after merge. [MENTION=5105835]Cl3Kener[/MENTION] helped me out, we switched CyanogenMods repo with Liquidsmooths in my manifest for the display-caf and it compiled and is running fine. Quick and dirty fix to get it to compile until cm fixes their issue. Doing my 5 builds of Hellybean this way tonight and its working fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Hmm... Didn't think about doing that. I'll have to give that a try when I get tired of working on my VanirAOSP project for Skyrocket.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I found the same commits for the sony_msm8x60 and sony_apq8064 kernels in CM. I added them to my kernel tree as well and just finished the build. About to flash and see how it goes.

Here's the changes. I added another one as well:

msm_fb: display: Add support to YCBYCR MDP format

msm: rotator: Add support to YCBYCR rotator format

edit: well that didn't go well. It's crashing all over the place, particularly when I go into Setting and click on anything. I''m not sure though whether that has anything to do with the change I made, the changes to display-caf or something derpy in PAC-man. They've been getting rather liberal lately with what they're willing to merge and I don't agree with some of it.

edit2: tried using Slim's display caf and was getting the same FC errors so I did a full wipe and flashed the build again and it seems to be all good now. Looks like there were some commits in Settings and Frameworks in PAC that were causing issues for Settings Provider data. So, perhaps those kernel changes might not cause any issues. Will have to do some more testing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I added both commits to my latest build and am running it right now. So far so good ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cameron581:
getting this error later on in my build never seen it before

/obj/JAVA_LIBRARIES/com.android.emailcommon_intermediates/classes)

packages/apps/Email/emailcommon/src/com/android/emailcommon/utility/SSLUtils.java:35: cannot access javax.net.ssl.KeyManager

bad class file: javax/net/ssl/KeyManager.class(javax/net/ssl:KeyManager.class)

unable to access file: corrupted zip file

Please remove or make sure it appears in the correct subdirectory of the classpath.

import javax.net.ssl.KeyManager;

edit: switched java version changed some things here is the full code

packages/apps/Email/emailcommon/src/com/android/emailcommon/utility/SSLUtils.java:35: error: cannot access KeyManager

import javax.net.ssl.KeyManager;

^

bad class file: /home/cameron581/camzfox/out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/classes.jar(javax/net/ssl/KeyManager.class)

unable to access file: corrupted zip file

Please remove or make sure it appears in the correct subdirectory of the classpath.

make: *** [/home/cameron581/camzfox/out/target/common/obj/JAVA_LIBRARIES/com.android.emailcommon_intermediates/classes-full-debug.jar] Error 41
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Anyone have difficulties getting supersu working on 4.3.1 (cm10.2)? I tried first to allow it to update the binary the normal way, failed but expected. Used twrp/cwm method, this installed everything but after boot no superuser access. None of my apps were initiating the dialog, so I couldn't grant permission and therefore no superuser access. I did finally manage to get it working and am not sure what finally worked. Could it be the numerous reboots or turning on universal init.d (init.d works properly already on my kernel)?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I had a similar error on another package a while ago. I deleted the package directory and re-synced to fix the error. There were left over artifacts from my last build that were causing that error ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I've also had that qcom/display-caf error; I hust saved a copy of /qcom from my last successful build and pasted. So far, it seems to have workd.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Me too. Had to manually patch the files, but it built and seems to be working fine now. Thanks m4570d0n for the pointer in the right direction!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
I was able to patch the the qcom/display-caf issue using the information provided and got my VanirAOSP project running again last night. I'm continuing to work on isolating the issue with the sdcard not mounting. Seen some good tips from other device forums that had the same issue and I hope I'm getting close, but don't want to make any promises just yet. Still :banghead: at this point.

Gonna patch my CM build tonight and see if I have the SU issue. I do know that the regular nightly has been either OOD or running a weird config for the SU binary because my Titanium backup has been giving me the "while it may work something isn't right" warning for about a week now. Will have to see if there are any commits on this in the repo or on the bug tracker.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I forget what it is but there are key aspects of the code that are closed source.

The dev sighting others mad him feel bad so he's not going to open it up.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Last I checked it was all open source (I made a build yesterday)... What features are closed source??

I have been following along on irc and there are some features that have to be activated (not merged yet) to be included in the build but are all available.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Got my CM builds going again and have a fully working 10212013 build. :victory::highfive:

I tried to apply the fixes from the previous posts as I had done for Vanir. While it did allow me to build, I noticed that I had some serious graphic issues in both roms (display sync problems, color palette was off, artifacting...). I didn't have a working backup and I didn't make a backup before applying the fixes :o, so I cleared the folder and re-synced the qcom/display-caf files from LiquidSmooth's repo as I had seen mentioned in an earlier post and all was well again. Here are the lines I added to my roomservice.xml to get things moving again:

<!-- temporary patch of qcom_display-caf -->
<remote name="qdc" fetch="https://github.com" />
<remove-project name="CyanogenMod/android_hardware_qcom_display-caf" />
<project name="LiquidSmooth/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="qdc" revision="jb3" />

(Probably don't need the lines for the remote stuff since the local repo is already set to github, but I still added it in anyway.)

As for the SU binary, mine is working with no problems, but I'm still getting this message from TiBu:

Your SU binary (version "13 com.android.settings") is funtional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead.

Just my thought, it probably needs to be updated to the latest binary (if there is one).
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Not sure, but this commit might be relevant to your SU issues, if you are doing a user build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
If github is already defined in the default manifest you can just add it this way:

<project name="LiquidSmooth/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="jb3" />

As long as it's a github repo, and you include the name of the github account in the project name (i.e. project name ="LiquidSmooth/*", project name ="CyanogenMod/", etc.) you don't need to add any definitions for remote repos. You can just use the github remote.

Also, just wanted to note that those two YCBYCR related commits I posted the other day were just merged into the kernel repo on CM this morning:

msm_fb: display: Add support to YCBYCR MDP format (Merged)

msm: rotator: Add support to YCBYCR rotator format (Merged)

So building shouldn't be an issue anymore. I don't know about any remaining issues with artifacting or the palette being off and such, but perhaps I missed it.

Yeah, no SU issues here either. Also, that warning was added in the last update to TiBu (v 6.1.1). It's in the "What's New" section of the app description on the Play Store and in the change log :

Titanium Backup has been updated to v6.1.1
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Then I don't know what I am talking about, maybe....? lol . Pretty sure that was the same omni we were talking about in the DU chat a few days ago. If the build finished then maybe I'm on glue but I can check it out for sure.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
believe all their stuff is either in github or Gerrit open source
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I'm not sure how I got into this situation, but I've run into a strange problem. I have been building my own version of a 'slim' ROM, where I basically take a stock CM10.2 tree and remove stuff I don't need or want, and tweak a couple of things to my liking. I use patch files, so after a repo sync, I apply the patches, then after the build I remove them, so it should still be a stock CM tree when it's done building. This has been working well for about a month or so, but after the problem with the video driver on the weekend (msm* updates), even though my repo says it is updated, the commits aren't there. I have to apply my own patches to the the msm files, and then it will build. If I try and cherry-pick the commits, git says they are already applied, but the files are not changed. I have a separate repo tree in another location that is completely stock with no modifications, and it does show the commits to the msm source files. Short of re-downloading the repo *again*, is there anything I can do to try and get my local repo back in sync? I am not a git expert or a developer by any means, as vincom says, I know how to do stuff...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Just delete the kernel directory and resync that project.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
[MENTION=4685003]car vs driver[/MENTION] I just wanted to thank you for pointing me to your commits for the screen unlock delay. I was able to implement your changes and it fixed the issue ;) very happy with my cm10.2 now thanks to you ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
So simple, and obvious. It worked, of course, thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Yep, you are correct, as usual. Turns out it was some other guy that was blaming one of there commits for breaking HIS private repo. hehehe oops! Carry on....

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

<remove-project name="CyanogenMod/android_hardware_qcom_display-caf" />
<project name="DU-Final/hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="jb-mr2" />

Fixes diplay_caf for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I'll have to give this a try. Display-caf broke my liquid build earlier. A nap first though.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
I'm trying to build SlimBean right now, and while there were some changes to the OP I had to make (like the git-repo path in the curl command), I get stuck in the build process with this:

lunch slimbean_skyrocket-userdebug && mka bacon
build/core/product_config.mk:231: *** Can not locate config makefile for product "slimbean_skyrocket". Stop.
Device skyrocket not found. Attempting to retrieve device repository from SlimRoms Github (http://github.com/SlimRoms).
Found repository: device_samsung_skyrocket
SlimRoms/device_samsung_skyrocket already exists
Syncing repository to retrieve project.
fatal: duplicate project CyanogenMod/android_kernel_samsung_msm8660-common in /home/dan/.repo/manifest.xml
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:231: *** Can not locate config makefile for product "slimbean_skyrocket". Stop.

** Don't have a product spec for: 'slimbean_skyrocket'
** Do you have the right repo manifest?

I'm new to building (first go-round, actually), and I'm not sure what I need to add and where. Can anyone help me with this? :confused:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
lunch slim_skyrocket-userdebug
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
The fixes have been committed to CM10.2 Skyrocket branch, no need to do a custom overlay for it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thank you pr. So slim not SlimBean...

Do I still need make bacon though?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
make -jwhatever bacon
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks again. Building now... fingers crossed!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Well, about 2 hours into the build, I got a segmentation fault:

target Java: core-junit (/home/dan/out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes)
In file included from external/llvm/lib/IR/Function.cpp:660:0:
/home/dan/out/target/product/skyrocket/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/llvm/IR/Intrinsics.gen: In function 'llvm::Intrinsic::ID llvm::Intrinsic::getIntrinsicForGCCBuiltin(const char*, const char*)':
/home/dan/out/target/product/skyrocket/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/llvm/IR/Intrinsics.gen:43243:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://source.android.com/source/report-bugs.html> for instructions.
make: *** [/home/dan/out/target/product/skyrocket/obj/STATIC_LIBRARIES/libLLVMCore_intermediates/Function.o] Error 1
make: *** Waiting for unfinished jobs....

I'm not sure what this means exactly. How can I fix this?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Slim skyrocket source compiles. Your build environment is missing stuff or your out of space?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Could be both. I just redid my machine with Mint and the OP tut for machine setup isn't complete for the lib pack. I posted the new required libs a few months back.

Do you have at least 30 gigs remaining on the host partition?

EDIT: from here on Sept., 25th:

Once those are in place, then apply the main lib pack for the latest one in the OP.

It will also whine at the end about pngcrush or the like for photo compression and lzop if you want to compile with moretz/marla
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks for the replies. I have plenty of free space; 125GB drive partition and 81GB free...

I ran [MENTION=4559825]wantowan2[/MENTION]'s suggestion for the new required libraries:

sudo apt-get install g++ dpkg-dev gcc-multilib g++-4.7-multilib

And this is the console output:

Reading package lists... Done
Building dependency tree
Reading state information... Done
dpkg-dev is already the newest version.
dpkg-dev set to manually installed.
g++ is already the newest version.
g++ set to manually installed.
g++-4.7-multilib is already the newest version.
g++-4.7-multilib set to manually installed.
gcc-multilib is already the newest version.
gcc-multilib set to manually installed.
The following packages were automatically installed and are no longer required:
lib32ncurses5 libtinfo-dev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

To me, this looks like I already have the latest gcc libraries, but I'm not sure about lib32ncurses5 and libtinfo-dev. Removal is suggested, but I haven't done this yet.

As far as the pngcrush and lzop libraries, would it hurt to install them just in case?

Maybe my original Intrinsics.gen error is due to a conflict of some kind?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Yep, installing those can't hurt anything. You can also try

sudo apt-get install update

Should ensure that what you have is stable.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Ok, they are installed.

That command didn't work as entered; it couldn't locate package update.

I ran:

sudo apt-get update

I got a bunch of Get and Hit lines then this:

Ign http://packages.domain.com raring Release
E: GPG error: http://packages.domain.com raring Release: The following signatures were invalid: NODATA 1 NODATA 2

So I disabled an entry under Software Sources -> Additional Repositories: packages.domain.com. It is obviously invalid, but idk how it got there.

Then the update command worked and fetched several small amd64 and i386 packages. I'll give it another go, thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Woo-hoo! Thanks for the help guys!

Package complete: /home/dan/out/target/product/skyrocket/Slim-skyrocket-4.3.build.2-UNOFFICIAL-20131026-1749.zip
e6fe735714a795af676d177cdf389e93 Slim-skyrocket-4.3.build.2-UNOFFICIAL-20131026-1749.zip

Now to test it...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
nice!

---------- Post added at 02:57 AM ---------- Previous post was at 02:29 AM ----------

All you have to do is break your build again trying to make it your own! lol

Just ask, I know all about breaking stuff. hahaha