yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] DROCSID:
I'm still a student ATM, applied computer science, but I haven't the

Linux stuff yet (2nd year), will get that soon. But I download loads

of 1-2-3 Ebooks for Linux and need to do it with that. Registred on

a good Linux n00b forum, so I can ask my :facepalm:-questions over

there.

I still believe linux is getting more- and more the future. I work in an

Office and we get every day more questions about hosting and the

implementing of Linux-based and opensource stuff, besides Windows.
[Galaxy S I9000 Android Development] Gvdn:
Another noob question. Atm im at work and the sync is at 6.1 gb but i have finished work. Is it it possible to stop the download and continue at home or if i stop it will i have to redoanload everything at home?
[Galaxy S I9000 Android Development] kasper_h:
I never did any computer studies. I just learned by trial-and-error (and using my brain :)). It's not so hard actually. I started by following how-to's but only typed things I could understand. Then I used google if needed (for example for the usage context of certain git commands).

With regard to building for a gio. You can just use the same approach as written in the tutorial, you only need to change the galaxysmtd specific commands to the gio-specific commands. Device & kernel trees should be downloaded automatically. I'm currently building for two devices, my own and my brothers' (i9100) :)

If the phone already has CM10, you can pull the device specific files with a script which should be present in the device-specific tree. If you don't have it, you can change the script so it pulls the device-specific files from a CM10-zip-file.
[Galaxy S I9000 Android Development] DerTeufel1980:
That's funny. Same for me ;)

To see/learn how to apply changes yourself, you should take a look at the githubs from others.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] DROCSID:
How old are you guys bytheway? Hehe
[Galaxy S I9000 Android Development] Gvdn:
Amazing really. I find u guys incredibly talented as when i look at github it seems like chinese to me atm. Perhaps im doing it wrong but looking at that site i even have no clue how to navigate in it.

Time for some more reading ;)
[Galaxy S I9000 Android Development] elitevet:
This plays out be a heart touching thread to follow. :D Keep it coming, we might have a catharsis around the corner.

W/regards to learning using linux, try the Linux Documentation Project and various HOW-TO guides from the internet. I had my start with Fedora, they have lots of good reading.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] pmos69:
:/

Sorry guys. It's just engraved on my brain.

When your a certain age, editor=vi
[Galaxy S I9000 Android Development] pmos69:
Yes, it's possível to stop and then resume.
[Galaxy S I9000 Android Development] samoled:
Hmm... No external speaker sound with build...?

:confused:pmos69, I'd first like to thank you for taking the time to write this great walkthrough. This was my first attempt at a build, and after some trial and error (with the vi thing...) and discovering 'gedit' I was able to finish my very first rom today- all thanks to your walkthrough. You officially rock :). The only issue I've found with my build is still puzzling me- I have no external (rear?) speaker volume. At all. For nothing- music, notifications, ringtones.... nada. I have phone speaker volume when in calls, and that's it. o_O ??? I modified your instructions to build for my d2att, and it seemed to compile without any issues whatsoever. Any idea where I should start looking for a culprit?

#Edit

Seems the 8/25 Nightly for CM10 has knocked everybody's sound out. I've seen plenty of posts speculating that only the d2tmo drivers were included. Can I "repull" the drivers from my phone and recompile to solve this?
[Galaxy S I9000 Android Development] pmos69:
If you know what commit removed your drivers, you can revert it, as long as it doesn't break anything else.

I think the 0825 build only has one commit, related to SQL, so it doesn't seem the cause.
[Galaxy S I9000 Android Development] DROCSID:
CPU usage

In my own laptop I took out the 4GB I extra added because I needed in another laptop.

I kept looking at my usage for the daily things and it was just overrated to have 8 GB.

But at those moments I see a consequently HUGE CPU usage on my laptop. How do

you guys keep this working? I have had several times that my buildings just stopped

because the CPU was too busy.

Can i limit the usage for the building or? Just freshly reinstalled mine too.

Like this (when started it):
[Galaxy S I9000 Android Development] elitevet:
You want the build process utilize as much CPU as it can get, so it builds fast.

If you want a no hassle resource management between the build process and other tasks, use a VM, imho. There is a good reason why they make'em build servers.

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] kasper_h:
Agree, I just start a build when I know I don't need to use my pc for some time. Works fine that way :)
[Galaxy S I9000 Android Development] DROCSID:
This is just a 'spare' laptop, I don't do any other things when building

something. But I was just wondering if it's important to keep checking

this :). Thanks anyway you both
[Galaxy S I9000 Android Development] samoled:
Repulling drivers from a build where audio worked and then rebuilding didn't fix the issue. (Sigh).
[Galaxy S I9000 Android Development] pmos69:
It seems the next nightly will take care of the audio breakage.

Or you can sync now and try it...
[Galaxy S I9000 Android Development] kasper_h:
http://review.cyanogenmod.com/#/c/22151/ - audio: Unbreak ALL the things

Nice patch name & commit message :)
[Galaxy S I9000 Android Development] DROCSID:
Lol at the comment indeed ghehe...
[Galaxy S I9000 Android Development] Gvdn:
Ok think i finished my first build. Just to make sure is it possible to build for first time in 1 hour 10 minutes? I read it should be more then 4 hours for the first build?

Also i read on the Cyanogen wiki that u have some options to speed it up. Any chance to get some more explanation on that and how to do it?

Thanks again.
[Galaxy S I9000 Android Development] DROCSID:
No error messages? Did you test the build/.zip file?
[Galaxy S I9000 Android Development] Gvdn:
Euh not that i know of. And how do u test the build? U mean flash it? If so i wanted to have confirmation that its possible before i flash it.

Edit: F... it ill flash and see. Will let u know

Edit 2: Great everything is running as it should be. Lol its funny seing your name on all the apps in TB.

Once again huge thanks for replying to all the questions and helping out
[Galaxy S I9000 Android Development] DROCSID:
Great!

As for the time, yesterday build a fresh one in about 1:35 and now just made a new update,

started on 21:08 and finished on 21:17. But ok, it's a small one!

But works like a charm! :)
[Galaxy S I9000 Android Development] kasper_h:
:( :(

I need a new and faster pc
[Galaxy S I9000 Android Development] Gvdn:
Could u post the commands for doing just an update and the one for full new build?

And why make full new build?? any advantage over just update?
[Galaxy S I9000 Android Development] pmos69:
The commands are in the OP.

No advantage in rebuilding everything, unless there's something very wrong with your local repository.
[Galaxy S I9000 Android Development] Gvdn:
So this

cd ~/android/system

repo sync -j16

make installclean

find ./out/ -name 'build.prop' | xargs rm

find ./out/ -name 'cm_galaxysmtd-target_files-eng.*.zip' | xargs rm

will not delete everything but just update whats needed?

was abit worried with the "make installclean"

Also im getting this error but dunno if i should pay attention to it?

/bin/bash: xsltproc: command not found

/bin/bash: xsltproc: command not found
[Galaxy S I9000 Android Development] kasper_h:
make installclean will clean the most essential parts of the out directory.

I get the same error with xsltproc, but it seems not to cause any issue...

To get rid of it, you can run "sudo apt-get install xsltproc"
[Galaxy S I9000 Android Development] DROCSID:
It's just deleting some things from the previous build in the OUT folder.

This is working great for updates.

And I had those 2 error lines too, then googled and just ignored it

(https://www.google.nl/#hl=nl&output...cp.r_qf.&fp=dbfc17b7b0113551&biw=1366&bih=600)
[Galaxy S I9000 Android Development] pmos69:
Yup, "make installclean" and the other 2 comands just make the essential housecleaning before building with updates.

"make clobber" is the one to worry about. This one cleans everything and building will take a long time again.
[Galaxy S I9000 Android Development] Gvdn:
Just tried to build latest updates and i got stuck at an error telling me i needed to run make mrproper in .../aries folder.

Did that , retried and it build fine. Just thought id share this
[Galaxy S I9000 Android Development] pmos69:
Can happen when some config files are updated.
[Galaxy S I9000 Android Development] Gvdn:
Yeah all good just flashed latest and everything running great
[Galaxy S I9000 Android Development] fishears:
Anybody else got a badly aligned lockscreen with their build? I synced & built this morning & this is what I get (lock is too far to the right):
[Galaxy S I9000 Android Development] iyahman:
Sync and building this afternoon but same problem as you, the lock is in the right of the screen
[Galaxy S I9000 Android Development] fishears:
Glad to hear its not just me, thanks
[Galaxy S I9000 Android Development] groksteady:
Same is happening over in the official CM10 thread with today's nightly.

Off-topic, to fishears: I'm happy for you that you've stepped up to this level of things compiling yourself. But in case you missed it, DerTeufel put out a new HellyBean with a different partition layout, test builds in the last two days. It's working really well for me, although I never had insane lag or app storage problems.

sent from a telephonic device
[Galaxy S I9000 Android Development] fishears:
Thanks, I'll check it out.
[Galaxy S I9000 Android Development] Gvdn:
+1
[Galaxy S I9000 Android Development] DROCSID:
http://xdaforums.com/showthread.php?p=30772811
[Galaxy S I9000 Android Development] fishears:
Just FYI (and most people probably already did it) but you can simplify the "nightly sync & rebuild" process by putting the commands from the OP into a shell script somewhere in your PATH:

#!/bin/sh
#Script to update CM10 repo and build for changes
repo sync -j16
make installclean
find ./out/ -name 'build.prop' | xargs rm
find ./out/ -name 'cm_galaxysmtd-target_files-eng.*.zip' | xargs rm
. build/envsetup.sh && brunch galaxysmtd

I call mine "updatecm" so all I have to do to sync changes and rebuild is go to my source directory and type "updatecm"
[Galaxy S I9000 Android Development] DROCSID:
Thanks! Did it yesterday, but with App Runner (put a script in it),

clicked and grabbed some beer, working flawless :D.
[Galaxy S I9000 Android Development] fishears:
Great minds...

I've just found the commit that was stopping my stock kernel from working (old partition layout). I've been using semaphore til now.

Very happy now I have fully working nightlies with the old layout. I'm considering putting in changes like DerTeufel just made in HellyBean. Now I've seen the code it looks less scary to repartition..
[Galaxy S I9000 Android Development] pmos69:
fishears was bitten by the open-source-android bug.

:)

Nothing will stop him now.

I see countless hours of coding and debugging in your future...
[Galaxy S I9000 Android Development] fishears:
You could be right!

I've just seen than Stratosk's kernel source is up on Github so now I can make my own Semaphore 2.0.6 with the old partition layout. I love Open Source. This is freedom.

repo init -u git://github.com/stratosk/samsung-kernel-aries.git -b jellybean
[Galaxy S I9000 Android Development] DROCSID:
Why are you so sticking to the old partition layout Fishears? Ghehe
[Galaxy S I9000 Android Development] fishears:
Simple. My phone doesn't lag and I have over 1gb of /data used.

I have tried the new layout and it just isn't faster for my device. Plus I had to do without a bunch of apps because not everything can move to SD. And every time I saw that 1.5gb free on /system I did a silent scream :eek:

You should try my build - its in my sig
[Galaxy S I9000 Android Development] DROCSID:
Ah ok, clear! Haven't tried with many apps, I have an oldtimer NAND too ;).

But I never have more than 20 / 25 apps, so I don't feel that (I suppose).
[Galaxy S I9000 Android Development] kasper_h:
I also have script doing everything for me. Except repo sync :)

The "problem" is that I have a lot of local changes to the code (either picked cherries or home-cooked). So every-now-and-then I get conflicts after a repo sync. When using a script which will build immediately after repo syncing, you may miss these conflicts messages (building will continue anyway)...
[Galaxy S I9000 Android Development] Nick0703:
I have successfully made two CM10 builds for my Samsung Captivate. Everything work out right. But I'm getting one little error, it's something like "`src not found" I get that when I compile the source code.

Is that error normal?
[Galaxy S I9000 Android Development] fishears:
Normal for me.

Congrats on your builds!
[Galaxy S I9000 Android Development] Nick0703:
Oh OK, I thought that there was something wrong with my files again.:p And thank you! :D

Now I just need to know how to do some cherry pick....
[Galaxy S I9000 Android Development] kasper_h:
Same error her :)

This is a guide for cherry picking I made for cm9:

http://xdaforums.com/showthread.php?p=23715982

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] malcho:
Hi guys,

Is there anyone that can help me with this?

http://xdaforums.com/showpost.php?p=30813327&postcount=191
[Galaxy S I9000 Android Development] pmos69:
But why don't you just follow the guide?
[Galaxy S I9000 Android Development] malcho:
Source build cna.There is no guide.

Trying to integrate galaxys into build tree.
[Galaxy S I9000 Android Development] samoled:
Hangs on 'Starting apps.'

Just finished compiling on a monster machine (40 minutes), but it's hanging on 'Android is upgrading... Starting apps.' on boot. I've tried wiping Dalvik, formating cache, and full wipe, all to no avail. Ideas?
[Galaxy S I9000 Android Development] pmos69:
Oh. Ok.

Away from pc, and didn't get that part.
[Galaxy S I9000 Android Development] Nick0703:
Sweet!! Thanks, I'll check it out. And I'm loving the I9000 community!! You guys are way more helpful and nicer than the Captivate community! Thank you guys!!:)
[Galaxy S I9000 Android Development] kasper_h:
It's easier to build semaphore separately, as it is not made to fit into inline building. Theoretically it should be possible to use a prebuilt kernel during cm10 building, but I have no experience how to do that (you could look at the cm7 github source, as our phone was using prebuilt kernels back then).

By the way, you should not repo init a single github project. You should either use git clone in a separate folder or add semaphore as a remote branch to your existing kernel folder.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] fishears:
Yes, I don't think stratosk has manifest.xml - I could only clone it with git rather than repo sync it.

I'm building it separately. Only problem is that it looks like it builds an ICS kernel for me even though I've set the ramdisk to /jb_combo/

I'll have more of a look at it tonight - might just ask the man himself, he's a good guy.

PS custom backlight settings are finally in the tree
[Galaxy S I9000 Android Development] kasper_h:
If you clone the stratosk/semaphore kernel, you have to for "git checkout jellybean" because the default branch of this github is the ICS branch. Changing the jb_combo will not be enough to solve that....
[Galaxy S I9000 Android Development] fishears:
Thanks for the tip. I'll have more success that way. I'm now thinking of adding fast charge to the stock kernel...
[Galaxy S I9000 Android Development] samoled:
Both builds hang on boot

What would cause a build that compiles with no errors to hang on boot? Both build files, the 'Unofficial' and 'OTA' hang on the 'Android is updating...Starting apps.' section of the boot process. I've cleared everything out of the phone- system, cache, data, dalvik, format sd, format ext sd, and nothing changes. Is there something I'm missing, or did it actually compile incorrectly?
[Galaxy S I9000 Android Development] pmos69:
Besides sometimes taking a lot of time (don't know why), if you cleared data I see no reason.

If you didn't install gapps try doing so.
[Galaxy S I9000 Android Development] fishears:
How long have you waited? Mine usually looks like its stuck at "starting apps" but eventually it gets to the lockscreen.
[Galaxy S I9000 Android Development] pmos69:
Thinking in logical terms, I would even say it has to take longer after wipes because all app data has been cleared and has to be initialized on app/service startup.
[Galaxy S I9000 Android Development] samoled:
The longest I waited was around 5 minutes. I'll let it sit for 10 and see if it takes.

-Attempted boot at 9:23, it is now 9:43, and still hung at 'Starting apps.'... (sigh)
[Galaxy S I9000 Android Development] fishears:
Is this the friendliest thread or what?! There's so much help & support here & nobody says "you're a ****" or "Why the hell would you want to do that"

Thanks Guys
[Galaxy S I9000 Android Development] DROCSID:
I quite like it here. The CM10 thread is less amusing since RSCHENK and

Silky_dude are not posting there anymore ghehe.
[Galaxy S I9000 Android Development] samoled:
I second that notion. Everyone on here rocks. OK, so I resynced and rebuilt, and I found that in the >target folder there is now a >generic folder that wasn't there yesterday. I recall when first building at home last week that my >target folder had a >generic folder beside the >d2att folder as well, and those builds booted just fine. I wonder if yesterday's build did have an error? I'm going to try and flash this build and see if it gets past the 'Starting apps.' point... (crossing fingers)

------------

Flashed at 10:00, it is now 10:08....hanging at 'Starting apps.'.... (facepalm)... Is there a way to drill down into the zip to check to see if something was omitted? Or am I better off trying to blow away the build completely and start with a clean slate?
[Galaxy S I9000 Android Development] pmos69:
Hope you don't have to clobber your repository.

Have you tried installing/running the latest nightly first? Just grasping at straws here...
[Galaxy S I9000 Android Development] pmos69:
Think it's mainly due to the different "target audience".

If this was a "ROM thread" most of the posters would be "ROM shoppers", not people interested in the development.

(Even if xda is supposed to be a developers forum.)
[Galaxy S I9000 Android Development] iyahman:
So..thank you pmos69 for opening this thread, and all other who post answer or good questions :good:
[Galaxy S I9000 Android Development] rycus86:
Adding another device

Hi!

Now that we can build our awesome CM10 for our beloved SGS, how can we add an other device to the repo?

Which projects should I look for?

My second target would be the Tab 10.1v (p3), but I would be happy if someone could give me answers in general.

Thanks!
[Galaxy S I9000 Android Development] fishears:
Weird. I have the generic folder too but as you can see from my sig I have a successful build today. Does logcat give you any clue as to what's causing the freeze?
[Galaxy S I9000 Android Development] samoled:
Latest Nightly boots fine...

Latest Nightly booted without a hitch. Blow out my repository and start over? And do I need to clobber my build first?
[Galaxy S I9000 Android Development] kasper_h:
If a device is officially supported, you can follow the guide from OP, replacing galaxysmtd with the abbreviation for the specific device. If the device is not supported, you have to look for the device tree & kernel tree (start reading in the CM10 topic for the device you want to build). I'm building for i9100 as well. Take into account that you need about 10GB extra per device you're building for.

The generic folder should be there, it are the steps done which are device-independent. I also don't understand the problem of a non-running CM10 after an error-less compile. Best thing to start with is try to get a logcat to see what's causing the problem...

---------- Post added at 07:52 PM ---------- Previous post was at 07:52 PM ----------

I would only remove the /out folder and start a fresh build....
[Galaxy S I9000 Android Development] samoled:
-------

How would I go about getting a logcat if it won't boot?
[Galaxy S I9000 Android Development] fishears:
Connect USB & in a terminal on PC type "adb logcat"

You should see the logs as your phone tries to boot
[Galaxy S I9000 Android Development] samoled:
Dang...

No dice. Terminal only states '- waiting on device -' and never shows a log when boot hangs. Still hangs at 'Android is upgrading... Starting apps.'. (sigh)
[Galaxy S I9000 Android Development] fishears:
Sorry, you have to wait (I think) until you see kernel logo on phone before you start adb logcat
[Galaxy S I9000 Android Development] samoled:
Bugreport from CWM

I was able to do a bugreport in CWM Recovery, from what I read it should be the same thing, I've attached it for anyone that wants to see.
[Galaxy S I9000 Android Development] fishears:
What phone is that from? I don't recognize the blk devices. Plus its referring to an ICS build from 17/08/2012.

Not sure its any help. I think its an old recovery log. Can you connect to adb from recovery?
[Galaxy S I9000 Android Development] samoled:
Its from an ATT SGS 3, and no, I couldn't get adb to connect to it with the CM10 build installed. Neither in Recovery nor during boot. O_o???
[Galaxy S I9000 Android Development] Nick0703:
Try reinstalling the drivers and see if adb can get your device.
[Galaxy S I9000 Android Development] samoled:
O_o....???

Ok, I'm going to do my best to get a logcat, and in the meantime I removed the /out folder and started a new build. The machine is a monster (i7 3770 oc'd to 4.5, 16GB of 1866, and a 256GB SSD), so it compiles from scratch in about 40 minutes. Something makes me think my repo may be jacked, i synced with -j16 and have seen plenty of references to syncing with -j1 to resolve issues. If this new build doesn't take my plan of action is to clobber, and dump my repo w/ :

sudo gedit /etc/apt/sources.list.d/*.list

Then I'll start over. :(
[Galaxy S I9000 Android Development] pmos69:
-j1 is to bypass GitHub connection issues, but if you had them you would almost certainly get build errors.

Your tribulations are uncommon. That makes it hard for anyone to help more... :/
[Galaxy S I9000 Android Development] fishears:
That's a nice PC you have there.

You should probably make fixing your adb connect issue a priority. That's unlikely to be build related if you can get into recovery.
[Galaxy S I9000 Android Development] kasper_h:
BTW, how did you extract the necessary files if adb doesn't work?
[Galaxy S I9000 Android Development] DROCSID:
Exactly my thoughts, otherwise it won't even be possible to build one, or?
[Galaxy S I9000 Android Development] pmos69:
Maybe it doesn't work only with the new build.

If that's the case, kind of reminds my of the strange USB issues I had when I started customizing the kernel (as I wrote on the other thread) although the builds worked fine except for the usb .

It was a simple mess up done by menuconfig after all. No big deal.