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>
Related
Since I cant post on the development board I will post this here
The addition to the local_manifest file is missing the a line you need to add
Code:
<project name="TeamFahQ/msm8660-common_lz_kernel" path="kernel/samsung/msm8660-common" remote="github" revision="jellybean" />
<project name="TeamFahQ/vendor_lz-kernel" path="vendor/lz-kernel" remote="github" revision="master" />
notzippy said:
Since I cant post on the development board I will post this here
The addition to the local_manifest file is missing the a line you need to add
Code:
<remote fetch="https://github.com/TeamFahQ" name="LZkernel" />
<project name="vendor_lz-msm8660-common.git" path="vendor/lz-kernel" remote="LZkernel" revision="master" />
<project name="/lge-kernel-iproj" path="nitro/iproj" remote="LZkernel" revision="android-msm-3.0-jb" />
Click to expand...
Click to collapse
Wat?
Sent from my LG-P930 using xda premium
lordcheeto03 said:
Wat?
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
In reference to message http://forum.xda-developers.com/showpost.php?p=34554462&postcount=3 I found the local_manifest changes incorrect and posted the updated ones here.
notzippy said:
In reference to message http://forum.xda-developers.com/showpost.php?p=34554462&postcount=3 I found the local_manifest changes incorrect and posted the updated ones here.
Click to expand...
Click to collapse
Ohh, i got ya.
Sent from my LG-P930 using xda premium
Hey everyone,
Some of you may remember simonsimons34 and I from awhile back. We both moved on to the HTC Primoc (One V), but we want to bring a new custom ROM to the Wildfire S community. Now that you all have CM10 and Jellybean 4.1, we can do this. I just need to know one thing from you:
Which kernel should I use for Wildfire S 4.1+ development? The 2.6 or 3.0?
Additionally, I will need a few testers who can pull a logcat and run some "adb shell" and fastboot commands. I'll probably need two or three per device. If you're marvelc, S-OFF is preferred. I no longer own a fully-workign marvelc and I never owned the marvel.
If you'd like to help out, post below. I will bring more details as time goes on.
this is the kernel from the latest build, I'm hoping that helps in some way. I'll try and get into contact with icu, he can probably help out way more.
Sent from my Marvelc using xda app-developers app
demi_fiend said:
this is the kernel from the latest build, I'm hoping that helps in some way. I'll try and get into contact with icu, he can probably help out way more.
Sent from my Marvelc using xda app-developers app
Click to expand...
Click to collapse
Thanks so much! That answers tons of questions. I do have one more:
Are modpunk's sources at http://git.cryptomilk.org still up-to-date or are there other sources that should be used now?
HAPPYNESS!!!!!!!!!!!
heck yea ill help lol and i got a new miui port for us to use.... that boots lol
Very cool.! i Want it.
kalaker said:
Thanks so much! That answers tons of questions. I do have one more:
Are modpunk's sources at http://git.cryptomilk.org still up-to-date or are there other sources that should be used now?
Click to expand...
Click to collapse
I believe those are the source's pi1vo has used. I'm not sure if they have the omx patches for working video in them or what's what. I'll pm him and try to get more information.
Sent from my Marvelc using xda app-developers app
demi_fiend said:
I believe those are the source's pi1vo has used. I'm not sure if they have the omx patches for working video in them or what's what. I'll pm him and try to get more information.
Sent from my Marvelc using xda app-developers app
Click to expand...
Click to collapse
Sweet. Thanks! As soon as I get info of what sources to use, I should be able to get it built pretty quickly.
Again, I'll need two testers per device (I don't have my Wildfire S anymore), but if anyone would like to help, let me know.
I just got word from oliver that those are indeed the up to date
Sent from my Marvelc using xda premium
demi_fiend said:
I just got word from oliver that those are indeed the up to date
Sent from my Marvelc using xda premium
Click to expand...
Click to collapse
Thank you so much! I will work on a build tonight and hopefully have it done soon. NO ETAs
no problem, thanks for trying this build, good luck going forward and I hope it works. ETAs only drive everyone crazy anyway haha
Sent from my Marvelc
To build CM10 for marvelc you'll need this
local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" revision="refs/jellybean" />
<project name="po1vo/android_device_htc_marvelc.git" path="device/htc/marvelc" revision="jellybean" />
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="refs/heads/gingerbread" />
<project name="eoghan2t9/HTC_Wildfire_S_Android4.0_Kernel" path="kernel/htc/msm7227" revision="master" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean" />
<project name="WinSuk/android_hardware_qcom_media" path="hardware/qcom/media" revision="jellybean" />
<project name="projects/marvel/android_device_htc_msm7x27-recovery.git" path="device/htc/msm7x27-recovery" remote="cryptomilk" />
<project name="projects/marvel/android_device_htc_msm7x27-common.git" path="device/htc/msm7x27-common" remote="cryptomilk" />
<project name="MarvellousAndroid/android_device_htc_marvel-common" path="device/htc/marvel-common" revision="jellybean" />
<project name="projects/marvel/android_vendor_qcom_msm7x27.git" path="vendor/qcom/msm7x27" remote="cryptomilk" />
<project name="projects/marvel/android_vendor_htc_marvelc.git" path="vendor/htc/marvelc" remote="cryptomilk" />
<project name="WinSuk/android_frameworks_av" path="frameworks/av" revision="jellybean" />
<project name="WinSuk/android_frameworks_native" path="frameworks/native" revision="jellybean" />
<project name="WinSuk/android_packages_apps_Gallery2" path="packages/apps/Gallery2" revision="jellybean" />
<project name="WinSuk/android_packages_apps_LegacyCamera" path="packages/apps/LegacyCamera" revision="jellybean" />
</manifest>
I have the feeling black bean is going to be replaced soon lol
Sent from my HTC-PG762 using Tapatalk 2
Any news?
Sent from my Marvelc using Tapatalk 2
OK then...
Sent from my Marvelc using Tapatalk 2
icu64 said:
OK then...
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that manifest. Some things came up suddenly and I wasn't able to get this done as quickly as I had hoped. It'll be done very soon.
po1vo said:
To build CM10 for marvelc you'll need this
local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" revision="refs/jellybean" />
<project name="po1vo/android_device_htc_marvelc.git" path="device/htc/marvelc" revision="jellybean" />
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="refs/heads/gingerbread" />
<project name="eoghan2t9/HTC_Wildfire_S_Android4.0_Kernel" path="kernel/htc/msm7227" revision="master" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean" />
<project name="WinSuk/android_hardware_qcom_media" path="hardware/qcom/media" revision="jellybean" />
<project name="projects/marvel/android_device_htc_msm7x27-recovery.git" path="device/htc/msm7x27-recovery" remote="cryptomilk" />
<project name="projects/marvel/android_device_htc_msm7x27-common.git" path="device/htc/msm7x27-common" remote="cryptomilk" />
<project name="MarvellousAndroid/android_device_htc_marvel-common" path="device/htc/marvel-common" revision="jellybean" />
<project name="projects/marvel/android_vendor_qcom_msm7x27.git" path="vendor/qcom/msm7x27" remote="cryptomilk" />
<project name="projects/marvel/android_vendor_htc_marvelc.git" path="vendor/htc/marvelc" remote="cryptomilk" />
<project name="WinSuk/android_frameworks_av" path="frameworks/av" revision="jellybean" />
<project name="WinSuk/android_frameworks_native" path="frameworks/native" revision="jellybean" />
<project name="WinSuk/android_packages_apps_Gallery2" path="packages/apps/Gallery2" revision="jellybean" />
<project name="WinSuk/android_packages_apps_LegacyCamera" path="packages/apps/LegacyCamera" revision="jellybean" />
</manifest>
Click to expand...
Click to collapse
Wow! That's a long manifest! I'll use that. I was gonna use modpunk's in his README, but obviously that wouldn't work!
kalaker said:
Thanks for that manifest. Some things came up suddenly and I wasn't able to get this done as quickly as I had hoped. It'll be done very soon.
Click to expand...
Click to collapse
Can't wait!
Sent from my Marvelc using Tapatalk 2
Thread Closed
As requested by OP
No test, no guarentee, only you and it! I won't test these rom and upload it like they will be!
CHANGELOG
V1.0
- First build from sources
- Add GApps lite
- Add Int2Ext+
- Add orientation fix
- Add youtube LQ fix
MD5SUM(32cdb0be18ff830142398918ffdc2b0b)
V1.1
- Add Noozy instead apollo
- Add ES File Explorer instead CMFile Manager
- Userdebug
- Removed some stock apps
- Removed GTalk (you can download hangout from Store)
MD5SUM(46641edc6a436a8cce96ccd7613ef957)
Reserved
Has this same bugs as Jdevs latest build or is it rallapag's source if yes then the rom doesn't make much sense for consumers because it has a lot of bugs and a bad perofrmance.
Hi, scardracs read my PM
Inviato dal mio nuovo HTC Desire HD
@Kevinjoa I use rallapag sources
Powered by Project X
@JDevs please publish here your Roomservice.xml or if you prefer via pm
Powered by Project X
ScardracS said:
@JDevs please publish here your Roomservice.xml or if you prefer via pm
Powered by Project X
Click to expand...
Click to collapse
I'm use the source code from the repo ARMv6 Team.
You need fixes for playback and camcorder? I upload my sources and fixes. later.
JDevs said:
I'm use the source code from the repo ARMv6 Team.
You need fixes for playback and camcorder? I upload my sources and fixes. later.
Click to expand...
Click to collapse
Ok but what repos do you use instead Rallapag?
And if you use rallapag's repo, how I can fix bugs like posted in bug list?
ScardracS said:
Ok but what repos do you use instead Rallapag?
And if you use rallapag's repo, how I can fix bugs like posted in bug list?
Click to expand...
Click to collapse
No. I'm use the repo CryptoMilk.
JDevs said:
No. I'm use the repo CryptoMilk.
Click to expand...
Click to collapse
Please send to me a pm with your roomservice
Powered by Project X
Kevinjoa said:
Has this same bugs as Jdevs latest build or is it rallapag's source if yes then the rom doesn't make much sense for consumers because it has a lot of bugs and a bad perofrmance.
Click to expand...
Click to collapse
based on rallapag’s localmanifest/roomservice
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM projects removed -->
<remove-project name="CyanogenMod/android_bionic" />
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<!-- armv6 projects removed -->
<remove-project name="androidarmv6/android_hardware_qcom_display-legacy" />
<remove-project name="androidarmv6/android_hardware_qcom_media_legacy" />
<!-- replacements -->
<project name="WinSuk/android_bionic" path="bionic" revision="cm-10.1" />
<project name="airk000/hardware_qcom_display" path="hardware/qcom/display" revision="jellybean2" />
<project name="arco/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" revision="cm-10.1" />
<remote name="cryptomilk"
fetch="git://git.cryptomilk.org/" />
<project name="projects/marvel/kernel_htc_msm7227.git" path="kernel/htc/msm7227" remote="cryptomilk" revision="cm-10.1" />
<project name="projects/marvel/android_vendor_qcom_msm7x27.git" path="vendor/qcom/msm7x27" remote="cryptomilk" revision="cm-10.1" />
<project name="projects/marvel/android_vendor_htc_marvel.git" path="vendor/htc/marvel" remote="cryptomilk" revision="cm-10.1" />
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="refs/heads/gingerbread" />
<project name="rallapag/android_device_htc_marvel" path="device/htc/marvel" remote="github" revision="master"/>
<project name="rallapag/android_device_htc_msm7x27-common" path="device/htc/msm7x27-common" remote="github" revision="master"/>
</manifest>
JDevs says:"Fix for camcorder and video playback later lay.There's the matter qcom."
~~~airk000/hardware_qcom_display
~~~airk000/android_hardware_qcom_display
support MSM7227
I have not tested it. But I think it will work. good luck .
Chinese speak. working on cm10.1 for chacha.
thanx to JDevs
New build is up! Enjoy!!
Removed!!
Sent from my Wildfire S using xda app-developers app
Closed on OPs request
Sent from my HTC One using Tapatalk 4 Beta
Hi everybody,
I am trying to compile CyanogenMod for my Galaxy W. I cloned using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and am using the following local_manifest:
Code:
<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>
My own repository is a fork of arco´s, but I added the automatic build of the kernel.
Additionally I cherry-picked two commits in /frameworks/native: (sorry, no links because forum does not let me)
hxxps://github.com/camcory/android_frameworks_native/commit/7818c36a19e190f2ba1358b317bd036a78e53b54
hxxps://github.com/camcory/android_frameworks_native/commit/b52dca3e5a9f67feb94b91c3aa88496a7d6b43c3
Everything compiles and an image gets generated. However, when I flash my Image, the phone does not boot. After the initial Samsung-Screen with "Cyanogenmod" on the bottom, the screen turns all black with the backlights turned on. I have also tried compilation using the prebuilt kernel-Images with the same result.
However, I managed to test my kernel: If I flash the recently posted ROM AOIP v1.6b4, and then flash my Kernel onto it, my phone boots and show my newly built kernel in the properties.
Do you have any hints how to build a working image?
I assume the issue is with the userland. Do I need to cherry-pick any other commits for the repositories.
Already thanks in advance
Just in case there is anyone wondering how to do it. I gave up worrying about 10.1 and checked out cm-10.2. I am using this local overlay.
Code:
<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.2"/>
<project path="vendor/samsung/ancora" name="android_vendor_samsung_ancora" remote="arco" revision="cm-10.2"/>
<project path="kernel/samsung/samsung-kernel-msm7x30" name="samsung-kernel-msm7x30" remote="arco" revision="cm-10.2"/>
</manifest>
I cherry-picked the two already mentioned commits and I can build cyanogenmod and run cyanogenmod.
Boot
ralisi said:
Just in case there is anyone wondering how to do it. I gave up worrying about 10.1 and checked out cm-10.2. I am using this local overlay.
Code:
<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.2"/>
<project path="vendor/samsung/ancora" name="android_vendor_samsung_ancora" remote="arco" revision="cm-10.2"/>
<project path="kernel/samsung/samsung-kernel-msm7x30" name="samsung-kernel-msm7x30" remote="arco" revision="cm-10.2"/>
</manifest>
I cherry-picked the two already mentioned commits and I can build cyanogenmod and run cyanogenmod.
Click to expand...
Click to collapse
So can i got a booted cm if compile it with this manifest? thanks
haky 86 said:
So can i got a booted cm if compile it with this manifest? thanks
Click to expand...
Click to collapse
Yes, I have not built it in months now, but it worked that way.
ralisi said:
Yes, I have not built it in months now, but it worked that way.
Click to expand...
Click to collapse
OK man i compiled it, but boot stuck with a black screen, how to fix it?thanks
haky 86 said:
OK man i compiled it, but boot stuck with a black screen, how to fix it?thanks
Click to expand...
Click to collapse
To be honest, I dont know. I have also experienced this problem and I tried a rebuild a couple of days later and it seemed that the issue got fixed in the meanwhile.
http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
jm492705 said:
http://forum.xda-developers.com/showthread.php?t=1863547&highlight=signal
Im trying to compile my own AOSPA for the S4
i got a noob question. When I try to # Initialize the ParanoidAndroid Repo i get a error on the terminal that states
/home/joel/bin/repo: line 1: syntax error near unexpected token `newline'
/home/joel/bin/repo: line 1: `<!DOCTYPE html>'
can somebody help me on what extactly im doing wrong. Ive googled it and found nothing that helped out.
Click to expand...
Click to collapse
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
lordcheeto03 said:
I will assume you followed the preceding instructions about installing Python and that it was configured correctly. I would say to "rm -rf ~/bin/repo", which will remove the folder /repo and all its contents... then to start back at #Install the Repo.
Click to expand...
Click to collapse
i did what you told me to attempt and still got the same error when try to #Install the Repo. Is there anything else that i can do. i just don't get what im doing wrong because i did it right when i did my own CM build, just attempiting now to make my own AOSPA ROM for the S4.
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where for my specific device? im confused on what to do next. plz help
Click to expand...
Click to collapse
jm492705 said:
i was able to Initialize the ParanoidAndroid Repo but now im stuck on adding the specific device trees for the S4. how do i find it and where? im confused
Click to expand...
Click to collapse
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
lordcheeto03 said:
I assume there's a better way than mine, but I always go into <your source location>/.repo and edit manifest.xml to include CM's android_device_samsung_jf-common, android_device_samsung_jfltetmo, and android_kernel_samsung_jf. After adding them to your manifest, just do another repo sync and you should have everything you need to start cranking out a build...
Click to expand...
Click to collapse
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" 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" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
jm492705 said:
is this the right informartion that i need to add to the manifest?
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_jfltetmo" path="device/samsung/jfltetmo" 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" remote="github" />
<project name="CyanogenMod/android_device_samsung_jf-common" path="device/samsung/jf-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_jf" path="kernel/samsung/jf" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Click to expand...
Click to collapse
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
lordcheeto03 said:
That looks good, but I didn't even think that @ayysir has his PA tree on his github.
I've never built PA but I would assume you could use CM's tree with a few modifications here and there.
Click to expand...
Click to collapse
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
jm492705 said:
So would it be okay for me to put the CM trees that it in the local manifest? just making sure, and then do the repo sync sorry for the noobness just getting the hang of things and really intrested on building PA
Click to expand...
Click to collapse
http://www.github.com/aospa-legacy