yashsingh1/xdaforums huggingface dataset:
[G2 Developer Discussion [Developers Only]] GalaticStryder:
The precious error was fixed by using C_FLAGS = -Os in camera makefile, for all .cpp. I'll commit all the changes I've done for future people who want to use these OPTS. But first I need to fix all of them :fingers-crossed:

I already had it, I fixed this error today but I got one that regards to this commit, I'll try reverting the commit and reply later, I am compiling my based on Slim and Slim Saber ROM, the straight from the source is fine [MENTION=2777226]arcardinal[/MENTION].

Edit, got an error related to qcom/media/... because of the heap_id_mask commit, I think editing the .h omx_video_base and changing the following line:

#ifdef _ION_HEAP_MASK_COMPATIBILITY_WA
#define ION_HEAP_MASK heap_mask
#else
#define ION_HEAP_MASK [U]heap_id_mask[/U]
#endif

to

[B]heap_mask[/B]

because it looks like ifdef _ION_HEAP_MASK_COMPATIBILITY_WA is not defined, so it takes else which is pointed to heap_id_mask. Let's see the next errors and fix them.
[G2 Developer Discussion [Developers Only]] Flo0008:
[MENTION=3279781]bender_007[/MENTION]

In any way, I cant send you a message anymore (it says, your inbox is exceeded ... So the rom did boot?
[G2 Developer Discussion [Developers Only]] bender_007:
It Boots. There is no network, no imei. Rotation works
[G2 Developer Discussion [Developers Only]] jfpsb:
Do you know where _ION_HEAP_MASK_COMPATIBILITY_WA is defined? I can't find it anywhere.
[G2 Developer Discussion [Developers Only]] arcardinal:
In the kernel. For instance, see this commit

https://github.com/SlimRoms/kernel_lge_msm8974/commit/4696250393c0c1e71da0ea26d45cfb58fe652f17
[G2 Developer Discussion [Developers Only]] jfpsb:
Great. Thank you very much.
[G2 Developer Discussion [Developers Only]] Bx16:
Hi Guys!

I have problem with not booting ROMs (stuck on LG logo), I had to reinstall my Ubuntu and after this I setup my env for compiling, used extract-files script and build ROM. ROM builed without any problems but it's smaller than previous. (215MB vs 235MB) and not boot.. I have this problem with Candy5 and crDroid. :(

Things which may help:

1. My local manifest

2. Build of not booting ROM: http://d-h.st/7AWp

Someone can tell what im doing bad and help fix it?
[G2 Developer Discussion [Developers Only]] Flo0008:
Try this: rm -rf kernel && rm -rf device && . build/envsetup.sh && make clean && make clobber && rm -rf out && repo sync -j8

Now build again please and tell me if this helped.
[G2 Developer Discussion [Developers Only]] Bx16:
Used this command and made new build and its have same size. :(
[G2 Developer Discussion [Developers Only]] GalaticStryder:
You're taking divergent source trees for vendor/lge, if you take a look the specific files that are in vendor/lge/$DEVICE we're not pushed to the .zip that's why the size is too small, actually their from LG-Devs but for your ROM I would recommend you take them directly from CM and vendor/lge from TheMuppets, the pathes are pointed in the device/lge/$DEVICE if you want to take a look and force the LG-Devs work with the device from CyanogenMod you'll need to change some paths.

Just as an example: https://github.com/SaberSunset/sync

I've ran into the same problem, here is my explanation for that: http://xdaforums.com/showpost.php?p=58503727&postcount=89

Each case is a case, but your problem looks the same that I had and maybe the solution will be change the source trees. Report back.
[G2 Developer Discussion [Developers Only]] Bx16:
[MENTION=6175749]GalaticStryder[/MENTION]: Thank you very much for help! I changed my sources to CM (only kernel is from LG-Devs) and ROM working fine. :)
[G2 Developer Discussion [Developers Only]] zg85:
No one could help me with migrating PAC (CM) to new kernel/device sources?

Last build settings was :

<project name="AICP/device_lge_d802" path="device/lge/d802" remote="github" revision="kitkat" />
<project name="AICP/device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="kitkat" />
<project name="AICP/kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="kitkat" />
<project name="AICP/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="kitkat" />
<project name="AICP/frameworks_native" path="frameworks/native" remote="github" revision="kitkat" />
<project name="AICP/hardware_libhardware_legacy" path="hardware/libhardware_legacy" remote="github" revision="kitkat" />
<project name="platform/hardware/qcom/msm8x74" path="hardware/qcom/msm8x74" remote="aosp" revision="refs/tags/android-4.4.4_r2" />
<project name="platform/hardware/qcom/sensors" path="hardware/qcom/sensors" remote="aosp" revision="refs/tags/android-4.4.4_r2" />

but still sensors are dead.. I'm missing maybe some policy settings? Any help? How to make CM work with pure KK kernel/device? Is it possible?

Best wishes !
[G2 Developer Discussion [Developers Only]] Boris31:
local_manifest

This is working local_manifest for me for comiling SlimLp thanks to [MENTION=5236920]zg85[/MENTION]

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="SlimRoms/device_lge_d802" path="device/lge/d802" remote="github" revision="lp5.0" />

<project name="SlimRoms/device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="lp5.0" />

<project name="SlimRoms/kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="lp5.0" />

<project name="SlimRoms/device_qcom_common" path="device/qcom/common" remote="github" revision="lp5.0" />

<project name="Pinky-Inky-and-Clyde/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.0" />

</manifest>
[G2 Developer Discussion [Developers Only]] zg85:
Probably this would be Your local manifest ;)

<project name="CyanogenMod/android_device_lge_d802" path="device/lge/d802" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.0" />
<project name="Pinky-Inky-and-Clyde/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.0" />
[G2 Developer Discussion [Developers Only]] Boris31:
Thanks for help but now i get this error after adding this lines in local_manifest when i try to sync repo:

simex@simex-desktop:~/cm12$ repo sync

fatal: duplicate path device/lge/d802 in /home/simex/cm12/.repo/manifest.xml
[G2 Developer Discussion [Developers Only]] zg85:
Search in manifest.xml for "device/lge/d802" and remove that line (and any of duplicated paths) :)

How do You add local manifest? Create folder in .repo called "local_manifests" and put Your XML there or by adding lines to manifest.xml?

The proper way is to create folder and put there Your manifest.xml.
[G2 Developer Discussion [Developers Only]] Boris31:
i create local_mainfest this way: cd cm12/.repo than sudo nano local_manifests.xml and copy your lines, there and crtl O to save. In file manifest.xml there is nothing with device/lge/d802
[G2 Developer Discussion [Developers Only]] wulsic:
See if there is maybe a file named roomservice.xml in your local_manifest folder and remove it.
[G2 Developer Discussion [Developers Only]] Boris31:
Help needed :)

So im compiling flawlessly slimlp with no problemes and now i would like to add some futures and optimizations but i cant seem to understand how to do it properly and there arent good and well explained guides for that. Is maybe any of you guys friendly developers free and willing to help me? :o :o :o
[G2 Developer Discussion [Developers Only]] TaRsY:
http://xdaforums.com/slimroms/general/rom-builders-collective-t2861778

Take a look here, especially from post #17 and ezio84's github link with the list of commits you can cherry-pick.

Compiling slim lp you synced all the slim repos or only the needed? Are you using repos from slim or from arcardinal, cardinal testing?
[G2 Developer Discussion [Developers Only]] rafitcu:
I need help.

I'm compiling a kernel with the sources of CM12.1 and pulls me this error:

**Ksym .tmp_kallsyms2.S

**AS .tmp_kallsyms2.o

**LD vmlinux

**SysMap System.map

**SysMap .tmp_System.map

**Objcopy arch / arm / boot / Image

**Building modules, Stage 2.

**MODPOST 35 modules

**Kernel: arch / arm / boot / Image is ready

**LZ4 arch / arm / boot / compressed / piggy.lz4

**CC arch / arm / boot / compressed / decompress.o

*** LZ4 Compression algorithm using CLI, by Yann Collet (Mar 14 2013) ***

Using stdin for input

Using stdout for output

In file included from arch / arm / boot / compressed /../../../../ lib / decompress_unlz4.c: 19: 0,

*****************from arch / arm / boot / compressed / decompress.c: 54:

include / linux / decompress / mm.h: In function 'free.isra.0':

include / linux / decompress / mm.h: 59: 1: internal compiler error: in df_reg_chain_verify_unmarked, at df-scan.c: 4305

*}

*^

Please submit a full bug report,

With preprocessed source If appropriate.

See <http://gcc.gnu.org/bugs.html> for instructions.

make [2]: *** [arch / arm / boot / compressed / decompress.o] Error 1

make [2]: *** It is expected to complete other tasks ....

Compressed into 8259556 bytes 17758660 bytes ==> 46.51%

Done in 0.94 s ==> 18.02 MB / s

make [1]: *** [arch / arm / boot / compressed / vmlinux] Error 2

make: *** [zImage-DTB] Error 2

Please help me frustrated took several days for this error.

thx in advance :)
[G2 Developer Discussion [Developers Only]] wulsic:
Here ya go,

http://xdaforums.com/chef-central/a...evelopment-t2814763/post59122369#post59122369

Read through the posts and I think you will fix your problem :good: I also think that it's toolchain related as newer toolchains can cause several issues.
[G2 Developer Discussion [Developers Only]] nimrodsv:
Hi everyone,

I'm trying to build SlimLP rom and for some reason starting yesterday i'm having issues with the TARGET_KERNEL_CONFIG on both d802 and d801.

Where can i find where the kernel config name is defined?

Thanks.

Im getting the following error on both:

***
*** Can't find default configuration "arch/arm/configs/cyanogenmod_d801_defconfig"!
***
/home/nimrodsv/Android/SlimLP/kernel/lge/msm8974/scripts/kconfig/Makefile:96: recipe for target 'cyanogenmod_d801_defconfig' failed
make[3]: *** [cyanogenmod_d801_defconfig] Error 1
/home/nimrodsv/Android/SlimLP/kernel/lge/msm8974/Makefile:497: recipe for target 'cyanogenmod_d801_defconfig' failed
make[2]: *** [cyanogenmod_d801_defconfig] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/nimrodsv/Android/SlimLP/kernel/lge/msm8974'
build/core/tasks/kernel.mk:218: recipe for target '/home/nimrodsv/Android/SlimLP/out/target/product/d801/obj/KERNEL_OBJ/.config' failed
make: *** [/home/nimrodsv/Android/SlimLP/out/target/product/d801/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
In file included from <command-line>:0:0:
./build/core/combo/include/arch/linux-x86/AndroidConfig.h:316:5: warning: "__GLIBC__" is not defined [-Wundef]
./build/core/combo/include/arch/linux-x86/AndroidConfig.h:316:23: warning: "__GLIBC__" is not defined [-Wundef]
# In case value of PACKAGES is empty.

By the way this is my local manifest:

<manifest><project name="SlimRoms/device_lge_d801" path="device/lge/d801" remote="github" revision="lp5.1"/><project name="SlimRoms/device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="lp5.1"/><project name="gmillz/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.1"/><project name="SlimRoms/kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="lp5.1"/><project name="SlimRoms/device_lge_d802" path="device/lge/d802" remote="github" revision="lp5.1"/></manifest>
[G2 Developer Discussion [Developers Only]] SergeantWagner:
Hey guys. Hopefully someone is still monitoring this thread.

I used to build cm for tf201 so I have some experience. Trying to build CM12 for D800 and I get this:

make: *** No rule to make target '/android/system/out/host/linux-x86/bin/dtbToolCM', needed by '/android/system/out/target/product/d802/dt.img'. Stop.

I tried changing dtbToolCM to dtbTool and did not solve the problem as the error is the same (with CM dropped from the dtbTool).

Any help would be greatly appreciated.

Edit: I found a dtbToolCM and just dumped them into system/out/host/.../bin/ and compiled successfully, then was able to boot to compiled rom. Apparently I could have just created a dummy dtbToolCM to get past the make error and just would not have dt.img

Now to start working on 12.1!
[G2 Developer Discussion [Developers Only]] ponces:
AOSP 6.0

Hello G2 devs,

I'm trying to build an AOSP 6.0 rom from AOSP source and CM13 repos. It is possible right?

This is my local manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="git://github.com" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge/" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_lge_d802" path="device/lge/d802" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_lge_g2-common" path="device/lge/g2-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_sepolicy" path="device/qcom/sepolicy" remote="github" revision="cm-13.0" />
</manifest>

I know kernel builds usually give a few headaches so I'm trying to build with a prebuilt kernel zImage extracted from a boot.img of the last CM13 nightly, changed its name to "kernel" and moved it to device/lge/d802 folder.

So I made several edits to some device files:

device/lge/d802/BoardConfig.mk

#TARGET_KERNEL_CONFIG := cyanogenmod_d802_defconfig

ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := device/lge/d802/kernel
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

PRODUCT_COPY_FILES += \
$(LOCAL_KERNEL):kernel

device/lge/g2-common/BoardConfigCommon.mk

#TARGET_KERNEL_SOURCE := kernel/lge/msm8974

After a make -j4 otapackage the result is this -> http://pastebin.com/N6nkxmUh

Is it possible to build only system.img? Will it boot with a boot.img from a CM13 nightly? Can anyone help me with this error?

Best regards,

ponces
[G2 Developer Discussion [Developers Only]] matteo0026:
Hi to all, i built an cm14 for d802, but i must resolve all the problems. It works only WiFi i think. To fix i have surely:

- RIL

- Bluetooth

- NFC

- Can't pull down fully QS (only see the main with notifications)

- Can't unlock Developer Options

Thanks.
[G2 Developer Discussion [Developers Only]] shaneel1491:
Today I tried my first build of an Android ROM, I downloaded the AOSP source, with the latest 7.0.0 r14 branch. I have been following the guide from the Xperia dev page, the cyanogen wiki and the Google source page, however when everything is downloaded and placed in the correct place. I downloaded the device tree as well and put it in place.

I'm getting the error of:

Don't know what I should do from here, I tried googling and doing what other people did, but I had no luck.

This is what my local manifest looks like, if it matters:
[G2 Developer Discussion [Developers Only]] matteo0026:
Hi guys, i'm trying to building cm14.1 with [MENTION=4575133]Rick Roll[/MENTION] repos and official's cm, but doesn't work RIL. Why?
[G2 Developer Discussion [Developers Only]] calbertoferreira:
I'm also trying to do the same thing, build AOSP MM with CM device files.

I'm having this issue, any idea why ?

[IMG="Build output"]http://i.imgur.com/CR7k6wl.png[/IMG]
[G2 Developer Discussion [Developers Only]] calbertoferreira:
I removed the external/sepolicy from CM13 and used AOSP one.

Now, after calling make dist i have a system.img, a userdata.img and a ramdisk.img.

How can i turn this into an update.zip ?
[G2 Developer Discussion [Developers Only]] calbertoferreira:
That didn't work, it only worked with make dist.

Now, after flashing the rom, my LG G2 doesn't boot, it shows a security error.

Any idea on how to bypass this ?
[G2 Developer Discussion [Developers Only]] Sk0rpi0n89:
flash bumpboot after flashing the rom?
[G2 Developer Discussion [Developers Only]] calbertoferreira:
That worked!

For reference, if you're unable to boot use https://github.com/CyboLabs/Open_Bump to bump your boot image.

Now i have another problem, i don't have secure boot errors but the phone doesn't go beyond the LG logo.

These are my current logs:

- dmesg (https://drive.google.com/open?id=0Bz3ILCh3f-54Uk5jOGo5d0RYcmc)

- last_kmsg (https://drive.google.com/open?id=0Bz3ILCh3f-54R0VIR2dMMHF1bzQ)

Any idea why ?
[G2 Developer Discussion [Developers Only]] jackcicci:
Error d802/boot.img missing

Hello,

i'm trying to build AOSIP for LG G2 802 and the process stops with this error:

ninja: error: '/home/android/aosip/out/target/product/d802/dt.img', needed by '/home/android/aosip/out/target/product/d802/boot.img', missing and no known rule to make it

I've successfully bulided other ROM (most LineageOS based) like AOKP, OCT and other but with AOSIP I get always this problem. :(

Anyone can help me to understand what I'm doing wrong?

Thanks :)

It stops at the beginning and I have no idea of what to do :crying:

(complete log attached)
[Android Q&A, Help & Troubleshooting] TecknoFreak:
Can anyone please tell me how to fix this?

Here is the log

http://pastebin.com/ggb932Lf

Is it a partition thing? I also read about this error happens because of permissions but all permissions are correct during build. No clue what else to look forward. [MENTION=2218140]kabaldan[/MENTION]

Thanks for your help
[Android Q&A, Help & Troubleshooting] kabaldan:
Too big system image size has been specified when the update package has been built.

It's BOARD_SYSTEMIMAGE_PARTITION_SIZE.

In CM12, it's specified in /device/motorola/qcom-common/BoardConfigCommon.mk as 1560281088.

It matches the size in /sys/block/mmcblk0/mmcblk0p37/size (3047424 * 512 = 1560281088) of both XT925 and XT897 I can personally check.

Is the system partition size of Atrix HD slightly smaller?
[Android Q&A, Help & Troubleshooting] TecknoFreak:
[MENTION=2218140]kabaldan[/MENTION] Shouldn't be the same as all these devices share the same specs? Like jbbl and kkbl device tree. Or would it varies on lolli?
[Android Q&A, Help & Troubleshooting] kabaldan:
The different moto_msm8960 devices never had the same specs. They are very similar but not the same.

The exact system size was not important (while it was big enough) till the Lollipop switch to block based flashing of system in update packages.

What's the value of /sys/block/mmcblk0/mmcblk0p37/size on mb886?

su
cat /sys/block/mmcblk0/mmcblk0p37/size
[Android Q&A, Help & Troubleshooting] TecknoFreak:
307200 is my device size bro

Thanks
[Android Q&A, Help & Troubleshooting] kabaldan:
Oops, sorry, p37 is the cdrom partition.

What's the size of p36 on mb886?

cat /sys/block/mmcblk0/mmcblk0p36/size
[Android Q&A, Help & Troubleshooting] TecknoFreak:
cat /sys/block/mmcblk0/mmcblk0p36/size

2507264
[Android Q&A, Help & Troubleshooting] kabaldan:
OK, that's it.

The system partition size on Razr HD, Razr M and Photon Q is 1560281088 while on Atrix HD it is 1283719168 (2507264 * 512).

To build an Atrix HD compatible update zip, you'd have to change 1560281088 to 1283719168 here:

https://github.com/CyanogenMod/andr...-common/blob/cm-12.0/BoardConfigCommon.mk#L59
[Android Q&A, Help & Troubleshooting] TecknoFreak:
Wooohoooooo perfect mate. Thanks a lot
[Android Q&A, Help & Troubleshooting] TecknoFreak:
Didnt worked as I thought it will this time. :(

I still get Status 1 error while flashing ROM.

Now with this recovery.log

http://pastebin.com/PeVZckDN
[Android Q&A, Help & Troubleshooting] kabaldan:
According to the log, the updater still tries to erase 380928 blocks (380928 * 4096 = 1560281088) instead of 313408 blocks (313408 * 4096 = 1283719168).

Was it a clean build?
[Android Q&A, Help & Troubleshooting] TecknoFreak:
Yes it was all the way in order to get a clean log.
[Android Q&A, Help & Troubleshooting] kabaldan:
Well, the system size 1560281088 that the updater is still using has to come from somewhere.

One possibility is that it was not cleanly rebuilt after the change to 1283719168, other possibility is that the 1560281088 size is still defined somewhere in the device tree from which you build.
[Android Q&A, Help & Troubleshooting] TecknoFreak:
Hey bro,

It works, it works. Thanks so much

now we can build a rom compatible to all moto_msm8960_jbbl devices. Raza M could lose some system partition size, but no big problem, it can be restored it with a correct BOARD_SYSTEMIMAGE_PARTITION_SIZE ROM.

Also [MENTION=274736]mijuu[/MENTION] said thank you so much
[Galaxy S 4 Q&A, Help & Troubleshooting] Musti222:
Hello guys,

I have a rooted S4 with Knox Flag and a custom rom which really worked well. But now i do not understand why i am getting a pop up which says that the phone can not recognize my sim card and wants to restart. First it just came some times. Now it totally does not find my sim card. I also bought a new card reader and built it in but i have the same problem.

I also tried to bring everything to Stock but this either doesn't worked.

I hope someone can help. :D

Thanks,

Musti
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Reflash STOCK ROM and tell me if works ok. Looks like a hardware problem anyway.
[Galaxy S 4 Q&A, Help & Troubleshooting] xDroidZz:
Things you can do.

-Flash stock again.

OR

Update your modem.

maybe its hardware related. go to phone repair shops if they can help you.
[Galaxy S 4 Q&A, Help & Troubleshooting] Musti222:
Hey,

so I flashed the stock rom via Odin but it is still the same problem.

What do you mean with updating the modem? Maybe I should read and try that out thanks!
[Galaxy S 4 Q&A, Help & Troubleshooting] Musti222:
Thanks for the help. Tried Stock rom and flashed a new Modem. Tried it from this http://xdaforums.com/showthread.php?t=2192025 but it doesnt worked. Again the same problem.
[Galaxy S 4 Q&A, Help & Troubleshooting] xDroidZz:
then its hardware related try to clean your sim tray or however is it called. or give it to a repair guy and let it fix. shouldnt be a big problem at all i think

Goodluck :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] MAX 404:
Hi mate

Check your imei , dial *#06# see if you have the same imei as in the sticker behind the battery of your phone
[Galaxy S 4 Q&A, Help & Troubleshooting] Musti222:
I bought one sim slot because i thought the same. But it didnt solve the problem.

Checked it. The Imei number from behind the phone is the same when i dial *#06#
[Galaxy S 4 Q&A, Help & Troubleshooting] xDroidZz:
then its time to go to a repair shop. thats your last option :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] MAX 404:
Hi mate ,

The problem may be in the EFS partition , do you have an EFS back up? if not you may have to take it to a local service shop , you need a Z3X box or similar to fix it.
[Galaxy S 5 Q&A, Help & Troubleshooting] Nightskill:
Hello,

Since I'm running Android Lollipop (the touchwiz version) I'm no longer able to control Spotify or PowerAmp using the head unit of my car.

There is also no media information transfered to the head unit.

With KitKat everything just worked fine.

Does someone know what I can to about this problem?

Greetz Nightskill

Gesendet von meinem SM-G900F