• 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

Well I tried to install Ubuntu on my HP Pavillon g7 labtop. Things didn't go well I got a black screen with white lines. :( No building for me.
 
PerkinsII said:
They have a netbook version of ubuntu you could try that
Click to expand...

UNR (Ubuntu Netbook Remix) is now antequated, the repos are available via Ubuntu's software channels.
Or I should say they *were* available. Since 11.04 they've been trying to streamline the experience for all users. My netbook's currently running 11.10 but it doesn't have the capacity to build without stalling the whole setup.
When my desktop is up and running again I'll be building from that (also running Ubuntu)

If Ubuntu won't install on your computer, there's always Xubuntu which uses a different UI so that it plays well with hardware that may not be able to run Unity or Ubuntu Classic. There's a lot of iterations, you'd just need to check which one would run.
Problem is, then you'd have to change the repos to whatever version of 'nux you're running.
 
@g60madman - I finally took a look at your guide. I have two comments.

1. You can change your section 4 to the following:

4. Pulling Proprietary Files Mantera Build
The proprietary files are now included in Mantera's repo. Run the following commands/script to copy them to their final locations:

# cd device/motorola/triumph
# ./extract-files.sh

2. In your Section 5. "Time to Build". The command that I use is what Isaac lists in the cm7 thread which combines all of your commands into 1 line:

Code: 
. build/envsetup.sh && brunch triumph

Also, if you use the command above, the final name of the file will be a Zip file that has all of the packages already optimized and zip-aligned. It is currently named

update-cm-9.0.0-RC0-Triumph-KANG-signed.zip
 
mantera said:
@g60madman - I finally took a look at your guide. I have two comments.

1. You can change your section 4 to the following:

4. Pulling Proprietary Files Mantera Build
The proprietary files are now included in Mantera's repo. Run the following commands/script to copy them to their final locations:

# cd device/motorola/triumph
# ./extract-files.sh

2. In your Section 5. "Time to Build". The command that I use is what Isaac lists in the cm7 thread which combines all of your commands into 1 line:

Code: 
. build/envsetup.sh && brunch triumph

Also, if you use the command above, the final name of the file will be a Zip file that has all of the packages already optimized and zip-aligned. It is currently named

update-cm-9.0.0-RC0-Triumph-KANG-signed.zip
Click to expand...

Awesome....been doing some research, but I thought that was just for CM7...Learning every day!
:)
 
Whyzor said:
To save any new devs the hassle of flashing back to Froyo ROM just to pick up the proprietary blobs. You can grab them here and just untar them into /vendor/motorola/triumph/proprietary, then run the extract-files.sh as usual (it'll just error on the adb pull part).

http://androidforums.com/triumph-al...7-source-development-area-11.html#post3634312
Click to expand...

Question:
When i did get the error on the adb pull
(./extract-files.sh: 301: vendor/__VENDOR__/DEVICE__/proprietary/libqueue/so:/system/lib/so: notfound)
I tried to lunch and mantera's build wasn't showing up....howscome???
:confused:
 
bradhoschar said:
Question:
When i did get the error on the adb pull
(./extract-files.sh: 301: vendor/__VENDOR__/DEVICE__/proprietary/libqueue/so:/system/lib/so: notfound)
I tried to lunch and mantera's build wasn't showing up....howscome???
:confused:
Click to expand...

do a repo sync

After it is done resyncing again, do

cd device/motorola/triumph
./extract-files.sh

After that is all done, do

cd ~
~/CM9_SOURCE/vendor/cm/get-prebuilts

cd ~/CM9_SOURCE

do another repo sync just to make sure nothing's changed since you last did a sync.

finally do

. build/envsetup.sh && brunch triumph

Notice there's a space between the . and build in the command above. You could also type out

source build/envsetup.sh && brunch triumph

and see where that takes you.
 
mantera said:
@g60madman - I finally took a look at your guide. I have two comments.

1. You can change your section 4 to the following:

4. Pulling Proprietary Files Mantera Build
The proprietary files are now included in Mantera's repo. Run the following commands/script to copy them to their final locations:

# cd device/motorola/triumph
# ./extract-files.sh

2. In your Section 5. "Time to Build". The command that I use is what Isaac lists in the cm7 thread which combines all of your commands into 1 line:

Code: 
. build/envsetup.sh && brunch triumph

Also, if you use the command above, the final name of the file will be a Zip file that has all of the packages already optimized and zip-aligned. It is currently named

update-cm-9.0.0-RC0-Triumph-KANG-signed.zip
Click to expand...

One more thing I just noticed, your guide is missing the step to get the cm prebuilts:

cd ~
~/CM9_SOURCE/vendor/cm/get-prebuilts

cd ~/CM9_SOURCE
 
So what would be the best tutorial to use out there? I've read a bunch and see the one linked to seems incomplete.

Thanks for all the assistance guys.

-Bidz
 
bidzer said:
So what would be the best tutorial to use out there? I've read a bunch and see the one linked to seems incomplete.

Thanks for all the assistance guys.

-Bidz
Click to expand...

I would use the guide in the original post. It is complete and is continually being modified as changes are made and mistakes found. I got through it without a problem.
 
Just went through this guide, thanks for the writeup, a few suggested corrections:

1. use apt-get lib32readline-gplv2-dev instead of outdated lib32readline5-dev
2. add-apt-repository "deb http://archive.canonical.com/ oneiric partner" since most people following guide will have more updated Ubuntu 11.10. or mention link to other older ubuntu versions here.
3. tar zxvf android-sdk_r16-linux.tgz (without the - in front)
4. $HOME/android-sdk-linux/platform-tools does not exist, maybe because this step fails:

Code: 
~/android-sdk-linux/tools$ sudo ./android update sdk
Exception in thread "main" org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.createDisplay(Unknown Source)
        at org.eclipse.swt.widgets.Display.create(Unknown Source)
        at org.eclipse.swt.graphics.Device.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Display.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Display.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Display.getDefault(Unknown Source)
        at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
        at com.android.sdkuilib.internal.repository.sdkman2.SdkUpdaterWindowImpl2.createShell(SdkUpdaterWindowImpl2.java:175)
        at com.android.sdkuilib.internal.repository.sdkman2.SdkUpdaterWindowImpl2.open(SdkUpdaterWindowImpl2.java:147)
        at com.android.sdkuilib.repository.SdkUpdaterWindow.open(SdkUpdaterWindow.java:147)
        at com.android.sdkmanager.Main.showSdkManagerWindow(Main.java:336)
        at com.android.sdkmanager.Main.doAction(Main.java:286)
        at com.android.sdkmanager.Main.run(Main.java:120)
        at com.android.sdkmanager.Main.main(Main.java:103)
Also the CM9_SOURCE dir name is not necessary (just ~/android saves on typing too). repo basically pulls down all available branches, froyo, gingerbread, and ICS. So technically, it's not just CM9 source.
 
Whyzor said:
Also the CM9_SOURCE dir name is not necessary (just ~/android saves on typing too). repo basically pulls down all available branches, froyo, gingerbread, and ICS. So technically, it's not just CM9 source.
Click to expand...

I actually use a subdirectory under ~/android for my android source similar to what g60madman writes -- partly because I followed Isaac's original guide and he had it set up that way and partly because it is a convenient way to organize all of my different android-related sources in the same ~/android/ folder, such as my kernels, the android source, other miscellaneous stuff, etc, and not be scattered amongst each other and other non-android related folders.
 
That's fine, I just hate typing ALL CAPS AND underscores, and want to spare others the pain and agony of it ;) . Also by the way the CM repos are named, that seems to the convention. I use ~/android/ for ROM, and ~/android/kernel/ for different kernels.
 
Whyzor said:
That's fine, I just hate typing ALL CAPS AND underscores, and want to spare others the pain and agony of it ;) . Also by the way the CM repos are named, that seems to the convention. I use ~/android/ for ROM, and ~/android/kernel/ for different kernels.
Click to expand...


Oh, yeah. I definitely agree with the all caps and underscores not being ideal.
 
@g60madman - After further research and re-reading the script, in Section 4:

4. Pulling Proprietary Files & Prebuilts

# cd device/motorola/triumph
# ./extract-files.sh
# cd ~/android/vendor/cm/
# ./get-prebuilts
# cd ~/android



You can skip the whole section about running the extract-files.sh script. Everything is already where it's supposed to be after you do a repo sync from my repo.

So the section can simply be:

4. Pulling Proprietary Files & Prebuilts

# cd ~/android/vendor/cm/
# ./get-prebuilts
# cd ~/android


Sorry about that bad information before.
 
mantera said:
@g60madman -


You can skip the whole section about running the extract-files.sh script. Everything is already where it's supposed to be after you do a repo sync from my repo.

So the section can simply be:

4. Pulling Proprietary Files & Prebuilts

# cd ~/android/vendor/cm/
# ./get-prebuilts
# cd ~/android


Sorry about that bad information before.
Click to expand...

Fixed :cool:
 
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.
 
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.
 
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...

So is it even worth it to try on an intel pentium T4200 with 2gb ddr2 ram?
 
You must log in or register to reply here.
Back
Top Bottom