Develop Bugs

Weekly rom for wildfire s cm10.1!

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

[Q] How To Fix Boot Stuck After Compilation?

Hello mates
I build successfully Cyanogen Mod 10.1 for my ancora device as test, i got many warning during compilation without any stop, if got warning during compilation did mean can't boot or what depend from?
i use this repos as source:
<?xml version="1.0" encoding="UTF-8"?>
<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>
Click to expand...
Click to collapse
Any one can help me, thanks

[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

Tab Pro 8.4 [T325] CM-13.0 from source -- unknown baseband, no IMEI

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.

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