Today, I cleaned up the KFire-Android gits a bit.
I moved the prebuilt files from the device/amazon/otter project back into the ics branch of vendor/amazon/otter (which hasn't been used for quite some time). And this is somewhat required for the device to be merged into CyanogenMod sources anyway.
So make sure if you're building for the ics branch of Kindle Fire that you update your local_manifest.xml to something like this:
https://github.com/KFire-Android/android_local_manifest/blob/ics/local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- local projects -->
<project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" remote="github" revision="ics" />
<project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" remote="github" revision="4AI.5" />
<project path="vendor/amazon/otter" name="KFire-Android/android_vendor_amazon_otter" remote="github" revision="ics" />
</manifest>
Related
WARNING: I'm changing / restructuring the projects on KFire-Android so that all of the Kindle Fire devices can be supported (in the future).
This involves standardization and renaming of the projects across the board.
The new local_manifest.xml is updated here:
https://github.com/KFire-Android/android_local_manifest
Please give me a few days to iron out the otter build again to make sure everything is running correctly before posting that it isn't working
Right now the local_manifest looks something like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- local projects -->
<project path="kernel/amazon/otter-common" name="KFire-Android/kernel_omap_otter-common" revision="cm-10.1" />
<project path="kernel/amazon/bowser-common" name="KFire-Android/kernel_omap_bowser-common" revision="cm-10.1" />
<project path="device/amazon/omap4-common" name="KFire-Android/android_device_amazon_omap4-common" revision="cm-10.1-dev" />
<project path="device/amazon/otter" name="KFire-Android/android_device_amazon_otter" revision="cm-10.1" />
<project path="device/amazon/otter2" name="KFire-Android/android_device_amazon_otter2" revision="cm-10.1" />
<project path="device/amazon/tate" name="KFire-Android/android_device_amazon_tate" revision="cm-10.1" />
<project path="device/amazon/jem" name="KFire-Android/android_device_amazon_jem" revision="cm-10.1" />
</manifest>
As you can see there are new devices for: 2nd Gen KFire, HD 7 and HD8 all setup to use a common projects folder so that we don't duplicate across all of the projects.
Once again: there is some downtime while I sort out the otter/jem builds and then we can look at bringing up support for otter2 and tate (HD 7).
If repo sync failed for omap4-common, try setting revision to cm-10.1-dev
Updated
Hello mates
I build successfully Cyanogen Mod 10.1 for my ancora device as test, i got many warning during compilation without any stop, if got warning during compilation did mean can't boot or what depend from?
i use this repos as source:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="arco" fetch="https://github.com/arco" />
<remote name="ralisi" fetch="ssh://[email protected]/ralisi" />
<project path="device/samsung/ancora" name="android_device_samsung_ancora" remote="ralisi" revision="cm-10.1"/>
<project path="vendor/samsung/ancora" name="android_vendor_samsung_ancora" remote="arco" revision="cm-10.1"/>
<project path="kernel/samsung/samsung-kernel-msm7x30" name="samsung-kernel-msm7x30" remote="arco" revision="cm-10.1"/>
</manifest>
Click to expand...
Click to collapse
Any one can help me, thanks
First time building CyanogenMod from source and I've run into a roadblock.
I am at the point where I have CM12 repo synced and when i run
Code:
breakfast d2spr
I get the error:
** Don't have a product spec for: 'cm_d2spr'
** Do you have the right repo manifest?
so then I run
Code:
breakfast
it returns a list of devices and d2spr is not in the list.
So I'm kinda stuck here. how do I get the vendor files for d2spr?
Thanks!
I had to add a roomservice.xml to the local_manifests folder (under .repo in your main directory), to get it up and running:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Hrubak/d2spr-tools.git" path="d2spr-tools" remote="github" revision="cm-12.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-12.0" />
<project name="CyanogenMod/android_device_samsung_d2spr" path="device/samsung/d2spr" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
and then run
Code:
d2spr-tools/apply.sh
Be advised that when I ran the shell script I got a conflict with one of the files. You can either attempt to correct the error or run "git cherry-pick --abort" in the conflicting directory.
and then finally
Code:
. build/envsetup.sh && brunch d2spr
will compile it.
got these instructions from here:
github.com/Hrubak/d2spr-tools
Hello I kinda hope I'm posting this in the right place. 'cause I kinda need some advice as to why I'm unable to build my mondrianlte with a working radio stack.
So breaking this down I'm on Mint Linux 17.3 (Rosa), I have all the ensured that I have my build environment set up etc.. build-essential, openjdk7 etc...
I've followed the CyanogenMod mondrianwifi wiki for the most part.
I think I had managed to crack the local_manifests (tabpro.xml) with some trial and, error.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest>
<remote name="git" fetch="https://github.com/" />
<project path="hardware/samsung" name="CyanogenMod/android_hardware_samsung" repo="github" revision="cm-13.0" />
<project path="kernel/samsung/mondrianwifi" name="CyanogenMod/android_kernel_samsung_mondrianwifi" remote="github" revision="cm-13.0" />
<project path="vendor/samsung" name="crpalmer/proprietary_vendor_samsung" remote="git" revision="cm-13.0" />
<project path="device/samsung/mondrianlte" name="crpalmer/android_device_samsung_mondrianlte" remote="git" revision="cm-13.0" />
<project path="device/samsung/tabpro-common" name="crpalmer/android_device_samsung_tabpro-common" remote="git" revision="cm-13.0" />
<project path="device/samsung/msm8974-common" name="CyanogenMod/android_device_samsung_msm8974-common" remote="github" revision="cm-13.0" />
<project path="device/samsung/qcom-common" name="CyanogenMod/android_device_samsung_qcom-common" remote="github" revision="cm-13.0" />
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-13.0" />
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" repo="github" revision="cm-13.0" />
</manifest>
One repo sync and, about 90 Minutes later...
$cd ../device/samsung/mondrianlte
$./extract-files.sh
Which when using a prior version of CM-13.0 manages to finish without any visible errors extracted Files could be found either in ../vendor/samsung/tabpro-common, or ../vendor/samsung/mondrianlte.
After that I run:
$source build/envsetup.sh
$breakfast mondrianlte
brunch mondrianlte.
The build (for me...), takes about ~5H 20m to complete, again with out any errors.
I can even boot it just fine, but alas with out any Cellular Voice & Data.
I've already tryed to swap out the Kernel, with what I would have assumes was a working version.
I've tried to reflash both the modem.bin & non-hlos.bin
I've even tried use EFS Backup & Partition Backup (to hopefully push what was a working /efs partition to my new build.
My Tab Pro 8.4 however wasn't having any of that.
Could it be that I have to somehow also mod the mondrianwifi kernel to become fully compatible with my lte version, or is it something else that I'm missing.
Ok having took a clue from another picassolte user, I tried rebuilding CM-12.1 from source again. The last time I had tried it I wasn't able to get off the bootloader screen (Where it says Samsung Tab|Pro T325...)
So that was about +7h of my life wasted back then. I guess I could chalk it down to not having a proper local_manifests *xml set up.
So in my epic adventure to try and get myself up to the May Security Updates LMY49J I decided that I had to give it another try.
This was the local_manifests *.xml that I finally used to install CM-12.1 on my T325
Code:
<?xml version "1.0" encoding="utf-8"?>
<manifest>
<remote name="git" fetch="https://github.com/" />
<project path="hardware/samsung" name="CyanogenMod/android_hardware_samsung" repo="github" />
<project path="kernel/samsung/mondrianwifi" name="CyanogenMod/android_kernel_samsung_mondrianwifi" remote="github" />
<project path="vendor/samsung" name="crpalmer/proprietary_vendor_samsung" remote="git"
<project path="device/samsung/mondrianlte" name="crpalmer/android_device_samsung_mondriante" remote="git" />
<project path="device/samsung/tabpro-common" name="crpalmer/android_device_samsung_tabpro-common" remote="git" />
<project path=device/samsung/msm8974-comon" name="CyanogenMod/android_device_samsung_msm8974-common" remote="github" />
<project path="device/samsung/qcom-common" name="CyanogenMod/android_device_samsung_qcom-common" remote="github" />
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="github" />
</manifest>
Again unlike CM-13.0 it took about +2h's longer to compile then CM-13.0 (5h 20m) to CM-12.1's (7h 30m).
But, unlike CM-13.0 I now have a fully working CM-12.1 build with fully working voice and Data.
Could this be because I was just trying to pull the cm-13.0 trees, instead of the master branches (like above?)
I think I might retry using the same manifest once more to build CM-13, just to be sure. But, I'm starting to think something might have gone a bit pare shaped and that's why we haven't been getting any new-ish nightlies from crpalmer. In which case I'd be just as lost... If not more so. Though I do hope to be able to dig down a bit deeper one of these days.
Hello,
I'm trying to compile android-6.0.1_r74 for my HTC One M8, but the device tree from CyanogenMod doesn't even get recognized by the AOSP build environment.
I only get:
Code:
[email protected]:~/android-6.0.1_r74$ . build/envsetup.sh
including device/asus/deb/vendorsetup.sh
including device/asus/flo/vendorsetup.sh
including device/asus/fugu/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/htc/flounder/vendorsetup.sh
including device/huawei/angler/vendorsetup.sh
including device/lge/bullhead/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/moto/shamu/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android-6.0.1_r74$ choosecombo
Build type choices are:
1. release
2. debug
Which would you like? [1] 1
Which product would you like? [full] cm_m8
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_m8". Stop.
** Not a valid product: cm_m8
Which product would you like? [full] m8
build/core/product_config.mk:222: *** Can not locate config makefile for product "m8". Stop.
** Not a valid product: m8
Which product would you like? [full] cm
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm". Stop.
** Not a valid product: cm
Which product would you like? [full] ^C
[email protected]:~/android-6.0.1_r74$
Does anybody
know of a device tree for the M8 that works with AOSP?
have an idea what has to be done to get the CM-device tree to work with AOSP?
know where I could find resources/documentation that could help solve this problem?
know of a person or chat group/irc/etc. that doesn't just ignore you completely?
Here is my manifest file. I already tried different configurations, but none of them worked:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/" />
<project name="SlimRoms/device_htc_m8" path="device/htc/m8" remote="github" revision="mm6.0" />
<project name="SlimRoms/device_htc_m8-common" path="device/htc/m8-common" remote="github" revision="mm6.0" />
<project name="CyanogenMod/android_device_htc_msm8974-common" path="device/htc/msm8974-common" remote="github" revision="cm-13.0" />
<project name="SlimRoms/kernel_htc_msm8974" path="kernel/htc/msm8974" remote="github" revision="mm6.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_vendor_cm" path="vendor/cm" remote="github" revision="cm-13.0" />
</manifest>
<!-- somewehre from github
<manifest>
<remote name="github" fetch="https://github.com/" />
<project name="CyanogenMod/android_device_htc_m8" path="device/htc/m8" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_htc_m8-common" path="device/htc/m8-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_htc_msm8974-common" path="device/htc/msm8974-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_kernel_htc_msm8974" path="kernel/htc/msm8974" 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_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-13.0" />
</manifest>-->
<!-- original
<manifest>
<remote name="github" fetch="https://github.com/" />
<project name="CyanogenMod/android_device_htc_m8" path="device/htc/m8" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_htc_m8-common" path="device/htc/m8-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_htc_msm8974-common" path="device/htc/msm8974-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_kernel_htc_msm8974" path="kernel/htc/msm8974" 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_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" revision="cm-13.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_vendor_cm" path="vendor/cm" remote="github" revision="cm-13.0" />
</manifest>-->