Related
Note:
1. This is extension to the Karthik's Guide with Adam's Repo's...
2. Based on my experience i have created this Guide, I have successfully compiled the Build and sharing this with you so some one can try it...
Preparing the system:
Follow this Link until step 4.4 (i.e. 4.4 - Initialize Repository & Sync)
Start with sources:
Code:
cd ~/android/system/
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync -j4
Wait until it's finished (takes a lot of time!).
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync -j4
Initialize the environment
NOTE: If you have trouble syncing due to connection issues, try repo sync -j1. It's slower but some ISPs have issues with -j4/16
Want to make sure you didn't get any connection errors and have the complete repository? Just run the repo sync command again. It can't give you ANY errors.
Wait until it's finished (takes a lot of time!).
VERY IMPORTANT: Now, Lets add the device specific tree..
1) Open your File Browser,
2) Press Ctrl+H (to show hidden files/directories)
3) Navigate to android/system/.repo/manifest.xml
(Right Click & open the XML file in text editor)
4) Add
Code:
<project path="device/samsung/galaxyr" name="Adam77Root/android_device_samsung_galaxyr" remote="github" revision="jellybean"/>
BEFORE the manifest closing tags (</manifest>).
5) Save & Close the File.
Run another
Code:
$ repo sync
Get Device Specific Repos:
Code:
. build/envsetup.sh
Extract files from phone:
NOTE: You need to have cm10 installed on the phone.
Code:
cd ~/android/system/device/samsung/galaxyr/
./extract-files.sh
Code:
~/android/system/vendor/cm/get-prebuilts
Important Things to be taken care before Building ROM:
1. Add these line in Boarconfig.mk
Code:
TARGET_ARCH := arm
BOARD_EGL_NEEDS_LEGACY_FB := true
2. Change the below line.
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 5242880
to
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 7242880
3. Delete Overlay folder.
4. Go to build/tools/releasetools and open file "ota_from_target_files" and replace the whole code with this code from this link.
Ok, You are done Now...
Building the ROM:
Code:
brunch cm_galaxyr-eng
it will take around 2 - 3 Hours....
Congrats you are done
Now Go to ~/android/system/out/target/product/galaxyr/cm-10.1-XXXXXXXXX-UNOFFICIAL-galaxyr.zip copy it to mobile and flash it on your mobile..
*********************************************************************************
Updating the Build:
Code:
cd android/system
repo sync -j1
make installclean
brunch cm_galaxyr-eng
Big Thanks to Adam for his Efforts and Device tree..
Friends if i've missed some things please correct me ...
Gr8 mj! It will be better if u post ur error and how u solved.. By that it help others...
Sent from my GT-I9103 using xda app-developers app
Waiting for cm10.1 ROM now. Using Cm 10 and it is great
Sent from my GT-I9103 using xda app-developers app
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
wow that's cool buddy...
Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
Not yet. The first builds will be only previews. If 10.1 gets as stable as 10 now is, I'll change to it. But there is work to be done on 10 as well and better to do it on a working build first. But I'm also very excited to see 10.1, so will definitely work on it.
Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.
sarun_biotech said:
Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.
Click to expand...
Click to collapse
Yes buddy you need to run it...
Friends updated the Guide with all the details and problems i have faced, so now you can simply follow the steps and build CM 10.1...
Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?
I used wubi... dual boot...
sarun_biotech said:
Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?
Click to expand...
Click to collapse
Even i also faced this problem, so i need to install the Ubuntu through the CD in different partition so that i have both Windows 7 and Ubuntu 12.10 64 Bit...
If you have any problem just PM me...
Cm10 official
Is there a official CM10 for galaxy r. If yes plz snd the link.
akirockstarr said:
Is there a official CM10 for galaxy r. If yes plz snd the link.
Click to expand...
Click to collapse
CM 10 & 10.1 are official for Galaxy R users and Unofficial from CM Team point of view...
1. CM 10 Thread.
2. CM 10.1 Thread.
Guys Check out xda-university.com An answer to all our development questions. :thumbup:
Everything at a single place.
I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Code:
[email protected]:~/mydev/cm10.1/device/samsung/galaxyr$ ./extract-files.sh
remote object '/system/etc/wifi/bcm4330_mfg.bin' does not exist
remote object '/system/etc/wifi/nvram_mfg.txt' does not exist
remote object '/system/bin/wlandutservice' does not exist
remote object '/system/bin/macloader' does not exist
remote object '/system/bin/mfgloader' does not exist
remote object '/system/bin/nv_hciattach' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/wlandutservice': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/macloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/mfgloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/nv_hciattach': No such file or directory
remote object '/system/bin/brcm_patchram_plus' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/brcm_patchram_plus': No such file or directory
remote object '/system/bin/drexe' does not exist
remote object '/system/bin/npsmobex' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/drexe': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/npsmobex': No such file or directory
Why are we extracting files from phone? The device tree should be holding them right?
kishoreinme said:
I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Click to expand...
Click to collapse
Not an issue you can proceed with next command, it will take care of these files.....
So I used @kylevessPL's "ready" configuration ( https://github.com/kylevessPL/android_device_lge_l70pn ) for our device's CM 12.1 to try to compile it and see what happens.
But with no luck, unfortunately. For some reason, when I execute the brunch command, errors show up.
Here's an example of one of the a lot similar errors that appear just right after the previous one was fixed: http://pastebin.com/KkhjttJB .
The exact error here is:
"Notice file: external/zip/NOTICE -- /home/max-pc/cm-12.1/out/target/product/l70pn/obj/NOTICE_FILES/src//system/xbin/zip.txt
make: *** No rule to make target `device/lge/l70pn/prebuilt/usr/keylayout/Generic-290.kl', needed by `/home/max-pc/cm-12.1/out/target/product/l70pn/system/usr/keylayout/Generic-D290.kl'. Stop."
P.S: You can also see the Terminal error in the picture attached to the post.
P.S. 2: I did NOT execute the "vendor/cm/get-prebuilts" command in "Initializing repo" section, because it always says: "bash: vendor/cm/get-prebuilts: No such file or directory"
proudlytm said:
So I used @kylevessPL's "ready" configuration ( https://github.com/kylevessPL/android_device_lge_l70pn ) for our device's CM 12.1 to try to compile it and see what happens.
But with no luck, unfortunately. For some reason, when I execute the brunch command, errors show up.
Here's an example of one of the a lot similar errors that appear just right after the previous one was fixed: http://pastebin.com/KkhjttJB .
The exact error here is:
"Notice file: external/zip/NOTICE -- /home/max-pc/cm-12.1/out/target/product/l70pn/obj/NOTICE_FILES/src//system/xbin/zip.txt
make: *** No rule to make target `device/lge/l70pn/prebuilt/usr/keylayout/Generic-290.kl', needed by `/home/max-pc/cm-12.1/out/target/product/l70pn/system/usr/keylayout/Generic-D290.kl'. Stop."
P.S: You can also see the Terminal error in the picture attached to the post.
P.S. 2: I did NOT execute the "vendor/cm/get-prebuilts" command in "Initializing repo" section, because it always says: "bash: vendor/cm/get-prebuilts: No such file or directory"
Click to expand...
Click to collapse
Renames "l70pn" to the original "l70pds".... or edit the following lines;
in the path "device/lge/l70pds/device_l70pds.mk
the_naxhoo said:
Renames "l70pn" to the original "l70pds".... or edit the following lines;
in the path "device/lge/l70pds/device_l70pds.mk
Click to expand...
Click to collapse
I just tried but I don't know the new compile command. Can you tell it to me ? When I do it with cm_l70pds-userdebug instead with cm_l70pn-userdebug command, this happens:
[email protected]:~/cm-12.1$ brunch cm_l70pds-userdebug
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
Device l70pds not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for l70pds not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_l70pds'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
proudlytm said:
I just tried but I don't know the new compile command. Can you tell it to me ? When I do it with cm_l70pds-userdebug instead with cm_l70pn-userdebug command, this happens:
[email protected]:~/cm-12.1$ brunch cm_l70pds-userdebug
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
Device l70pds not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for l70pds not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_l70pds'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse
no no no, my mistake, i'm sorry... you should use Github "VM03". Or my Github ( https://github.com/ignacio28 )
just change "device/lge/l70pds/prebuilt/usr/keylayout/Generic-290.kl:system/usr/keylayout/Generic-D290.kl" to "device/lge/l70pds/prebuilt/usr/keylayout/Generic-D290.kl:system/usr/keylayout/Generic-D290.kl" in the file "device_170pn.mk"
@proudlytm Would you like to do a telegram group for compilation on LG L Fino? @the_naxhoo is helping me with the compilation. If both of you tells me what to do i can help. I have already CM 12.1 sources downloads so maybe i can do something with my computer
carliquiss said:
@proudlytm Would you like to do a telegram group for compilation on LG L Fino? @the_naxhoo is helping me with the compilation. If both of you tells me what to do i can help. I have already CM 12.1 sources downloads so maybe i can do something with my computer
Click to expand...
Click to collapse
I wish I could help but I accidentally hard bricked my phone and I'm gonna take it to the place I bought it from and they're either gonna get it exchanged for a new one, or they will repair it. I think it will take like 1 week for everything to be done.
proudlytm said:
I wish I could help but I accidentally hard bricked my phone and I'm gonna take it to the place I bought it from and they're either gonna get it exchanged for a new one, or they will repair it. I think it will take like 1 week for everything to be done.
Click to expand...
Click to collapse
Okey no problem, if you want you can help is debugging the compilation and we can try in our smartphones. If you are interested send me a pm with your telegram name
Enviado desde mi Zippers 5 mediante Tapatalk
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?
Kernel Source of Nokia 1
(TA-1047/TA-1060/TA-1056/TA-1079/TA-1066)
LINK > https://github.com/DhirajSurvase/Kernel_Nokia_1_MT6737
Instructions >
clone the source code
go to kernel dir
run "bash build.sh" command
ur compiled kernel will be under out/arch/arm/*
Official release of Nokia 1 Kernel sources available at https://www.nokia.com/en_int/phones/opensource
Hi,
We tried the official kernel and built it. After flashing the kernel, phone boot and it asked for a password. We gave password "1234" and it reboots and went in recovery.
Its always rebooting in recovery. We flashed the original boot image. Behavior did not change.
Is there any other recovery image we can use and flash the original boot image and bring the phone to working condition?
Thank You!
Mayur
DhirajMS said:
Kernel Source of Nokia 1
(TA-1047/TA-1060/TA-1056/TA-1079/TA-1066)
LINK > https://github.com/DhirajSurvase/Kernel_Nokia_1_MT6737
Instructions >
clone the source code
go to kernel dir
run "bash build.sh" command
ur compiled kernel will be under out/arch/arm/*
Click to expand...
Click to collapse
Everyone, help me compile kernel from this source please. I can't do it, because i'm noobie for compile any sources.
ntnamkg said:
Everyone, help me compile kernel from this source please. I can't do it, because i'm noobie for compile any sources.
Click to expand...
Click to collapse
just clone it..
and hit "bash build.sh"
Thanks for respond. But, it is fail, below (some text):
make[1]: *** [scripts] Error 2
make[1]: Leaving directory `/home/namnt/Nokia1/Kernel_Nokia_1_MT6737-master/out'
make: *** [sub-make] Error 2
make: Leaving directory `/home/namnt/Nokia1/Kernel_Nokia_1_MT6737-master'
Click to expand...
Click to collapse
I try build on Ubuntu 14.04, 16.04 and Manjaro linux, all get this notice.
Ok
build.sh: line 35: make: command not found
build.sh: line 39: make: command not found
Click to expand...
Click to collapse
After run bash build get above notice. How to fix it? Thanks
ntnamkg said:
After run bash build get above notice. How to fix it? Thanks
Click to expand...
Click to collapse
apt-get install build-essential
would install make, gcc and other required tools.
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