yashsingh1/xdaforums huggingface dataset:
[Android] nicesoni_ash:
I was worried about that thing when putting up that screenshot. :)

Actually build first failed coz my root drive got almost full so I had to cancel that in between and increased my root partition some more. Since most of the work was already done, it used already built files and it finished this early. I'll clean build next time though. I had to use a different drive on same disk, was getting I/O errors using a different disk. Only 4gb RAM so almost took 6 hours even after 50gb ccache and 10gb swap file. I just have to get my other 4gb RAM replaced but too lazy to visit the service center.

After testing the build, it mostly worked except some issues. I am getting Unknown in device model. Double tap to wake doesn't work (this existed in official release too so I am confused whether this is the rom's fault or not) and last, notification slider doesn't work at all.

So I have to fix up these issues before calling it a complete success. :)
[Android] juancarlos5:
This is my error

I use Open JDK 7 & 8 with the same result. I have done multiple tests with build, vendor, device & kernel of CM without optimizations,

And not use more tests, I tried adding flags -Wno-error=strict-aliasing -fno-strict-overflow -fno-strict-aliasin -Wno-strict-aliasing with the same error.

Now I test ubuntu 16.04

Could someone give me a hand when I'm doing wrong?

Thanks in advance

PD: Forgive my poor English, I'm not very good and use a translator to communicate better.
[Android] nicesoni_ash:
Could be an issue of low root space. Check that out. And next time hide ur code or paste on pastebin or something.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] SlimShady's:
I have 300GBs free.

I already hided it. XDA Labs doesn't show hide code yet. ^^
[Android] surajsj:
Is this method only for cyanogen mod ROMs
[Android] neonkat:
every open source rom.
[Android] nicesoni_ash:
If I use my 64gb 3.0 pen drive for output folder rather than using my sata hdd, will it make any improvements in building or worse coz I don't have any SDD?

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] Startrek852:
It will be vastly worse.
[Android] Xendrix:
what do i do if my phone only goes up to kitkat but i want build a lollipop rom for it???

we have cm 12.1 but its not good enough for daily use....wifi causes reboots, mobile data does not work, also causes a reboot but can still call/text no problem. and camera does not work

-Desire 510
[Android] mazhdini:
Was having trouble with the Ubuntu version asked from the thread with installing the JDK, however no issues at all in Ubuntu 14.04. If possible can the thread be updated to use this version as it would need minimal tweaks.

Edit: Could not install JDK due to repository problems that arose with Ubuntu 13.10
[Android] ABSathe:
Can we build Android nougat on Ubuntu 15.04 ? Or Do we need 16.04?

And what about jdk version for Nougat ?.. 1.7/1.8?

Thanks in advance
[Android] nicesoni_ash:
Instead of suggesting a specific Ubuntu version, it's best to mention how to install openjdk7.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] mazhdini:
You can build Android Nougat on minimum Ubuntu 14.04 as long as you have JDK 8 installed. For more information go to this website .. Requirements | Android.
[Android] arnabJ:
Hi guys, I am trying to build AOSP 7.0 for Moto Play. But I am stuck due to several errors. 1 of them is : Gist.Github.com .

So, I tried a fix stated in this post and it worked but according to the post it's a workaround if I don't have kernel source but I do have. So it means that there's some issue with it?

Now I get a new error : Gist.Github.com
[Android] josip-k:
i am getting the same error. but the funny thing is i'm building it for LG Nexus 5x.
[Android] ABSathe:
I was having some problems with my moto e.. I set kernel to permissive and it worked .. try it
[Android] arnabJ:
Your screenshot doesn't seems to be same as mine. But may be I skipped.

How to do this? I have Cyanogenmod Kernel Source for my device.
[Android] spookcity138:
Assuming all of the commits are there for SELinux to work its as simple as finding the selinux=disabled or =enforcing line in the config file and changing it to selinux=permissive.
[Android] nicesoni_ash:
I compiled my rom with UberTC 4.9. Since for architecture 64, same toolchain will work for Kernel and Rom, I built it with UberTc 4.9. Rom built successfully but didn't boot and bootlooped to oneplus sign so I flashed a custom kernel and that booted it up. So I am guessing Kernel didn't get build through UberTc toolchain. Any suggestions? I didn't have any kind of errors related to toolchain etc. I am using Seraph08 op2 kernel tree for my source kernel, that built fine with default toolchain.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] arnabJ:
Which config file will have this data?
[Android] spookcity138:
kernel source/arch/arm/configs...then which ever config file you're using to build the kernel.
[Android] arnabJ:
There's no such line as selinux=disabled/enforcing or permissive (checked just in case).
[Android] spookcity138:
Hmm,very strange. I don't know. I've built a few CM13 kernels and they've all had that. Did you search the file for selinux? If so and nothing then I'm sorry,but I have no other ideas. Hopefully someone else will be more helpful.
[Android] arnabJ:
There are 9 occurances of selinux :

CONFIG_SECURITY_SELINUX=y
# CONFIG_SECURITY_SELINUX_BOOTPARAM is not set
# CONFIG_SECURITY_SELINUX_DISABLE is not set
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
CONFIG_DEFAULT_SECURITY="selinux"
[Android] hackslash:
There is no need to disable SELinux completely. Just set it to enforcing.

Uncomment the CONFIG_SECURITY_SELINUX_BOOTPARAM is not set line and replace is not set with =y. Then in your boot image, add this flag in the boot command line: androidboot.selinux=permissive (modify if already present, most probably will be set to enforcing).

The good thing about enforcing is that the logcat will show you AVC_DENIED errors which are basically SELinux denials which you would get if SELinux is set to permissive. In enforcing these denials are ignored but they are logged for debugging purposes. Disabling SELinux completely is not recommended.
[Android] arnabJ:
Boot image will be created when build is complete inside the rom zip right? Or are you saying to use pre-built boot image?

----

Still same :

Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/product/lux/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by 'out/target/product/lux/obj/EXECUTABLES/vold_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
[Android] hackslash:
I'm sorry. I should have been more clear.

In your device tree open the BoardConfig.mk and add androidboot.selinux=permissive flag in BOARD_KERNEL_CMDLINE.
[Android] arnabJ:
Check my previous post again.

Also is this correct :

BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M androidboot.bootdevice=7824900.sdhci utags.blkdev=/dev/block/bootdevice/by-name/utags utags.backup=/dev/block/bootdevice/by-name/utagsBackup movablecore=160M androidboot.selinux=permissive
[Android] adityaupreti:
any idea building Nougat 7.0 for grand 2 ms013g

[ 28% 9758/34376] build /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates/sepolicy
FAILED: /bin/bash -c "(/home/adityaupreti/n/out/host/linux-x86/bin/checkpolicy -M -c 30 -o /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy _intermediates/sepolicy.tmp /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates/policy.conf ) && (/home/adityaupreti/n/out/host/ linux-x86/bin/checkpolicy -M -c 30 -o /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit /home/adityaupreti /n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates/policy.conf.dontaudit ) && (/home/adityaupreti/n/out/host/linux-x86/bin/sepolicy-analyze /home /adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates/sepolicy.tmp permissive > /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/ sepolicy_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolic y_intermediates/sepolicy.permissivedomains ]; then echo \"==========\" 1>&2; echo \"ERROR: permissive domains not allowed in us er builds\" 1>&2; echo \"List of invalid domains:\" 1>&2; cat /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolic y_intermediates/sepolicy.permissivedomains 1>&2; exit 1; fi ) && (mv /home/adityaupreti/n/out/target/product/ms013g/obj/ETC /sepolicy_intermediates/sepolicy.tmp /home/adityaupreti/n/out/target/product/ms013g/obj/ETC/sepolicy_intermediates/sepolicy )"
device/samsung/msm8226-common/sepolicy/mm-qcamerad.te:2:ERROR 'unknown type mm-qcamerad' at token ';' on line 20361:
#line 1 "device/samsung/msm8226-common/sepolicy/mm-qcamerad.te"
allow mm-qcamerad media_rw_data_file:dir search;
checkpolicy: error(s) encountered while parsing configuration

Edit: Fixed
[Android] arnabJ:
I have created a gist @ gist.github.com containg different errors I am facing and the sollution I applied to each until I reached to another error.

Hope someone can help me fix the issues. As the solution I used is in no way the correct way to fix the issues.

gist.github.com
[Android] Swp1996:
Yes Anyone Could Help ....Thankss
[Android] adityaupreti:
i fixed by my own ;)
[Android] Swp1996:
Ohhh great Any Help or testing im there bro
[Android] MSF Jarvis:
Then maybe post the fix as well
[Android] nicesoni_ash:
That should supposed to be the default response.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] MSF Jarvis:
Though people who know the stuff know the fix was deleting the line from the sepolicy specified in the error ;)
[Android] nicesoni_ash:
Wow, that's just great.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Android] Xendrix:
if wifi and mobile data cause random reboots...and reboots from switching it off/on would that be a kernel issue or driver compatibility?
[Android] nitin.chobhe:
Any idea about this error: http://www.hastebin.com/putufuguvu.js

Trying to build LiquidDark (aosp) ROM with CM device trees. Did this successfully for LG G3 and G4.

But getting above error for Samsung galaxy S5 (klte)

Nitin
[Android] ratvim:
Can i use cynogenmod cm13 device tree to built aosp 7 rom?
[Android] arnabJ:
Getting clang++ error while trying to build AOSP 7.0, full error

here

.
[Android] MSF Jarvis:
Clearer than daylight, you need to remove all cmhw references from device tree
[Android] nitin.chobhe:
Thanks! I couldn't find the references. Can you help me?

https://github.com/CyanogenMod/android_device_samsung_klte

And

https://github.com/CyanogenMod/android_device_samsung_klte-common
[Android] adityaupreti:
disable clang from device tree
[Android] arnabJ:
But won't that effect the final rom.zip?

Also can you shed some light on this error :

Starting build with ninja
ninja: Entering directory `.'
[ 0% 4/25310] build out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.sorted.tmp
FAILED: /bin/bash -c "(out/host/linux-x86/bin/checkfc -e out/target/product/lux/obj/ETC/sepolicy_intermediates/sepolicy out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.tmp ) && (out/host/linux-x86/bin/fc_sort out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.tmp out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.sorted.tmp )"
libsepol.context_from_record: type thermal-engine_exec is not defined
libsepol.context_from_record: could not create context structure
out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.tmp: line 9 has invalid context u:object_r:thermal-engine_exec:s0
Error: could not load context file from out/target/product/lux/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.tmp
[ 0% 4/25310] target thumb C++: libbinder <= frameworks/native/libs/binder/IMediaResourceMonitor.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

#### make failed to build some targets (01:08 (mm:ss)) ####
[Android] adityaupreti:
give me device tree link
[Android] arnabJ:
https://github.com/boulzordev/local_manifests/tree/caf-6.0

Lux and msm8916-common.

Btw I commented the lines which showed error in out directory. And it continued after that.
[Android] ABSathe:
Just start building with cm13 trees

You will get HELL lot of errors (at least for me :p)

Squash them one by one until your build gets compiled finally .. try flashing it so as to check booting status .. if it boots well and good .. other wise go back to device trees .. do changes and get a booting device

Simple isn't it ?:laugh:

Lol ..just kidding .. in short answer is you can use them as your basic device trees but mind that they may not conpile successfully:good:

Don't forget hiitng thanks if I helped you :good:
[Android] MSF Jarvis:
Remove BOARD_USES_CYANOGEN_HARDWARE from BoardConfig and delete the cmhw folder

This is your enemy :p

# CMHW

BOARD_HARDWARE_CLASS += $(LOCAL_PATH)/cmhw

klte-common/BoardConfigCommon.mk
[Android] Arvind7352:
Assuming this is the Source Repository for LiquidDark ROM

From their manifest, it seems that 'android_frameworks_opt_hardware' doesn't exist in the specified remote (i.e on https://github.com/TeamHorizon ) so it went missing...

So, what you can do is, sync the CMHW repo from CyanogenMod.

For a Bigger Explaination ...

Other Non-CM based ROMs maybe haven't changed the cmhw class name yet, and one of your device's repo (hardware/samsung) imports the new class name (org.cyanogenmod.internal instead of the older org.cyanogenmod.hardware - From the error you posted)

No need to remove CMHW stuff if it was necessary.
[Android] arnabJ:
Now stuck with completely new errors.

hardware/qcom/audio-caf/msm8916/policy_hal/AudioPolicyManager.cpp:496:58: error: 'mPatchHandle' is a protected member of 'android::AudioOutputDescriptor'
ssize_t index = mAudioPatches.indexOfKey(outputDesc->mPatchHandle);

gist.github.com
[Android] nitin.chobhe:
Thank you so much. Deleting the hardware/samsung/cmhw worked... Everything works on the build except it doesn't have navigation bar :(

See attached screenshot

Yes, the source link is correct. I had also came to this conclusion. But my source already had frameworks/opt/hardware

So I removed hardware/samsung/cmhw and it worked, no errors at all while building; but getting above problem.

Nitin
[Android] spookcity138:
Add "qemu.hw.mainkeys=0" to your build.prop to enable navbar.
[Android] MSF Jarvis:
[MENTION=5044214]nitin.chobhe[/MENTION] if you want to add it into the device tree this commit should give you a fair idea https://github.com/seedmtk-devs/and...mmit/1dc405b441dcfc2e034924c40dd64c2847572595
[Android] nitin.chobhe:
Thanks again; but the commit is about OTA updates. You linked to the correct commit?

Nitin
[Android] nicesoni_ash:
Certainly not. [emoji14]

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[Android] MSF Jarvis:
I was simply showing how to add entries to the build.prop lol
[Android] Qiangong2:
My twrp build keeps on halting at this: http://pastebin.com/mk3sA1Xq

I can't find out what is the problem.

kernel tree: https://github.com/Qiangong2/android_kernel_scx15_sp7715ga_FS001

device tree: https://github.com/Qiangong2/android_device_blu_scx15_sp7715ga_FS001
[Android] MSF Jarvis:
Use a prebuilt kernel if you can't read errors about missing parentheses in kernel source files
[Android] Qiangong2:
I still get the same error after fixing the parentheses. I've tried building with a prebuilt kernel already.
[Android] adityaupreti:
Any idea for this error Build AOSP-CAF 7.0 For Galaxy Grand 2

[MENTION=6552280]MSF Jarvis[/MENTION]

: Entering directory `.'
ninja: error: '/home/adityaupreti/rom/out/target/common/obj/JAVA_LIBRARIES/rcs_service_api_intermediates/classes.dex.toc', needed by '/home/adityaupreti/rom/out/target/common/obj/APPS/Mms_intermediates/classes.noshrob.jack', missing and no known rule to make it

ninja

Edit : Fixed by rm -rf packages/apps/Mms
[Android] Xendrix:
How would i build a lollipop rom for a device that stopped at kitkat 4.4
[Android] NepoRood:
Depends on the device and if you do or don't have kernel source. Some kernels won't build on LP (outdated), you'll probably have to make some tree changes, to "upgrade" to new source.

Best thing you can do is "give it a shot, with what you got" and go from there. You'll most likely get build errors, and then bootloops, followed by a heaping helping of frustration (sorry, that's just how it goes)

However, there's a lot of helpful people around here, most with tons of "Androidoligy" under their belts. So, go make bacon and see what happens :good:
[Android] MSF Jarvis:
rm -rf packages/apps/Mms will build a ROM without the messaging app. You want that?

Don't tell me you didn't `make clobber` before restarting the build
[Android] Xendrix:
Well we have a built cm 12.1, but it has wifi/mobile data errors that cause reboots alot, broken camera :/ for Desire 510

I was told it has too many errors and cant be repaired, but id like to learn and build a stable 5.1

Ill try to post where im stuck at if thats ok
[Android] adityaupreti:
Any one have any idea about this error AOSP 7.0

http://pastebin.com/raw/HruARNVb

Edit: Fixed by modifying build
[Android] arunmcops:
Error in building Nougat

Hi,

I am working on building nougat AOSP for Kenzo. Facing some errors while building. I request the users as well as devs to help in ironing out errors so that a working build may be done soon.

This is the error I am getting while building AOSP.

ninja: error: 'out/target/product/kenzo/obj/KERNEL_OBJ/usr', needed by 'out/target/product/kenzo/obj/EXECUTABLES/ipacm_intermediates/IPACM_Main.o', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

I have added few changes to CM device tree to work with AOSP . AndroidBoard.mk reads as

LOCAL_PATH := device/xiaomi/kenzo/

#
# Boot files
#
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel

file := $(INSTALLED_KERNEL_TARGET)
ALL_PREBUILT += $(file)
$(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)
$(transform-prebuilt-to-target)

And BoardConfig.mk reads as

# Kernel
TARGET_PREBUILT_KERNEL := device/xiaomi/kenzo/kernel

I am attaching .mk files so that interested devs can see and id the errors/mistake.
[Android] Albe96:
Is CM14 Available To Build?
[Android] MSF Jarvis:
It's available, but won't compile that easily
[Android] Albe96:
why?
[Android] MSF Jarvis:
https://github.com/seedmtk-devs/and...mmit/f5e1671ec57375ac8b8e0d7fc4035c9778af1955

---------- Post added at 05:23 PM ---------- Previous post was at 05:23 PM ----------

Because it's not ready :rolleyes:
[Android] Startrek852:
Technically, yes. You can initialize and sync CM 14.0, but most features aren't fully updated yet.
[Android] Albe96:
Ok.Thanks Guys
[Android] Qiangong2:
I make clean before every build after I make changes
[Android] desalesouche:
cm14.0

hi may i request some help about those errors?

http://pastebin.com/u6Tk6H3u

i think that [MENTION=6622051]Startrek852[/MENTION] is right, cm-14.0 is not ready yet.
[Android] arunmcops:
AOSP Building error

Earlier error regarding kernel solved. Thanks to MSF Jarvis. Now getting new one.

ninja: error: 'out/target/product/kenzo/obj/SHARED_LIBRARIES/libnfnetlink_intermediates/export_includes', needed by 'out/target/product/kenzo/obj/EXECUTABLES/ipacm_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

Solved by commenting out in device.mk.

# IPACM
#PRODUCT_PACKAGES += \
# IPACM_cfg.xml \
# ipacm
[Android] Albe96:
yes.he is right.its in development,wait untill cyanogenmod team finish it
[Android] arnabJ:
BUMP.

Can No One Help With These Errors?
[Android] ABSathe:
[MENTION=6552280]MSF Jarvis[/MENTION] .. you mean cm14 sources are released ?
[Android] NepoRood:
CM 14 is still "staging", you can go to Github and snag it if you want, but it's not ready yet.
[Android] MSF Jarvis:
staging/cm-14.0 branch. It's disconcerting that no one wants to do a tiny bit of browsing and see for themselves, and choose to spam the board.
[Android] YannikM:
Hi,

I tried building aosp 7.0 for the i9300, but erverytime i am getting this error.

http://pastebin.com/7ryWVnwd
[Android] MSF Jarvis:
Using a CM device tree on AOSP will always cause trouble. Remove all the CM bits and try again
[Android] ABSathe:
How do we remove cm bits from trees ?
[Android] MSF Jarvis:
Some common sense to identify it :eek::rolleyes:

Generally you want to nuke anything that says cmhw or cyanogen
[Android] manhar2108:
added pa_kenzo in vendor/pa/product/kenzo with dependencies

modified AndroidProducts.mk

and vendor.sh files

still getting the errors please help

http://hastebin.com/uqimovodiy.mel

thanks for help [MENTION=6049586]Arvind7352[/MENTION] and [MENTION=7065337]spookcity138[/MENTION]

SOLVED BY HIT AND TRAIL

now another error :/

http://hastebin.com/cisabavuqa.vhdl
[Android] spookcity138:
Can probably get away with just commenting out the offending lines in the build/tools/roomservice.py without any issues.
[Android] arunmcops:
comment out the AdvancedDisplay app causing error in mk file.
[Android] Arvind7352:
Is the .dependencies file present in vendor/pa/product/kenzo and named as pa.dependencies ?

If it is not then search your Device tree for a .dependencies file, move it to the vendor, rename it to pa.dependencies and start the build.

Else create a empty file pa.dependencies in vendor/pa/products/kenzo and start the build.
[Android] YannikM:
Thanks to all! I commited the advanced Display out and now it works.

But now i'm getting this error message:

http://pastebin.com/0curZyuM
[Android] arunmcops:
Looks like you are using Pre Build Kernel. Define the directory of zImage . Either in Kernel/Samsung/i9300 or device/Samsung/i9300-kernel

Recheck mk files in device tree for correct Kernel location.
[Android] spookcity138:
Add

”ifeq ($(TARGET_PREBUILT_KERNEL),) LOCAL_KERNEL := device/samsung/i9300-kernel/kernel else LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL) endif PRODUCT_COPY_FILES := \ $(LOCAL_KERNEL):kernel ”

To your device.mk

Prebuild the kernel and put the prebuilt in the i9300-kernel folder as my example here. Or whatever folder you'd like. Just adjust the device.mk accordingly.
[Android] ParanoidNemo:
Roomservice.py is autogenerated so changing it is useless. Comment/remove duplicates in pa.dependencies or in Your local manifest to solve the issue
[Android] spookcity138:
I have commented out lines in roomservice.py more than once with no problems. Obviously you need to understand what you're commenting out and yes,repo sync will force you to redo I suppose.

Although,I do agree with your solution in the long run being better.
[Android] tschmid:
Does anybody know what this failure is:

http://pastebin.com/wnJDmnwZ

Boot forever after this

Gesendet von meinem Nexus 6P mit Tapatalk
[Android] MSF Jarvis:
Tons of SELinux denials. Google for "Validating SELinux" and check Android Developers site for instructions how to write sepolicy rules to fix the denials.
[Android] tschmid:
Thanks, im runing this in permisive mode, do you think the denials are the reason that my rom shows the cm Bootamin forever?

Gesendet von meinem Nexus 6P mit Tapatalk
[Android] MSF Jarvis:
From the limited logs you posted, seems to be the case.