yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
Well, after the first error, I just deleted the Mms folder then make clobber then make clean with the same pac_evita.mk configuration. Afterwards, I reinit my environment and built it. Sorry, I actually finished awhile back. I was setting up my thread.

[ROM][Pa+Aokp+Cm][ALPHA] P.A.Cman True All in 1 ROM[11-10-12]
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Well, it's been a long time since I've fallen a sleep with my face on the keyboard .... Anyway, Nibbles 1.1 is pretty much done now just didn't finish testing last night.

If anyone wants to use Aroma for their ROM installer, I'll post a general tutorial to this thread later today (after I post my rom update). I'd be happy to answer questions in the meantime, it's actually pretty easy once you get the hang of how it works.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I would love to make that addition to my new ROM! :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Absolutely! Just working through what I believe is the last bug in the custom installer side, as soon as that's working I think I'm good to go.

---------- Post added at 01:27 PM ---------- Previous post was at 12:47 PM ----------

Uploading Nibbles 1.1 now .... will post the link here as soon as it's done if anyone wants to fiddle with it. I'm going to do a bit more testing before I update my thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Just an FYI, make clobber and make clean do the same thing. I don't know why they did it this way, but the clobber command just points to the clean command.

https://github.com/CyanogenMod/android_build/blob/jellybean/core/main.mk#L814

.PHONY: clean
clean:
@rm -rf $(OUT_DIR)/*
@echo -e ${CL_GRN}"Entire build directory removed."${CL_RST}

.PHONY: clobber
clobber: clean
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Here you go guys. Anyone want to download and beat the crap out of this for me?

http://d-h.st/OOt
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'm all over it:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Forgot to mention, just download and run the zip. It will take care of wiping data, caches, etc based on your choices.

The first boot will take several minutes, just be patient.

Lastly, as soon as you are greeted with the setup wizard, pull down the notification bar and turn your wifi. For some reason it doesn't always kick on right after it boots (for the initial setup). It works fine from there on. This tends to be a hit or miss, sometimes the setup wizard after boot asks you to sign into wi-fi ... sometimes it doesn't. I have no idea why.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Just an FYI, I've added support to Hercules on the PAC repo, in case anyone wants to build for it as well, also I'm in the process of pushing the fix for the build error.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
AROMA Installer - Rough Guide

Want to use Aroma Installer on your ROM? Here's a very brief tutorial to get you started. Feel free to ask questions if you get stuck, as this is not a 100% step by step tutorial. This covers the basics.

First, you need to download the Aroma Demo package from here:

http://xdaforums.com/showthread.php?t=1461712

Second, read through the first couple posts in that thread and search there for answers before asking questions here. I found that most of the problems I ran into were covered already in that thread. Otherwise, PM me or post here with questions specific for TEAM ROOK.

Setup:

Once you have the zip, there's a couple key pieces included in it, they are all located in /META-INF/com/google/android.

aroma-config: This file facilitates the user experience in Aroma. This is where you will setup your options for installation and variables.

updater-script: The example script in the download shows you how to access the options chosen by the user in Aroma.

update-binary: This is important. It is a new version of the standard update-binary that ensures that Aroma starts when the zip is flashed. This file runs the Aroma installer menu system.

update-binary-installer: Do not use this one. What you will need to do is take your update-binary and rename it to update-binary-installer and drop into the B]/META-INF/com/google/android[/B] directory. This runs the actual updater-script underneath Aroma.

aroma: This is actually a directory. Just copy it into your zip, you likely won't need to make any changes to this at all.

Go reread what I said about update-binary and update-binary-installer ... two more times.

Now you have the basics of what's what. If you want to run the demo as-is to get a feel for it, just update the update-binary-installer file as noted above and flash it from recovery.

I'm not going to get into the details of how to actually modify and use the scripts, there's enough detail in the demo to get you moving. I will however, share my modified script files from Nibbles 1.1. That'll show you how I got it working. What that also shows you is that within my flashable zip (feel free to crack it open and poke around), I placed optional files in a specific resources directory for the most part. There are also other directories that contain different applications that can be installed.

The important part is that you remove any apk and other files from your /system directory in the zip if you want them to be optional. You'll notice that I kept a LOT of the standard updater-script commands from a stock build. They are just moved around a bit to accomodate for the optional installations.

So that's really the quick and dirty explanation. I'm going to get back to watching football and drinking beer!

Cheers!

CvD
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
So I've modified and prebuilt (for testing) 4-5 LiveWallpapers. I used the AOKP framework to build them. They work!

I wanted to add them to my build. Now I have 2 options.

1. leave my modded files in place and hope that the build will just make them and add to build. Would they fail?

2. Go ahead and add these new .apk's to

'aokp/vendor/aokp/prebuilt/common/app'

.

Where are the potential conflicts here. ie: I modded phasebeam. And I don't want to end up with 2 versions installed. Will the build see my prebuilt and not go ahead with building it? Should I modify or delete the phasebeam in?

aokp/packages/wallpapers

I did add the packages to

aokp/vendor/configs/common.mk

like this.

'vendor/aokp/prebuilt/coomon/app/phasebeamW.apk:system/app/phasebeam.apk

On a side note. I have seed to have lost touch sensitivity on all my builds. Aokp and CM10. The button is there and you can click it but it's greyed out?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Hey guys I was wondering if someone could help me? I have successfully been able to compile cm10 for my phone I'm currently trying to incorporate lightning zap kernel into my build I've changed my local manifest for the team fahq git I've modified my default manifest I have all the scripts and Lz make file but I'm obviously missing something because I'm still getting a regular kernel after build. Any ideas would be appreciated. Thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
So you removed the orignal kernel entry from your local_manifest.xml correct?

Then you ran a make clean.

Then you ran a repo sync.

Then build?

Need a little help here, what steps did you take to get where you are?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
yes to all the above, also went into the .repo file /projects and removed the kernel giti placed the call cmd # adding Lightning Zap tweaks to build

$(call inherit-product, vendor/lz-msm8660-common/lightningzap.mk)

in this device/samsung/msm8660-common/msm8660.mk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Maybe I'm just getting old, but I don't remember needing to do all that. I just did a 'make clean', or 'clobber', it makes no difference. Then, I changed the local manifest to have the path for the kernel I was wanting to build with. For example, the CM10 manifest looks something like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_hercules" path="device/samsung/hercules" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
</manifest>

I would change this:

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

to the appropriate line from the lightning zap git found here : https://github.com/TeamFahQ/msm8660-common_lz_kernel

I would post it here for you but the ****ty desktop at work is having a case of death pages on github. Then, build as usual.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
BPM7777 is correct, I didn't need to do anyting beyond changing the manifest to include KKO.12 in my build. I saw that lightning zap had some other scripts that you needed to include, so maybe that's the issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] latinohot:
Delete
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Thanks guys I'll give it a try here in a minute
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Emil9727:
I'll run these after I re-install mint. I Had switched because I thought mint was going to be a problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pixelcreativ:
If u wanna learn command line. Never ever ever ever ever ever use that retarded GUI package management system .

Sent from my Skyrocket running SKY ICS
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] zomgjosho:
And learn vim. Gedit and the like blow.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pixelcreativ:
Also how's that nexus 7 run I heard it had sensitivity issues. I bet that can be fixed with roms though. Are there roms for it yet?

Sent from my Skyrocket running SKY ICS
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pixelcreativ:
Nano is best terminal editor I think. Vim works but nano for me is win.

Sent from my Skyrocket running SKY ICS
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pixelcreativ:
Changing default apps and settings can all be done through command line. Everything can be done through command line and much faster by the way its just a matter of accumulating knowledge.

Sent from my Skyrocket running SKY ICS
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I totally hear you. I am humbled and amazed at how little I really know. I am getting a lot of practice now lemme tell ya:silly:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Emil9727:
I will work on doing that :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Emil9727:
There are a ton of custom Roms but I haven't installed any yet. I only find sensitivity issues in certain games. I don't know if its the ROM or the games. Although they usually are not an issue. Aside from that its a really awesome tablet, especially for the money. I thought 7 in might be too small but its actually perfect for portability and gaming is a dream.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Pixelcreativ:
Dope I'm gonna get one and hack its balls off.

Sent from my Skyrocket running SKY ICS
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Got this again, oh joy

fatal: cannot create directory at 'libc/kernel/common/linux/lockd': No space lef

t on device

Traceback (most recent call last):

File "/home/bmp7777/.repo/repo/main.py", line 385, in <module>

_Main(sys.argv[1:])

File "/home/bmp7777/.repo/repo/main.py", line 365, in _Main

result = repo._Run(argv) or 0

File "/home/bmp7777/.repo/repo/main.py", line 137, in _Run

result = cmd.Execute(copts, cargs)

File "/home/bmp7777/.repo/repo/subcmds/sync.py", line 467, in Execute

project.Sync_LocalHalf(syncbuf)

File "/home/bmp7777/.repo/repo/project.py", line 1026, in Sync_LocalHalf

self._InitWorkTree()

File "/home/bmp7777/.repo/repo/project.py", line 1840, in _InitWorkTree

raise GitError("cannot initialize work tree")

error.GitError: cannot initialize work tree

What gives? Why is every aspect of this project like pulling friggin teeth for me?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Emil9727:
Yeah the tablet is one of the factors why I wanted to start delving into programming. Phone I need to be more stable/dependable. Tablet I can afford for more bugs :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Looks like partition too small. First line says you ran out of space. What size is your partition?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
43 gigs. I gave gathered over 40 gigs of data without ever building anything. Apparently I am downloading everything in the universe every time I sync repo. I don't mind the space but now I'm trying to add more space and I'm denied permission. Trying to research how to get permissions to my own system for gparted. Didn't know the boot partition is where all of this goes or why it has to be that way. Can't the files be accessed from another partition? Why would you have such a huge amount of data designed to be used and altered on the same part as the grub? It sounds like a recipe for disaster
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rmarquez1974:
You have to type in a terminal this : sudo gparted

Then provide your password.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
How many partitions did you setup? Seriously, your life will be 5000x easier if you only have 2 partitions. One EXT 4 mounted as / and a 2nd one that is swap. That's it. Then you don't have to worry where anything goes because it's all going to the / partition.

Oh, realized why my last build only took about 20 minutes, I completely forgot to clean out the last build, oops. Kinda surprised the changes I made even happened. Also why the date was off and kernel didn't show show changes.

I'm rebuilding now and it's obviously taking much longer! lol Gonna be about 90-120 minutes I believe.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
View attachment 1229965

BMP7777 it seem like you get every error possible when building, :D I'm taking this personal I want to get you up and running let's start by gathering a little system info.

Download the attached file and do the following in a terminal:

1. Rename the file "mv get_system_info.txt get_system_info.sh" xda won't allow me to upload a file with a .sh extention go figure.

2. Make it executable "chmod +x get_system_info.sh"

3. Run the file "./get_system_info.sh 2>&1 | tee BMP7777.log" this will gather some system info display it in your terminal and also save it to a file called BMP7777.log attach the log file to your reply.

Let's see if we can get to the bottom of your problems.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Still cant add any space to the partition that I need to. I could see shrinking throwing up alarms but expanding from another space? Ugh
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Not sure if you guys are aware see USHERROB's post!!!

Official CM10 by The Ferg! (aka topprospect)

http://xdaforums.com/showpost.php?p=29508873&postcount=1214

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Log your build to a file an post it here when you are done. That will help us see what's going on.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
2 quick ques: How do you Log your build...

Add time stamp to cmd output?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Easy .... add > build.log to the end of your build command, like ...

$> brunch cm_skyrocket-userdebug > build.log

This might work for a time stamp. Typing this from memory on my phone so .... YMMV ...

$> brunch cm_skyrocket-userdebug | gawk '{ print strftime("[%Y-%m-%d %H:%M:%S]",systime()), $0 }' > build.log
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
OK will do. I'm building for the i577 . I know you guys build the skyrocket but I reference this thread quite often. The whole rookie thing. Has a lot of relevant info

Edit: So after days of pulling my hair out I finally got it to run..:D. I had the device file named wrong. I know such a simple thing to cause so much frustration.. lol. Thanks guys for the help and having a thread like this.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Anyone here able to provide a quick walk through on how to push commits to gerrit? I've been able to ssh to github to make changes on my source, but just can't seem to be able to do it through gerrit,.. any input would be much appreciated.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I would change this to only level 2 to cut down on the noise.(i.e. brunch cm_skyrocket-userdebug 2> warn.log)

Sure. I'll write something up when I get home and get back to my computer.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Submitting to Gerrit

Okay, so I'll assume that if one wants to submit to gerrit they have git and ssh set up already, following a guide like the one on github here:

https://help.github.com/articles/set-up-git

Additionally, you can find documentation on any of the gerrit sites for the various ROMs (AOSP, CM, AOKP, PA, etc.) relating to gerrit at the top of the page under Documentation. For example, on CM's gerrit, at the very top click on "Documentation", and then click on "Uploading" (here).

Anywho, first I registered on the gerrit site by clicking on the "Register" link in the top right corner and signed in using my google account (1, for simplicity, and 2, because that is the email used when setting up git).

After registering and signing in I set up my profile to make sure the user name and email were the same as they are for git. Then I added my public ssh key. It will likely be in your /home/[your_name]/.ssh folder. There will be a file named id_rsa.pub. Open this file and copy the contents of this file. Then on the gerrit site, go to Settings, and click on "SSH Public Keys" on the left panel. Click on Add Key, and paste the key you copied from id_rsa.pub.

That's pretty much all you have to do. To test the connection, type this:

ssh -p 29418 sshusername@hostname

where sshusername is your user name that you used when setting up git/ssh and the name you put as your user name on your gerrit profile. The hostname is the gerrit server you are connecting to. So for CM's gerrit, it would look like this:

ssh -p 29418 m4570d0n@review.cyanogenmod.com

Okay you're set up and now you want to change some **** and submit it. When you make changes to a project, first you need to commit the changes. Let's say you were working on Mms. Then, from the root of the build tree:

cd packages/apps/Mms
git commit -a

For the commit message, The very first line will be the title of the commit. Then skip a line and the next line will be the start of the description. If this is the first change you are commiting, a Change Id will be generated automagically so you don't need to worry about that. Keep the description to about 80 characters per line, otherwise it will be one ginormous line. I made that mistake with my 2nd submission, which you can see here as an example of how not to do it :):

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

After saving the commit message you can now use git push to submit it to gerrit (enter commands while still in your Mms directory):

git push ssh://m4570d0n@review.cyanogenmod.com:29418/Cyanogenmod/android_packages_apps_Mms HEAD:refs/for/jellybean

If you wanted to submit something to another gerrit, like AOKP for example, it's the same exact process and commands, just change the hostname and, if necessary, the branch or project name:

git push ssh://m4570d0n@gerrit.sudoservers.com:29418/AOKP/packages_apps_Mms HEAD:refs/for/jb

It's also possible to use repo to submit stuff to gerrit but I have not messed with it yet. Here's some info on it though:

http://gerrit.googlecode.com/svn/documentation/2.0.34/user-upload.html#repo_upload
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Excellent quick guide, that should do the trick for me, I guess what i was looking for is how to check the connection since Its different from github, thanks a lot.! I owe you one!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
oooo!! Android 4.2 was pushed to AOSP today. That means we should see it merged into CM10/AOKP within the next few days.:victory:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
This is why i needed to learn to gerrit, support for all devices was dropped on PA repo, and they have to be added again.http://review.paranoid-rom.com/#/c/288/

AOSP preliminar configuration
Remove all the devices except nexus. We hope them to be added again,
as this is a really big change. Also use buildtools and device trees pointing
to our repos
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yep, cannot wait to start playing with this ... will be CM10.1 when it hits.

http://www.cyanogenmod.org/blog/cyanogenmod-10-0-release
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Oh yeah!!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Hey BMP7777 ... any thoughts to a Google+, Facebook or IRC for TEAM ROOK?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
There is a Facebook page but I boycott that crappy site. I have a g+ and we can all team up. I'm down for Irc too

EDIT : I want to clarify, I boycott the SITE, not the guys that have a Facebook page. Decepticoans is a cool guy and a member of this team. Hopefully, I didn't give anyone the wrong impression :angel:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Cool, lets get something moving with IRC and G+ then. I'll shoot you a PM tonight and we can get it all sorted out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'm down.... trying to get out of work at 4 today (QUALITY IS A FULL TIME JOB I TELL YOU:eek:), so I'll be working on the project you and I've been going back and forth about. Point is, I'll be available. Be cool

In my office right now; PM me a G+ name and I'll sync you up. Then, we can plan our TAKEOVER OF THE PLANET HAHAHAHA did I say that out loud?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
If I can help let me know, I've been wanting to take over this planet for a while now! I'm all in for G+ and or irc to.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Come on in, the global domination is fine!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Just registered #TeamROOK on freenode.net.

Feel free to join, I'll likely be logged in from my phone and probably unresposive until tonight. When I get time tonight, I'll configure the channel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
gs2user,

My directions for submitting to gerrit need to be updated to use the ".org" domain rather than ".com" for the host name.

Also, wow. I just came across the reason for CM changing everything to .org.

http://www.cyanogenmod.org/blog/psa-transition-to-cyanogenmod-org
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yeah, pretty effed up huh?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
That's friggin HARDCORE
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] whassupmyninja:
Does that mean cm development is going to be halted like have to start all from scratch?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] liquidzoo:
No. It was all about the domain, and the situation has now (thankfully) been resolved.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Running a repo sync this morning for CM10 ... anyone getting this error or know how to handle it?

Syncing work tree: 100% (321/321), done.

error: device/samsung/skyrocket/: CyanogenMod/android_device_samsung_skyrocket checkout f2705264fad156b89fe393fad516c28efcf08b1b