Database Info

[Q] Having trouble building CM7 from source using OS X

So I've been trying to build CM7 from source following this guide. I follow it exactly (apart from replacing "Vision" with "Glacier" and "-froyo" with "-gingerbread") and it gives me an error when I enter in the command "make -j`sysctl -an hw.logicalcpu` bacon"
"make: *** No rule to make target `vendor/htc/glacier/proprietary/MS-HTCVISION-KNT20-02.apk', needed by `out/target/product/glacier/system/app/MS-HTCVISION-KNT20-02.apk'. Stop.
make: *** Waiting for unfinished jobs...."
And countless other ones during the process.
Any idea why this is happening? I'm on OS X if it helps.

I think I've waiting long enough to warrant a bump.
Anyone?

ELBdelorean said:
So I've been trying to build CM7 from source following this guide. I follow it exactly (apart from replacing "Vision" with "Glacier" and "-froyo" with "-gingerbread") and it gives me an error when I enter in the command "make -j`sysctl -an hw.logicalcpu` bacon"
"make: *** No rule to make target `vendor/htc/glacier/proprietary/MS-HTCVISION-KNT20-02.apk', needed by `out/target/product/glacier/system/app/MS-HTCVISION-KNT20-02.apk'. Stop.
make: *** Waiting for unfinished jobs...."
And countless other ones during the process.
Any idea why this is happening? I'm on OS X if it helps.
Click to expand...
Click to collapse
My first thought for what's wrong is that you have the latest version of gmake(3.82) which has a bug that prevents android from building. If you haven't already done so, downgrade to gmake 3.81 and see if that solves your problem. You can do that following the step-by-step from the AOSP build guide or the instructions in this post.

Yes, I have downgraded gmake.

Ok, I think I figured out why you're getting the error which sounds like it gets thrown when the proprietary files are not pulled from your phone through adb when you run extract-files.sh as they should. From here:
make: *** No rule to make target `.../[something]', needed by `.../[something]'. Stop.
You need to copy the proprietary files off your phone. Make sure you have ADB set up and plug your device to your computer via USB. Then run:
Code:
cd /Volumes/CyanogenModWorkspace/android/system/device/htc/glacier/
./extract-files.sh
Click to expand...
Click to collapse
Hopefully that will get you up and running.

[Q] Help compiling Galaxy W sources

Hopefully this is quick.
When I type "./build.sh kezraplanes (my username)" I get this:
[email protected]:~/samsung_ancora/platform$ ./build.sh kezraplanes
./build.sh: linha 43: cd: /home/kezraplanes/samsung_ancora/platform/Android: file or directory does not exist
make: *** no rule to process target `update-api'. Stop.
make: *** no rule to process target `PRODUCT-generic-eng'. Stop.
Click to expand...
Click to collapse
Any idea why this is happening? I'm doing exactly what the readme tells me to xD
P.S. Go easy on me, I'm learning this
Edit: The command line has been roughly translated since my Ubuntu is in Portuguese and I obviously translated the errors into English myself.

[INCOMPLETE HOW TO] Reconstruct Mi 4c kernel source

I'm writing this incomplete instruction for my friend @emfox based on the instruction I used to reconstruct Redmi 2 kernel source http://forum.xda-developers.com/and.../how-to-convert-qualcomms-dtb-to-dts-t3221223 Unfortunately I couldn't finish this instruction without Mi 4c device. This is just a quick look, short information, to check the possibility to reconstruct an open source kernel based on CAF project. It's will be hard but not impossible.
1. Clone MSM8992 vanilla kernel source, LA.BF64.1.2.2-02940-8x92.0 release for Marshmallow 6.0.1 (release LA.BF64.1.2.1.c1-05410-8x92.0 branch LA.BF64.1.2.1.c1_rb1.38 for Lollipop 5.1.1) https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/?h=LA.BF64.1.2.2_rb4.22
Code:
git clone git://codeaurora.org/quic/la/kernel/msm-3.10 -b LA.BF64.1.2.2_rb4.22
2. Stock 4c kernel was compiled without CONFIG_IKCONFIG, vanilla kernel config libra_defconfig attached
3. Attached 3 dts file from stock kernel, msm8992-mtp-0xc.dts seem compatible to emfox device (qcom,board-id = <0xc 0x0>; )
4. Attached a vanilla dts file for MSM8992 MTP msm8992-mtp.dts as a result of LA.BF64.1.2.2_rb4.22 built
You can compare msm8992-mtp-0xc.dts to msm8992-mtp.dts using a diff tool (i.e. Kompare app) and start creating device tree source for Mi 4c: msm8992-mtp-libra.dts, msm8992-mtp-libra.dtsi, batterydata-itech-3020mah.dtsi, dsi-panel-sharp-rsp61322-1080p-video.dtsi, dsi-panel-auo-nt35596-1080p-video.dtsi, dsi-panel-lgd-nt35596-1080p-video.dtsi, dsi-panel-sharp-nt35595-1080p-video.dtsi, dsi-panel-jdi-nt35595-1080p-video.dtsi, msm8992-camera-sensor-mtp-libra.dtsi, etc. You can use https://github.com/kumajaya/android...mmit/3de4f3564a82f44049a8664d4383c6d3ed43cb47 as a reference. Mi 4c based on same board platform as LG G4 or Nexus 5X. Good luck!
How to build kernel outside Android source tree:
I assume your home directory is /home/user, kernel source inside /home/user/android/libra/kernel, Android source tree inside /home/user/android/system-13.0
1. Create an environtment text file, save it as /home/user/android/build-arm64.env (change CROSS_COMPILE to point to your toolchain):
Code:
export CROSS_COMPILE='/home/user/android/system-13.0/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-'
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm64
export ARCH=arm64
2. Import environtment file above, create a build directory outside the kernel source tree (to keep the kernel source clean):
Code:
$ cd /home/user/android/libra/kernel
$ source /home/user/android/build-arm64.env
$ mkdir -p /home/user/android/libra/kernel-out
$ make O=/home/user/android/libra/kernel-out mrproper
3. Import the kernel config file, change the kernel configuration (if needed) and start the building process:
Code:
$ make O=/home/user/android/libra/kernel-out libra_defconfig
$ make O=/home/user/android/libra/kernel-out menuconfig
$ make O=/home/user/android/libra/kernel-out
4. Copy the resulting kernel and modules (if available) to a binary directory:
Code:
$ mkdir -p /home/user/android/libra/kernel-bin
$ mkdir -p /home/user/android/libra/kernel-bin/modules
$ cp /home/user/android/libra/kernel-out/arch/arm64/boot/Image /home/user/android/libra/kernel-bin/
$ find /home/user/android/libra/kernel-out/ -type f -name *.ko -exec cp {} /home/user/android/libra/kernel-bin/modules/ \;
Creating a boot image:
Remember, this is incomplete guide

Roger that! I thought you have bought xiaomi 4c several days ago.

You're so kind to provide this tutorial. Since I know nearly nothing about kernel development, I'll start learning it step by step.

Thanks for the instruction.
Also @ekkilm / Teamsuperluminal might be able to help :fingers-crossed:

Autines said:
Roger that! I thought you have bought xiaomi 4c several days ago.
Click to expand...
Click to collapse
No, too expensive and my main device still in very good condition :laugh:
emfox said:
You're so kind to provide this tutorial. Since I know nearly nothing about kernel development, I'll start learning it step by step.
Click to expand...
Click to collapse
No problem, you also helped me a lot.
kevinnol said:
Thanks for the instruction.
Also @ekkilm / Teamsuperluminal might be able to help :fingers-crossed:
Click to expand...
Click to collapse
You're welcome.

OK, I've gone through the buiding kernel outside android tree steps, and now am trying to build MSM8992 vanilla kernel source from inside cm13 source directory.
command is 'source build/envsetup.sh &&breakfast libra && mka bootimage', but always got a command not found error, don't know what is missing...
Code:
<manifest>
<remote name="ghub" fetch="git://github.com/"/>
<project name="xiaomi-dev/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>
<project name="AndropaX/proprietary_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="ghub" revision="master"/>
</manifest>
and put kernel source to kernel/xiaomi/libra.
The error is
Code:
host C++: libc++_static <= external/libcxx/src/strstream.cpp
host C++: libc++_static <= external/libcxx/src/system_error.cpp
host C++: libc++_static <= external/libcxx/src/thread.cpp
host C++: libc++_static <= external/libcxx/src/typeinfo.cpp
host C++: libc++_static <= external/libcxx/src/utility.cpp
host C++: libc++_static <= external/libcxx/src/valarray.cpp
host StaticLib: libc++abi (/home/emfox/android/system-13.0/out/host/linux-x86/obj/STATIC_LIBRARIES/libc++abi_intermediates/libc++abi.a)
host StaticLib: libmincrypt (/home/emfox/android/system-13.0/out/host/linux-x86/obj/STATIC_LIBRARIES/libmincrypt_intermediates/libmincrypt.a)
host C: acp <= build/tools/acp/acp.c
host StaticLib: libhost (/home/emfox/android/system-13.0/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/libhost.a)
Building kernel...
/bin/bash: line 1: @: command not found
Export includes file: system/core/libcutils/Android.mk -- /home/emfox/android/system-13.0/out/host/linux-x86/obj/SHARED_LIBRARIES/libcutils_intermediates/export_includes
make[1]: Entering directory '/home/emfox/android/system-13.0/kernel'
make[1]: *** No rule to make target 'libra_defconfig'. Stop.
make[1]: Leaving directory '/home/emfox/android/system-13.0/kernel'
make[1]: Entering directory '/home/emfox/android/system-13.0/kernel'
make[1]: *** No rule to make target 'headers_install'. Stop.
make[1]: Leaving directory '/home/emfox/android/system-13.0/kernel'
kernel/xiaomi/libra/AndroidKernel.mk:110: recipe for target '/home/emfox/android/system-13.0/out/target/product/libra/obj/KERNEL_OBJ/.build_stamp' failed
make: *** [/home/emfox/android/system-13.0/out/target/product/libra/obj/KERNEL_OBJ/.build_stamp] Error 2
make: *** Waiting for unfinished jobs....
make: Leaving directory '/home/emfox/android/system-13.0'
#### make failed to build some targets (01:41 (mm:ss)) ####

Hi @emfox, i would gladly help you since i just finished cm12.1 build with device tree (i made a thread, with prebuilt kernel of course) and I'd like to start with cm13.
If you open source kernel has compiled correctly, can you do a "kernel_xiaomi_libra" github repository?

alterbang said:
Hi @emfox, i would gladly help you since i just finished cm12.1 build with device tree (i made a thread, with prebuilt kernel of course) and I'd like to start with cm13.
If you open source kernel has compiled correctly, can you do a "kernel_xiaomi_libra" github repository?
Click to expand...
Click to collapse
no, not really. I haven't finished the source.
I have little kernel hacking knowledge, so I'd like to set up and working environment first, then I'll go to deal these *dts files.

Ok, sorry then. I thought "'I've gone through the buiding kernel outside android tree steps," meant you had already finished
Maybe when I'll have some free time in the next days i will give the entire process a try!

alterbang said:
Ok, sorry then. I thought "'I've gone through the buiding kernel outside android tree steps," meant you had already finished
Maybe when I'll have some free time in the next days i will give the entire process a try!
Click to expand...
Click to collapse
oh, that would be great. I'm a developer but just on web and application domain, and have no much time to dig into kernel deeply. But I am learning

@emfox Don't forget copy libra_defconfig to arch/arm64/configs/

ketut.kumajaya said:
@emfox Don't forget copy libra_defconfig to arch/arm64/configs/
Click to expand...
Click to collapse
yes i have copied, or the error msg will be 'cannot found kernel configuration ...blabla'

emfox said:
yes i have copied, or the error msg will be 'cannot found kernel configuration ...blabla'
Click to expand...
Click to collapse
Please recheck your device board config, you can use LG G4 config as a reference https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/BoardConfigCommon.mk#L49-L61

don't understand a thing from the coding but from what i have learned, kernel source would be awesome to develop more for the 4c. keep up the good work!

Yea would be really awesome, too bad xiaomi doesn't release it themself
Well there are a lot of crazy guys here on xda so there's still hope

Thinking to help @emfox to create a such template for 4c but no much free time here, just a short free time between my workload and no much interest without the device

ketut.kumajaya said:
Thinking to help @emfox to create a such template for 4c but no much free time here, just a short free time between my workload and no much interest without the device
Click to expand...
Click to collapse
yes, a working building directory structure will help me start the porting.
but no need hurry, we now have cm from www.teamsuperluminal.org. although it's close-sourced and use prebuilt kernel, still much better than miui.

Hi, anyone can give some more info how to build AOSP from nexus 5X?

am i alone like Taylor?

Looks like the kernel source will be released soon: http://en.miui.com/thread-235127-1-1.html

[Resolved] Need help with compiling android 7.0 from source!

Hello xda users,
Today I started to build android 7.0 aosp for the Zenfone 2 ZE550ML (Z008) using this guide and the Cyanogenmod guide.
But when trying to build the rom with "lunch" and "make Z008" I received an error message (this also happends with "make -j2" and "sudo")(soms words are dutch):
Running kati to generate build-aosp_x86.ninja...
out/build-aosp_x86.ninja is missing, regenerating...
<A lot of text>
build/core/binary.mk:928: warning: overriding commands for target `out/target/product/generic_x86/obj/STATIC_LIBRARIES/libv8_intermediates/src/base/atomicops_internals_x86_gcc.o'
build/core/binary.mk:928: warning: ignoring old commands for target `out/target/product/generic_x86/obj/STATIC_LIBRARIES/libv8_intermediates/src/base/atomicops_internals_x86_gcc.o'
build/core/binary.mk:664: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:664: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:668: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
build/core/binary.mk:668: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
build/core/ninja.mk:163: recept voor doel 'out/build-aosp_x86.ninja' is mislukt
make: *** [out/build-aosp_x86.ninja] Eliminated
#### make failed to build some targets (52 seconds) ####
See the whole log here
Can anyone help me solve this issue?
-Greeting Indy

I installed kati manually and added
export EXPERIMENTAL_USE_JAVA8=true
export USE_NINJA=false
if [ -d "$HOME/android_source/build/kati" ] ; then
PATH="$HOME/android_source/build/kati:$PATH"
fi
to my bashrc.sh file.
After this it worked just fine , but now have to see if it finishes.

Well, got an error 41 so Lets try it all over again

Solved
Solved

Any pointers. I'm running Linux Ubuntu from a VM I got updates and tools set repo and ran sync found my device binaries on github made git clone and put them in folder "vendor" and ran "make -j3" cause the VM has 3 cores assigned. It failed when It go to jack. Make with Jack is confusing. What do I do did i put the right files in the right place?
Sent from my SM-G900T using XDA-Developers mobile app

@Migush
How did you solve the problem?
Thanks for the response.

excelly2k1 said:
@Migush
How did you solve the problem?
Thanks for the response.
Click to expand...
Click to collapse
I'm sorry, but I don't know. It just worked after I did something I can't remember.

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?