Database Users

[Q] Kernel for AOSP build?

As the topic says. After 3 days of working, I finally built Gingerbread 2.3.7_r1 from sources. Now I got hit by another problem: Where I could get a kernel/source which is compatible with it? I'm stuck in the "Huawei" screen at the moment.
I would love to get my build up and running. Thanks in advance.

Unrealized said:
As the topic says. After 3 days of working, I finally built Gingerbread 2.3.7_r1 from sources. Now I got hit by another problem: Where I could get a kernel/source which is compatible with it? I'm stuck in the "Huawei" screen at the moment.
I would love to get my build up and running. Thanks in advance.
Click to expand...
Click to collapse
Huawei 2.6.35 will do fine. I'd suggest TomGiordano's kernel_huawei on 2.6.35 branch in GitHub.
Sent from my U8800 using Tapatalk 2

Thank you. Should I dump the newer propietary libs from the stock rom as well?
Also, seems like the kernel tree doesn't like me:
Code:
In file included from arch/arm/mach-msm/proc_comm.c:27:
arch/arm/mach-msm/smd_private.h:79:2: error: #error No SMD Package Specified; aborting
make[1]: *** [arch/arm/mach-msm/proc_comm.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
Edit: hmm, now it started to compile with hw7x30_defconfig

Unrealized said:
Thank you. Should I dump the newer propietary libs from the stock rom as well?
Also, seems like the kernel tree doesn't like me:
Code:
In file included from arch/arm/mach-msm/proc_comm.c:27:
arch/arm/mach-msm/smd_private.h:79:2: error: #error No SMD Package Specified; aborting
make[1]: *** [arch/arm/mach-msm/proc_comm.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
Click to expand...
Click to collapse
Stock ROM proprietary libs will do fine.
About the kernel error - did you do make hw7x30_defconfig?

It still seems to hang in the Huawei screen. It does the same with stock boot.img
I'm using this this device tree.
My build process is like this:
Code:
. build/envsetup.sh
lunch huawei_u8800-userdebug
make -j2
make otapackage
java -Xmx512m -jar out/host/linux-x86/framework/signapk.jar build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 out/target/product/u8800/huawei_u8800-ota-eng.unrealized.zip signed.zip
Not sure what's wrong here, with my old Gio it worked fine. Any help would be appreciated.

Unrealized said:
It still seems to hang in the Huawei screen. It does the same with stock boot.img
I'm using this this device tree.
My build process is like this:
Code:
. build/envsetup.sh
lunch huawei_u8800-userdebug
make -j2
make otapackage
java -Xmx512m -jar out/host/linux-x86/framework/signapk.jar build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 out/target/product/u8800/huawei_u8800-ota-eng.unrealized.zip signed.zip
Not sure what's wrong here, with my old Gio it worked fine. Any help would be appreciated.
Click to expand...
Click to collapse
Does ADB work or is it completely stuck?

running adb shell works. I guess it has something to do with the init?
Edit: added dmesg.. Seem to be a lot of problems there. I'd appreciate any help. If I could get my first build to succeed I would be able to work myself then.
Edit2: Also, I think there are problems in the device tree I'm using as I couldn't find a clean one. I'm redownloading the 2.3.7_r1 tree once again, I hope someone could link me the device tree to use.

CM11 jflteatt compile error

Can someone help me with this.. I've just synced and tried a fresh build of CM11 for jflteatt and I'm running in to this:
Code:
target thumb C: irda.msm8960 <= device/samsung/jf-common/irda/irda.c
target thumb C++: keystore.default <= system/security/softkeymaster/module.cpp
device/samsung/jf-common/irda/irda.c:25:27: fatal error: hardware/irda.h: No such file or directory
compilation terminated.
make: *** [/home/kaschenberg/android/system/out/target/product/jflteatt/obj/SHARED_LIBRARIES/irda.msm8960_intermediates/irda.o] Error 1
make: *** Waiting for unfinished jobs....
Thanks :good:
EDIT:
I can see this was moved.. FWIW thanks to anyone who's viewed this but, mods, please this won't get the correct exposure in this section. This belongs in the dev section because it's dev-related material, not generic Q&A material.

chaosclarity said:
Can someone help me with this.. I've just synced and tried a fresh build of CM11 for jflteatt and I'm running in to this:
Code:
target thumb C: irda.msm8960 <= device/samsung/jf-common/irda/irda.c
target thumb C++: keystore.default <= system/security/softkeymaster/module.cpp
device/samsung/jf-common/irda/irda.c:25:27: fatal error: hardware/irda.h: No such file or directory
compilation terminated.
make: *** [/home/kaschenberg/android/system/out/target/product/jflteatt/obj/SHARED_LIBRARIES/irda.msm8960_intermediates/irda.o] Error 1
make: *** Waiting for unfinished jobs....
Thanks :good:
EDIT:
I can see this was moved.. FWIW thanks to anyone who's viewed this but, mods, please this won't get the correct exposure in this section. This belongs in the dev section because it's dev-related material, not generic Q&A material.
Click to expand...
Click to collapse
Found this thread via Google. I fixed it by either removing "Android.mk" and "irda.c" or just renaming "Android.mk" to something else from ~/android/system/device/samsung/jf-common/irda
This will kill any IR functionality, though.

chaosclarity said:
Can someone help me with this.. I've just synced and tried a fresh build of CM11 for jflteatt and I'm running in to this:
Code:
target thumb C: irda.msm8960 <= device/samsung/jf-common/irda/irda.c
target thumb C++: keystore.default <= system/security/softkeymaster/module.cpp
device/samsung/jf-common/irda/irda.c:25:27: fatal error: hardware/irda.h: No such file or directory
compilation terminated.
make: *** [/home/kaschenberg/android/system/out/target/product/jflteatt/obj/SHARED_LIBRARIES/irda.msm8960_intermediates/irda.o] Error 1
make: *** Waiting for unfinished jobs....
Thanks :good:
EDIT:
I can see this was moved.. FWIW thanks to anyone who's viewed this but, mods, please this won't get the correct exposure in this section. This belongs in the dev section because it's dev-related material, not generic Q&A material.
Click to expand...
Click to collapse
anekdotos said:
Found this thread via Google. I fixed it by either removing "Android.mk" and "irda.c" or just renaming "Android.mk" to something else from ~/android/system/device/samsung/jf-common/irda
This will kill any IR functionality, though.
Click to expand...
Click to collapse
This is because the IRDA frameworks aren't added in to the frameworks yet. We have this issue on omni, but I know for a fact that omni doesn't have the IRDA frameworks. I thought CM had them in the cm11 source but apparently not since you're getting this error.
For future reference, that is not the actual line in the terminal output that is where the build was killed at. it's farther up. easiest way to find it is to go to the end of your terminal output and search for "error"
just do the following, and you'll be good to go.
Code:
FROM ROOT OF SOURCE:
cd device/samsung/jf-common
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_jf-common refs/changes/25/53625/1 && git cherry-pick FETCH_HEAD
cd ..
cd ..
cd ..
make clobber
source build/envsetup.sh
brunch jflteatt
you may or may not run into more build errors, just post them up in here and i'll get a fix for ya
This does belong in the Q&A section, if it is going to be its own thread. If you had posted this in the CyanogenMod thread, then it would have been alright there as well. :good:

[EXPERIMENT] Building CM11 on Cygwin

I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.

Restl3ss said:
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Click to expand...
Click to collapse
Hey bro you are doing such a good thing for developers so please continue this thread and make some thing new
All the best :good:

[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.