Database Develop

[Android] Building Eclair camera... feel free to help

The devs in the Dream forum have posted open-source camera drivers for Eclair. I'm working on merging the Eclair updates with our current source, but it will take me some time to get up to speed. I'm reading that you have to compile a build from scratch to get the drivers working, which is another hurdle. Has anyone else taken a look at the source yet?
Here's the G1 libs source:
http://gitorious.org/eclair-camera-drivers
Here's our camera sources:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/camera.git;a=summary
http://github.com/dzo/VogueCamera
& Here's our kernel source (not sure we need it):
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
EDIT: Which code are we running right now? Sourceforge or dzo, and from what date?

Hmm. So the camera lib isn't working with Eclair?
Well, if you can post the source from the Dream forum and the current source for cupcake/donut, I'd be happy to take a look and see if I can figure anything out.

Here's the G1 libs source:
http://gitorious.org/eclair-camera-drivers
Here's our camera source:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/camera.git;a=summary
& Here's our kernel source (not sure we need it):
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue

http://gitorious.org/eclair-camera-...mmit/be437d1eb67f106101ae22e8f7829d19e831142e
This commit is a diff from a Donut to an Eclair driver in one convenient place, and it looks like Jesse already did a little of the CAMERA_MESSAGE flags etc. in the 12-13 commit for Vogue.
Shouldn't be too complex.

This is a build from Dream forum with working sync and camera, you may want to take a look at it...
http://forum.xda-developers.com/showthread.php?t=589344

sshark said:
This is a build from Dream forum with working sync and camera, you may want to take a look at it...
http://forum.xda-developers.com/showthread.php?t=589344
Click to expand...
Click to collapse
nah they have different camera drivers. it wouldnt work

Besides the sources I linked, what is the minimum amount of files I need in order to compile the camera lib for our devices? Should I start downloading now so I can leave it overnight??

polyrhythmic said:
Besides the sources I linked, what is the minimum amount of files I need in order to compile the camera lib for our devices? Should I start downloading now so I can leave it overnight??
Click to expand...
Click to collapse
this is from source.android.com/download
Ubuntu Linux (32-bit x86)
To set up your Linux development environment, make sure you have the following:
* Required Packages:
o Git 1.5.4 or newer and the GNU Privacy Guard.
o JDK 5.0, update 12 or higher. Java 6 is not supported, because of incompatibilities with @Override.
o flex, bison, gperf, libsdl-dev, libesd0-dev, libwxgtk2.6-dev (optional), build-essential, zip, curl.
$ sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
* You might also want Valgrind, a tool that will help you find memory leaks, stack corruption, array bounds overflows, etc.
$ sudo apt-get install valgrind
* Intrepid (8.10) users may need a newer version of libreadline:
$ sudo apt-get install lib32readline5-dev
Ubuntu Linux (64-bit x86)
This has not been as well tested. Please send success or failure reports to [email protected].
The Android build requires a 32-bit build environment as well as some other tools:
* Required Packages:
o Git, JDK, flex, and the other packages as listed above in the i386 instructions:
o JDK 5.0, update 12 or higher. Java 6 is not supported, because of incompatibilities with @Override.
o Pieces from the 32-bit cross-building environment
o X11 development
$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl sun-java5-jdk zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev
* Set the system to use the right version of java by default:
$ sudo update-java-alternatives -s java-1.5.0-sun
* X11: Ubuntu doesn't have packages for the X11 libraries, but that can be worked around with the following command:
$ sudo ln -s /usr/lib32/libX11.so.6 /usr/lib32/libX11.so
Click to expand...
Click to collapse
i havent personally compiled android from source yet but this should get you started
EDIT: there are also instructions on pulling the tree also at source.android.com/download
EDIT2: keep in mind the source is ~2 GB so if you have a slower connection like i do i would download it overnight

Ok, I've got my programs installed and am ready to pull source. Now, should I pull the master branch (Eclair + updates), or the main Eclair branch? I'm having trouble matching the Android git branches with the version numbers... I assume I want to pull 2.0.1, but maybe pulling master is better? I can't tell what version the master branch is.

The master isn't any point release version - it's the head, which means it's whatever code happens to be the latest.
However, because Google like to keep upcoming Android releases a somewhat-secret, they don't necessarily push their latest code to the publicly-facing master, which makes things even more complicated in terms of trying to relate master to a point release.
I'd just stick with the Eclair branch for the moment.

Thanks bri3d, I'm pulling the Eclair branch now...

bri3d said:
However, because Google like to keep upcoming Android releases a somewhat-secret, they don't necessarily push their latest code to the publicly-facing master, which makes things even more complicated in terms of trying to relate master to a point release.
Click to expand...
Click to collapse
Which sucks. Any idea when we can expect 2.1 to be made available? I can't seem to find anything online regarding it.

no idea hopefully soon though as we now have the sdk. im pulling the eclair branch also as i type this, gonna play with it i guess lol

Ok, dzo's repo and the androidhtc sourceforge repo seem to have splintered. dzo's last two commits in his repo haven't been applied to the code used at the sourceforge repo. However, the sourceforge camera has since been updated with the initial code for Eclair, while dzo's has not.
dzo's code looks more complete, with the ability to choose resolutions in addition to the jpeg updates.
Which code are we running right now? Sourceforge or dzo, and from what date?
I'm thinking I should take dzo's and add in the Eclair updates... thought I'd ask the guys who wrote it first

use the donut repo at github as a reference. vilord did some initial work porting it to eclair but some more work needs to be done. what he had done will compile but isnt working.

Hey Poly, you might want to check this out. Looks like it may be an entirely updated MSM7k hardware library via JBQ from Google designed for Eclair on our devices. Haven't played with it, but I will in a few..

Shidell said:
Hey Poly, you might want to check this out. Looks like it may be an entirely updated MSM7k hardware library via JBQ from Google designed for Eclair on our devices. Haven't played with it, but I will in a few..
Click to expand...
Click to collapse
that link is to cyanogens github, he develops (and is probably the only real developer on xda) for the dream. His hardware gits may contain some gems that could be ported over for us, but they will not directly work without modification. A great place to look for ideas though glad you posted the link

mssmison said:
that link is to cyanogens github, he develops (and is probably the only real developer on xda) for the dream. His hardware gits may contain some gems that could be ported over for us, but they will not directly work without modification. A great place to look for ideas though glad you posted the link
Click to expand...
Click to collapse
Interesting, thanks for the heads up.

Many of Cyanogens updates require a newer kernel with more features... unfortunately I'm swamped, one of the servers I maintain went down this week and we're taking the opportunity to upgrade, I haven't made further progress on this driver yet.

Damn hate necro posting, but any news of working camera on eclair guys?

[GUIDE] Rolling your own CM7

Here's a short tutorial on how to build your own version of CM7.
Requirements:
- Linux distro such as Ubuntu.
- 30 GB of space.
- Fast internet.
Instructions:
1. Open terminal and install these packages through the commands:
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
If you are on a 64-bit system, install these also:
Code:
sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.4-multilib g++-4.4-multilib
2. Create directories.
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
3. Fetch files from CM.
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
~/bin/repo sync
This will take some hours.
4. Download this git: https://github.com/koush/proprietary_vendor_lge - then extract to /vendor/lge/ (so you have /vendor/lge/p970/...).
5. Build.
Code:
~/android/system/vendor/cyanogen/get-rommanager
. build/envsetup.sh && brunch p970
You'll have the .zip in ~/android/system/out/target/product/p970/.
6. Flash the kang!
That's it.

Only a remark:
- Trying to build my own ROM, I've found that the .zip were 15MB smaller than the same nightly because it doesn't include proprietary files into the ROM. Then arcee told me that before build it, you have to run ./setup-makefiles.sh inside the device's dir.

Huexxx said:
Only a remark:
- Trying to build my own ROM, I've found that the .zip were 15MB smaller than the same nightly because it doesn't include proprietary files into the ROM. Then arcee told me that before build it, you have to run ./setup-makefiles.sh inside the device's dir.
Click to expand...
Click to collapse
No need, check point 4.

thank you very much manuel, very kind of you to share your knowledge with those of us who want to continue your work!

When I tried, I ran ./extract-files.sh in order to get proprietary files from phone itself.
Getting it from the indicated git, you get also the needed .mk files, and then there's no need to run ./setup-makefiles.sh
Forget what I've said...

I hope this guide may inspire some members to give a hand cooking own rom, and we can see this development section filled with different roms. What an optimistic scenario it would be ! .
Thanks again all devs.

knzo said:
Here's a short tutorial on how to build your own version of CM7.
Code:
curl http://android.git.kernel.org/repo > ~/bin/repo
chmod a+x ~/bin/repo
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
~/bin/repo sync
Click to expand...
Click to collapse
in case anyone else faces this, could not run repo init and was going crazy, finally realized repo was not taking the exec flag, opened it up and saw the url was moved, but the link it provided did not work either. remembered the original setup i did for the full android development on another machine and tried this instead -
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
worked like a charm! now, on to the rest...

i am happy to say that i have successfully built and am running my first homegrown KANG, thanks to this tutorial! give it a try, it isn't as hard as you might think (but it does take a VERY long time!)

Hi.
I am a completely n00b here and on the Android environment in general.
So, I was watching the Knzo's instructions and I noted this:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [/bold]gingerbread[/bold]
So I changed it to:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [/bold]isc[/bold]
And it worked!
But, trying to build here:
Code:
~/android/system/vendor/cyanogen/get-rommanager
. build/envsetup.sh && brunch p970
My system says:
Code:
bash: /home/said/android/system/vendor/cyanogen/get-rommanager: No such file or directory
Then I tough, "It's ok, I can get the rom-manager from the market. And skipped to:
Code:
. build/envsetup.sh && brunch p970
But then my system said:
Code:
[email protected]:~/android/system$ . build/envsetup.sh && brunch p970
including device/samsung/maguro/vendorsetup.sh
including device/samsung/tuna/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
Device p970 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_p970
Duplicate device 'CyanogenMod/android_device_lge_p970' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_p970'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Then I tried:
Code:
. build/envsetup.sh && breakfast p970
And this is the output:
Code:
including device/samsung/maguro/vendorsetup.sh
including device/samsung/tuna/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
Device p970 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_p970
Duplicate device 'CyanogenMod/android_device_lge_p970' found in local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/p970/cm.mk]]: "device/*/p970/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_p970'
** Do you have the right repo manifest?
So I went to:
Code:
/android/system/build/envsetup.sh
But couldn't find anything resembling the repo manifest. So that's why I'm here... any help?
Thanks in advanced.
EDIT: Maybe I'm just naïve...

saidhabla said:
I am a completely n00b here and on the Android environment in general.
So I changed it to:
Code:
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b [b]isc[/b]
And it worked!
Click to expand...
Click to collapse
What is isc? Do you mean ics stands for Ice Cream Sandwich?
ICS from CyanogenMod isn't even completed yet, then what are you trying to do?
If you really want to hacking the Android system, I suggest that you synchronize the original android source for ICS to build your own ROM:
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
PS: I don't know yet the size of ICS source would be.. It says ~6 GB, but I'm not getting into it yet...
.CMIIW.

The first part is easy, rom-manager is in vendor/cm folder instead. The second part is a bit more difficult - there are only device branches for a few models, you need to look at those makefiles and figure out how to recreate them for our device. I'm at the same point myself. Don't be discouraged by negatives, it certainly can be done (arcee is running it) but we should probably discuss it elsewhere and not hijack this thread. Good luck, and PM me of you get anywhere, I'll do the same.
Sent from my LG-P970 using XDA App

redy2006 said:
What is isc? Do you mean ics stands for Ice Cream Sandwich?
ICS from CyanogenMod isn't even completed yet, then what are you trying to do?
If you really want to hacking the Android system, I suggest that you synchronize the original android source for ICS to build your own ROM:
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
PS: I don't know yet the size of ICS source would be.. It says ~6 GB, but I'm not getting into it yet...
.CMIIW.
Click to expand...
Click to collapse
Thanks!
So, just in case some lost soul come here and watch your post, the command has to be like this:
Code:
~/bin/repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
Thanks again...
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
dharmabm said:
The first part is easy, rom-manager is in vendor/cm folder instead. The second part is a bit more difficult - there are only device branches for a few models, you need to look at those makefiles and figure out how to recreate them for our device. I'm at the same point myself. Don't be discouraged by negatives, it certainly can be done (arcee is running it) but we should probably discuss it elsewhere and not hijack this thread. Good luck, and PM me of you get anywhere, I'll do the same.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Agree!
And if someone knows how to open a new thread, please let us know. Over for now.

saidhabla said:
And if someone knows how to open a new thread, please let us know. Over for now.
Click to expand...
Click to collapse
"How to open a new thread" ?
Just on the thread list of General/Android Development section, you will notice a yellow box on the top saying in capital : "NEW THREAD". Just click it..

saidhabla said:
Thanks!
So, just in case some lost soul come here and watch your post, the command has to be like this:
Code:
~/bin/repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
Click to expand...
Click to collapse
If you've read the main Android documentation, before we can run just "repo" command, we should set the path:
Code:
$ PATH=~/bin:$PATH
If the path didn't set, then it should run the command:
Code:
$ ~/bin/repo
.CMIIW.

Why would I build my own CM7
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário

offcourse said:
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário
Click to expand...
Click to collapse
i'm sorry,but how long have you been in mars ? lol
the nightlies had stopped at v #20 because of the buildbot was down, and no more update till now
that's why all of us (i don't know if it's just me) are so desperated

offcourse said:
Hi
Cyanogen has nightly builds fo CM7. Why would I build my own?
Does it make it possible to change the packages included? Is there a tutorial for it?
Is it possible to take out the LG launcher, widgets and that top bar thing that allows to control the connections, and include it in my build?
(please don't ask why would I want the LG launcher. I just like it...).
Thanks
Mário
Click to expand...
Click to collapse
Well you can build your own ROM if you having the source code, for example this CM source. And yes, you can do everything you want (change the packages, framework, anything). AFAIK there's no tutorial how to do it, but you should have basically programming skill, especially with C++ and Java, since it's based from those programming language. If you don't have that, then you can just using any launcher out there
CMIIW

redy2006 said:
Well you can build your own ROM if you having the source code, for example this CM source. And yes, you can do everything you want (change the packages, framework, anything). AFAIK there's no tutorial how to do it, but you should have basically programming skill, especially with C++ and Java, since it's based from those programming language. If you don't have that, then you can just using any launcher out there
CMIIW
Click to expand...
Click to collapse
OK, thanks. Clearly not for me coz' we, Martians, don't have programming skills. Just wanted a gingerbread rom without all the crap, neither LG's, Vodafone or even Cyanogen.
Also, because LG's gingerbread update, when it comes, will probably not have the VPN and I can't get any vpn software to work currently, except in Cyanogen (which is buggy in some apps).

I am sorry but vendor lge have 404 error can you get another link ?

[WIP][DEV][ROM][ARC/S] Project Stock MooDeD JB - Project Open Source For Everyone!

Hi.. Guys what is special here is that Will try to Compile the JB from Source 6.0+GB Plus Thats A Big File from there server BTW. I Need some help regarding to some Kernel We need. So Stock JB will work on your Arc. So Ill Start compiling This ROM This night + I Need little help regarding on Ramdisk So we can Start That amazing Stock JB... :good:
My Procedure :
Sync all JB Source 9 ( Tree ) 6.0+GB Will Take A Night 20Mbps Of Speed :silly:
Get A Info Building JB Kernel for Unit/Device
RAMDISK Configuration [ Usually This Is What I Need An Help ]
Make My Own Git
And Lastly The ROM Will be Alpha for our Xperia Arc
So Ill Be Adding More Info Tom / This Night / Next Week Based on my Timeline of Development per Device Maintaining 4+ Device :cyclops:
Current Work Im Doing :
Find Info and ready to Sync and Compiling my Own CWM Thanks To pyvparts
This Is A Real WIP !! Everybody Get in
[ Placeholder For More Info ]
Compiling My OwnRamdisk For JB Kernel Alpha..
Google also test compiling on Ubuntu 10.04 LTS, but I used 10.10, 32 bit. These instructions are for Ubuntu version 10.04-11.10
To install JDK6 (needed):
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner" sudo apt-get update sudo apt-get install sun-java6-jdk
FOR 64bit: You will need the required packages, so open up your terminal and enter:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \ x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \ libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \ libxml2-utils xsltproc
On Ubuntu 10.10:
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
On Ubuntu 11.10:
Code:
sudo apt-get install libx11-dev:i386
FOR 32bit (what I used): You will need the required packages, so open up your terminal and enter:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev \ libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown \ libxml2-utils xsltproc
Now, onto downloading the source
First of all, you need to get the google repo tool, in a terminal:
Code:
mkdir ~/bin PATH=~/bin:$PATH curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo chmod a+x ~/bin/repo
Then reboot the PC
Now, we will actually initialize the repository:
Code:
mkdir -p ~/android/ics/ cd ~/android/ics/ repo init -u git://github.com/CyanogenMod/android.git -b ics
Then enter your name and email address
Then:
Code:
repo sync -j8 if you have bad internet, use a smaller number than 8, eg. 4 or 2
Now, wait for the repo to sync (all 6GB of it )
Then after that is done, you need to setup vendor and device trees for our device
In the terminal again:
Code:
cd ~/android/ics/vendor/ git clone https://github.com/koush/proprietary_vendor_semc.git -b ics semc
Then:
Code:
cd ~/android/ics/device/ mkdir semc cd semc git clone https://github.com/CyanogenMod/android_device_semc_msm7x30-common.git -b ics msm7x30-common git clone https://github.com/CyanogenMod/android_device_semc_anzu.git -b ics anzu git clone https://github.com/CyanogenMod/android_device_semc_mogami-common.git -b ics mogami-common
to sync changes since last sync:
Code:
cd ~/android/ics/ repo sync
get CM props:
Code:
cd ~/android/ics/vendor/cm/ ./get-prebuilts
then to build :
Setup environment:
Code:
cd ~/android/ics/ . build/envsetup.sh
then to get device list:
Code:
lunch
Now, select the number that is anzu-full (or something like that number 4 for me NOT THE ONE WITH "cm_" before it.)
if you get an error about the room service fine and substrings n stuff open the file
build / tools / roomservice.py
goto line 16 or 17
it will have this
device = product[product.index("_") + 1:]
change it to
device = product
save then lunch and you should be able to build (will break other device builds tho)
Now to finally build:
Code:
make -j4 recoveryimage
once you have done that then the recovery + ramdisk will be in
out/target/anzu/recovery/combinedroots/
MAYBE THIS AOSP Kernel Will Work On MooDeD Stock JB Alpha! Kinda Let See.
Click to expand...
Click to collapse

I'm pretty sure I saw code for compiling for job which I believe is slightly different than ics. If urz doesn't work I would suggest looking around xda for a job specific tutorial
Sent from my LT18i using xda app-developers app

zainthesnipe said:
I'm pretty sure I saw code for compiling for job which I believe is slightly different than ics. If urz doesn't work I would suggest looking around xda for a job specific tutorial
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Thats A Good Opinion But ICS Kernel [ Cyanogenmod ICS Source ] maybe Good To Start A Pre-Alpha MooDeD JB From Source

can't wait
hope you release it soon

Tell me one thing... If the internet connection drops while i'm syncing the repo (the 6 gbs of source) do i have to download it all again or it gets resumed from the part it dropped..?

flsmidth said:
Tell me one thing... If the internet connection drops while i'm syncing the repo (the 6 gbs of source) do i have to download it all again or it gets resumed from the part it dropped..?
Click to expand...
Click to collapse
For Me I dont experienced that kind of error My Answer is Unkown I left it overnight to sync the Repo.
Sent from my GT-I9100G using xda app-developers app

ChaosFirZen said:
For Me I dont experienced that kind of error My Answer is Unkown I left it overnight to sync the Repo.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Actually I tried syncing the repo once to make AOSP for Arc.. But due to power failure there a connection drop and i didn't bother to sync it again because i have slow internet connection..

flsmidth said:
Actually I tried syncing the repo once to make AOSP for Arc.. But due to power failure there a connection drop and i didn't bother to sync it again because i have slow internet connection..
Click to expand...
Click to collapse
We Have 20MBps Of Internet Speed
Sent from my GT-I9100G using xda app-developers app

Nice, I like to have a pure AOSP 4.1 rom for the Xperia Arc. Always wondered why there were no AOSP roms for the Arc

The problem is that there is not a lot of device in the git "only samsung and nexus", other devices aren't present. So when you sync, you can't build JB.
"https://github.com/koush/proprietary_vendor_semc.git" don't exist.
Replace ics with jb in the google repo and ics with jellybean in CM repo to sync the Jelly Bean tree.
Good luck.

ChaosFirZen said:
We Have 20MBps Of Internet Speed ;
Click to expand...
Click to collapse
In download or upload?

mekayzer said:
The problem is that there is not a lot of device in the git "only samsung and nexus", other devices aren't present. So when you sync, you can't build JB.
"https://github.com/koush/proprietary_vendor_semc.git" don't exist.
Replace ics with jb in the google repo and ics with jellybean in CM repo to sync the Jelly Bean tree.
Good luck.
Click to expand...
Click to collapse
Even better to sync fxp's vendor trees.. fxp have modified their's to work with jb..
i dont know about arc but here's the one for pro
https://github.com/CyanogenMod/android_device_semc_iyokan/tree/jellybean
* try replacing "iyokan" with anzu or ayame.. You may get the jb tree for Arc/S

rod555 said:
In download or upload?
Click to expand...
Click to collapse
Download
flsmidth said:
Even better to sync fxp's vendor trees.. fxp have modified their's to work with jb..
i dont know about arc but here's the one for pro
https://github.com/CyanogenMod/android_device_semc_iyokan/tree/jellybean
* try replacing "iyokan" with anzu or ayame.. You may get the jb tree for Arc/S
Click to expand...
Click to collapse
Pro Will work on It but the PROBLEM is the Kernel + RAMDISK { Ramdisk 10% Complete }

ChaosFirZen said:
Download
Pro Will work on It but the PROBLEM is the Kernel + RAMDISK { Ramdisk 10% Complete }
Click to expand...
Click to collapse
Ramdisk can't be ported i guess..

I tried 2days ago, but can't build for anzu.
Perhaps when fxp release CM10, we will build again from source.
Someone got the kernel build ?

the only thing that i can say is, THANK YOU ALL!!
very good news.
i have 100 MB internet conection, if that helps any one!!

flsmidth said:
Ramdisk can't be ported i guess..
Click to expand...
Click to collapse
\Thats Why Im Creating My Own Ramdisk ... For MooDeD JB Alpha

ChaosFirZen said:
\Thats Why Im Creating My Own Ramdisk ... For MooDeD JB Alpha
Click to expand...
Click to collapse
Try the ramdisk from the ARC JB AOKP.. the problem with their boot image is gallroc. You might make it work..

Let's use ICS Kernel for the meantime, we'll work on Jelly Bean kernel when we have a working build of it. But with ICS Kernel I doubt Project Butter will function very good, and maybe Voice Action won't work too.
But for a pre-alpha, ICS Kernel would be acceptable!

maybe this can help you
butits tutorial how to build cm10 rom
http://forum.xda-developers.com/showthread.php?t=1789190

Development! Project JellyBeanSwift - Open Source Project!

I will teach you build ROM.
Lets get some ROCK!!!
Operating System
First step is having a fully functional linux distro. You can choose what you prefer, I'm using ubuntu and I write commands for it. You can use OSX too, as I know, but I've completely no idea how, I never had a Mac.
Well, talking about linux, you need a 64bit distribution, so if you have an old 32 bit processor youn cannot go ahead.
To check which version do you have, type in a shell
uname -a
If the results include "x86_64" you're ok.
Required Packages
You need to install some little packages, to be able to proceed, you can do this with your favorite package manager:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Some systems need some trick to install all this package, is your care to check this process completed correctly and fix eventually problems.
Install "repo"
Repo is the program that handles synchronization between our pc and the repository, in this case Cyanogen's one. To install do:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
So we have downloaded and added executables flag to it. Now we need a folder to store locally the sources, you can put it everywhere, but to be coherent with other guides, I do:
mkdir -p ~/CM10/
Repository initialization
Well, now it's time to initialize our source folder to correctly sync with repository:
cd CM10
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Nota: Maybe the repo command is not recognized. In this case you can restart the shell or te machine.
Download
Now is download time! Write this command and get a fresh beer, you have to download several GB of data, please wait.
repo sync -j16
The "-j16" switch may be modified as you want, is the number of concurrent thread downloading from repo. 16 is my value, for a 100Mbit connection, maybe you can decrease a little to match your line speed. Someone uses 8 threads for an 8Mbit ADSL line.
Download precompiled files.
There are some others files needed, like the toolchain, including GCC, to compile code.
~/CM10/vendor/cm/get-prebuilts
Another small wait time and we're ready!
Add sources code for GT540
Copy sources from https://github.com/mmxtrem/device_lge_swift to ~/CM10/device/lge/swift
Or extract this archive http://depositfiles.com/files/1chflk58r to ~/CM10/device/lge/swift
Build
Great, we're ready to build!
The build process takes some hours, so be patient. My notebook, takes more than 10 hours!
cd CM10
source build/envsetup.sh && brunch swift
Install
When is ready, we can find the result here:
~/CM10/system/out/target/product/swift/cm-10-XXXXX-JellyBeanSwift-XXXX.zip
This is the package to be flashed in recovery mode.
There are Gapps included.
Update
If you want to update your build, you have to do only this:
cd CM10
repo sync
and build again!
P.S. Dont forget write Credit my name, when will be publish your ROM. Good Luck!
[Guide] How to use Github
http://forum.xda-developers.com/showthread.php?t=1877040

Wow I always wanted to try this out! Thanks for the surprise tutorial!

Wow wow wow.. forget my post in the other thread. This thing miro, this thing here is possible your best contribution to this community.. I'm getting my old gt540 back from my brother and trying these right tomorrow..
I actually thought about asking you for such a tutorial but scratched it as I didn't believe you would do it. But thank you again and again.. I was so wrong

I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob

Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8

-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
+1
Sent from my LG-P990 using Tapatalk 2

smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
Yes, gt540 is msm7x27

smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Please dont write stupid massages like "smiles" or +1 or other, make it clean! Devs only, if you want build ROM real, if no go spaming into other thread!

XiproX said:
Yes, gt540 is msm7x27
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Click to expand...
Click to collapse
damn

-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
^ This, make a guide for this, or is just all "lets google it"?

thanks for that tut miroslav !!
i would be happy if you can make example of bug fixing/driver porting (something simple as example).

Oh, nice post Miro
But one thing, why don't you post how to make device files. It would be of more use as people will try to make their own sources and a good chance that they could make their own device in collaboration. :good:

i've ear i can do a build in a 32bits processor too! but you know xD do what was said up please!!

Could someone try to build this because I can't cause I have 32bit system in my PC.
We need JB for daily use!

Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?

aaa801 said:
Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?
Click to expand...
Click to collapse
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.

Niquel97 said:
We need JB for daily use!
Click to expand...
Click to collapse
Just do it! (c. Nike)
P.S. Dreams-dreams-dreams.... :laugh:

miroslav_mm said:
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.
Click to expand...
Click to collapse
So should work fine if set to hard yes?

i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])

al3000 said:
i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])
Click to expand...
Click to collapse
Yes, me too, the build comes so big that it fails the size checks on the default partition layout.
To avoid that change the contents in device/lge/swift/BoardConfig.mk, I've used these values:
Code:
# PARTITIONS
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00900000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0010B07600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x007478A00
BOARD_FLASH_BLOCK_SIZE := 131072
I believe you can still zip up the right files in out/target/product/swift/ to have a signable update zip, the command "make otapackage" which I found somewhere didn't seem to work.

[TUT] How to build CM10.1 from source for Atrix HD

Disclaimer: I'm not responsible for what this does to your shiny device, SO DON'T BLAME ME!!!
Requirements:
Ubuntu 12.10 64-bit
15GB of disk space (25Gb recommended)
Internet connection
Brain
First:
Install required packages:
Code:
apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jre openjdk-6-jdk pngcrush schedtool libxml2 xsltproc g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.7-multilib g++-4.5-multilib
Install repo:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod 755 ~/bin/repo
echo "export PATH=\${PATH}:~/bin" >> ~/.bashrc
export PATH=${PATH}:~/bin
Second:
Sync all the sources
Code:
cd ~/android/system
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
curl -L -o .repo/local_manifests/razrqcom.xml -O -L https://raw.github.com/razrqcom-dev-team/android_local_razrqcom/master/razrqcom.xml
repo sync -j1
Go sleep for the night, because this takes overnight
Third:
Build:
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
cd ~/android/system/device/motorola/qinara
./extract-files.sh
cd ~/android/system
. build/envsetup.sh
lunch cm_mb886-userdebug
make otapackage
ENJOY!!!

Resverved...

tcf38012 said:
Resverved...
Click to expand...
Click to collapse
Cool tutorial.
Did you have success using this method?

Your internet must really suck :silly, takes me an two hours tops during heavy traffic. Well, Defy GB takes many, many hours...but it also syncs for like 20 devices untill you modify the xmls and scripts.
Also, sync -j1 is the slowest setting and only recommended if you net really does suck. I get best results between -j3 and -j5 depending on time of day. The number is me amount of simultaneous downloads that will occur.
Do everyone a favor and not add in the ccache part of the guide. I've had issues in the past where the only difference in compile was ccache, and the ccache version was the buggy one. I used to love it, but once you use if for a bit and start getting buggy roms, only to disable it and recompile the same crap and not have a buggy rom....quit using ccache easy decision to make for me.
Thanks for the guide, I'm sure someone will find it useful. Once my cable net gets back online I plan on messing around with CM10.
//Gotta love MR's no tethering entitlement check

Markyzz said:
Cool tutorial.
Did you have success using this method?
Click to expand...
Click to collapse
Yeah I wish
I just need to make it work and upload to github.
I will work on it more on the weekend

skeevy420 said:
Your internet must really suck :silly, takes me an two hours tops during heavy traffic. Well, Defy GB takes many, many hours...but it also syncs for like 20 devices untill you modify the xmls and scripts.
Also, sync -j1 is the slowest setting and only recommended if you net really does suck. I get best results between -j3 and -j5 depending on time of day. The number is me amount of simultaneous downloads that will occur.
Do everyone a favor and not add in the ccache part of the guide. I've had issues in the past where the only difference in compile was ccache, and the ccache version was the buggy one. I used to love it, but once you use if for a bit and start getting buggy roms, only to disable it and recompile the same crap and not have a buggy rom....quit using ccache easy decision to make for me.
Thanks for the guide, I'm sure someone will find it useful. Once my cable net gets back online I plan on messing around with CM10.
//Gotta love MR's no tethering entitlement check
Click to expand...
Click to collapse
Go ahead and use your lte lol
I just have a 325kb/s inet speed at the max, so I just use -j1
You can change it if you have a super connection at your house
Downloads, unless your wireless, work better solo anyways...

Why the tuturial? Why not just build the CM10.1 yourself and collect the $50 reward?

tcf38012 said:
Go ahead and use your lte lol
I just have a 325kb/s inet speed at the max, so I just use -j1
You can change it if you have a super connection at your house
Downloads, unless your wireless, work better solo anyways...
Click to expand...
Click to collapse
325k..now I get it. I have 1.5m down with 60k up...ISP caps upload to stop torrenting, but I guess they've never heard of leeching.
No LTE here, closest is 30 milesish. 3gb data cap with $10 per GB afterwards....damn ripoff.
I can -j2 and both [email protected] or [email protected]
One of my neighbors uses only WPA security... I'll "access" that network if mines not back up soon.
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
nick2012 said:
Why the tuturial? Why not just build the CM10.1 yourself and collect the $50 reward?
Click to expand...
Click to collapse
Just because its a repo doesn't mean it works. This is a start and could end up being the working one. We need a starting point & this is just that.

Reportedly Hashcode's 10.1 boots on our AHD, but the display is black. This is because the newer RazrHD builds use a different display name/driver(?) than the AHD. Same goes for the touchscreen (I think). If you look at some log in /proc after booting up (I forgot the name, but you need to reboot, not power off, or else it'll be erased), you'll see the error about the display
This is also why TWRP doesn't load on the AHD. Hashcode tested a rebuild with the display name fix, and the screen worked, but something else didn't so it's not ready for primetime just yet.
I'm not sure if it's a kernel/init or system issue, but the cm10 version I uploaded is an older RarzrHD build by Hashcode and doesn't have a broken display on the AHD, whereas Epinter's latest cm10 doesn't work. So maybe that's a place to start for the display issue.
As a test, I flashed only Epinter's /system, leaving Hashcode's boot.img intact, and the ROM booted up. The backlight lit up during an incoming call but it did not vibrate or ring, and the display was black, of course. Hopefully this helps with building 10.1.

progrockguy said:
Reportedly Hashcode's 10.1 boots on our AHD, but the display is black. This is because the newer RazrHD builds use a different display name/driver(?) than the AHD. Same goes for the touchscreen (I think). If you look at some log in /proc after booting up (I forgot the name, but you need to reboot, not power off, or else it'll be erased), you'll see the error about the display
This is also why TWRP doesn't load on the AHD. Hashcode tested a rebuild with the display name fix, and the screen worked, but something else didn't so it's not ready for primetime just yet.
I'm not sure if it's a kernel/init or system issue, but the cm10 version I uploaded is an older RarzrHD build by Hashcode and doesn't have a broken display on the AHD, whereas Epinter's latest cm10 doesn't work. So maybe that's a place to start for the display issue.
As a test, I flashed only Epinter's /system, leaving Hashcode's boot.img intact, and the ROM booted up. The backlight lit up during an incoming call but it did not vibrate or ring, and the display was black, of course. Hopefully this helps with building 10.1.
Click to expand...
Click to collapse
Latest CM10.1 merge broke a few things on the RAZR HD side and they're working on it...
Before I even got an Atrix HD, I had a feeling Atrix\RAZR HD would be like Bravo\Defy and I was right....Quit making clone phones Motorola. We need 5 models a year -- small, medium, large, small tablet, and big tablet with all running the same OS...That's what I would do if I were in charge.
Almost up to a 1:1 post to thank ratio. Makes me happy.

skeevy420 said:
Latest CM10.1 merge broke a few things on the RAZR HD side and they're working on it...
Before I even got an Atrix HD, I had a feeling Atrix\RAZR HD would be like Bravo\Defy and I was right....Quit making clone phones Motorola. We need 5 models a year -- small, medium, large, small tablet, and big tablet with all running the same OS...That's what I would do if I were in charge.
Almost up to a 1:1 post to thank ratio. Makes me happy.
Click to expand...
Click to collapse
Atrix is for AT&T, Razr is for Verizon. That's OK, and that's great.
Cause we, as Atrix users, can use RAZR builds :good:

The display don't work with the razrhd kernel, right? somebody has a dmesg ?

epinter said:
The display don't work with the razrhd kernel, right? somebody has a dmesg ?
Click to expand...
Click to collapse
It does not. If you can teach me how to get a dmesg I'll do it right now. If you want, PM me. I really need to learn to use dmesg so it would be awesome if you could teach me while getting what you need.
Sent from my XT925 using xda app-developers app

EcHoFiiVe said:
It does not. If you can teach me how to get a dmesg I'll do it right now. If you want, PM me. I really need to learn to use dmesg so it would be awesome if you could teach me while getting what you need.
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
adb shell dmesg

Updated
See OP for more details

Since you seem to be one of the few into compiling from source, have you had any issues with compiling the kernel? I cannot get the kernel to build and its driving me crazy. I first noticed that it wasn't calling the right defconfig, so a "make ARCH=arm menuconfig", load the correct one and saved it as .config...you'd think that would work, but it then started complaining about missing files -- zconf.tab.c & zconf.hash.c -- noticed that both of them were in the .gitignore file for scripts/kconfig (where those 2 files should be). Have you seen that in your compiles, and if so, any fix?
For what I'm doing, I could just use the CM10.1 kernel from epinter's latest, but I'd have to set up the makefiles to reflect that...and I'd rather not do that for what is probably a minor\dumb issue on my end.
I'd post a build log, but I didn't save any from last night. I'll post one in a little while once I have it.
EDIT: Saw another issue I could be having -- gcc4.7. Forked the kernel repo and changed to the gcc4.7 branch. Gonna pick in the latest 10.1 commits and go from there. :fingers-crossed:
EDIT2: All my issues were from using gcc4.7. Switched to gcc4.6 & everything's fine.