Database Users

[Q] want to compile CM7 - easy dev

So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?

It IS Lupus said:
So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
Click to expand...
Click to collapse
Well... You'll need a vendor tree first. And you'll have to run it on a 64-bit box with 64-bit linux. You have to change 'froyo' to 'gingerbread' in EasyDev, so it will grab CM7 source. There will also be some other differences to work out.
As soon as there's a vendor tree available and I have the time to test, I'll finish up EasyDev v7. Some of the additions that I have actually worked on so far are:
1) two or three bug fixes
2) adding CM7
3) adding option to install tiny or full gapps
The CM6 code has been unstable recently in addition to koush's hosting having issues, so I have had plenty of speed bumps in addition to real life stuff.
So... If you can wait on me, that's fine. If not, go for it! Feel free to post your code changes in the thread. We'll take any help we can get.

gnarlyc said:
And you'll have to run it on a 64-bit box with 64-bit linux.
Click to expand...
Click to collapse
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0

bftb0 said:
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
Click to expand...
Click to collapse
I honestly wasn't sure, but a quick Google search...
http://groups.google.com/group/android-building/browse_thread/thread/852d63ab6124c87e
This is a post from the Android Building group. It appears to be a JDK issue. I've not really tested either way as of yet, although apparently Google says "use a 64-bit host to build, that's what is supported."

[VMWare Image][9-DEC-2011] Android AOSP/ROM Developer Environment

Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.

A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).

This is awesome. My only problem is that I only have VMWare Workstation 7.

Super! Waiting for this

djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.

You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.

I would appreciate it. THANKS

nice.....this could be very useful
Sent from my Nexus S using xda premium

FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%

@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.

suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.

djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.

i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.

I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?

I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!

Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'

http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?

updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!

yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.

Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.

native ubuntu for tab 7.7

any idea how can i install ubuntu on tab 7.7 natively

What do you mean by "native"? You could try and chroot and then install Ubuntu. This might work, but i have never tried it.

odessa2 said:
What do you mean by "native"? You could try and chroot and then install Ubuntu. This might work, but i have never tried it.
Click to expand...
Click to collapse
maybe there is some hope in this? (Xda won't let me post links but just google search "ubuntu phone") Ubuntu are releasing a mobile version of their operating system that runs natively on phones. So far they are only developing on the galaxy nexus but there is more to come

There are installers for Debian and Ubuntu in the app store. They run in a chroot environment.

I have tried chrooting... It wasn't that useful...
And that ubuntu phone thing isnt released yet...

virsingh said:
I have tried chrooting... It wasn't that useful...
And that ubuntu phone thing isnt released yet...
Click to expand...
Click to collapse
the Ubuntu OS has two parts.
platform : not depending on target.
Linux Kernel: depend on target (chipset machine and drivers and HAL )(same as android)
in fact we can use locerra kernel to build Ubuntu rom images when it's released.
but generic kernel that's for pc won't work at all, this an embedded device not generic pc.

[Q] about framework/base

any ideas about using /framework/base from git to compile trebulchet or systemui?
i'm using IntelliJ IDEA
thank you

fabiosarts said:
any ideas about using /framework/base from git to compile trebulchet or systemui?
i'm using IntelliJ IDEA
thank you
Click to expand...
Click to collapse
This is the Trebuchet repo: https://github.com/CyanogenMod/android_packages_apps_Trebuchet

i got the trebuche package and others i would need by downloading the entire cm10 source git using repo, the only problem is the libraries i need to compile it

i've found i could compile it, but the prebuilt gcc is 32 bits, i can't run it, since i got a 64 bits system, but there's a 64 bit gcc there, but i can't make to make use it instead using the 32 bits

fabiosarts said:
i've found i could compile it, but the prebuilt gcc is 32 bits, i can't run it, since i got a 64 bits system, but there's a 64 bit gcc there, but i can't make to make use it instead using the 32 bits
Click to expand...
Click to collapse
Shouldn't the 32 bit version run in compatibility mode?

sadly my debian and slackware didn't came with 32 bit compatibility
i could compile it on mac os, but all i got it's a final dexed jar, no android APIs there D:

[TUTORIAL][VIDEO]KernelANDROID[LINARO][SABERMOD][NDK]build from source

Here is a complete tutorial about:Android Kernel(compile)+ Linaro/Sabermod/NDK.​
//In the future I will add a tutorial related to undervolt., overclock, cpu governor, and others.(only Snapdragon CPU)
Kernel Features HERE
Youtube channel(if you have troubles).
Part 1: vmware+ubuntu+Installing the required files:
Linaro
Part 2: download kernel source files+ setup toolchain+jdk+abootimg
Part 3: kernel+ boot.img file
Part 4: test
Part 2/3 SABERMOD
Part 2/3 Android NDK
More:
extract .config via ADB:
compile-speed:
dump boot.img:
Change bootimg.cfg size-hex:
Create boot.img via script.sh. Much faster!!!
Linaro vs NDK:
I'll keep you updated, so stay tuned ​

Reserved

Thank you so much for this guide! before people had to learn from strictly written ones and it was difficult for a lot of us to pick up
oh and congrats on Portal feature!

Thank you for this guide . I can wait to try it .
Sent from my GT-I9100G using XDA Premium 4 mobile app

Sorry if its already been answered but can I use Ubuntu 14.04 to do this? what advantage does 12.04 have?

You can use either Ubuntu 14. However this does not affect anything(about kernel). But I preferred the version 12 because it is more popular, and if problems "arise", it's easier to find solutions.

!
great tutorials! any chnce of one compiling with GCC?
also man! YOUR COMPUTE IS ON STEROIDS!!!

Maybe, but in summer(I'm still busy with school). GCC needs to be changed in Part II.
also man! YOUR COMPUTE IS ON STEROIDS!!!
Click to expand...
Click to collapse
Configuration is:
Asus k53sv
-Intel Core I7 2630QM
-12 GB Ram (1333 mhz cl9)
-HDD: 750GB WD Black;
-GPU Intel HD 3000+Nvidia GT540M 2gb ddr3;
+1080p tv(monitor) but only for tutorials.

srsdani said:
Maybe, but in summer(I'm still busy with school). GCC needs to be changed in Part II.
Configuration is:
Asus k53sv
-Intel Core I7 2630QM
-12 GB Ram (1333 mhz cl9)
-HDD: 750GB WD Black;
-GPU Intel HD 3000+Nvidia GT540M 2gb ddr3;
+1080p tv(monitor) but only for tutorials.
Click to expand...
Click to collapse
yeah ive been having problems with GCC on ubuntu 14.04, on my last installation(also 14.04) all compiled fine, yet this fresh installation theres no errors but doesnt boot(stock unmodified sources) :/

What's your device? Some have a slightly different configuration(Samsung or Sony/Sony Ericsson etc.).

srsdani said:
What's your device? Some have a slightly different configuration(Samsung or Sony/Sony Ericsson etc.).
Click to expand...
Click to collapse
after days of troubleshooting i finally just found the problem..
i had exported PATH to JDK 8 in my .bashrc, i just compiled and it worked
thanks to your video making me look in .bashrc!
LEGEND!!!!

Ricky Divjakovski said:
after days of troubleshooting i finally just found the problem..
i had exported PATH to JDK 8 in my .bashrc, i just compiled and it worked
thanks to your video making me look in .bashrc!
LEGEND!!!!
Click to expand...
Click to collapse
Can this work for my s4 I9506 stock kernel

Kind of over complicated?
No need to modify .bashrc to build kernels, also nautilus-open-terminal, and synaptic arent needed in any way for kernel compilation and its kinda bad practice to auto accept with sudo apt-get install -y.
Also I dont think java is needed to build kernels (since they are mostly C and assembly code), but oracle java 6 is usually what is recommended for android builds.
Basically all you really need to do is install the required packages, download kernel source and desired toolchain, then run these lines in terminal to get your zImage-
export ARCH=arm
export CROSS_COMPILE= <directory to toolchain>
make <your kernel default config>
make -j<number of threads>
That way makes it much easier to try out different toolchains and toolchain versions

Buddy, mention clearly of which device u r using, n on which device it will work.:laugh: by the way nice work

Niku-Droid said:
Buddy, mention clearly of which device u r using, n on which device it will work.:laugh: by the way nice work
Click to expand...
Click to collapse
kernel building for different devices is pretty much all the same, all that differs is the kernel source, defconfig and sometimes a few extra commits to work with linaro toolchain. And if you use the arch specific toolchains you need to pick the right one for your device

metalspring said:
kernel building for different devices is pretty much all the same, all that differs is the kernel source, defconfig and sometimes a few extra commits to work with linaro toolchain. And if you use the arch specific toolchains you need to pick the right one for your device
Click to expand...
Click to collapse
Yea, buddy, but he should mention about which device is he using, so it would give us a brief idea, that what we have to do.

Niku-Droid said:
Yea, buddy, but he should mention about which device is he using, so it would give us a brief idea, that what we have to do.
Click to expand...
Click to collapse
Device: Acer Cloudmobile s500
Cpu snapdragon s4 krait dual—core 1.5 ghz
Gpu Adreno 225;
1gb ram
8 mp camera+1.9 mb front;
1460 mah battery
Hd 720p display

Very nice tutorial. I just got into building from source. Yesterday shortly before you posted this, I have successfully compiled a ROM for the first time. Also can you add the link to the other tutorial when it's done on this thread?

can anyone just post the video links they are not opening on my mobile , are they on YouTube so I can DL them for future reference
Thanks

Look great will be looking into tutorials