Develop Bugs

[Q] local_manifest.xml

i am trying to compile cm10.1...where can i find the local_manfest.xml for my epic 4g touch

You need to make a local_manifest.xml file.
Sent from my SPH-D710 using xda premium

Mattix724 said:
You need to make a local_manifest.xml file.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I know I need to make one...and I k ow that each ROM and each device has a different set of specs it uses for the local_manifest.xml and I have searched everywhere...I can't find any details on what to put in it for my phone

Jump on IRC at irc.freenode.net and join #JB-DEV-E4GT
They'll help you out after giving you a hard time for a few... just don't take them serious and get butt hurt.
Sent from my SPH-D710 using xda premium

Mattix724 said:
Jump on IRC at irc.freenode.net and join #JB-DEV-E4GT
They'll help you out after giving you a hard time for a few... just don't take them serious and get butt hurt.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I tried going there...no one ever answers

Jump on now. I'm online.
Sent from my Slim E4GT using xda premium

For anyone else that might want to build AOSP ROM's from source, here is the local_manifest that I have which I just gave to the OP of this question.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- local projects -->
<project name="dastin1015/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" revision="cm-10.1" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" revision="cm-10.1" remote="github" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" revision="cm-10.1" remote="github" />
<project name="Evervolv/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" revision="jellybean" remote="github" />
<project name="EpicCM/d710tools" path="d710tools" revision="mr1-staging" remote="github" />
<project name="Evervolv/android_device_samsung_d710" path="device/samsung/d710" revision="jellybean" remote="github" />
<project name="dastin1015/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-10.1" remote="github" />
</manifest>
Please, if anyone else knows more than I do about building from source. Comment about whether or not this is a good local_manifest.xml file to be using for building 4.2.2 or CM10.1 based ROMs from source for the E4GT
There are also a few other resources that will help with building from source that can be found here...
http://forum.xda-developers.com/showthread.php?t=1762641
https://github.com/EpicCM/d710tools/tree/mr1-staging
https://github.com/chris41g/cyanogenmod_epic4gtouch
That last link is out of date, it was meant for building CM9 from source.
Anyways. I hope that I've helped at least 1 person build an AOSP based ROM.

Mattix724 said:
For anyone else that might want to build AOSP ROM's from source, here is the local_manifest that I have which I just gave to the OP of this question.
Code:
Please, if anyone else knows more than I do about building from source. Comment about whether or not this is a good local_manifest.xml file to be using for building 4.2.2 or CM10.1 based ROMs from source for the E4GT
There are also a few other resources that will help with building from source that can be found here...
http://forum.xda-developers.com/showthread.php?t=1762641
https://github.com/EpicCM/d710tools/tree/mr1-staging
https://github.com/chris41g/cyanogenmod_epic4gtouch
That last link is out of date, it was meant for building CM9 from source.
Anyways. I hope that I've helped at least 1 person build an AOSP based ROM.
Click to expand...
Click to collapse
Don't mix and match trees unless you know what you're doing. If you're using my trees use all of them. The Evervolv trees don't work with my other trees as they have been modified specifically for Evervolv. You don't need the d710 tools and chris41g's trees are out of date. I'm the author of that tutorial so if you have questions feel free to ask.
私のEVO 4G LTEから送信される。

dastin1015 said:
Don't mix and match trees unless you know what you're doing. If you're using my trees use all of them. The Evervolv trees don't work with my other trees as they have been modified specifically for Evervolv. You don't need the d710 tools and chris41g's trees are out of date. I'm the author of that tutorial so if you have questions feel free to ask.
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
I was looking at your git and the only ones I found are what I put in that manifest. I appreciate your feedback and will definitely learn from what you have to say.
I was just trying to help this guy that asked the question the best that I could with what little knowledge I have.
Sent from my Slim E4GT using xda premium

Mattix724 said:
I was looking at your git and the only ones I found are what I put in that manifest. I appreciate your feedback and will definitely learn from what you have to say.
I was just trying to help this guy that asked the question the best that I could with what little knowledge I have.
Sent from my Slim E4GT using xda premium
Click to expand...
Click to collapse
These will get it working properly. You just need to manually create a vendorsetup.sh in the device tree, or manually add in the lunch option in vendor/cm.
Code:
add_lunch_combo cm_d710-userdebug
d710: https://github.com/dastin1015/android_device_samsung_d710
gs2-common: https://github.com/dastin1015/android_device_samsung_galaxys2-common
kernel: https://github.com/dastin1015/android_kernel_samsung_smdk4210
vendor: https://github.com/dastin1015/proprietary_vendor_samsung

Since dastin gave me some constructive criticism, I went ahead and made some edits to the local_manifest.xml file and this is what I have and what I will try using later today for a build.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- local projects -->
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" revision="cm-10.1" remote="github" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" revision="cm-10.1" remote="github" />
<project name="dastin1015/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" revision="cm-10.1" remote="github" />
<project name="dastin1015/android_device_samsung_d710" path="device/samsung/d710" revision="cm-10.1" remote="github" />
<project name="dastin1015/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" revision="cm-10.1" remote="github" />
<project name="dastin1015/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-10.1" remote="github" />
</manifest>

[ROM][6.0.1][K920][kingdom_row]AOKP for Lenovo Vibe Z2 Pro ROW

Unofficial build of AOKP for international Lenovo Vibe Z2 Pro
DOWNLOAD
Google+ community
known bugs:
- FM radio not working
- restart doesn't work
- echo - try to install latest stock ROM then install CM-13.0 to fix
...
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="aokp-mm" />
<project name="frantisheq/android_kernel_lenovo_msm8974" path="kernel/lenovo/msm8974" remote="github" revision="cm-13.0" />
<project name="frantisheq/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
</manifest>
Click to expand...
Click to collapse

fixed download https://www.androidfilehost.com/?fid=24438995911973785

Hi! Thanks for developing roms for this great phone. I'm before flashing your rom and i have few questions. Did HDR works now ? snapit, camera app from stock will work on this rom ?

same base as CM, same bugs so no HDR

new build https://basketbuild.com/filedl/devs...kingdom_row_mm_unofficial_2016-03-24_1726.zip

Thank u bro for developing the rom

1-)When we are talking on the phone, it's makes an echo so you hear your, voice again.I don't hear any echo own echnly you hear.
2-)This problem occurs in all softwares except euphoria.What is wrong with other softwares .What can I do for that problem.To solve this problem in my mobile phone,could you give me any different modem software?

new build https://basketbuild.com/filedl/devs...kingdom_row_mm_unofficial_2016-03-30_1218.zip

[ROM][6.0.1][K920][kingdom_row]AICP for Lenovo Vibe Z2 Pro ROW

Unofficial build of AICP for international Lenovo Vibe Z2 Pro
DOWNLOAD
Google+ community
known bugs:
- FM radio not working
- restart doesn't work
- echo - try to install latest stock ROM then install CM-13.0 to fix
...
kernel source: https://github.com/frantisheq/android_kernel_lenovo_msm8974
local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="frantisheq/android_device_lenovo_kingdom_row" path="device/lenovo/kingdom_row" remote="github" revision="aicp-mm6.0" />
<project name="frantisheq/android_kernel_lenovo_msm8974" path="kernel/lenovo/msm8974" remote="github" revision="cm-13.0" />
<project name="frantisheq/proprietary_vendor_lenovo" path="vendor/lenovo" remote="github" revision="cm-13.0" />
</manifest>
Click to expand...
Click to collapse

I can't download. Receiving error OOPS!
no mirrors found.

fixed download https://www.androidfilehost.com/?fid=24438995911973743

new build, updated DOWNLOAD link in first post

Thank u bro

1-)When we are talking on the phone, it's makes an echo so you hear your, voice again.I don't hear any echo own echnly you hear.
2-)This problem occurs in all softwares except euphoria.What is wrong with other softwares .What can I do for that problem.To solve this problem in my mobile phone,could you give me any different modem software?

new build https://basketbuild.com/filedl/devs...p_kingdom_row_mm-11.0-UNOFFICIAL-20160330.zip

new build based on 7.1.1 ready to go http://frantisheq.synology.me/android/kingdom/aicp

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

Is Anyone Building Other ROMs Not Posted?

The choice of ROMs has slowly been dipping since Lollipop as more and more ROMs no longer have Official support for Galaxy Nexus.
At the same time, newer ROMs are popping up for other devices and they look quite interesting.
Ones I have been looking at are Dirty Unicorns, Screw'd, AICP and OctOS.
However, building an unofficial ROM has been troublesome for me.
I have been focusing on Marshmallow since there are still some bugs with AOSP/Unlegacy nougat.
My main issue is that it isn't clear which gnex repos I should be adding after I have sync'd the main ROM source.
There are lots of different forks around and it isn't clear which one to choose.
Which repos do I need to add for AOSP based ROMs?
What is the recommended way to add them?
Does it make any difference if the ROM uses Cyanogenmod or Omnirom as a base instead of AOSP?
Has anyone built these (or any other ROMs) privately and would like to share all the commands necessary for a successful build?

Take a look at this backstage development
https://www.androidfilehost.com/?a=show&w=files&flid=18435
SAOSP has more nougat builds,
Then Dirty Unicorn and Pure Nexus.....
Thank him -> @voidz777

My present time is 5 o'clock in the morning.
In other words, it is before going to work.
So I can not write much.lol
Hi, opticyclic
I did not ignore you.
I have been working forever since I got your email.
Because I can not tell the right way unless I port it before telling you.
I was doing screwed work for a while.
https://github.com/voidz777-crewd
But I can not boot it.
Probably, I think it is due to more optimizing.
I got tired because I got tired.lol
After a while, delete https: //github.com/voidz777-crewd.
It is another addition.
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="pdk,linux,arm" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" revision="aosp-6.0" />
<project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="unlegacy" revision="stable" groups="omap4" />
<project path="vendor/ti" name="proprietary_vendor_ti" remote="unlegacy" revision="stable" />
<project path="vendor/widevine" name="proprietary_vendor_widevine" remote="unlegacy" revision="aosp-6.0" />
I'm sorry, my English is not good.
If I could write in Japanese here, I can tell you a little more about the way of port.
There is no time now.
PS.Ah, oct could be pored immediately.

@voidz777 No apologies necessary!
Your posts about different ROMs on Google plus are actually what prompted me to try to build some myself!
Thanks for the info.
I'll post back after trying out a few different ROMs and give an update in the OP on any successes.

I tried to build octos with
Code:
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm
and this in .repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<project remote="unlegacy" path="device/samsung/tuna" name="android_device_samsung_tuna" />
<project remote="unlegacy" path="hardware/ti/omap4" name="android_hardware_ti_omap4" revision="stable" groups="omap4" />
<project remote="unlegacy" path="vendor/samsung" name="proprietary_vendor_samsung" />
<project remote="unlegacy" path="vendor/ti" name="proprietary_vendor_ti" revision="stable" />
<project remote="unlegacy" path="vendor/widevine" name="proprietary_vendor_widevine" />
</manifest>
However, they are doing something funny with the build/envsetup.sh and it isn't picking up the vendorsetup.sh so the device isn't picked up by brunch/breakfast etc.
As far as I can tell, there is no specific info on GitHub, GooglePlus or any posts on xda on how to add a new device for their ROM.
On to AICP....

Check vendor / rom - name or device / other - device /.
If oct it will be platform_vendor_to.
Let's see the commit log.
Is there any device added?
For example, let's look for mako.
https://github.com/Team-OctOS/platform_vendor_to/commit/d30dd90c018ca521d458c939a2c56ffc5a97741d
Mako has been added by this commitment.
Create the tuna file in the same way.
Well, will you continue your way of thinking? Or do you want to know the answer quickly?

Thanks for the tip.
If they are going to use a different build structure, it should really be on the README or a FAQ somewhere.
It's bad programming practice in general to expect people to search through commit logs just to try to work out how a project works.
So instead of just adding a local manifest, OctOs requires the following:
to.dependencies (same as local manifest but in JSON instead of XML)
to.mk - same as the device board (aosp_tuna.mk)
extra line in vendorsetup_community.sh - it ignores your vendorsetup.sh
Then do lunch aosp_tuna-userdebug.
Then do mka bacon
However, the first time I did this, it overwrote my .repo/local_manifest/roomsevice.xml with a generated version that contained octos revisions instead of the aosp revisions, which obviously failed as there is no octos revision in unlegacy!
Weirdly, after reverting the roomservice.xml and running lunch again didn't overwrite it.
AICP was more straightforward.
I just added the roomservice.xml and ran lunch aosp_tuna-userdebug and mka bacon.
However, both failed with the following error:
Code:
build/core/base_rules.mk:157: *** packages/apps/Nfc//nxp/jni: MODULE.TARGET.SHARED_LIBRARIES.libnfc_jni already defined by packages/apps/Nfc/nxp/jni/. Stop.
What is weird about this is that it is the same module defining the library, however, the first one has a double slash in the path!

Probably revert this commit
https://github.com/Team-OctOS/platf...mmit/1b8ed2250fc89adce8e0b0dbb6c5ca4d82705ccb
Sent from my Nexus 5

Good catch.
I wonder how that didn't cause a build failure on the build servers.
The next failure in both was:
Code:
build/core/base_rules.mk:157: *** hardware/invensense/60xx/mlsdk: MODULE.TARGET.SHARED_LIBRARIES.libmlplatform already defined by device/samsung/tuna/libsensors. Stop.
That was resolved by removing the Cyanaogenmod project and using the unlegacy one instead, so the local manifest now looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<remove-project name="CyanogenMod/android_hardware_invensense" />
<project name="android_device_samsung_tuna" path="device/samsung/tuna" remote="unlegacy" />
<project name="android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="unlegacy" revision="stable"/>
<project groups="omap4" name="android_hardware_ti_omap4" path="hardware/ti/omap4" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" />
<project name="proprietary_vendor_ti" path="vendor/ti" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="unlegacy" />
</manifest>
I chose revision="stable" for android_kernel_samsung_tuna", although there is also "aosp-6.0-sound" but I just wanted any kernel to allow me to compile at this point.
The next error (both ROMs) is this (maven 3 is installed)
Code:
make: *** No rule to make target '/home/buildbot/android/aicp/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/aar/classes.jar', needed by '/home/buildbot/android/aicp/out/target/common/obj/APPS/messaging_intermediates/AndroidManifest.xml'. Stop.
This relates to this dir https://github.com/AICP/vendor_aicp/
Interestingly, ambientsdk dir existed all thoughout the n7.0 branch and only got removed recently in the n7.1 branch
https://github.com/AICP/vendor_aicp/commit/8f150895f8b361480ac91ef0ace941e06e9f548e
I also don't see any maven messages in the build log and com.cyngn.ambient/ambientsdk/ is not in my ~/.m2/repository which makes me wonder if I am missing a project.
The only similar errors I see online are if people don't have maven installed.
I tried removing the files like the 7.1 branch even though it felt wrong,
Code:
rm vendor/aicp/overlay/common/frameworks/base/core/res/res/values/cm_arrays.xml
rm -rf vendor/aicp/ambientsdk
Not surprisingly, it seems like something else is calling it as the same error pops up 25 mins into build.
repo grep ambientsdk shows ContactsCommon, Trebuchet and ContactsProvider using it in the Android.mk files and grepping for ambient shows lot of java imports.
So now I am stuck again.
To be honest, I wasn't expecting to have to deal with errors like this as they don't seem to be device specific.
i.e. there are builds for other devices so how did they compile?

i have posted nethunter rom here: https://forum.xda-developers.com/galaxy-nexus/development/rom-kali-linux-net-hunter-t3676472

[ROM][9.0][UNOFFICIAL] [G800H] LineageOS 16.0 [28-03-2022]

Following this post from November 2020 ([ROM][9.0][UNOFFICIAL] [G800H] LineageOS 16.0), I made an update of the LineageOS 16.0 ROM for Samsung S5 mini Duos (kmini3g). I used the same sources referenced in the post mentioned above. I did not test very much, but since I did not change anything, it should hopefully do as good as the previous version did.
Find the download here. Please use at your own risk.
Install as usual using adb push and TWRP (please follow instructions in the post mentioned above).
All credits go to the initial creators of the LineageOS 16 port! Nice job!
Here is my local manifest (for the curious):
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com/LineageOS" name="los" revision="refs/heads/lineage-16.0" />
<remote fetch="https://github.com/S3NEO" name="s3neo" revision="refs/heads/lineage-16.0" />
<!-- Device -->
<project name="android_device_samsung_kmini3g" path="device/samsung/kmini3g" remote="s3neo" />
<project name="android_device_samsung_msm8226-common" path="device/samsung/msm8226-common" remote="los" />
<project name="android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="los" />
<!-- Kernel -->
<project name="android_kernel_samsung_msm8226" path="kernel/samsung/msm8226" remote="los" />
<!-- Vendor -->
<project name="android_vendor_samsung_kmini3g" path="vendor/samsung/kmini3g" remote="s3neo" />
<project name="android_vendor_samsung_msm8226-common" path="vendor/samsung/msm8226-common" remote="s3neo" />
<!-- Hardware -->
<project name="android_hardware_samsung" path="hardware/samsung" remote="los" />
<project name="android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="los"/>
</manifest>
Click to expand...
Click to collapse
Kernel sources thus are to be found at:
https://github.com/LineageOS/android_kernel_samsung_msm8226

For the records: At first I incidentally copied the old build from 2020 to androidfilehost. Now the new build is linked above. Sorry for any inconvenience...

The auto rotation is not working for me. Does it work for you? If it does I think I will reinstall to see if it resolves.

As I wrote: I did not test much. Screen rotation does not work for me either... You may want to try the earlier 2020 version mentioned in my initial post, of which it is said to be working?

HerrElling said:
As I wrote: I did not test much. Screen rotation does not work for me either... You may want to try the earlier 2020 version mentioned in my initial post, of which it is said to be working?
Click to expand...
Click to collapse
Yeah, I did that and everything is working now. Thanks for answering.

This is my main phone, I really like it. Please make CrDroid Android 9 or 11

And..auto-rotate and gps not work(