Help!!! Building AOSP - Miscellaneous Android Development

Hey guys I was tryna build aex 7.1.2 using my lineage sources
I get this error Everytime I lunch and mka aex
Code:
build/core/base_rules.mk:319: warning: ignoring old commands for target `/home/khannz7/aex/out/target/product/f1f/system/vendor/etc/audio_effects.conf'
build/core/Makefile:46: warning: overriding commands for target `/home/khannz7/aex/out/target/product/f1f/system/lib64/libjni_latinime.so'
build/core/base_rules.mk:319: warning: ignoring old commands for target `/home/khannz7/aex/out/target/product/f1f/system/lib64/libjni_latinime.so'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/khannz7/aex/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/khannz7/aex/out/target/common/obj/JAVA_LIBRARIES/com.cyanogenmod.keyhandler_intermediates/with-local/classes.dex', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Sources I use
Device
https://github.com/LineageOS/android_device_oppo_f1f.git
Kernel
https://github.com/LineageOS/android_kernel_oppo_msm8939.git
Device common tree
https://github.com/LineageOS/android_device_oppo_common.git
Device common msm8939 tree
https://github.com/LineageOS/android_device_oppo_msm8939-common.git

khannz7 said:
Hey guys I was tryna build aex 7.1.2 using my lineage sources
I get this error Everytime I lunch and mka aex
Code:
build/core/base_rules.mk:319: warning: ignoring old commands for target `/home/khannz7/aex/out/target/product/f1f/system/vendor/etc/audio_effects.conf'
build/core/Makefile:46: warning: overriding commands for target `/home/khannz7/aex/out/target/product/f1f/system/lib64/libjni_latinime.so'
build/core/base_rules.mk:319: warning: ignoring old commands for target `/home/khannz7/aex/out/target/product/f1f/system/lib64/libjni_latinime.so'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/khannz7/aex/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/khannz7/aex/out/target/common/obj/JAVA_LIBRARIES/com.cyanogenmod.keyhandler_intermediates/with-local/classes.dex', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Sources I use
Device
https://github.com/LineageOS/android_device_oppo_f1f.git
Kernel
https://github.com/LineageOS/android_kernel_oppo_msm8939.git
Device common tree
https://github.com/LineageOS/android_device_oppo_common.git
Device common msm8939 tree
https://github.com/LineageOS/android_device_oppo_msm8939-common.git
Click to expand...
Click to collapse
That's probably caused by the oppo common repo found here
https://github.com/LineageOS/android_device_oppo_common/tree/cm-14.1
Also make sure you are using cm-14.1 branch to build and not lineage-15.1

messi2050 said:
That's probably caused by the oppo common repo found here
https://github.com/LineageOS/android_device_oppo_common/tree/cm-14.1
Also make sure you are using cm-14.1 branch to build and not lineage-15.1
Click to expand...
Click to collapse
I do use the 14.1 branch..
+ Is there a particular thing in this repo making this error

khannz7 said:
I do use the 14.1 branch..
+ Is there a particular thing in this repo making this error
Click to expand...
Click to collapse
Yes it's that line
https://github.com/LineageOS/android_device_oppo_common/blob/cm-14.1/configpanel/Android.mk#L26

messi2050 said:
Yes it's that file
https://github.com/LineageOS/android_device_oppo_common/blob/cm-14.1/configpanel/Android.mk#L26
Click to expand...
Click to collapse
Should I remove this or what?

khannz7 said:
Should I remove this or what? Please
Click to expand...
Click to collapse
Yea try to comment out those 2 lines:
LOCAL_STATIC_JAVA_LIBRARIES := \
org.cyanogenmod.platform.internal

messi2050 said:
Yea try to comment out those 2 lines:
LOCAL_STATIC_JAVA_LIBRARIES := \
org.cyanogenmod.platform.internal
Click to expand...
Click to collapse
Thnx will try and report it to you

khannz7 said:
Thnx will try and report it to you
Click to expand...
Click to collapse
You are welcome

messi2050 said:
Yea try to comment out those 2 lines:
LOCAL_STATIC_JAVA_LIBRARIES := \
org.cyanogenmod.platform.internal
Click to expand...
Click to collapse
Same error again

khannz7 said:
Same error again
Click to expand...
Click to collapse
Hmm.. try to comment out all lines that contain
org.cyanogenmod.platform.internal
And make sure to make clean then start building again or just remove the whole oppo common folder xD

messi2050 said:
Hmm.. try to comment out all lines that contain
org.cyanogenmod.platform.internal
And make sure to make clean then start building again or just remove the whole oppo common folder xD
Click to expand...
Click to collapse
It may contain some dependencies

khannz7 said:
It may contain some dependencies
Click to expand...
Click to collapse
If it still give error i will try to check it later on pc and make sure what should be removed for a smooth build.

messi2050 said:
If it still give error i will try to check it later on pc and make sure what should be removed for a smooth build.
Click to expand...
Click to collapse
Ok ..
So this time I try removing the whole common folder
@messi2050
Removed oppo/common new error
** Don't have a product spec for: 'aosp_f1f'
** Do you have the right repo manifest?
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/oppo/f1f/aosp_f1f.mk]]: "device/oppo/common/common.mk" does not exist. Stop.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/oppo/f1f/aosp_f1f.mk]]: "device/oppo/common/common.mk" does not exist. Stop.

messi2050 said:
If it still give error i will try to check it later on pc and make sure what should be removed for a smooth build.
Click to expand...
Click to collapse
Still errors

khannz7 said:
Still errors
Click to expand...
Click to collapse
I will check the repos later and report back to you

messi2050 said:
I will check the repos later and report back to you
Click to expand...
Click to collapse
Ok

khannz7 said:
Ok
Click to expand...
Click to collapse
ok delete oppo-common folder and clone this one instead [it already have all required changes]
https://github.com/AospExtended-Devices/android_device_oppo_common
that should fix your problem. good luck.

messi2050 said:
ok delete oppo-common folder and clone this one instead [it already have all required changes]
https://github.com/AospExtended-Devices/android_device_oppo_common
that should fix your problem. good luck.
Click to expand...
Click to collapse
Thanks heaps buddy :good:

khannz7 said:
Thanks heaps buddy :good:
Click to expand...
Click to collapse
Let me know how it goes

messi2050 said:
Let me know how it goes
Click to expand...
Click to collapse
It gives me this new error

Related

remote object '/system/lib/libhuawei-ril.so' does not exist

Hi all,
I want to build cm 11 for my A700 but the build fails.
The build says:
make: *** No rule to make target 'vendor/acer/a700/proprietary/bin/rild', needed by '/home/triv/android/a700/out/target/product/a700/system/bin/rild'. Stop.
Click to expand...
Click to collapse
I guess the cause is that the ./extract-files.sh get following error:
remote object '/system/lib/libhuawei-ril.so' does not exist
Click to expand...
Click to collapse
I guess I need this file. But I have installed the regular nightly of cm11 so, why are they not inside?
Does anybody know where I can get this file?
I found solution on IRC from cyanogenmod. The lib files in the cyanogenmod nightly are not complete. So the exact-files.sh could not work! Sum up it was 3 files which was missing.
You got all from: git clone https://github.com/TheMuppets/proprietary_vendor_acer.git -b cm-11.0 vendor/acer

[HELP]Kernel building

Showing me this when i type
Code:
make -j4
scripts/kconfig/conf --silentoldconfig Kconfig
include/config/auto.conf:189:warning: symbol value 'elf32-i386' invalid for OUTPUT_FORMAT
include/config/auto.conf:271:warning: symbol value 'arch/x86/configs/i386_defconfig' invalid for ARCH_DEFCONFIG
include/config/auto.conf:617:warning: symbol value '-fcall-saved-ecx -fcall-saved-edx' invalid for ARCH_HWEIGHT_CFLAGS
*** Error during update of the configuration.
/home/pranav/android2/kernel/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 1
/home/pranav/android2/kernel/Makefile:496: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.
Click to expand...
Click to collapse
Trying to build it for Z3 MM Stock from Sony Copyright Archives
you have already configured toolchain?
if so, what are you using?
Then you must select defconfig, in case, shinano_leo_defconfig
Gustavo RD78 said:
you have already configured toolchain?
if so, what are you using?
Then you must select defconfig, in case, shinano_leo_defconfig
Click to expand...
Click to collapse
I have doomlord's toolchain..
This error only comes when i type that command at the end..
Following this Guide
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
pranavmali said:
I have doomlord's toolchain..
This error only comes when i type that command at the end..
Following this Guide
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
Click to expand...
Click to collapse
Which kernel are you trying to build also is your build machine 64-bit?
HerroYou said:
Which kernel are you trying to build also is your build machine 64-bit?
Click to expand...
Click to collapse
Its a 32bit machine
Building MM Stock based kernel
pranavmali said:
Its a 32bit machine
Building MM Stock based kernel
Click to expand...
Click to collapse
There is the problem, you need a 64 bit machine.
First you need to configure the kernel by making the defconfig.
Then you need to specify architecture you're building for using ARCH command.
See here:
http://developer.sonymobile.com/kno...h-a-linux-kernel-from-sony-copyleft-archives/
Also I don't see a branch for 23.5.A.0.575 which is the latest public MM firmware for Z3, so you need to grab the source code for this version off http://developer.sonymobile.com/downloads/xperia-open-source-archives/

[Completed] Ninja_wrapper error

building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!
skyskidder said:
building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!
Click to expand...
Click to collapse
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.
blinoff82 said:
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.
Click to expand...
Click to collapse
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!
skyskidder said:
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!
Click to expand...
Click to collapse
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...
blinoff82 said:
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...
Click to expand...
Click to collapse
Hey thanks for the idea on using this new repo for the device blobs and providing the link! But i have a few questions.
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
You dont need to give me a full out explanation a brief one will do if you can, if you cant dont sweat it!
I will also try this new repo when i get home and I'll update you on how it goes.
Thank you so very much!
-Sky
skyskidder said:
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
Click to expand...
Click to collapse
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.
blinoff82 said:
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.
Click to expand...
Click to collapse
Welp. I tried what you told me to do and Ive gotten farther but i ran into another error.
FAILED: /bin/bash -c "(make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= cyanogenmod_jf_defconfig ) && (if [ ! -z "" ]; then echo "Overriding kernel config with ''"; echo >> /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" oldconfig; fi ) && (make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" savedefconfig ) && (if [ ! -z "" ]; then echo "Using additional config ''"; kernel/samsung/jf/scripts/kconfig/merge_config.sh -m -O /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config kernel/samsung/jf/arch/arm/configs/; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" KCONFIG_ALLCONFIG=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config alldefconfig; fi )"
make: Entering directory '/home/lochlan/LAOS/kernel/samsung/jf'
GEN /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/basic/fixdep
/home/lochlan/LAOS/kernel/samsung/jf/scripts/basic/fixdep.c:106:23: fatal error: sys/types.h: No such file or directory
compilation terminated.
scripts/Makefile.host:118: recipe for target 'scripts/basic/fixdep' failed
make[2]: *** [scripts/basic/fixdep] Error 1
/home/lochlan/LAOS/kernel/samsung/jf/Makefile:417: recipe for target 'scripts_basic' failed
make[1]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
make: Leaving directory '/home/lochlan/LAOS/kernel/samsung/jf'
[ 6% 2204/33925] target R.java/Manifest.java: framework-res (/home/lochlan/LAOS/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp)
warning: string 'candidates_style' has no default translation.
warning: string 'gsm_alphabet_default_charset' has no default translation.
warning: string 'wfcSpnFormat' has no default translation.
nothing matches overlay file default_wallpaper.png, for flavor hdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxxhdpi-v4
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
#### make failed to build some targets (08:00 (mm:ss)) ####
Click to expand...
Click to collapse
Any idea what this error is?
Sorry my friend you should think for yourself. That's all.
http://stackoverflow.com/questions/37771339/sys-types-h-no-such-file-or-directory
:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...
skyskidder said:
:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Hi, thanks for taking your time to help me. Sadly this is the original guide I have been following when attempting to build my ROM.

Resurrection Remix nougat sync error

I'm trying to download Resurrection Remix repo files. Already downloaded 32GB but then at a point it showed me this error and the sync exited :
Fetching projects : 100% (586/586)
error: Exited sync due to fetch errors
I even tried with repo sync -f but it didn't work. Same error at that particular point. Please somebody tell me what to do. I dont want this 32GB to be a waste.
You need to scroll up and see which repo is failing to sync. Then you can try to figure it what the problem with that one is.
jisoo said:
You need to scroll up and see which repo is failing to sync. Then you can try to figure it what the problem with that one is.
Click to expand...
Click to collapse
Oh I see, acrually there are many files which are showing error while fetching ( "error: cannot fetch platform/prebuilts/go/darwin-x86" and many more). But the thing is how do I fix this ? I have a stable network connection but how can i download those particular files which are not being fetched ?
Suvam Mondal said:
Oh I see, acrually there are many files which are showing error while fetching ( "error: cannot fetch platform/prebuilts/go/darwin-x86" and many more). But the thing is how do I fix this ? I have a stable network connection but how can i download those particular files which are not being fetched ?
Click to expand...
Click to collapse
The repository is either not there anymore, or the branch which repo is looking for doesn't exist.
You can have a look at the manifest in .repo/manifest.xml to see in more detail which URL and branch this is.
How did you get this manifest file (i.e. how did you init your repo) which has such non-existing repos?
jisoo said:
The repository is either not there anymore, or the branch which repo is looking for doesn't exist.
You can have a look at the manifest in .repo/manifest.xml to see in more detail which URL and branch this is.
How did you get this manifest file (i.e. how did you init your repo) which has such non-existing repos?
Click to expand...
Click to collapse
Dont know, just followed the instructions in the Resurrection Remix github page.
However, restarted my pc and that error seemed to be fixed, but got this error at the last step of the process(i.e, during uncompression of files)
I have attached the log file. Please have a look and tell me what to do.
Suvam Mondal said:
Dont know, just followed the instructions in the Resurrection Remix github page.
However, restarted my pc and that error seemed to be fixed, but got this error at the last step of the process(i.e, during uncompression of files)
I have attached the log file. Please have a look and tell me what to do.
Click to expand...
Click to collapse
It looks like there was some errors downloading some of the hardware/qcom repositories, and some of the files are corrupt. That really should not happen by itself, and you may have other bigger issues happening with your VM.
Anyway, you have the option of deleting everything and starting from scratch. If you don't want to do that, you can try deleting the ".repo/project-objects/LineageOS/hardware_qcom_media.git/" and possibly the other hardware_qcom folders. This may remove all the corrupted files as well, and let you re-download only those repositories by doing "repo sync" later.
If repo is able to finish successfully, you should at least have non-corrupted files for the build, though as I said you may have some deeper filesystem corruption issues going on as well.
jisoo said:
It looks like there was some errors downloading some of the hardware/qcom repositories, and some of the files are corrupt. That really should not happen by itself, and you may have other bigger issues happening with your VM.
Anyway, you have the option of deleting everything and starting from scratch. If you don't want to do that, you can try deleting the ".repo/project-objects/LineageOS/hardware_qcom_media.git/" and possibly the other hardware_qcom folders. This may remove all the corrupted files as well, and let you re-download only those repositories by doing "repo sync" later.
If repo is able to finish successfully, you should at least have non-corrupted files for the build, though as I said you may have some deeper filesystem corruption issues going on as well.
Click to expand...
Click to collapse
Thank you very much, it worked. Successfully downloaded the repo files :
But now I'm stuck at the breakfast codename step
My device(Meizu m2 note) has no codename, you know any alternate way for this step ?
Suvam Mondal said:
Thank you very much, it worked. Successfully downloaded the repo files :
But now I'm stuck at the breakfast codename step
My device(Meizu m2 note) has no codename, you know any alternate way for this step ?
Click to expand...
Click to collapse
That would be because RR doesn't officially support this device, and therefore the device and kernel trees are not in the repo probably.
You'll need to port the device yourself, which may be difficult or easy (depending on your experience and how well supported the device generally is).
I had a quick look, and it's probably best if you use source trees from the dev who builds for LineageOS: https://github.com/Moyster?tab=repositories
You'll want to be familiar with the basics of git and github for this, I think.
Best way to figure out what is needed to port a device to another ROM is to compare the device trees of an identical device on the 2 different ROMs. So for instance, because I have a Nexus 5X (bullhead), I would compare the device_lge_bullhead repos in both Resurrection Remix and LineageOS, in order to figure out what I need to add to port a LineageOS device tree to Resurrection Remix.
Anyway, that's pretty much all I can suggest. If you have any specific question, feel free to post here or send me a PM.
Good luck!
jisoo said:
That would be because RR doesn't officially support this device, and therefore the device and kernel trees are not in the repo probably.
You'll need to port the device yourself, which may be difficult or easy (depending on your experience and how well supported the device generally is).
I had a quick look, and it's probably best if you use source trees from the dev who builds for LineageOS: https://github.com/Moyster?tab=repositories
You'll want to be familiar with the basics of git and github for this, I think.
Best way to figure out what is needed to port a device to another ROM is to compare the device trees of an identical device on the 2 different ROMs. So for instance, because I have a Nexus 5X (bullhead), I would compare the device_lge_bullhead repos in both Resurrection Remix and LineageOS, in order to figure out what I need to add to port a LineageOS device tree to Resurrection Remix.
Anyway, that's pretty much all I can suggest. If you have any specific question, feel free to post here or send me a PM.
Good luck!
Click to expand...
Click to collapse
Yes, almost there. This is the first time I am building a ROM, very excited
But i got this error while building the ROM. First i tried with USE_NINJA which gave some error build-lineage_m2note.ninja failed to make. Then I tried with USE_NINJA=false which gave me this error(log file).
I have attached the log file. Please tell me what to do. I followed every step still I got this error, that also in the final step . :crying:
Suvam Mondal said:
Yes, almost there. This is the first time I am building a ROM, very excited
But i got this error while building the ROM. First i tried with USE_NINJA which gave some error build-lineage_m2note.ninja failed to make. Then I tried with USE_NINJA=false which gave me this error(log file).
I have attached the log file. Please tell me what to do. I followed every step still I got this error, that also in the final step . :crying:
Click to expand...
Click to collapse
I would stick with not adding any specific definition for the build, and just using the standard variables (so not adding USE_NINJA true or false), and then having a look at the error messages there.
At least, I won't be able to help much otherwise, as I always just use the default settings for the build.
In the log you attached, there's a bunch of "Cannot allocate memory" errors. I would have a look at the kernel logs as well (you can get these with the "dmesg" command, or using "cat /var/log/kern.log"). You will probably see what is causing the error from here, as it seems to be related to the OS itself.
You may have out of memory (OOM) issues, which is common with nougat builds. To fix that, you can follow the instructions here: http://stackoverflow.com/questions/...ror-try-increasing-heap-size-with-java-option
jisoo said:
I would stick with not adding any specific definition for the build, and just using the standard variables (so not adding USE_NINJA true or false), and then having a look at the error messages there.
At least, I won't be able to help much otherwise, as I always just use the default settings for the build.
In the log you attached, there's a bunch of "Cannot allocate memory" errors. I would have a look at the kernel logs as well (you can get these with the "dmesg" command, or using "cat /var/log/kern.log"). You will probably see what is causing the error from here, as it seems to be related to the OS itself.
You may have out of memory (OOM) issues, which is common with nougat builds. To fix that, you can follow the instructions here: http://stackoverflow.com/questions/...ror-try-increasing-heap-size-with-java-option
Click to expand...
Click to collapse
Did that. But now I am facing this nina_wrapper error 1 at 99% of compilation
Code:
[ 99% 3295/3298] Docs droiddoc: /home/...t/target/common/docs/doc-comment-check
FAILED: /bin/bash /home/suvam/rr/out/target/common/docs/doc-comment-check-timestamp.rsp
frameworks/base/core/java/android/provider/Settings.java:3657: error 101: Unresolved link/see tag "android.provider.Settings.Global#KEY_SMS_BREATH" in android.provider.Settings.System
frameworks/base/core/java/android/widget/SeekBar.java:41: error 101: Unresolved link/see tag "ProgressBar#setMax(int)" in android.preference.CustomSeekBarPreference
DroidDoc took 345 sec. to write docs to /home/suvam/rr/out/target/common/docs/doc-comment-check
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Suvam Mondal said:
Did that. But now I am facing this nina_wrapper error 1 at 99% of compilation
Code:
[ 99% 3295/3298] Docs droiddoc: /home/...t/target/common/docs/doc-comment-check
FAILED: /bin/bash /home/suvam/rr/out/target/common/docs/doc-comment-check-timestamp.rsp
frameworks/base/core/java/android/provider/Settings.java:3657: error 101: Unresolved link/see tag "android.provider.Settings.Global#KEY_SMS_BREATH" in android.provider.Settings.System
frameworks/base/core/java/android/widget/SeekBar.java:41: error 101: Unresolved link/see tag "ProgressBar#setMax(int)" in android.preference.CustomSeekBarPreference
DroidDoc took 345 sec. to write docs to /home/suvam/rr/out/target/common/docs/doc-comment-check
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
As per this page (http://stackoverflow.com/questions/36733124/failed-to-make-the-source-of-android-6-0), you should check which JDK version you are building with. I've never seen this type of error, so you may just want to google it a bit further, if the JDK version doesn't help. Looks like you are making a lot of progress though!
jisoo said:
As per this page (http://stackoverflow.com/questions/36733124/failed-to-make-the-source-of-android-6-0), you should check which JDK version you are building with. I've never seen this type of error, so you may just want to google it a bit further, if the JDK version doesn't help. Looks like you are making a lot of progress though!
Click to expand...
Click to collapse
Checked. My jdk version is 1.8 as required for android 7
Resynced and used brunch DeviceCodeName and got this error
Code:
Building Kernel Config
make CFLAGS_MODULE="-fno-pic" -C kernel/meizu/m2note O=/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/home/suvam/rr/prebuilts/misc/linux-x86/ccache/ccache aarch64-linux-androidkernel-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= los14_m2note_defconfig
make[1]: Entering directory '/home/suvam/rr/kernel/meizu/m2note'
HOSTCC scripts/basic/fixdep
/bin/sh: 1: ccache: not found
scripts/Makefile.host:118: recipe for target 'scripts/basic/fixdep' failed
make[3]: *** [scripts/basic/fixdep] Error 127
/home/suvam/rr/kernel/meizu/m2note/Makefile:424: 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/suvam/rr/kernel/meizu/m2note'
vendor/cm/build/tasks/kernel.mk:283: recipe for target '/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ/.config' failed
make: *** [/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
It took approx 4 hours and then the compilation terminated.
Really hopeless now
*UPDATED*
resynced the repo and the device kernel and used brunch devicecode command and got this out of memory error and asked me to increase my heap size. How much should I set the heap size to ? I am having 6gb ram and current heap size is 3gb (by using java -Xmx 3072m)
I have attached the log file
Sync app email
Hi, i have installed on my Samsung s3 i9300 a resurrection remix but my app "aquamail" don't synchronizes in background.
When i update manually, it works regularly.
Please, can you help me?. :crying:
Thank's
mariorolex said:
Hi, i have installed on my Samsung s3 i9300 a resurrection remix but my app "aquamail" don't synchronizes in background.
When i update manually, it works regularly.
Please, can you help me?. :crying:
Thank's
Click to expand...
Click to collapse
Can someone help me?
mariorolex said:
Can someone help me?
Click to expand...
Click to collapse
Does anyone else have my own problem?. :crying::crying::crying:
Suvam Mondal said:
*UPDATED*
resynced the repo and the device kernel and used brunch devicecode command and got this out of memory error and asked me to increase my heap size. How much should I set the heap size to ? I am having 6gb ram and current heap size is 3gb (by using java -Xmx 3072m)
I have attached the log file
Click to expand...
Click to collapse
Reduce jack threads if you don't have at least 8GB free ram.
How do you solve Unresolved link/see tag error?

[HELP] Can't flash compiled AOSP

Hey guys, thank you in advance. I have an LG X Power (K220) and I started to develop the stock AOSP from source (Android 6.0.1). I followed all the instruction from LG and Google (downloaded both google and LG source and then merged them). After seven hours of compiling I got my image file: system.img, cache.img, userdata.img and ramdisk.img. It was the time to flash and test the new build, so I used these command:
Code:
fastboot flash cache cache.img
Code:
fastboot flash ramdisk ramdisk.img
But when I have to flash the system.img and the userdata the device tell me that the images are too big and the message “Invalid sparse file format at header magi”. So I googled it and I tried with:
Code:
fastboot -S 256M flash system.img
But nothing. I also read that I could try to modify the BoardConfig.mk and add:
Code:
TARGET_USERIMAGES_SPARSE_EXT_DISABLED := true
But I do not know what BoardConfig.mk I have to modify becouse when I merge the file and go to /device/lge/k7 there isn't the mk file, so I think that use the generic aosp for arm devices.
How could I solve this problem? Thank you another time :fingers-crossed:
Hi I'm also building AOSP for X Power. You need to change SYSTEM IMAGE partition size in aosp/device/generic/armv7-a-neon/BoardConfig.mk. That's beacouse we use "lunch 1" which mean "lunch aosp_arm-eng". If u need help send me message.
kko7 said:
Hi I'm also building AOSP for X Power. You need to change SYSTEM IMAGE partition size in aosp/device/generic/armv7-a-neon/BoardConfig.mk. That's beacouse we use "lunch 1" which mean "lunch aosp_arm-eng". If u need help send me message.
Click to expand...
Click to collapse
Are you able to build debug versions? That may help things for you.
Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1
kko7 said:
Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1
Click to expand...
Click to collapse
I fixed it. Now I am waiting for the compilation to finish.
If someone want I can upload it to AFH
kko7 said:
I fixed it. Now I am waiting for the compilation to finish.
If someone want I can upload it to AFH
Click to expand...
Click to collapse
How did you fix the error?
Modify build/core/clang/HOST_x86_common.mk
android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If that doesn't work then
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in aosp folder
kko7 said:
Modify build/core/clang/HOST_x86_common.mk
android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If that doesn't work then
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in aosp folder
Click to expand...
Click to collapse
Excellent, thank you! ?
Sands207 said:
Excellent, thank you! ?
Click to expand...
Click to collapse
No problem
kko7 said:
Maybe I will be able but I'm getting clang error, so I need to fix it first.
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [build/core/host_shared_library_internal.mk:51: out/host/linux-x86/obj/lib/libartd.so] Error 1
Click to expand...
Click to collapse
How do you fix it?
I trying make a build for my Xperia X and Xperia M2 Aqua, but, justly, launch that error...
sebasrock156 said:
How do you fix it?
I try to make a build for my Xperia X and Xperia M2 Aqua, but, justly, launch that error...
Click to expand...
Click to collapse
Modify core/clang/HOST_x86_common.mk
https://android-review.googlesource.com/c/platform/build/+/223100/1/core/clang/HOST_x86_common.mk
If this doesn't work then try this command:
cp /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/bin/ld
But you need to be in the aosp folder

Categories

Resources