• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [GUIDE] Setting Up your Android Environment

marc12868 said:
A 20GB hdd should be fine for this right? I'm just going to use my 360's hdd (since its a 2.5 ide) if it is. And I mean for building ICS.
Click to expand...

I'm pretty sure 20GB isn't enough. I think you need about 30GB, maybe more. You probably need about 3GB of ram as well. I have 3 GB and I have had builds fail because the process get killed because it runs out of memory.
 
wsimon said:
I'm pretty sure 20GB isn't enough. I think you need about 30GB, maybe more. You probably need about 3GB of ram as well. I have 3 GB and I have had builds fail because the process get killed because it runs out of memory.
Click to expand...

Hmm then I guess I'll just have to partition my main 250GB HDD, but I only have 2gb of ram :eek:
 
marc12868 said:
Hmm then I guess I'll just have to partition my main 250GB HDD, but I only have 2gb of ram :eek:
Click to expand...

If you use wubi, then you don't have to partition your hd. It works well for me. But 2GB or ram might not make it. I am going to buy more ram so I can build this beast consistently without worrying about closing everything down while it builds.
 
wsimon said:
If you use wubi, then you don't have to partition your hd. It works well for me. But 2GB or ram might not make it. I am going to buy more ram so I can build this beast consistently without worrying about closing everything down while it builds.
Click to expand...

Hmmm maybe I'll get a C2D and 4Gb of ram so I can do more :D
 
marc12868 said:
Hmm then I guess I'll just have to partition my main 250GB HDD, but I only have 2gb of ram :eek:
Click to expand...

Don't waste your time with it unless you have more RAM and the CPU to back it. The key to development is having the hardware to handle recompiling after you make changes! konspiracy's system is a very good example of that

http://androidforums.com/triumph-al...uing-triumph-ics-development.html#post3850273

Seriously you don't want to be wasting countless hours on compiling when you forgot to close one tag that brings your code to a halt and have to recompile and it take 3-4 hours to build just because you forgot a close a bracket >
 
g60madman said:
Don't waste your time with it unless you have more RAM and the CPU to back it. The key to development is having the hardware to handle recompiling after you make changes! konspiracy's system is a very good example of that

http://androidforums.com/triumph-al...uing-triumph-ics-development.html#post3850273

Seriously you don't want to be wasting countless hours on compiling when you forgot to close one tag that brings your code to a halt and have to recompile and it take 3-4 hours to build just because you forgot a close a bracket >
Click to expand...

Hmmm... yea thats what i figured :/ I guess I'll just have to wait like everyone else...
 
wsimon said:
I'm pretty sure 20GB isn't enough. I think you need about 30GB, maybe more. You probably need about 3GB of ram as well. I have 3 GB and I have had builds fail because the process get killed because it runs out of memory.
Click to expand...

I think 30 GB is needed, there's additional dev tools needed too. And going forward who knows what kinds of updates they keep adding. I wish they would trim off some of the older branches like Froyo though.

marc12868 said:
Hmm then I guess I'll just have to partition my main 250GB HDD, but I only have 2gb of ram :eek:
Click to expand...

I've used a trick by exporting 'USE_CCACHE=1' env variable can speed up recompiling small changes. The first compile will take a long time, but later ones will be shorter. Give it a try, doesn't hurt, except your time :) but it's a good learning experience.
 
Whyzor said:
I think 30 GB is needed, there's additional dev tools needed too. And going forward who knows what kinds of updates they keep adding. I wish they would trim off some of the older branches like Froyo though.



I've used a trick by exporting 'USE_CCACHE=1' env variable can speed up recompiling small changes. The first compile will take a long time, but later ones will be shorter. Give it a try, doesn't hurt, except your time :) but it's a good learning experience.
Click to expand...

Ok thanks I guess I'll get ubuntu on my main hdd and see if I can get anything to build :D
 
Can someone help me please..? I have tried installing Ubuntu on my Toshiba Satellite L755D-S5204 but after it reboots and I select Ubuntu as my boot option it goes to a blank screen. The hard drive light stays flashing like it's doing something, but it just stays on a blank screen. Any suggestions...? I would like to help in the ICS development but have been stuck trying to figure out why Ubuntu won't boot properly.

Edit: Could I use Eclipse instead...? And if so, does anyone know how to build with it...? Thanks in Advance.
 
I tried ubuntu server and it seems like it will work, but now I don't know if I want to install it because it wants to partition my hard drive and I would hate to lose all my files and windows7. Any other ideas...?
 
After about an hour of searching I found out how to repartition my HD without data loss, but now I can't figure out how to install Ubuntu server to the partition I designated for it. It's looking like by the time I get it set up, you all will be done developing ICS.
 
evanrobinson85 said:
After about an hour of searching I found out how to repartition my HD without data loss, but now I can't figure out how to install Ubuntu server to the partition I designated for it. It's looking like by the time I get it set up, you all will be done developing ICS.
Click to expand...

I'm willing to bet we won't. ICS is difficult to get working, and even with a team now, it'll take weeks if not months to get it polished & usable.
 
g60madman said:
20GB should be OK, it's not a lot of space and it's border line depending on what all you add to the build but the key is your computer speed. I have a core duo 1.6Ghz with 4GB of ram and an SSD drive. However even though it boots in 3 seconds because of the SSD it's just simply a bear taking 3-4 hours per build. It's useless for me even to build right now. So if you have a screaming system Xeon, i5, i7 or AMD that's similar in architecture then you should be fine.

It just doesn't help to write code, make a few mistakes and have the build fail at 2 1/2 hours to have to go back and make edits and try again. Right now I am not helping on the project but hopefully by next week when I get my Quad Core Xeon I can pick up where I left off. Again compiling source can be a fun project but if you don't have the quality hardware it makes it very difficult to compile and very very time consuming.
Click to expand...

It sounds as if you have a Macbook Air, but I am probably wrong. :P Anyway, I sorta agree with you on your statement about "computer speed." I have a 2.16 C2D Macbook w/ 4GB RAM. It doesn't take too long to build (I just started building again, I got so fed up with repo issues due to Issac's repo being outta date. :( )
I'll time mine and see, but at a MINIMUM you should have a dual-core or higher. Single cores (no matter the GHz) aren't going to cut it.
 
could i use eclipse to build my environment...? ubuntu just does not want to install properly on my laptop. i even tried kubuntu and ubuntu server
 
evanrobinson85 said:
could i use eclipse to build my environment...? ubuntu just does not want to install properly on my laptop. i even tried kubuntu and ubuntu server
Click to expand...

No... Eclipse is just an IDE. You need a linux based operating system. If you are going to use anything but ubuntu you would probably need previous experience with it as the directions will be different.

I think your best bet would be to figure out why Ubuntu is not working properly for you.
 
wsimon said:
No... Eclipse is just an IDE. You need a linux based operating system. If you are going to use anything but ubuntu you would probably need previous experience with it as the directions will be different.

I think your best bet would be to figure out why Ubuntu is not working properly for you.
Click to expand...

The easiest thing to do is if you have an extra 100 Gb or so on your HDD, don't even partition prior to install....just put the Ubuntu 10.04 disc in, and it'll partition it for you to run along Windows....I was having trouble because I would partition space for Ubuntu and with those Linux distros, they wanna do the work themselves! It took me about 4 tries before I just let it do its thing...

Hope it helped!
:cool:
 
Big thanks for the guide, I have not built ICS for my Triumph yet but this guide has helped me build CM7 on 2 other devices. The guides for the other devices had a few mistakes or directions had been confusing so I was able to look at this guide and extrapolate what I was not getting from the other sources. Otherwise prior to looking at this guide had built ICS for the Galaxy Nexus as a practice run as the guide for building was very clear and simple to understand? I have been running Ubuntu 10.4 in Virtualbox, gave it 100MB of space 2g of ram and 2 cores and can build CM7 in 2 & 1/2 hours. ICS for Galaxy Nexus took about 4 hours. For anyone who is interested the Galaxy Nexus directions are below, which if anything can be used as a guide for setting up an environment running inside a virtual machine. Now I
 
ok so im at the point where i put in this code ./android update sdk and the screen never comes up. i am using ubuntu 10.xx server. is there another command i can put in to force start it.? please help
 
evanrobinson85 said:
ok so im at the point where i put in this code ./android update sdk and the screen never comes up. i am using ubuntu 10.xx server. is there another command i can put in to force start it.? please help
Click to expand...

That step is to be able to use 'adb', which is not needed to build on the machine. I got the same error but can build fine on that machine. (I use adb in windows instead).
 
I think I've got everything working in a VirtualBox VM running Ubuntu 10.04 x64 from a Windows 7 host, but I am getting the following error trying to build:
Code: 
No private recovery resources for TARGET_DEVICE triumph
Symlink: out/target/product/triumph/system/bin/lsof -> toolbox
make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/triumph/system/app/RomManager.apk'.  Stop.

edit: solved:
cd vendor/cm && ./get-prebuilts

edit2: Yup, rocking and rolling, have a CM9 rom built from Mantera's source from virtual machine. Great thread, thanks.
 
I'm trying to sync my repo with Mantera's source and I got an error on at least one of the groups.
Scratch that. My sync exited out due to fetch errors. What does this mean for me and would I be able to sync parts, or do I need to sync the whole thing?:confused:

And also, is there a log that I can refer to to see what may need refetching?
 
You must log in or register to reply here.
Back
Top Bottom