yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok, here you go. I only want to hear that your phone boots! lol (However I am curious to see if the cam is fixed)

SlimBean

Use At Own Risk...yadda...

-4.2.2

-stock everything

-mostly cm10.1 but enough slim to make it slim

-current as of 2/3/13

Slim-4.2.2.build.1-i727-20130301-2058-UNOFFICIAL.zip - 85.49 MB

-MD5: A8389566E966951CFB7A1094B468879C

Slim-4.2.2.build.1.2-i727-20130304-2356-UNOFFICIAL.zip - 85.33 MB

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

Great will try soon
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I don't know if you need or not but sometimes the built in stock kernel got borked and wouldn't boot. (Weird cuz all I would have to do is flash a cm boot.img and it would be great) So, either flash a compatable kernel pack or let me know and I will post a stock one for you/anybody.... :-/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Well, there has been a call out for OP updates. I've thought about helping with that but can't test my process right now...

As for the "kernel tut" in the OP, as far as I know, it's total bunk for the SR. I tried forever and couldn't make that work. (Not to say nobody could...)

The toolchains and the kernel folder have to be on the same level in the file tree.

INITRAMFSDIR=~/initramfs

export ARCH=arm
export CROSS_COMPILE=~/toolchains/arm-eabi-4.4.3/bin/arm-eabi-

cd kernel
make clean
make mrproper
make msm8660_celox_usa_att_defconfig.......... make msm8660_celox_defconfig?? .....whatever_defconfig
make -j4

Then, when it finishes....make a script file like this:

#! /bin/sh
# copy the freshly compiled modules to the initramfs.
cp crypto/ansi_cprng.ko $INITRAMFSDIR/lib/modules/
cp drivers/bluetooth/bthid/bthid.ko $INITRAMFSDIR/lib/modules/
cp arch/arm/common/cpaccess.ko $INITRAMFSDIR/lib/modules/
cp arch/arm/mach-msm/dal_remotetest.ko $INITRAMFSDIR/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $INITRAMFSDIR/lib/modules/
cp arch/arm/mach-msm/dma_test.ko $INITRAMFSDIR/lib/modules/
cp drivers/input/evbug.ko $INITRAMFSDIR/lib/modules/
cp drivers/media/video/gspca/gspca_main.ko $INITRAMFSDIR/lib/modules/
cp arch/arm/perfmon/ksapi.ko $INITRAMFSDIR/lib/modules/
cp drivers/video/backlight/lcd.ko $INITRAMFSDIR/lib/modules/
cp drivers/net/wireless/libra/librasdioif.ko $INITRAMFSDIR/lib/modules/
cp drivers/misc/msm_tsif.ko $INITRAMFSDIR/lib/modules/
cp arch/arm/oprofile/oprofile.ko $INITRAMFSDIR/lib/modules/
cp drivers/crypto/msm/qcedev.ko $INITRAMFSDIR/lib/modules/
cp drivers/crypto/msm/qce.ko $INITRAMFSDIR/lib/modules/
cp drivers/crypto/msm/qcrypto.ko $INITRAMFSDIR/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $INITRAMFSDIR/lib/modules/
cp drivers/spi/spidev.ko $INITRAMFSDIR/lib/modules/
cp drivers/misc/tsif_chrdev.ko $INITRAMFSDIR/lib/modules/
cp drivers/misc/vibetonz/vibrator.ko $INITRAMFSDIR/lib/modules/

What is missing is:

-The easy version patch way?

-correct/specific OC mod

- gov's, IO, etc...

But something niiiiiice and simple.

If there is something wrong with what I've said above. Anybody. Please lets revise it while it's fresh and doesn't get stretchetd over 2 weeks and 10 pages of thread.... :-/ tnx

.......ya know, if anybody feels like it. Hahaha
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jahrule:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Boots and looks nice but no camera
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
You want a strait up stock cm kernel to see? Let me know....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I am using cm10.1 device tree. I also have no camera. Something in slim's build is borking the camera and haven't figured it out yet.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya, but isn't it 1/3 AOKP as well? I thought of "repo init" and sync on the slim folder with AOKP source just once, then re init it for slim. Then test that out. A bit crazy but I really have no idea.

I just repo'd cm's git and there were alot of changes to the kernel I think. It's taking like 3-4 secs per lib. Onse I've never seen before.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

I'll try to get it in the OP today
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
What wre you going to add?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Whatever slim info you give me, heh heh. Seriously, I only scanned your post this morning as I was getting ready to go to work. Thought it had specifics that I could use in the build process. I can post what you posted, but it looks to be a patch at the end of the build. I just don't (can't) build for this device anymore, so I need actual builders to give me whatever updates they want to see made. You're the first one that has even mentioned that updates need to be made. At least I think so. I try to check every day......let me know
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mefrodo:
yep boots and looks nice but also broswer not working, installed dolphin broswer doesnt work either. wifi working ok. do you guys want me to test somting else before going back to my previus rom?

wantowan2, if you make another package ill give a tray
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jahrule:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Sounds crazy enough that it might work lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kaymmm:
For those interested, here's my 2nd build of PAC 20.1.0, with the latest moretz kernel built in. I flashed with the 20130301 gapps and it's working great so far. My repo was sync'd at around 1:00est so it has the latest commits up to 5 Mar.

http://ge.tt/3voHe9a/v/0?c
[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 think that would be a bad idea why don't you just pull in a different camera and gallery with your room service XML set up add and removes on it that's what i have done and it works
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Obviously, I don't care who uses Moretz or for what purpose - heck, most of it is cherry-picked or kanged from something else ... but in the future, before you put up a ROM for distribution give me a heads up. I just like to know where it's being used publicly :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jahrule:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Would you mind posting your XML or build?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kaymmm:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

sorry about that. thanks for all your work! i just saw your post about other cherry picks and might try playing around with some of them.

On a related note, I'm completely new to all of this and was wondering if there is an easy way to determine what commits to the cm kernel are or arent merged into your repository without manually comparing the commits in my browser. I'm guessing this is easy in git, but i haven't been able to find clear instructions...probably cos I'm not googling the right search terms.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Not really ... problem with this particular repo of mine is that git wouldn't let me fork it from the cyanogenmod repo. I have no idea why.

So, I pulled the zip file from git and build my own stand alone repo. I manually cherry-pick the upstream changes and apply my own commits. It has proven to be excruciatingly painful. I fear that fixing it so I have a proper fork would be even more of a hassle at this point because of all the changes I've applied outside of cyanogenmod commits.

As of this very moment, it is up to date.

Also ... if someone has a clever way I can fix the upstream link to the cyanogen repo while keeping my changes intact I'd be eternally grateful. I think what I may do this weekend is create a new fork from cyanogenmod, then use something like Meld to run a massive diff and single commit against it. I think that may be the only way to sort it out, but I'll lose individual commits that way - not that they're clean anyway, so it probably doesn't matter.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
This is a stock cm10.1 kernel to try on top of that slim I posted... Might help cam

CM10.1_SKYROCKET_WANTOWAN2_KERNEL_Stock_04_03_13.zip - 5.88 MB

---------- Post added at 06:00 PM ---------- Previous post was at 05:55 PM ----------

When we left off deving this with prbassplayer, we were looking at libs being the issue. There is no real cam app any more. It basically fully apart of Gallery2. But pulling and making Gallery2.apk from cm10.1 build doesn't work either.....hmmm
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mefrodo:
after flashing your stock kernel zip, got stuck on boot logo, i went recovery again did all wipes and its still stuck at boott logo got 6 minutes now :confused:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

My guess it was related to either hardware folders missing/tweaking or common device folders. My next step was changing dependencies to CM's hardware folders. If that didn't work I would do that and call CM's common FOLDERS, msm8660-common and don't remember what else.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok wait, I'm get you a slim boot image to flash.

In the mean time try going into recovery and "format cache". Not wipe but format. In mounts and storage

---------- Post added at 08:18 PM ---------- Previous post was at 07:48 PM ----------

Ok, try flashing this. Or you can try flashing the rom over again. In both cases do your wipes.

Slim_4.2.2_SKYROCKET_WANTOWAN2_KERNEL.zip - 7.01 MB

Remember, this is dev-host so check md5 sums
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mefrodo:
this is what i did

1. flash the rom you post before

2. reboot

3. flash Slim_4.2.2_SKYROCKET_WANTOWAN2_KERNEL.zip - 7.01 MB

4. reboot

5. it boots

cam still doesnt work

broswer crashes

install dolphin broswer and doent work

wifi ok

music player ok

mms ok

gallery ok

what else should I try?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
You mean the folder themselves. Just rename them? Or stipulate with local_manifest and resync?

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.1" />
<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" />
</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]

Change it in slim.dependency. When you lunch it should change local manifest and pull it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Re: [GUIDE/ROM] Project Rookie - How to's - Building ROMs, Kernels & Mods [TEAM ROOK]

Yup that probably be it... I don't even remember using that folder in general.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
OK. If I switched and built a kernel, would that fix the rom?

Also, slim puts a local manifest in platform manifest folder... this is the local manifest it made for itself. Does this look right?

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jb4.2" />
<project name="SlimRoms/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb4.2" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-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/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_qcom_audio-caf" path="hardware/qcom/audio-caf" remote="github" revision="cm-10.1" />
</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]

Looks how I left it. slim.dependency is found in skyrocket device folder.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Thanks...damn ubuntu. I did search for it....lol

---------- Post added at 10:17 PM ---------- Previous post was at 10:16 PM ----------

Seems like alot of new google source guys....

"android-cts-4.2_r2"?

---------- Post added at 10:22 PM ---------- Previous post was at 10:17 PM ----------

Hey, before I got your previous post, I changed local manifest to this (added the bottom line:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jb4.2" />
<project name="SlimRoms/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb4.2" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-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/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_qcom_audio-caf" path="hardware/qcom/audio-caf" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_qcom" path="hardware/qcom" remote="github" revision="cm-10.1" />
</manifest>

How come it deleted everything?

Fetching projects: 100% (330/330), done.
Deleting obsolete path /home/wantowan2/sb2/device/samsung/celox-common
Deleting obsolete path /home/wantowan2/sb2/device/samsung/msm8660-common
Deleting obsolete path /home/wantowan2/sb2/device/samsung/qcom-common
Deleting obsolete path /home/wantowan2/sb2/device/samsung/skyrocket
Deleting obsolete path /home/wantowan2/sb2/hardware/qcom/audio-caf
Deleting obsolete path /home/wantowan2/sb2/hardware/qcom/display-caf
Deleting obsolete path /home/wantowan2/sb2/kernel/samsung/msm8660-common
Deleting obsolete path /home/wantowan2/sb2/vendor/samsung
Syncing work tree: 100% (330/330), done.

Is it because I added the parent folder, I can delete the other 2 from the local manifest?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
From what I've read, timeout issues are due to excessive demand on the server.

I was having problems until I stopped using the -j16 or even a -j4 switch (even though 4 is the default - go figure).

For sh!ts and giggles, try my method a few posts up starting at the beginning. if something is already installed, apt-get will skip it.

Also, I think the most important thing I found is to monitor the memory usuage while it builds using some sort of system monitor utility. If CPU and RAM/SWAP max out, it's gonna fail, guaranteed. You'll have to do something about the RAM/SWAP if that happens, like add an extra swap file for more memory. More swap will help reduce the CPU usage a bit, bit obviously won't be as fast as RAM.

Also, regarding swap files, if you add an extra swap file using GParted or some other partitioning utility, using the swapon command doesn't seem to stick across reboots - it didn't on my machine anyways. I went into the fstab file and added a line so it *should* hopefully activate it the next time I reboot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
anyone know if you have to use java 6? I see that 7 is out now and i was wondering if that is a better option?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
In my experience, 7 will cause an error. I had an auto install of 7 on an Ubuntu install, and had to revert to 6 anyway.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
New is not always better... ;) In my experience, new is rarely better! I still use and insist on Windows XP and I'm running a rooted stock Gingerbread as my DD! hehe

Not to mention, it's not "certified" by Google for building Android. (not sure if that's the correct wording, but you get the idea)

Why would you think it's a better option, out of curiosity?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] new ion?:
Hmmm, thanks.

I ran it earlier without the -j16 flag and still no dice. That was the latest run.

It seems ridiculous that every time I try to sync it'll be too taxed. And I've got 6GB RAM and like 4GB swap.... this project has been a nightmare so far.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Roger and I are going over what exactly I have done to f*** this up since last night. He's obviously working today, but doesn't have all day access to a computer to field these dumb questions. If 6 gigs is the standard, then why do I currently have 13.5 in the CM10 file alone? I scanned the file, and it doesn't seem as though I have doubled up on anything.Since there is no simple way(that I know of) to expand the partition I am using, and 43 gigs is where I currently max out, I am going through the process of moving my CM10 file to another area, to free up that space. Should I do the same with the other files? Why am I amassing so much data if it's not neccesary? Do I follow the original andriod/jellybean build tutorial, or sk8rs? I've been doing one than the other, thinking that the android/jellybean tut is the base and sk8rs is additional data relative to our specific device. Do I have it all wrong? And if I download one repo and continue to the next, why can I do it all over again if I don't need to? Isn't it supposed to skip the items not needed? And, what about syncing the phone to extract data? One tut says it's neccesary, but others never touch on that. Is sk8rs tut where you get that data without the need of hooking your phone up? I tried to extract from my phone at one point and was given an error there as well. Debugging was enabled, if that question comes up.....

By the way, I'm going to keep up with this throughout the day, but I have promised my wife I would unplug and spend some time with her, without seething about my complete douchebaggery in the building process of 4.1.1 Soooo, if anyone has great advice for me, please continue to help. I am going to get this right sooner or later!:eek:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
You do not need the android base, that's exactly what CM is. It's AOSP built with some extras. You follow the android tutorial just to setup up the build environment. Use the one I posted.

Then follow sk8er's to sync the CM repo (this will pull the base android branch for CM). Then the xml local_manifest will define the exact extras that are needed for the specific device. Sk8er provides the file needed for Skyrocket. For other devices I recommend searching your forums to see what repos need to be included for your device.

Then you sync again, after you have the local_manifest. This will sync the device specifics.

Repeat, you do not need to get the full android source from Google, it useless to us right now. We are not building from source. Basically, CM has already done all that dirty work for us. This is why all the AOSP roms build from a CM base.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
Basically becuase I had read that the newer version was more "compliant". Like you said newer is not always better. Honestly I prefer windows 7, Love it! XP was better than vista tho.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
THANK YOU!! I have been wasting hours trying to cover all the bases and now I know. I'll definitely try it your way:good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
I found that after I attempted to do a build, the total size of the files was huge and in that 13.5 range... Do a "make clobber" and then see what the size of the folder is.

Yes, you can use the CM10 folder after it is moved to another drive, as long as it's a Linux file system I would assume... I had moved mine (IE: I'm not using my $HOME directory for my development. I had moved my CM10 folder to a different drive before I had reinstalled Linux so I didn't lose the files, and then continued to use the CM10 direntory in the new location. It is my belief that the only files you need are the Android SDK (accessible in your PATH variable), the CM10 repository files, and your device specific files (see comment below) - I agree that you do not need to sync the AOSP tree as dakpluto says a few posts back.

I'd say follow the steps in my post, but then again, I'm biased since the procedure worked for me... In reality, anyone who has had a successful build and says to follow their steps should be fine. If Rodger is helping you, I'd say you're in good hands, but if you want to take a step back and start fresh, wipe your Linux system, install Mint Linux 64bit and start fresh.

I got fed up dealing with a messed up system after trying so many tutorials that I decided to scrap my Ubuntu attempt, start fresh and download Mint (~830MB, not a couple of gigs like Ubuntu).

By the time I had downloaded Mint, burned it, installed it and got the base dev environment ready for a build, I think only about 2.5 hrs had passed. In my mind that was a small investment of time compared to hours of frustration with a buggered Linux install.

If you do it successfully once, then each time you do a sync afterwards, it does just that - it syncs any changes as opposed to downloading the whole mess again.

I didn't have any success with this step either, and after looking at the script, found the files it was looking for in the device and vendor trees. Since I was able to do a build successfully without this step, I am going to say that it is not required...

HOWEVER, you must have a complete set of files in your device and vendor folders for your device. For me it was:

CM10/vendor/samsung/hercules (or skyrocket)

- and -

CM10/device/samsung/hercules (or skyrocket)

Once I had those folders populated, I was off to the races.

All I can say to that is a little patience and a break every now and then paid off for me. ;)

---------- Post added at 12:04 PM ---------- Previous post was at 11:49 AM ----------

I tend to agree.... I think what is actually happening is that the network connection is tripping on itself or something to that effect and it stalls. Reducing the number of jobs from 16 ( -j16 ) to the default (apparently -j4 ) seems to be inline with this theory.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aSquard:
I'm going to delete my cm10 and WORKING folders tonight and start from scratch using your method dakpluto - hopefully I can get something completed finally :good:

Maybe I'll try Mint tonight instead. I do like Ubuntu, but something lighter that works faster (like Kubuntu on my PC) would be ideal - obviously I like options... going for Mint tonight.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
Since I keep preaching about Mint, here's the download page:

http://www.linuxmint.com/download.php

I'm using the MATE 64-bit version (linuxmint-13-mate-dvd-64bit.iso). In my experience, using the 64 bit version is key, by the way...