Database Develop

[CLOSED] Porting to the Nexus 7 2013 (Flo)

NOT ENOUGH HELP, CAN'T PORT THIS WITH MY CURRENT SCHEDULE. THREAD CLOSED.
Ubuntu Touch Porting Efforts to the Nexus 7 2013 (Flo)
Status: WIP
Why is this going to be so hard and take so long?
The biggest issue is that Ubuntu Touch is still based on CM10.1 (Android 4.2) and not CM10.2 (Android 4.3).
Not to mention that Android 4.3 images and binaries for this device have only recently been released.
Ubuntu Touch isn't yet (as of September 21st, 2013) compatible with an Android 4.3 base.
Lend a Hand
Ubuntu Touch Porting Wiki (Needs a HUGE Update): https://wiki.ubuntu.com/Touch/Porting
Ubuntu Touch Porting Wiki 2.0 (WIP): https://wiki.ubuntu.com/Touch/PortingFlippedInProgress
CM Device Source: https://github.com/CyanogenMod/android_device_asus_flo
CM MSM Google Kernel Source: https://github.com/CyanogenMod/android_kernel_google_msm
AOSP Kernel: https://android.googlesource.com/device/asus/flo-kernel/
AOSP Kernel Source: https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-jb-mr2
AOSP Kernel Tree for Qualcomm Chipsets: https://android.googlesource.com/kernel/msm/
~/working_directory/.repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_asus_flo" path="device/asus/flo" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="cm-10.2" />
</manifest>
How to Initialize the CM-10.2 Branch (credit to @stbgs in Post #4)
Code:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo

Reserved.

Where to go from here...
Code:
[HIDE][email protected]:~/utouch$ . build/envsetup.sh && brunch flo
including device/asus/flo/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/goldfish/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
pull-lp-source: Downloading libhybris version 0.1.0+git20130606+c5d897a-0ubuntu16
pull-lp-source: Downloading libhybris_0.1.0+git20130606+c5d897a.orig.tar.gz from archive.ubuntu.com (0.483 MiB)
pull-lp-source: Downloading libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.debian.tar.gz from archive.ubuntu.com (0.082 MiB)
gpgv: Signature made Fri 09 Aug 2013 10:56:57 AM EDT using RSA key ID B16223A3
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.dsc
dpkg-source: info: extracting libhybris in libhybris-0.1.0+git20130606+c5d897a
dpkg-source: info: unpacking libhybris_0.1.0+git20130606+c5d897a.orig.tar.gz
dpkg-source: info: unpacking libhybris_0.1.0+git20130606+c5d897a-0ubuntu16.debian.tar.gz
dpkg-source: info: applying 0001-Media-adding-initial-compat-files-for-media.patch
dpkg-source: info: applying 0002-Media-Recorder-adding-initial-support-for-media-reco.patch
dpkg-source: info: applying 0003-hybris-common-jb-Making-libhybris-buildable-x86-64.patch
dpkg-source: info: applying 0004-platforms-Makefile.am-temporarily-disabling-fbdev-to.patch
dpkg-source: info: applying 0005-common-hooks.c-adding-NVIDIA-HACK-needed-by-Nexus-7.patch
dpkg-source: info: applying 0006-jb-linker.c-allow-debug-of-the-linker-and-hooked-sym.patch
dpkg-source: info: applying 0007-jb-linker.c-ubuntu-touch-uses-dev-alog-instead-of-de.patch
dpkg-source: info: applying 0008-hooks-shm-fixing-logic-with-cond-is-negative-error.patch
dpkg-source: info: applying 0009-jb-linker.c-reduce-debugging-output-for-prelinked-li.patch
dpkg-source: info: applying 0010-hardware-include-adding-audio-hal-related-headers-fr.patch
dpkg-source: info: applying 0011-hooks.c-no-need-to-map-strcasestr.patch
dpkg-source: info: applying 0012-hooks.c-handle-invalid-mutex-in-pthread_mutex_destro.patch
dpkg-source: info: applying 0013-implement-getset-property-via-property-service.patch
dpkg-source: info: applying 0014-input_compatibility_layer.cpp-avoid-blocking-on-exit.patch
dpkg-source: info: applying 0015-camera_compatibility_layer.cpp-don-t-explicitly-rele.patch
dpkg-source: info: applying 0016-media-adding-files-for-media-codec-support-with-stag.patch
dpkg-source: info: applying 0017-common-hooks.c-handle-null-attr-in-pthread_rwlock_in.patch
dpkg-source: info: applying 0018-properties.c-better-handling-for-name-and-value-size.patch
dpkg-source: info: applying 0019-Fix-last-argument-to-pthread_cond_timedwait.patch
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 82, in <module>
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 410, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 523, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 448, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 531, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'[/HIDE]

Hey there
I am also in the process of trying to build ubuntu touch for flo
I realized the branch name are missing from build/tools/roomservice.py, however you can add the branch by setting up the ROOMSERVICE_BRANHCES env variable like so:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo
I am still having issues with the build though..

stbgz said:
Hey there
I am also in the process of trying to build ubuntu touch for flo
I realized the branch name are missing from build/tools/roomservice.py, however you can add the branch by setting up the ROOMSERVICE_BRANHCES env variable like so:
export ROOMSERVICE_BRANCHES=cm-10.2 && brunch flo
I am still having issues with the build though..
Click to expand...
Click to collapse
Thanks mate! Post your terminal outputs here after failed builds so we can help each other out .
Sent from my Nexus 7 (2013).

Also, how did you add the extra configs for the kernel? android/kernel doesn't exist. Also, device/asus/flo/aosp_base.mk doesn't exist.
Sent from my Nexus 7 (2013).

MikeyCriggz said:
Thanks mate! Post your terminal outputs here after failed builds so we can help each other out .
Sent from my Nexus 7 (2013).
Click to expand...
Click to collapse
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_asus_flo
Default revision: phablet-10.1
Checking branch info
Searching for repository on phablet.ubuntu.com
Repository not found on phablet.ubuntu.com
This may likely be an unsupported build target
Using fallback branch: cm-10.2
CyanogenMod/android_device_asus_flo already exists
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Didn't add any modifications to the kernel. and yes the file aosp_base.mk is being included from device/asus/flo/aosp_flo.mk, but my source tree doesn't have such file not sure why

stbgz said:
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
Device flo not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_asus_flo
Default revision: phablet-10.1
Checking branch info
Searching for repository on phablet.ubuntu.com
Repository not found on phablet.ubuntu.com
This may likely be an unsupported build target
Using fallback branch: cm-10.2
CyanogenMod/android_device_asus_flo already exists
Syncing repository to retrieve project.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/asus/flo/cm.mk]]: "build/target/product/aosp_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_flo'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Didn't add any modifications to the kernel. and yes the file aosp_base.mk is being included from device/asus/flo/aosp_flo.mk, but my source tree doesn't have such file not sure why
Click to expand...
Click to collapse
Can you post your repository to Git-Hub? It'll make the team effort much easier .
Sent from my Nexus 7 (2013).

Will do, as soon as I have something to add, so far I have only realized that ubuntu repos don't have the cm10.2 branch? (hence the missing files), we have to find a way to have the ubuntu toold build with the cm10.2 branch(which includes aosp 4.3 changes I think)

stbgz said:
Will do, as soon as I have something to add, so far I have only realized that ubuntu repos don't have the cm10.2 branch? (hence the missing files), we have to find a way to have the ubuntu toold build with the cm10.2 branch(which includes aosp 4.3 changes I think)
Click to expand...
Click to collapse
Yeah, this is going to take some makeshift hacks.
Sent from my Nexus 7 (2013).

I'm going to try and mod an aosp_base.mk file from another device (perhaps Mako, since it has a very similar chipset). I'll let you know how it goes.
Sent from my Nexus 7 (2013).

Got it to start compiling stuck at this:
Code:
Export includes file: system/su/Android.mk -- /home/criggs/utouch/out/target/product/flo/obj/EXECUTABLES/su_intermediates/export_includes
Notice file: system/su/NOTICE -- /home/criggs/utouch/out/target/product/flo/obj/NOTICE_FILES/src//system/xbin/su.txt
make: *** No rule to make target `frameworks/native/data/etc/android.hardware.bluetooth_le.xml', needed by `/home/criggs/utouch/out/target/product/flo/system/etc/permissions/android.hardware.bluetooth_le.xml'. Stop.
make: *** Waiting for unfinished jobs....

This line needs to be removed from 'device/asus/flo/aosp_flo.mk' in order to bypass the first error:
Code:
# Inherit from the common Open Source product configuration
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
Edit: Don't worry, the original 'aosp_flo.mk' will be backed up automatically as 'aosp_flo.mk~'.

MikeyCriggz said:
This line needs to be removed from 'device/asus/flo/aosp_flo.mk' in order to bypass the first error:
Code:
# Inherit from the common Open Source product configuration
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
Edit: Don't worry, the original 'aosp_flo.mk' will be backed up automatically as 'aosp_flo.mk~'.
Click to expand...
Click to collapse
Hey there I got it somwhat compiling, most of the changes are in the file:
.repo/manifest/defualt.xml
(the - lines are lines that go the removed the + are the opposite)
basically
added a few repos straight from cyanogen and the kernel straight from google.
I'm building we'll see if it finishes and then if it works
build like so
TARGET_PREBUILT_KERNEL=kernel/flo-kernel/kernel brunch flo
here are the changes I did
diff --git a/default.xml b/default.xml
index 48b4917..d6714b7 100644
--- a/default.xml
+++ b/default.xml
@@ -7,6 +7,9 @@
<remote name="github"
fetch="git://github.com" />
+ <remote name="google"
+ fetch="https://android.googlesource.com" />
+
<default revision="refs/heads/phablet-10.1"
remote="phablet"
sync-c="true"
@@ -53,6 +56,7 @@
<project path="external/icu4c" name="CyanogenMod/android_external_icu4c" />
<project path="external/jhead" name="CyanogenMod/android_external_jhead" />
<project path="external/jpeg" name="CyanogenMod/android_external_jpeg" />
+ <project path="kernel/flo-kernel" name="device/asus/flo-kernel" remote="google" revision="master" />
<project path="external/kernel-headers" name="CyanogenMod/android_external_kernel-headers" />
<project path="external/liblzf" name="CyanogenMod/android_external_liblzf" />
<project path="external/libncurses" name="CyanogenMod/android_external_libncurses" />
@@ -82,8 +86,8 @@
<project path="external/zlib" name="CyanogenMod/android_external_zlib" />
<project path="frameworks/av" name="CyanogenMod/android_frameworks_av" />
- <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" />
- <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" />
+ <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" remote="github" revision="cm-10.2"/>
+ <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" remote="github" revision="cm-10.2" />
<project path="frameworks/opt/emoji" name="CyanogenMod/android_frameworks_opt_emoji" />
<project path="hardware/broadcom/wlan" name="CyanogenMod/android_hardware_broadcom_wlan" />
@@ -101,7 +105,7 @@
<project path="hardware/qcom/gps" name="CyanogenMod/android_hardware_qcom_gps" />
<project path="hardware/qcom/keymaster" name="CyanogenMod/android_hardware_qcom_keymaster" />
<project path="hardware/qcom/media" name="CyanogenMod/android_hardware_qcom_media" />
- <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" />
+ <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" remote="github" revision="cm-10.2"/>
<project path="hardware/qcom/power" name="CyanogenMod/android_hardware_qcom_power" />
<project path="hardware/qcom/sensors" name="CyanogenMod/android_hardware_qcom_sensors" />
<project path="hardware/qcom/wlan" name="CyanogenMod/android_hardware_qcom_wlan" />

stbgz said:
Hey there I got it somwhat compiling, most of the changes are in the file:
.repo/manifest/defualt.xml
(the - lines are lines that go the removed the + are the opposite)
basically
added a few repos straight from cyanogen and the kernel straight from google.
I'm building we'll see if it finishes and then if it works
build like so
TARGET_PREBUILT_KERNEL=kernel/flo-kernel/kernel brunch flo
here are the changes I did
diff --git a/default.xml b/default.xml
index 48b4917..d6714b7 100644
--- a/default.xml
+++ b/default.xml
@@ -7,6 +7,9 @@
<remote name="github"
fetch="git://github.com" />
+ <remote name="google"
+ fetch="https://android.googlesource.com" />
+
<default revision="refs/heads/phablet-10.1"
remote="phablet"
sync-c="true"
@@ -53,6 +56,7 @@
<project path="external/icu4c" name="CyanogenMod/android_external_icu4c" />
<project path="external/jhead" name="CyanogenMod/android_external_jhead" />
<project path="external/jpeg" name="CyanogenMod/android_external_jpeg" />
+ <project path="kernel/flo-kernel" name="device/asus/flo-kernel" remote="google" revision="master" />
<project path="external/kernel-headers" name="CyanogenMod/android_external_kernel-headers" />
<project path="external/liblzf" name="CyanogenMod/android_external_liblzf" />
<project path="external/libncurses" name="CyanogenMod/android_external_libncurses" />
@@ -82,8 +86,8 @@
<project path="external/zlib" name="CyanogenMod/android_external_zlib" />
<project path="frameworks/av" name="CyanogenMod/android_frameworks_av" />
- <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" />
- <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" />
+ <project path="frameworks/base" name="CyanogenMod/android_frameworks_base" remote="github" revision="cm-10.2"/>
+ <project path="frameworks/native" name="CyanogenMod/android_frameworks_native" remote="github" revision="cm-10.2" />
<project path="frameworks/opt/emoji" name="CyanogenMod/android_frameworks_opt_emoji" />
<project path="hardware/broadcom/wlan" name="CyanogenMod/android_hardware_broadcom_wlan" />
@@ -101,7 +105,7 @@
<project path="hardware/qcom/gps" name="CyanogenMod/android_hardware_qcom_gps" />
<project path="hardware/qcom/keymaster" name="CyanogenMod/android_hardware_qcom_keymaster" />
<project path="hardware/qcom/media" name="CyanogenMod/android_hardware_qcom_media" />
- <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" />
+ <project path="hardware/qcom/msm8960" name="CyanogenMod/android_hardware_qcom_msm8960" remote="github" revision="cm-10.2"/>
<project path="hardware/qcom/power" name="CyanogenMod/android_hardware_qcom_power" />
<project path="hardware/qcom/sensors" name="CyanogenMod/android_hardware_qcom_sensors" />
<project path="hardware/qcom/wlan" name="CyanogenMod/android_hardware_qcom_wlan" />
Click to expand...
Click to collapse
You're the man! I'll see if I can get any further later tonight. I have to compile PA for a few devices and do some things first.

Things are going pretty well for this port so far. Will push all of my work thus far to a GitHub repository as soon as I can.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Not having Ubuntu Touch available on the N7(2013) model has kept me from saving to buy one.
I've used Ubuntu Touch for at least 2 months now as a daily driver on my Original N7 and really love it. especially being able to hack unity8
Sent from my LG-LS970 using xda app-developers app

blmvxer said:
Not having Ubuntu Touch available on the N7(2013) model has kept me from saving to buy one.
I've used Ubuntu Touch for at least 2 months now as a daily driver on my Original N7 and really love it. especially being able to hack unity8
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, long time no see .

Hey man, I've been around if you haven't already seen them, I have some apps in the apps/games folder.
You know modifying unity8 and such.
Oh I have a question for you, How much do you know about the infographic circle on the greeter screen?
I want to modify it to capture the weather and maybe updates from friends.
Sent from my LG-LS970 using xda app-developers app

blmvxer said:
Hey man, I've been around if you haven't already seen them, I have some apps in the apps/games folder.
You know modifying unity8 and such.
Oh I have a question for you, How much do you know about the infographic circle on the greeter screen?
I want to modify it to capture the weather and maybe updates from friends.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I don't know much about the new welcome screen. I haven't been around the Ubuntu Touch scene for a bit. Let's not digress here, though. Send me a PM or ping me on Google Hangouts ([email protected]) .

Assistance compiling Nexus 4 Rom

Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.

caspian154 said:
Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.
Click to expand...
Click to collapse
U just delete the <project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" /> in the local_manifest.xml

yeah, I've tried that - it comes, but I don't get the zip file. I tried a couple of options in the local_manifests from another thread and actually got a zip!
Sent from my Nexus 4 using xda app-developers app

caspian154 said:
yeah, I've tried that - it comes, but I don't get the zip file. I tried a couple of options in the local_manifests from another thread and actually got a zip!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
can you post the link about the other thread ?
thanks a lot !!

ilpolpi65 said:
can you post the link about the other thread ?
thanks a lot !!
Click to expand...
Click to collapse
Yep - sorry, I haven't been near a computer until now. I haven't tested out the rom yet, but it definitely generated a zip file ~ 155 mb, which doesn't seem wrong. Anyway, here's the post I stole from: http://forum.xda-developers.com/showpost.php?p=46661249&postcount=5
here's specifically what I have in my .repo/local_manifests/roomservice.xml
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_broadcom.git" path="vendor/broadcom" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nvidia.git" path="vendor/nvidia" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_elan.git" path="vendor/elan" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_invensense.git" path="vendor/invensense" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_widevine.git" path="vendor/widevine" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nxp.git" path="vendor/nxp" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_asus.git" path="vendor/asus" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_imgtec.git" path="vendor/imgtec" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="omnirom/android_device_asus_flo" path="device/asus/flo" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_google_msm" path="kernel/google/msm" remote="github" revision="android-msm-mako-3.4-jb-mr2" />
<project name="omnirom/android_device_lge_mako" path="device/lge/mako" remote="github" revision="android-4.3" />
<project name="omnirom/android_kernel_lge_mako" path="kernel/lge/mako" remote="github" revision="android-4.3" />
</manifest>

caspian154 said:
Hey all -
I've been trying for a couple days to build from the instructions at docs.omnirom.org/Build_for_mako without much success. I am able to sync the repository - it seems to download all the devices though and I'm a little confused at that.
I resync after adding the vendor blobs by adding the following to .repo/local_manifests/ (from the guide):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/mako-kernel" name="device/lge/mako-kernel" groups="device,mako" revision="refs/tags/android-4.3_r2.1_" />
</manifest>
Then I receive the following:
Code:
fatal: duplicate project device/lge/mako-kernel in /mnt/ddrive/android/omni/.repo/manifest.xml
This makes sense because the project is already in the .repo/manifest.xml
From there I try to execute the following from my repository.
Code:
. build/envsetup.sh; brunch mako
It runs for about 23 minutes, I don't get any errors, but I also don't get the installable .zip file.
Sorry if this is the wrong place to ask development questions.
Click to expand...
Click to collapse
My bad, I'm the one who edited part of the doc there, and i was fearing some confusion, definitely need a bit of rewrite, as i wrote that doc prior to roomservice.xml intergration.
Basically, if you are using an omni.dependencies file in the device folder, you don't need to include mako kernel dependencies in local_manifest.xml, but you will need to lunch breakfast and lunch prior to brunch to actually sync this branch.
If you are not using omni.dependencies, you should ignore the first part of the doc, and only use the second part, with title "deprecated".
You should actually delete roomservice.xml if you're not using it to sync, or else you would have the problem you currently have.
In other terms, keep only that part
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/" />
<project name="android_kernel_lge_mako" path="kernel/lge/mako" remote="omnirom" revision="android-4.3"/>
</manifest>
in a local_manifest.xml in your .repo/local_manifests directory, and delete the roomservice.xml file which is useless until you use an omni.dependencies file.
Also delete the changes you made out of local_manifest.xml, rule is only one declaration per branch
The so called blobs ( i didn't write that part) are actually not part of that repo, you could add themuppets repo for mako in your local_manifest.xml, for legal reasons, i couldn't include it in Omni's wiki.
Hope this will solve your problem, will try to edit the doc tomorrow to allow roomservice usage.

thanks a lot! I figured that all made more sense for those that were more experienced ROM developers. I would rather use the also stuff and not rely on cm blobs. I'm building for educational purposes - I'd like to make some tweaks here and there, so I want it as close to what the omni nightlies will be when they arrive.
Thanks for your explanation and documenting all that you do! I've been leaching off ROM developers for years and want to join in and help out.
Sent from my Nexus 4 using xda app-developers app

caspian154 said:
thanks a lot! I figured that all made more sense for those that were more experienced ROM developers. I would rather use the also stuff and not rely on cm blobs. I'm building for educational purposes - I'd like to make some tweaks here and there, so I want it as close to what the omni nightlies will be when they arrive.
Thanks for your explanation and documenting all that you do! I've been leaching off ROM developers for years and want to join in and help out.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You're welcome, and you can actually ignore part of my previous post, I just fully edited the doc, now everything is using roomservice.xml and omni.dependencies, so all mako's files get synced when you launch brunch mako, only themuppets repo can be added manually in local_manifest.xml in your .repo/local_manifests directory.
Sorry for the delay in a proper doc, got quite busy, and had little time do write something accurate.

I'm sorry - I am still not getting a zip file when I follow the steps on the wiki.
I sync the repo using the instructions,
Code:
repo sync -j1
It completes, I don't make any changes to the repo. I run the build
Code:
. build/envsetup.sh
brunch mako
It seems to complete without any errors. I do see complaints that I don't have an omni.dependencies file. Do I need to manually create that? I really want the purest rom - nothing special.

I think you have to create it, but I'm not perfectly sure..anyone else?

22anl said:
I think you have to create it, but I'm not perfectly sure..anyone else?
Click to expand...
Click to collapse
No. If you don't get a zip in your out folder, you've got a build error.

OK, that helps, I will comb through the output and see if I can find out what I'm missing. Thanks!
Sent from my Nexus 4 using xda app-developers app

You may need to cherry pick from gerrit to get it to build right
Also, here's what it will look like if your build is successful

Sweet thanks guys! I got it building, I somehow missed that I needed to do breakfast before I did a sync and build.

[DEV]CM 10.1 Salsa development

Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.

theschneidi said:
Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
Click to expand...
Click to collapse
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.

vigoos said:
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.
Click to expand...
Click to collapse
Thanks,
Still downloading all packages
Hope it will work
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" />
<project name="projects/marvel/kernel_htc_msm7227-3.0.git" path="kernel/htc/msm7227" revision="master" remote="cryptomilk" />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="Ganster41/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="ProjectLlama/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/>
</manifest>

vigoos said:
...
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
...
Click to expand...
Click to collapse
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin

theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk

vigoos said:
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.

theschneidi said:
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
Click to expand...
Click to collapse
There's some problem in that XML it means, I'll study the XML from ma few other devices so I can get an idea where the problem is
Sent from my GT-P3100 using Tapatalk

theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk

vigoos said:
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
In some threads I read that they deleted those lines in the XML. I will try that method first. Hope I'll get a build this evening. I got some other errors, which I post here in a few days.

vigoos said:
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Click to expand...
Click to collapse
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk

djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Ok, I will try it. Some things I had to change in kernel. When all things from 3.0 don't work I switch to the good old 2.6.x kernel.
OWL-Predator works with Salsa, the last CM10 for icong is built with it.
Vielen Dank DjOlivier

djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Danke DjOlivier. It wasn't interrupting but it was rather a big boost.... So we will switch back to owl now. We are able to compile with owl properly, it is not a really big deal. And vielen dank for the XML. I'll fix it today.
Sent from my GT-P3100 using Tapatalk

No problem... Here's CM10.1 git for marvel. I'm utterly convinced CM10.1 will work on icong. 3.x kernel has also been discontinued because the developer lacks time. There are many other devs who have tried to continue, but none of them has succeeded yet. If you need help with CM10.1, I'm here. Also @Kevinjoa, @thehacka1 or @izi501 are experts from wfs fora...
Gesendet von meinem LT26i mit Tapatalk

I got a Question if you dont mind me asking, how stable or bugfree is CM10.1 for WFS? Also since 4.4 got out why not just go directly for that as it seems to be running on a lot of the older devices.

CM10.1 is 90-95% bugfree, there are some small bugs here and there but it depends on the user if he notices them or not.
As for CM11 (4.4), we are currently fighting with CM10.2 for WFS. I don't think it's possible to port it. Nah, wait: It's certainly possible, but that will cost you a huge amount of time and it will probably never run well. Support for ARMv6 was dropped long time ago and there are so many features that won't work on armv6. So let's better port CM10.1 and make it as stable as possible.
Gesendet von meinem LT26i mit Tapatalk

djolivier said:
...
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="cm-10.1"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="cm-10.1"/>
Click to expand...
Click to collapse
I would suggest the branch cm-10.1 instead of jellybean because it doesn't compile without error.
djolivier said:
<project name="airk000/hardware_qcom_display" path="hardware/qcom/display" revision="jellybean2" />
Click to expand...
Click to collapse
I try now airk000 instead of WinSuk.
The guys from AndroidARMv6 have a CM-10.2 and 11 branch too, so we can hope that maybe a device like Wildfire S or Salsa could run the newer Android versions. But that doesn't make sense, if only three or more people try to get these Android versions working. It is not very difficult but it takes a long time. I do that only in my free time as an engineer student.
EDIT:
 @vigoos
device/htc/icong/libcamera/mt9v113.c:25:23: fatal error: linux/io.h: No such file or directory
I think media/mt9v113.h and mt9v113_regs.h could be the next error messages. I have to check this first, but mt9v113 is not in kernel 3.0.x. Switching back to an older kernel would be a better idea or I try to find the right files to integrate them into kernel.

I totally agree with you, but why not using WinSuk's qcom display?
As I said above, 4.4 is possible. But I also lack time since I'm a student (who goes to school) and a build environment. Back to Kitkat, it may work, but if not, we have to accept that armv6 development slows down and it's only a matter of time until even devs abandon their projects and move along to other devices (if they haven't already).
Gesendet von meinem ODYS-Chrono mit Tapatalk 2

I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB

Kevinjoa said:
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
Click to expand...
Click to collapse
In arch/arm/configs/cyanogen_msm7227_defconfig from OWL-Predator-KERNEL you find a config that works. Maybe CPU frequencies have to be changed.

Make me a icong.config and I will build rom again and you will tell me if it works

Out of no where, Errors w/in AndroidManifest.xml - Help Please...

Things have been going good within the app and I have been running the app on my phone or tablet throughout the build with no issues.
All of a sudden, I have errors within the Manifest and it will not run/load on to my phone or tablet any longer.
I have googled for answers and "fixes" but have not been able to make any progress, I hope that I can get help here and get everything back in working order so I can move forward with the build.
The only thing I can think of that I did prior to seeing the errors was I may have "Alt+Enter" and chose API Google by accident at one point.
I went back and deleted all the Google things from my manifest and so forth. It was at this point I noticed the errors within the manifest.
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.z.flowmaster">
<application ---------------------------> App is not indexable by Google Search; consider adding at least one Activity with an ACTION-VIEW intent filler.
android:allowBackup="true" --------------------------------------------- On SDK Version 23 and up, your app data will be automatically backed up and restored on app install. Consider adding the
android:icon="@mipmap/ic_launcher" ---------------------------------attribute android:fullBackupContent to specify an @xml resource which configures which files to backup. More info at ............
android:label="Backflow Master"
android:supportsRtl="true"
android:theme="@style/AppTheme" />
<activity android:name=".ActivityHome"> ------------> Element activity not allowed here / This inspection highlights unallowable XML ......
<intent-filter> --------------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android rsource files & AndroidManifest.xml
<action android:name="android.intent.action.MAIN" /> --------> Element action is not allowed here / This inspection highlights unallowed XML .....
<category android:name="android.intent.category.LAUNCHER" /> --------> Element catagory is not allowed here / This inspection highlights ......
</intent-filter> ----------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android resource files & AndroidMainfest.xml
</activity> --------------------------> says same as below "activity"
<activity android:name=".TestingMain" /> ---------------> "activity" is highlighted "Element activity is not allowed here."
<activity android:name=".TestingRP" /> --------------------------- This inspection highlights unallowed XML tags in Android resource files and AndroidManifest.xml
<activity android:name=".TestingDC" />
<activity android:name=".TestingPVB" />
<activity android:name=".TestingSRVB" />
<application/>
</manifest>

Assuming you are using AS, under the build tab in Android Studio, try clicking on "Clean" and then do a "Re-build"

Yes, I am using Android Studio 2.1.1
* However, I will note that at the time the error first occurred I was using 1.5.1 I believe.
After getting the error and trying a few things to rid the error, I finally just uninstalled the full program and reinstalled (new version) Android Studio.
I think I reinstalled everything correctly but I could have left something out or something is out of place I guess.
I feel like I have checked to make sure the reinstall was done correctly but that's not saying I didn't miss something...
After going to >Build >Clean Project I receive the following in my Messages "Gradle Build":
! A problem occurred evaluating project ':app'.
>Failed to apply plugin [id'com.android.application']
>Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users .....
! BUILD FAILED
! Total time: 0.611 secs
! 1 error
! 0 warnings
! See complete output in console
When I "Rebuild" it gives me the same as above.

Can you post the contents of your Gradle properties files here. I think this is where the issue lies "Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users ....."

-Project-
v Flowmaster
v app
build.gradle
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
defaultConfig {
applicationId "com.example.z.flowmaster"
minSdkVersion 16
targetSdkVersion 23
versionCode 1
versionName "1.0"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:24.0.0-alpha1' ----------> This support library should not use a different version (24) than the compileSdkVersion(23) / There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion.)
}
-Project-
v Flowmaster
v gradle
v wrapper
- gradle-wrapper.jar
v gradle-wrapper.properties
#Wed Oct 21 11:34:03 PDT 2015
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-2.8-all.zip
-Project-
v Flowmaster
v gradle
- build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.1.0'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
-Project-
v Flowmaster
v gradle
- build.properties
# Project-wide Gradle settings.
# IDE (e.g. Android Studio) users:
# Gradle settings configured through the IDE *will override*
# any settings specified in this file.
# For more details on how to configure your build environment visit
# http://www.gradle.org/docs/current/userguide/build_environment.html
# Specifies the JVM arguments used for the daemon process.
# The setting is particularly useful for tweaking memory settings.
# Default value: -Xmx10248m -XX:MaxPermSize=256m
# org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
# When configured, Gradle will run in incubating parallel mode.
# This option should only be used with decoupled projects. More details, visit
# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
# org.gradle.parallel=true

Trying to compile LineageOS 18.1 for discontinued SM-T713

I've been following the instrucsions from here:
[GUIDE/HOW-TO] Building LineageOS for an Unsupported Device
Foreword: This is my own notes I created to build LOS for my device (SM-T713 or gts28vewifi). After reading this, I encourage you to create your own notes as it will help you better understand the build process. I followed the official guide...
forum.xda-developers.com
To try and compile LOS 18.1, and I am using this manifest:
local_manifests/gts28vewifi.xml at lineage-17.1 · team-infusion-developers/local_manifests
Contribute to team-infusion-developers/local_manifests development by creating an account on GitHub.
github.com
And i am getting this error. Wondering if anyone has any insight into how to get past this. Thanks in advance:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1

@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.

thefanum said:
Code:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1
Click to expand...
Click to collapse
The above error is because you are trying to use the 17.1 tree and compiling 18.1 and you are not picking up the 18.1 tree at
https://github.com/LineageOS/android_hardware_samsung/commits/lineage-18.1
If you look at the March 18, 20 and 21, 2021 changes, that's where they added libperfmgr.

retiredtab said:
@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.
Click to expand...
Click to collapse
You're the man! Thanks so much for your help here.
I'm on it!