yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Good idea. I took the long way around and started from scratch. One question though, would this technique work even though I was attempting to expand from space off of the Windows partition? I run 7 as a primary, and Luninux 12 as a secondary. I was able to shrink my 7 partition to provide the space, but was unable to expand my EXT4 partition with it even though the space was unallocated. Just dumped everything, partitioned with a lot more space, reinstalled and went from there.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] new ion?:
Now, I'm not going to bash our group at all,

but I found this the other day, and i think cyanogen has some very valuable advice.

here

as well as helpful links.

we are all here to learn, and we are learning as a group. I think we should start taking advantage of the git that someone grabbed. (i can't remember who as i'm not on FB ATM)

if we don't wanna use that one, I'm more than happy to start another.

and what i mean by that, is someone should figure out how to download from the cm9 repository, then we can push that to our git, so we all have common code to play with and such - maybe start a group project. something small. :)

if only i could sync... and had the time to actually code. in between classes now so i have time to fart around, but it's going to be full steam ahead studying in the evenings....

the 16th im free. :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Good advice; and thanks for bringing it here. I pasted it up front for everybody to see. As far as a Git, it was me who said I had one. I created it last week and it's ready to go. My repository is waiting to be used, and you can find it here: https://github.com/BMP7777/project-rookie-4.1.1

I have been trying to get up and running and forgot that others are further along than me:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] new ion?:
Lol, I'm one of the ones behind, but the people who are farther could in theory push to the got, which could possibly help out the people who can't sync 'cough' me 'cough' lol

Granted, I haven't been able to devote as much time as others

I totally get where cyanogen is coming from, however. I think we're learning more or less the right way...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
What kind of help do you need with syncing? I have been around this particular block quite a few times....No joke, if you are experiencing problems, you may just want to begin from scratch. Follow the first 5 steps of the android tut, then go to sk8rs thread and follow those steps. You should be able to sync from there. One of the many issues myself and others are having is the WORKING DIRECTORY and steps after....those apparently aren't required for a CM10 build and may be behind our problems. Let me know..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] new ion?:
Unfortunately, as I have a hercules, I can't follow sk8rs thread as that has skyro specific downloads and such. I was following the cm9 one. I also found the team chopsticks guide. But I haven't really tried lately...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I thought it was only a matter of altering the commands to be specific to your device instead of mine. Do I have that wrong?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I compiled slim today and it's about as good as it gets I think. STILL BUGGY Tested w PR about 10+ combinations, 4 diff kernels, *_caf's, device*,,,+++ lol It's got Moretz and some apps. Link is at the bottom of my sig.

My local
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I don't totally know what I am looking at but...

This doesn't look complete to me? dunno

"CyanogenMod / android_hardware_qcom_display-caf"

https://github.com/CyanogenMod/android_hardware_qcom_display-caf/blob/cm-10.1/common.mk

Mentions:

($(TARGET_BOARD_PLATFORM), msm8974)

display: Use actual kernel headers for all builds

common_deps :=

kernel_includes :=

&

https://github.com/CyanogenMod/android_hardware_qcom_display-caf/blob/cm-10.1/Android.mk

Mentions: Only build CAF display variant when requested.

($(filter msm8960,$(TARGET_BOARD_PLATFORM)),)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Well the way I understand it (because CM tried usin caf with mako and ended up reverting it) was for caf to be used it needs to be called, HOWEVER for mako didn't use full caf when enabled. Just speculating
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I don't know, clearly, but doesn't that code look messy and incomplete? What does this mean?

And there is no mention to call. ($(TARGET_BOARD_PLATFORM), msm8660

Problem is, maybe, that the kernel headers aren't set up for this use? display: Use actual kernel headers for all builds
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Odd that it's hard coded like that. I'll swap it out with our board tomorrow and run a build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I don't think msm8660 ever had a specific called just " common_flags += -DQCOM_BSP"

The reason specific calls are made (msm8960 or msm8974) is because they can't use caf repos in its whole. Again this is what I understand @ 1:30 am and half asleep looking at the files posted. So unless msm8660 now requires a specific set of insstructions? I'm I off basis?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
ok guys here is my build error i want know if anyone has seen it or knows how to fix it this is for paranoidandroid and it's a bit of a bear.

target thumb C++: libnbaio <= frameworks/av/media/libnbaio/AudioStreamOutSink.cpp

In file included from frameworks/av/include/media/nbaio/AudioStreamOutSink.h:20:0,

from frameworks/av/media/libnbaio/AudioStreamOutSink.cpp:21:

hardware/libhardware/include/hardware/audio.h: In function 'size_t audio_stream_frame_size(const audio_stream*)':

hardware/libhardware/include/hardware/audio.h:419:23: error: 'AUDIO_CHANNEL_IN_5POINT1' was not declared in this scope

hardware/libhardware/include/hardware/audio.h:435:10: error: 'AUDIO_FORMAT_EVRC' was not declared in this scope

hardware/libhardware/include/hardware/audio.h:438:10: error: 'AUDIO_FORMAT_QCELP' was not declared in this scope

make: *** [/home/nick/Android/pa/out/target/product/skyrocket/obj/SHARED_LIBRARIES/libnbaio_intermediates/AudioStreamOutSink.o] Error 1

make: *** Waiting for unfinished jobs....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You are missing declarations somewhere, I would guess that you have a bad header file.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Now if only I knew what that meant lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Headers end with .h as noted in your error.

Their purpose is to allow for shared definitions and re-use in your code base. You can read more about them here: http://en.wikipedia.org/wiki/Header_file

Basically, your header file is included in :: frameworks/av/media/libnbaio/AudioStreamOutSink.cpp

When the compiler runs, one of the first things it verifies is that all of your declarations are in proper order. In this case, it bombs because in your hardware/libhardware/include/hardware/audio.h file there are declarations that get put into use that have not been defined somewhere else.

So, it could be a few things ...

1. The header file in question has some missing code.

2. A header that may be included from within that header is missing code - or not included at all.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Thank you CVD and now the hunt begins
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
No problem. Not sure how applicable it is to PA (I've never touched it), but quite a few things moved around on the 4/24 code base. Specifically some headers that weren't previously shared between the kernel and the OS are now shared. You might be running into that if your repositories are out of sync from those changes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Any idea on the status with that? Has cyanogen gotten to patching those *_caf files? Is build busted still? I guess a kernel header revert is the only way?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
What do you mean busted? CM10.1 compiles just fine, there are bugs yes, but it is being worked on.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I sent you a message about builds with new cm stuff :p. Little feedback I've gotten seems positive
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
?? Sorry I missed it? New build box is up and running great! woot! Built it yesturday and dual booted. Even got slim synced and compiling but it busted.... ....soooo, based on what cvd said, this is a slim/cm issue? All I do know is, last I chacked, it was this kernel header integration, pre 24th crap....

P.S. In ubuntu 13.04 (new install, not update) when I enter terminal I see this:

Any idea what this "-System-Product-Name" is?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Looks like your build environment isn't right. Then again I have no clue what I got on git right now, I'll see if I can get it synced up but build server is busy right now. Also weekend won't be doing much compiling at all :p
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
.....were you referring to build errors or this "-System-Product-Name"?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Errors. Because Slim source as is should compile. But be unstable piece of crap but should compile.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] liquidzoo:
Pretty sure the System-Product-Name is the host name assigned by the Ubuntu install.

I used to know where to go to fix that (on Gentoo and Mandrake/Mandriva)...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Yup, thanks. I changed hosts and host name reboot. Fixed it.

---------- Post added at 10:55 PM ---------- Previous post was at 10:46 PM ----------

This is the error I was getting last night
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
disregard
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Sudo apt-get install lzo
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Hey guys. So I have been trying to build PA here. I have a sucessful build but it still wont boot.

On boot I get a black screen with ANDROID_ in white lettering.

I run a log on boot and all it reads is..

What does this mean and where do i start looking? I checked the zip and that file is not there. Do I need to find that file and add it to the zip or.... ??

Toyes
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
I had a ROM do the same thing find that sh file from another ROM and place it in your zip and it should boot up
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Thats what i was thinking to try but looked in both my aokp build and cm10.1 and niether zip has it either ??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
I got the same thing the first time I built, and I rezipped it with CMs kernel & modules and it booted. Clean install with no gapps. Give that a shot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Gotta have sh...lol here yo go. (not flashable)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
sudo apt-get install lzo

[sudo] password for wantowan2:

Reading package lists... Done

Building dependency tree

Reading state information... Done

E: Unable to locate package lzo
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
try lzop instead of lzo. that should work
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Hey guys. I've been out of the loop for a little while, but I've been getting back to building again lately. It looks like I've missed out on quite a few significant changes while I've been away. Can someone fill me in on the current status with the cm-10.1 kernel? For the last few days all of my builds are giving me SODs like we had when we first got Android 4.2 working on our phones. I'm still using PAC-man as my base with the standard cm-10.1 kernel.

---------- Post added at 03:05 PM ---------- Previous post was at 02:46 PM ----------

I don't know why that wouldn't be getting compiled. It's a pretty fundamental system binary that is almost guaranteed to be included in any Unix-based OS. I do know though that it should be located in both /system/bin/ and /system/xbin/. /system/bin is for executables used by the system such as reboot, mkdir, mount, chmod, etc. and most terminal commands you're probably familiar with. /system/xbin is for root-related executables such as busybox. Also, browsing through my phone briefly just now I noticed that /system/bin/sh is just a symbolic link to /system/bin/mksh, and /system/xbin/sh is a just a symbolic link to /system/xbin/busybox.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Well hello there stranger, welcome back.

CM10.1 long story short ... 4/24 introduced an entirely new code base for the kernel along with other sweeping changes across the msm8x60 platform. There are two outstanding issues being worked right now as a result (many have been fixed already). Primarily, there are Random Reboots (RR's) and the screen not waking up from sleep - cap lights come on, but screen is black and responds to touch input; hitting power twice more turns the screen on.

Both issues are intermittent.

More detail in the later couple of pages in this thread ... check the last post by topprospect for links to the JIRA issues I noted above:

http://xdaforums.com/showthread.php?t=2138102
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Thanks.:)

We might be talking about the same thing but what I've been seeing is that I'll be using my phone and it locks up. The screen turns off, the phone vibrates and I see the Samsung boot logo. However, the screen goes black from there.and there is no response from the screen or any hardware keys. One would think that the phone just turned off, except that I have to hold down the power button for 10sec (or however long it is), and then the phone turns off. Then I can hold the power button down again for a second or two to turn it back on. Additionally I can confirm that it wasn't off until I held down the power button because I had it plugged in on several of the instances in which this has occurred, and it wasn't until the hard reboot that the phone turned off and you could see the battery charging animation on the screen.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
m4570d0n what you just described above is QSDB-30

https://jira.cyanogenmod.org/browse/QSDB-30

Welcome back!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Thanks.

Yeah I saw that little bit after my post. I made a new build this afternoon with this cherry-pick (msm8660: disable inlining of spinlocks) but I've still had QSDB-30 and QSDB-31 at least once already. Fr some reason my kmsg was really short and didn't seem to have the relevant info, but I'll grab it if/when it happens again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
@ m4570d0n

Welcome back!

I thought it was something I said.....yikes!

---------- Post added at 08:12 PM ---------- Previous post was at 08:11 PM ----------

I don't recall needing this. Should we get it added to the OP?

---------- Post added at 08:22 PM ---------- Previous post was at 08:12 PM ----------

Also, what about adding a poll to the thread. AKA: petition.

Seems Cyanogen has eliminated USB Mass storage from storage options. To me, Android, is not a media device. nor should it's capabilities be slashed by the lesser protocol 'Media Device'.

What do you guys think? Will this be a loss for you guys?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kaymmm:
I had to install lzop too at some point in the last week or two, so I agree it should be added to the op in the big apt-get command. fwiw I'm on Ubuntu 13.04.

Now that I think about it, perhaps op could also be updated to say that both 12.10 and 13.04 will work for building. there's a good how-to somewhere on xda for setting up a fresh 13.04 install, but too lazy to find/link it from my phone. but iirc, its pretty much the same as setting up 12.04...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Except for a big kernel update I think... 3.5 vs 3.8.8

There is this one but it uses the crappy java....http://xdaforums.com/showthread.php?t=2224142

This is the good java.... and it will purge the ice tea too...http://xdaforums.com/showthread.php?t=2043285
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I haven't seen lzo as a building requirement anywhere whether it's xda, rootzwiki, the AOSP site, or anywhere else. That said, I already had it installed on my Mint 14 partition. You should be able to get by using zlib, unless something changed that I haven't come across.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
If toy change kernel compression, as I have in marla/moretz to LZO you will need to install it. The stock kernel uses gzip by default.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I sent a note to BMP7777 about updating the OP, in the meantime ... for CM10.1 please use the following instructions to setup your roomservice.xml (local_manifest).

After your run the repo init command, do the following to setup roomservice.xml - you no longer use local_manifest.xml

create a new directory in ~/cm10/.repo called local_manifests

Got into that directory and create a new file called: roomservice,xml

Paste in this code:

<?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_hercules" path="device/samsung/hercules" 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_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.1" />
</manifest>
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
Does this still require me to move the kernel manifest over? Also can you help me out im trying to build for AOKP? Will this work for that also?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
That manifest includes the stock kernel for the msm8660 chipset. Along with the repo init and full sync from the op, it will give you everything you need for a stock cm10.1 build.

I've never built AOKP, so I'm not sire what repos to reference for it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
Okay thanks. I tried your method and I'm still getting a error: Exited Sync due to fetch error.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
roomservice.xml

Toyes
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You need to be more specific, what is the error message that you are getting? Just scroll up in your terminal window until you see it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
That's just it it would be in the middle of fetching and stop and that its all that pops up I'll try and get a picture. And look a little harder.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
OP updated

Updated the OP to reflect the new roomservice.xml code. I have sent a message to prbassplayer about changing the OP ownership from myself to CvD, but have not heard back. Let me know by PM what other changes need to be made to the OP and I will take care of them until the change over takes place. Almost wish I still had my skyrocket; other devs are not as friendly and/or helpful. ALMOST :p Be cool everybody :cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
You can try: repo sync -f

Which -f stands for force sync even if there's errors.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Capt. Martin#30:
I've also did that.. I'll check errors when I get home. But also durning that process of using -f it stops randomly and doesn't move on.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
[MENTION=382473]cvd[/MENTION]

Between you/PR Things seem to be really coming together! Thank you guys. My most recent build is Slim 5.5/moretz 3.0.5.

I am getting some crashes here and there but other then that, seems smooooth.

Are you looking for kmesg/paste bin? I think I'm seeing some MPD out of range... repetitive booting second processor calls...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Thanks man, I can't take too much credit for it ... i'm a hack. All the stability stuff has been from Cyanogen and TeamChopsticks - I'm just picking/upstream merging all those into my latest builds.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
This also applies to me lol. I'm just using their upstream.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Well you guys can minimize all you want but from what I hear around xda and from BMP, we here at Skyrocket have a good/unique thing going here. I just think of what I would have to revert too without Slim or A custom kernel to work with..... not good thoughts...lol

EDIT: Hey! I just noticed. CVD is a "Recognized Contributor"! Congrats man!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Thanks dude ... got "promoted" a few weeks ago ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yes, this is a great thing that continues here. I am in the process of creating a Project Rookie II in the Sprint LGOG forum, and have made some new friends that are going to help get it off the ground. I am very pleased that all of you still find use and relavance for this thread; it is exactly the way I had hoped it would be. You guys rock! Keep it up! Anybody wanna help me figure out a damn local_manifest for building the LGOG? Ugh, its like pulling teeth..... nothing good ever comes easy, am I right? If anybody has any updates for the OP, PM me and I'll take care of it. I'm sure they will eventually turn this over to CvD, but for now I have no problem with making any and all changes that you all need. Be cool :cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
I think this is the most unique thread on xda one should be started on xda university I build for two different phones neither of which is a sky rocket but most of the issues I encounter while building or modding can be found in this thread
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
'

Looks like the thread has now been transferred over to me.

Just want to thank BMP7777 for getting this started and everyone who has contributed so far. Without this thread, there are a number of roms and projects that would have never been built - including pretty much everything I've distributed along with that.

I look forward to getting some updates into the OP and reformatting a bit. Beyond that, I don't really plan to change anything. Everything this thread is about works, and it's going to stay that way.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Congrats man! Brian started one of the best threads I've ever seen on XDA for learning. Nobody comes in here griping or whining. Just a bunch of great guys! Hope to see this thread continue strong and when you guys get new devices I hope it branches off in a positive manner.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
OP updated with some formatting and minor changes to the CM10.1 instructions.

I should have time next week to run through each of the tutorials to verify them for accuracy. If someone has already done that and can confirm they're good, or bad (and how to fix them), please let me know.