AOSPA 3+ Building from source - Sony Ericsson Xperia Neo, Pro

Hey there!
I'm trying to build AOSPA for the Neo V from source because our devices have no support and halo is just awesome!
I'm following the guide here: http://forum.xda-developers.com/showthread.php?t=1863547, but I cannot find the device tree for the Neo V. Can anyone help me?
-> Now, Lets add the device specific trees:
Add your own device tree, kernel tree, hardware source tree, & vendor proprietaries tree in the local manifest.
For this, create a new file .repo/local_manifest.xml, & use something in similar terms:
For example, I'm using all corresponding trees for Samsung Galaxy S3 i9300 - International
Following is just an example, not what you should copy/paste. SEARCH & USE YOUR OWN DEVICE SPECIFIC TREES.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.1" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
</manifest>
CAUTION: Your device tree, kernel source, vendor props etc WILL be different. Search & find out where your device specific sources are located.
Click to expand...
Click to collapse

Use LegacyXperia sources add remote="github" revision="cm-10.2 or cm-10.1" to local_manifest... but i get error when compiling
Sent from my Xperia Neo using xda premium

I have same problem, who is can help me? pls.

Related

[Q] trouble when trying compile CM10 for nozomi

hi
I was trying to compile CM10 for the sony xperia s (nozomi) ... I sync the CM repo for the jb branch ,then I used this local manifest to get the device's code
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_FMRadio" path="packages/apps/FmRadio" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_sony_nozomi" path="device/sony/nozomi" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_sony_fuji-common" path="device/sony/fuji-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="jellybean" />
</manifest>
and sync it with repo sync ,every thing goes right ... but when I type the commande
Code:
brunch nozomi
it say device not found !!
my question is : am I using the right repositories ? is this local_manifest valide ? WHERE can I get the CM10 code sources for the nozomi device ?
thank you .

[Q] Building help cm12

guys im trying to build cm12 ??what do i have to write in "local_manifest.xml" before building for sirius???
Edit : After searching online i have come to this code.
Is it enough
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_sony.git" path="vendor/sony" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_device_sony_sirius" path="device/sony/sirius" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_kernel_sony_msm8974" path="kernel/sony/msm8974" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_qcom-common" path="device/sony/qcom-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_device_sony_fusion3-common" path="device/sony/fusion3-common" remote="github" revision="cm-12.0" />
<project name="CyanogenMod/android_bootable_recovery" path="bootable/recovery" remote="github" revision="cm-12.0"/>
</manifest>
and for Get prebuilt apps from cm is not working from cm guide
Get prebuilt apps
Add a comment to this section
Next,
$ cd ~/android/system/vendor/cm
then enter:
$ ./get-prebuilts
You won't see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.
Click to expand...
Click to collapse
EDIT:I was able to fix it and now its compling .....
EDIT FINAL:Thanks to XDA and GOOGLE i was able to get past the errors and now i compiled my first cm rom thanks everyone!!!!!!!!!!!!!!!
Hi! Do you can show how you solved this problem? For me, the same thing happens. I don't had much luck with research as you! lol

[Q] CM 12.1 ROMs

I am currently on the CM12.1 by 1619415. What is the difference between CM12.1 Roms by Clark44 and 1619415 ?
I use different repos mine have a few different commints and stuff like that. We also use different manifest stuff:
Mine (1619415):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- lg devices -->
<project name="CyanogenMod/android_device_lge_ls990" path="device/lge/ls990" remote="github" revision="cm-12.1" />
<!--lg kernels -->
<project name="CyanogenMod/android_kernel_lge_g3" path="kernel/lge/g3" remote="github" revision="cm-12.1" />
<!-- the muppets -->
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1" />
<!-- common -->
<project name="CyanogenMod/android_device_lge_g3-common" path="device/lge/g3-common" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-12.1" />
</manifest>
Clark44:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Hrubak/ls990-tools.git" path="ls990-tools" remote="github" revision="cm-12.1" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
<!-- common -->
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" />
<!-- lg -->
<project name="CyanogenMod/android_device_lge_g3-common" path="device/lge/g3-common" remote="github" />
<project name="CyanogenMod/android_kernel_lge_g3" path="kernel/lge/g3" remote="github" />
<project name="CyanogenMod/android_device_lge_ls990" path="device/lge/ls990" remote="github" />
</manifest>
:good: thanks for ur quick response
tareyaz said:
:good: thanks for ur quick response
Click to expand...
Click to collapse
No problem, glad I could help.

[Q] Do I need all devices mentioned in the manifest to compile android?

Hi, I'm building a ROM for my device and I was wondering if i needed to download all the devices mentioned in the manifest . So to compile lollipop (5.1.1), manifest would be here and inside the manifest (part of it), needs these devices
Code:
<project path="developers/docs" name="platform/developers/docs" />
<project path="developers/samples/android" name="platform/developers/samples/android" />
<project path="development" name="platform/development" groups="pdk-cw-fs" />
<project path="[COLOR="DeepSkyBlue"]device/asus/deb[/COLOR]" name="device/asus/deb" groups="device,flo" />
<project path="[COLOR="DeepSkyBlue"]device/asus/flo[/COLOR]" name="device/asus/flo" groups="device,flo" />
<project path="[COLOR="DeepSkyBlue"]"]device/asus/flo-kernel[/COLOR]" name="device/asus/flo-kernel" groups="device,flo" clone-depth="1" />
<project path="[COLOR="DeepSkyBlue"]device/asus/fugu[/COLOR]" name="device/asus/fugu" groups="device,fugu" />
<project path="device/asus/fugu-kernel" name="device/asus/fugu-kernel" groups="device,fugu" clone-depth="1" />
<project path="[COLOR="DeepSkyBlue"]device/asus/grouper[/COLOR]" name="device/asus/grouper" groups="device,grouper" />
<project path="device/asus/tilapia" name="device/asus/tilapia" groups="device,grouper" />
<project path="device/common" name="device/common" groups="pdk-cw-fs" />
So i was wondering if I must include all the devices or can i skip some to save disk space if I'm compiling for a device not mentioned in the manifest? (PS: I have a 1.5TB HDD)
NEVER touch default.xml
If you need additional repositories, there is a place to do this that is safe to the rest of the ROM structure...
.repo/local_manifests/roomservice.xml
Yes you need to leave the default xml intact, completely. But the roomservice.xml tells repo what devices to grab.
example for flo:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="arter97/android_device_asus_flo" path="device/asus/flo" remote="github" />
<project name="arter97/android_kernel_google_msm" path="kernel/google/msm" remote="github" />
<project name="TheMuppets/proprietary_vendor_asus" path="vendor/asus" remote="github" />
</manifest>

How do I solve the "nfc_enchanced.mk is missing" when building lineage-14.1?

How do I solve the "nfc_enchanced.mk is missing" when building lineage-14.1?
After trying the rom for zerofltexx with the name NexusXXXX in it (didn't boot past the Lineage setup guide) I decided to build cm-14.1 for it since https://github.com/LineageOS/android_device_samsung_zerofltexx/branches shows that the cm-14.1 branch exist (even though it's not updated).
I know that SM-G925F is not officially supported by either Cyanogenmod or Lineage, and my build fails to find nfc_enhanced.mk even though all the repos are correct in my local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_samsung_zerofltexx" path="device/samsung/zerofltexx" remote="github" />
<project name="LineageOS/android_device_samsung_zero-common" path="device/samsung/zero-common" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_exynos7420" path="hardware/samsung_slsi-cm/exynos7420" remote="github" />
<project name="LineageOS/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="LineageOS/android_kernel_samsung_exynos7420" path="kernel/samsung/exynos7420" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" />
</manifest>
How can I fix this so that cm-14.1 will build for this model?
I intend to make a working manifest to start porting to Sailfish OS.
I'm having the same problem. I have a similar local manifest as you do. I'm trying to port Halium. If you PM me we can try and help each other out.
I have found a working solution to build cm-14.1 for zerolte so I'll upload it to my mega repo soon.
This thread and it's issue can therefor be closed as fixed.

Categories

Resources