Showing posts with label Building. Show all posts
Showing posts with label Building. Show all posts

Friday, 5 August 2016

Having an issue building cyanogenmod 13.0



Hey guys,
I'm having an issue when building cyanogenmod 13.0. It gets to about 20 min into the build, then fails with this error:

Code:


ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:57: HSIC cannot be resolved to a type
make: *** [/home/edwin/phonelab/cm-shamu/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41


if anyone can point me in the right direction to get this straightened out I'd be appreciative.



Friday, 29 July 2016

Kernel building 101



I am considering making a very detailed guide on how to build a Samsung kernel. I'm talking about from A-Z....

But, I want to see who is interested in this first. If it's just 2 people who want to learn then it's a no go. The guide will take me hours to complete if not a couple of days...



Building and installing ROMs for HTC



Hi, please let me know if this should me moved to another section.

I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.

So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.

Thanks!



Monday, 18 July 2016

Building CM 13 CAF



Hello, I'm trying to build cm 13 caf rom myself (i have never done it before) and I'm following this guide. I have done everything to the step "download the source code" from https://github.com/CyanogenMod/android.git. Now I should "Prepare the device-specific code", but the guide is for hammerhead CM (non-caf) and, if I'm right, I should add some local_manifests but I have no idea of how to do this. (in fact if I type $ breakfast hammerheadcaf it starts downloading and then it says
** Don't have a product spec for: 'cm_hammerheadcaf'
** Do you have the right repo manifest?)
Can anyone explain it to me, please?



Help with building CM11 for my unsupported device.



Hi.
Im going to build CM 11 for my unsupported device LG Optimus Lte2. I need help with many steps as im a newbie.
1) First of all are the steps explained here all which i need to do or do i have to do some extra steps with my mobile's boot.img as my mobile is an unsupported mobile.

2) i am very confused with making the local manifest for downloading my mobile's device tree, kernel and vendor.
To be honest idk where to get these three files from. I found a link on github but i dont know to recognize a device tree so can someone please tell me if this is a device tree? https://github.com/zcop/android_devi..._d1lkt?files=1
Please also tell if i download the kernel and vendor file found in that link or any other?

I would be very delighted if someone can make the local manifest file for me using the above link or atleast explain to me in noob-friendly way about how to make it.

3) After that i have to make device tree compatible just by changing the name and some contents of some files as shown in this post. Am i right? But in the post it was shown for slim rom. I replace slim with cm, right?

After that i compile the rom.

Is that all?



Tuesday, 12 July 2016

Building AOSP for Manta



Dear friends,
I really need your help compiling PureNexus for Manta. Here is what I did:
1) set up the environment. I'm fairly sure that I did this right, on Ubuntu 16.04. I installed the required libs, openjdk7, android sdk, set the PATH, installed repo ofc.
2) created a folder for the project, did the repo init as specified in the github manifest:


Code:


repo init -u https://github.com/PureNexusProject/manifest.git -b mm2

Next, before doing a repo sync, I added a local manifest in .repo/local_manifests/local_manifest.xml, with the following content:


Code:


<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh" fetch="git://github.com/" />
<project path="kernel/samsung/manta" name="CyanogenMod/android_kernel_samsung_manta" remote="gh" revision="cm-13.0" />
<project path="device/samsung/manta" name="CyanogenMod/android_device_samsung_manta" remote="gh" revision="cm-13.0" />
<project path="vendor/samsung/manta" name="TheMuppets/proprietary_vendor_samsung" remote="gh" revision="cm-13.0" />
</manifest>


This is what I was able to find regarding manta. I added the device tree and kernel from Cyanogen's, and the vendor stuff from TheMuppets.
3) repo sync -j5 successfully downloaded everything, so it was build time!
4) As manta is not officially supported, I had to add and edit a few things here and there:
4.1) in vendor/nexus/products/AndroidProducts.mk I added this code:


Code:


ifeq (nexus_manta,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/nexus_manta.mk
endif


4.2) next I actually created the nexus_manta.mk. I copied and adapted the flounder one, it ended up like this:


Code:


#Include Pure Nexus tablet configuration
include vendor/nexus/configs/nexus_tablet.mk

# Inherit AOSP device configuration for flounder
$(call inherit-product, device/samsung/manta/aosp_manta.mk)

# Override AOSP build properties
PRODUCT_NAME := nexus_manta
PRODUCT_BRAND := Google
PRODUCT_DEVICE := manta
PRODUCT_MODEL := Nexus 10
PRODUCT_MANUFACTURER := Samsung

# Device Fingerprint
PRODUCT_BUILD_PROP_OVERRIDES += \
    PRODUCT_NAME=mantaray \
    BUILD_FINGERPRINT=google/mantaray/manta:6.0.1/MOB30P/2960889:user/release-keys \
    PRIVATE_BUILD_DESC="mantaray-user 6.0.1 MOB30P 2960889 release-keys"


4.3) finally i edited vendor/nexus/vendorsetup.sh to add this line at the end:


Code:


add_lunch_combo nexus_manta-user

5) After this I did:


Code:


. build/envsetup.sh
 lunch


picked number 31, nexus_manta-user, all seemed fine.

6) Time to build, "brunch manta". This won't end up well, the current issue is:


Code:


make: * No rule to make target '/home/android/android/system/out/target/product/manta/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by '/home/android/android/system/out/target/product/manta/obj/SHARED_LIBRARIES//import_includes'.  Stop.
make: * Waiting for unfinished jobs....


I must admit that manta and exynos 5 arent really popular, cause I often never found anything useful.
Anyway, I'm stuck there, but in the next post I'll add something that I tried to get started again, but didn't work out.

Thank you so much everyone,
TD



Monday, 11 July 2016

Wednesday, 6 July 2016

[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G3 [building]




This ROM is in building stage and not ready for daily use at the moment


CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community

First I would like to thank the following developers :
I used the orsprey and merling sources as a starting point and combined them with Motorola's stock kernel sources to base this cm 13.0 build on.

Before you start

THIS ROM IS TESTED ON XT1622 UNTESTED BY DEVELOPER ON ANY OTHER MOTO G4


Code:


*
 * Your warranty will be voided !
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 *



About the ROM

Current state of ROM : building

I hope to get finish a compile today. Build is past kernel compile, so I have good hopes.

What is Fixed
What is not working

Important
  • Everything.


Minor
Instructions

How to install CM13.0
  • If you don't have TWRP yet, get it from here : TWRP by bender1987 (Use the flash option, not just boot)

  • Download the ROM and the Gapps that are located below to your device

  • Reboot into TWRP by holding VOL UP + POWER + HOME on boot (Needs to be tested)

  • In case things go wrong make a backup

  • After the backup has completed return to home and select Wipe and then Advanced Wipe

  • Now ONLY tick Dalvik Cache, System, Data and Cache

  • After ticking those, Swipe below to wipe

  • Once the wipe has completed return to home and select the ROM

  • After you selected the ROM swipe below to install it

  • After the ROM has installed flash the Gapps

  • When all of this is done, reboot into system, wait, and enjoy CM12.1


How to ROOT
  • In CM 13.0 Enable the developer options

  • Select Root access

  • Select Apps Only

  • Done


Questions and bug reporting

The following questions will be ignored
  • Inappropriate questions

  • Forced orders, EX. : "PLS FIX!!!!!!"

  • ETA's

  • Often repeated questions usually by the same user

  • Requests that are out of CM's framework (Ex. Adding Samsung Apps)


How to report a bug/issue
  • Explain exactly what happens

  • Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)

  • If you can't mention a log, explain as precise as possible when, why and where it occurs!


Changelog

Code:


**********
06/07/2016 - First compile (I hope)
**********



Downloads

Latest CM 13.0 build :

All CM 13.0 releases can be found here :
All CM 13.0 beta releases can be found here :

Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)


Source

All our sources can be found here : https://github.com/Moto-G4


Screenshots








DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU



XDA:DevDB Information
CyanogenMod 13.0 for Moto G4, ROM for the Moto G4

Contributors
T_I
Source Code: https://github.com/Moto-G4

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod

Version Information
Status: Testing

Created 2016-07-06
Last Updated 2016-07-06



Tuesday, 5 July 2016

Building custom ROM based on stock kernel



I want to know that is it possible to have custom rom like cyanogenmod (5.1.1 or 6.0) running on stock kernel . Is anyone working on it ? I know tank0124 had built a aosp 5.0 rom but I (many users) want a custom ROM.



Thursday, 30 June 2016

[HELP]Kernel building



Showing me this when i type

Code:


make -j4


Quote:









scripts/kconfig/conf --silentoldconfig Kconfig
include/config/auto.conf:189:warning: symbol value 'elf32-i386' invalid for OUTPUT_FORMAT
include/config/auto.conf:271:warning: symbol value 'arch/x86/configs/i386_defconfig' invalid for ARCH_DEFCONFIG
include/config/auto.conf:617:warning: symbol value '-fcall-saved-ecx -fcall-saved-edx' invalid for ARCH_HWEIGHT_CFLAGS

*** Error during update of the configuration.

/home/pranav/android2/kernel/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 1
/home/pranav/android2/kernel/Makefile:496: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.




Trying to build it for Z3 MM Stock from Sony Copyright Archives



Help Building KeyGuard for Cyanogenmod 11?



I want to make a small change to KeyGuard so that the buttons are bigger. I'm trying to just get the source and build it, but I can't seem to do that. I've done a "repo" command and modified the manifest just to get the source for the project I need, but it doesn't seem to want to build.

The source of it on github: https://github.com/CyanogenMod/andro...kages/Keyguard

Trying to build it with "make KeyGuard" but I'm not entirely sure that is the right command, as it is in a subset of a package "frameworks base".