Develop Bugs

[marvel(c)] Planned ROM - SickleRom | Dev help needed

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​

[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>

Problems building cm-10.1

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.

[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][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(