[Q] appropriate roomservice.xml for cm12 and hlte?

linedot

Member
Dec 14, 2013
16
6
0
Hi,

I tried building cm12 for my note 3, but the resulting rom won't boot. I figured it might have been some modifications I made, so I tried with just the sources from git. Didn't work either. I looked at temaseks unofficial build and it boots without any problems - they seem to use a different kernel, so I tried that, too, but booting was stuck on the boot animation again. So I thought maybe my whole roomservice.xml is wrong:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
	<project name="CyanogenMod/android_device_samsung_hlte" path="device/samsung/hlte" remote="github" revision="cm-11.0"/>
	<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github"/>
	<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github"/>
	<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github"/>
	<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github"/>
	<!--<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github"/>-->
	<project name="temasek/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" revision="staging-v1"/>
 	<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
	<project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display-caf-new" remote="github" revision="cm-11.0"/>
	<project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media-caf-new" remote="github" revision="cm-11.0"/>
	<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
	<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
</manifest>
Also - I don't know how to properly debug boot failures - is there some sort of log somewhere that persists and can be seen/saved from recovery?