Hi guys I occured an error while trying to compile my own rom .. I'm actually a starter to developing roms .. and so I tried compiling a Stock 4.0.4 rom for the nexus S and I got this error:
Text version :
host C++: libLLVMJIT <= external/llvm/lib/ExecutionEngine/JIT/OProfileJITEventListener.cpp
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default]
<built-in>:0:0: note: this is the location of the previous definition
host C++: libbccExecutionEngine <= frameworks/compile/libbcc/lib/ExecutionEngine/Compiler.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
host C++: libbccExecutionEngine <= frameworks/compile/libbcc/lib/ExecutionEngine/FileHandle.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libbccExecutionEngine_intermediates/FileHandle.o] Error 1
make: *** Waiting for unfinished jobs....
cc1plus: all warnings being treated as errors
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libbccExecutionEngine_intermediates/Compiler.o] Error 1
[email protected]:~/ICS_SOURCE#
.. Can anyone help me ? not sure what to do ..
I was using this video ; http://www.youtube.com/watch?v=OS5c_ws_N7g
There is a makefile in framework/compile
Find the package. The fix is similar to this. Its because of your gcc version.
https://github.com/Rom2012/android_...mmit/2762b8375e1b0185b910614a7cb5ea59ebed08d7
Edit: looks like frameworks/compile/libbcc
Sent from my Nexus S 4G using xda premium
lithid-cm said:
There is a makefile in framework/compile
Find the package. The fix is similar to this. Its because of your gcc version.
https://github.com/Rom2012/android_...mmit/2762b8375e1b0185b910614a7cb5ea59ebed08d7
Edit: looks like frameworks/compile/libbcc
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm sorry can you help me out a little? I'm a HUGE noob .. I've been trying to make B2G and ICS roms .. I'm actually learning how to.. not TO familier with ubuntu, only used it a couple of times .. so can you dumb it down a little ? :$
smoke_weed said:
I'm sorry can you help me out a little? I'm a HUGE noob .. I've been trying to make B2G and ICS roms .. I'm actually learning how to.. not TO familier with ubuntu, only used it a couple of times .. so can you dumb it down a little ? :$
Click to expand...
Click to collapse
Go into your build folder.
then
Code:
cd frameworks/compile/libbcc
Open Android.mk, remove -Werror
lithid-cm said:
Go into your build folder.
then
Code:
cd frameworks/compile/libbcc
Open Android.mk, remove -Werror
Click to expand...
Click to collapse
Hi,
I also have this problem while compiling.
I try to find -Werror but I cannot find it in the file.
I am running Ubuntu 11.10 and I followed all instruction on source.android.com
This is my error.
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libbccExecutionEngine_intermediates/FileHandle.o] Error 1
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libbccExecutionEngine_intermediates/Compiler.o] Error 1
Thanks
I don't have -werror also ..
I also don't have -Werror in Ubuntu 13.04 or 12.10 or 12.04
So which switch is he talking about?
The correct file for -Werror is another one
Hi, the folder is ok but the file is not "Android.mk" but "libbcc-config.mk"
Before: libbcc-config.mk:libbcc_CFLAGS := -Wall -Wno-unused-parameter -Werror
After: libbcc-config.mk:libbcc_CFLAGS := -Wall -Wno-unused-parameter
Best regards,
Iker De Echaniz.
lithid-cm said:
Go into your build folder.
then
Code:
cd frameworks/compile/libbcc
Open Android.mk, remove -Werror
Click to expand...
Click to collapse
---------- Post added at 03:51 PM ---------- Previous post was at 03:24 PM ----------
Although the file I said previously is the correct one to eliminate -Werror, a better solution exists.
code.google.com/p/android/issues/detail?id=20795
Best regards,
Iker De Echaniz
deviker said:
Hi, the folder is ok but the file is not "Android.mk" but "libbcc-config.mk"
Before: libbcc-config.mk:libbcc_CFLAGS := -Wall -Wno-unused-parameter -Werror
After: libbcc-config.mk:libbcc_CFLAGS := -Wall -Wno-unused-parameter
Click to expand...
Click to collapse
Related
Requirements :
OS linux Ubuntu 12.04 32bits
2Gb RAM with 3Gb swap or above
Processor dual core or above
120Gb Harddisk or above
Fast internet connection ( i have no this )
First download this file
Installer SDK and Build packages by squadzone modified for me
you will get installerBuildRomGalmin.sh , run this file via Terminal on Ubuntu!
Code:
chmod a+x ~/installerBuildpackages.sh
installerBuildpackages.sh
Create the Directories
You will need to set up some directories in your build environment.
To create them:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Enter the following to download make executable the "repo" binary:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Device repo !
clone its
choose branch master
put on device tree or replace totoro folder on device tree
(/device/samsung/totoro)
Vender folder clone its
pu on vendor folder !
(/vendor/samsung/totoro)
Download RomManager
NOTE: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
~/android/system/vendor/cyanogen/get-rommanager
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Galaxys2.
. build/envsetup.sh && brunch totoro
Notes :
based on tutorial for galaxy mini by squadzone
the device repo created for me ( add credits if you use its )
sorry bad english !
changelog :
1.0
-initial tutorial for cm7 galaxy y ( may need some modifications! )
reserved for more updates if necessary !
Thanks for this buddy :good:
OFF : Any news about CM9 ?
wow.. reserved sir whitexp.. long time no post? D
I WIIL TRY IT BOR
By SOMKLL
But this Cyanogen has the same bugs,right?
whitexp what about cm9 ? when will u continue xD
and great guide
This message is COPYRIGHTED to me and stolen from:My post
Cyanogen 7/9 only get developed again when the gpu driver become released
Awesome tutorial sir...
Just one question...if we still have GPU restrictions while compiling CM7/9/10, then what is the use of the tutorial? Is there any update I should be aware of?
I'm not at all disrespecting OP's efforts...I respect him...he is doing commendable job for this device..hat's off! this question is just out of curiosity!
everyone needs brodcom drivers,without it nothing is possible.
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Well it's still possible to boot it, so yeah. It's a handy tutorial, LEARN to appreciate guys! That's the reason why SGY devs are leaving, 1 by 1, because of you people that whine! Thank them for the effort!
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Without this kind of tutorial and with gpu drivers will you make cm7 for sgy????
Awesome tutorial sir!!
Tutotial is good.no doubt.I said drivers are a stumbling block.
PREMOLIKES said:
Tutotial is good.no doubt.I said drivers are a stumbling block.
Click to expand...
Click to collapse
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Mohamed.Anwar said:
Thanks for this buddy :good:
OFF : Any news about CM9 ?
Click to expand...
Click to collapse
what gaming rom r using
Exellent tut buddy.:thumbup::thumbup:
sent while doin' some burnouts
hell_lock said:
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
cosminx13 said:
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
Click to expand...
Click to collapse
A suggestion from me.you can use both os like dualboot.for info about this try google
MANY GREEEEETZ!!!
Hello guys i'm here with my first guide of how to build cyanmobile from source for galaxy fit ......
As you all might know cyanmobile went opensource thanks to squadzone now we can compile it from source with our own modifiactions.....
Requirements
1)Linux machine (recommended 64bit and ubuntu) with atleast 50gb free space
2)Common sense of how to use google and fix errors
3)Basic knowledge of git and its commands
4)A possibilty of bricking your fit
5)A fast and stable internet connection
now lets get started
Assuming we have linux installed
installing required build packages
from terminal
HTML:
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 sun-java6-jdk pngcrush schedtool
Note:- All the packages are important dont skip any of them
now making the directories to download the source
HTML:
mkdir -p ~/bin
mkdir -p ~/android/system
here mkdir stands for make directory
~ refers to your home folder (incase if you are a beginner)
Next
making the repo command executable
copy paste this terminal
HTML:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Reboot your system after executing this
This defines the repo command or the repo command usable on your machine
chmod is giving permissions to the folder a+x is the permissions given don't go deep into this.
Next
Downloading the source
i will be referring execute to copy pasting in the terminal
HTML:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b gingerbread
now
repo sync
alternatives
repo sync -jx
here x can be anything depends on your internet speed ther will x number of simultaneous download if you use the arguement
like if you use
repo sync -j4
There will 4 downloads going on simulatneously
Next after the source has been downloaded you will find someting like this...
syncing working tree 100
now you have the source downloaded
Preparing the build environment
install java jdk6 or jdk 5 using this tutorial
http://codingforme.wordpress.com/2012/05/14/installing-oracle-java-jdk-6-or-7-on-ubuntu-12-04/
Install the android sdk following this tutorial
http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-ubuntu-11.04
not testsed on jdk 7 so better use 6 or 5
fix its path using "export PATH=$PATH:"ur sdk path""
ur sdk path depends on where you install it
install adb using this guide
http://forum.xda-developers.com/showthread.php?t=921169
Connect your phone with usb debugging enabled and execute this
preferable do this when you are on a cm based rom ..
HTML:
adb devices
if you see something like this its working for you
HTML:
List of devices attached
S5670efac482b device
now go to device > samsung > beni execute extract-files.sh as root use sudo and drag that to terminal and hit enter
now cd into the root of your source folder
HTML:
cd ~/android/system
then
HTML:
source buid/envsetup.sh
HTML:
lunch
you will see all the build properties something like this
HTML:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.8
TARGET_PRODUCT=cyanogen_beni
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
now type make -jx otapackage
x depends on your hardware more it is faster the build
you will find the built one in out/samsung/beni /cm--xxx.zip
Flash it and enjoy
credits
wilfredcool007
vishwanthptl
sakindia123
yajnab
ravi h basawa
adit_pat
squadzone
google
xda
without these guys it wouldnt be possible pree thanks for them plz
1 st reserved
Thumbs up
Nice guide ajay :good:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
yajnab said:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
Click to expand...
Click to collapse
i am too doing a list of common errors encountered and will update the op
speed_bot said:
i am too doing a list of common errors encountered and will update the op
Click to expand...
Click to collapse
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
yajnab said:
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
Click to expand...
Click to collapse
dude do this remove all devices and sync only beni and tass the source is small and use aosps prebuilt the download is only 3gb bro...and can plz upload the prebuilt directory for me i will upload frameworks and devices by tmrw for you..........plz i need the prebuilt directory
You rock man, keep up the good work.. thank you..
praveen_kalasa said:
You rock man, keep up the good work.. thank you..
Click to expand...
Click to collapse
thanks bro..
Nice Work
Very useful Guide for Begineers. Keep this thread updated
RishabhAd said:
Very useful Guide for Begineers. Keep this thread updated
Click to expand...
Click to collapse
but only few people responded to it so what can i update with
??
hi.i am trying to build from your how to...will report ...thank you for this...
desalesouche said:
hi.i am trying to build from your how to...will report ...thank you for this...
Click to expand...
Click to collapse
im already compiling for your device
How to build cyanmobile x from source for p500?
thanks
x-dira said:
How to build cyanmobile x from source for p500?
thanks
Click to expand...
Click to collapse
just choose p500 during lunch
building for huawei u8800pro and u8860
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Nice guide :thumbup:
I'll try it for GalaxyW
desalesouche said:
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Click to expand...
Click to collapse
u need kernel 2.6 for gb 3.x supports only ics and above.android 4.2.2 is buildable provided u have all drivers and other binaries
K_TECH said:
Nice guide :thumbup:
I'll try it for GalaxyW
Click to expand...
Click to collapse
dude this guide is for galaxy fit but u can build it for w or any device by using the tress specific for that device.
Bump
I wanna try to port this ROM to the LG e739, but I have no idea what to do at this point. I downloaded the sources, but the device tree I have from cm7.2 is just plain, it lacks everything else the other devices have and to be honest I'm overwhelmed. Any help is greatly appreciated
Hi, i want to compile a custom kernel from cink king JB sources. After a lot of studies of the linux kernel, its modules and configuration, i started a compilation on Ubuntu 12.04 with all ndk and toolchains for android development. After a lot of errors during the kernel compilation that i solved, there is an error that i can't solve and so i need yourhelp.
I write:
$ [email protected]:/kernel# make TARGET_PRODUCT=mt6577 MTK_ROOT_CUSTOM=../mediatek/custom
The compilation begins and it stucks whit this error:
Make: *** No rule to make target "include/config/auto.conf" needed in "include/config/kernel.release". Exiting.
I googled a lot, but nothing helped me.
Sorry for scarry english.
Sent from my GLADIATOR (a110) using xda app-developers app
tatto97 said:
Hi, i want to compile a custom kernel from cink king JB sources. After a lot of studies of the linux kernel, its modules and configuration, i started a compilation on Ubuntu 12.04 with all ndk and toolchains for android development. After a lot of errors during the kernel compilation that i solved, there is an error that i can't solve and so i need yourhelp.
I write:
$ [email protected]:/kernel# make TARGET_PRODUCT=mt6577 MTK_ROOT_CUSTOM=../mediatek/custom
The compilation begins and it stucks whit this error:
Make: *** No rule to make target "include/config/auto.conf" needed in "include/config/kernel.release". Exiting.
I googled a lot, but nothing helped me.
Sorry for scarry english.
Sent from my GLADIATOR (a110) using xda app-developers app
Click to expand...
Click to collapse
Dude use motorola source wiko sources are not usable.
Thanks fo your answer. I will try Motorola source and post here for results.
Sent from my GLADIATOR using xda app-developers app
can anyone tell me why i am gettting this error
>>> build out/framework-miui-res.apk...
/home/pramod/patchrom/tools/apktool --quiet d -f -t miui /home/pramod/patchrom/miui/XHDPI/system/framework/framework-miui-res.apk out/framework-miui-res
/home/pramod/patchrom/miui/src/frameworks/miui/core/res/res/values-xhdpi/alias.xml:1: error: Error parsing XML: not well-formed (invalid token)
make: *** [out/framework-miui-res.apk] Error 1
I think if u want to make a rom. You must make a thread of disscusion, for easier to ask.
Sent from my GT-I8262 using XDA Premium 4 mobile app
Are you trying to compile a ICS patchrom using a jellybean stock rom? xDDDD.The branch of that source tree is ICS not Jellybean...Try to sync the correct repo first with $ repo init -u git://github.com/MiCode/patchrom.git -b jellybean
Hi everybody!
Finally, our LG G2 got an Developer Discussion area. So I decided to create this thread:
This thread is set up for people who want to compile roms for our great device. Perhaps you compiled already
a rom sucessfull but the rom isn't booting? Post it here! Errors during the compile process? Again, write it in this
section here. Apps are crashing on your compiled rom? In here again!
This thread should be kept clean, no offtopic, this means no questions when a rom will be published.
This area should only be for devs or for people who want to get one.
Thank you and happy compiling!!!
Flo0008 said:
Hi everybody!
I need help from devs please:
So, I built Slim LP for the D802 but my problem is I am stuck in a bootloop (at the LG logo) after a clean installation.
I use the GCC 4.8 toolchain to compile the rom and the kernel.
Perhaps a dev can take a look on my local_manifest.xml if there are missing any needed repos.
Slim LP: https://github.com/Flo0008/android_scripts/blob/lp5.0/.repo/local_manifests/local_manifest.xml
Device tree:
https://github.com/Flo0008/android_device_lge_d802
https://github.com/Flo0008/android_device_lge_g2-common
I ran . build/envsetup.sh, then lunch slim_d802-userdebug and then make -j8 otapackage.
Do I have to run another command?
Thanks in advance!
Perhaps @arcardinal, have you an idea what causes the bootloop?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
How far do you get? Do you see Slim's boot logo? Also when you open the created zip, does everything look to be there? Like boot.img and such? Can you think of any more info?
RenderBroken said:
How far do you get? Do you see Slim's boot logo? Also when you open the created zip, does everything look to be there? Like boot.img and such? Can you think of any more info?
Click to expand...
Click to collapse
Thanks firstly for your help!
I get until the LG bootlogo, not further. I didn't see the bootlogo of Slimrom.
I have the same problem with AOSP, I don't get further than the LG logo.
SlimLP: After some time (at the LG logo) the phone starts vibrating but not more.
I flashed the roms via TWRP recovery and my phone is running the latest KK version 20h.
The boot.img is there and seems ok with a size of about 5.7Mb in the .zip file, the system folder seems to be complete and the META folder is also there.
In the thread of another device I read something about a problem with com.qualcomm.location in system/app or anything but I can't find this file there.
There were no errors during the flash-process on my device too. A problem I recogniced on AOSP LP was when I rebooted the device after flashing the rom with TWRP, that I got on a screen where on the top left is written:
[650] Fastboot mode started
[700] udc_start()
For both roms I used the kernel source of lg-dev's repo. One weird thing I recognized on AOSP was that the .zip file has only about 166Mb, SlimLP has a .zip size of aroung 195Mb.
I was thinking about that I am perhaps missing any device specific repo here on my local_manifest: https://github.com/Flo0008/android_scripts/blob/aosp_g2/.repo/local_manifests/local_manifest.xml
or I asked myself if I have to run any file like extract-files.sh in the device repo here: https://github.com/Flo0008/android_device_lge_d802/tree/aosp5.0.
One more thing I tried was to replace the boot.img of both roms with that one from CM's. Nevertheless nothing changed, the rom didn't boot up.
If you need more information please tell me.
Thank you very much!!!
Flo0008 said:
Thanks firstly for your help!
I get until the LG bootlogo, not further. I didn't see the bootlogo of Slimrom.
I have the same problem with AOSP, I don't get further than the LG logo.
SlimLP: After some time (at the LG logo) the phone starts vibrating but not more.
I flashed the roms via TWRP recovery and my phone is running the latest KK version 20h.
The boot.img is there and seems ok with a size of about 5.7Mb in the .zip file, the system folder seems to be complete and the META folder is also there.
In the thread of another device I read something about a problem with com.qualcomm.location in system/app or anything but I can't find this file there.
There were no errors during the flash-process on my device too. A problem I recogniced on AOSP LP was when I rebooted the device after flashing the rom with TWRP, that I got on a screen where on the top left is written:
[650] Fastboot mode started
[700] udc_start()
For both roms I used the kernel source of lg-dev's repo. One weird thing I recognized on AOSP was that the .zip file has only about 166Mb, SlimLP has a .zip size of aroung 195Mb.
I was thinking about that I am perhaps missing any device specific repo here on my local_manifest: https://github.com/Flo0008/android_scripts/blob/aosp_g2/.repo/local_manifests/local_manifest.xml
or I asked myself if I have to run any file like extract-files.sh in the device repo here: https://github.com/Flo0008/android_device_lge_d802/tree/aosp5.0.
One more thing I tried was to replace the boot.img of both roms with that one from CM's. Nevertheless nothing changed, the rom didn't boot up.
If you need more information please tell me.
Thank you very much!!!
Click to expand...
Click to collapse
Did I understand right that you are on a KK Bootloader? You need to be on a JB Bootloader for all of the current LP Source out right now. Try that and see if you get any further.
Wow..finally someone tryin to port slimlp..hope u get it Working??
Thanks again. Yes I am on KK bootloader but I dont understand why Cyanogenmod 12 is working. But thanks for the information, I will try it.
Sent from my LG-D802 using XDA Free mobile app
So, what I did now: I flashed the JB baseband on my device via TWRP, rebooted to recovery and flashed SlimLP, but I still get a bootloop.
Or should I flash the .kdz of a JellybeanRom?
And do you know how to fix this error? I get it when I try to build AOSP LP.
/bin/sh: 1: cd: can't cd to out/target/product/d802/obj/KERNEL_OBJ
make[1]: Entering directory `/home/fabio/rasta/kernel/lge/msm8974'
Makefile:121: *** output directory "out/target/product/d802/obj/KERNEL_OBJ" does not exist. Stop.
make[1]: Leaving directory `/home/fabio/rasta/kernel/lge/msm8974'
make: *** [out/target/product/d802/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
Sent from my LG-D802 using XDA Free mobile app
First:
In root directory of rom: make clean -> this should fix build error.
My proposition:
1. repo init -u https://github.com/SlimRoms/platform_manifest -b lp5.0-caf
2. roomservice.xml need to looks like:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
# Device Specific part
<project path="device/lge/d802" name="Flo0008/android_device_lge_d802" revision="lp5.0" remote="github" />
<project path="device/lge/g2-common" name="Flo0008/android_device_lge_g2-common" revision="lp5.0" remote="github" />
<project path="kernel/lge/msm8974" name="Flo0008/android_kernel_lge_msm8974" revision="cm-12.0" remote="github" />
<project path="vendor/lge" name="Flo0008/proprietary_vendor_lge" revision="cm-12.0" remote="github" />
</manifest>
Click to expand...
Click to collapse
3. repo sync.
4.
. build/envsetup.sh
brunch d802
Try this if you want.
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
When finish building of DU will try SlimLP
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
SlimLP has a .zip size of aroung 195Mb.
Click to expand...
Click to collapse
Size of compiled CM12 is about 240 MB -> something is missing in your build...
---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------
look here:
https://github.com/TheMuppets/proprietary_vendor_lge/blob/cm-12.0/d802/d802-vendor-blobs.mk
See how much blobs is there...
insteed of using your blobs try TheMuppets's blobs:
https://github.com/TheMuppets/proprietary_vendor_lge
add this to roomservice.xml
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
My last proposition is to try using cm device tree and kernel...
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
# Device Specific part
<project path="device/lge/d802" name="CyanogenMod/android_device_lge_d802" revision="cm-12.0" remote="github" />
<project path="device/lge/g2-common" name="CyanogenMod/android_device_lge_g2-common" revision="cm-12.0" remote="github" />
<project path="kernel/lge/msm8974" name="CyanogenMod/android_kernel_lge_msm8974" revision="cm-12.0" remote="github" />
<project path="vendor/lge" name="TheMuppets/proprietary_vendor_lge" revision="cm-12.0" remote="github" />
</manifest>
Click to expand...
Click to collapse
Then make some changes in device/lge/d802 .
Thanks for your answer. I use already CM device repos (from lg-devs), all device specific folders are picked from them and I modified only some things for SlimLP.
I have to use the caf branch of Slim?
Sent from my LG-D802 using XDA Free mobile app
Flo0008 said:
Thanks for your answer. I use already CM device repos (from lg-devs), all device specific folders are picked from them and I modified only some things for SlimLP.
I have to use the caf branch of Slim?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
I think this is problem with blobs... Try using TheMuppets and will see
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
Yes, need CAF branch
Is Rashed using the caf branch for CM too?
Sent from my LG-D802 using XDA Free mobile app
Flo0008 said:
Is Rashed using the caf branch for CM too?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
I'm building my own CM12 daylies and using standard CM sources.
EDIT:
Building and not sharing, only for my personal use.
@RenderBroken
Can you or anybody else help me with this build error on AOSP Lollipop?
Target boot image: /data1/Flo0008/aosp_g2/out/target/product/d802/boot.img
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
-o|--output <filename>
device/lge/g2-common/releasetools/mkbootimg.mk:47: recipe for target '/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img' failed
make: *** [/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img] Error 1
make: *** Waiting for unfinished jobs....
Thanks in advance.
Wished i had knowledge i would help.
If u need any tester for d802 u can Holla at me..
Maybe ASK @varund7726 Compiler of resurection remix he did Good job on the Rom...maybe he can give u advice..since he is a Good dev who also helps others.
Good luck my friend..
Flo0008 said:
@RenderBroken
Can you or anybody else help me with this build error on AOSP Lollipop?
Target boot image: /data1/Flo0008/aosp_g2/out/target/product/d802/boot.img
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
-o|--output <filename>
device/lge/g2-common/releasetools/mkbootimg.mk:47: recipe for target '/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img' failed
make: *** [/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img] Error 1
make: *** Waiting for unfinished jobs....
Thanks in advance.
Click to expand...
Click to collapse
This error means that the mkbootimg tool you have is not the correct one. Apparently there are more than one out there and the other supports different flags. Use the one here:
https://github.com/RenderBroken/mkbootimg_tools
Also CAF (to me) doesnt seem to be ready as a Daily Driver. Are you just wanting to mess around or get out a fully functioning build? I do know that LG-Devs CAF branch is still being worked on. Not sure about TheMuppets but they are always solid. Still LP CAF is not stable yet.
---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------
reaper61616 said:
First:
In root directory of rom: make clean -> this should fix build error.
My proposition:
1. repo init -u https://github.com/SlimRoms/platform_manifest -b lp5.0-caf
2. roomservice.xml need to looks like:
3. repo sync.
4.
. build/envsetup.sh
brunch d802
Try this if you want.
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
When finish building of DU will try SlimLP
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
Size of compiled CM12 is about 240 MB -> something is missing in your build...
---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------
look here:
https://github.com/TheMuppets/proprietary_vendor_lge/blob/cm-12.0/d802/d802-vendor-blobs.mk
See how much blobs is there...
insteed of using your blobs try TheMuppets's blobs:
https://github.com/TheMuppets/proprietary_vendor_lge
add this to roomservice.xml
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
My last proposition is to try using cm device tree and kernel...
Then make some changes in device/lge/d802 .
Click to expand...
Click to collapse
Great Info! Thanks for chiming in.
Syncing repo of SlimLP
Ok, keep me up to date
Flo0008 said:
Ok, keep me up to date
Click to expand...
Click to collapse
Have no good news...
After build zip is 190 MB... :/
Give it up today. Tomorrow will check what is wrong.
@RenderBroken
I built AOSP LP again today, build size seems ok with around 200Mb but when I tried to flash the rom I gout stuck in TWRP. A kind of a flashloop (instead of bootloop) - anyway, the device didn't get bricked althought I shut down the phone after that. This means the .zip file didn't flash. Any ideas?
And where can I paste your mkbootimg_tools repo to build the boot.img with it?
And one more thing: In lollipop (Cyanogenmod 12) all the system files and so on get compressed into a .dat file, right? I have the problem, for me there isn't such a file in my .zip file ... Do you know what to do against this problem?
I hope I don't bother you too much ...
reaper61616 said:
Have no good news...
After build zip is 190 MB... :/
Give it up today. Tomorrow will check what is wrong.
Click to expand...
Click to collapse
But the size shouldn't be that problem ... Did the build boot up?