Compiling CM12 for G2 topic

Hi guys! I've worked in several stock ROM projects, but I never learned how to build roms from source, I dont know why. Yesterday, I read some threads, and installed Ubuntu 14.04 in my lap. I am following the following threads to compile CM12:

• Compiling CM12 for Moto G


• Official CM12 Compiling guide

I started the first one, which I think is very clear, but when I arrive to this I have to stop:

Quote:

Once all that stuff's over, create a folder called Code: local_manifests in the .repo folder, and then make a new file in that folder called Code: roomservice.xml open roomservice.xml using gedit, and add the following: Code: <?xml version="1.0" encoding="UTF-8"?> <manifest>  <project name="CyanogenMod/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-12.0"/>  <project name="CyanogenMod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" 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="CyanogenMod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-12.0"/>  <project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-12.0"/> </manifest>

Obviously, that code is for Moto G, but I don't know what should I write in that file. I found a thread in G2 section with the same question, but the OP had no answer.

Then I switched to the official thread trying to find some information. About local manifests it says:

Quote:

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type: Code: $ source build/envsetup.sh $ breakfast d802 This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod's GitHub and list all of the repositories defined in cm.dependencies in your local manifest.

Then I went to d802 github and located the cm.dependencies. Is that what I have to copy into the roomservice.xml file? Is this another way of preparing specific-device code?

If u know any other more comprehensive guide for d802 I would thank u so much if u could share with me. Any help is thanked.

Help with compiling topic

Hey guys,

Just got out of surgery and am looking at building my own copy of SlimLP. I am currently syncing the repo at the moment, my query was, how do I remove certain apps before compiling?

I don't use Email, Exchange e.t.c. so wanted to remove them from the rom.

Sorry if it's been asked before. Still a little woozy from the drugs and have been trying to search.

[Q/A] CM12 Git & ROM Compiling Error's topic

Hello , Everybody I'm Asanan . I'm Student . Today I Will Ask you about CM12 Compiling Error

i found some error for hwc_utils.cpp (qcom_display-caf)

if you can answer me . please reply . Thankyou :D

i will get screenshot on soon :victory:

[Q] Please help! (Kernel compiling, android booting) topic

Hello everyone!

I've seen everyone asking for Android on the Gear 2, but I'm not sure if anyone has actually _tried_. Has anyone? Is there a device tree I can use? has anyone found some info about it?

I thought at least I would give it a try, so I started digging a bit...
First thing is always the same, get to know the platform you're working with:

For what I've seen so far the CPU is quite similar to Galaxy S5 mini (Exynos 3470) but with 2 cores. GPU seems the same.

Gear 2
CPU: Exynos 3250
GPU: Mali 400
Display panel type: MIPI

Partition table:
boot -> ../../mmcblk0p5 --> Main Kernel
bota0 -> ../../mmcblk0p1
bota1 -> ../../mmcblk0p2
csa -> ../../mmcblk0p3 --> ext4 -> /csa
csc -> ../../mmcblk0p12 --> ext4 -> /system/csc
fota -> ../../mmcblk0p10 --> seems empty
module -> ../../mmcblk0p9 --> ext4 -> /lib/modules <-- Just one kernel module, I don't know why they left this here and not compile it directly, it makes no sense
param -> ../../mmcblk0p4 --> raw, it has some values lost along the flash, header starts with adv_eng.img
ramdisk1 -> ../../mmcblk0p7 // empty
ramdisk2 -> ../../mmcblk0p8 // ext4, it really doesn't seem to use it for anything, it looks like it's supposed to boot some kind of recovery but as far as I've seen, you can delete it all and it won't matter, recovery works from rootfs (look below)
recovery -> ../../mmcblk0p6 --> looks like another kernel, zImage-recovery when flashing, not sure if it's used
rootfs -> ../../mmcblk0p15 ext4 "/" --> Root file system, recovery works from here too. If you break it it will only boot to download mode.
system -> ../../mmcblk0p11 EMPTY --> Did samsung start with Android on this thing then changed their minds?
system-data -> ../../mmcblk0p13 --> ext4, /opt
user -> ../../mmcblk0p14 EXT4, /opt/usr --> all user data, including the MTP available part (/opt/usr/media)

Both kernel and recovery kernel partitions do have enough space to pack a boot image with a ramdisk, and in case that would be an issue for any other reason, Tizen kernel boots directly to the rootfs, so we could leave the init files in there and simply keep the root= parameter intact.

Now, to the main issue: Recompiling a kernel:
I grabbed the kernel source from Samsung's dial-up speed developer portal. I found the relevant config file for the Gear 2 (from now on, b2), and attempted to compile it:

Code:

---

make ARCH=arm tizen_b2_defconfig

---

Then, when you try to compile it...

Code:

---

In file included from include/drm/exynos_drm.h:32:0,
                from arch/arm/mach-exynos/board-tizen-display.c:19:
include/drm/drm.h:47:24: fatal error: sys/ioccom.h: No such file or directory
compilation terminated.
scripts/Makefile.build:307: recipe for target 'arch/arm/mach-exynos/board-tizen-display.o' failed
make[1]: *** [arch/arm/mach-exynos/board-tizen-display.o] Error 1
Makefile:947: recipe for target 'arch/arm/mach-exynos' failed

---

I've tried to disable the DRM part of the config, but the board-tizen-display is dependent on that code, failing to compile due to missing functions hardcoded on the display. Disabling the board-tizen-display entirely would render the LCD disabled, so that's not an option. Any ideas on how to fix this?

In case you're curious I've attached both bootloader log and the first try on booting TWRP recovery on this thing (it halts on healthd, and it eventually reboots itself...)

Attached Files

	twrp_launch_attempt1.txt - [Click for QR Code] (73.8 KB)
	sboot.txt - [Click for QR Code] (5.6 KB)

[Q] Dts/i & Compiling Vanilla Linux On Samsung Gt-S7580 topic

Hi guys,

As some of you are maybe aware of, broadcom released the documentation to their Videocore 4 chipset not long ago making all videocore 4 based SoC's, for all practical purposes and intent, open source. As such I was thinking of porting a linux distro to the GT-S7580; this will allow for continuos updates & extension of its lifecycle to beyond a smartphone.

Doing a cat /proc/cpuinfo on the GT-S7580 produces a Hardware : hawaii_ss_kylepro rev0000. This(hawaii) apparently corresponds to the BCM21664/T CPU and not the 21855(capri) as wikipedia originally indicated.

So I did some kernel "spelunking" on the opensource.samsung.com source and found that (unfortunately) the GT-S7580 device kernel does NOT use DTS. This means to actually compile vanilla for the 7580 I would need to some how include all the board files into the vanilla kernel OR create a DTS from the board files that I found; neither of which is a simple task from what I understand.

I have also however , in the process found that the device kernel does have a .dtsi file for the 21644 and a .dts for another board that uses it(kyleve == GT-S7392?) Oddly enough there is also a board file for the kyleve version.
So I've read up quite a bit on devicetree.org/free electrons but the task of writing a DT is still quite daunting to me. Seems like the main HW difference is in RF(HSPA etc) , camera specs; so Im thinking that they actually use the same pcb?? Can the dts for the 7392 used instead?

Im not allowed to post links since this is my first post but here is the post I made on CM that has inline pastebin links:

http(dot)//forum(dot)cyanogenmod(dot)org/topic/103336-dtsi-compiling-vanilla-linux-on-samsung-gt-s7580/

Can someone help me create a dts from the board files? Or show me how? Is there a board-->dts generator?

Thanks & Regards,
fps

[C++] Compiling OpenCL application to native ARM ELF using Debian topic

Hello,

I am posting to begin a thread regarding the native compilation and execution of OpenCL code on an ARM Android device, namely the HTC One M8.

I have used the app Linux Deploy to install a Debian desktop environment alongside Android, sharing the same Linux kernel but supplying different runtime libraries. Additionally, I have installed gcc/g++, Code::Blocks, and the OpenCL ICD and header files necessary to compile a native binary.

My intent is to continue developing a graphics render algorithm, but if I can get a working Android binary from g++ on a GNU toolchain, I would be happy to share generalized source code so that others can do the same with some simplicity.

Currently, I have success compiling a binary with shared libraries for GNU/Linux, but it does not detect the OpenCL devices on my system. I tried statically linking my application, but it refuses to link OpenCL statically.

The way I see it, there are two ways to solve my problem:

1) I assume Debian cannot see devices due to a driver issue, but I could be wrong, and I don't believe appropriate GNU drivers exist at this time. (Please correct me in a response if you know this to be false.) I have talked briefly with some of the folks from the Freedreno project, and it seems the OpenCL compiler is the biggest missing piece between the driver and the hardware. Unfortunately, I do not know if a working driver would even solve the issue in my case.

2) Compile binary with Android shared libraries. This may be most easily done with Eclipse, but I prefer Code::Blocks, so if the libraries could be linked in, then it may be trivial to change IDEs. I suppose it depends entirely on how the NDK handles compilation.

Option 2 is most likely the best course of action. I intend to publish my progress in milestones. Discuss.

XDA:DevDB Information
PLoW, Device Specific App for the Verizon HTC One (M8)

Contributors
Agenthex, agenthex

Version Information
Status: Testing

Created 2015-01-03
Last Updated 2015-01-03