Database Info

Unified Github for Galaxy Y

Hello Everybody,
I am new to these forums but I have seen the efforts to port cm7, cm9, etc to our device.
The ports so far are great, but there are major bugs though, which cannot be fixed.
Compiling from source is the way forward for us.
A few days ago I tried a test build of cm9 but it would not boot.
The problem was because there is no device tree on github for our device.Something like "android_device_samsung_totoro". There are two or three but those are incomplete.
So....
GITHUB REPOS FOR GALAXY Y
http://github.com/GT-S5360
All devs are invited to create and collaborate.
This will create a central resource system forum which anyone can fork, clone, sync, and improve the sources.
Those who want to add a repo can email me at [email protected]
Now,
For development(compile, debug, etc) we need two things:
1. The android source (any flavor)
2. Device File Tree (eg. "android_device_samsung_totoro")
Two teams should be formed for these two tasks, and the second task must be completed fast. An ideal example of this would be here:
github.com/teamhacksung/android_device_samsung_cooper
complete with an extract-files.sh
This unified github will help us bring AOSP, AOKP, CM7, CM9 and whatnot to our galaxy y.
Please pm me if you are interested for development, and we could form a team and collaborate to speed up work, that is to say compiling.

Reserved
Reserved for future use

Ita really grear news...........for all dev
Sent from my GT-S6102 using xda premium

The link is down.

Andromeduh said:
The link is down.
Click to expand...
Click to collapse
It's not. It just links to github.com instead of github.com/GT-S5360

Ok I will tell mr.marroc to joining you
He already make cm7 for our device maybe he can help u sir
Sent from my GT-S5360 using xda premium

Need some help
Thanks, tell every dev you know. I need some help in doing this

Final BroadCom driver for Galaxy Y!!

Here's the final driver for our device!
http://www.broadcom.com/docs/support/videocore/Brcm_Android_ICS_Graphics_Stack.tar.gz
I got it from this site: http://www.broadcom.com/support/
Devs, try to make new roms with this driver

this is real bro ..? or just expired thread
Sent from my GT-S5360 using xda app-developers app

heinrichie said:
this is real bro ..? or just expired thread
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
They 've just released it few days ago!

ICS here we comeDDD

how to install it ?

DvikzzDroid said:
how to install it ?
Click to expand...
Click to collapse
Download the tar.gz file and see readme.txt in the file

Here is the read me
This package contains the Broadcom Android ICS Graphics stack for arm v5
==================================================================
Package contents:
a new folder that contains the Graphics stack source codes:
-----------------------------------------------------------------
brcm_usrlib/dag
Required file changes in existing AOSP repos to build this Graphics stack
-----------------------------------------------------------------
AOSP repo name: repo_aosp/platform/bionic
libc/private/bionic_tls.h
AOSP repo name: repo_aosp/platform/build
core/legacy_prebuilts.mk
target/board/generic/device.mk
AOSP repo name: repo_aosp/platform/external/webrtc
src/common_audio/resampler/main/source/Android.mk
src/common_audio/signal_processing_library/main/source/Android.mk
src/common_audio/vad/main/source/Android.mk
src/modules/audio_processing/aec/main/source/Android.mk
src/modules/audio_processing/aecm/main/source/Android.mk
src/modules/audio_processing/agc/main/source/Android.mk
src/modules/audio_processing/main/source/Android.mk
src/modules/audio_processing/main/test/process_test/Android.mk
src/modules/audio_processing/main/test/process_test/process_test.cc
src/modules/audio_processing/main/test/unit_test/Android.mk
src/modules/audio_processing/ns/main/source/Android.mk
src/modules/audio_processing/utility/Android.mk
src/system_wrappers/source/Android.mk
AOSP repo name: repo_aosp/platform/frameworks/base
opengl/include/EGL/eglext.h
opengl/libagl/egl.cpp
opengl/libs/EGL/egl.cpp
opengl/libs/EGL/eglApi.cpp
opengl/libs/EGL/egl_entries.in
opengl/libs/EGL/getProcAddress.cpp
opengl/libs/GLES2/gl2.cpp
opengl/libs/GLES_CM/gl.cpp
services/input/InputReader.cpp
services/surfaceflinger/Android.mk
services/surfaceflinger/DisplayHardware/DisplayHardware.cpp
AOSP repo name: repo_aosp/platform/hardware/libhardware
Gralloc changes:
include/hardware/fb.h
modules/gralloc/Android.mk
modules/gralloc/framebuffer.cpp
modules/gralloc/gr.h
modules/gralloc/gralloc.cpp
modules/gralloc/gralloc_priv.h
modules/gralloc/mapper.cpp
Hwcomposer changes:
modules/gralloc/Android.mk
modules/hwcomposer/Android.mk
modules/hwcomposer/hwcomposer.cpp
AOSP repo name: repo_aosp/platform/system/core
include/system/graphics.h
==================================================================
Instructions to build this Graphics stack on Android ICS project:
1. Check out a Android ICS (example: android-4.0.1_r1.1) workspace with the following sequence of commands:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1.1
repo sync -j8
2. Extract the content of this package (excludes this README.txt) in the root directory of the Android ICS workspace:
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5

-CALIBAN666- said:
Here is the read me
This package contains the Broadcom Android ICS Graphics stack for arm v5
==================================================================
Package contents:
a new folder that contains the Graphics stack source codes:
-----------------------------------------------------------------
brcm_usrlib/dag
Required file changes in existing AOSP repos to build this Graphics stack
-----------------------------------------------------------------
AOSP repo name: repo_aosp/platform/bionic
libc/private/bionic_tls.h
AOSP repo name: repo_aosp/platform/build
core/legacy_prebuilts.mk
target/board/generic/device.mk
AOSP repo name: repo_aosp/platform/external/webrtc
src/common_audio/resampler/main/source/Android.mk
src/common_audio/signal_processing_library/main/source/Android.mk
src/common_audio/vad/main/source/Android.mk
src/modules/audio_processing/aec/main/source/Android.mk
src/modules/audio_processing/aecm/main/source/Android.mk
src/modules/audio_processing/agc/main/source/Android.mk
src/modules/audio_processing/main/source/Android.mk
src/modules/audio_processing/main/test/process_test/Android.mk
src/modules/audio_processing/main/test/process_test/process_test.cc
src/modules/audio_processing/main/test/unit_test/Android.mk
src/modules/audio_processing/ns/main/source/Android.mk
src/modules/audio_processing/utility/Android.mk
src/system_wrappers/source/Android.mk
AOSP repo name: repo_aosp/platform/frameworks/base
opengl/include/EGL/eglext.h
opengl/libagl/egl.cpp
opengl/libs/EGL/egl.cpp
opengl/libs/EGL/eglApi.cpp
opengl/libs/EGL/egl_entries.in
opengl/libs/EGL/getProcAddress.cpp
opengl/libs/GLES2/gl2.cpp
opengl/libs/GLES_CM/gl.cpp
services/input/InputReader.cpp
services/surfaceflinger/Android.mk
services/surfaceflinger/DisplayHardware/DisplayHardware.cpp
AOSP repo name: repo_aosp/platform/hardware/libhardware
Gralloc changes:
include/hardware/fb.h
modules/gralloc/Android.mk
modules/gralloc/framebuffer.cpp
modules/gralloc/gr.h
modules/gralloc/gralloc.cpp
modules/gralloc/gralloc_priv.h
modules/gralloc/mapper.cpp
Hwcomposer changes:
modules/gralloc/Android.mk
modules/hwcomposer/Android.mk
modules/hwcomposer/hwcomposer.cpp
AOSP repo name: repo_aosp/platform/system/core
include/system/graphics.h
==================================================================
Instructions to build this Graphics stack on Android ICS project:
1. Check out a Android ICS (example: android-4.0.1_r1.1) workspace with the following sequence of commands:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1.1
repo sync -j8
2. Extract the content of this package (excludes this README.txt) in the root directory of the Android ICS workspace:
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5
Click to expand...
Click to collapse
really , im not understand

-CALIBAN666- said:
Here is the read me
This package contains the Broadcom Android ICS Graphics stack for arm v5
==================================================================
Package contents:
a new folder that contains the Graphics stack source codes:
-----------------------------------------------------------------
brcm_usrlib/dag
Required file changes in existing AOSP repos to build this Graphics stack
-----------------------------------------------------------------
AOSP repo name: repo_aosp/platform/bionic
libc/private/bionic_tls.h
AOSP repo name: repo_aosp/platform/build
core/legacy_prebuilts.mk
target/board/generic/device.mk
AOSP repo name: repo_aosp/platform/external/webrtc
src/common_audio/resampler/main/source/Android.mk
src/common_audio/signal_processing_library/main/source/Android.mk
src/common_audio/vad/main/source/Android.mk
src/modules/audio_processing/aec/main/source/Android.mk
src/modules/audio_processing/aecm/main/source/Android.mk
src/modules/audio_processing/agc/main/source/Android.mk
src/modules/audio_processing/main/source/Android.mk
src/modules/audio_processing/main/test/process_test/Android.mk
src/modules/audio_processing/main/test/process_test/process_test.cc
src/modules/audio_processing/main/test/unit_test/Android.mk
src/modules/audio_processing/ns/main/source/Android.mk
src/modules/audio_processing/utility/Android.mk
src/system_wrappers/source/Android.mk
AOSP repo name: repo_aosp/platform/frameworks/base
opengl/include/EGL/eglext.h
opengl/libagl/egl.cpp
opengl/libs/EGL/egl.cpp
opengl/libs/EGL/eglApi.cpp
opengl/libs/EGL/egl_entries.in
opengl/libs/EGL/getProcAddress.cpp
opengl/libs/GLES2/gl2.cpp
opengl/libs/GLES_CM/gl.cpp
services/input/InputReader.cpp
services/surfaceflinger/Android.mk
services/surfaceflinger/DisplayHardware/DisplayHardware.cpp
AOSP repo name: repo_aosp/platform/hardware/libhardware
Gralloc changes:
include/hardware/fb.h
modules/gralloc/Android.mk
modules/gralloc/framebuffer.cpp
modules/gralloc/gr.h
modules/gralloc/gralloc.cpp
modules/gralloc/gralloc_priv.h
modules/gralloc/mapper.cpp
Hwcomposer changes:
modules/gralloc/Android.mk
modules/hwcomposer/Android.mk
modules/hwcomposer/hwcomposer.cpp
AOSP repo name: repo_aosp/platform/system/core
include/system/graphics.h
==================================================================
Instructions to build this Graphics stack on Android ICS project:
1. Check out a Android ICS (example: android-4.0.1_r1.1) workspace with the following sequence of commands:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1.1
repo sync -j8
2. Extract the content of this package (excludes this README.txt) in the root directory of the Android ICS workspace:
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5
Click to expand...
Click to collapse
It says for armv5

Doesn't matter.Arnav is compiling CM9 for SGY.

aniket.lamba said:
Doesn't matter.Arnav is compiling CM9 for SGY.
Click to expand...
Click to collapse
So, it will stabe with Broadcomm Driver ?

aniket.lamba said:
Doesn't matter.Arnav is compiling CM9 for SGY.
Click to expand...
Click to collapse
I'll wait for BroadcomCM version

GSculerlor said:
So, it will stabe with Broadcomm Driver ?
Click to expand...
Click to collapse
Yes and also bieltv.3 is compiling CM9 with his teammates.

i hope someone make a duos build too,i cant currently.

aniket.lamba said:
Yes and also bieltv.3 is compiling CM9 with his teammates.
Click to expand...
Click to collapse
But, why not use Percy's CM 9 to build it ?

Breaking News : bieltv.3 said that he'll compile CM9 for SGY after 1 month
First he'll compile it for cooper
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
GSculerlor said:
But, why not use Percy's CM 9 to build it ?
Click to expand...
Click to collapse
He'll use it as a base I guess.

CyanogenMod will change this list after it

OMG Happy As Hell.....
Sent from my GT-S5360 using xda app-developers app

-CALIBAN666- said:
i hope someone make a duos build too,i cant currently.
Click to expand...
Click to collapse
yeah bro,really we will be grateful if someone compile cm9 for sgy duos too!

GSculerlor said:
But, why not use Percy's CM 9 to build it ?
Click to expand...
Click to collapse
we cant.
aniket.lamba said:
Breaking News : bieltv.3 said that he'll compile CM9 for SGY after 1 month
First he'll compile it for cooper
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
He'll use it as a base I guess.
Click to expand...
Click to collapse
according to the read me, these drivers need to be built while building the rom from source (google if u dunno) and not on built rom
Moreover, @-CALIBAN666- idk what is written in it (maybe my knowledge is less) , but sgy is armv6, and
-CALIBAN666- said:
Here is the read me
3. Build the Android source tree with the following sequence of commands:
source build/envsetup.sh
lunch full-eng
make -j8 TARGET_DEVICE=generic_armv5
Click to expand...
Click to collapse
Confuses me really...

[Q] Self compiled CM11 doesn't boot

I compiled CM11 with latest sources but it doesn't boot.
I did breakfast bacon and add TheMuppets prop. files repo, sync repos again. Bacon zip doesn't boot... The same build for Ville - it boots!
I am on latest TWRP. I don't know what I am missing.

Anyone?
Sent from Oneplus One

I resolved this. I synced Oneplus TheMuppets repo but I didn't sync oppo repo, too.
Sent from Oneplus One

mikronac.ns said:
I resolved this. I synced Oneplus TheMuppets repo but I didn't sync oppo repo, too.
Sent from Oneplus One
Click to expand...
Click to collapse
Are there pretty easy directions to follow for building CM11? I tried to follow this:
http://forum.xda-developers.com/oneplus-one/general/guide-building-lollipop-oneplus-one-t2947949
Except changing cm-12.0 to cm-11.0 and it did not work. Any tips?

[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