Database Info

Nightly Skyrocket AOKP Builds [UNOFFICIAL]

Figured I'd make my personal AOKP builds available to the public domain. I basically took AOKP source, added CM9's MSM8660, SkyRocket, and QCOM_MEDIA source to the mix. Changed a couple XML files and voila get AOKP built with SkyRocket support.
I'm not developing anything, just compiling and making the builds available to those that want to try. I've been cherry picking fixes important for SkyRocket from the CM9 team before they're merged, too.
One thing I did notice was the Camera doesn't get built/added, but downloading a camera from the Store seems to work fine. Other than that, everything appears to be working. I'd be interested in hearing what works and doesn't work.
CM9 is my daily driver, but did this for some fun. I have detailed instructions on what I do to a stock AOKP source to get it to compile if you want them.
Thanks go out to the usual suspects...
Team Chopsticks
CyanogenMod Team
AOKP Team
I'm sure there are others, but not sure who they since I grabbed from Github sources.
Feel free to mirror. I will post updates everyday to the link below.
Latest Build
6/17 Build 38 http://d-h.st/3Go
6/15 Build 38 http://d-h.st/jCN
6/13 Build 38 http://d-h.st/Tmx
6/11 Build 38 http://d-h.st/U98
Make sure you are using the UCLE2 Radio since everything in these builds is UCLE2-based.
Build 38 Change Log
reverted tablet nav bar button padding change (back to stock ics padding now)
fix SMS/BT crash bug when no msgs exist
reworked lockscreen music layout to be cleaner
fix ugly gradient on dark holo background
added AOKP Tips widget
added statusbar autohide for tablets (for apps that need full screen)
added support for more lockscreen targets (2-8 options, your choice)
cleaned up octo lockscreen layout
fixed certain FCs with RC related to weather
Mms: fixed stripping certain Polish characters
decreased size of custom lockscreen apps to match other icons
statusbar brightness enabled by default after you wipe (sliding thumb across statusbar to change brightness)
added statusbar notification counter (RC > Statusbar General > Notification Counter)
new AOKP boot animation from @rascarlo
Out of range Bluetooth devices won't show up anymore in Settings
Browser: added option to close all other tabs (besides current)
Fixed data toggle
Removed requirement to reboot when toggling keyboard switcher (IME switcher) in statusbar
added nav bar widgets (to enable, go to nav bar settings > add toggle widgets as one of your nav bar actions/ long press actions, then add widgets -- be sure to add at least 2 for best experience)
as always, tons of fixes for devices and other backend fixes!

Installation Instructions
Here's what I do...
DARKSIDE WIPE (http://forum.xda-developers.com/showthread.php?t=1477955)
Format CACHE (Super important that you don't skip this. Darkside does something to /cache that causes CM9/AOKP to boot loop)
Install AOKP zip
Install GAPPS zip (http://goo.im/gapps/gapps-ics-20120429-signed.zip)
Reboot
Open System Settings->More (under Wireless & Networks)->Mobile Networks->Access Point Names
Select the WAP APN...
a. APN = PTA
b. Username = BLANK (delete whatever is there)
c. MMSC should be http://mmsc.mobile.att.net
d. MMS Proxy = proxy.mobile.att.net
e. Hit Menu button and select SAVE​
Give it a few seconds and data should be working
Install camera app from Google Store (I'm working on getting this to compile into the build)
Build Instructions
Here's what I do starting from the root of the build directory
Setup up AOKP repo and sync it (i.e. repo init -u git://github.com/AOKP/platform_manifest.git -b ics && repo sync)
Create a file called local_manifest.xml in .repo directory with the text below.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="gh" revision="ics" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="gh" revision="ics" />
<project name="TeamChopsticks/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="gh" revision="ics" />
<project name="TeamChopsticks/android_vendor_samsung_skyrocket" path="vendor/samsung/skyrocket" remote="gh" revision="ics" />
</manifest>
Run "repo sync" again to get the above added trees
Edit device/samsung/skyrocket/overlay/packages/providers/TelephonyProvider/res/values/config.xml
Delete config_preferred_apn line and save
Edit device/samsung/skyrocket/overlay/packages/apps/Settings/res/values/config.xml
Delete has_led_flash line and save
Edit device/samsung/skyrocket/full_skyrocket.mk
Change the word "Torch" to "Camera" and save
Create a file called "skyrocket.mk" in vendor/aokp/products with the text below
Code:
$(call inherit-product, device/samsung/skyrocket/full_skyrocket.mk)
# Inherit some common CM stuff.
# $(call inherit-product, vendor/cm/config/gsm.mk)
$(call inherit-product, vendor/aokp/configs/common_phone.mk)
# Inherit some common CM stuff.
# $(call inherit-product, vendor/cm/config/common_full_phone.mk)
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SGH-I727 TARGET_DEVICE=SGH-I727 BUILD_FINGERPRINT="samsung/SGH-I727/SGH-I727:4.0.4/IMM76D/UCLE2:user/release-keys" PRIVATE_BUILD_DESC="SGH-I727-user 4.0.4 IMM76D UCLE2 release-keys"
TARGET_BOOTANIMATION_NAME := vertical-480x800
PRODUCT_NAME := aokp_skyrocket
PRODUCT_DEVICE := skyrocket
PRODUCT_BRAND := samsung
PRODUCT_MANUFACTURER := samsung
PRODUCT_MODEL := SAMSUNG-SGH-I727
Edit AndroidProducts.mk in vendor/aokp/products and add "$(LOCAL_DIR)/skyrocket.mk \" above stingray.mk line.
Run "source build/envsetup.sh"
Run "make clobber && lunch aokp_skyrocket-userdebug && make -j<number or processors X number of thread per processor> bacon"
These are the steps that work for me. I hope they work you as well. Let me know and I'd be happy to help.

so would i install this the same way as i do cm9 (instruction wise)?

That's correct. I'd do a full wipe and install. I've been running the 6/3 build for 24 hours with no problems. Only thing I had to do was install camera 360 and change apn to PTA.
Sent from my SAMSUNG-SGH-I727 using xda premium

Got it and loving it thank you so much for sharing

6/4 Build https://www.sugarsync.com/pf/D7693548_2736667_069288
Camera should be working in this build. Let me know.

i can confirm that the camera is working for me
InstigatorX said:
6/4 Build https://www.sugarsync.com/pf/D7693548_2736667_069288
Camera should be working in this build. Let me know.
Click to expand...
Click to collapse

Shouldn't this be in the Development forum?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

SassyMrsK said:
i can confirm that the camera is working for me
Click to expand...
Click to collapse
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium

i've never used teamwafflehouse just teamchopsticks sorry
abteer said:
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse

You guys are hurting my feelings here lol I will say though thanks for the nightly builds bro good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

IEatKittys! said:
Shouldn't this be in the Development forum?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not really "developing" anything, just having some fun compiling from AOKP/CM9 source. I'd be happy to post my build instructions if you anyone is interested.
nrm5110 said:
You guys are hurting my feelings here lol I will say though thanks for the nightly builds bro good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!

InstigatorX said:
I'm not really "developing" anything, just having some fun compiling from AOKP/CM9 source. I'd be happy to post my build instructions if you anyone is interested.
Thanks!
Click to expand...
Click to collapse
I think it would be helpful and/or a nice addition.
Sent from my SAMSUNG-SGH-I727 using xda premium

Might have screwed up... but how do I get my phone rooted again after installing 4.0.4?

abteer said:
Is this running better than the team wafflehouse release?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes and no, is it more up to date with the work being done? Yes, but are you expected to run into bugs? Yes.
The wafflehouse builds are tested, modified, played with, and released on a basis of what works, and you know in advance usually.
With nightly builds you NEVER know what the state of it will be. Data may not work on one, but work on the next nights, camera might work on one but not the next nights etc. Since these roms are in a constant state of development right now you never know what may happen.
So yes these are a bit more up to date than wafflehouse.
Better, is subjective to the build and build date.
If you really like messing with your phone and a flash junky, use the nightlies, if you want someone to help out and make sure things work stick to waffles.

is it possible that this may work on the t989?

k786 said:
is it possible that this may work on the t989?
Click to expand...
Click to collapse
You guys have your own builds silly. I'll PM you.

R4INS said:
Yes and no, is it more up to date with the work being done? Yes, but are you expected to run into bugs? Yes.
The wafflehouse builds are tested, modified, played with, and released on a basis of what works, and you know in advance usually.
With nightly builds you NEVER know what the state of it will be. Data may not work on one, but work on the next nights, camera might work on one but not the next nights etc. Since these roms are in a constant state of development right now you never know what may happen.
So yes these are a bit more up to date than wafflehouse.
Better, is subjective to the build and build date.
If you really like messing with your phone and a flash junky, use the nightlies, if you want someone to help out and make sure things work stick to waffles.
Click to expand...
Click to collapse
Couldn't agree more.
Sent from my SAMSUNG-SGH-I727 using xda premium

OP updated with 6/6 build. Got distracted yesterday.

Second post updated with BUILD INSTRUCTIONS.

[REF] Building AOKP -- Transient Issues -- 2012/09/18

At the present time, it appears that AOKP is again moving some of their git repositories around. As a result, the Team Acid build environment is "broken" until AOKP updates their repo manifest. It doesn't matter if you are doing this manually, or through Acidify.
Please read the entire thread as work-arounds have been changing from day to day.
One of the issues is that AOKP's frameworks/base and prebuilt git repos are returning
Access to this repository has been disabled by GitHub staff due to excessive use of resources. You'll need to contact support to restore access to this repository. Read here to learn more about decreasing the size of your repository.​
That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt. If you do, you can call repo -f sync which will skip a given git repository if there is a failure and continue with the rest.
Here are some work-arounds for the other issues
Patch your .repo/local_manifest.xml to replace the old git repos with their new location. Mine now looks like
Check yours after sync to the TeamAcid repo, either direct or thorugh Acidify, as FB has updated the TeamAcid version
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="AOKP/android_hardware_libhardware" />
<remove-project name="AOKP/android_hardware_msm7k" />
<remove-project name="AOKP/android_hardware_qcom_media" />
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
<project path="hardware/msm7k" name="AOKP/hardware_msm7k" remote="gh" revision="ics" />
<project path="hardware/qcom/media" name="AOKP/hardware_qcom_media" remote="gh" revision="ics" />
<!-- Projects we're removing -->
<remove-project name="AOKP/vendor_aokp_ics" />
<remove-project name="AOKP/vendor_samsung" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<!-- Projects we're replacing them with -->
<project path="vendor/aokp" name="fbis251/vendor_aokp" remote="gh" revision="ics" />
<project path="vendor/samsung" name="teamacid/proprietary_vendor_samsung" remote="gh" revision="ics" />
<project path="bootable/recovery" name="teamacid/Team-Win-Recovery-Project" remote="gh" revision="master" />
<!-- Projects we're adding -->
<project path="kernel/samsung/galaxys4gmtd" name="teamacid/android_kernel_galaxys4gmtd" remote="gh" revision="ics" />
<project path="device/samsung/galaxys4gmtd" name="fbis251/android_device_samsung_galaxys4gmtd" remote="gh" revision="ics" />
</manifest>
<!--
teamacid's AOKP local_manifest.xml
=================================
vi: ts=4:sw=4:et:noai
-->
Also, a line snuck into the device/samsung/galaxys4gmtd code that will cause a compile error. Adding a declaration for the parameter resolved the build problem.
Check your version (git log) as FB incorporated the patch on the 18th. "Patch to fix config_backKillTimeout build issue for AOKP" is the log entry you are looking for.
Code:
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 9bdf1b1..2cae795 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -199,6 +199,7 @@
<!-- Timeout in MS for how long you have to long-press the back key to
kill the foreground app. -->
+ <add-resource type="integer" name="config_backKillTimeout"/>
<integer name="config_backKillTimeout">1500</integer>
<!--Boolean to enable stk functionality on Samsung phones-->

I have a fix for the overlay but I will use your patch instead. I was finally working with aokp again last night and I got a build ready but still need to change a few things.
EDIT
Do you know if your overlay patch will fix the issue and build fine with CM9 instead of just AOKP? I'd like to push this to the main Team Acid repo when I can.

I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.

jeffsf said:
I didn't find any references to backKilltimeout in Team Acid AOKP. From what I could find, it's a CM-ism that isn't (yet) in the AOKP tree Team Acid is using. I didn't delete the line to try to prevent future merge issues. The AOKP overlay is different than the one Team Acid is using for CM9.
EDIT -- Checking a CM9 build with the "hack" in place now. Builds OK.
Click to expand...
Click to collapse
It's good that it builds. I'll try to remember to push it tonight

I saw they were re doing their repos for jellybean..a whole new start of it

Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?

fzhh said:
Is the repo for AOKP ics branch still broken? Does anyone know when it will be fixed?
Click to expand...
Click to collapse
I've been able to repo sync using jeff's changes to local_manifest.xml.

Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
error: revision ics in AOKP/hardware_libhardware not found
Click to expand...
Click to collapse

Theraze said:
Was broken for my attempt yesterday, said that there was no ICS... but might be fine now. And hey, there's a new build of AOKP. Guess I don't need to build AOKP today... maybe tomorrow. Heh.
Edit: Nope, still get:
Click to expand...
Click to collapse
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware

hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.

FBis251 said:
The repository exists though... Are you sure you made the right changes in local_manifest.xml?
https://github.com/AOKP/hardware_libhardware
Click to expand...
Click to collapse
Same error I've gotten since the first time jeff said to fix it in the github issues thread.
Most recently, I copied and pasted the local_manifest above fully to replace mine.
But as he said... apparently they removed the ics version and are currently only offering jb and master. Joy. Wonder if master is ics, or if they just screwed it up.

jeffsf said:
hadware_libhardware is pooched right now (2012/09/23 morning) as it only has jb and master branches. Likely an AOKP issue that Team Acid can't resolve.
Click to expand...
Click to collapse
We can always try pushing the ics branch to our personal githubs and temporarily editing the local_manifest to reflect this.

As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of framework/base and prebuilt of the ics branch. I tried the Jeff's local_manifest.xml but the sync will fail at the end complaining to framework/base.

fzhh said:
As Jeff mentioned in his original post "That is something neither Team Acid nor you can resolve if you don't already have a copy of frameworks/base and prebuilt."
I don't have a copy of "framework/base and prebuilt".
Click to expand...
Click to collapse
I've uploaded my local repository of hardware/libhardware into my github profile:
https://github.com/fbis251/hardware_libhardware
You can use this by changing the line in jeff's local manifest from:
Code:
<project path="hardware/libhardware" name="AOKP/hardware_libhardware" remote="gh" revision="ics" />
to
Code:
<project path="hardware/libhardware" name="fbis251/hardware_libhardware" remote="gh" revision="ics" />
Try a repo sync after that and I think it'll all work fine.

Little farther, but the new error is 211/314:
error: revision ics in AOKP/hardware_msm7k not found
Click to expand...
Click to collapse
Wild guess here, but qcom/media will probably have the same error, since those are the 3 repos that get replaced together...

I'll try to upload those repos with the ICS branch when I'm not on my school's wifi. They seem to not like letting us ssh over their wifi. :/

Okay I got the changes made:
https://github.com/teamacid/teamacid.github.com/commit/1afa77a372a9aeec9b1c90daa6bb3224f51e9325
Someone test it out by grabbing the local manifest file:
http://teamacid.github.com/manifests/sgh-t959v/AOKP/local_manifest.xml

I still got the following error:
Fetching projects: 100% (314/314), done.
Checking out files: 100% (19168/19168), done. files: 3% (635/19168)
Checking out files: 100% (4743/4743), done.
Checking out files: 100% (9386/9386), done.out files: 17% (1628/9386)
Checking out files: 100% (3156/3156), done. out files: 31% (991/3156)
Checking out files: 100% (24618/24618), done.
Syncing work tree: 61% (192/314) error: revision ics in AOKP/frameworks_base not found

Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...

Theraze said:
Looks like it's working happily now. Thanks!
fzhh, that means you're using the original version, without ANY of the fixes mentioned in this post (since that error is the one fixed in post 1) or the update by FBis251 ~8 hours ago. Run acidify init aokp again, to download the updated local_manifest. Or edit it yourself...
Click to expand...
Click to collapse
Actually an acidify sync should take care of him (NOT repo sync, since repo sync doesn't grab the updated local_manifest.xml)

add own kernel source into rom source

ok i want to add my own kernel source into my aokp source, how would i edit the manifest.xml file to stop getting the kernel source form CM's kernel tree, and instead use my source like so: https://github.com/azoller1/android_kernel_asus_grouper
would i have to create a local_manifest?

azoller1 said:
ok i want to add my own kernel source into my aokp source, how would i edit the manifest.xml file to stop getting the kernel source form CM's kernel tree, and instead use my source like so: https://github.com/azoller1/android_kernel_asus_grouper
would i have to create a local_manifest?
Click to expand...
Click to collapse
You will have to create a local manifest and then remove the project.. And add your own. I don't think this question belongs here. I think you can post either in the Q and As / some help thread or try and check out this thread. Hope this helps.

i just clone mine manually into kernel/asus/, calling it somn different and edit the device/asus/grouper/BoardConfigCommon.mk to
`...
TARGET_KERNEL_CONFIG := oxydo_defconfig
TARGET_KERNEL_SOURCE := kernel/asus/oxydo
...`
ofc some kernels require different toolchains, but that's a different question
Sent from my Nexus 7

[DEV] [sm-t320 == tab pro 8.4] CM-11.0 unofficial bringup for mondrianwifi USA

This thread is for developers only and I will not be posting ROMs here.
I am posting this here in the hope that someone else has time, skills and motivation to help work on this. If so, please PM me and/or send me pull requests.
I am basing this off of the HLTE kernel because it is being very well maintained and has many huge advances from CAF.
Links:
Kernel: https://github.com/crpalmer/android_kernel_samsung_mondrianwifi
Device: https://github.com/crpalmer/android_device_samsung_mondrianwifi
Vendor: https://github.com/crpalmer/android_vendor_samsung_mondrianwifi
I am also using these dependent repositories:
Code:
<project path="device/samsung/msm8960-common"
name="CyanogenMod/android_device_samsung_msm8960-common"
remote="github" revision="cm-11.0"
/>
<project path="device/samsung/qcom-common"
name="CyanogenMod/android_device_samsung_qcom-common"
remote="github" revision="cm-11.0"
/>
<project path="hardware/qcom/display-caf-new"
name="CyanogenMod/android_hardware_qcom_display-caf-new"
groups="caf"
/>
<project path="hardware/qcom/media-caf-new"
name="CyanogenMod/android_hardware_qcom_media-caf-new"
groups="caf"
/>
<remove-project name="CyanogenMod/android_hardware_invensense" />

This was the status but since I got further faster than I was expecting, there is now a build thread which has the status there.

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
* CM 11 boots and the base seems to be generally not horrendously broken
Hardware status:
* display: backlight doesn't work, therefore it also won't turn back on once it turns off
* usb: adb works, nothing else tested
* WiFi: doesn't work
* everything else: haven't even looked at it, and therefore probably doesn't work
Click to expand...
Click to collapse
The source has been published by Samsung.
opensource.samsung.com
Sent from my SM-T320 using XDA Premium HD app

crpalmer said:
Current status:
* clockworkmod recovery: seems to be working fine
Click to expand...
Click to collapse
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!

blulite said:
I'm interested. Do you have a version of CWM recovery that you have compiled that you can share or steps you used to build?
Thanks!
Click to expand...
Click to collapse
The cwmr that I am using is the one that gets built by running a full CM build using the repos I pointed toward. If you can build CM then you should be able to build a recovery that works on at least my tablet. However, I am definitely not sharing a build because of the fact that it is based on the hlte kernel and could be causing serious problems.
I'm going to try to merge the official source into the hlte kernel and see if I can get that working. If so, it will be a fair bit less risky (although it is still risky because random people like me are playing with how the hardware gets used including voltages, current, etc.).
If you were trying to build a recovery yourself, yeah, you probably ran into problems because the bootloader requires a boot.img with a device tree and the DT needs to be version 2 format which is quite new.

Updated the kernel link. It is a merge of the KK_NA source released by samsung into the hlte kernel from cyanogenmod. It builds but the display is still borked (the left hand of the screen now turns back on, but the right does not...).
If anyone was working with these repos, please do not use the original hlte fork any longer.

[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