Database Users

[Q] Problem compiling jb for P3113

Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?

rainfalls said:
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
Click to expand...
Click to collapse
To build it proper you need...
https://github.com/AOKP/android_device_samsung_p3100
https://github.com/AOKP/android_device_samsung_p3113
And:
https://github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.

cmenard said:
To build it proper you need...
github.com/AOKP/android_device_samsung_p3100
github.com/AOKP/android_device_samsung_p3113
And:
github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
Click to expand...
Click to collapse
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated

rainfalls said:
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
Click to expand...
Click to collapse
Yup. Just use the links I provided and you should be able to build just fine.

cmenard said:
Yup. Just use the links I provided and you should be able to build just fine.
Click to expand...
Click to collapse
Ok. I've started from scratch, deleted all the things in the samsung folders. i git clone p3113, p3100 and vendor. So now I have p3113,p3100 and samsung_vendor folders. Do I have to pull the p31xx folders from vendor and paste it directly into the samsung one?
when I do a ./extract-files.sh, i don't have any error until there ->
180 KB/s (14268 bytes in 0.077s)
453 KB/s (45380 bytes in 0.097s)
remote object '/system/lib/libsec-ril.so' does not exist
120 KB/s (9620 bytes in 0.077s)
172 KB/s (13768 bytes in 0.077s)
My p3113 is connected with usb debugging and appears correctly in adb devices.
Plus, nothing as been added into the p3113 folders at the end of the extract-files. At the end of the extract, should a vendorsetup.sh file supposed to be created?
Sorry but I'm a noob looking to learn something
thanks
EDIT: ok I found what was wrong with the vendor.. it's not going into /device/samsung folder but /vendor/samsung/p31xx right? still having the libsec-ril issue tho..

Do you have any hint cmenard?

You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10

MultipleMonomials said:
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Yeah I already added the vendor setup file manually. I'll resync my jb tonight maybe something went wrong. I'll have to figure out the extract file problem too. All this when I'll get back from work lol

Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.

imnuts said:
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
Click to expand...
Click to collapse
I was using it because I've followed the guide step by step but I was asking the same question myself. I'll retry again as soon as I go back home

I'm getting a bit farther now. Not compiling yet but.. will do soon.. when I'm trying to do a make -j4 otapackage, I'm getting a series and I wrote them in pastebin
http://pastebin.com/f3UP50ku
I'm using:
[email protected]:~/android$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
I'm kinda lost
thanks for your help!

You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10

MultipleMonomials said:
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Well.. this is what I've done so far
1. I downloaded java there http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html (jdk-6u34-linux-x64.bin)
2. Went to terminal chmod +x jdk-6u34-linux-x64.bin
3. Then /.jdk-6u34-linux-x64.bin == install successfull
4. sudo update-alternatives --config java -> to choose the last jdk I've installed (by default, OpenJDK is installed with ubuntu instead of java jdk)
still having the same output with java -version
still having same issues

I got the same problem too when I'm trying to compile.
pastebin.co m/wcSZq6wq
it stops there and nothing.
I'm using p3113, p3110 and p3100 folder from /github.co m/AOKP/
Any idea someone?
Thanks

Finally I've been able to compile it through the end. Now time for debugging... I got a bootloop (surprising eh!?)
http ://pastebin.co m/e6STwe0E
Any help will be appreciated!
thanks!
EDIT: I've uploaded my work so far right there:
https ://docs.google.c om/file/d/0B6GzemNaw2dRY3BTT0tPWDdKYnM/edit
REMEMBER it's bootloading!

Nobody have a clue?

[GUIDE] Build Your Own Android Kernel{Easiest and Fastest Way] [Using The NDK]

This is the quickest and easiest way to build your own Kernel using the Android NDK
Note:I will be reffering to the following
yourusername=the username that you are logged in to
devicecode=The codename for the device you are building a kernel for(Google it on what is the code name
Click to expand...
Click to collapse
Note:I am only showing you how to make it to be flashed via CWM. If you wan't a tuttorial on how to make a boot.img comment and i will make it.
What you will need
Ubuntu 12.04 or newer
A lot of patience
Click to expand...
Click to collapse
Step 1:Installing the required files
Open a terminal and type the following (copy-paste)
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
This will install the packages you need
Download the kernel source code for your device (This is important. We are going to build the kernel from this)
For HTC http://htcdev.com
For Samsung http://opensource.samsung.com/
Click to expand...
Click to collapse
Find your device and click Download
Download The NDK
Move the NDK and your device Kernel source code in your home folder
Extract both the NDK and your kernel source code
Rename the folder were you have the NDK installed to NDK. And rename the folder where you have the kernel installed to Kernel
Now we are ready to build.
Step 2:Tweaking the kernel
Navigate to the kernel folder
Code:
cd /home/[COLOR="red"]yourusername[/COLOR]/Kernel
Next we need to point the NDK tools to the kernel folder
Code:
export CROSS_COMPILE=/home/[COLOR="red"]yourusername[/COLOR]/NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
We've pointed the NDK tolls and now we can use the NDK to tweak the kernel
Next we need to clean the previous work just incase:
Code:
make clean && make mrproper
If everything goes well you are good to go. If you have an Error(s) then something is wrong.
Now we are ready.
Next we need to add the kernel features to the NDK so we can modife them
Firs open your kernel source code folder go to arch/arm/configs
Here you will all the configs.
We need only one. Find that. It is called:Yourdevicecode_somethingbalblabla.defconfig
Rename it to maker.defconfig
Now type this in your terminal
Code:
make maker.defconfig
Now we need to tweak those configs.
Code:
make menuconfig
A user interface will pop out showing you all the tweaks you can do. I am not going to show you whow to use it. Google it(Sorry don't have that enough space)
When you are ready close the UI and click SAVE
Step 3 Building
So we tweaked the Kernel and we are ready to build.
make -j# ARCH=arm
Click to expand...
Click to collapse
Note:The # means the number of CPU cores +1. For example my device has a quad core CPU and I will type
Code:
make -j5 ARCH=arm
This will build the Kernel. It will take about 10 minutes.
Step 4: Finalizing
Now that kernel is ready you will need to find a kernel flashable zip for your device(Just google it)
Download the zip file and leave it in your home folder.
Now got to your kernel source and go to arch/arm/boot and copy zImage
Paste your Zimage to the zip file and replace it.
Now we need the WI-FI modules otherwise your WI-FI will not be working
Go to the Kernel source code folder and go to driver/net/wireless/bcm4329_204 and copy bcm4329.ko
Got the zip file go to the System folder and replace it's bcm4329.ko with your bcm4329.ko
You are ready all you need to do is flash it.

mmm..interesting...i always build without the ndk,but simpy sdk.what's the advantages?
and i usually do the git clone to download all the sources,in my case nexus7 and maguro.
thanks for this!

Well i am just waiting for Samsung to release JB sources for N7000 to start learning on how to create my own kernel
This is a pretty good base! Thanks

Sorry if this is a stupid question but do we need 64 bit like we do for ROM compiling, or will this work fine for 32 bit (I'm running Ubuntu 12.10 32 bit). Also, roughly how much is there to download? Thanks

:good: Thanks! I'm use Ubuntu 10.04 64 bit don't know if can?

HTCDreamOn said:
Sorry if this is a stupid question but do we need 64 bit like we do for ROM compiling, or will this work fine for 32 bit (I'm running Ubuntu 12.10 32 bit). Also, roughly how much is there to download? Thanks
Click to expand...
Click to collapse
I am not sure. I think you can on 32 bit try it the download takes all together about 500 MB

TheWizardOfROMs said:
I am not sure. I think you can on 32 bit try it the download takes all together about 500 MB
Click to expand...
Click to collapse
Thanks, do you know how large all the files are once installed on the system (you might have guessed I'm slightly short of space atm)

HTCDreamOn said:
Thanks, do you know how large all the files are once installed on the system (you might have guessed I'm slightly short of space atm)
Click to expand...
Click to collapse
About 700 MB

sert00 said:
mmm..interesting...i always build without the ndk,but simpy sdk.what's the advantages?
and i usually do the git clone to download all the sources,in my case nexus7 and maguro.
thanks for this!
Click to expand...
Click to collapse
What are you building? If a whole ROM like AOSP,AOKP,PA or CM then they typically bundle the toolchain/kernel with the source, making this totally unneeded.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
HTCDreamOn said:
Sorry if this is a stupid question but do we need 64 bit like we do for ROM compiling, or will this work fine for 32 bit (I'm running Ubuntu 12.10 32 bit). Also, roughly how much is there to download? Thanks
Click to expand...
Click to collapse
No 32-bit is fine, just install the right libraries. I actually believe that you can compile a ROM on 32-bit as well.
Self-Plug http://forum.xda-developers.com/showthread.php?t=1748297

Also just to warn users, the above defconfig convention is just that, a convention. The author of a kernel can name the defconfig whatever they want, so it is something to keep in mind.
Sent from my SCH-R950 using Tapatalk 2

thewadegeek said:
What are you building? If a whole ROM like AOSP,AOKP,PA or CM then they typically bundle the toolchain/kernel with the source, making this totally unneeded.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
No 32-bit is fine, just install the right libraries. I actually believe that you can compile a ROM on 32-bit as well.
Self-Plug http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
i builded some kang rom for personal use,but lately only kernels (for my nexus devices and 2 emebedded system board like in my sig.

Thanks for the guide, but unfortunately I am getting errors during compilation:
Code:
make -j3 ARCH=arm
CHK include/linux/version.h
CHK include/generated/utsrelease.h
HOSTCC scripts/kallsyms
HOSTCC scripts/bin2c
CC scripts/mod/empty.o
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[2]: *** [scripts/mod/empty.o] Error 2
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
I am trying to compile the Andromadus 3.0 kernel for HTC Vision, I'd really appreciate some help. I'm using Ubuntu 12.10 32 bit and the Android NDK.

TheWizardOfROMs said:
This is the quickest and easiest way to build your own Kernel using the Android NDK
Note:I will be reffering to the following
Note:I am only showing you how to make it to be flashed via CWM. If you wan't a tuttorial on how to make a boot.img comment and i will make it.
What you will need
Step 1:Installing the required files
Open a terminal and type the following (copy-paste)
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
This will install the packages you need
Download the kernel source code for your device (This is important. We are going to build the kernel from this)
Find your device and click Download
Download The NDK
Move the NDK and your device Kernel source code in your home folder
Extract both the NDK and your kernel source code
Rename the folder were you have the NDK installed to NDK. And rename the folder where you have the kernel installed to Kernel
Now we are ready to build.
Step 2:Tweaking the kernel
Navigate to the kernel folder
Code:
cd /home/yourusername/Kernel
Next we need to point the NDK tools to the kernel folder
Code:
export CROSS_COMPILE=/home/yourusername/NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
We've pointed the NDK tolls and now we can use the NDK to tweak the kernel
Next we need to clean the previous work just incase:
Code:
make clean && make mrproper
If everything goes well you are good to go. If you have an Error(s) then something is wrong.
Now we are ready.
Next we need to add the kernel features to the NDK so we can modife them
Firs open your kernel source code folder go to arch/arm/configs
Here you will all the configs.
We need only one. Find that. It is called:Yourdevicecode_somethingbalblabla.defconfig
Rename it to maker.defconfig
Now type this in your terminal
Code:
make maker.defconfig
Now we need to tweak those configs.
Code:
make menuconfig
A user interface will pop out showing you all the tweaks you can do. I am not going to show you whow to use it. Google it(Sorry don't have that enough space)
When you are ready close the UI and click SAVE
Step 3 Building
So we tweaked the Kernel and we are ready to build.
Note:The # means the number of CPU cores +1. For example my device has a quad core CPU and I will type
Code:
make -j5 ARCH=arm
This will build the Kernel. It will take about 10 minutes.
Step 4: Finalizing
Now that kernel is ready you will need to find a kernel flashable zip for your device(Just google it)
Download the zip file and leave it in your home folder.
Now got to your kernel source and go to arch/arm/boot and copy zImage
Paste your Zimage to the zip file and replace it.
Now we need the WI-FI modules otherwise your WI-FI will not be working
Go to the Kernel source code folder and go to driver/net/wireless/bcm4329_204 and copy bcm4329.ko
Got the zip file go to the System folder and replace it's bcm4329.ko with your bcm4329.ko
You are ready all you need to do is flash it.
Click to expand...
Click to collapse
will work with an ics device like amazon kindle fire?
Sent from my KFTT using xda app-developers app

HTCDreamOn said:
Thanks for the guide, but unfortunately I am getting errors during compilation:
Code:
make -j3 ARCH=arm
CHK include/linux/version.h
CHK include/generated/utsrelease.h
HOSTCC scripts/kallsyms
HOSTCC scripts/bin2c
CC scripts/mod/empty.o
arm-eabi-gcc: No such file or directory
Is your PATH set correctly?
make[2]: *** [scripts/mod/empty.o] Error 2
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
I am trying to compile the Andromadus 3.0 kernel for HTC Vision, I'd really appreciate some help. I'm using Ubuntu 12.10 32 bit and the Android NDK.
Click to expand...
Click to collapse
Check your toolchain definition, looks like your path is wrong.

thewadegeek said:
Check your toolchain definition, looks like your path is wrong.
Click to expand...
Click to collapse
Thanks, you're right my path was wrong, but now I have fixed all the problems and it appears to compile successfully however there is no zImage in arch/arm/bin. Any suggestions? Thanks

HTCDreamOn said:
Thanks, you're right my path was wrong, but now I have fixed all the problems and it appears to compile successfully however there is no zImage in arch/arm/bin. Any suggestions? Thanks
Click to expand...
Click to collapse
Try building it again. Be sure to clean the source folder before you start

TheWizardOfROMs said:
Try building it again. Be sure to clean the source folder before you start
Click to expand...
Click to collapse
Thanks very much, I'd been recommended using Linaro tool chain instead and it works perfectly now, booting and WiFi and all. If I can learn some more advanced modding stuff to do to it then I'll release it in the Vision forums and I'll make sure to link to this guide

I installed Ubuntu on my windows laptop.my computer stars are 3Gigs of memory with 140 Gigs of available free space.Do I have enough space and is my laptop good enough to build kernels on.and I do use Ubuntu 12.04 to build kernels correct.I'm sorry I'm all new to this I just would like to be able to build a kernel for my sensation and HTC one which I will have next week.thanks very much for your time and expertise.
Sent from my HTC Sensation using xda app-developers app

rp56 said:
I installed Ubuntu on my windows laptop.my computer stars are 3Gigs of memory with 140 Gigs of available free space.Do I have enough space and is my laptop good enough to build kernels on.and I do use Ubuntu 12.04 to build kernels correct.I'm sorry I'm all new to this I just would like to be able to build a kernel for my sensation and HTC one which I will have next week.thanks very much for your time and expertise.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I compiled with Ubuntu 12.10 and only 2 GB of RAM, and only 30GB free space. The tool chain and kernel really doesn't use up much room at all. As long as you don't go OTT on the -jx bit (I do -j3 as I've got a lowly core 2 duo) you should be fine. By the way if you get errors and you're path is definitely correct, then try with the Linaro tool chain instead.

got an error something like, "make ** [vm.virtual], waiting for unfinished jobs..." then stops, going to try new defconfig and new toolchain

Firefox OS Porting to Motorola G

I and my friend are trying to port Firefox OS on Motorola G device. Because of our lack of experience in the field, we are stuck. Mozilla's documentation is not that helpful and we don't know at the moment how to continue.
What we did:
- created manifest xml for the device, based on unofficial cyanogenmod for Moto G.
- synced all sources
- added manually prebuilt kernel.
- tried to build everything but it doesn't build, of course, we don't know why.
The error seem to be:
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.

Welcome to the forums !
coldSense said:
I and my friend are trying to port Firefox OS on Motorola G device. Because of our lack of experience in the field, we are stuck. Mozilla's documentation is not that helpful and we don't know at the moment how to continue.
What we did:
- created manifest xml for the device, based on unofficial cyanogenmod for Moto G.
- synced all sources
- added manually prebuilt kernel.
- tried to build everything but it doesn't build, of course, we don't know why.
The error seem to be:
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.
Click to expand...
Click to collapse
Now I haven't been on these forums long but I'd like to say congrats on ur first post ! ;0 That error
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.
means there is no target to build the path. I need more info. What compiler are you using. Or are you just using the command prompt?What's the custom kernel, you could try using CM #2 Unoffical However that'd only work if ur Moto G is currently running android with CWM (to flash the kernel when u build it) Can u link to the mozilla post, I didn't bookmark it and I can be bothered to google it Can u send me what you've done so far pls. Thanks

Or are you just using the command prompt?
Click to expand...
Click to collapse
Yes, I'm using terminal to compile everything. Actually a specialized script for that purpose. Environment versions are:
g++ - 4.6
gcc - 4.6
Actually I'm using this guide .
Yes, I use Clockwork but before that there is building problem. Anyway, the link for porting is this.
The kernel I got is from here.

Admittedly, I know jack **** about android development, but I was under the impression that Firefox OS was based on an ICS kernel? I don't think the CM11 kernel works.

coldSense said:
Yes, I'm using terminal to compile everything. Actually a specialized script for that purpose. Environment versions are:
g++ - 4.6
gcc - 4.6
Actually I'm using this guide .
Yes, I use Clockwork but before that there is building problem. Anyway, the link for porting is this.
The kernel I got is from here.
Click to expand...
Click to collapse
Never seen that error before. Know wat it means tho. Have u tried complieing with Xcode (mac) or another 3rd part app ?

Apph3x said:
Never seen that error before. Know wat it means tho. Have u tried complieing with Xcode (mac) or another 3rd part app ?
Click to expand...
Click to collapse
No. I don't have and don't use mac computers, at least for now. I did this in Linux. It seems that it just doesn't read kernel/ directory or just ignores it.

Yeah
coldSense said:
No. I don't have and don't use mac computers, at least for now. I did this in Linux. It seems that it just doesn't read kernel/ directory or just ignores it.
Click to expand...
Click to collapse
It's like its invisible....

I solved (apparently) that problem by modifying variable TARGET_KERNEL_SOURCE (device/motorola/msm8226-common/BoardConfigCommon.mk) to be absolute path but now I have another error
Code:
make: *** No rule to make target `out/host/linux-x86/bin/acp', needed by `out/debug/host/linux-x86/bin/validatekeymaps'. Stop.

@coldSense
Try this way please
Code:
rm -rf out
rm -rf objdir-gecko
./build.sh gecko
then run
Code:
./build.sh gaia
and copy file from <build_path>/gaia/profile/webapps to <build_path>/out/project/<device_name>/system/b2g/webapps
Then replace all file from out/target/<product>/system to /system of AOSP ROM
then edit ramdisk follow https://developer.mozilla.org/en-US/Firefox_OS/Porting
and flash boot.img and /system you were edit to your Motolola G
Try this way please

Any luck with this? I might try myself, but curious if you can update.

Hi everyone !
I'm currently tryaing to build Firefox OS on own device.
I have this error :
Code:
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. cm_falcon-userdebug
6. mini_armv7a_neon-userdebug
Which would you like? [aosp_arm-eng] full_falcon
build/core/product_config.mk:222: *** Can not locate config makefile for product "falcon". Arrêt.
** Don't have a product spec for: 'full_falcon'
** Do you have the right repo manifest?
Could someone help me ?
Thanks a lot !

feherneoh said:
try full_falcon instead
Click to expand...
Click to collapse
Code:
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. cm_falcon-userdebug
6. mini_armv7a_neon-userdebug
Which would you like? [aosp_arm-eng] full_falcon
Invalid lunch combo: full_falcon
OR
Code:
$ ./build.sh full_falcon
including device/motorola/falcon/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
build/core/product_config.mk:222: *** Can not locate config makefile for product "full_flo". Arrêt.
** Don't have a product spec for: 'full_flo'
** Do you have the right repo manifest?
> Build failed! <
Build with |./build.sh -j1| for better messages
If all else fails, use |rm -rf objdir-gecko| to clobber gecko and |rm -rf out| to clobber everything else.
A modification in device/motorola/falcon/vendorsetup.sh maybe ?
UPDATE :
Modifying vendorsetup.sh like this
add_lunch_combo full_falcon-eng

Can somebody explain me how to use a prebuilt kernel to build that please ?
Thank You
I have this error ... (in french)
Code:
No private recovery resources for TARGET_DEVICE falcon
make: *** Pas de règle pour fabriquer la cible « out/target/product/falcon/kernel », nécessaire pour « prebuilt ». Arrêt.
make: *** Attente des tâches non terminées....

h2o64 said:
Can somebody explain me how to use a prebuilt kernel to build that please ?
Thank You
I have this error ... (in french)
Code:
No private recovery resources for TARGET_DEVICE falcon
make: *** Pas de règle pour fabriquer la cible « out/target/product/falcon/kernel », nécessaire pour « prebuilt ». Arrêt.
make: *** Attente des tâches non terminées....
Click to expand...
Click to collapse
You can try to create the folder falcon-kernel inside device/motorola/ and put into it your kernel image.
In device/motorola/(your model) create the file AndroidBoard.mk and put inside:
ifeq ($(TARGET_PREBUILT_KERNEL),)
TARGET_PREBUILT_KERNEL := device/motorola/falcon-kernel/kernel
endif
Than try to rebuild.

[LOLLIPOP] Xperia AOSP Project

hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J

Wohooo! Finally! [emoji106] [emoji2] [emoji3]

Excellent! An AOSP ROM is the only thing I can think is missing from an otherwise perfect device.
GCC here we come..

Andoroid L (5.0) code, binaries and guides are published

No working camera or modem, looks like we've still got awhile guys...

great news,thankss

nice

I'm syncing it now. I'm going to do a blind build (not changing anything just going with what's already there) because I have yet to unlock my bootloader and won't until they can figure out a way so at least the camera and noise cancellation don't get messed up when unlocking (if I go back to a sony stock rom I know it won't matter on AOSP)

graffixnyc said:
I'm syncing it now.
Click to expand...
Click to collapse
Preparing to build as well. Like you, I haven't BL unlocked and won't until the DRM issues are resolved.

jerpelea said:
Andoroid L (5.0) code, binaries and guides are published
Click to expand...
Click to collapse
Your work is really appreciated. FYI, I convinced a friend to buy a Z3C in large part due to your AOSP commitment. [emoji106]

Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?

illogic6 said:
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
Click to expand...
Click to collapse
no

Reverse Engeneering
In other words - SONY will deliver the required drivers or better all required driver will be there in a while...

I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated

m0d said:
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
Click to expand...
Click to collapse
just re sync your tree and fix is there

That inform you in: <insert the cpu thread number of your computer> ??? Please

I got a build to finish. I'll post the boot and system img for someone to try.. I'm not going to go through the trouble yet to make a flashable zip until we at least know it boots. I'll upload the images now

Posted the images: http://forum.xda-developers.com/z3-compact/development/img-aosp-5-0-boot-imgs-t2940499

So @NisseGurra flashed the build I made yesterday here is what he found to be broken:
no wifi, no network, some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp

Thank you for the guides,
I was able to compile AOSP for D5803 successfully.
A couple of issues,
First,
Has the Cherry-Pick for external/libnfc-nci/ that is provided in the guide been merged?
As I get the following error,
Code:
/external/libnfc-nci $ git cherry-pick 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
fatal: bad object 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
(Updated on blog to correspond with Shinano Issue.)
Second,
I get the following error when I try to output zipped package,
Code:
[B]No private recovery resources for TARGET_DEVICE aries
No recovery.fstab for TARGET_DEVICE aries[/B]
make: *** no rule to make target `otapackage'. stop.
Does this have anything to do with: TARGET_BOOTLOADER_BOARD_NAME := D5803
or that it is called aosp_d5803 (aosp_d5803.mk)
UPDATE: otatools seems to work, [" . build/envsetup.sh && time lunch aosp_d5803-userdebug && make otatools "].
But I can not find the output / output directory for package
Oh,
Is there supposed to be a userdata.img too?
Looking around a different sources mention it, however there is no userdata.img when I compiled it.
Thank you for your time

Building stock kernel for Huawei Y5II CUN-L01

Hello guys, first of all thanks for all the hard work you do for us noobs
So to begin, i am trying to build a simple kernel without any modifications (for now) using source code provided by Huawei on their official website (You will need to select Y5II(CUN-L01) to get something downloadable).
consumer*huawei*com/en/support/phones/y5ii/
(New user external url block)
DOWNLOADS
Y5II Open Source(CUN-LXX,Android5.1,kernel,en) | 2016-04-14 | 140.76 MB
Click to expand...
Click to collapse
I've tried at least 5 different toolchains, I've followed many tutorials for building kernels including the mediatek specific guides but without luck. I would be grateful if someone could point me in the right direction and tell me if I am the one doing something wrong or is the source code broken ?
From many tutorials i've followed i've come to some usual steps i do:
1.
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=/home/mita/toolchain/bin/arm-eabi-
2.
I create a .config using predefined config
make hq6735_35u_b1n_l1_defconfig
3.
I try to do a make clean - i get an error
4.
I try to do a make mrproper - also an error
5.
I try just make and make -j4 - also errors
I can post the errors i am receiving, i have experience with android application development but i can't figure out a way to track down errors like i did in Eclipse and Android Studio.
CLEAN .
CLEAN arch/arm/kernel
"CONFIG_TRUSTONIC_TEE_SUPPORT = "
scripts/Makefile.clean:17: /home/mita/Kernel_Development/kernel-3.10/drivers/misc/mediatek/cpu_stress/Makefile: No such file or directory
make[4]: *** No rule to make target '/home/mita/Kernel_Development/kernel-3.10/drivers/misc/mediatek/cpu_stress/Makefile'. Stop.
scripts/Makefile.clean:94: recipe for target 'drivers/misc/mediatek/cpu_stress' failed
make[3]: *** [drivers/misc/mediatek/cpu_stress] Error 2
scripts/Makefile.clean:94: recipe for target 'drivers/misc/mediatek' failed
make[2]: *** [drivers/misc/mediatek] Error 2
scripts/Makefile.clean:94: recipe for target 'drivers/misc' failed
make[1]: *** [drivers/misc] Error 2
Makefile:1040: recipe for target '_clean_drivers' failed
make: *** [_clean_drivers] Error 2
Click to expand...
Click to collapse
Edit 1:
I forgot to mention i tried building on multiple OS’s: Ubuntu 32bit and 64bit, Lubuntu 32bit and 64bit, Kali Linux 64bit, and even on Raspberry Pi (i know it’s low spec but i had to try building on arm device just to rule it out) - Raspbian Stretch.
Thanks in advance for all the help

Bump
Before bumping i’ve read the rules “Once every 24h bumping”
I just not sure if there is a button to bump or is post like this required, sorry in advance if there is a bump button.

Once again a bump...
I would really be grateful if someone could tell me if source is broken or not so i can know my next steps.