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.

Merging HALO code?

How do I merge HALO into my ROM? I'm a little lost here lol
Device: Nexus 5 16GB Black
ROM: PABETA3 (ZacksBuild) w/ Franco r32

Open a terminal and cd to the directory that you set up your repo. Then, in your browser, open up [1/2] Settings: HALO and [2/2] Frameworks: HALO from the gerrit.
Because it's titled [1/2], we'll start with the settings entry.
See where it says "Project AOSPA/android_packages_apps_Settings"? That's important. It says that this change is in packages/apps/Settings. So, in terminal:
Code:
cd packages/apps/Settings
Now, in the top right of the page, there's a download button. Click that, then choose "anonymous http" from the dropdown, instead of "repo". Click the clipboard button next to the one titled "cherry pick". It will copy the command to your clipboard, then paste it in terminal. It should look like this:
Code:
git fetch https://gerrit.paranoidandroid.co/AOSPA/android_packages_apps_Settings refs/changes/39/239/13 && git cherry-pick FETCH_HEAD
Press enter, and it'll download the changes. If all goes well, you'll see a message saying it's done. If not, you'll need to fix the errors. I'll get to that later.
Now, bring your terminal back to the top of your build directory with
Code:
cd ../../..
Now that you've put the settings entry for Halo in, now you need to add the frameworks. Go to the second gerrit entry, [2/2] Fameworks HALO.
You'll notice on the build page that, under project, it says AOSPA/android_frameworks_base. This means you have to go to the frameworks/base folder.
Code:
cd frameworks/base
Again, go to the download tab and copy the cherry-pick
Code:
git fetch https://gerrit.paranoidandroid.co/AOSPA/android_frameworks_base refs/changes/44/244/21 && git cherry-pick FETCH_HEAD
Press enter, and it'll try to merge. Chances are, this is where it doesn't work. The terminal output will tell you if it didn't work. If it didn't work, enter this command to check the problem:
Code:
git status
The terminal will then output all the changes to files this cherry pick consists of. In green are the files that work, and in red are the problem files. Here is the trickiest part.
Usually, for the frameworks cherry pick, my "git status" output tells me the problem is in packages/SystemUI/res/values/pa_strings.xml. So, in terminal:
Code:
gedit packages/SystemUI/res/values/pa_strings.xml
This will open up the file in question in a text editor. Now, on the gerrit entry for the Halo frameworks, there's a list of changed files. Click on the entry for pa_strings.xml (it's toward the bottom) (or here's a link). It'll show you the difference in the base file and the file needed for Halo frameworks. Everything in green is added, and everything in red is removed. So check this against your file, and make sure the changes are done. Frequently when you run into cherry picking errors, all you need to do is remove the line "<<<<< HEAD" that gets mistakenly put into the file.
Once you've edited the problem file, in this case pa_strings.xml, you need to tell your terminal you've fixed the problem. So save and exit the text editor, and type this in terminal:
Code:
git add packages/SystemUI/res/values/pa_strings.xml
Once again, check for any errors.
Code:
git status
If everything turns up green, you're good to go. Commit these changes to your build.
Code:
git commit
Now, go back to the base of your build in terminal.
Code:
cd ../..
From here, you just have to build to see if it works.
Code:
./rom-build.sh hammerhead
Wait for it to do its thing. If it compiles and tells you where the output file is, congratulations! You have a build with halo! If not, look at the output and do your best to fix the error that stopped it from building.
Then, at the end of the day, when you want to get rid of whatever cherry picking you've done, sync with the PA source code and it'll wipe out all cherry picks.
Code:
repo sync
This reverts it to a clean build, using the latest code from PA and all the commits from the "merged" section of the gerrit.

My build failed with 20 errors lol. I'm going to repo sync and try again using only HALO
Device: Nexus 5 16GB Black
ROM: PABETA3 (ZacksBuild) w/ Franco r32

jabza is a great guy,maybe the best one i have meet here.
Thanks for your help pal.

micr0g said:
jabza is a great guy,maybe the best one i have meet here.
Thanks for your help pal.
Click to expand...
Click to collapse
+1 bro. Be is good!! He has helped me out a lot!!!
Sent from my Nexus5™. On PA™.
" Nothing's ever locked..."

@jabza, sorry but I am trying to add to my PA whitout success...are there new tricks to do??

Crostantin said:
@jabza, sorry but I am trying to add to my PA whitout success...are there new tricks to do??
Click to expand...
Click to collapse
Well it depends. What are the errors you're getting?
Sent from my Nexus 5

jabza said:
Well it depends. What are the errors you're getting?
Sent from my Nexus 5
Click to expand...
Click to collapse
@jabza
target R.java/Manifest.java: SystemUI (/home/crostantin/AOSPA/out/target/common/obj/APPS/SystemUI_intermediates/src/R.stamp)
frameworks/base/packages/SystemUI/res/values/pa_strings.xml:74: error: Error parsing XML: not well-formed (invalid token)
frameworks/base/packages/SystemUI/res/layout/status_bar_expanded_header.xml:91: error: Error: No resource found that matches the given name (at 'contentDescription' with value '@string/accessibility_halo').
make: *** [/home/crostantin/AOSPA/out/target/common/obj/APPS/SystemUI_intermediates/src/R.stamp] Errore 1

Crostantin said:
@jabza
target R.java/Manifest.java: SystemUI (/home/crostantin/AOSPA/out/target/common/obj/APPS/SystemUI_intermediates/src/R.stamp)
frameworks/base/packages/SystemUI/res/values/pa_strings.xml:74: error: Error parsing XML: not well-formed (invalid token)
frameworks/base/packages/SystemUI/res/layout/status_bar_expanded_header.xml:91: error: Error: No resource found that matches the given name (at 'contentDescription' with value '@string/accessibility_halo').
make: *** [/home/crostantin/AOSPA/out/target/common/obj/APPS/SystemUI_intermediates/src/R.stamp] Errore 1
Click to expand...
Click to collapse
That doesn't look too hard to fix. Edit frameworks/base/packages/SystemUI/res/values/pa_strings.xml
The terminal says there's an error at line 74 of pa_strings.xml, so I'd start there. Chances are it's something as simple as a missing "/ >". If you can't figure it out just by looking at it, you can check it with the pa_strings.xml listed under the android_frameworks_base gerrit entry and see what's different.
Edit: Also, the error you're getting about status_bar_expanded_header.xml is because of an error in the pa_strings.xml, so you don't have to worry about that.
Sent from my Nexus 5

jabza said:
That doesn't look too hard to fix. Edit frameworks/base/packages/SystemUI/res/values/pa_strings.xml
The terminal says there's an error at line 74 of pa_strings.xml, so I'd start there. Chances are it's something as simple as a missing "/ >". If you can't figure it out just by looking at it, you can check it with the pa_strings.xml listed under the android_frameworks_base gerrit entry and see what's different.
Edit: Also, the error you're getting about status_bar_expanded_header.xml is because of an error in the pa_strings.xml, so you don't have to worry about that.
Sent from my Nexus 5
Click to expand...
Click to collapse
did it...everything fine...
Thx
Inviato dal mio Nexus 4 utilizzando Tapatalk

thanks a million for the tips, jabza.
along with gedit, i use diffuse to compare files when merging:
http://sourceforge.net/projects/diffuse/files/diffuse/
it highlights differences between files, which makes merging and resolving conflicts a bit easier.

fzr-r4 said:
thanks a million for the tips, jabza.
along with gedit, i use diffuse to compare files when merging:
http://sourceforge.net/projects/diffuse/files/diffuse/
it highlights differences between files, which makes merging and resolving conflicts a bit easier.
Click to expand...
Click to collapse
I think Ubuntu and some other major Linux distros come with diff, which does the same thing and it's what I use. Its a little harder to use, though, as it outputs the differences in the terminal rather than a GUI.
But that's a good tip, I might have to take a look.
Sent from my Nexus 5

oops, nevermind!

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

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?

Building RR for Mata

I'm hoping to make my own builds (that I can share) of RR for the essential phone. So far I've followed the official guide found in the readme here: https://github.com/ResurrectionRemix/platform_manifest
However, when I get to the point where I'm ready to build for mata, I'm not sure what to do. I took the local_manifests.xml file from here: https://gist.github.com/invisiblek/5ee546a7129c524c3d7432b15b78aa37
I know there must be additional steps that I'm missing or doing wrong, any help is appreciated! I've tried following both threads from @Ashwin Prabhunerurkar and @invisiblek - if you guys have any advice, let me know thanks!
I'm right now stuck on an error that says and am not sure what I need to do first or change:
[email protected]:~/RR$ brunch rr_mata-userdebug
build/core/product_config.mk:238: *** Can not locate config makefile for product "rr_mata". Stop.
Device mata not found. Attempting to retrieve device repository from ResurrectionRemix-Devices Github (http://github.com/ResurrectionRemix-Devices).
Repository for mata not found in the ResurrectionRemix-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/roomservice.xml
build/core/product_config.mk:238: *** Can not locate config makefile for product "rr_mata". Stop.
build/core/product_config.mk:238: *** Can not locate config makefile for product "rr_mata". Stop.
** Don't have a product spec for: 'rr_mata'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'

Mata is not offical supported by RR.
I have tried to compile as you did and failed.
To slove your problem,you need to
cd ./device/essential/mata
mv ./lineage.mk ./rr.mk
Then edit ./rr.mk, search for PRODUCT_NAME := lineage_mata , replace with PRODUCT_NAME := rr_mata
Then, run brunch rr_mata-userdebug