yashsingh1/xdaforums huggingface dataset:
[Android] MZO:
Get it to 120GB and you're good then. No need to wipe old stuff you can carryitforward
[Android] Magoratogha:
I'm trying to build AOSPA for the LG G3 D855, but in the compilation process I got the following error:

Ninja: error: 'out/target/product/d855/ramdisk-recovery.img', needed by 'out/target/product/d855/recovery.img', missing and no known rule to make it

I searched everywhere, but I do not know how to solve it. A little help please ?

---------- Post added at 11:27 PM ---------- Previous post was at 11:20 PM ----------

Recently, I just synchronized the AOSPA sources, weighing around 31 GB. After decompressing and synchronizing the working tree, it occupies around 70 GB
[Android] neonkat:
check if you have packages/resources/devicesettings.

if not,then sync from los.(android_packages_resources_devicesettings:branch cm-14.1)
[Android] DiamondJohn:
I found I was missing the path "~/android/RR/packages/resources" a little after I posted the above :o , so I copied it across from LineageOS and have kicked off another build. I'll let you know how it works out.:fingers-crossed: big thanks!
[Android] Dersaun:
Can someneone plase help me?

I can't flash my build, I'm having error.

"update process ended with error 7".

E:Unable to mount '/system'

Failed Every Time
[Android] neonkat:
if you have twrp,flash the rom once,after you get error,in twrp go to advanced->copy log to sd(similar name).upload you recovery.log file(probably in internal sd card).
[Android] DiamondJohn:
So it now builds!:highfive:

And flashes!:D

But.. does not boot:crying::crying::crying: It doesn't even get to the bootanimation, just sits on the bootloader bootimage or bootloops from there:(

I tried plugging into a USB port to try and get a catlog, but it doesn't recognize it in adb. But during a boot loop I do rarely get a recognised device, but it isnt authorrised. So I cant do anything.Would the logs while in TWRP (after the bad boot) have anything worth getting?

The "dodgy" thing i did to get it to build was simply copy the device & vendor & stuff (as above) from the LineageOS 14.1 branch I also build from (successfully). Would that make any issue? my Lineage branch had a repo sync on it before I started all the copies. NB: The blue one was the one I missed and added in the previous posts
[Android] Dersaun:
Hi, Here is my recovery.log, can you help me? Thanks!
[Android] sai2698:
I know how to write manifest files. What i am unclear is I put a name 'RR' for the project and sync the repo in that folder and I clone the source code of ressurection ROM .here is the doubt!! Where should I place device tree ,vendor tree,and kernel source .as I making ROM for redmi note 4 which has device code name mido. So I put kernel source in RR/kernel/xiaomi/mido and device tree in RR/device /xiaomi/mido and vendor tree in RR/vendor/xiaomi/

.....Is it right? And how can we know where to place them exactly ..I think what I getting error is I unable to fetch vendor source something like that.

I saw in some tutorials that we need to edit manifest according to the project folder name that is 'RR:(' . is it true?? And finally when we take source code what we have to change to make that android version run on our device i.e is it required to change anything in the source code. As I am a beginner these r the doubts that r coming in my mind .I saw many articles but I am ending up in errors that it unable to access vendor.mk something. please help me to make any changes in location of vendor files rather than editing in local manifest.:(

---------- Post added at 08:14 PM ---------- Previous post was at 08:05 PM ----------

hhello sir

As i am also trying to make RR rom .do you make any chnages in source code of RR like local manifest or something else..please tell it may help me .......:(
[Android] pvineeth97:
Hi! :)

We built Resurrection Remix successfully for LG K10!

We fixed almost all bugs... except Double Tap 2 Wake and battery.

I locked my phone, screen went black (as usual)... I took uevent of the tap so I could test if screen turns on... but it doesn't!

Here is the uevent: https://pastebin.com/ddVfSBRB

We are trying to solve this bug from almost a day...

Here is our kernel: https://github.com/LG-K10/android_kernel_lge_msm8916

Here is our touchscreen drivers: https://github.com/LG-K10/android_kernel_lge_msm8916/tree/cm-14.1/drivers/input/touchscreen

Here is our LPWG: https://github.com/LG-K10/android_k...hscreen/unified_driver_4/lgtp_common_driver.c

[MENTION=6304619]MZO[/MENTION] [MENTION=7237874]NepoRood[/MENTION]
[Android] MZO:
Yes you have to make a local manifest, and put your device trees there
[Android] Akhilesh S V:
TWRP version ?
[Android] Archerous:
Building RR on bacon with Sultan patches

Hi :)

Im building RR on Bacon,with Sultan patches.My last functional build was on 14.7.17.But now,the rom is building fine no problem so far.Flashing the Rom,all ok

But not booting anymore,stucks on bootloader Screen :(.All builds after 16.7.17.I dont know why.My Build Host is Archlinux
[Android] DiamondJohn:
I have a secondary device (Nexus 5 - hammerhead) which is an official build target of RR. I first tested making a build from their git a few days ago, and just tried flashing the resultant ROM zip. It too failed to boot. There may be something not quite good across their source right now. I haven't checked for any chatter on their other specific social media channels (I think they use g+)

It also provides some comfort as my unsupported device (xt897) ROM I build also fails to boot. The hammerhead build was an acid test to see if I could build a RR ROM, and I cant. I can build a working LOS 14.1 last time I tried.

---------- Post added at 06:17 PM ---------- Previous post was at 06:09 PM ----------

I am no expert rom-builder by any stretch of the word, however, my understand of editing the local manifest is the correct mechanism to get a copy of the source code down from GIT into the correct folders. To short-cut this step, since I have a copy of the device & vendor trees etc for LOS 14.1, I have simply performed a file copy for now from LOS to RR. This step has enabled me to successfully run a build. I have pre-syched all the folders, so I do not need to do a repo-synch at this stage (which editing the manifest would enable/automate) These steps were just a quick and dirty method to see if it was all possible before I committed to editing the manifests for something that didn't work, and also add another point for failure on my part.

Doing the copy of device/vendor etc is based on the fact that I am building for an official LOS device, that is not an RR officially supported device, so the trees are there in LOS, and it appears RR can use those trees.
[Android] MZO:
Yes RR can use those, you're totally correct up to this point. Now you need to change cm to rr in your devoce tree because you're nuilding RR, so for the ROM to recognize your source you need to do that. And call the correct makefile from vendor/rr/ and you're ready to build then.
[Android] DiamondJohn:
If I am not mistaken, the mk files in the device tree will branch off to the correct LOS vendor trees, and that appears to be what has happened. I simply copied the device and vendor stuff directly over from lineageos, and it built (once I got allllllll the dependencies). The device tree entry point seems compatible with RR and I also checked it against a supported device tree also (and it looked compatible)

I also found a file in LOS (not in RR, which appears to specify the device & vendor specific requirements for my device) in "~/android/linege/lineage/updater/device_deps.json" it lists

"xt897": [
"android_device_motorola_msm8960_jbbl-common",
"android_device_motorola_qcom-common",
"android_device_motorola_xt897",
"android_device_qcom_common",
[COLOR="Red"]	"android_external_sony_boringssl-compat",
"android_external_stlport",[/COLOR]
"android_kernel_motorola_msm8960-common",
"android_packages_resources_devicesettings"

The two lines in red were new to me, so I included (ie copied them over) and right now I am looking at a booted RR build :highfive: But its in some strange set-up I have not seen before :silly:. I might try not flashing gapps before my first boot. Funny thing is that my unsupported device boots :good:, but my build of a supported device fails to boot.:confused:

---edit

actually just realised I did not correct the touch screen drivers for my device so its simply has an inverted touch which was confusing me. a simple flash of a single file should correct that.
[Android] Dersaun:
My version is 3.1.1
[Android] heisenberg33:
can someone help :confused::confused:

https://hastebin.com/ewovajiwaj.go
[Android] MZO:
ROM's build is broken. Illegal letters in Python script which can't be converted are there. Replace them
[Android] nithin chandra:
yeah thanks...:good: but previous i cloned n7x branch instead of n7x-caf for du... & cloned ril-caf from halogen this time the build successfully compiled
[Android] nithin chandra:
new error while compiling omni https://hastebin.com/dafiveyiho.tex
[Android] MZO:
Put the full link for gralloc_priv.h in the include
[Android] neonkat:
make sure you got caf hals(display,media,audio).
[Android] XTutorials:
Developing Team (off-topic)

(OFF-TOPIC)

Hi. I want to make a developing team for faster development for some devices and I want some members

Requirements:

-Decent computer

-At least some android development and linux terminal knowledge

-(optional) (prefferably) an Huawei device with Kirin platform

If you want to get into the team send me a PM for more info.

Thank You.

P.S.- Sorry for off-topic
[Android] Dersaun:
can someone help me?
[Android] DiamondJohn:
Is ANYONE successfully building even a supported device of ResurrectionRemix Nougat ROM? Even when I build for hammerhead (ie Nexus 5, which is officially supported) I don't get a bootable ROM.:crying:
[Android] nithin chandra:
im unable to get your word :( can you say clearly
[Android] MZO:
You are probably missing some dependencies, vendor is included?
[Android] MZO:
It should be in vendor/resurrection, no they should be equally stable. If it is unstable then it means you're missing something
[Android] XTutorials:
I am trying to make my own device source code with AOKP source but when I run the command:

andrei@Andrei-HP-EliteBook:~/aokp/system$ ./build/tools/device/mkvendor.sh huawei hi6210sft ~/Desktop/stock/recovery.img

Arguments: huawei hi6210sft /home/andrei/Desktop/stock/recovery.img

unpackbootimg not found. Is your android build environment set up and have the host tools been built?

andrei@Andrei-HP-EliteBook:~/aokp/system$

I ran make -j4 otatools 3 times already and just gives me ninja errors, if I disable ninja gives me this:

make: *** No rule to make target 'otatools'. Stop.

Can someone help me?

Thank you.
[Android] DiamondJohn:
I was also expecting a vendor/resurrection but it didnt appear. I do note that the vendor/cm are very different. I tried seaching through the manifests to see if there was some mapping of vendor_resurrection, but didnt find any references. I have no idea how it got downloaded.

Ignoring the hammerhead issue, I did a comparison between lineageos and RR local manifests and found there was an extra line in the local manifest

<project name="LineageOS/android_device_motorola_msm8960-common" path="device/motorola/msm8960-common" remote="github" />

I think thats device specific details for a KitKat bootloader (mine is JBBL). But I wouldn't expect it to branch off into that directory as part of the build anyway. I have no idea how that snuck in :confused: I mean really no idea where I picked up that line from.edit. that was supposed to be there

I hope the next build is good :fingers-crossed:
[Android] MZO:
Since everything is so broken, I'd recommend you to start from 0 again, clean sync
[Android] DiamondJohn:
I do a full sync with "repo sync -j1 -fc --force-sync --force-broken" before every build, especially since it was a "Friday", which is when it appears a lot of official builds get built and released also.

I built a crDroid Nougat for my device, that built, flashed and booted, and seemed pretty good (ie no systemUI crashes):victory:, until I flashed GApps. Then it became a storm of crashes in systemUI, NFC and everything else.:silly:

I also rebuilt RR, and that also ran pretty good, until I flashed GApps.

I think I will release an "EXPERIMENTAL" build for others to try and hopefully it may catch the attention of one of the device specific maintainers on LineageOS 14.1

I am pretty surprised how far I have gotten thus far.:eek:
[Android] nicesoni_ash:
That's vendor/cm. Check rr-n.xml file in manifest/snippet folder.

Sent from my "1+2" powered by Unofficial RR 7.x.x

Compiled by myself
[Android] DiamondJohn:
Yep, that appears tro show that android_vendor_resurrection goes to vendor/cm

<project path="vendor/cm" name="android_vendor_resurrection" remote="rr" />

My last build using a local manifest is now more stable than the dodgy copy method I used. But still not usable after flashing GApps.
[Android] NepoRood:
Try a different GApps package, which are you using now?

Lots of people like Beans GApps
[Android] dom133:
I sucessfull compile LOS but i have battery bug. Battery is always 100% and charging. Anybody can help? Logcat: http://pastebin.pl/view/raw/7fd3b6a8 Dmesg: https://hastebin.com/oxapojirun.md
[Android] DiamondJohn:
I have been messing with the local_manifest to remove whole projects (eg debloat) my ROM,but now I need to only delete a subfloder within a project. Is this possibl;e with the manifest? I tried

<remove-project name="LineageOS/android_device_motorola_xt897" path="device/motorola/xt897/AsantiKeypad"

it seemed logical, but that failed ie specify a path within a specific project to exclude. Is there a way to do it using the manifest?
[Android] :
Hello Brothers @NepoRood & [MENTION=6304619]MZO[/MENTION]

Can anyone guide me why this problem is coming, even the file it has mentioned is there.

Here's the log and screenshot is attached in the post for reference. https://hastebin.com/owahimewem.sql.

Regards

Bond
[Android] NepoRood:
Just remove the project from your device repo, or remove the call to include from device.mk (or wherever it may be hiding) under "PRODUCT_PACKAGES +=" or "PRODUCT_COPY_FILES +=". AFAIK, you can't use the manifest for subfolders, it's the whole project or none.

---------- Post added at 06:15 AM ---------- Previous post was at 06:14 AM ----------

Again, it can't seem to find your defconfig :confused:
[Android] MZO:
Revert the mismerged qcacld-2.0 from kernel, I had the same thing yesterday.

Alternatively you can define the variable

TARGET_KERNEL_VERSION=<kernel version like 3.10> brunch oneplus3
[Android] :
Brother,

Its already there. You can check the screenshot attached in the post.

Brother,

Can you please elaborate or guide me in doing this.

Regards

Bond
[Android] MZO:
It's quite simple and just like how I wrote before. Go to your kernel dir, find the qcacld merge by git log command, and git revert the commit with its sha#. That'll fix your problem most probably.
[Android] tcpcd:
i cant find device/vendor tree anywhere. can i extract from stock rom? i have rooted mobile
[Android] :
Brother,

You're a pro in all these but honestly I am not. I tried changing Kernel Version as you said from 3.18 to 3.16 but that also didn't worked.

Don't know but this is happening in all ROM based on CAF or AOSP.

Regards

Bond
[Android] DiamondJohn:
It uses a "build all subs", so simply doing a physical delete of the folder gets it done. Was hoping the local manifest could do the delete for me. Thanks for confirming.
[Android] anhenrique:
Now i get this https://hastebin.com/apopiqawex.rb
[Android] MZO:
Log isn't enough
[Android] anhenrique:
https://hastebin.com/edudumetoj.coffeescript
[Android] MZO:
cm/platform/sdk/sdk/src/java/cyanogenmod/app/IProfileManager.aidl:21: couldn't find import for class android.app.NotificationGroup
[Android] unknown:
I have 6.0 source and i want to build 7.1 for my device

Anyway to do it ? :confused::confused:

Will this guide work ?

---------- Post added at 06:24 AM ---------- Previous post was at 05:31 AM ----------

https://pastebin.com/fK9vRw5A

Can someone check this ? :confused:
[Android] DiamondJohn:
sooooo close!

I am coming out of my skin here!

I have built a ResurrectionRemix 7.1.2 ROM for an XT897 :good:, which is not an official device for RR but is an official device for LineageOS 14.1. So I simply used the device tree from LOS against RR. Basically it built, flashed and booted :highfive: It appears to be smooth and great with all the eye candy/features in RR. HOWEVER as soon as I flash GApps, it all goes south in a big way. Multiple apps start force closing uncontrollably and in quick succession making the ROM unusable (the errors are constant).

A couple of the errors look like the following, with more logcat at https://www.hastebin.com/otuzivaguj.sql its MB's in a few seconds.

07-25 22:46:44.977 3212 3212 D AndroidRuntime: Shutting down VM
07-25 22:46:44.978 3212 3212 E AndroidRuntime: FATAL EXCEPTION: main
07-25 22:46:44.978 3212 3212 E AndroidRuntime: Process: com.android.nfc, PID: 3212
07-25 22:46:44.978 3212 3212 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/support/v4/content/FileProvider$PathStrategy;
07-25 22:46:44.978 3212 3212 E AndroidRuntime:	at android.support.v4.content.FileProvider.getPathStrategy(FileProvider.java:554)

It is SOOOOO frustrating that this seams so close, and yet so far away. Anyone have any ideas? I have tried both Open GApps Pico and also Full Open GApps and also beans, all with the same result/behaviour. A lot of the errors were sourced from NFC, so I tried removing it in TWRP and others just took its place.

Anyone please?:crying::crying::crying:
[Android] NepoRood:
Just curious, did you try flashing GApps at the same time as the ROM?
[Android] DiamondJohn:
From memory, thats what I did the first time as a standard flashing install. I only tried the ROM only method to see how it went. I also tried wiping cache/dalvick and rebooting, to no change. And also Pico, Full and beans GApps.

The slightly confusing thing is that i can successfully build LineageOS 14.1 and RR is based off of that. why it goes so horribly wrong is confusing.:confused:
[Android] aoleary:
Hi.

I was having a bug in DirtyUnicorns that no-one else was having so I decided to completely start from afresh, so I deleted my entire DU folder, recreated it and did a fresh repo sync

However, now, when I build, I get this error:

ninja: error: '/home/antoin/DU/out/target/product/d855/obj/SHARED_LIBRARIES/libmdmdetect_intermediates/export_includes', needed by '/home/antoin/DU/out/target/product/d855/obj/SHARED_LIBRARIES/gps.msm8974_intermediates/import_includes', missing and no known rule to make it

I verified that I have "hardware/qcom/gps" and within that I have "msm8974"

Any ideas?

When I browse the file structure, I only have as far as /home/antoin/DU/out/target/product/d855/

I tried creating the rest of the directory structure required, but it still bombs out with the same error..

Full error log

here

.
[Android] DiamondJohn:
In case anyone was wondering, in short, i'm doing the same with crDroid, I flashed it again, took a heap of logs, scanned over them, found that a lot of references were to "CMParts", checked the repo sources for crDroid, found they had their own version (ie not using Lineage), compared the two and found that Lineage seemed possibly a little "ahead", so edited the local manifest to switch back to Lineage for CMParts, rebuilt and flashed it, and it was a LOT better. even allowing me to flash gApps; even allowed logging on and using the playstore. Who'da thunk the logs would be so helpful...;) It still crashes:p, but a lot less now.:D

for ref, the chage to local_manifes/roomservice.xml was

<remove-project name="crdroidandroid/android_packages_apps_CMParts" remote="crdroid"/>
<project path="packages/apps/CMParts" name="LineageOS/android_packages_apps_CMParts" remote="github"/>

I know its a hack and should do a manual merge if anything, but I would of thought since they build numerous devices it would of just worked as is :confused:
[Android] utkarshp64:
Compiling slim rom 7.1.2 for Sony Xperia M (nicki) got above error...

Please help!

INSTALL drivers/crypto/msm/qce40.ko
INSTALL drivers/char/adsprpc.ko
INSTALL drivers/crypto/msm/qcrypto.ko
INSTALL drivers/crypto/msm/qcedev.ko
INSTALL drivers/gud/mckernelapi.ko
INSTALL drivers/gud/mcdrvmodule.ko
INSTALL drivers/media/video/gspca/gspca_main.ko
INSTALL drivers/misc/eeprom/eeprom_93cx6.ko
INSTALL drivers/net/ethernet/micrel/ks8851.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL drivers/spi/spidev.ko
INSTALL drivers/staging/prima/wlan.ko
DEPMOD 3.4.0-nicki+
make: Leaving directory '/home/utkarshp64/slimRom_nicki/kernel/sony/msm8x27'
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
/bin/bash: arm-linux-androidkernel-strip: command not found
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/utkarshp64/slimRom_nicki'
[Android] pvineeth97:
We are tried to compile the ROM with keymaster. We compiled it successfully but the ROM just gets stuck on the LOS boot logo.

Here is the log: https://ufile.io/4gs60

Device Tree: https://github.com/LG-K10
[Android] NepoRood:
That doesn't show an error, scroll up and look for "Failed:" Also, don't post logs here, upload somewhere (pastebin, hastebin, github, etc) and give us a link...

---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------

I don't see anyone trying to actually "download" your error, please use a pasting service (see above) :good:
[Android] pvineeth97:
Actually, we have two models in K10 that is K420DS and K420N. Both have same SoC and almost same specs. We applied the fix for keymaster bug in the newest build of LOS and RR. It worked in K420N but on K420DS we get this error:

Our repo: https://github.com/LG-K10

01-10 07:43:23.378 11663 11663 D QCOMKeyMaster: keymaster app is loaded
01-10 07:43:23.378 11663 11663 D QCOMKeyMaster: keymaster app got loaded at attempt number 0
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : App is not loaded in QSEE
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Loading image failed with ret = -1
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : App is not loaded in QSEE
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Loading image failed with ret = -1
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-10 07:43:23.378 11663 11663 D QSEECOMAPI: : App is not loaded in QSEE
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/skeymast.mdt
01-10 07:43:23.378 11663 11663 E QSEECOMAPI: : Error::Loading image failed with ret = -1
01-10 07:43:23.378 11663 11663 E QCOMKeyMaster: Loading keymaster app failed