yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] sparksco:
Yes. It only cleans out your installation folders, not all the compiled things.

Sent from "The Mile High State"
[Nexus 7 Android Development] slebit:
Thanks. Will try that too. Maybe I have time to look at it tomorrow.

Edit: Tried "make clean install" and it did erase all of my files in "out" folder. Maybe it's supposed to be "make install clean". I will try that one next time. :)
[Nexus 7 Android Development] sparksco:
It's makeinstallclean one word

https://groups.google.com/forum/m/?fromgroups#!topic/android-building/TLPcHh05DxM

Sent from "The Mile High State"
[Nexus 7 Android Development] slebit:
Thanks. Will try that next time.
[Nexus 7 Android Development] sparksco:
The Google guys were wrong lol. I tried it. It's make installclean but I don't know if that'll work for cm roms. It might just be a aosp thing. I wish cm would add their own option to do something similar though. Would make it much easier. Well as you know I've added some bash scripts to do my bidding :p

Sent from "The Mile High State"
[Nexus 7 Android Development] slebit:
Thanks for all your help. I really appreciate it. :)
[Nexus 7 Android Development] #define:
Works on all roms... Even aokp and pa...

Self-tested...

ғг๏๓ ҭђє ғเรђ! ™
[Nexus 7 Android Development] #define:
It seems that the servers that you're trying to download from, dont have those packages anymore.. Have you tried doing 'apt-get update' and 'apt-get upgrade' before installing the packages??

Sent from my Nexus 7
[Nexus 7 Android Development] memphian:
Think I found the problem. Seems I had the wrong JRE and JDK versions.
[Nexus 7 Android Development] memphian:
On the tut it states...

You can make this change to the path permanent for all future Terminal sessions:

$ gedit ~/.bashrc

I don't see a .bashrc. Should .profile be used instead?
[Nexus 7 Android Development] sparksco:
You can make a ~/.bashrc and terminal will automatically use it. I had to do this with Linux mint. After you make it open a new terminal window and the path in your ~/.bashrc for java will be automatically used.
[Nexus 7 Android Development] TheDarkDefender:
Hey all, I'm using ubuntu 12.10 and I've been getting constant notifications to upgrade to 13.04 . Should I? Is it good/better than 12.10? Is anyone using it?

Sent from my Nexus⁴
[Nexus 7 Android Development] :
I use it and don't have any problems but that's not song that there aren't any bugs. I do not build for the N7 anymore but I do build my own CM for the AT&T One XL and it builds fine. Some visual tweaks on Unity for 13.04 but I use the gnome desktop. I like the look better
[Nexus 7 Android Development] underwaterjr:
I've also been using 13.04 and really like it. No problems using it and both my phone and tablet connect a lot easier to it.
[Nexus 7 Android Development] sparksco:
Don't know why people are afraid of progress or change, I've never had a issue upgrade Ubuntu unless I'm trying to build froyo. With the exception of setting up java properly, but I've gotten used to that as well.
[Nexus 7 Android Development] technicaltitch:
How can I reduce the size of the initial repo sync?

I am trying to get the source code. The problem is that repo sync seems to kill my router, so I've used an Amazon AWS server as a staging post. I've given my instance a 30GB drive to repo sync into, which it has completely filled. I thought the source was closer to 20GB. In two days I return to Ethiopia, where I have no chance at all of downloading anything bigger than a GB, so I need to get this source quickly. So I've given up syncing to my AWS, started creating a tar and FTPing it to myself, but even if I left it running all three days I wouldn't get the whole tar file, which is still incomplete..

How big is the cyanogenmod source? Is there any way I can exclude bits from my 'repo sync'? Are there projects I don't need? How can I exclude other devices?

I want it so that I can create a custom build for the Nexus 7 (wifi) (grouper). I wan to lock down the UI, so that children can use the tablets as educational devices without distractions, ie the tablet boots straight into my app. I also want to enable creation of a wifi hot spot, and get the tablets to disable themselves if not connected via wifi for 48 hours, to prevent theft.

Any ideas or suggestions very very gratefully received, thanks, I'm pulling my hair out!
[Nexus 7 Android Development] disconnecktie:
The cm source is closer to 40gigs.
[Nexus 7 Android Development] technicaltitch:
GREAT to know, thank you.

Anyone know the size of the CyanogenMod source if I get no source control history, ie, git clone -- depth 0?

It looks like I can edit the repo python file to set depth (on the line

# Original: group.add_option('--depth', type='int', default=None,
group.add_option('--depth', type='int', default=0,
dest='depth',
help='create a shallow clone with given depth; see git clone')

).
[Nexus 7 Android Development] Archaic1881:
Just finished my first CM build, completed succesfully, but I'm a bit hesitant to flash it to my device...

Is there any way for it to not work even when it has completed succesfully ?
[Nexus 7 Android Development] DJLamontagneIII:
Its possible... Just make a backup
[Nexus 7 Android Development] sparksco:
Follow the wiki instructions and it should be fine.
[Nexus 7 Android Development] sgt. meow:
Would it be completely stupid if I were to ask if root issues still persisted in your build [MENTION=3041959]fattire[/MENTION]? Great job anyway. :)
[Nexus 7 Android Development] fattire:
What root issues? I think I have root...

$ adb shell

shell@android:/ $ uname -a

Linux localhost 3.1.10-g1e8b3d8 #2 SMP PREEMPT Sat Jul 27 08:32:22 PDT 2013 armv7l GNU/Linux

1|shell@android:/ $ su

shell@android:/ #

(I haven't been paying much attention to what root issues people were having, but if you want me to test something I can... was this related to the selinux stuff?)
[Nexus 7 Android Development] TheDarkDefender:
[MENTION=3041959]fattire[/MENTION]

Hi.

I wanted try out a build for mako. So i created a new directory,copied .repo folder from the cm10.1 source into the new dir, to save some sync time. So I then did a "repo init" from the 10.2 manifest,and then repo sync. I keep getting fetch errors and warnings like,

and

thanks.

Sent from my Nexus 4
[Nexus 7 Android Development] sparksco:
Wow did one person really merge frameworks/base on cm-10.2? So much for starting over. Hmm, how can anyone tell what changed besides looking at each file imdividualy? Looks like over 3000 files changed...

[MENTION=3041959]fattire[/MENTION]
[Nexus 7 Android Development] :
Would you mind sharing your CM10.2 with us? For me building would take 1-2 days.
[Nexus 7 Android Development] slebit:
Building cm10.2 right now. Will see how it works in about an hour. :)
[Nexus 7 Android Development] fattire:
I want to wait until it's a wee bit more stable. It's very usable and everything, but MTP doesn't work (settings->storage crashes too). Not sure if this is something messed up by me, or something not working for everyone using cm 10.2 or what. It also gives an occasional but annoying "android.process.media" crash error every now and again, which i've confirmed is affecting other devices too so it's not my fault :) Also chrome has crashed twice and I think Trebuchet at least once. No clue why.

That said, what appears to be working right now includes accelerometer, backlight, camera, sound, video, bluetooth, wifi... didn't test NFC... umm, what else is there... pretty much everything. It's just a stability thing.

I'm guessing the small issues are related to things that need to be fixed (or already have been) in the other CM repositories... I have written a quick walk-through on how to build for yourself, and I'm just waiting for my /device folder to upload to github before I post it.

At some point after that, someone else will no doubt build an unofficial version and rush it out prematurely :) Let them enjoy the glory and deal with the inevitable complaints. It's only been merged with CM for probably 24 hours, so instability is to be expected.

For those do-it-yourselfers, here are the first few steps if you want to get started. The steps assume you have built 10.1 for grouper before and have the source already loaded and everything set up for a grouper build.

All these commands should be issued from the root of the source tree (~/android/system if you've used the wiki instructions). So cd to ~/android/system or type croot or do whatever you do to get to the source code's main directory.

Now re-initialize the repository to use the 10.2 source by typing this:

$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2

Make sure you remove any old local manifests for 10.1 by getting rid of .repo/local_manifest.xml and anything in the .repo/local_manifests directory that may not belong.

repo sync to get the source. (You may see some warnings about repositories that don't have cm-10.2 branches. Ignore them.)

While the source is loading, you can, from the main source directory, mv vendor ../vendor-old-10.1 to move the 10.1 vendor blobs out of the way. You can find the sparkling new blobs for grouper here. Download each of the .tgz files to the main source directory, ungzip/tar them to get the install .sh script. Then chmod a+x each shell script so they are easly runnable, run them from the Terminal (sh [filename].sh), agree to the terms by typing "I AGREE" and the blobs should automatically be placed in the vendor directory.

I'll finish this up in a bit...
[Nexus 7 Android Development] sparksco:
I did a large merge into my AOSP ROM and they did change mounting around, so that doesn't surprise me that mtd is broke...

I take it you merge the kernel successfully? :)
[Nexus 7 Android Development] Scott:
I REFUSE to believe that someone asked this...

Im gonna check out your guide!

Any PC specs you recommend?
[Nexus 7 Android Development] fattire:
I'm using AOSP's stock kernel for now. Just rename tegra3_android_defconfig to cyanogenmod_grouper_defconfig and make sure that kernel modules are turned on in there. The cm-specific stuff on top of that should be pretty easy, but I wanted to go with a known kernel.

The device was the most challenging, with a few steps needed... I will make that available-- it's all done, but for some reason a gigantic factory image got stuck in the device history, so I'm trying to figure how to strip that out.. (if I can't soon I'll just make the device folder available.. it's tiny... no idea where these 256MB files are coming from when I try to push....)

Update: Okay, looks like it updated. Someone who feels adventurous can try building using these instructions/repositories. Let me know if it works.
[Nexus 7 Android Development] bangsti:
Many thanks [MENTION=3041959]fattire[/MENTION] for the Tips.:good:

My Grouper Build is ready, the only Problem i have no root. I will look later.
[Nexus 7 Android Development] yukkio:
Hi, Could someone share a personal 10.2 build?

Thanks.

BR.
[Nexus 7 Android Development] bangsti:
Now Root is working for my private CM10.2 Build.
[Nexus 7 Android Development] neilrl79:
Any chance you might share your build? I don't have the hardware to build my own but would like to have a look at one.
[Nexus 7 Android Development] jblazea50:
Mind sharing your build or PM your build?

Thanks
[Nexus 7 Android Development] TheDarkDefender:
[MENTION=4477697]bangsti[/MENTION] I think SU by koush wasnt merged when you synced.
[Nexus 7 Android Development] bangsti:
Yes i see the merge. Great work from CM Team. Little bugs but i think i few days CM10.2 are better and better.

Gesendet von meinem Nexus 7
[Nexus 7 Android Development] fattire:
Congrats! Glad I'm not alone now. Okay! Who's next?! :)
[Nexus 7 Android Development] bhu1:
Anyone of u who has built 10.2 today mind sharing the build. Many of us don't have capable enough hardware to build ourselves. And stock aosp lacks tons of features, it will be good to move back to good old cm.
[Nexus 7 Android Development] sparksco:
I'm sure cm will start releasing nightlies soon when they feel it's ready for public release...
[Nexus 7 Android Development] fattire:
Yeah for all its lack of features, stock aosp does have stability now, so I'd stick with it until the cm 10.2 stuff gets a wee more robust. A few days of patching and testing upstream will make a big difference. The code has been merged now for maybe 36 hours? There will be issues. Cm isn't yet the dependable and rock solid experience that it will be... Which is why I'm not posting a build.. It's still too crashy... At least my first one was. Things may already be more stable...
[Nexus 7 Android Development] bhu1:
Main problems are with dialer, ril etc. and some minor problems with root still there. But nexus 7 isn't a phone so it doesn't require dialer or ril.

I know current code isn't rock solid and knowing that I asked as I am used to running unstable ROMs and beta ROMs. I know small things will be broken but I also know that I can live with that instead of missing major cm features.
[Nexus 7 Android Development] GeyerA:
Hi Fattire,

I started to compile AOSP and have a few questions. Since I believe your thread is quite active, I hope you do not mind me posting here.

When I compile with "make otapackage -jx", I will still not have a fully flashable zip, isn't it? I compiled having the .img's but I would like to have a zip which can be flashed on a fully wiped device. How do you do this? Thanks :)
[Nexus 7 Android Development] azoller1:
Make otapackage should work but you could lunch device then just do "make" instead of with otapackage, brunch might work but that might only be for CM
[Nexus 7 Android Development] GeyerA:
Hi, thanks. I already made this but then I get the img files which need to be flashed via fastboot. I do not want this. I wanted to learn how to have a completely made/signed zip which can be flashed afterwards......
[Nexus 7 Android Development] fattire:
After source build/envsetup.sh try "lunch grouper" maybe?
[Nexus 7 Android Development] sparksco:
I think all you need to do is type lunch after . build/envsetup.sh

That will bring up the lunch menu. Select device by the number for the build. Ex. 15 for cm_grouper-user-debugg (not accurate)

After that make -j otapackage

Ex. make -j8 otapackage

Edit: also to make clean for only one device make clean will work after initialing the build environment.
[Nexus 7 Android Development] antp121:
You guide worked great! Thanks [MENTION=3041959]fattire[/MENTION] ! I hit a few hiccups but it was all on Cm's side of things and it was fixed with a repo sync. Anyways, everything seems pretty stable to me.
[Nexus 7 Android Development] GeyerA:
Ok thanks for your input here - let me show precisely what I already tried (and worked).

1. build/envsetup.sh

2. lunch (here I chose the grouper or mako)

3. make -j4 (or make otapackage -j4)

By using the make without otapackage, I will get the img files which need to be flashed via fastboot.

Using the otapackage, I will get a nice zip but my screen stood black on booting. The zip file was also quite small (around 135MB) where the factory images are around 350MB..?

So if I listen to you, the make otapackage zip file should work, right?
[Nexus 7 Android Development] fattire:
I think make otapackage (over the air package) is exactly right. The .zip should work though. Are you sure you're using the right binary blobs? Not using the right ones could result in a black screen (especially when it comes to the video stuff). Check the logcat and see if it's bootlooping or something.
[Nexus 7 Android Development] fattire:
Sweet! That's 3 of us now, I think. Anyone else want to join the club?

(In other Nexus news, my buddy kornyone has CM 10.2 building for the Nexus 10 now! Check his Google+ page for more.)
[Nexus 7 Android Development] GeyerA:
Hi, thanks. Sorry but what is a binary blob? Don't I get these when I sync my repo? And if not, what do I need to do. I thought about the zip file again and re-try to flash.
[Nexus 7 Android Development] fattire:
take a look at step 5 of the instructions I posted a couple pages back. It talks about how to put stuff in the vendor directory that you get directly from Google. These "binary blobs" are specific to AOSP 4.3 (and CM 10.2) and you need 'em.

That said, you sure building CyanogenMod 10.2 isn't preferable? Aside from getting the CyanogenMod features, you'll be building your own kernel from scratch too instead of using the prebuilt ones.

You can get the build instructions for all CyanogenMod-supported devices from the wiki. Those are the 10.1 instructions, and I bring it up-to-date for 10.2 with my instructions a couple pages back.

Incidentally-- a big plug for the wiki. It has all kinds of information for varying levels of CM people from beginners to advanced. Hopefully easy to read and digest, and as I said, walkthrough tutorials are available on installing and building cyanogenmod from source for every single device that is supported. Plus a ton of tips in the development section for people who are interested in the stuff covered in this thread.
[Nexus 7 Android Development] GeyerA:
Hello, thanks. I think I should have those "blobs" as my repo sync went always pretty well (except after adding some github commits where I then screw up my files). I decided to start with AOSP since this is all about learning. CM is absolutely having all features anybody needs but learning how to add one or another thing does also widen the horizon. I am already quite familiar with the apktool to de- and compile again but the xmls to add cherries is not too smooth.

I tried to add volume rocker wake to AOSP and ended up in a mess. I read the wiki pages (even took the print-outs home) but there is too many steps missing for me as a starter. However, I will try to return to make a zip which I can flash and then come back to your nice thread to challenge you with the next questions.

BTW, I also tried to follow to add the integrated superuser following Koush's explanations on his github but even the file which was specified could not be found by me.....

First, in a product makefile (like vendor/cm/config/common.mk), specify the following:
[Nexus 7 Android Development] fattire:
The blobs do NOT come in from a repo sync. The only way to get them is to pull them from a stock device or to install them using the installers from Google. The former method isn't set up yet in the device repository, so for all practical purposes, you should use the latter method.

You will NOT get an error if you don't have the vendor blobs. You also will NOT (I'm digging "NOT" in all caps for some reason) get a successful boot. The blobs are NOT an option. NOT.

I am totally biased here, but I think the build instructions on the wiki for cyanogenmod is really good. I wrote them, but still... they have been tested by thousands of people, so I'm pretty confident that they'll take you from zero to a full build. And I think you'll learn a lot from the process too :) I know I have.

It's good to see you're reading the wiki. If you are confused at times, please let me know where so i can try to clarify or fix things up... and feel free to stop by #cyanogenmod or #cyanogenmod-dev to chat with people who might be able to help you.
[Nexus 7 Android Development] GeyerA:
Hi, thanks for the explanation. No issue with capital NOT's as these make people understand. I will return to read the wiki and let you know. :)
[Nexus 7 Android Development] Archaic1881:
Doesn't work yet, while repo syncing I get 'Raise EOFError' in python stuff, will look at it later unless someone wants to shortcut me to the solution ?
[Nexus 7 Android Development] fattire:
Hmm. I don't quite know what that error means.. EOF usually means End Of File... but beyond that, unless you do a pastebin (www.pastebin.com) of the error and a few lines above it, I don't know what it means.. I can only suggest repo syncing in an hour or so. Sometimes things get gummed up over at github, though that usually involves a "can't download a file" type of error...
[Nexus 7 Android Development] Archaic1881:
Full error when i try to repo sync again

~/android/cm10.2 $ repo sync
Traceback (most recent call last):
File "/home/jb/android/cm10.2/.repo/repo/main.py", line 414, in <module>
_Main(sys.argv[1:])
File "/home/jb/android/cm10.2/.repo/repo/main.py", line 390, in _Main
result = repo._Run(argv) or 0
File "/home/jb/android/cm10.2/.repo/repo/main.py", line 138, in _Run
result = cmd.Execute(copts, cargs)
File "/home/jb/android/cm10.2/.repo/repo/subcmds/sync.py", line 588, in Execute
to_fetch.sort(key=self._fetch_times.Get, reverse=True)
File "/home/jb/android/cm10.2/.repo/repo/subcmds/sync.py", line 723, in Get
self._Load()
File "/home/jb/android/cm10.2/.repo/repo/subcmds/sync.py", line 743, in _Load
self._times = pickle.load(f)
File "/usr/lib/python2.7/pickle.py", line 1378, in load
return Unpickler(file).load()
File "/usr/lib/python2.7/pickle.py", line 858, in load
dispatch[key](self)
File "/usr/lib/python2.7/pickle.py", line 880, in load_eof
raise EOFError
EOFError

I'll try setting up the build machine again, I tried to build a cm9 build earlier, maybe something got ****ed up due to some changes there ?
[Nexus 7 Android Development] Whaleshark345:
this is not personal i found have no idea if it works or is legit just searched google http://www.androidfilehost.com/?fid=23060877489996865
[Nexus 7 Android Development] yukkio:
Thanks but the developer has removed the rom when i had downloaded 90%...
[Nexus 7 Android Development] Whaleshark345:
I downloaded it on my computer I might throw it up for download have not tested it and want some one else to before I do
[Nexus 7 Android Development] antp121:
Yeah because that was my personal build for me and my friend. I didn't really want it being shared everywhere lol...
[Nexus 7 Android Development] .torrented:
You could just make it private after you upload it or upload it to a private folder
[Nexus 7 Android Development] bmakk2055:
Is it possible for you to make a YouTube video (how to build CM10.2 from source m)
[Nexus 7 Android Development] yukkio:
Ok hehe could you share to us please?
[Nexus 7 Android Development] #define:
I have an almost fully working CM10.2 build for the grouper, and a booting build for my other device..

But I hardly use CM on the 7..

ғг๏๓ ҭђє ғเรђ!
[Nexus 7 Android Development] GeyerA:
Hi Fattire, I added all the blobs and can't believe, the ROM booted up without problems after compiling. Thanks a lot for the indications....:). BTW, I compiled an AOSP...
[Nexus 7 Android Development] Whaleshark345:
Please post
[Nexus 7 Android Development] fattire:
I really don't want to "support" the current builds...

Awesome! Nice job!

As for everyone begging for a build-- first off, I don't know about everyone else, but there's still some upstream stuff that's shaking out, so it's not even that amazing yet. :silly: And yeah, not everyone has the resources, bandwidth, and time to build-- but since it's still in a state of flux, what's the point of having it out there? If you want it THAT bad, learn to build it yourself.

As for the video-- really, the build instructions are going to be easier to follow at your own pace rather than having to squint at a screen, constantly pausing and such. We're all here to help you, and you can also find "live" help on IRC.

Look at how happy GeyerA is at his build :) It's worth it-- no cheating with PMed binaries and such (although obviously not much I can do to stop someone from doing it). Remember, this thread is about learning to build CM, not where to find unstable builds :)

In fact, insofar as any of the issues may be from my /device tree, I'd like people to help out. (I'm thinking maybe tonight I'll go back and add some of the CM patches to the kernel to get stuff like BFQ and things back in it.)

For example-- thanks to manuel for the first pull request! Which reverts this commit. I'm wondering why they turned off all this stuff. Anyone want to test it?