Database Develop

[Resolved][HELP] Compile error [mik kernel]

I have this error when i compile mik kernel (i downloaded it from his git repo):
Code:
CC [M] drivers/net/wireless/bcm4325/src/shared/linux_osl.o
cc1: warnings being treated as errors
drivers/net/wireless/bcm4325/src/shared/linux_osl.c: In function 'osl_pktfree_static':
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
drivers/net/wireless/bcm4325/src/shared/linux_osl.c:376:34: error: array subscript is above array bounds
make[4]: *** [drivers/net/wireless/bcm4325/src/shared/linux_osl.o] Error 1
make[3]: *** [drivers/net/wireless/bcm4325] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
I asked mik, but he doesn't reply...
i compile with "make -j2"
NB: This error there is in "git clone", "tar.gz" and "zip"...

I don't get any errors when I built from his code. Maybe you just have a bad copy

Which version of gcc are u on? I think you should update gcc.
Sent from my LG-P500 using XDA Premium App

Code:
git clone git://github.com/mik9/ThunderG-Kernel.git
OR I downloaded it from his repo with "Download Now" "tar.gz"

4silvertooth said:
Which version of gcc are u on?
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
I download the environment from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1803

DookMatt said:
I download the environment from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1803
Click to expand...
Click to collapse
do u work under windooze or linux?
i consider to use linux - on windows, the dumb cygwin environment have not
all needed includes.
if u use linux, try to take the latest android from cyanogen - there are prebuild
libs and binaries to compile both the android system and kernel.
u only have to export the path to the arm-ebi and the arch:
Code:
export ARCH=arm
export CROSS_COMPILE=<ANDROID_INSTALLPATH>/prebuild/linux86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
this works on my VM (virtualBox) without problems.
otherwise, try the bcm4325 tree from my github if you can compile, its a error in mik's driver tree or he have another compiler.

ArchLinux x86_64... now i removing openjdk and istalling jre... i hope this is the problem.

DookMatt said:
ArchLinux x86_64... now i removing openjdk and istalling jre... i hope this is the problem.
Click to expand...
Click to collapse
I don't think so.
Sent from my LG-P500 using XDA Premium App

jre/jdk has nothing to do with kernel compiling - you need this only to compile the android system
btw: try a 32bit system - i have had problems too to compile android under 64bit OS (ubuntu)

andy572 said:
jre/jdk has nothing to do with kernel compiling - you need this only to compile the android system
btw: try a 32bit system - i have had problems too to compile android under 64bit OS (ubuntu)
Click to expand...
Click to collapse
Now i creating a VM... but... on archlinux i installed 32bit library...

DookMatt said:
Now i creating a VM... but... on archlinux i installed 32bit library...
Click to expand...
Click to collapse
u can use a linux to your choice, you need only a working environment

I think you should try with google android ndk instead of codesourcery.
http://developer.android.com/sdk/ndk/index.html
Then
make -j2 ARCH=arm CROSS_COMPILE=~/android-ndk-PATH/toolchains/arm-linux-androideabi-x.x.x/prebuilt/linux-x86/bin/arm-linux-androideabi-
(Please change the path to ur ndk toolchain setup)
Sent from my LG-P500 using XDA Premium App

4silvertooth said:
I think you should try with google android ndk instead of codesourcery.
http://developer.android.com/sdk/ndk/index.html
Then
make -j2 ARCH=arm CROSS_COMPILE=~/android-ndk-PATH/toolchains/arm-linux-androideabi-x.x.x/prebuilt/linux-x86/bin/arm-linux-androideabi-
(Please change the path to ur toolchain setup)
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
WAAAAAAAAAAAAAA!!! It works on Archlinux x86_64! Thank you very much!!!

So do we get a new Nessy any time sooner. Hmmm. I know Irene is out.
Sent from my LG-P500 using XDA Premium App

That error happens when you compile with -O2 flag. Here is the fix on that error so you can compile again with -O2:
https://github.com/LeeDroid-/Ace-2.6.35/commit/0e3632e38829f7b5baac3e7e88f179762173d3ba

franciscofranco said:
That error happens when you compile with -O2 flag. Here is the fix on that error so you can compile again with -O2:
https://github.com/LeeDroid-/Ace-2.6.35/commit/0e3632e38829f7b5baac3e7e88f179762173d3ba
Click to expand...
Click to collapse
I've fix the file but i've this error:
Code:
`dhd_module_cleanup' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
make: *** [.tmp_vmlinux1] Error 1

Which file did you patched?

franciscofranco said:
Which file did you patched?
Click to expand...
Click to collapse
PATCH

There's not much I can do. How did you patched bfs? My kernel already has it so why adding it again? I saw you used my v14.1 in your rom.

franciscofranco said:
There's not much I can do. How did you patched bfs? My kernel already has it so why adding it again? I saw you used my v14.1 in your rom.
Click to expand...
Click to collapse
I add it on mik kernel (for CM7)... "patch -p0 < PATCHNAME" and the directory name is linux-2.6.32.40-bfs

[SOLVED] Problem compiling cyanogen mod 7 with subskype tass device

Hello I'm trying to compile cyanogenmod 7 with subskyper tass device to try to mantain this project update in line with the original philosophy: keep it 100% cyanogenmod without any tweaks
When I compile I face two errors that broke my compilation:
1-
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml:95: error: Resource at swap_volume_keys_orientation appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Errore 1
make: *** Eliminazione del file "out/target/common/obj/APPS/framework-res_intermediates/package-export.apk"
make: *** Attesa per i processi non terminati....
This one I commented out the line reguarding swap_volume_keys_orientation in file
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml
but when i continue...
2-
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/AndroidRuntime.o: in function android::gRegJNI:AndroidRuntime.cpp(.data.rel.ro+0x148): error: undefined reference to 'register_android_hardware_fm_fmradio(_JNIEnv*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Errore 1
make: *** Attesa per i processi non terminati..
Someone faced same problems?
Any ideas?
thanks a lot

Send PM With The Error To Subpsyke

t-r-e said:
Send PM With The Error To Subpsyke
Click to expand...
Click to collapse
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.

mebitek said:
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
Click to expand...
Click to collapse
Best Luck Buddy Don't Give Up Early , We Look Forward To See Your Work As We Need To Keep Subpsyke Project Alive

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld:
Click to expand...
Click to collapse
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.

coolsandie said:
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
Click to expand...
Click to collapse
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation

Now I have a signed zip to flash into my sgm.
It contains subskype cm7.2 tass device configuration and latest cm 7.2 sources update at 31-01-2012.
to check changes:
http://review.cyanogenmod.com/#q,status:open,n,z

It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
Great news. Glückwunsch (don't know the english word at the moment).
Supercharger would be possibly good. Subpsyke said something to it but i don't rember clearly.
Keep up your work.
Sent from my GT-S5570 using xda premium

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
No not add anything. It s better. Completely clean
Inviato dal mio GT-S5570 usando Tapatalk

mebitek said:
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Click to expand...
Click to collapse
For the radio, I used my patch to add support for the bcm2xxx devices with proper seeking. It's on gerrit here: http://review.cyanogenmod.com/#change,10358

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
no no...no v6.
Just vanilla cm7...and thanks for the initiative and ABT!
dont add scripts..but maybe something from cm gerrit if u wish..but then it'll not be vanilla.

[Q] Help Compiling with Camera Patches

I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.

theAPANT said:
I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.
Click to expand...
Click to collapse
I had this issue camcory never pushed the finished camera sources
Here
https://docs.google.com/file/d/0Bwu6jmegWBFQRXNpRFAwc2dZam8/edit
Also, if RIL (data) doesn't work pull the hardware/ril folder from cm10.
I don't have the sources for aokp atm but I think I had to do a few other things to get everything working but they broke camera
Sent from my Nexus 7 using xda app-developers app

Re awaking this thread, hopefully someone can help. OK i am having allot of problems building /hardware/qcom/display and surfacflinger on 4.2.2 liquidsmooth so far i have just removed the problematic things from the specific Android.mk but I'm stilling having lots of problems. Ill post specific error if that is helpful. What have you done to get it to build, I'm downloading aosp now to see if the loquidsmooth team hasnt pushed files but i doubt it. Thanks
Sent from my Nexus 7 using xda app-developers app

CM10.1 wpa problem
I'm getting this and don't know how to fix it. Hopefully one of you do, I had to try using cm10.1 sources instead of liquidsmooth because they haven't pushed changes yet. Any ideas? Thanks
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x198): error: undefined reference to 'wpa_driver_signal_poll'
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x1a0): error: undefined reference to 'wpa_driver_wext_driver_cmd'
collect2: ld returned 1 exit status
make: *** [/home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
make: *** Waiting for unfinished jobs....

Well I deleted /external/wpa_supplicant_8 and renamed the wpa_supplicant_6 to 8 and compiled and I got it to build.
Package complete: /home/theapant/cm10.1/out/target/product/ancora_tmo/cm-10.1-20130301-UNOFFICIAL-ancora_tmo.zip
md5: e714e16988f891693df172e405be1b54
Unfortunately it doesn't boot (black screen) perhaps an issue with using the prebuilt kernel in device/samsung/ancora_tmo/prebuilt/zImage?
Any ideas anyone? I will add the TARGET_KERNEL_CONFIG := ancora_tmo_defconfig in boardconfig.mk and see if that works. Also hopefully someone could shed some light on the previous error that i didn't actually fix. Thanks
Edit: still no boot when i build the kernel

if i can ever get some time dude ill try and help but look for a cm10.1 release from me in a couple of days. i ahve it built and working just havent had time to do anything with it. been working on getting the team sites looking good

target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):device/samsung/ancora_tmo/camerahal/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
[email protected]:~/aokp$
I'm getting the same error that I got a long time before. I'm using camcory's device github. If i remove the camerahal.cpp from the android.mk it finishes the build fine and I think I have everything else working now. I built it with camcory's prebuilt 3.0.66 kernel, so is that the issue? Any suggestions are welcome. Thanks!

Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.

jfbs said:
Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.
Click to expand...
Click to collapse
Thanks I all ready knew why it is kernel version 3.0.66. I could swap out the zimage but i still cant get camerahal.CPP so i need to fix that first. Camcory built slimbean with camera and 3.0 kernel and i would like to do the same with aokp, however i have to take camerahal out of the make file so that the build finishes because of that error above. I have built plenty of kernels and i can just add kernel source and the target_kernel_config := ancora_tmo_defconfig to boardconfig and it would build the kernel that way too however camcorys kernels are much more stable than mine, so.... Any ideas on how i can fix the camerhal thing?
Sent from my Nexus 7 using xda app-developers app

That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.

jfbs said:
That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.
Click to expand...
Click to collapse
Thanks again, I made a really stupid mistake and only had Overlay.h when I also needed Overlay.cpp, your post made me go back and check my sources and I found the problem. Before I was racing around trying to modify camerahal.cpp with no c++ knowledge. I also fixed an issue I was having with turning wifi on in settings and now I think I have a fully working build of AOKP with 3.0 kernel. Once again thanks!!!

Boot fail from fresh AOSP Build

Hi,
i have a Problem with building a Hammerhead Rom from AOSP.
Buildin otapackage went fine.
running: java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpHi4Kxb out/target/product/hammerhead/aosp_hammerhead-ota-eng.androidenv.zip
done.
Click to expand...
Click to collapse
But if flash this zip with TWRP, my Nexus 5 stand still at Google boot logo.
how can I check what I have done wrong?

isRaZZe said:
Hi,
i have a Problem with building a Hammerhead Rom from AOSP.
Buildin otapackage went fine.
But if flash this zip with TWRP, my Nexus 5 stand still at Google boot logo.
how can I check what I have done wrong?
Click to expand...
Click to collapse
My guess would be that you are missing some (or all) proprietary vendor blobs.

upndwn4par said:
My guess would be that you are missing some (or all) proprietary vendor blobs.
Click to expand...
Click to collapse
Your right. Do you have a link for me where i get these vendor blobs and how to include them ?

isRaZZe said:
Your right. Do you have a link for me where i get these vendor blobs and how to include them ?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers

Lethargy said:
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
Thanks. :good:
How do i include them in a automatic process in building ?

isRaZZe said:
Thanks. :good:
How do i include them in a automatic process in building ?
Click to expand...
Click to collapse
You should check if the path on /device/lge/hammerhead/full_hammerhead.mk is correct
and if, when you extract the zip, the device-vendor.mk works....
btw, my advice is to use some working blobs like AOSPA or CM...some binaries aren't in the source zip
...You can check my source for have an idea...

Crostantin said:
You should check if the path on /device/lge/hammerhead/full_hammerhead.mk is correct
and if, when you extract the zip, the device-vendor.mk works....
btw, my advice is to use some working blobs like AOSPA or CM...some binaries aren't in the source zip
...You can check my source for have an idea...
Click to expand...
Click to collapse
This is considerably more complex than I had imagined before.
Can someone explain me in more detail as I insert the blobs and can build a functioning Images?

isRaZZe said:
This is considerably more complex than I had imagined before.
Can someone explain me in more detail as I insert the blobs and can build a functioning Images?
Click to expand...
Click to collapse
in my opinion, the best way is to clone this in your tree (or add it in a local_manifests)
https://github.com/ThankYouMario/proprietary_vendor_lge_hammerhead
and move files to this path: vendor/lge/hammerhead
then you should make this little modification:
https://github.com/BoostPop/android_device_lge_hammerhead/commit/616c559e9fcfbde0e4fb477c681bc36627d5eb00

Crostantin said:
in my opinion, the best way is to clone this in your tree (or add it in a local_manifests)
https://github.com/ThankYouMario/proprietary_vendor_lge_hammerhead
and move files to this path: vendor/lge/hammerhead
then you should make this little modification:
https://github.com/BoostPop/android_device_lge_hammerhead/commit/616c559e9fcfbde0e4fb477c681bc36627d5eb00
Click to expand...
Click to collapse
Thanks. Will try it this evening.
Another question i have...
My idea is to build my own AOSP-Rom with some little modifikation. One of these modifikation are to include the "Close all Tabs" in the system wide tab view.
Where i can find this Code ?
I need to understand first where the individual parts of code are and was hoping that some of you support.
But first I need an executable Rom.
Edit:
I had checkout from git and copy to working directory. Path is vendor/lge/hammerhead. edit full_hammerhead.mk and remove the line and add
$(call inherit-product-if-exists, vendor/lge/hammerhead/hammerhead-vendor.mk)
then:
source build/envsetup.sh .
lunch aosp_hammerhead-userdebug
make -j4 otapackage
end in error :
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libloc_eng.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libloc_eng.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libmmcamera_interface.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libmmcamera_interface.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
No private recovery resources for TARGET_DEVICE hammerhead
build/core/tasks/vendor_module_check.mk:56: *** Error: Product "aosp_hammerhead" cannot have overlay in vendor tree: vendor/lge/hammerhead/overlay. Stop.
Click to expand...
Click to collapse
Edit2:
Problem solved. Add the repo over local_manifest solution and build succesful and rom flash&boot are okay.
before build i need to set PRODUCT_RESTRICT_VENDOR_FILES := false in full_hammerhead.
soo... next step is to add some tweaks. from cm source... also over manifest?

isRaZZe said:
soo... next step is to add some tweaks. from cm source... also over manifest?
Click to expand...
Click to collapse
IMO best way to add features to your own build is get to know how to cherry-pick.
Then how to deal with conflicts etc.
So best way is to check google "how to cherry-pick" , its really easy when you get it.
Then you check CM github the commits you need.

Sick1 said:
IMO best way to add features to your own build is get to know how to cherry-pick.
Then how to deal with conflicts etc.
So best way is to check google "how to cherry-pick" , its really easy when you get it.
Then you check CM github the commits you need.
Click to expand...
Click to collapse
I now have posited me with cherry pick apart. This works so far very good.Thanks for that tipp !
Now I am facing a problem. I want to integrate Koush superuser settings, but the patch from Koush for this is very old (cm10.1) and does not work with cm12. Does anyone have a link to a patch with which I can integrate superuser in the Settingsapp?

nobody?

isRaZZe said:
I now have posited me with cherry pick apart. This works so far very good.Thanks for that tipp !
Now I am facing a problem. I want to integrate Koush superuser settings, but the patch from Koush for this is very old (cm10.1) and does not work with cm12. Does anyone have a link to a patch with which I can integrate superuser in the Settingsapp?
Click to expand...
Click to collapse
isRaZZe said:
nobody?
Click to expand...
Click to collapse
Every question you have asked, and will ask in the future, has been asked and answered many times. Xda alone has many threads on building from source, so creating this thread was pointless.
Google is your friend. Search, read, learn.
Since you want to cherry-pick CM, then the CM github is a great place to start. But I'll give you a hint...CM doesn't use Koush's superuser anymore.
https://github.com/CyanogenMod

Hello guys ...
Can someone tell me the whole process to compile pure AOSP for hammerhead ?? .. How to extract d blobs and everything ..
It would be great if someone helps me
Hope someone helps ..
Thanx

CM11 Kenel compiling trouble !!

Hi. i have tried to compile cm11 kernel by using kernel source from http://github.com/cm-nokia-x2 and gcc toolchain 4.8 from here http://github.com/huyparody/gcc_linaro
i get config.gz from /proc/
and renamed it to ara_defconfig
and when i:
make ara_defconfig
make
after a few minute, it show me a error:
CC drivers/input/touchscreen/cyttsp4_device_access.o
drivers/input/touchscreen/cyttsp4_device_access.c: In function 'cyttsp4_grpdata_store_touch_params':
drivers/input/touchscreen/cyttsp4_device_access.c:1447:19: warning: 'rc3' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: cyttsp4_device_access.c:1447
make[3]: *** [drivers/input/touchscreen/cyttsp4_device_access.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
[email protected]:~/android/kernel/nokia/msm8610$
Click to expand...
Click to collapse
how to solve it!! thanks much

kaotd99 said:
how to solve it!! thanks much
Click to expand...
Click to collapse
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.

zombah said:
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
Click to expand...
Click to collapse
thanks dev

oh god... i got new error:
i type:
export PATH=/home/kaotd/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
and:
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make msm8610-nokia_defconfig
#
# configuration written to .config
#
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
kernel/bounds.c:1: error: bad value (cortex-a7) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
[email protected]:/home/kaotd/android/kernel/nokia/msm8610#
Click to expand...
Click to collapse
can you help me ? thanks.... because im a newbie and sorry about that

kaotd99 said:
can you help me ? thanks.... because im a newbie and sorry about that
Click to expand...
Click to collapse
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7

zombah said:
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
Click to expand...
Click to collapse
thanks.. i will try and report to you later!! thanks again

@zombah hi again. i was compiled a kernel( zImage )
now i have "Kernel: arch/arm/boot/zImage is ready"
so how can i compare it with boot.img ?

Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.

zombah said:
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
Click to expand...
Click to collapse
thanks much

can you tell me which file contain OverClock number of nokia x2 ? and which kernelPatch i can apply with this kernel ?

Hello,
I don't know, i'm not interested in overclocking and never investigated this question.
And i don't recommend you to play with overclocking without deep embedded development skills, it is very easy to kill your device with wrong power modifiers.

i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !

kaotd99 said:
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
Click to expand...
Click to collapse
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?

zombah said:
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
Click to expand...
Click to collapse
thanks... now i'm trying to port double-tap to wake feature from Nokia Stock Kernel. There is any suggestion ?? Thanks

i'm trying to add this: https://github.com/ryanaepple/android_kernel_motoe/commit/080003bc8e61349bf7c8da00fa6923f3c84d1927
and being stuck at editing synaptics_dsx_i2c.c and synaptics_dsx_i2c.h
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h

kaotd99 said:
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
Click to expand...
Click to collapse
Hello,
Nokia X2 have Cypress TMA4XX touchscreen, driver location is drivers/input/touchscreen/cyttsp4*