yashsingh1/xdaforums huggingface dataset:
[Android] Cristiano Lira:
I put that line in the end of the BoardConfig.mk from /device/generic/arm64. But I got another from /device/generic/armv7-a-neon and others from mini-emulator-*.

Device tree: https://github.com/AOSPA/android_device_lge_mako/

Another thing, acording to here (https://github.com/AOSPA/manifest) I should be using "marshmallow" branch for mako, correct? And if yes, how can I know it, it's just to look for a branch that the device tree have?
[Android] Startrek852:
I would put the line in mako's device tree, because then it won't affect builds for any other devices. And you can check what branch

your device tree is on by running git branch in the device tree directory.
[Android] Qiangong2:
I've been trying to build twrp for my ubifs device for a while now, and today I succeeded :) but now I can't wipe or backup any of the partitions. It recognizes the ubifs partitions, but it cannot do anything with them. How can I fix this?

Here is the recovery log: http://pastebin.com/3VxqUgj4

here is my tree: http://github.com/Qiangong2/android_device_blu_scx15_sp7715ga_FS001 branch twrp
[Android] Garv Maggu:
[MENTION=6049586]Arvind7352[/MENTION] [MENTION=6552280]MSF Jarvis[/MENTION] [MENTION=4150512]The Marionette[/MENTION]

Finally the ROM got compiled after I added the cache size but it is not booting, when I flashed it, my recovery got lost and no boot logo, not even the 'SONY' logo and boot animation didn't come. It soft-bricked, so I flashed another kernel, a recovery and installed another ROM and it booted but when I flashed DU again, it again got bricked.

Also when I did some math, the cache size was 226577664 but I wrote 246577664 as Arvind Sir said you need to increase it.

Also, when it almost finished compiling it showed this (Total 0 blocks are packed as new blocks due to insufficient cache size). Below is the screenshot :-

[IMG="Insufficient Cache Size Error"]http://s6.postimg.org/k7cgk8fbl/2_Insufficient_Cache_Size_Error.png[/IMG]

Also I uploaded the compiled ROM here, in case you need it :- https://www.androidfilehost.com/?fid=24591000424954802

So, I think I should increase the cache size and try again, but I don't know how much should I increase. Please help me with that.

BTW, thanks to all for your support. :)
[Android] MSF Jarvis:
That error is normal, almost everyone gets it. It's not even an error lol. If you're booting with enforcing SELinux, first step is to grab the dmesg and look for "avc denied" lines. Then use audit2allow to generate the fixed sepolicy rules for it
[Android] Garv Maggu:
Okay, insult me, but I'm a NOOB here, sorry for that. Please tell me how to grab a logcat (I think what you wrote refers to that) or give me a link for instructions to follow.

Because I think you can only grab a logcat if your phone can boot up.
[Android] MSF Jarvis:
You can grab a logcat even on the bootanimation. Simple adb logcat does the trick ;)
[Android] Garv Maggu:
But it doen't show the boot animation or anything, please explain, it shows no devices found in CMD.
[Android] MSF Jarvis:
Not booting is a very vague term. If there's no bootanimation then your ramdisk and/or kernel are derped
[Android] hackslash:
I have been successfully able to build a ROM (thanks to this guide). There are some issues with the ROM. I'm trying to fix them but the most stupid one is the abnormal battery percentage. CM reports it incorrectly. It reports it as 3397%. Does anyone knows from where should I start to resolve this issue.
[Android] Cristiano Lira:
Now I'm getting this error from ProGuard. Before adding that line to fix Jack Server error I didn't get this.

Error:
[Android] OfficerJimLahey:
If it is perpetually "no devices found" or always "waiting for device", then you would have a kernel/ramdisk issue. Try to get back recovery and a /proc/last_kmsg (or a log like that) may just be waiting for you.

If your device pops up for a short period but is inaccessible (e.g. "unauthorized"), you will need a commit like this in your device tree, at least for the time being.

Hope this helps. :cowboy:
[Android] Arvind7352:
Pls share your Device and kernel tree. According to your piece of code, you're trying to build a ROM for which the source is located here...

https://github.com/carbon-mt4gs

branch 'jb2'

I presumed you were using THIS Device Tree and THIS Kernel tree.

If this is true then, the TARGET_KERNEL_SOURCE definition (kernel/htc/android_kernel_htc_msm8660) and the kernel checkout directory (viz. kernel/htc/msm8660) are Different.

But i don't think my assumption would be right. Pls correct me if I'm wrong.
[Android] spenceboy98:
Okay, so I've been able to successfully build Cyanogenmod 13 for my LG G3 (vs985), and now I'm experimenting with building Cyanogenmod for unsupported devices. At first I was getting an issue with a "malformed recovery.fstab" (which I still couldn't figure out what was wrong with it), but now I'm getting an entirely different issue after I did "repo sync."

Notice file: bionic/libc/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libc.so.txt
Notice file: bionic/libc/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libc_common.a.txt
Notice file: external/jemalloc/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libjemalloc.a.txt
Notice file: bionic/libdl/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libdl.so.txt
Notice file: bionic/libm/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libm.so.txt
Notice file: bionic/libm/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//system/lib/libm.a.txt
make: *** No rule to make target 'vendor/cm/charger/fonts//font_log.png', needed by '/home/spencer/android/system/out/target/product/ariel/obj/ETC/font_log.png_intermediates/font_log.png'. Stop.
make: *** Waiting for unfinished jobs....
Notice file: external/sepolicy/NOTICE -- /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src//root/property_contexts.txt
make: Leaving directory '/home/spencer/android/system'

#### make failed to build some targets (04:24 (mm:ss)) ####

I have no idea what's causing this issue or the issue I was having before. Any advice would be appreciated.
[Android] OfficerJimLahey:
Source repo is right, but I am using the KK branches.

That would be:

Kernel (in a test branch for now, to not overwrite the android-msm-doubleshot-3.4-caf branch)

Device Tree

Common Device Tree

ROM Manifest and Last-Known-Good local manifest

Lastly the QCom Display-Legacy, sans latest commit (so please ignore the highlighted line and note the one I shared above)

As mentioned before, the kernel (at least parts) have been building thus far.

Hope this helps.
[Android] osas514:
Got same error with aicp but i was able to bypass the error by simply copying font_log.png from vendor/aicp/charger/fonts/hdpi(My device is hdpi) to vendor/aicp/charger/fonts

in your case you should goto vendor/cm/charger/fonts and simply copy font_log.png from the xxhdpi(Not sure if this is the correct one for your device) folder and paste it to vendor/cm/charger/fonts
[Android] Garv Maggu:
Getting this error.

I searched about it everywhere and they said I am missing some repos but I don't think I am missing a single repo.

[IMG="Hostapd Error"]http://s6.postimg.org/e2q040tjl/4_Hostapd_Error.png[/IMG]

Any ideas?
[Android] spenceboy98:
Alright that seemed to do the trick. Thanks!

But now I'm back where I was before:

build/tools/generate-notice-files.py /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.txt /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot	emmc	/dev/block/mmcblk0p6"
build/core/Makefile:1074: recipe for target '/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh' failed
make: *** [/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/spencer/android/system'

#### make failed to build some targets (03:08:28 (hh:mm:ss)) ####

Here is my recovery.fstab:

# mount point	fstype	device	[device2]

/boot	emmc	/dev/block/mmcblk0p6
/cache	ext4	/dev/block/mmcblk0p13
/data	ext4	/dev/block/mmcblk0p14
/recovery	emmc	/dev/block/mmcblk0p7
/system	ext4	/dev/block/mmcblk0p12
/usb-otg vfat	/dev/block/sda1 /dev/block/sda
/system_image emmc /dev/block/mmcblk0p12

Any help is appreciated.
[Android] Jeik:
Hello! :D

I managed to make the system mount(FINALLY!),but now there is another thing.

The CyanogenMod boot animation logo is extremely small,and it loops there.

I first only incorporated the proprietary graphics libs from my phone in order to make the rom boot first.

Here is the logcat:

http://hastebin.com/honuboguwu.md

This line

08-17 17:48:01.978 281 281 E SurfaceFlinger: hwcomposer module not found

seems to be the cause,but I have no idea what it is asking for. :S

I hope somebody can help me...
[Android] Arvind7352:
Seems like it's searching for libhwcomposer.so module.

This module is built from hardware/qcom/display

(display-caf won't work coz its for QCOM Devices, and I think your device has a Kirin Processor (Kirin 650 I guess))

BTW, Congo for getting it till here. :)
[Android] Frostyagent:
out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts: line 338 has invalid context u:object_r:btlock_file:s0

libsepol.context_from_record: type mpctl_socket is not defined

libsepol.context_from_record: could not create context structure

libsepol.context_from_string: could not create context structure

libsepol.sepol_context_to_sid: could not convert u:object_r:mpctl_socket:s0 to sid

out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts: line 341 has invalid context u:object_r:mpctl_socket:s0

libsepol.context_from_record: type camera_socket is not defined

libsepol.context_from_record: could not create context structure

libsepol.context_from_string: could not create context structure

libsepol.sepol_context_to_sid: could not convert u: object_r:camera_socket: s0 to sid

out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts: line 342 has invalid context u:object_r:camera_socket:s0

Invalid context file found in out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts

make: *** [out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts] Error 5

make: *** Deleting file `out/target/product/f320/obj/ETC/file_contexts_intermediates/file_contexts'

Having this issue while compiling AOSP 6.0.1 .. anyone help me please
[Android] NepoRood:
You need to reformat your fstab file like so:

/dev/block/mmcblk0p6 /boot emmc
[Android] Jeik:
Emm,I am a bit confused.

I discovered that I hadn't configured the cache partition size in my BoardConfig,so I decided to do that.

However,while building,I get this "warning":

unable to load device-specific module; assuming none
using prebuilt recovery.img from BOOTABLE_IMAGES...
using system.img from target-files
Total of 655360 4096-byte output blocks in 1871 input chunks.
Generating digraph...
Finding vertex sequence...
Reversing backward edges...
0/0 dependencies (0.00%) were violated; 0 source blocks stashed.
Improving vertex order...
Revising stash size...
Total 0 blocks are packed as new blocks due to insufficient cache size.
Reticulating splines...
max stashed blocks: 0 (0 bytes), limit: 214748364 bytes (0.00%)

with the emphasis on

Total 0 blocks are packed as new blocks due to insufficient cache size.

The phone won't get to the boot animation anymore with the new build(which has cache partition size defined)

Here is my BoardConfig.mk

http://hastebin.com/uheboyulox.vala

I set the cache partition size to the one of a Huawei P8 Lite,because it and the P9 Lite are the most similar phones...
[Android] NepoRood:
Allwinner A83

First off, this is a great thread! I've been reading and learning here for hours :good:

For my issue(s) I'm having some problems getting my roms to boot on my X10 tablet. It'll either loop or boot to manufacturer logo, then shut down.

After doing some exploring, I found out after compiling there's no init or anything sepolicy related in the boot.img. Only a few "cm" or "du" related init.*.rc files, and what I copied over using product copy files.

The device tree and vendor tree are made from scratch, as I really had nothing to go on. Last custom rom built for Allwinner was Jelly Bean, as far as I can tell and 99% of stuff I've found on Github is 3 or more years old :crying:

But I'm having fun, lol

Any thoughts would be appreciated.

Regards,

Nepo

Source Code: BlissRoms and Dirty Unicorns (both Android 6)

Device Tree (most up to date tree)

Vendor Tree
[Android] spenceboy98:
It's still not working:

build/tools/generate-notice-files.py /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.txt /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/dev/block/mmcblk0p6	/boot	emmc"
build/core/Makefile:1074: recipe for target '/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh' failed
make: *** [/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/spencer/android/system'

#### make failed to build some targets (03:09:20 (hh:mm:ss)) ####

Current recovery.fstab:

# device	[device2]	mount point	fstype

/dev/block/mmcblk0p6	/boot	emmc
/dev/block/mmcblk0p13	/cache	ext4
/dev/block/mmcblk0p14	/data	ext4
/dev/block/mmcblk0p7	/recovery	emmc
/dev/block/mmcblk0p12	/system	ext4
/dev/block/sda1	/dev/block/sda	/usb-otg vfat
/dev/block/mmcblk0p12	/system_image emmc

Again, any help is appreciated.
[Android] Droidcore:
[MENTION=4139665]martinusbe[/MENTION] any news? Why I always stop on kernel/obj/.header_stamp_install.o

Kernel/oneplus/msm8994 error
[Android] AndDiSa:
[MENTION=6868754]spenceboy98[/MENTION] you need to respect the format, i.e. insert spaces / tabs where needed ...
[Android] tschmid:
Make a space like so /boot emmc

/boot is the mountpoint and emmc the fs type

Same with others

Gesendet von meinem Nexus 6P mit Tapatalk

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

/cache ext4

Gesendet von meinem Nexus 6P mit Tapatalk
[Android] akhilnarang:
Confirm whether its the same as your device's
[Android] PseudoDev:
Porting ubuntu touch

[MENTION=5305791]KeTuRr74[/MENTION]
[MENTION=5854483]akhilnarang[/MENTION]

I downloaded sources for ubuntu touch.

I Didnt modify the "manifest.xml" in any way.

Here's the error that i get when i run "repo sync". :

warn: .repo/manifests: Not replacing locally modified pre-auto-gc hook
warn: .repo/manifests: Not replacing locally modified commit-msg hook
fatal: error parsing manifest /home/pseudodev/phablet/.repo/manifest.xml: not well-formed (invalid token): line 1, column 7

Please help me.
[Android] Jeik:
In stock rom,it is 248MB=260046848 bytes for BoardConfig.mk.

I mean,the logcat mentioned this in builds which didn't have cache size defined in BoardConfig.mk:

08-17 17:48:02.238 318 322 W BootAnimation: Unable to cache the animation

and

08-17 17:48:02.253 318 322 D BootAnimation: Use save memory method, maybe small fps in actual.

Could that error be because of the lack of a defined cache partition size?

And I still don't understand why the boot animation logo is so small,why does it say 5760 px??

08-17 17:48:01.977 281 281 I gralloc : xres = 1080 px
08-17 17:48:01.977 281 281 I gralloc : yres = 1920 px
08-17 17:48:01.977 281 281 I gralloc : xres_virtual = 1080 px
08-17 17:48:01.977 281 281 I gralloc : yres_virtual = 5760 px

EDIT

Even though I added cache partition size variables,I saw this in the output while building.

Total 0 blocks are packed as new blocks due to insufficient cache size.

And this is the latest logcat:

http://hastebin.com/owabapapiy.md

The phone enters the bootanimation,and unlike in old builds,it reboots after a while into TWRP. :confused:
[Android] nicesoni_ash:
I am a complete newbie in rom building and this is my first attempt in doing so. I appreciate all help I can get here.

So far I installed all needed packages, synched the rr repo (complete source).

When I run lunch command, I got list of devices and I selected #93 which was for cm_oneplus2-eng.

I got error about not finding make file for it and script automatically tried to sync from cm repositories searching for op2. It then merged both repositories and keep downloading stuff.

So far it was ok but then it was downloading repositories of oneplus1 too and that's why I halted that process and now repeating it doesn't do that and ask me whether I know the correct repository.

So so far what have I done wrong, how to fix this op2 makefile error and how to clear and unmerge such mess that I made.

Thanks and I appreciate all help.

Regards

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

Fueled by 7000mAh ZeroLemon Battery
[Android] Garv Maggu:
Can't get past this error.

make[1]: Entering directory `/home/garvmaggu/du/kernel/sony/msm8x27'
Symlink: /home/garvmaggu/du/out/target/product/nicki/system/bin/app_process -> app_process32
Symlink: /home/garvmaggu/du/out/target/product/nicki/system/bin/dalvikvm -> dalvikvm32
make: *** No rule to make target `NOTICE-TARGET-STATIC_LIBRARIES-libqc-art-compiler', needed by `/home/garvmaggu/du/out/target/product/nicki/system/lib/libart-compiler.so'. Stop.
make: *** Waiting for unfinished jobs....
CHK include/linux/version.h
make[1]: Leaving directory `/home/garvmaggu/du/kernel/sony/msm8x27'

Any help is appreciated.

Thanks in advance. :)
[Android] sagarshah1729:
Pick this commit in art and your error will be solved..

http://review.cyanogenmod.org/#/c/112322/
[Android] Jeik:
Emm,guys,how can I enable full adb on an experimental CM build?

I made an engineering build,but the kernel it creates won't get past the boot animation.

And the modified stock kernel actually gets past the boot animation and then a black screen appears.

However,on the modified stock kernel,the device is recognized as "offline" in adb, so I can't make a logcat.

I tried editing the default.prop,but nothing changed...
[Android] spenceboy98:
But I did have tabs. :| I replaced them all with spaces, though and tried again. Same error:

build/tools/generate-notice-files.py /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.txt /home/spencer/android/system/out/target/product/ariel/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/spencer/android/system/out/target/product/ariel/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/home/spencer/android/system/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/dev/block/mmcblk0p6 /boot emmc"
build/core/Makefile:1074: recipe for target '/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh' failed
make: *** [/home/spencer/android/system/out/target/product/ariel/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/spencer/android/system'

#### make failed to build some targets (03:27:03 (hh:mm:ss)) ####

New recovery.fstab:

# device [device2] mount point fstype

/dev/block/mmcblk0p6 /boot emmc
/dev/block/mmcblk0p13 /cache ext4
/dev/block/mmcblk0p14 /data ext4
/dev/block/mmcblk0p7 /recovery emmc
/dev/block/mmcblk0p12 /system ext4
/dev/block/sda1 /dev/block/sda /usb-otg vfat
/dev/block/mmcblk0p12 /system_image emmc
[Android] sagarshah1729:
Cherry pick this commit in build..Your error will be solved..

https://github.com/CyanogenMod/android_build/commit/ad12b369afca4b6b3764ad0a70778c0a924cdc68
[Android] Garv Maggu:
This error is irritating me a lot.

First of all, it said that it needed a libvixl.so file.

The error was "No rule to make target /<long path>/libvixl.so" so I manually created it.

Now it is showing that it is empty, ofcourse it is.

Any ideas?

prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8//x86_64-linux/bin/ld: error: /home/garvmaggu/du/out/host/linux-x86/obj/lib/libvixl.so: file is empty
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8//x86_64-linux/bin/ld: error: /home/garvmaggu/du/out/host/linux-x86/obj32/lib/libvixl.so: file is empty
[Android] nicesoni_ash:
After four long hours in the end, I got this error and build failed.

Make fork : cannot allocate memory

Any suggestions?

I don't remember whether I set the value of ccache to 50gb or not. I have 4gb of ddr3 ram on my Ubuntu mate 16.04.1 x64 build.

Should I add swap file coz I didn't.

What can I do to fix this issue? Thanks.

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

Fueled by 7000mAh ZeroLemon Battery
[Android] AndDiSa:
You need to add some swap space, 4GB is definitely much too low, but unfortunately your build will take even longer ...
[Android] nicesoni_ash:
I'll put 4gb more tomorrow and some swap space too, 10gb would be good enough or excessive? Thanks.

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

Fueled by 7000mAh ZeroLemon Battery
[Android] AndDiSa:
For building Android you'll never have excessive memory ... :)
[Android] MSF Jarvis:
I've got 32 gigs on my server and it sometimes feels very less lol
[Android] HB72K:
http://pastebin.com/1b7q0g0U

any idea? tnx
[Android] AndDiSa:
Insufficient memory for jack to compile ... You need to increase the value for max heap size for jack, e.g. add -Xmx4g to JACK_SERVER_VM_ARGUMENTS