Related
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
sarkar1990 said:
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
Click to expand...
Click to collapse
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
nil1511 said:
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
Click to expand...
Click to collapse
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
Awesome. You can either upload them link me the git if its there
sarkar1990 said:
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
Click to expand...
Click to collapse
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
nil1511 said:
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
Click to expand...
Click to collapse
If you want to learn. It would be best to clone the Doomlord git and then read the files and scripts that are present there. This will give you the knowledge you may need to proceed further.
the git for our processor msm8960t is already present on github. Also download the kernel sources and drivers provided by Sony themselves from their developerworld page
sarkar1990 said:
the git for our processor msm8960t is already present on github.
Click to expand...
Click to collapse
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
eeehaw said:
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
Click to expand...
Click to collapse
Here is the link
https://github.com/DooMLoRD/android_kernel_sony_msm8960t.git
eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
sarkar1990 said:
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
Click to expand...
Click to collapse
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
eeehaw said:
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
Click to expand...
Click to collapse
Can you push your device file on github
nil1511 said:
Can you push your device file on github
Click to expand...
Click to collapse
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
eeehaw said:
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
Click to expand...
Click to collapse
Man, I keep running into the error! Ahh.. I think we need a better device tree.
sarkar1990 said:
Man, I keep running into the error! Ahh.. I think we need a better device tree.
Click to expand...
Click to collapse
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
CallMeVentus said:
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
eeehaw said:
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
Click to expand...
Click to collapse
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
eeehaw said:
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
Click to expand...
Click to collapse
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
CallMeVentus said:
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
No. I knew there were changes but I never knew what they were ? I asked a few people in a few threads but was not able to decipher.
Do you have any idea what sort of changes are required. ?
Hello everyone, I'm a noob that want try to learn something more about Android.
I'm trying to compile the Optimus-prime kernel of Demetris, but I'm stuck on an error during compile session.
My steps:
1) git init -u git://github.com/Ntemis/lge-kernel-p880
2) downloaded NDK from google http://dl.google.com/android/ndk/android-ndk-r9c-linux-x86.tar.bz2
(I'm using Slackware 14.1 32 bit)
3) I've used as baseconfig this one : cyanogenmod_x3_defconfig
4) then as toolchain :
Code:
export CROSS_COMPILE=~/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi-
5)finally I did
Code:
make -j2 ARCH=arm SUBARCH=arm
Now the error:
Code:
CC arch/arm/mach-tegra/lge/x3/board-x3-i2c-dev.o
arch/arm/mach-tegra/lge/x3/board-x3-i2c-dev.c:58:27: fatal error: board-lge-nfc.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-tegra/lge/x3/board-x3-i2c-dev.o] Errore 1
make[1]: *** [arch/arm/mach-tegra/lge/x3] Errore 2
make: *** [arch/arm/mach-tegra] Errore 2
The include file board-lge-nfc.h is present in the same folder of board-x3-i2c-dev.c
Where is the error?
are you sure the cross compile path points to the correct directory?
try using doomlord toolchain, kernel compiling is quite tricky and most toolchains give errors
Poi se vuoi se ne parla in pvt
Rudjgaard said:
are you sure the cross compile path points to the correct directory?
try using doomlord toolchain, kernel compiling is quite tricky and most toolchains give errors
Poi se vuoi se ne parla in pvt
Click to expand...
Click to collapse
Hi,
I have only the official NDK on my machine. Anyway I'll try also that doomlord toolchain
Thx for the hint. :good:
I've tried DoomLord's toolchain,but I have the same problem.
So I've tried to download Iodak's sources and I'm been able to compile it without any problem.
Is there a problem with Optimus Prime sources?Is there some special trick?
Well, I've found a solution....
It looks like there is some problem with include path.I've moved the "board-lge-nfc.h" file inside the include folder in the main root of the kernel sources and it worked.
Now I'm stuck with tspdrv. Same story: missing files when they are there instead. I did the same trick with another include file and it worked again, but now I have other missing files.
I'm sure there is something wrong in my setup/sources ...
bilbo75 said:
Well, I've found a solution....
It looks like there is some problem with include path.I've moved the "board-lge-nfc.h" file inside the include folder in the main root of the kernel sources and it worked.
Now I'm stuck with tspdrv. Same story: missing files when they are there instead. I did the same trick with another include file and it worked again, but now I have other missing files.
I'm sure there is something wrong in my setup/sources ...
Click to expand...
Click to collapse
Simply just cherry-pick this commit and you'll be fine
https://github.com/laufersteppenwolf/lge-kernel-p880/commit/c2e57252398ded9520beb9382f538da53f9a0199
I think this will help you
https://github.com/iodak/LG_X3_P880_v20a/commit/6f2086454d537c6f49038f36d6eeddbe4adcd70a
Also look at other commits on this page when you get into problems.
https://github.com/iodak/LG_X3_P880_v20a/commits/master?page=9
Sent from my LG-P880 using xda app-developers app
Wow! Thanks you very much for your help guys! :highfive:
Now I have to study cherry-picking
bilbo75 said:
Wow! Thanks you very much for your help guys! :highfive:
Now I have to study cherry-picking
Click to expand...
Click to collapse
One of the best ( if not the best) git(hub) tuts on xda: http://forum.xda-developers.com/showthread.php?t=1877040
everything's covered, and even git noobs ( such as I am ) can easily understand it
You have to:
git fetch https://iodak/LG_X3_P880_20a
Then wait for a while
Then git cherry-pick 6f2086454d537c6f49038f36d6eeddbe4adcd70a
Commit that you want.
Sent from my LG-P880 using xda app-developers app
I'm amazed from your kindness guys!
A big thanks again! :victory:
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
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
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
sk806 said:
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
Click to expand...
Click to collapse
That is Samsung for ya. Maybe @g.lewarne could provide some insight
mikeyinid said:
That is Samsung for ya. Maybe @g.lewarne could provide some insight
Click to expand...
Click to collapse
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
sk806 said:
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
Click to expand...
Click to collapse
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
elesbb said:
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
Click to expand...
Click to collapse
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
sk806 said:
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
Click to expand...
Click to collapse
It is related to modules compiling from what I can gather. If I use Ktoonsez source, I don't get that error. However, I notice it doesn't compile any modules. I still get an Image in my boot directory. Do you? I think the kernel itself is safe to use. You could probably ignore this error.
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
sk806 said:
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
Click to expand...
Click to collapse
There are others I've seen using my commit (no credit) and didn't cherry-pick keeping the history. I believe the Image still flashes with or without though
I am having the same issue can you explain what was the issue ?
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
elesbb said:
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
Click to expand...
Click to collapse
Can you tell me what you did? I have the same error and i cant fix it ????
minealex2244 said:
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
Click to expand...
Click to collapse
Did you figure it out?
EncryptedCurse said:
Did you figure it out?
Click to expand...
Click to collapse
Uhm somehow. I used a script which ignored that error as your kernel image is already built and you shouldn't care about modules. But if you still want a fix then see my commit: https://github.com/minealex2244/AldeXus/commit/e89301766b3d251b285649a38ee4dea4f2871b99
This commit shows you what to remove (it may be the perfect fix or just an example of what you should do in your code).
Tell me if it helped.
Broken link
Hey, I'm having the same issue but I can't find your commit, could you please fix the link?. Thanks in advance.