Database Info

[Q] How can i build ROM from Andromadus GitHub Repository

Hi everyone,
as i said in question title, i'd like to build ROM from Andromadus GitHub Repository, just for fun...
I've already follewed some guide that i've found in all XDA Forum end I already have managed to set up a virtual machine and synced the repository.
Now i miss how to compile cm10.1 branch for our devices...Can anyone suggest me how to do?
I'm an EECS student so I like getting my hands dirty with source code!

TheLegendGZ said:
Hi everyone,
as i said in question title, i'd like to build ROM from Andromadus GitHub Repository, just for fun...
I've already follewed some guide that i've found in all XDA Forum end I already have managed to set up a virtual machine and synced the repository.
Now i miss how to compile cm10.1 branch for our devices...Can anyone suggest me how to do?
I'm an EECS student so I like getting my hands dirty with source code!
Click to expand...
Click to collapse
Which branch did you init your repo with?

Hi Flinny!
First of all thanks for your great work!
I use cm10.1 - >
Code:
repo init -u git://github.com/Andromadus/android.git -b cm10.1
But i know that last night the Cyanogenmod Team has completed the rebranch from mr1-staging to cm10-1 is that change something?
Many thanks for your help!

TheLegendGZ said:
Hi Flinny!
First of all thanks for your great work!
I use cm10.1 - >
Code:
repo init -u git://github.com/Andromadus/android.git -b cm10.1
But i know that last night the Cyanogenmod Team has completed the rebranch from mr1-staging to cm10-1 is that change something?
Many thanks for your help!
Click to expand...
Click to collapse
no that's fixed in the repo when you sync
basically.. repo sync then
. build/envsetup.sh
brunch cm_saga-eng
will get you a build.

Flinny said:
no that's fixed in the repo when you sync
basically.. repo sync then
. build/envsetup.sh
brunch cm_saga-eng
will get you a build.
Click to expand...
Click to collapse
Thank you very very much!Now, i try to build!
I changed smileys icon with Sense one!
I've searched all day, where can i find the images of lockscreen weather?

Lockscreen weather is not there yet in CM 10.1.
Tapatalked from Desire S running Andromadus

Yep, i know that but i want to change it in CM10 just for fun!
Sent from my Desire S using xda premium

So did you manage to build it?
Tapatalked from Desire S running Andromadus

Almost...First Time yes, but now I get an error with Term.apk ...
By the way, it's Christmas so, best wishes to everyone!
Sent from my Desire S using xda premium

[ROM][4.3][CM 10.2][31/07/13] elicik's Unofficial CM 10.2 builds

Hey, I realized that there aren't many CM 10.2 ROMs out there yet, so I made one of my own. This is my first published ROM, so expect a buggy, unsupported experience. I am using fat-tire's repos for the time being. For now, I recommend the GAPPS posted here. I will attempt to post a new build everyday, but no promises.
I don't do support, but I will try to answer questions, and I would appreciate bug reports. Note that CM 10.2 is very much in development right now.
Download/ Changelog
07/31/13 (mirror) - Just a new sync, there should be no real changes.
07/30/13 (mirror) - Initial build, uses fat-tire's repos for device and kernel
For detailed changes see the gerrit page.
Bugs
Focal doesn't work
Two Clock apps, one from Google, one from Android.

Sweet. Been waiting for this. Thanks

the only reason that there are two clocks is because there is one in the cm10.2 zip and the 4.3 gapps.

Can I get a mirror, please? The download always fails at 144MB for me.

Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?

MBQ_ said:
Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?
Click to expand...
Click to collapse
I would, but grouper's device and kernel don't as of yet have 10.2 branches. I use fattire's because I believe they are the best I can do until we have official.
fattire said:
* The /device tree is basically 10.1's device plus a bunch of cherry-picked stuff from AOSP 4.3, plus newer SELinux rules, plus my own minor changes.
* The /kernel tree is currently AOSP 4.3 stock with a cyanogenmod_android_defconfig added. None of the customization from 10.1 are here yet.
Click to expand...
Click to collapse

sgt. meow said:
Can I get a mirror, please? The download always fails at 144MB for me.
Click to expand...
Click to collapse
Done

[LineageOS port] libqdutils_intermediates/export_includes needed but can't make

As the title suggests, I am porting lineageOS and keep getting this error
/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
here is the full log https://paste.myself5.de/JfHg5EA2Je.sql
I have tried re syncing the repo and re downloading the source trees. nothing seems to be fixing this.. :/

Is this problem solved?

How did u solved this issue? @nzzane

Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing

nzzane said:
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
Click to expand...
Click to collapse
Sry i didnt get u. What do u mean two different repos?
Sent from my AO5510 using Tapatalk

Raja_12 said:
What do u mean two different repos?
Click to expand...
Click to collapse
If there is a repo named abc at github that supports i.e. FMRadio and another named xyz, that also supports FMRadio, it is neccessary that depending files are coming from the same repo. Actually the repo from LineageOS clashes with the one from SonyLOS and vice versa.
That's, what nzzane wanted to say IMHO...

Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)

nzzane said:
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
Click to expand...
Click to collapse
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.

Raja_12 said:
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Click to expand...
Click to collapse
It depends what each repo does, and how you want to build it (stock blobs or all device tree)

nzzane said:
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
Click to expand...
Click to collapse
all device tree

Raja_12 said:
all device tree
Click to expand...
Click to collapse
Then one of the repos must be conflicting somewhere :S

nzzane said:
Then one of the repos must be conflicting somewhere :S
Click to expand...
Click to collapse
Yea sometimes I can't make clean or clobber. With one repo it works with other it didn't. So I have to maintain only one repo at a time.

I ran into another issue. Can u help
target arm C: audio.primary.msm8916_32 <= hardware/qcom/audio/hal/voice.c
In file included from hardware/qcom/audio/hal/voice.c:32:
hardware/qcom/audio/hal/voice_extn/voice_extn.h:194:71: error: unused parameter 'adev' [-Werror,-Wunused-parameter]
static int voice_extn_compress_voip_set_mic_mute(struct audio_device *adev, bool state __unused)
Sent from my AO5510 using Tapatalk

[REFERENCE] LineageOS with full Substratum support - Closed until Oreo

Introduction
Hello everyone! I am one of the members of the Substratum team and we constantly have people asking how to add support to ROMs. I have made a repo regarding all of our documentation here, in which I include steps to add support. Normally, it is easy to add support to most ROMs; however, Lineage has made some underlying changes to AssetManager and PackageManager that makes adding the patches a little difficult if you do not have some solid programming background. To help people who are familiar with building and git but not necessarily Java and C, I have created a series of reference repos that you can use to cherry pick the commits into your forks or local builds to easily have theme support! Please read this entire thread, I go over a lot of info and I will be upset if you do not read it all enjoy!
Information
Substratum currently uses OMS (Overlay Manager Service), Sony's theming framework, that allows for real time swapping of resources via overlays. This is accomplished through a series of commits, which include the core OMS framework, exposures so themes can overlay hardcoded resources, and a second set of framework commits to allow Substratum to do all of its operations without root access. You can read more about this in the main Substratum thread. We have made it so that it is easy to merge OMS and all of our exposures on AOSP or close to AOSP ROMs. Lineage is not one of those ROMs as they have based on CAF, which modifies AOSP to suit a large range of devices. Lineage has also modified core components like Package Manager for security reasons and some of those changes will conflict with OMS changes. I have merged the changes on top of Lineage and verified everything has worked properly. I will continue to maintain this as long as time permits. I plan to try and rebase the changes every day on Lineage updates but I may need to do it weekly depending on how much free time I have.
What do I have to do?
All you need to do is merge the changes from our repos into yours! Link: https://github.com/LineageOMS
This can be done in one of four ways (ONLY ONE):
1. Cherry-pick our changes
This will be the best option if you have forked Lineage and made any changes (basically basing a ROM on Lineage). Once you have merged these changes, you can track our progress on Gerrit and merge patches as they come down. The patches you need to pick will be either "committed with nathanchance" or "nathanchance committed".
Code:
git fetch <url> cm-14.1
git cherry-pick <first_sha1>^..<second_sha1>
Example:
Code:
git fetch https://github.com/LineageOMS/android_frameworks_base cm-14.1
git cherry-pick d6b3f93bec61769fab7ebf31e78bf0acb42bb2e6^..1e00bba63c5b6facec5a8beef1bb39863b251183
2. Pull our changes
This will be a good option if you have either forked Lineage and made no changes or do straight builds from their repos, as this will fetch and merge automatically. You can still cherry-pick if you want but this should result in no conflicts (basically a clean merge).
Code:
git pull <url> cm-14.1
Example:
Code:
git pull https://github.com/LineageOMS/android_frameworks_base cm-14.1
3. Sync using our manifest
This is good if you are just building straight from Lineage's sources. The one issue with this is you will be fully reliant on me for updates; Lineage often merges patches across a few repos and you may run into errors if ALL repos are not up to date.
From the top of your Lineage repo folder:
Code:
mkdir LineageOMS && cd LineageOMS
repo init -u https://github.com/LineageOMS/android -b cm-14.1 --no-clone-bundle --depth=1
repo sync -j$( nproc --all ) --force-sync -c --no-clone-bundle --no-tags --optimized-fetch --prune
4. Use the provided local manifest
This is good if you are just building straight from Lineage's sources. As with the above option, you MAY run into errors if a patch is merged across several repos and I have not update my repos with the proper changes.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
4. Use the provided local manifest
I would only recommend doing this if you are building straight from Lineage's sources and willing to build only when I rebase my changes. Lineage often merges patches across several repos and without every repo being up to date, you may get build errors.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
That's it! Super easy as it should be.
Support
If you run into any issues with merging patches, ask in this thread.
If you PM me on XDA... I will ignore you.
If you PM me on Hangouts... I will ignore you.
If you PM me on Telegram... I will ignore you.
See a pattern? This thread is the place for support, nowhere else.
If you run into issues with using Substratum itself, ask in the main thread.

Great!

This is great!

wew...this is great bro

This is great!

Wow, great :laugh:

Awesome!

Awesome, build successfully. Thx.
Finding beautiful themes now.
通过我的 Mi 5s Plus 上的 Tapatalk发言

Great it can't be easier thn this.

Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
akhilnarang said:
Great!
Click to expand...
Click to collapse
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.

actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.

nareshnani142 said:
Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.
Click to expand...
Click to collapse
You need to build for yourself, you cannot do this to an already compiled build.
Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Unfortunately, if you cannot understand what I wrote, you need to do a lot of research into the world of git and custom ROMs, I cannot provide that to you in this thread. A good place to start would be my guide on how to compile from source: https://github.com/nathanchance/Android-Tools/raw/master/Guides/Building_AOSP.txt

I made my own manifest to build lineage with OMS here: https://github.com/DespairFactor/android

@cvxda @xamio

Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Bro lets wait our dev will do this for us,,,,

Thanks
[Thanks bro!!]
[¡Gracias, viejo!]

Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952

tywinlannister7 said:
Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952
Click to expand...
Click to collapse
Delete the file "sepolicy/themeservice_app.te" in your device tree. I removed CMTE's sepolicy as ours conflicts.

dont work with touchwiz roms or?

gtaelbordo said:
dont work with touchwiz roms or?
Click to expand...
Click to collapse
Are TouchWiz ROMs LineageOS? Then no, this is not applicable for TouchWiz ROMs. If you mean Substratum as a whole, probably not as TouchWiz is nowhere close to stock Android and this should be asked in the main Substratum thread.
Sent from my Nexus 6P using XDA Labs

Building cm-13.0 SNAPSHOT

I've build cm SNAPSHOT for KitKat when it was released, now I'm having issues building it for marshmallow. While building for KitKat I was able to just bring a file over from a SNAPSHOT build into my source code, that's not the case with MM. Can anyone help?
Sent from my SM-G900P using XDA-Developers Legacy app

use the muppets repo for propietary blobs
https://github.com/TheMuppets/proprietary_vendor_samsung

paujmos said:
use the muppets repo for propietary blobs
https://github.com/TheMuppets/proprietary_vendor_samsung
Click to expand...
Click to collapse
That really doesn't help with my question. What command do I run to build?