Develop Bugs

DEVS: Attention: Changes to KFire-Android projects

WARNING: I'm changing / restructuring the projects on KFire-Android so that all of the Kindle Fire devices can be supported (in the future).
This involves standardization and renaming of the projects across the board.
The new local_manifest.xml is updated here:
https://github.com/KFire-Android/android_local_manifest
Please give me a few days to iron out the otter build again to make sure everything is running correctly before posting that it isn't working
Right now the local_manifest looks something like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- local projects -->
<project path="kernel/amazon/otter-common" name="KFire-Android/kernel_omap_otter-common" revision="cm-10.1" />
<project path="kernel/amazon/bowser-common" name="KFire-Android/kernel_omap_bowser-common" revision="cm-10.1" />
<project path="device/amazon/omap4-common" name="KFire-Android/android_device_amazon_omap4-common" revision="cm-10.1-dev" />
<project path="device/amazon/otter" name="KFire-Android/android_device_amazon_otter" revision="cm-10.1" />
<project path="device/amazon/otter2" name="KFire-Android/android_device_amazon_otter2" revision="cm-10.1" />
<project path="device/amazon/tate" name="KFire-Android/android_device_amazon_tate" revision="cm-10.1" />
<project path="device/amazon/jem" name="KFire-Android/android_device_amazon_jem" revision="cm-10.1" />
</manifest>
As you can see there are new devices for: 2nd Gen KFire, HD 7 and HD8 all setup to use a common projects folder so that we don't duplicate across all of the projects.
Once again: there is some downtime while I sort out the otter/jem builds and then we can look at bringing up support for otter2 and tate (HD 7).

If repo sync failed for omap4-common, try setting revision to cm-10.1-dev

Updated

Attempting to build Liquid Smooth ROM for captivate glide

First off i'm going to say, I know SOME BASIC CODING (I developed some for windows and a little bit on android)
I decided to TRY to build our Captivate glide users more KitKat roms!
So basically I have the source for liquid smooth but I don't know what to do from there (Remember I'm new so don't blow up on me,I'm trying!)
If there is a guide on how to build or you guys can help me on this that would be great!
I was following this guide:
[GUIDE][AOSPA:v3.+] How to Compile AOSPA from Source : + Support and Maintenance
Instead of compiling PA, I decided to use Liquid Smooth (for the life of me couldn't find PA android 4.4.2 REPO!)
did what the guide said and now i'm stuck here:
VERY IMPORTANT: Now, before the final stage sync, make sure there's no code referring to 'ParanoidPreferences' in manifest.
To check that
1) Open your File Browser,
2) Press Ctrl+H (to show hidden files/directories)
3) Navigate to android/system/.repo/manifest.xml
(Right Click & open the XML file in text editor)
*REMOVE ANY 'PARANOIDPREFERENCES' CODE FROM MANIFEST*
*REMOVE GROUPER DEVICE TREE FROM MANIFEST* (This'll be useless, unless you're compiling for Grouper: Nexus 7)
-> Now, Lets add the device specific trees:
Add your own device tree, kernel tree, hardware source tree, & vendor proprietaries tree in the local manifest.
For this, create a new file .repo/local_manifest.xml, & use something in similar terms:
For example, I'm using all corresponding trees for Samsung Galaxy S3 i9300 - International
Following is just an example, not what you should copy/paste. SEARCH & USE YOUR OWN DEVICE SPECIFIC TREES
(codes)Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
I also didn't download the repo into /android/system like it says, I put it into /liquid (followed this) How to compile liquid smooth
Any help would be greatly appreciated! I'm eager to learn how to do this!
My setup
Ubuntu 13.10 x64

did you read that?
Any error message?
wget http://commondatastorage.googleapis.com/git-repo-downloads/repo
chmod 777 repo
./repo init -u git://github.com/LiquidSmooth/android.git -b kitkat
./repo sync
Than you should have source.

Well this attempt to develop is on stand still until I go off on my ISP for shutting off my services because we "apparently" did't pay enough when we did!
Sent from my Kitkatified I927 running CM 11

Here is the paranoid android 4.4 repo:
https://github.com/AOSPA-legacy/manifest

mondrianwifi CM14 breakfast error

I'm trying to build Nougat for this device, which has recently been given a CM14 branch.
I'm getting binary blobs from TheMuppets and after syncing, breakfast gives me this error.
Code:
$ breakfast mondrianwifi
including vendor/cm/vendorsetup.sh
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
Device mondrianwifi not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_mondrianwifi
Default revision: staging/cm-14.0
Checking branch info
Using fallback branch: cm-14.0
Checking if device/samsung/mondrianwifi is fetched from android_device_samsung_mondrianwifi
CyanogenMod/android_device_samsung_mondrianwifi already fetched to device/samsung/mondrianwifi
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_mondrianwifi
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
build/core/config.mk:671: COMMON_GLOBAL_C(PP)FLAGS changed
build/core/config.mk:675: *** bailing.... Alto.
** Don't have a product spec for: 'cm_mondrianwifi'
** Do you have the right repo manifest?
This is my local manifest.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_mondrianwifi" path="device/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_kernel_samsung_mondrianwifi" path="kernel/samsung/mondrianwifi" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.0" />
</manifest>
Any clue?
Thanks.

Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?

Ichijoe said:
Did you forget to run envsetup.sh first?
Which version of the MSM are you attempting to use?
Click to expand...
Click to collapse
I didn't forget to run envsetup.sh
I'm using the MSM8974 repo that appears on github.
https://github.com/CyanogenMod/android_device_samsung_mondrianwifi/blob/cm-14.0/cm.dependencies
Which is this one
https://github.com/CyanogenMod/android_device_samsung_msm8974-common/tree/cm-14.0
Thanks for your reply.

(ratafraking stupid spellcheck!!)
It corrected JDK (Java Development Kit), back to MSM... Which is (if we're to be quite honest) a redundant question. As you really don't have much choice beyond the 8974.
But, my rational thinking is either telling me that JDK 7 is no longer supported, or you might have missed some dependency for JDK 8.

I only have JDK 8 installed, I have successfully compiled CM13 with it.

Which of these groups are optional?

I am trying to reduce the CyanogenMod source download as much as possible. So far I have:
Code:
repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0 --depth=1 --groups=all,-notdefault,-device,-darwin,-x86,-mips,-exynos5,-intel,-eclipse,-device
Then I add Ziyans device tree in roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_maguro" path="device/samsung/maguro" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" />
<project name="Ziyann/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
</manifest>
However, when I do
Code:
repo manifest -o snapshot.xml -r
I still have over 500 projects.
This is a unique list of the groups in the xml file.
Which of them can I exclude without affecting the functionality of the ROM or causing compile issues?
Code:
apps_nfc
apps_stk
arm
broadcom_wlan
cts
dra
drm_
drm_hwcomposer
frameworks_ims
intel_sensors
invensense
libxml2
libyuv
linux
marvell_bt
mediatek
mediatek_wear
omap3
omap4
omap4-aah
pdk
pdk-cw-fs
pdk-fs
qcom
qcom_
qcom_audio
qcom_display
qcom_fm
qcom_keymaster
qcom_msm8960
qcom_msm8994
qcom_msm8x26
qcom_msm8x27
qcom_msm8x74
qcom_msm8x84
qcom_wlan
themes
tools
vboot
omap3 and mediatek look like candidates and some of the qcom ones maybe?
I have attached the snapshot.xml in case anyone has any suggestions of project level items that can be removed rather than group level.

Is Anyone Building Other ROMs Not Posted?

The choice of ROMs has slowly been dipping since Lollipop as more and more ROMs no longer have Official support for Galaxy Nexus.
At the same time, newer ROMs are popping up for other devices and they look quite interesting.
Ones I have been looking at are Dirty Unicorns, Screw'd, AICP and OctOS.
However, building an unofficial ROM has been troublesome for me.
I have been focusing on Marshmallow since there are still some bugs with AOSP/Unlegacy nougat.
My main issue is that it isn't clear which gnex repos I should be adding after I have sync'd the main ROM source.
There are lots of different forks around and it isn't clear which one to choose.
Which repos do I need to add for AOSP based ROMs?
What is the recommended way to add them?
Does it make any difference if the ROM uses Cyanogenmod or Omnirom as a base instead of AOSP?
Has anyone built these (or any other ROMs) privately and would like to share all the commands necessary for a successful build?

Take a look at this backstage development
https://www.androidfilehost.com/?a=show&w=files&flid=18435
SAOSP has more nougat builds,
Then Dirty Unicorn and Pure Nexus.....
Thank him -> @voidz777

My present time is 5 o'clock in the morning.
In other words, it is before going to work.
So I can not write much.lol
Hi, opticyclic
I did not ignore you.
I have been working forever since I got your email.
Because I can not tell the right way unless I port it before telling you.
I was doing screwed work for a while.
https://github.com/voidz777-crewd
But I can not boot it.
Probably, I think it is due to more optimizing.
I got tired because I got tired.lol
After a while, delete https: //github.com/voidz777-crewd.
It is another addition.
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="pdk,linux,arm" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" revision="aosp-6.0" />
<project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="unlegacy" revision="stable" groups="omap4" />
<project path="vendor/ti" name="proprietary_vendor_ti" remote="unlegacy" revision="stable" />
<project path="vendor/widevine" name="proprietary_vendor_widevine" remote="unlegacy" revision="aosp-6.0" />
I'm sorry, my English is not good.
If I could write in Japanese here, I can tell you a little more about the way of port.
There is no time now.
PS.Ah, oct could be pored immediately.

@voidz777 No apologies necessary!
Your posts about different ROMs on Google plus are actually what prompted me to try to build some myself!
Thanks for the info.
I'll post back after trying out a few different ROMs and give an update in the OP on any successes.

I tried to build octos with
Code:
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm
and this in .repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<project remote="unlegacy" path="device/samsung/tuna" name="android_device_samsung_tuna" />
<project remote="unlegacy" path="hardware/ti/omap4" name="android_hardware_ti_omap4" revision="stable" groups="omap4" />
<project remote="unlegacy" path="vendor/samsung" name="proprietary_vendor_samsung" />
<project remote="unlegacy" path="vendor/ti" name="proprietary_vendor_ti" revision="stable" />
<project remote="unlegacy" path="vendor/widevine" name="proprietary_vendor_widevine" />
</manifest>
However, they are doing something funny with the build/envsetup.sh and it isn't picking up the vendorsetup.sh so the device isn't picked up by brunch/breakfast etc.
As far as I can tell, there is no specific info on GitHub, GooglePlus or any posts on xda on how to add a new device for their ROM.
On to AICP....

Check vendor / rom - name or device / other - device /.
If oct it will be platform_vendor_to.
Let's see the commit log.
Is there any device added?
For example, let's look for mako.
https://github.com/Team-OctOS/platform_vendor_to/commit/d30dd90c018ca521d458c939a2c56ffc5a97741d
Mako has been added by this commitment.
Create the tuna file in the same way.
Well, will you continue your way of thinking? Or do you want to know the answer quickly?

Thanks for the tip.
If they are going to use a different build structure, it should really be on the README or a FAQ somewhere.
It's bad programming practice in general to expect people to search through commit logs just to try to work out how a project works.
So instead of just adding a local manifest, OctOs requires the following:
to.dependencies (same as local manifest but in JSON instead of XML)
to.mk - same as the device board (aosp_tuna.mk)
extra line in vendorsetup_community.sh - it ignores your vendorsetup.sh
Then do lunch aosp_tuna-userdebug.
Then do mka bacon
However, the first time I did this, it overwrote my .repo/local_manifest/roomsevice.xml with a generated version that contained octos revisions instead of the aosp revisions, which obviously failed as there is no octos revision in unlegacy!
Weirdly, after reverting the roomservice.xml and running lunch again didn't overwrite it.
AICP was more straightforward.
I just added the roomservice.xml and ran lunch aosp_tuna-userdebug and mka bacon.
However, both failed with the following error:
Code:
build/core/base_rules.mk:157: *** packages/apps/Nfc//nxp/jni: MODULE.TARGET.SHARED_LIBRARIES.libnfc_jni already defined by packages/apps/Nfc/nxp/jni/. Stop.
What is weird about this is that it is the same module defining the library, however, the first one has a double slash in the path!

Probably revert this commit
https://github.com/Team-OctOS/platf...mmit/1b8ed2250fc89adce8e0b0dbb6c5ca4d82705ccb
Sent from my Nexus 5

Good catch.
I wonder how that didn't cause a build failure on the build servers.
The next failure in both was:
Code:
build/core/base_rules.mk:157: *** hardware/invensense/60xx/mlsdk: MODULE.TARGET.SHARED_LIBRARIES.libmlplatform already defined by device/samsung/tuna/libsensors. Stop.
That was resolved by removing the Cyanaogenmod project and using the unlegacy one instead, so the local manifest now looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<remove-project name="CyanogenMod/android_hardware_invensense" />
<project name="android_device_samsung_tuna" path="device/samsung/tuna" remote="unlegacy" />
<project name="android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="unlegacy" revision="stable"/>
<project groups="omap4" name="android_hardware_ti_omap4" path="hardware/ti/omap4" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" />
<project name="proprietary_vendor_ti" path="vendor/ti" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="unlegacy" />
</manifest>
I chose revision="stable" for android_kernel_samsung_tuna", although there is also "aosp-6.0-sound" but I just wanted any kernel to allow me to compile at this point.
The next error (both ROMs) is this (maven 3 is installed)
Code:
make: *** No rule to make target '/home/buildbot/android/aicp/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/aar/classes.jar', needed by '/home/buildbot/android/aicp/out/target/common/obj/APPS/messaging_intermediates/AndroidManifest.xml'. Stop.
This relates to this dir https://github.com/AICP/vendor_aicp/
Interestingly, ambientsdk dir existed all thoughout the n7.0 branch and only got removed recently in the n7.1 branch
https://github.com/AICP/vendor_aicp/commit/8f150895f8b361480ac91ef0ace941e06e9f548e
I also don't see any maven messages in the build log and com.cyngn.ambient/ambientsdk/ is not in my ~/.m2/repository which makes me wonder if I am missing a project.
The only similar errors I see online are if people don't have maven installed.
I tried removing the files like the 7.1 branch even though it felt wrong,
Code:
rm vendor/aicp/overlay/common/frameworks/base/core/res/res/values/cm_arrays.xml
rm -rf vendor/aicp/ambientsdk
Not surprisingly, it seems like something else is calling it as the same error pops up 25 mins into build.
repo grep ambientsdk shows ContactsCommon, Trebuchet and ContactsProvider using it in the Android.mk files and grepping for ambient shows lot of java imports.
So now I am stuck again.
To be honest, I wasn't expecting to have to deal with errors like this as they don't seem to be device specific.
i.e. there are builds for other devices so how did they compile?

i have posted nethunter rom here: https://forum.xda-developers.com/galaxy-nexus/development/rom-kali-linux-net-hunter-t3676472