yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Connection was my sync issue. Built slim successfully overnight. Syncing PAC and CM from scratch this morning and will see where its at. Updates at git for CM most likely the culprit for most building hassles. As far as 4.2, it isn't available for I727 yet. For your device, I'm not sure. When I get home I'll see what's up. Post your issues and I'll help if I can.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rachanta:
I have been through this error while doing make otapackage for my i9100 .

I added:

TARGET_CPU_ABI := armeabi-v7a in BoardConfig.mk in device/samsung/i9100.

I found that I have to set the value armeabi-v7a by googling. Anyway you may have already passed this hurdle by now. All the best!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
When you say connection did you mean your internet or a bad connection with the cm server?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Unsure what is happening with this thread, I am finding that information is suddenly not where it was in the OP, even though I haven't tried to change anything since adding a few details for the guava fix in the Slim build section. As of last night, none of the local manifests are in their locations for CM or AOKP. Hmmmm.....:confused: Try to get it back together as soon as I can:eek:

Anybody want to chime in with their local manifests? I've tried different variations of CM in the last couple of days and all fail out. Have some new things happening at work, and won't have as much time as I'd like to manage the threads. If you want to add some tips, tricks, and new manifests, I'd be thankful....successful items only please :p I have been building CM, AOKP, Slim, and PAC. PAC will compile and work, but I have a feeling that is only due to no new additions having been made in over a week(they're probably waiting for all of the commits and merges to die down). Slim built and booted successfully, although it had no wifi. AT ALL. AOKP and CM fail out for me repeatedly. CM goes back and forth between no term. apk, no term4. apk, and no libaudioalsa. apk depending on which way I configure the local manifest. I've been researching this and performing some attempts at workarounds, but so far no luck. Whether or not it is git or user error, I'm not sure(most likely user error, with me it almost always is:silly:), but I haven't seen anything about these issues anywhere else, and devs like CvD seem to be rolling along. If anybody out there still uses a skyrocket, can we get some feedback going? Not just for my sanity, but so I can update the thread accurately. Be cool everybody.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Did you try starting from scratch in a new build directory? I do that once in a while to clear up repo syncing issues and freshen things up.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Man, I dumped my entire CM file and resynced the whole thing. Three times. In the last 36 hours. Tried it twice before that. No dice. Would you mind sharing you local manifest with me? Just want to see if yours looks incredibly different than mine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Took a break from failing with building CM10.1 and came back to building jb 4.1.2. I'm still using the same manifest and not running into any issues:

<?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_celox-common" path="device/samsung/celox-common" 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>
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bearclaw7380:
I'm going to give this a try. Always wanted to build from source. I was getting sick of making ports all the time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Here's mine:

<?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_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jellybean" />
<project name="DAGr8/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="jellybean-oc" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
</manifest>

and with it, I get all the aforementioned failouts. I have tried with the default kernel in place here as well, and get no love. Could not having cleared my ccache in while be the culprit? i cleared it before starting a new CM build, but haven't since then.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yep, that's pretty much my manifest except I'm pulling in the Nibbles kernel from my git repo.

For some reason, the cm.dependencies files always forced me back to the CM10 kernel until I edited them. Frustrating that there is a buried dependency in there, at least for me it was.

As an aside, I've also grown really annoyed with the crappy screen auto-dimming on our platform. I'm working on changes to the Nibbles kernel to support 20 levels of dimming for smoother, more responsive transitions. The automatic light sensor levels only ever pay attention to the first 4 settings, no matter how many more levels you add. By adding more (20), not only will the transition be smoother, but it'll be less likely to jump to a higher brightness and save battery significantly.

If you look at the settings now, in an average room it'll hit 150 (of 255 MAX) on the brightness. In a dim room, it'll drop to 40. The in between of 100 doesn't usually get triggered often, so you have a huge change in brightness instead of a smoother, more linear progression.

Pending my test results, I may add support for more than 20 - I have a lot of testing to do with the settings once the code is done to figure all that out. Fortunately, there are a lot of useful posts for devices that support that amount so I have some data already available.

I have already figured out where the changes need to be made in the kernel, I just have see if any of the UI needs to be changed to support it as well (I'm thinking not, but you never know). This really should be as straight forward as I think it is, but I hate to underestimate it :)

Why should you care?

Well .. obviously, if you use my kernel or rom you care. But I'll share the code, maybe even submit a CM10 gerrit, so you can use it in your own builds.

The trick here is going to be capturing more sensor data in different levels of bright/dark to see what values are there. So, I wrote a script to do that for me. Tonight I'll run it through various scenarios from a dark room to flicking on a light and slowly dimming lights. Tomorrow, if it's nice out, I'll see what value corresponds to direct sunlight. After that, I should be set to figure out truly how many levels we need and what brightness should be at each point.

Now, back to my day job ...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Hmmm. I don't have too much trouble with dimming on Blinky, but I tell you where I do see that problem; my N7 with the codefire ROM. Would love to see a walkthrough on adjusting those settings. Bugs the crap outta me, so I understand what you mean. Any chance yer picking up a N7 soon? haha. Back to the other issue, throw me a bone and let me in on where to find these dependancies that keep tripping me up. I have spent hours scouring my files looking for this, because it's probably the true cause. Would be grateful to be pointed in the right direction on that one as well.

As for the other stuff, isn't anybody building Slim or AOKP? Need to know what the deal is with Slim having no wifi, but an other wise relatively functional build. AOKP; I saw a post with a possible solution to my issue a page or two back, just haven't had time to try it out. A CPU value, I think it was? I haven't looked at the posters name recently, sorry. If your'e around, could you expand on the tip and tell me what you did to work it out? Thanks to all in advance.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Beyond the update to the Term.apk url path on 12/30 that I mentioned already, I don't see any other changes to the jellybean branch of CM that could be giving you any issues, and the only other difference I see based on what you've told me so far is kernel source, but I don't see how that would cause any Term.apk issues. Are you sure you're still having an issue with Term.apk? If you do a straight vanilla CM 10.0 build with the CM kernel, what is the specific error that breaks the build?

Two more questions: which toolchain are you building with? What's the directory/file tree look like at /vendor/cm/proprietary? It should look like this:

m4570d0n@HP-dv5:~/cm10/vendor/cm/proprietary$ tree
[COLOR="RoyalBlue"].[/COLOR]
|-- [COLOR="RoyalBlue"]lib[/COLOR]
| |-- [COLOR="RoyalBlue"]armeabi[/COLOR]
| | `-- libjackpal-androidterm4.so
| |-- [COLOR="RoyalBlue"]mips[/COLOR]
| | `-- libjackpal-androidterm4.so
| `-- [COLOR="RoyalBlue"]x86[/COLOR]
| `-- libjackpal-androidterm4.so
`-- Term.apk

4 directories, 4 files
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Here is from last night's attempt after a complete reinstall of CM files:

make: *** No rule to make target `vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so', needed by `/home/bmp7777/cm10/out/target/product/skyrocket/system/lib/libjackpal
-androidterm4.so'. Stop.
make: *** Waiting for unfinished jobs....

As far as the toolchain, I have nothing in vendor/cm/proprietary except term.apk. I've always figured there was a problem there, but in all honesty, I had no idea how to fix it on my own. In times past, this has been one of those issues that seemed to fix itself. I assumed that a resync would take care of it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Did you run the get prebuilts script?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yes. I went straight from the tut in post #1, except for the local_manifest, which for some reason has decided to go by-by. Had a manifest saved in my files; haven't built straight CM since Sept.

This is what I get when trying get prebuilts:

bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/cm10$ vendor/cm/get-prebuilts
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 223k 100 223k 0 0 259k 0 --:--:-- --:--:-- --:--:-- 338k
Archive: vendor/cm/proprietary/Term.apk
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of vendor/cm/proprietary/Term.apk or
vendor/cm/proprietary/Term.apk.zip, and cannot find vendor/cm/proprietary/Term.apk.ZIP, period.

?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
It should look like this:

m4570d0n@HP-dv5:~/cm10$ ./vendor/cm/get-prebuilts
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 335k 100 335k 0 0 316k 0 0:00:01 0:00:01 --:--:-- 376k
Archive: /home/m4570d0n/cm10/vendor/cm/proprietary/Term.apk
inflating: /home/m4570d0n/cm10/vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so
inflating: /home/m4570d0n/cm10/vendor/cm/proprietary/lib/mips/libjackpal-androidterm4.so
inflating: /home/m4570d0n/cm10/vendor/cm/proprietary/lib/x86/libjackpal-a
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Cleared ccache, made clean, resynced using:

repo init -u git://github.com/CyanogenMod/android.git -b jellybean-stable

an still:

bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/cm10$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/skyrocket/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/cm10$ ./vendor/cm/get-prebuilts
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 223k 100 223k 0 0 292k 0 --:--:-- --:--:-- --:--:-- 373k
Archive: ./vendor/cm/proprietary/Term.apk
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of ./vendor/cm/proprietary/Term.apk or
./vendor/cm/proprietary/Term.apk.zip, and cannot find ./vendor/cm/proprietary/Term.apk.ZIP, period.

I even went as far as to delete this apk out of the file, and it syncs the same one in its place......
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
This is what your get-prebuilts script should look like:

BASEDIR=`dirname $0`

mkdir -p $BASEDIR/proprietary

# Get Android Terminal Emulator (we use a prebuilt so it can update from the Market)
curl -L -o $BASEDIR/proprietary/Term.apk -O -L http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk
unzip -o -d $BASEDIR/proprietary $BASEDIR/proprietary/Term.apk lib/*

if it already looks like that, then paste this link in your browser:

http://jackpal.github.com/Android-Terminal-Emulator/downloads/Term.apk

and save the Term.apk to /vendor/cm/proprietary. Then extract the "lib" directory from within the Term.apk and place that directory at /vendor/cm/proprietary/lib.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Haven't looked at the script itself yet. I pulled the cm/proprietary file from my PAC directory and added it to my CM. Building now. I will look into that though. Thanks:)

Now i just have to figure out what the deal is with the Slim and AOKP builds:banghead:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Have you made any head way on Slim? I don't understand why you wouldn't have wifi? There is not many changes in Slim these days due to everyone moving to 4.2 and Slim has dropped our phones support for now. I have a bad feeling that our phones are going to be left behind, I hope I'm wrong though!

Here is a copy of my local_manifest:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="SlimRoms/device_samsung_hercules" path="device/samsung/hercules" remote="github" revision="jb" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />

<project name="SlimRoms/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb" />

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

</manifest>
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
My manifest is identical, and won't even sync up anymore. Dunno......

I don't know what the deal is, other than to say ours is a dead phone. Slim, AOKP, and Liquidsmooth are all unsupportive of the skyrocket at this point. I think CM is only keeping up with it due to the 8660common files, but I could be wrong. I am like CvD in that I don't see why support continues to thrive for devices like the Captivate, that have lower specs, but not for ours. The only thing i cn think of is that all the ones with the real knowhow don't want or own one any longer, so there's no one to pick up the torch and run with it, so to speak. I personally don't know enough to try and work out how to continue support in terms of new building; I have been trying. If some of you want to get together and try to work some new builds out, I'm down. Otherwise, I'm not sure what to say. CM and PAC are still building, but I have no new features to offer for PAC(it's not updating for this device anymore either), and CM is not adding support for this device in it's transition to 4.2, at least not yet. Hmph
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'll go ahead and say it for the record ...

Ladies and gentlemen, we have a legacy device.

I don't see myself leaving anytime soon though. I've no real reason to. The phone is fast, works well and does all I need it to do. I initially wanted the Note II, but for the price, I'm not so sure (I only buy unlocked, no contract phones). The S3? I'll be replaced by EOY with the S4, which is probably what I'm going to get next - I'm expecting it to have AMOLED and one of those new 8 core processors announced at CES this week.

If not ..

Well, this looks awfully nice too ....

http://www.gizmag.com/lenovo-new-smartphones/25734/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
You was talking about clearing cache? I have never done that. I make clean or clobber before every build. And can still sync and build Slim with no problem, there just hasn't been much of anything going on for the hercules or skyrocket

---------- Post added at 10:52 AM ---------- Previous post was at 10:46 AM ----------

I read the S4 could be out by march. I would be mad if I upgraded to s3 and new one is out in 9 months from release.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
OMG, that thing is SWEEEEEEET! I'm pitching a tent and drooling at the same time. Probably gonna cost a grand though......WITH CONTRACT. Too rich for my blood.

Makes me think of a saying a read here that truly said it all about people like us. It was something to the effect of...'You know you're a phone junkie when you get caught by your wife staring at a chicks ass, and it was only because you were trying to see what the brand of phone it was hanging out her back pocket' D'OH!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Well I don't know what changed from a couple days ago but my repo sync with cm10.1 for d2att worked this morning. I actually made a successful build, transfered it to my phone, and it won't boot. It built without errors so I don't know why it wouldn't boot. I even compared it to another AOSP ROM and everything looked pretty much identical. So now I'm stuck at that part of it...

Really is frustrating consider it took 3 hours to sync and 4 hours to build on my slow laptop. I'm actually in the process of building my very first computer, so I think I'm going to wait to do the the building and syncing until after its complete. Its not going to stop me from trying this stuff though. Does anyone have any suggestions as why it won't boot or somewhere i could look or test to get the kinks worked out? Thanks for the guide and the help so far. I have a genuine interest in learning this stuff.

BMP did you get your sync issues worked out? Like I said I had the same errors as you when trying to sync but for some reason it worked today. Good luck man.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
Boot lap is totally related to kernel related issue...

Check for that...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Thank you for the help but I honestly have no idea where to start with finding out if it is a kernel problem. I've done some research and most of it is just to build the kernel from source. Can you point me in the right direction where to go. I don't mind doing the research and such, just kinda gimme a nudge maybe....:fingers-crossed:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Where does it get stuck in the boot process? Do you get to the boot animation?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
No it just goes black. It shows the samsung logo for a second then solid black. If I held the power button down(reset) it would show the logo again then nothing....solid black. I have a boot.img file in my zip. Just kinda stuck here. Took me forever to get back to recovery and restore a backup.

Like I said I compared my basic files in the zip with another CM rom from someone else and its almost identical. The file sizes are similar and the structure is the same.

I know this is part of the process to learning and I'm all for it. Just need to know why and how to fix it. (or should i say where to find out how to fix it). I don't mind the work. Just hard to do when I'm just starting this with hardly any knowledge of compiling. I've researched forever and it took me forever to finally get sync and a build(2 weeks) so i have the patience.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Well i use twrp and if it was me i would pull the lastkmesg and see if there were any errors
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Flash a different kernel on it and see if it boots up.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
First open the ota zip with archive manager and check for the boot.img file if present...

Other make sure you have right manifest for your device kernel...

If you have used cm kernel repo and building cm then there should be no other problem ...

If these two things are correct then make clean and sync repo again and try to build...

If still problem persist then something is seriously wrong...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Tried a different kernel....no go. :banghead:

My boot.img file is there. My kernel manifest looks good. I'll check it again and rebuild.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
Hey could you post your cm kernel and device tree github repo link...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
My github repo link? I didn't know i needed to have one. I was just following the guide from the cyanogen wiki. Or do i need to setup a personal one?

I'm going to try to build something else and see if that works or if i have the same error.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Black_Prince:
No my friend...

I just wanted to see from where you downloaded sources...like cm github link to your device tree repo and kernel too...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
I'm getting everything from cyanogenmod. I'm following their instructions of their wiki specifically for the d2att. I keep thinking that it has to do with the proprietary blobs but i do the step to get them as they show. Right below where it gives the instructions it says not doing this step may cause you not to be able to see anything. I'm pretty sure its flashing because I'm coming from 4.1.1 to 4.2.1 and 4.2.1. has a different file structure where it creates "0" folders and as soon as i restore my backup and look in my file explore the "0" file is there.

I really appreciate your help. I'm trying to build a RootBox rom right now to see if it boots. Im just trying to eliminate the variables.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Built another Slim build from absolute scratch over the weekend, and still no wifi. Don't have a clue as to why. Researched all over the forum, site, and net in general, and the closest I can come is that some other devices had a no wifi issue with current builds months ago. Sooooo, I dunno. Fully expected this to be a user-error situation, but can't find what I'm doing wrong anywhere. Anyone? Anyone? (My Ben Stiller moment):confused: