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

[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

[ROM][6.0.1][K920][kingdom_row]AICP for Lenovo Vibe Z2 Pro ROW

Unofficial build of AICP 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="aicp-mm6.0" />
<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" />
</manifest>
Click to expand...
Click to collapse

I can't download. Receiving error OOPS!
no mirrors found.

fixed download https://www.androidfilehost.com/?fid=24438995911973743

new build, updated DOWNLOAD link in first post

Thank u bro

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...p_kingdom_row_mm-11.0-UNOFFICIAL-20160330.zip

new build based on 7.1.1 ready to go http://frantisheq.synology.me/android/kingdom/aicp

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

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.

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