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
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
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>
Hello, i'm trying to build PA from source but cannot find the following info for our device:
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.
<?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>
RE: Building Paranoid Androis from source
@masterleron It's because the Vision isn't officially supported, but it's easy enough to add support yourself, as luckily for you we are supported by the Andromadus team! This might work:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Andromadus/android_device_htc_vision" path="device/htc/vision" remote="github" revision="cm-10.1" />
<project name="Andromadus/htc7x30-3.0" path="htc7x30-3.0" remote="github" revision="cm-10.1" />
<project name="Andromadus/android_device_htc_msm7x30-common" path="device/htc/msm7x30-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-10.1" />
<project name="Andromadus/android_hardware_qcom_librpc" path="hardware/qcom/librpc" remote="github" revision="cm-10.1" />
</manifest>
EDIT: OK I don't know if that will actually work, probably not, look here for help
This new one worked perfectly for me:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Andromadus/android_device_htc_vision" path="device/htc/vision" remote="github" revision="jb4.2" />
<project name="Andromadus/htc7x30-3.0" path="htc7x30-3.0" remote="github" revision="andromadus" />
<project name="Andromadus/android_hardware_qcom_librpc" path="hardware/qcom/librpc" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_libhardware" path="hardware/libhardware" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_qcom_audio" path="hardware/qcom/audio" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_libhardware_legacy" path="hardware/libhardware/legacy" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_ril" path="hardware/ril" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" remote="github" revision="mr1-staging" />
<project name="Andromadus/android_hardware_qcom_camera" path="hardware/qcom/camera" remote="github" revision="ion" />
<project name="Andromadus/android_hardware_msm7k" path="hardware/msm7k" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_gps" path="hardware/qcom/gps" remote="github" revision="jellybean" />
<project name="Andromadus/proprietary_htc_vision" path="vendor/htc" remote="github" revision="jb4.2" />
</manifest>
Sent from my HTC Vision using Tapatalk 4 Beta
I have a long standing issue with my htc g2 which I have not been able to correct until now, my phone hooks even when I was running it on stock rom gb 2.3.4, and then jumped it to gb 2.3.7 it never got better and again jumped it to andromadus mimicry ics hoping it will get better still remained the same and I'm currently running it on andromadus jellybean and it's still hooking and flashed the kernel nothing seems to be working at all. I'll press the power button for like 3 to 4 times for the screen to go off and on every time it hooks for it to work normal again which most time it doesn't. Please I really need your help cos everything I've tried seem not to be working. Thanks [email protected]
Sent from my HTC Vision using xda app-developers app
This new one is the best for the vision, downloads all the necessary files.:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Andromadus/android_device_htc_vision" path="device/htc/vision" remote="github" revision="jb4.2" />
<project name="Andromadus/proprietary_htc_vision" path="vendor/htc" remote="github" revision="jb4.2" />
<project name="Andromadus/htc7x30-3.0" path="htc7x30-3.0" remote="github" revision="andromadus" />
<project name="Andromadus/android_device_htc_common" path="device/htc/common" remote="github" revision="jb" />
<project name="Andromadus/android_device_htc_msm7x30-common" path="device/htc/msm7x30-common" remote="github" revision="cm10.1" />
<project name="Andromadus/android_hardware_qcom_librpc" path="hardware/qcom/librpc" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_qcom_audio" path="hardware/qcom/audio" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_qcom_gps" path="hardware/qcom/gps" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_camera" path="hardware/qcom/camera" remote="github" revision="ion" />
<project name="Andromadus/android_hardware_libhardware" path="hardware/libhardware" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_libhardware_legacy" path="hardware/libhardware/legacy" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_ril" path="hardware/ril" remote="github" revision="jb4.2" />
<project name="Andromadus/android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" remote="github" revision="mr1-staging" />
<project name="Andromadus/android_hardware_msm7k" path="hardware/msm7k" remote="github" revision="jellybean" />
<project name="Andromadus/android_frameworks_av" path="frameworks/av" remote="github" revision="cm10.1" />
<project name="Andromadus/android_frameworks_native" path="frameworks/native" remote="github" revision="cm10.1" />
</manifest>
Sent from my HTC Vision using Tapatalk 4 Beta
For android 4.3 (PA 3.99):
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Andromadus/android_device_htc_vision" path="device/htc/vision" remote="github" revision="cm10.2" />
<project name="Andromadus/proprietary_htc_vision" path="vendor/htc" remote="github" revision="jb4.2" />
<project name="Andromadus/htc7x30-3.0" path="htc7x30-3.0" remote="github" revision="andromadus_4.3" />
<project name="Andromadus/android_device_htc_common" path="device/htc/common" remote="github" revision="jb" />
<project name="Andromadus/android_device_htc_msm7x30-common" path="device/htc/msm7x30-common" remote="github" revision="cm10.2" />
<project name="Andromadus/android_hardware_qcom_librpc" path="hardware/qcom/librpc" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="jb4.3" />
<project name="Andromadus/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="jb4.3" />
<project name="Andromadus/android_hardware_qcom_audio" path="hardware/qcom/audio" remote="github" revision="jb4.3" />
<project name="Andromadus/android_hardware_qcom_gps" path="hardware/qcom/gps" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_qcom_camera" path="hardware/qcom/camera" remote="github" revision="ion" />
<project name="Andromadus/android_hardware_libhardware" path="hardware/libhardware" remote="github" revision="jb4.3" />
<project name="Andromadus/android_hardware_libhardware_legacy" path="hardware/libhardware/legacy" remote="github" revision="jellybean" />
<project name="Andromadus/android_hardware_ril" path="hardware/ril" remote="github" revision="jb4.3" />
<project name="Andromadus/android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" remote="github" revision="mr1-staging" />
<project name="Andromadus/android_hardware_msm7k" path="hardware/msm7k" remote="github" revision="jellybean" />
<project name="Andromadus/android_frameworks_av" path="frameworks/av" remote="github" revision="cm10.2" />
<project name="Andromadus/android_frameworks_native" path="frameworks/native" remote="github" revision="cm10.2" />
</manifest>
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>-->