yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Kasaweb:
For my first build 2 days ago i've got cm-10-20120806-UNOFFICIAL-galaxysmtd.zip, and today i've done a repo sync and rebuild and i'm still getting cm-10-20120806-UNOFFICIAL-galaxysmtd.zip

Have I missed something ?
[Galaxy S I9000 Android Development] mbarreto:
Works

Can't do last step, my mom is dead, all else works. Great tut, tks :good:
[Galaxy S I9000 Android Development] gangstaboy13:
Precisely the same as me!!
[Galaxy S I9000 Android Development] kasper_h:
You have to clean your /out directory, otherwise lots of files are reused and filename is not updated.

I use the following script to clean my out directory:

#!/bin/bash

out=~/android/system/out/target/product/galaxysmtd

#****************************************************************
## Clean environment:
make installclean
rm $out/system/build.prop
rm $out/obj/PACKAGING/target_files_intermediates/cm_galaxysmtd-target_files-eng.kasper.zip
rm $out/obj/PACKAGING/target_files_intermediates/cm_galaxysmtd-target_files-eng.kasper/SYSTEM/build.prop

Off course you have to adapt it if your username is not kasper :)
[Galaxy S I9000 Android Development] DROCSID:
Your mom is dead? Wow, heavy. Wish you all the best.
[Galaxy S I9000 Android Development] Kasaweb:
Thanks !

I think this should be added to the OP
[Galaxy S I9000 Android Development] pmos69:
Yes, it should. :o
[Galaxy S I9000 Android Development] CheesyNutz:
will this work for the captivate ?

could i just change the galaxymtd to captivatemtd ?
[Galaxy S I9000 Android Development] pmos69:
I guess so, since it's one of the supported devices...

But it's just a guess.
[Galaxy S I9000 Android Development] CheesyNutz:
vi ~/.bashrc

just brings on the / .bashrc in terminal ?
[Galaxy S I9000 Android Development] pmos69:
You're supposed to edit the ".barshrc" file (in your home directory). In this case using the vi editor.

But you can use any editor you want: gedit, nano, etc.
[Galaxy S I9000 Android Development] Kasaweb:
Time for some reporting after flashing : It works like a charm !

Some info :

android/system folder size after first repo sync : 14gb

rom builded in 2h30 on a "old" 2x2.5GHz / 4gb ram laptop. It generated an extra 15gb of data.

Thanks to all contributors for this awesome guide :D
[Galaxy S I9000 Android Development] pmos69:
Now if only the other guide also had no issues :-/

http://xdaforums.com/showthread.php?t=1815598
[Galaxy S I9000 Android Development] iyahman:
hi, I'm trying your guide but have a problem..

maybe someone have an idea? :confused:
[Galaxy S I9000 Android Development] pmos69:
Don't know.

Do a repo sync and 4.5 again.

Perhaps something didn't sync properly. (It happens sometimes).

The guide was completely tested from top to bottom.
[Galaxy S I9000 Android Development] msri3here:
I have the exact same problem..

then I added a local manifest xml file like this:

and now it syncing again (2105958 files!!!)

btw, can anyone tell me how big is the repository "CyanogenMod/android_kernel_samsung_aries"? and can I download it directly and use it?

I got an error while syncing at 405.45 MB and the sync started all over again :(

here is the error:

fatal: The remote end hung up unexpectedly405.45 MiB

fatal: early EOF

fatal: index-pack failed
[Galaxy S I9000 Android Development] gangstaboy13:
Make installclean doesnt work for me! Ill get an old version
[Galaxy S I9000 Android Development] kasper_h:
You can download the full contents of the kernel folder from github as a zip file (github.com/CyanogenMod/android_kernel_samsung_aries). Just paste the contents of the zip file in the correct folder and repo sync again.

Only make installclean is not enough, see my previous post on that....

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] pmos69:
... it's in the OP...
[Galaxy S I9000 Android Development] pmos69:
Communication issues will happen occasionally.

Sometimes from GitHub, sometimes from your ISP (using a lower -j setting might help), sometimes just because.
[Galaxy S I9000 Android Development] msri3here:
Thanks!!! downloading the zip now...

another question though,

the zip file I am trying to download is about 129 MB and the repository that I am trying to sync has downloaded over 400 MB. How come?
[Galaxy S I9000 Android Development] kasper_h:
That is what zip is for: compressing :):)

The original code is just text files, so it is easy to compress them (actually, I think repo will also compress the data sent over the internet connection, so that the network traffic is minimized).
[Galaxy S I9000 Android Development] msri3here:
well, my impression too was that repo will compress the data and thats why the question :P

maybe zip compression ration is more than that of repo...will get to know only when the download is complete :fingers-crossed:
[Galaxy S I9000 Android Development] msri3here:
No luck trying to copy the contents of the zip file to the location in the ~/android/system folder...

when I run repo sync, the system is trying to download the whole reporsitory again..

Someone who build CM10 successfully, can you please check and tell me the size of the .pack file located at: "~/android/system/.repo/projects/kernel/samsung/aries.git/objects/pack"?

and also if someone successfully downloaded and copied the files instead of syncing the repo, please guide me how to do it...I dont have a good speed to download over 400 MB of data again :(
[Galaxy S I9000 Android Development] pmos69:
Then this will not be easy for you.

The complete repository is about 14GB on disk.
[Galaxy S I9000 Android Development] elitevet:
Yeah, I gave up after 4 days of repeatedly trying to sync over 4.5M ADSL. Always an error at some point. Git should switch to torrent for first time sync or something...

Really frustrating :'(

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] pmos69:
I know what you mean.

One suggestion for people who get problems like that: do the syncs with -j1

It takes longer but it gets around some ISPs behaving badly when handling repos with multiple threads.

I've witnessed this first hand.
[Galaxy S I9000 Android Development] shane87:
Yeah, anyone with repo syncing problems, try running repo sync -j1. I have 3M ADSL, and I had no problem syncing the cm10 repos. My only issue was that my build box is x86, not x64. Here in a few days, though, I'll be setting up on an x64 box!
[Galaxy S I9000 Android Development] kasper_h:
I was wondering whether people here all run ubuntu 64bit? I run it in 32 bit and have some problems with compiling JB. I don't know whether it's due to 32 bit or to something else...
[Galaxy S I9000 Android Development] DROCSID:
I run Linux Mint (debian) 64-bits.
[Galaxy S I9000 Android Development] elitevet:
It's been suggested earlier in this thread you have to compile on a 64-bit OS.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] pmos69:
That's the info I got from a few places regarding compiling JB after investigating a little.

I updated the OP with that.

Anyway, if someone manages to do it in 32bit I'll look into it.

All my tests were in 64bit.
[Galaxy S I9000 Android Development] kasper_h:
I know 64bit is recommended. I tried adapting the buildscript, but I really can't get it to build on x86...
[Galaxy S I9000 Android Development] stbenz:
See https://groups.google.com/forum/?fromgroups#!topic/android-building/61CoTjyGg_o[1-25]

Other than previous versions, Jelly Bean requires a 64-bit host as the included GCC is a 64-bit binary.
[Galaxy S I9000 Android Development] kasper_h:
Thanks. I just download 64 bit ubuntu, backupped all important data and will upgrade tomorrow :)

BTW, a question about the OP. It says to add:

PATH=$PATH:/home/YOUR-USERNAME/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

But doesn't that mean the "old" 4.4.3 toolchain is used in stead of the newer 4.6 toolchain?
[Galaxy S I9000 Android Development] pmos69:
Seems logic.

Didn't really give it much thought, to be honest.
[Galaxy S I9000 Android Development] elitevet:
Are you into retro or something? I could donate you some to help with buying a proper cpu, pm me ;)

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] kasper_h:
I have a 64bit computer, so for upgrading I only need to upgrade the OS (which involves a complete wipe). I already backupped everything and installed Ubuntu 64bit, now I only need to reinstall the necessary software again :)
[Galaxy S I9000 Android Development] elitevet:
at last... the sync gone through and teh build finished successfully :)

I actually managed to sync with 'repo sync -j8' and not -j1 over 4Mbps ADSL

It seems like github.com has some network/load issues, or maybe it's the ISP.

So if you got hungups while syncing don't despair, try again and eventually it'll go through.

Built in 1:23:14 on (VMWare) 4xCore i7 930@3.74GHz VM with 2GB RAM

Linux cyanobuilder 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[Galaxy S I9000 Android Development] msri3here:
I started the sync again last night and it went through successfully :victory:. PHEW!!! Finally...

building now :fingers-crossed:

EDIT: Build completed successfully and everything working perfectly. YIPPIEEEE :D :D
[Galaxy S I9000 Android Development] CheesyNutz:
The download file appears to be corrupted. Please refer

to the Troubleshooting section of the Installation

Instructions on the download page for more information.

Please do not attempt to install this archive file.

ive downloaded the java file 3 times O.o
[Galaxy S I9000 Android Development] albertobom:
So it's not recommended to install try in a 32 bits system?

Please ignore.
[Galaxy S I9000 Android Development] kasper_h:
Compiles well now I have 64 bit ubuntu :)

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] pmos69:
Was there any doubt? ;)
[Galaxy S I9000 Android Development] kasper_h:
Not really :)

I did things a bit easier than in op.

-I installed openjdk6 with the other packages

-I didn't change any of the usb code stuff, adb worked out-of-the-box

-I didn't add any toolchain info to the .bashrc file

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] elitevet:
Hey guys, anybody tried to build today?

synced at 10:50 IDT, build broken with:

arget thumb C++: libEGL <= frameworks/native/opengl/libs/EGL/egl_object.cpp
frameworks/native/libs/ui/GraphicBufferAllocator.cpp: In member function 'android::status_t android::GraphicBufferAllocator::alloc(uint32_t, uint32_t, android::PixelFormat, int, const native_handle_t**, int32_t*)':
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:134:5: error: no return statement in function returning non-void [-Werror=return-type]
frameworks/native/libs/ui/GraphicBufferAllocator.cpp: At global scope:
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:135:5: error: expected ')' before '(' token
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:135:5: error: expected ')' before '(' token
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:135:5: error: expected ')' before '(' token
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:138:5: error: expected unqualified-id before 'if'
frameworks/native/libs/ui/GraphicBufferAllocator.cpp:178:2: error: expected '}' at end of input
cc1plus: some warnings being treated as errors

make: *** [/home/cyanobacter/android/output/system/target/product/galaxysmtd/obj/SHARED_LIBRARIES/libui_intermediates/GraphicBufferAllocator.o] Error 1
make: *** Waiting for unfinished jobs....
cyanobacter@cyanobuilder:~/android/system$

Any ideas?
[Galaxy S I9000 Android Development] kasper_h:
Are there about recent merged patches for /frameworks/native ?

I can't check due to extremely slow internet...

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] elitevet:
There's been a commit regarding Tiled rendering, there are quite some for FRAMEWORKS_BASE (looking at BBQ Log) and they keep coming. The change in partitioning pawitp promised is partially (i guess) commited right now. I guess I synced in the middle... will wait for the merges to pause and try to sync again...
[Galaxy S I9000 Android Development] beetfarmer:
From what I could see in the code, line 130 should have a "{". But C++ isn't my strong point, you'd need someone more knowledgeable to confirm this :)

Edit: Or maybe line 134 shouldn't have a "}"?
[Galaxy S I9000 Android Development] pmos69:
Commits are coming down heavy. Some broke things. Some breakage has already been fixed.

It happens. Wait a bit and it will be fixed. (Or search gerrit to see what's coming up).

It seems the development speed has picked up quite a bit. Maybe because of the focus shift from cm9 to cm10.

I'm on vacation with the Ms and kids, so I'm not doing a lot of compiling at this time :)
[Galaxy S I9000 Android Development] kasper_h:
Enjoy your holidays :)

I feel like waiting a bit with doing another repo sync as well now that so much gets merged...

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] elitevet:
Yes, indeed a spare } there :)

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] gangstaboy13:
Hey man what kind of linux do you have?

kind of a cyanogenmod linux or so?

And what files do you have under android/system/vendor?
[Galaxy S I9000 Android Development] DROCSID:
Lol, CyanogenMod Linux :p.

Think Debian
[Galaxy S I9000 Android Development] fishears:
Has anyone done a recent built with http://review.cyanogenmod.com/#/c/21300/ reverted?

I'm just pulling the repo in (the long waity part) and plan to restore /system and /data to their rightful places and then keep up to date with the rest of the code.

I use Fedora & its been awhile (Gingerbread) since I had a build env set up and so I'm hoping I get all the right packages ;)
[Galaxy S I9000 Android Development] elitevet:
Ubuntu. Look few pages back, I posted uname -a output. Why does it matter, anyway?

.. /vendor/cm obviously, again, why do you ask?

sent from CM10 powered SGS

---------- Post added at 01:04 PM ---------- Previous post was at 12:55 PM ----------

Fishears, you've really took it personal from pawitp, huh? LOL, man, I really don't get what your problem with the new partitioning schema is. This single change should be declared Commit of the year, it gave our phone another year or two.

Wishing you most of luck building your own version. :)

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] fishears:
:D

Thanks. I guess I just already have a fast enough phone without losing data space..

I've cooled-off a lot since yesterday ;)
[Galaxy S I9000 Android Development] elitevet:
Glad to hear you're cool. Life is better that way :)

OT: Just to educate myself, is there any particular reason you're not considering the "move to SDCard" option for your apps?

Oh, and back on topic: resynced an hour ago and, voila, it builds again sweetly:

151225036 Aug 18 14:12 cm-10-20120818-UNOFFICIAL-galaxysmtd.zip
[Galaxy S I9000 Android Development] fishears:
I don't particularly have anything against that if I had really run out of space. But there's a big fat 1.5gb waste on /system ... If I push apps to /system/app to use that space I'll have to do that every time I flash a new nightly. Its hassle
[Galaxy S I9000 Android Development] elitevet:
I am sure Google will fill that space in a year or so :)
[Galaxy S I9000 Android Development] pmos69:
Exactly.

Besides the slow movinand issue, which is a present one, the size of the system partition was probably going to start being an issue in the next versions of android.

This seems a nice compromise.

Other custom partitioning schemes could be implemented, but they would break compatibility and would involve changes in recovery, etc.

When btrfs becomes stable that will probably also inject some more performance options and minimize the slow movinand impact by reducing real io.

In the mean time, its probably better to cut the developers a break and let them concentrate on their main job...
[Galaxy S I9000 Android Development] pmos69:
Man, you sure are passionate about this phone :)
[Galaxy S I9000 Android Development] kasper_h:
Although you can indeed build your own cm10 reverting this change, I would be careful about future updates to the source code, which may cause conflicts...

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] DROCSID:
Haven't looked at it yet, but did someone picked that FM radio

to implement? Read something about it somewhere, don't know

where.
[Galaxy S I9000 Android Development] fishears:
About everything :)
[Galaxy S I9000 Android Development] elitevet:
IIRC, there were a couple of commits dealing with audio routing for the FM. I gave that up long time ago, the need to connect earphones drives me crazy. I use TuneIn, since I have a 2GB data plan. The app is just brilliant. The only downside (if you can call it that) is the couple of seconds delay from the actual radio broadcast.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] fishears:
Nearly there. All synced and crappy-commit reverted. Just need to downgrade my java to 1.6 then its build time. Have to wait til tomorrow now though because I'm a little too toasted ATM...
[Galaxy S I9000 Android Development] Mike_77:
So if I wanted to use propietary files from github.com/TheMuppets/ How would I go about doing that?
[Galaxy S I9000 Android Development] kasper_h:
Can you be a but more specific on what you would like to do?
[Galaxy S I9000 Android Development] fishears:
repo init -u git://github.com/TheMuppets/android.git -b jellybean
[Galaxy S I9000 Android Development] kasper_h:
For a single github project, you usually don't need to create a fresh repo. Sometimes you can add it to the local_manifest of your existing repo. But that depends on what you want to do with it :)
[Galaxy S I9000 Android Development] Mike_77:
Ahh.. well I'm building for the Epic (and yes, I know this isn't the right forum, but the guide has been helpful, and there has been a discussion here, so.... lol) but I have to use TheMuppets proprietary files with the rest of the CM10 stuff from Cyanogenmod github.. or libsurfaceflinger doesn't work.. so trying to figure out how to incorporate them :)
[Galaxy S I9000 Android Development] kasper_h:
I think it's best to go to /android/system/vendor/samsung and then do

$ git clone git://github.com/TheMuppets/proprietary_vendor_samsung.git

This will pull the whole set of proprietary files from the github account to your local pc.
[Galaxy S I9000 Android Development] Mike_77:
I'll give that a shot and let you know. Thank you!
[Galaxy S I9000 Android Development] fishears:
Built and flashed!

Thanks a lot for this thread. I've now got a current CM10 with the original partition layout. :feelingprettyfine:
[Galaxy S I9000 Android Development] pmos69:
The beauty of open source.

But this thread is just a small push.

All the real work is done by Google 1st, and the CM team 2nd.

Glad you made it.

Now you can investigate further and implement a /datadata partitioning if you want...
[Galaxy S I9000 Android Development] elitevet:
Positive vibration, yo! :)

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] groksteady:
congratulations -- that's pretty awesome, and the best possible solution/way out of your jam. glad that's worked for you.
[Galaxy S I9000 Android Development] fishears:
Thank you. It's a good learning experience too. Plus it stops me *****ing and whining in the CM10 thread :p

Everybody's happy.
[Galaxy S I9000 Android Development] dman3285:
Just an FYI. 12.04 is NOT the required system. You can use 10.04. I've been compiling and building JB on 10.04 for weeks flawlessly. please don't give people the impression 12.04 is the only way to build JB. Its is by far. not the only way. Thanks.
[Galaxy S I9000 Android Development] pmos69:
As I cannot guarantee that the guide will work in any/all 64bit Linux distributions, or indicate packages for all of them, I simply chose a specific distribution and version.

If you follow the guide, things will work. For sure. (Everything is tested).

That doesn't mean things won't work with other Linux distributions or versions. In fact it should work in any fairly recent 64bit distro, as long as you get the correct packages.

Same thing about Java.
[Galaxy S I9000 Android Development] fishears:
Absolutely. It works with Fedora 17, but it takes some effort to find the correct rpm packages & installing JDK 6 is quite a hassle ;)

The guide is correct to state which OS it was written for.
[Galaxy S I9000 Android Development] .:Crack:.:
Haha, Mr. Linux noobie is doing things wrong i guess :D

step 3.7 doesn't work for me....
[Galaxy S I9000 Android Development] pmos69:
That's just invoking one of the SDK tools.

Check previous steps...
[Galaxy S I9000 Android Development] .:Crack:.:
Yeah I figured. Turns out i wasn't root while typing "android". Works fine with su.
[Galaxy S I9000 Android Development] fishears:
You shouldn't need root for that. It should be in user home directory.
[Galaxy S I9000 Android Development] pmos69:
Maybe he added the SDK to the path of the root user by mistake.

Either way he got there...
[Galaxy S I9000 Android Development] fishears:
Yes, but it might cause other issues if the SDK is installed as root. Probably best to remove & reinstall as user.
[Galaxy S I9000 Android Development] pmos69:
I'm sure he'll let us know how it goes :)
[Galaxy S I9000 Android Development] .:Crack:.:
Haha, crap... How big is the repo? I had to less space on my VM and have to make a new one... Is 16GB sufficient?
[Galaxy S I9000 Android Development] pmos69:
Not if you want to build anything at the end.

http://xdaforums.com/showpost.php?p=29966856&postcount=88

Guess I'll update the OP with space requirements to avoid "surprises"...
[Galaxy S I9000 Android Development] elitevet:
You have to have 14G just for the repo, plus about 10 for Ubuntu + not less than 5G if you use CCACHE (and better make it a separate vmdk on a separate host disk) + linux swap, that depends on how much RAM you've got + about 10G for the build output... I made two vmdks 72 and 80 GB.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] fishears:
Yup, the best plan is to install Linux as your main OS. Join the fun for real ;)
[Galaxy S I9000 Android Development] elitevet:
Nope, I haven't said it is the main OS on my rig. I run the build machine inside a VM that has 4 cpu cores and 4 GB of RAM.

The two vmdk files are located on different disks of the host machine, one of them on a RAID 0 partition, this is the fast disk for swap and ccache and the other one is on the regular SATA2 disk for system and repo.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] fishears:
Yeah I got that :D

It really a suggestion to .:Crack:. :laugh: I like to do my bit to promote linux to the World
[Galaxy S I9000 Android Development] kasper_h:
My experience is that build time dropped significantly after switching to a standalone ubuntu (but my laptop is not that quick anyway).

My linux disk is 62GB of which 42GB is used (for ubuntu 64bit + needed packages + some extras + git repo + build output). Swap is an additional 3GB.
[Galaxy S I9000 Android Development] DROCSID:
I have an Aspire 5551g with 6GB and Samsung SSD. Does anyone else experience better build times with a SSD? Haven't tried without a SSD, therefor my question, always did that on a desktop pc.

The Samsung SSD are like lightfast but I was wondering if it will have some effort on the building proces. Or is that bollocks? I have only 1 partition (+

small swap) on Linux Mint.
[Galaxy S I9000 Android Development] elitevet:
Do you mind to quantify? I build a full build in about 1:20 and a typical two days worth of updates build in about 20 minutes.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] fishears:
Of course, all results are subjective depending on each persons hardware. But it stands to reason that any OS will perform faster when not virtualized. Having said that, your computer runs the VM Linux fast enough as far as I can see :D No reason to change as long as you're happy. Happiness is everything!