yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I have the same problem with building CM10.1 on the N7. But, for me, I can't seem to get the blobs from the device itself. Even if I can get Linux to 'see' the device, which comes and goes, I can't pull the files from the device. I followed the steps in the Cyanogenmod tut for building 10.1, but obviously I'm falling short somewhere. Do you know for a fact that you get the blobs, or do you assume it takes place because you follow the directions? Not being a smartass; the tut I'm following says that the command won't show that the 'pull' has taken place. So, are you checking the files afterward, or just building? The build won't fail, it just won't boot; or have a screen. What steps are you taking here? Also, I thought that the '0' folder issue had been straightened out. Is it still a problem?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
I can see the adb commands pulling the files from the device after i type in the .sh script. It extracts some lib files. It may not be pulling all of them since i can't see anything but i check my directory where its supposed to pull to and it does add files. I've checked and started 100% over about 5 times now to see if maybe i did something wrong, and when i say start over i mean deleting everything and starting from the making directories instruction. It'll build what is assume is correctly. I can install it and it'll show the android logo for a split second then go black. Nothing more. But i can restore my nandroid (4.1.1) and it shows the "0" file structure from 4.2.1. , so i assume it flashes correctly, just doesn't show images. I've let is sit, tried rebooting and nothing. The "0" folder will be there on 4.2.1. The problem was recoveries making "0", then "0" inside that folder and so on....

I'm in the process of building a brand new beast (or at least better than what i got) so I'm gonna wait and get that up and running and try then. Didn't want to wait but after all these attempts its beginning to get more than frustrating.

Oh, and i tried to build the RootBox ROM and spent 3 hours repo syncing and 3.5 hours building only for it to not create a zip file. Started at 2 this morning finished at 8ish. That kinda was the final straw until i get this new rig up and running. I wanna build aokp so bad but it seems way more tedious than CM. I wanna get a 100% successful build with that first as that seems to be the easier route. Once i get it going maybe we can gtalk or something more capable of quicker responses.

When you plug your N7 in can you see the files that are on it? MTP connections is a mo fo to get setup by the way
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
If you can see the adb, then you are definitely on the right track. I don't even get that far. I can get my system to recognize the N7 from windows no prob, which of course does me no good. I can get it to recognize through PTP(pictures) but not MTP(media), so of course I don't even get that far. If you have some tips, I'd love to hear them.

As for your build, are you building a straight vanilla CM right now? I keep starting from scratch as well, and I'm not sure that the two of us aren't wasting more time than we need to due to lack of knowledge. I have to walk away from it sometimes, and just let certain things come to me as options for a fix. I am not familiar with RootBox, is that a ROM you are creating or kanging? Just curious if you have added files that could be contributing to your issues. I am on google+, although I don't get the chance to hang out on it much. Send me your handle and I'll request you. Otherwise, look for BMP7777 and you should be able to find me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
I technically own the skyrocket too but it's not my dd anymore. The new KingBeatZ mod is reworked and new DSP manager. Its now called BeatZ BanGer. I've been busy with my kernel but now it back to the mod.

REAL 96kHz Audio Processing. 24bit and 32bit audio conversion. Noozy settings but even better.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Are you tweaking the audio drivers or just applying adjustments to the audio during playback?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
Well, I'm doing more than just that. I'm giving your audio system an overhaul since the libs I'll replacing is the audio base for 4.2. I can only replace so much do to conflicting libraries I'm my ROM I have custom audio and what not linaro. Blah blah Lol plus this isn't just for Audio alone. It had been optimized.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I think I will man-up and admit that I can use Git for accessing other devs files, but don't have much of an idea of how to do other things. I know I'm not the only one, but someone has to throw out the 'rookie' card and get this opened up for discussion. I am willing to embarrass myself in order to not only get the info I need to progress, but to make yet another tut that will benefit all in the long run.

1) I know how to access other's files from git, but what about pulling from others to make my own repository? I have attempted it, but am smart enough to know how dumb I am and haven't gone much further. How does one put together a repo from other places that will provide the means with which to build? I would like to do just that, so if changes bork the overall repo, I can still build with my current files, albeit un-updated.

2) What is the method used to create, modify, or otherwise change your local_manifest.xml to have other additions in place? How do you add an 'after-market' kernel to your vanilla build? Why does it take more changes in some cases and not in others? For example, why does the addition of the KKO kernel only take a small addition to the local manifest, and another type, like the LZ or Nibbles kernel, require the altering of other files as well? How do you determine the difference, and how do you 'create' the addition for the manifest?

I feel VERY dumb having gone this far with building and not having some of these questions answered; at this point, I think that not knowing these things(and others) is keeping me from going to the next level of building, learning, and progressing. So, anybody wanna lay it all out for the idiot? This way, all the ones that feel that dumb but were afraid to ask can pawn it off on me.....:angel:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
I found a site through google that was a little older but it worked for the most part. Sometimes it would mess my files up (like the ability to see some files) and had to reboot to get it back to normal. I'll give you a link if you'd like. I was trying to build straight CM from scratch as per their wiki. I'd love to have more knowledge but i learn easier from watching rather than instruction which suck. YouTube has been a savior. RootBox is an AOSP ROM that was made available for some devices. Look in the AT&T Galaxy S3 Original Dev forums for it. Kinda cool. Its basics but some CM some AOKP. And I tried it 100% separate from building CM (deleting EVERYTHING). My name on G+ is Sean Boren. I looked for you but couldn't find you. I have never really used it but for something like this I may have to start since I see so many people (android enthusiasts) that use it.

I'm in the same boat but at least you have gotten some good results like successful compiling on something....but yeah i wondered the exact same things. I was gonna ask all that stuff next as soon as i got a good build going but thanks for stepping off that ledge....hahaha
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
Oh man, I'm more of an example guy than a guide guy. Lol I should have class session. Lolol

---------- Post added at 03:09 PM ---------- Previous post was at 02:58 PM ----------

Its the kernel. They changed something. You boot but you're stuck at splash for a but longer than you go black right ?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey everybody! hehe

I agree w the kernel bit. I'm still on DAG cuz It's the only one I can make work. Any equally quality/easy to repo kernels out there?

Needless to say I've fallen behind...

The other is the manifest area of the OP under cm10? nano?...blank...?

I was wondering what the general state of cm10 was.

1.

ie: diff between v4.1.2 and cm10.1? lol

2.

Is 4.2 going to be cm10.2?

3.

Is the latest kernel base still 3.0.49?

4.

Do I have to modify my local_manifest for cm10.1? I see lots being added during repo sync but my build vervion is still 4.1.2

5.

In repo sync -j16....Is the j16 a job count # or is it the sdk version?

Any help clearing these up would be great, thanks!

PS: I guess I should add that ultimately I would like to get myself on to the most up to date cm10 version possible.... :-/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
4.1 is cm10. 4.2 is 10.1. To answer your question yes ALOT in the framework and audio.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Cool! But what question? Kernel....? I'd love to get caught up with everything. I read back, awaaaaaay back through the thread and I didn't catch when everybody switched to 10.1. I thought somebody said that it would just slowly get merged into the main JB repo automatically. Clearly not the case. When I check the git, there is no diff addy for JellyBean, Jellybean-stable or cm10.1. And alot of the rom doesn't have 10.1 even. Do you have to just change the local_manifest to reflect name only along with the fetch record?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aznrice2k4:
Nah, it more then just that. The way 10.1 builds is differently than 10.1. The proprietary files are different too. My kernel isn't in my repo. Lol I link it from my own kernel directory.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
This was fixed quite a while ago with recovery version 6.0.1.6 back in mid Nov.

https://github.com/CyanogenMod/andr...mmit/8e40f42d2e0b21a8ed02cd66c825f913876917cd

You have an up to date version of recovery?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That's cool. Would you be able to explain a little deeper? I'm not too bright....:-/

I actually thought that it might show up in the OP.... the cm10.1 updates to everything.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Yes I always run the latest TWRP 2.3.3.1. I was explaining to BMP that it does make a "0" folder (just one like its supposed to) when i flash the CM zip that I had compiled, so i think it does flash. It just doesnt show me any images. Ive tried pulling the proprietary blobs (which i assume is the problem...maybe...:confused:) when i was on 4.1.1 and on a 4.2.1 ROM to see if that would make a difference. It still gave me the same results. I don't get multiple "0" folders. The file structure is there when I restore my nandroid just like when I go from a working AOSP 4.2.1 rom back to 4.1.1 so something from my zip has compiled right. I just can see anything.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Have you checked your udev rules (/etc/udev/rules.d/70-android.rules)? I would assume you would probably need to update that file for the N7.

# Google Nexus 7 16 Gb
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="your-login" # MTP media (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your-login" # MTP media with USB debug on(multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e43", MODE="0666", OWNER="your-login" # PTP media (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="your-login" # PTP media with USB debug on (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="your-login" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your-login" # Recovery
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Looking through my root files now and don't find a udev file. I've looked in /etc and /system/etc and no dice. Am I a moron? Don't answer that...:rolleyes:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You should have that file there. You need that for setting up USB/ADB. It's in the first guide in your OP for the initial build environment setup (Step #3). In that guide you had it as "/etc/udev/rules.d/51-android.rules"

It's also part of AOSP's guide here, under "Configuring USB Access":

http://source.android.com/source/initializing.html

The number itself is different depending on what you decided to use. Files in /etc/udev/rules.d/ are parsed in lexical order, and in some circumstances the order in which the rules are parsed is important. That's where the numbers come into play, as a file named 10-some.rules will be parsed before a file named 20-some-more.rules.

From the various guides I've seen, it seems like the general rule of thumb is that you would use 50 if you are running Ubuntu 8.04, 8.10, or 9.04 (50-android.rules), a higher number like 70 if you are running Ubuntu 9.10, 10.04, or 10.10 (70-android.rules). I've seen several guides and threads that seem to use "99" on newer releases like Ubuntu 12.04 and 12.10 (99-android.rules}, but I don't know if going with that high of a number is necessarily needed. I feel like I recall reading something more specific about that several months ago but I have no idea where that source might be now if I did.

Anywho, I would be very surprised if you did not have this file there at all. However, since it's a file you just create and then never really look at again unless you get a new device, I figured it was possible that might be a potential source of your issues with getting the N7 to connect. Even if you did have one of those lines for the N7 added to your udev rules (as I have seen in several N7 specific threads) there's also a chance that adding those other lines might help. It can't hurt anything, so worst case scenario you're in the same position you're already in. :)

---------- Post added at 09:46 AM ---------- Previous post was at 09:38 AM ----------

btw, this is off topic but I thought you might like to know BMP, that Fedora 18 has been released and the torrents are now live as of a few hours ago. :)

http://torrent.fedoraproject.org/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
How do you know all this stuff, man? Damn, do you even own an N7? If this is how you deal with your hobby, you must be the man at your job. LOL. Anyway, back to the 'am I a moron?' question. I guess so, cuz I mistakenly thought you were referring to my root files on THE DEVICE, not my build environment. The reason for my thinking is that I have a lot of trouble getting the device to connect through my Linux distro(Luninux 12), even to just to access the memory for adding new builds. So I wrongly assumed you meant to fix my connection issues in general. I will definitely add those lines to my file as soon as I get a chance. Thanks for your help, as always. Do you think Fedora would be a better build environment than Luninux? I have had good success with building using it, and had an easy time interacting with the UI for daily driver stuff. Ubuntu always gave me trouble......
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
There is no cm10.1 for our device yet (or really any msm8660 device)... at least not one that will boot. For CM, all Android 4.2 stuff is on the cm10.1 branch and all Android 4.1.2 stuff since "jellybean-stable" was released is still being pushed to the "jellybean" branch. For AOKP, 4.1.2 still is still on the "jb" branch, and 4.2 stuff is on the "jb-mr1 branch." ParanoidAndroid decided to just say fudge it, and has merged all android 4.2/cm10.1 stuff into their "jellybean" branch, meaning there will be no more 4.1.2 updates on PA, and if you try to build a ROM with any of their repos (like with PAC-man ROM) you'll run into issues unless the manifest is set to specifically use the Head from the last commit before PA started merging in 4.2 stuff.

Check the 4.2 thread for more info on the current status of getting cm10.1 to work on our phone.

http://xdaforums.com/showthread.php?t=1990891
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
That explanation was extremely well put, and I have posted it in other threads FYI. I hope you don't mind.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I don't have an N7 and I think I just got lucky (or my google-fu is just that good now days) that when I did a quick search, the first result had that list of all the udev rules for the N7, while pretty much every link I looked at after that only had one line listed in the guide/thread/whatever.

I've never used Luninux but it looks like it's just Ubuntu with Gnome 3/Gnome Shell, rather than Unity, pretty much like Linux Mint 12-13 was (minus the Mint-specific Cinnamon/MGSE stuff). I haven't built on Fedora so I can't speak from personal experience, but they're doing some interesting stuff with the new release.

http://www.techrepublic.com/blog/op...-be-released-with-game-changing-features/4105

http://fedoraproject.org/wiki/Releases/18/FeatureList
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Have you looked at elementary OS Luna? It's simple but looks good
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
looks really nice, it reminds me of mac osx but still looks clean and crisp :p
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok , I'll have to wait for cm10.1...

As for "AOKP...4.2 stuff is on the "jb-mr1 branch"...

I started a new build folder and attempted

repo init -u [URL]https://github.com/AOKP/platform_manifest.git[/URL] -b jb-mr1

Then a repo sync. It made it to 99%(349/353) then froze there, repeatedly.

I then tried to add a local_manifest to try and point it to SR but still no go. At one point it actually went and deleated everything samsung???

Any way to build this 4.2.1/jb-mr1 AOKP?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
hey bmp, im trying to setup my build enviroment again, finally got around to setting up my comp again for linux, the last one died, man i forgot alot of stuff, been following this thread though to see whats happening, too bad for 10.1

been following the guide in the op and the local manifest sections in the tuts are empty, can you explain as too why or did i miss something in this thread
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
This is the last known for me. When you sync, it will say it's deprecated, but it still works.

<?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" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jellybean" />
</manifest>

....this is for cm10
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Working on the same thing for N7, and am having similar issues. I keep getting error 404 and clone not found fails. DOOFENSHMIRTZ :crying:

I have no idea what happened to my OP, and I keep forgetting to update those missing manifests. Sick as a dog but still dragged my ass to work. Got my laptop and will try to update those missing sections at some point this morning. Sorry :angel:

Mine is very similar. I will get the manifests back where they belong ASAP:eek:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
Hey bmp. Got my computer built in about 3 hours Tuesday and setup my build environment yesterday. Got report sync done and tried to pull the proprietary files and I think I found my problem. It starts to pull them then fails when it says it can't find a files so it pulls nothing. That's Why I couldn't see anything. I pm 'd a dev about it and waiting for a response. I'll give more info when he writes back
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Had the same problem. Took my proprietary files from my PAC build directory and pasted em in CM and voila! Ran like a......like a....well, it ran. I'll shoot them to you as soon as I get a chance.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
He told me to use TheMuppets proprietary files and copy them to my local manifest

But Yeah. Shoot them over and I'll look at them too to compare
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Either way, brother. They come from the same place. Let me know how it goes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roughneckboren:
So is that where you got your proprietary files initially?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
PAC has a CM base so, yes. But, I noticed that Muppets hadn't updated in a while and that may have something to do with it. Not sure to be honest. But, my PAC proprietaries did it for a CM build. If you have any trouble with muppets, let me know.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Also,when you have a chance, the OP needs to be revised for SlimBean.

[SIZE=4]

[COLOR=Black] lunch slimbean_skyrocket-userdebug && mka bacon[/COLOR]

[/SIZE]

Needs to be changed to :

brunch slim_skyrocket-userdebug && mka bacon
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
did you guys see this, cm10.1 jb 4.2.1 booted on hercshttp://xdaforums.com/showthread.php?t=2103831

i changed the updater script and buildprop, flashed and yup.......it booted, rotation is fracked up though cant seem to fix that, no data/phone connection, wifi works
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Any chance that would have anything to do with why my Slim builds have no friggin wifi? CAN"T FIGURE IT OUT AND IT"S DRIIIVVVIIINGG MMMEEEE MMAAAAADD!

Ok, Ill get that changed as soon as I can.

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

Well bmp looks like you gotta gotta work to do now! Glad the skyrocket guys got this thing Maybe started. :D:p:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
yuuuuuuuuuup, was trying to get a screenshot, but it wasnt working, trying to get gapps to play nice, but nope, im going to find a comp. gapps or edit the one for 4.2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
brunch includes the mka bacon command so you don't need that at the end of the second command you posted. The brunch command is literally defined as breakfast [device name] && mka bacon, and the only difference between breakfast and lunch is that lunch allows you to build unofficial or non-standard builds for devices.

So:

lunch slimbean_skyrocket-userdebug && mka bacon

and

brunch slim_skyrocket-userdebug

are the exact same commands and do the same thing. You can use either.

If you ran

brunch slim_skyrocket-userdebug && mka bacon

then you would be initializing the build configuration (breakfast/lunch) and then building the ROM... and then building it again. ;)

---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------

Nope.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yeah, I knew. But, I was hoping. You're the stud around here. WTF? I have followed the steps properly twice and have a fully functional build in every other way. But, no wifi, no ROM. Looked and asked around and no one knows or is telling.....