Related
For developers only!! We are not supporting users yet
The instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
There are two steps initially - first is to flash and convert filesystems, update recovery, kernel and CM7, but after that you can just install the CM7 zip if you have done another rebuild as you do development.
There is no easy way of going back to froyo - you would have to flash to stock via Odin one-click and let it blow away the filesystem etc. This is why it is for developers only - it is very alpha and you will find yourself going back and forth a lot.
Warning - this will eat your kitties and possibly your doggies and goldfish too!
-Atin
I dont mean to ruin the thead but, just want to say thanks to all devs working on cm7! And look foward to running cyanogen again after using on my htc magic a couple years ago!
Building right now...I am the excite.
good stuff.
can't wait to see the first gingerbread rom on captivate.
Trusselo said:
i hope your ROM building is better than your sentence building
Click to expand...
Click to collapse
Why the hate? Take a chill pill.....
shawn122 said:
Why the hate? Take a chill pill.....
Click to expand...
Click to collapse
Because he likes to act like a little kid in just about any thread that he can.
There's always gotta be one douchebag.
Anyways, let's keep this thread clean.
That **** isn't needed here. Building now and pretty stoked. Thanks!
I am the excite.
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
Thanks in advance for all those who cook up some GREAT ROMS!!!
atinm said:
For developers only, the instructions to build Gingerbread are on http://cmsgs.com
If you intend to develop for Captivate, you are welcome to use the instructions to build from source and test/debug/fix. This is not for the average user right now and we ask that you do not post binaries for users because things are unstable and we'd really rather not be dealing with users who've managed to screw up their phones.
Warning - this will eat your kitties!,
-Atin
Click to expand...
Click to collapse
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Try again - seems to be working here.
bamonkey said:
Im interested in trying to impliment voodoo sound. Ive been following this http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=16 and it looks like it wouldnt be too hard. Any ideas on how easy or hard this really is or what i could try to do on my end to try to add from supercurio's repo? *see his nexus S thead from the link above*
Click to expand...
Click to collapse
Since all the code is on github, both for voodoo sound and for CM7, you just need kernel/android smarts to pull in the changes. Clone the repos, take what you need . . . sorry I can't help more, I haven't looked at voodoo sound but there are others who have that could help I'm sure.
cchant said:
Getting errors on sync. 'Bad head' not at my computer so can't get exact error
Click to expand...
Click to collapse
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
I got this error.
Code:
error: revision refs/heads/master in manifests not found
I got both of those. Clean repo
ballz0iron said:
Error in line 1380 of project.py, in GetHead fd = open(path, 'rb')
Click to expand...
Click to collapse
this is an error with repo/your machine, not CM7. try syncing again after a while (possibly after a reboot) or clearing out the folder (including your .repo folder) and trying again
ih4ckback said:
I got this error.
Code:
error: revision refs/heads/master in manifests not found
Click to expand...
Click to collapse
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
ih4ckback said:
Actually I should clarify, I got that error trying to init the GB initial flash repo. Any assistance? I need to start there since I don't have it or do I not really need it?
Click to expand...
Click to collapse
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
atinm said:
Sorry guys - there should be a -b gingerbread on the repo init -u git://github.com/teamhacksung/android.git -b gingerbread, I've fixed the wiki page with the instructions for the initial flash.
Click to expand...
Click to collapse
I seeeeeee. Syncing now lol.
Hello all,
due to the fact, that there are already activities to compile ICS for a lot of other devices, i have taken the liberty to open a thread for all Dev's and those who are interested in getting ICS to work on cooper. Hope that this is ok...
Meanwhile i could 'partly' compile ICS by using koljas configuration files. But i have to say, that i removed some libraries for compilation because i couldn't find solutions to successfully compile them. First 'goal' should be to have an image which boots. So we have a start. Compilation; without the 'error' libraries; completely succeeded here now. But creation of a first otapackage failed. This is my actual response of 'make otapackage'. I alreday tried to google this problem, but couldn't find a solution..
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.1
TARGET_PRODUCT=cooper
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv5te-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ITL41D
============================================
build/core/main.mk:324: implicitly installing apns-conf_sdk.xml
No private recovery resources for TARGET_DEVICE cooper
Package OTA: out/target/product/cooper/cooper-ota-eng.lagloose.zip
unzipping target target-files...
running: unzip -o -q out/target/product/cooper/obj/PACKAGING/target_files_intermediates/cooper-target_files-eng.lagloose.zip -d /tmp/targetfiles-8iaaXh
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 839, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 791, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/lagloose/WORKING_DIRECTORY/build/tools/releasetools/common.py", line 144, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(zip)
File "/home/lagloose/WORKING_DIRECTORY/build/tools/releasetools/common.py", line 163, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot bml boot NULL NULL NULL NULL"
make: *** [out/target/product/cooper/cooper-ota-eng.lagloose.zip] Fehler 1
Any ideas ?
thx, lagloose
Hi! I think that at the moment trying to make aosp from android 4 source waste of time! More wisely to try to build android 4 from sorce code with the changes cyanogenmod9)
I changed a few config files for cm9.
And build a lot of libs to lipng and dalvic
Can you help me with config files?
P.S. add armv6-vfp.mk from gingerbread to android_build/core/combo/arch/arm
P.P.S. configs will be on my github's account tomorrow
Axel2033 said:
Hi! I think that at the moment trying to make aosp from android 4 source waste of time! More wisely to try to build android 4 from sorce code with the changes cyanogenmod9)
I changed a few config files for cm9.
And build a lot of libs to lipng and dalvic
Can you help me with config files?
P.S. add armv6-vfp.mk from gingerbread to android_build/core/combo/arch/arm
P.P.S. configs will be on my github's account tomorrow
Click to expand...
Click to collapse
Sounds good...
leave a message here when you're files are at github...
Did you install all the required packages ?
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Did you install all the required packages ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Yep. I think it is a more a problem with the config files. Anyway, i will follow Axels idea, and give a try to the Cyanogen Sources ...
Sent from my GT-S5830 using Tapatalk
lagloose said:
Yep. I think it is a more a problem with the config files. Anyway, i will follow Axels idea, and give a try to the Cyanogen Sources ...
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
To think the AOSP sync is such an ass .
Sent from my GT-S5830 using XDA App
I dont know much about python, but looking at the stacktrace the problem is in main(sys.argv[1:]), of course you know that, mind checking that line "File "./build/tools/releasetools/ota_from_target_files", line 839"
When you set this line TARGET_PRODUCT=cooper, does it try to config the files for it? Just trying to help here.
traduz said:
I dont know much about python, but looking at the stacktrace the problem is in main(sys.argv[1:]), of course you know that, mind checking that line "File "./build/tools/releasetools/ota_from_target_files", line 839"
When you set this line TARGET_PRODUCT=cooper, does it try to config the files for it? Just trying to help here.
Click to expand...
Click to collapse
Thanx for reply....
i already found the problem. The file 'recovery.fstab' was malformed...
Generally it seems to me, that Kolja took the Config from ZTE Blade and changed only the most important things. But as i alreday said, i'll stop now on AOSP and try the Canogenmod Sources. They are almost updated hourly at the moment.
PS: It would be nice, if all people who tried to compile ICS for our device could give a short information on how far they already got...
Greetz, lagloose
Hi.
First of all i would not consider myself noob and i would like to help out, but right now i have no idea where to start. any pointers or howtos to get started? would love to see ICS on ace
What stage of the development are u guys at and what problems are u currently facing?
lagloose said:
Thanx for reply....
i already found the problem. The file 'recovery.fstab' was malformed...
Generally it seems to me, that Kolja took the Config from ZTE Blade and changed only the most important things. But as i alreday said, i'll stop now on AOSP and try the Canogenmod Sources. They are almost updated hourly at the moment.
PS: It would be nice, if all people who tried to compile ICS for our device could give a short information on how far they already got...
Greetz, lagloose
Click to expand...
Click to collapse
You can use my android_device_samsung_cooper
http://github.com/EmoBoiix3/android_device_samsung_cooper
Sent from my GT-S5830 using XDA App
I'm sorry I was very busy(
Today will be config on git)
making a fork... if you have a site to make documentation should be great!
https://github.com/axel2033/device_cooper_cm9
Thanks for sharing... I'm busy this Weekend. So can't do anything before Monday....
Sent from my GT-S5830 using Tapatalk
Updated coolya kernel https://github.com/teamhacksung/android_kernel_samsung_msm/tree/merge
Good luck for the dev's.I will help for testing , debugging and bug reporting.
Axel2033 said:
https://github.com/axel2033/device_cooper_cm9
Click to expand...
Click to collapse
Great, now we have 3 devs working for it
Great to see work in progress, stares at github with confused look
Sent from my GT-S5830 using xda premium
Guys, please stop posting here except you are a developer or know how to help ...
Sent from my GT-S5830 using XDA App
Xperia Play Users,
I am currently working on bringing CM10 to the Play, and I'm looking for input from anybody else who has ideas.
The Rules:
Post something constructive, no "Good Luck" "reserved" etc. this thread is for working through problems when building CM10
That said.
Update: I'll be posting errors here, so it'll be easy to keep track of.
First error I hit (& fixed? (compiler hasn't failed yet on this one)) deals with hardware/qcom/display/libcopybit where copybit_c2d.cpp fails to compile with a couple of errors related to "KGSL_USER_MEM_TYPE_ION" is not declared. (iirc)
I fixed this (I think) by replacing CM10's qcom/display with caf's qcom/display
Second error: (Erroring out right now)
In-line kernel building. I'm getting a (possible) GCC compiler false error where it says
Code:
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5335:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5338:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: At top level:
cc1: error: unrecognized command line option "-Wno-unitialised" [-Werror]
Possible fix: for now turn off in-line kernel building until either error is solved.
Error 3 -- Removed in-line kernel building, but forgot to set device/semc/zeusc/prebuilt/kernel to copy to out/target/product/zeusc/kernel ... whoops
Error 4 -- The way things are sent to logcat has been changed from ICS
Code:
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_string:device/semc/msm7x30-common/liblights/lights.c:87: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_int:device/semc/msm7x30-common/liblights/lights.c:66: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function set_light_backlight:device/semc/msm7x30-common/liblights/lights.c:131: error: undefined reference to 'LOGV'
Fixed by copying over liblights/ from jellybean version of msm7x30-common/
Error 5 -- Same error happens with msm7x30-common/libsensors/
Fixed the same way as error 4
Error 6 -- Last error I'm gonna talk about tonight:
I did (apparently) a half baked revert to using a prebuilt kernel & it just bit me in the butt. I'll fix it tomorrow & keep updating this.
Fixed it by using half of FXP's custombootimg.mk where it calls (PRODUCT_OUT)/kernel instead of (TARGET_PREBUILT_KERNEL)
Anybody else up for learning with me & briniging JB to the Play?
Pax
UPDATE: Pre-alpha release are available here: http://www.mediafire.com/?6ggud46a7c6cq
Latest kernel is here: http://forum.xda-developers.com/showpost.php?p=29498363&postcount=233
Remember, this is an alpha, a lot of stuff does not work. Please logcat any errors you find, otherwise (unless it's something like baseband unknown) I WILL IGNORE THEM
What Works:
CDMA Data
Calls
SMS
AUDIO!!
HW Video
GPS
What Doesn't Work:
Haven't tested to much, you guys tell me
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
sasukekun67 said:
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
Thank you, I think for JB CM wants to use -O2 when compiling so I'm not gonna touch that one (for now)
A Good place to start would be with Keiran's building ICS tutorial with some changes.
First off, I'm using Ubuntu 10.04 LTS, but Ubuntu 12.04 LTS *should* work (no guarantees)
To download the vendor tree (vendor/semc)
use this instead of what Keiran has (koush cleaned out a lot of the vendor trees out of his git, and mine is outdated)
Code:
git clone https://github.com/kali-/proprietary_vendor_semc.git -b ics semc
also, I'm using the ICS device tree (same as keiran) instead of JB because the JB tree's are not 100% functional right now.
Pretty much if you follow that (& I suggest instead of doing make -j# bacon do mka bacon) & run into any errors, i'll help with whatever suggestions I might have (or anybody else)
Note: If somebody needs help trying to build AOKP, I'll help, but I'm not as familiar with the source as I am with CM
Pax
Also, before I forget, here a how-to sync caf's (code aurora forums) repo (similar to cm/AOSP/etc)
https://www.codeaurora.org/xwiki/bin/QAEP/
The branch I synced was jb.
Pax
Sent from my R800x using Tapatalk 2
First build is complete, I'm need to make a nanadroid & flash a new kernel (I'm on keics/CNA right now so it'll be a little bit before I post results )
Pax
hi,
it won't boot on sony ericsson hdpi devices without msm.... changes (look at mini pro thread you will find a lot of usefull information about it)
you need to enable triple buffer in the kernel
Thanks Nickholtus, i'll look into it.
Status 6 error in the update-script (really? off the cm-10 building ?!?!) so i'm working on that now...
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
nickholtus said:
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
Click to expand...
Click to collapse
I'll probably base it off either FXP or Mjolnir's kernel (sorry Lupus)
[sritke]Do you have a link with a how-to add in triple buffer? [/strike] CAF!! - https://www.codeaurora.org/gitweb/q...it;h=50c3bc621e2cf0c3587b1827d931738d148c33d8
UPDATE: Nickholtus, it's not this easy, is it?!?! https://www.codeaurora.org/gitweb/q...;hpb=1125e58c5744e1ad833e30e5d2a74eb6dca1ca20
Also, if anybody wants to try to fix the update-script, i've attached it
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
edit:
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
nickholtus said:
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
---------- Post added at 09:03 PM ---------- Previous post was at 08:58 PM ----------
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
Click to expand...
Click to collapse
Here's the best diff (all 3) i've found for the commit
https://www.codeaurora.org/gitweb/q...ff;h=acffb1675f468a85f528e01707f3fa98f45b77f8
i am going ask kamarush and see what he thinks
he thinks it can probaply fix it
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Sythedragon said:
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Click to expand...
Click to collapse
hahaha, different type of scripts, but thanks for the idea
Pax
Also: Made the changes in the kernel I have on hand, fxp's from cm9/10 source. I've added in the correct stuff to cyanogen_zeus_defconfig & mach-msm/board-semc_zeus.c as soon as I'm done downloading Doom's ndk, i'll try & build it & see if it works
Pax
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
nickholtus said:
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
Click to expand...
Click to collapse
I was, then I got arrowed in the knee
Or i would be, but then my git clone downloads at ~200 kb/s
Nickholtus,
Here's a test kernel, the changes are in the zImage, the ramdisk is FXP's from well, it's a source build off code from yesterday.
thanks
going to try it now
still the same error
edit: i need to get adb working
doesn't find the device
Lemme look into it, i'll test it out shortly (trying to get my build of cm10 to install )
Pax
Edit: Nickholtus, could you post a link to your build, mine just doesn't want to work
Pax
Edit 2: I think it's because i'm coming from CNA to CM10, i'm gonna build cm9 then retry with that
Pax
i can't upload my build, the upload speed here is 15kbps atm
How does one port ROMs to another phone? I'm looking to try and port Xylon to the Find 5.
Sent from my X909 using xda app-developers app
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
if you are building from source:
Find the 4.2.2 source code of the ROM you want to port
Get the manifest.
Add the CM10.1 device/kernel tree and proprietary libs in the .repo/local_manifest/roomservice.xml
sync all the repos
(do whatever the source might need you to set up: EG paranoid android, need you to setup your device properly in vendor/pa/* files)
compile. Fix any problems(maybe missing files, etc)
you could try a non-4.2.2-based ROM to port, but you'll run into more incompatibility issues to fix
mbh87 said:
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
Click to expand...
Click to collapse
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
newbcake said:
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
No, build from source since it's available.
mbh87 said:
No, build from source since it's available.
Click to expand...
Click to collapse
You mean Oppo's source or AOSP from Google? I presume AOSP
Sent from my X909 using xda app-developers app
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
paperWastage said:
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
Click to expand...
Click to collapse
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
newbcake said:
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
Click to expand...
Click to collapse
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
paperWastage said:
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
Click to expand...
Click to collapse
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Well, I removed the HTC lines from manifest.xml (maybe not a good idea?) but anyway, it finished syncing after.
mbh87 said:
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Click to expand...
Click to collapse
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
paperWastage said:
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
Click to expand...
Click to collapse
Understood. I'm syncing up the Cm10 now. Thanks!
Is is best to do this all on Linux, Mac, or Windows?
It isn't possible to do it on windows so one of the other two.
mbh87 said:
It isn't possible to do it on windows so one of the other two.
Click to expand...
Click to collapse
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
newbcake said:
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
paperWastage said:
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
Click to expand...
Click to collapse
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
newbcake said:
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
Click to expand...
Click to collapse
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file/line might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast/lunch & mka
paperWastage said:
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast & mka
Click to expand...
Click to collapse
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
newbcake said:
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
Click to expand...
Click to collapse
you could source the log for errors
or just run the compile script again and again.... the scheduler will continue building other packages, but it'll come to a point where it can't build anything else without that broken package.... and hence, the error in the log will be obvious(since everything else is already built, no logs from them)
it should be an error-free compile, but sometimes things could happen (a small tweak in package/A gives some problems when compiling with package/B)
I would say, most likely there's some build package incompatibility in your system.
Hi there,
Today I set up my machine to start building omni Rom for my Nexus 7 gsm (tilapia)
I followed the guide from the wiki for the Nexus 4 and changed it to suit the tilapia.
After I finished I got some errors about grouper Commons files missing so I guessed that the tilapia builds rely on the grouper(Nexus 7 wifi) and executed breakfast for grouper, too.
Afterwards the build started, however it gave me an error /warning to begin with
"device/asus/tilapia/omni.Dependencies file not found"
As mentioned before, the build started nevertheless.
Will this render my build useless or is it one of the warnings that might occur without harm?
If so, How can I fix it?
Sent from my Nexus 7 using xda app-developers app
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
dibblebill said:
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
Click to expand...
Click to collapse
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I've seen it said that you must have 4gb available, but I don't know. I can do a Tilapia build for you after Xmas if you like.
Sent from my Nexus 10
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
make core/java/android/
make packages/SystemUI/
make policy/src/com/android/internal/policy/impl/
make services/java/com/android/server/
Click to expand...
Click to collapse
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
punshkin said:
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
Click to expand...
Click to collapse
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
dibblebill said:
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
Click to expand...
Click to collapse
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Story runs thus.
I run a custom desktop with a 2nd generation Intel i7 at 3.06GHz (quad-core, Hyperthreading), 12GB triple-channel XMP RAM, and a good graphics card. 1.5TB hard drive. I have WIndows 7 on that. I procured, in exchange for beer to an adult of legal age, a 80GB, 7200RPM notebook HDD which I put Linux on, and build on that. I'm replacing that 80GB drive with a new 3.5" 1TB drive. 64MB of cache. I plan to give it a ccache of around 50GB. Since I boot into a full Linux installation, I get to use the full power of that CPU and RAM, and boy does compilling Android kick that CPU's ass.
well my build core failed (no make file)
I added 16Gb swap and run over night and see what happens
I'm not done with this yet
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
punshkin said:
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Click to expand...
Click to collapse
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
dibblebill said:
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
Click to expand...
Click to collapse
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
punshkin said:
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
Click to expand...
Click to collapse
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Tweakecho said:
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Click to expand...
Click to collapse
thank you, i just glanced over it but it seems very helpful
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
punshkin said:
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
Click to expand...
Click to collapse
do you clear before you build again? make clobber will clean up your "out" with out killing your build times to bad as far as i can tell. All you need to do is get the proprietary blobs for the grouper from either CM or Google and let them place themselves in the Vendor/asus/ directory and then you can make breakfast grouper to pull down the needed repos. my grouper specific stuff is only ~70 MB so it wont be to bad for your Hard drive i don't think. so you'd have to pull down some other radio stuff extra is about all.
I do think doing the builds together will double the size of the output as now you will have an OUT/product/Grouper as well as a OUT/product/Tiliapia... but i'm just making assumptions
If anything you could build them one at a time.
I'm sure i'll be corrected by one of the real dev's if i'm wrong...
EDIT: did some digging in to all the directories and it looks like mose of the stuff is already there for tiliapia in my repo so you should have the grouper stuff too.... i think.. lol